Type Of Contract Suitable for The Project

Larson & Toubro (L&T) signed the contract to construct the second Narmada bridge in
Gujarat on a build-operate-transfer basis (BOT). An organisation hires a service provider
to set up, optimise and run an IT or Business Process Service Delivery operation with the
contractual intent of transferring the operation back to that organisation as a captive centre
under the terms of a BOT agreement.
The bridge, to come up on national highway number 8 near Jadeswar, estimated to cost Rs
123 crore. Investment during construction, approach road and riverbed protection
embankment are included in this cost. The main bridge has a length of approximately 1.36
kms.
So, the type of contract suitable for this project was Fixed Price Contract (FPC) also called
Lump sum contract, involve a predetermined fixed price for the product and are used when
the product is well defined. As a result, the seller's cost risk is greater than the buyer's.

After a competitive bidding process in which three other engineering majors had staked their
claims, L&T won the contract.

Constain-Balecha Company, a UK-Indian joint venture, Escort and Gammon India. For its
size, this is the first project of its kind undertaken by the private sector as part of a build,
operate, and transfer model.

L&T has already received a letter of intent from L&T's management. After the necessary
formalities are completed, the work will be awarded upon signing of the agreement. Three
years of construction are included in the 15-year concession period. Already acquired
property will be made available for no charge.

REQUIREMENT ANALYSIS

Defining requirements sufficiently so that designers will know what they are striving for is
called requirements analysis.

PROJECT USER REQUIREMENT

A project's use cases often include user requirements that must be documented. User
Requirements definition is carried out in conjunction with the customer or product managers
who are familiar with the way the embedded system will be used by the end user. Many user
requirements are concerned with how a user will interact with a system and what that user
expects from the system in the first place.

The two main types of user requirement are: Functional requirement and System
Requirements
FUNCTIONAL REQUIREMENTS

Functional requirements specify the functions that the new system must be able to perform to
meet the user requirements. For example, the functions of the spaceship include propulsion,
handling and maneuverability, human habitability, safety, and support and maintenance. The
common tool for identifying the functional requirements of a complex system is the
functional flow block diagram, FFBD

SYSTEM REQUIREMENTS

System requirements is a statement that identifies the functionality that is needed by a

system to satisfy the customer's requirements. System requirements are a broad and narrow
subject that could be implemented to many items.

System requirements provide general direction for the project, but they are high-level and not
detailed enough to tell the project team what it must design, build, or purchase to create the
end-item system. Stipulations must be placed on each of the requirements; these are called
system specifications.

Functional Flow Block Diagram, (FFBD)