CalMod Design-Build Electrification Services

Transcription

1 SECTION SYSTEMS INTEGRATION AND INTEGRATOR REQUIREMENTS PART 1 GENERAL DESCRIPTION A. This section specifies the system-wide integration requirements for the Caltrain Electrification system, i.e. the System. GENERAL A. The Design-Build Contractor, identified as Contractor, shall be responsible for the System-wide integration of all hardware and software within their scope of Work. The Contractor shall be responsible for the implementation and management of the integration of the System and for their design, installation and testing interfaces with the existing and new external systems that include but are not limited to JPB Engineering, Operations and safety, EMU Vehicles, CBOSS PTC, Signals, Highway Grade Crossings, Communications, SCADA, OCS, TPSS, CEMOF, ROCS, other railroad tenants and operations, associated hardware, software and human operations and maintenance support systems. B. The Contractor shall be responsible for systems integration to ensure: compliance with all performance and functional requirements, safety certification requirements, System/subsystem reliability, availability and maintainability requirements, and provision of integrated training and maintenance support materials. C. The Contractor shall be responsible to coordinate with all affected stakeholders satisfactory integrated solutions to resolve all integration issues. D. The Contractor shall review and coordinate their Work with the Reference Documents provided in Volume 4 as is necessary to integrate their Work into the System in accordance with the requirements of the Contract. DEFINITIONS A. Definitions shall be in accordance with IEEE 100, The Authoritative Dictionary of IEEE Standards Terms and Definitions, and the Glossary of Terms and Acronyms in the Scope of Work. REFERENCE STANDARDS A. The Contractor s systems integration plan and procedures shall be based upon a rigorous and Project specific approach, such as that defined in IEEE 1220: IEEE Standard for Application and Management of the Systems Engineering Process, or approved equivalent. SUBMITTALS A. Systems Integration Management Plan; B. Requirements Traceability (Baseline) Matrix and monthly summary reports on requirements traceability and management including planned actions; C. Configuration Management Plan; Contract # 14-PCJPB-P-053 Page 1 of 6 (Rev. 2.0, )

2 D. System Database Standards, System Database Administration Tool(s); E. Design Review Submissions; F. Verification and validation compliance reports as defined in the System Integration Management Plan; G. The JPB will facilitate meetings on a regular (bi-weekly or as otherwise needed at the discretion of the JPB) basis at which the Contractor and interfacing 3rd party entities shall report progress and issues on work to define the resolution of associated interfaces. Attendees may include JPB departments or contractors that are required to alter operational, maintenance and logistical support systems and processes for which they are responsible. Contractor participation, including the preparation of any materials relating to interface status reporting shall be included in the Contract price. PART 2 PRODUCTS Not Used PART 3 EXECUTION 3.01 GENERAL A. System Integration Management Plan: 1. The Contractor shall develop and submit for SONO a System Integration Management Plan, as part of the Systems Engineering Plan that delineates all systems integration activities throughout the lifecycle of the project. The System Integration Management Plan shall describe how the Contractor plans to manage and control integration risk associated with interoperability and other mission critical aspects. 2. The System Integration Management Plan shall: a. Define how progress and issues are communicated within the Contractor s organization and how such information is then consolidated for reporting to JPB; b. Establish the activities and documentation for validation and verification of the System including: i. Verification actions to incrementally confirm that the delivered System, subsystems and services will meet the requirements of these Specifications. ii. Validation actions to incrementally confirm that the behavior of the delivered System, subsystems and services will meet JPB s needs and standards. c. Establish the activities and documentation requirements of systems integration activities, necessary to support the Reliability, Availability, Maintainability (RAM) Program, the Safety Program, the FRA Certification process including submittals and overall System Safety Certification. B. Requirements Traceability and Management (RTM): Contract # 14-PCJPB-P-053 Page 2 of 6 (Rev. 2.0, )

3 1. The Contractor shall establish and manage a RTM process, using a JPB-approved requirements management and traceability process of the specified requirements and resulting works deliverables. The Contractor shall provide to JPB all required software licenses for the JPB- RTM tool installed on PCs. 2. The Contractor shall develop a Systems RTM Plan (as part of the Systems Integration Management Plan) that identifies the roles and responsibilities of the Contractor (including all subcontractors). 3. The Contractor shall identify all requirements, and systems integration requirements, and shall be responsible for their incorporation into the RTM process. The performance requirements and the systems integration requirements shall be linked through the hierarchy of Contractor prepared design documents to the appropriate Contract functional and performance requirements. 4. The Contractor shall identify and attribute that all subsystem performance requirements and functional requirements, and shall be responsible for their incorporation into the RTM process. 5. The Contractor shall identify and link the validation and verification activities for each construction segment of the project to the formal requirements, including those in the phases of; design, factory test, post installation test, subsystemslevel test, both factory and field integrated systems test, operational activation and pre-revenue test, and reliability, availability and maintainability demonstration/test including validation and verification of change throughout the contract. 6. The Contractor shall establish parameters for the RTM attributes and linkages for RTM items that are needed in the RTM database for systems integration. The RTM shall provide the ability to trace a contract requirement down to the subsystem and detailed design aspects and the software and hardware that implement the requirement and conversely that ability to trace from each piece of hardware or software the features and capabilities that link back up to contract requirements. 7. The Contractor shall establish attributes of the RTM to track verification and validation of all vital requirements throughout the design and test processes. 8. The Contractor shall submit traceability and records of all factory and field test plans, test procedures and test results to the specific contract requirement or corresponding design requirements. The Contractor shall include RTM aspects of all factory and field integration tests of software running in the host hardware, all re-test for new hardware or software releases, integration test within the subsystems, factory tests of functionality and interoperability before shipment, post installation tests, and final systems-level on-site cut-over tests. C. PTC Configuration Management: 1. The Contractor shall be responsible for updating overall configuration management as modified by this project. a. The Contractor shall utilize the JPB approved CBOSS Configuration Management Plan, which may be included as a part of the Systems Engineering Plan, to document a configuration management program including processes for declaration of configuration baselines, change Contract # 14-PCJPB-P-053 Page 3 of 6 (Rev. 2.0, )

