Infosys Microsoft Alliance and Solutions blog

« WPF - Performing Conditional Validation | Main | Visual Studio 2010 Beta 1 install experience »

Understanding an ERP implementation – Bridge Analogy

This is a simplistic approach of relating an ERP implementation to constructing a bridge (under Build, Operate and Transfer basis by a private contractor) due to the inherent nature of activities being the same in both the scenarios.

The making of a bridge entails site inspection to ground preparation to blueprinting ending with construction where there are tests in the intervening duration to ensure that this is safe and can serve the intended purpose without risking the lives of the users who are going to use this to go from Point A to Point B. The work is not limited to only bridge but also entails making approach roads and giving a complete end to end solution to the commuter needs.

The ERP implementation is no different! Let’s see how…

S. No.

Stage in Bridge Construction

Stage in ERP Implementation

Important Consideration

Ground Preparation
Project Planning


This is the planning phase in which the entire work plan is made, teams are organized, responsibilities given and basic discussions/groundwork is started to assess the details needed for design
The initial discussions around the scope of work, team structure, execution details and discussions, formation of teams by partner and client, objectives and outcomes expected
·Business user buy-in at client end,
·Organization readiness for change,
·Communication of objectives and expected benefits,
·Be as open as possible with partner to  help him understand the details
Defining Dependencies
Project Initiation 


Regulations, blasting controls & approvals, contractor negotiations for outsourced work, deciding on methodology of execution, identifying external dependencies
Understand the client business needs, pain points, success criteria, regulatory environment, need for 3rd parties involvement, project execution methodology (waterfall, agile, etc.), external dependencies (product vendors, add-ons ISVs, other solutions)
·Business needs and pain points must be clearly articulated and documented
·Project execution methodology once frozen need to be religiously followed
·Risks around the external dependencies need to be documented and understood by client and partner
Site Inspection
Scoping & Requirement Gathering


To see that the real scenario of the bridge site and assess the potential situations. This helps in defining accurate scope of work and arriving  a ‘good’ budgetary number
It is very important to define the scope of the ERP implementation along with the details of what all would be covered in the execution plan. This will help in arriving at a ‘good’ budgetary number which can help in budgeting for the entire project.
·Any increase in scope of work can impact project cost
·Scope delimitation and finalization is a very important part of the overall project execution
·This helps the partner to plan the execution more effectively


This is the phase in which the design starts and the load, span along with other design parameters are decided. This also includes incorporating affect of external (environmental) load factors like Wind, Seismic forces, flooding, etc.


The broad architecture, technical design and entity definition happens in this stage. There is a focus on the both functional and non-functional items along with focus on load factors like Concurrent users, time zones, transaction loads, peak load analysis, bandwidth availability, hardware needs, network detailing and interface loads
·The loads around users, transactions, network, hardware and instance strategy should be properly sized
·The need for interfaces, reports, legal formats, statutory needs, data migration elements need to be planned for development to proceed smoothly


Once the design is completed with finalized parameter, we would move into actual construction. This would not be limited to construction of bridge but would also involve –
·   Strengthening the foundation where the bridge would rest
·   Making the correct road alignment for the approach roads both at approach and exit from bridge
This involves setting up the coding standards and best practices for the development Lifecycle (Strengthening the foundation), code development for the business needs (making the bridge), Building the interfaces (approach roads) and configuring the reports
·The code development should commence once the design has been finalized so that there are no reworks – which leads to delays, errors and integration issues later
·The interface details need  to be very clearly captured along with their fit into the overall design and business process


Each component of the bridge like girders, foundations, angles, connectors, rivets are tested individually and finally the entire bridge is loaded and tested as well
Each code component has to be unit tested. The final code has to undergo multiple rounds of system integration testing to see that they work together and finally the users have to conduct the User Acceptance Testing for the customizations developed.
·SIT should happen after the interfaces are built to ensure they work in a test environment
·The User test cases must be prepared by client team well in advance to ensure complete coverage of test scenario
Communication & Inauguration
Cutover & Go-Live


With the project being completed as per the defined parameters, this is the time to make it available for public to use. The general public need to be aware of the new route and need to be given ample driving directions on the approach roads as well
There needs to be proper user training, handholding and activities around getting the business ready for the correct usage of the application for their own benefit. The data migration and final cutover of balances to the production environment will happen here
·Cutover planning is very important and should cover timing of communication and content
·Opening balances need to be carried to new environment
·The change management aspects for the organization will yield benefit in this stage
Bridge Maintenance
Steady State Support


The bridge has to be maintained on an ongoing basis with regular maintenance along with any urgent maintenance as well which can sometime even entail stopping the flow of traffic on the bridge
Supporting the application for bug-fixes, software patch application, major and minor enhancements, database administration, user administration, application maintenance, access management, disaster recovery mechanism
·The support team should have all documentation from the project implementation
·The release of bug-fixes and enhancements should follow the complete lifecycle of development to testing before being deployed on production
·Disaster recovery mechanism should never be overlooked

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter