Title: Systems Integration: A Key Approach to Successfully Mitigate Risk
Abstract: This paper describes how as rail transit systems become more complex, from a hardware, software and technology standpoint, new approaches are being contemplated in order to reduce capital project risk. Systems Integration has come forward as a means to efficiently transition from traditional systems designed and installed independently without the need for a formal, structured process for physical, functional, logical, and operational integration, to more integrated systems. Systems Integration is not the silver bullet; however, it can be used to successfully mitigate project risks related to quality, cost, and schedule. This paper presents systems integration applications as a way to alleviate project risks and challenges on two light rail projects in New Jersey. A Design-Build-Operate-Maintain (DBOM) project delivery method was used for the first modern diesel light rail system in North America (The River LINE), while a more traditional Design-Bid-Build delivery option was used for the high profile, award winning Newark City Subway Extension project. With the diesel light rail turnkey project, contract specifications required the DBOM Contractor to establish a systematic, fully documented systems integration process through all phases of the project life cycle. For the Newark City Subway Extension project, the integration of legacy systems with two new supervisory control and data acquisition (SCADA) systems, a new cut and cover tunnel segment, a new emergency ventilation system with four jet fans and 125 vent fans, five above ground stations, 14 grade crossings, new track work and overhead catenary system, was deferred to the end of the construction phase. This paper discusses how and at what levels various and complex interfaces were managed - not just the technical interfaces - but also those other interfaces that control scheduling (coordination of sequential or concurrent activities), planning, information and communication. It presents methods used to ensure that interface gaps were avoided, duplication reduced, conflicting requirements across projects negotiated and managed, and coordination among all stakeholders refined. It also highlights similarities and differences in the way the systems integration process was approached for these two projects, the unique challenges faced by the project teams, and general lessons learned that can be carried forward on other capital projects.
Publication Year: 2007
Publication Date: 2007-01-01
Language: en
Type: article
Access and Citation
AI Researcher Chatbot
Get quick answers to your questions about the article from our AI researcher chatbot