4 D. Design Reviews: requests, modifications, and update releases. Corrective changes that materially affect the configuration, or have the potential for affecting the configuration, shall be treated as change requests. b. The Configuration Management Plan shall cover all System hardware and software design, design analysis and hazard analysis documentation, factory and field test plans and procedures, associated test equipment and simulation tools, test facilities, operations, JPB field force account support and maintenance documentation and all other items that are normally placed under configuration control for a safety and mission critical system. CBOSS plans and specifications are included in Volume 4 as reference. 1. The Contractor shall be responsible for leading all design reviews. 2. The Contractor shall be responsible for verification and validation of all systemlevel design requirements. Requirements traceability verification that is programmed to be achieved by inspection of the design shall be formally documented including references to any higher level hierarchal documents. 3. The Contractor shall report all design concerns and deficiencies to JPB as soon as the concern/deficiency has been identified and with sufficient detailed information to for a preliminary characterization of the problem. E. Working Groups and Design Workshops: 1. The Contractor shall schedule and administer a series of workshops with representatives from JPB to incrementally advance systems engineering to allow re-validation of the design and integrated work throughout the life cycle of the project. The primary objective will be to resolve design issues as early as possible and in advance of formal verification activities that are the scheduled design review and test milestones. 2. The Contractor shall lead or participate, as requested, in Working Groups with JPB staff, consultants to JPB, and other nominated participants. 3. The Contractor shall maintain a log of all issues and potential requirements changes that arise from the Working Groups. F. Performance Compliance: 3.02 DESIGN REVIEW PROCESS 1. The Contractor shall be responsible for ensuring compliance with the specified functionality and performance requirements. 2. The Contractor shall allocate performance and functional requirements to each Electrification and Signal subsystem and interfacing element of work to ensure that the specified requirements are met. The Contractor shall report the verification of these requirements to JPB throughout the project. 3. The Contractor shall conduct performance simulations to demonstrate the throughput and runtime capabilities of the traction electrification, integrated wayside signaling and grade crossing warning Systems. A. During System design development, JPB will monitor the Contractor s progress to verify compliance with the requirements through design reviews and audits. Design reviews Contract # 14-PCJPB-P-053 Page 4 of 6 (Rev. 2.0, )

5 and audits shall be conducted jointly by JPB, the Contractor, and other JPB-designated parties. SONO by JPB shall not constitute relief from contractual obligations. Reviews shall be conducted incrementally, and, as a minimum, grouped for the major system elements listed below. All ancillary and associated designs shall be included in the reviews of the major system elements below. Each succeeding level of design review shall update the material from the previous review as well as advancing the design to the next level. B. Design reviews shall be held to review system and subsystems designs for each of the following major areas. Reviews can be combined for logically associated system elements and locations, and are subject to SONO by the JPB. 1. Electrification: a. OCS b. TPSS c. SCADA d. CEMOF e. JPB operations, maintenance and safety 2. Signals & Communications: 3. Vehicles a. CBOSS/PTC; b. ROW Signals; c. Highway Grade Crossings; d. Communications e. ROCs a. EMU Vehicles C. Provide all required design review materials for a scheduled design review at least twenty (20) working days prior to the proposed review date and notice to the JPB PM for all design reviews. D. Preliminary Design Review (PDR): 1. The purpose of these reviews is to ensure that the Contractor fully understands the basis of design and can express rational assumptions relating to the design at the start of the detail design process. A PDR shall be conducted by the Contractor for each interface, subsystem or combination thereof prior to detail design so that JPB can determine that the Contractor will adequately progress the design at the start. 2. Submit to JPB, within 60 days after the Contract Notice of Award, a date by which a satisfactory PDR can be performed. Hold the reviews on mutually agreeable dates at a JPB designated location. JPB may, at its sole discretion, elect to hold the review at a contractor s facility. E. Critical Design Review (CDR): Contract # 14-PCJPB-P-053 Page 5 of 6 (Rev. 2.0, )

6 1. Conduct these reviews incrementally when the detail design of an item is at least to the 50% design completion level. This review will determine that the detail design of the item under review will satisfy the design requirements in these Specifications and to establish exact interface relationships between the item and other items of equipment, software or facilities being procured under this or other contracts. Hold the review on mutually agreeable dates at a JPB designated location. JPB may, at its sole discretion, elect to hold the review at a contractor s facility. 2. The final wayside layouts and CIH, case, and other facility layouts with maintenance facilities and clearances shall be completed no later than CDR. 3. The final housing construction detail, including cabling facilities and requirements shall be completed no later than CDR. 4. Detailed plans, procedures and schedules for the installation and commissioning of the System shall be completed no later than CDR. F. Final Design Review (FDR): 1. The final design review shall be conducted and the design reviewed for SONO by JPB. END OF SECTION Contract # 14-PCJPB-P-053 Page 6 of 6 (Rev. 2.0, )