C.12_Program_Tech_Mngmt_of_Reqs,_Cert,_and_Assurance.pdf

IFB No.: HSR25-12 Fresno Station Early Works

C.12 Program Technical Management of Requirements, Certification, and Assurance (TMRCA) Rev. 1.0

Revision(s) Date Description 0 12/10/2025 Initial Release

IF

B

N o.

: H S

R

-1

IN

IT

IA

L

R E

LE

A

S E

2/

/2

Standard Specifications REQS-0017 – Program Technical Management of Requirements, Certification, and Assurance (TMRCA) Rev. 1.0

Authored: 12/9/2025 Kossell Argudo, V&V Manager Date

Checked: 12/9/2025 Mohamed El-Guindy, System Integration Manager Date

Checked:

R Greenwood 12/9/2025

Rubina Greenwood, Deputy Director of Network Integration Date

Approved: 12/9/2025 Ryan Scott, Director of Rail Engineering Date

Released: 12/9/2025 Amit Joshi, Configuration Manager Date

CALIFORNIA HIGH-SPEED RAIL AUTHORITY

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 2 of 25

Document Revision History – Program TMRCA Specifications

Second Edition

December 2025

Revision Date Revision Description

0.0 October 2025 First Edition

1.0 December 2025 Review and minor updates for clarity

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 3 of 25

TABLE OF CONTENTS

1 SCOPE OF THE DOCUMENT

2 REFERENCE STANDARDS AND DOCUMENTS

3 CROSS CUTTING SYSTEMS ENGINEERING METHODS

APPENDIX A: REQUIREMENTS MANAGEMENT: RVTM/CIL TEMPLATE

APPENDIX B: CHANGE REQUEST FORM TEMPLATE

APPENDIX C: DVR FORM

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 4 of 25

1 Scope of the Document

1.1 Scope Description

1.1.1 The scope of this Technical Specification is to define the Authority’s Requirements for Requirements Management (RM), Verification and Validation (V&V) Management, Configuration Management (CfM), Design Variance Request (DVR), and Systems Certification and Acceptance processes.

1.1.2 This specification consolidates the Authority’s systems engineering management expectations into contractual requirements. It defines the processes and deliverables necessary to ensure consistent application of Requirements Management Plan, Verification & Validation Management Plan, Project Configuration Management Plan, and Certification Management Plan practices throughout all phases of the project.

1.1.3 This Technical Specification is based on the following reference Plans:

o Requirements Management Plan (PLAN-1026) o Verification and Validation Management Plan (PLAN-1034) o Project Configuration Management Plan (PLAN-1038) o Design Variance Request Form (BULL-PDEC-02) o Systems Certification and Acceptance Plan (PLAN-1037)

1.1.4 This Technical Specification provides non-functional (or process) requirements applicable to the Contractor for RM, V&V, CfM, DVR, and Systems Certification and Acceptance. The Contractor should also refer to the Plans referred in Clause 1.1.3 for additional details on how the Authority expects the related tasks to be performed.

1.1.5 These requirements shall be implemented and managed in conjunction with the scope of work as outlined in the Technical Contract Requirements.

1.1.6 The requirements are formulated using the following words and their meanings:

• “Shall”: Indicates mandatory requirement that must be strictly implemented.

Any impossibility to fulfil this requirement must be agreed through a derogation case (see change management procedure).

• “Must”: Indicates an obligation or a mandatory requirement.

• “Should”: Indicates preferred course of action, recommendations. No agreement of derogation is necessary, there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course - for example the same goal is reached by other solutions, which are permissible within the binding standards or documents.

• “May”: Indicates a permissible course of action within the limits of the standards, but which is not mandatory to be fulfilled.

The Schedules define the technical scope of the Work for the Project. The requirements set out in these Schedules are mandatory. The Contractor is obliged to comply with these requirements, subject to any waivers and variations from specific requirements that the Authority may grant in its sole discretion, or for which the Contractor may apply through the Design Variation Request (DVR) process.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 5 of 25

2 REFERENCE STANDARDS AND DOCUMENTS

2.1 Authority documents

# Document Title

1 REQS-0003 Systems Development Life Cycle (SDLC) Requirements

2 PLAN-1015 System Engineering Management Plan (SEMP)

3 PLAN-1037 System Certification and Acceptance Plan

4 PLAN-1038 Project Configuration Management Plan

5 PLAN-1034 Verification and Validation Management Plan

6 PLAN-1026 Requirements Management Plan

7 TM 1.1.18 Design Variance Guideline

8 BULL-PDEC-02 DVR Form (Rev. 1)

9 PD-ROD-SE-021-Rev0 DOORS Manual

2.2 Standards

# Document Title

1 ISO/IEC/IEEE 15288 System Life cycle Processes

2 ISO/IEC 10007 Quality management – Guidelines for configuration management

INCOSE Systems Engineering Handbook Rev. 5: A Guide for

System Life Cycle Processes and Activities

An official, globally recognized guide for understanding and applying systems engineering processes and activities throughout a system's life cycle

4 FRA CFR Title 49, Parts 200-299 U.S. Department of Transportation, Title 49 Code of Federal Regulations, Parts 200 to 299

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 6 of 25

3 CROSS CUTTING SYSTEMS ENGINEERING METHODS

3.1 General Requirements

3.1.1 The Contractor shall implement effective Requirements Management to ensure the successful delivery of the project and alignment of the final product with the Authority’s standards, codes, and safety requirements.

3.1.2 The Contractor shall implement a comprehensive Verification and Validation (V&V) Management process to ensure that all project components and systems fully meet or exceed the established project and program requirements. This process shall support the successful delivery of a safe, reliable, and efficient high-speed rail network.

3.1.3 The Contractor shall implement a comprehensive a Program Integration Program to deliver a fully integrate high-speed rail system that meets the highest performance and standards.

3.1.4 The Contractor shall implement Configuration Management within the project that complies with applicable state laws related to high-speed rail, as well as all other relevant state and federal laws, regulations, and standards.

3.1.5 The Contractor shall implement effective System Certification Management to ensure that the system readiness, operational readiness and maintenance readiness are appropriately reviewed and considered. This management process shall ensure the successful delivery of the project and aligns with the CHSRA System Certification Management Plan and CHSRA System Certification Acceptance Plan.

3.2 Requirements Management

3.2.1 The Contractor shall align their requirements management activities in accordance with Requirements Management Plan (PLAN-1026).

3.2.2 The Contractor shall capture, manage, and maintain all the requirements in the Requirements Management (RM) Tool in accordance with Systems Development Life Cycle (SDLC) Requirements (REQS-0003) and DOORS Manual (PD-ROD-SE-021- Rev0).

3.2.3 The Contractor RM Tool shall include technical contract requirements, Stakeholder requirements, System requirements, Procurement Requirements, Regulatory Requirements, Operations & Maintenance Requirements, RAM Requirements, Interface Requirements, Safety & Security Mitigations, Environmental Requirements, Sustainability Requirements, Asset Management Requirements, allocated requirements, and new/derived requirements resulting from Engineering Analysis, Engineering Best Practices, and/or Change Management.

3.2.4 The Contractor RM Tool shall identify and manage the Technical Contract Requirements (TCR) Types, including the following:

• Operational requirements

• Safety requirements

• Security requirements

• Environmental requirements

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 7 of 25

• Sustainability requirements

• Reliability, Availability, Maintainability (RAM) requirements

• Functional requirements

• Performance requirements

• Physical requirements

• Interface requirements

• Expandability requirements

• Logistics, support, other requirements

3.2.5 The Contractor’s RM Tool shall identify and manage the TCR design elements by the following:

• General design criteria

• Survey and mapping

• Clearances

• Track geometry

• Trackwork

• Intrusion protection

• Civil site design

• Drainage

• Utilities

• Geotechnical design

• Seismic design

• Structural design

• Tunnels

• Stations

• Support facilities

• Mechanical

• Electrical

• Plumbing

• Grounding and bonding

• Corrosion control

• Hardware

• Software

3.2.6 The Contractor shall submit a Requirements Management Plan (RMP).

3.2.7 The Contractor’s RMP shall describe all roles involved in the RM process.

3.2.8 Any update or modification to the Contractor’s RMP shall follow the same review, approval process and resubmit to the Authority as per the Project Configuration Management Plan (PLAN-1038).

3.2.9 Contractor key personnel involved in RM shall be professionals with at least 10 years of relevant experience.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 8 of 25

3.2.10 The Contractor shall submit resumes of Key Personnel to the Authority for review and approval.

3.2.11 The Contractor RMP shall specifically include a detailed implementation of the RM process in the RM tool as described in the REQS-0003 and PD-ROD-SE-021-Rev0.

3.2.12 The Contractor shall provide requirements for bi-directional traceability throughout the SDLC using the RM tool as described in the REQS-0003.

3.2.13 The Contractor shall use the RM Tool to collect stakeholder technical requirements at all levels of the CHSR System.

3.2.14 The Contractor’s RM Tool shall demonstrate compliance to TCRs using the RVTM and CIL as described in the REQS-0003 and PD-ROD-SE-021-Rev0.

3.2.15 The Contractor’s RVTM and CIL shall comply with Appendix A.

3.2.16 The Contractor shall maintain TCRs, maintain traceability, Verification and Validation (V&V) information, and control changes to the TCR baseline by using the RM Tool.

3.2.17 The Contractor shall create links using the in-built functionality of the RM Tool in accordance with REQS-0003.

3.2.18 The Contractor shall ensure that changes to requirements, baselines or milestones are done in a controlled manner and managed by the Contractor’s Configuration Management (CfM) process that aligns with PLAN-1038.

3.2.19 The Contractor shall write new requirements in a common form as described in the INCOSE Guide to Writing Requirements that aligns with PLAN-1026.

3.2.20 The Contractor shall assign a unique identifier to each new requirement.

3.2.21 The Contractor shall ensure requirements are reviewed and approved by the Authority before they are issued.

3.2.22 The Contractor shall use a requirements action tracker to document comments, responses, actions and resolutions from Technical Contract Reviews.

3.2.23 The Contractor shall assess and action residual requirements prior to the final design.

3.2.24 The Contractor shall provide a requirements volatility matrix in compliance with section 9.13 of PLAN-1026.

3.2.25 The Contractor shall manage through formal approval and release of successive Configuration Baselines any changes to requirements that may impact another.

3.2.26 The Contractor shall formally issue Requirements Baseline at specific stages in the project lifecycle or when significant scope changes occur in accordance with REQS- 0003.

3.2.27 The Contractor shall identify, develop, record and manage Derived Requirements as described in REQS-0003.

3.2.28 The Contractor shall perform a requirements analysis based on all applicable standards and references.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 9 of 25

3.2.29 All applicable requirements identified shall constitute Technical Contract Requirements (TCR) and be managed under the processes described in Schedule 3.

3.2.30 The Contractor shall perform Engineering Analyses and place the identified requirements relating to the Work into the requirements management tool established by the Track/OCS Design Services Consultant.

3.2.31 Each of the Contractor’s Engineering Analysis shall have a separate module in the requirements management tool.

3.2.32 Additional technical requirements derived from the Contractor’s engineering analyses shall be allocated to the correct system and traced down to objective evidence.

3.2.33 The Contractor shall develop, implement, manage, submit and maintain a comprehensive Project inspection and testing plan to define how the TCRs are verified in accordance with REQS-0003.

3.2.34 The Contractor’s Project Inspection and Testing Plan shall develop, submit, manage and maintain an individual inspection and test management plans for the following:

• Prototype Testing

• First Article Compliance Inspection

• Production Run Testing

• Factory Acceptance

• Inspections

• Site Acceptance

• Interoperability Test

• Start-Up Testing

• Pre-Revenue Testing

• Reliability, Availability, Maintainability Testing

• Safety Certification

• Security Certification

3.2.35 The Contractor’s individual inspection and test management plans shall address the following:

• Inspection and test preparation

• Inspection and test coverage

• Inspection and test execution

• Inspection and test reports

• Inspection and test failure reporting, analysis and corrective action system

• Regression inspection and testing

3.3 Verification and Validation Management

3.3.1 The Contractor shall develop and implement a V&V process to demonstrate by provision of objective evidence compliance to contract requirements.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 10 of 25

3.3.2 The Contractor shall develop, maintain and submit a Verification and Validation Management Plan (CVVP).

3.3.3 The Contractor shall document their V&V process in the CVVP that aligns with System Certification and Acceptance Plan (PLAN-1034) and REQS-0003.

3.3.4 The Contractor shall document their V&V process for RAM requirements that specifies verification scope, objectives and activities implemented to demonstrate design compliance with the Project RAM requirements in the CVVP that aligns with System Certification and Acceptance Plan (PLAN-1034) and REQS-0003.

3.3.5 The Contractor shall apply V&V activities early in the project life cycle to provide consistency and control while enabling validation processes later in the project life cycle.

3.3.6 The CVVP shall address roles and responsibilities, methods, tools, and metrics used for Project V&V activities.

3.3.7 The Contractor shall submit Technical Contract Submittals (TCS’s) together with Contractor V&V report to the Authority Network Integration & Assurance (NIA) Team in accordance with REQS-0003.

3.3.8 The Contractor shall submit a Verification and Validation (V&V) Report that includes a RVTM demonstrating that the design and construction comply with all applicable TCRs.

3.3.9 The Contractor shall provide a Verification and Validation (V&V) Report that includes a CIL, demonstrating that the final design and construction comply with all applicable TCRs.

3.3.10 The Contractor shall develop and submit a RAM Verification Report (RVR) to demonstrate compliance of the Final Design with RAM requirement.

3.3.11 The Contractor shall develop and submit a RAM Validation report (refer to Section

6.28 of PLAN-1033 for additional details) during the Integration and System Validation Phases, the.

3.3.12 The CIL shall include Safety requirements, including hazard mitigations and resolutions, Security requirements including threat mitigations and resolutions, Interfaces and interoperability items, Environmental requirements and mitigations, Sustainability requirements and goals.

3.3.13 The Contractor shall trace the requirements to the supporting objective evidence, whereby tracing is defined as using RM tool links.

3.3.14 The Contractor shall use external links (hyperlinks) to trace objective evidence that is located outside of the RM tool.

3.3.15 The Contractor shall include a Certificate of Conformance in the V&V Report, self-certifying that the submittal complies with all applicable contract requirements.

3.3.16 The Contractor shall identify Critical Items that cannot be closed prior to the start of the next Project phase at each Project lifecycle milestone and provide a justification, using the RM tool.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 11 of 25

3.4 Configuration Management

3.4.1 General

3.4.1.1 The Contractor shall develop and maintain a Configuration Management Plan (CfMP) ensuring that all documents, software, and hardware configurations are uniquely identified, traceable, and controlled throughout the SDLC.

3.4.1.2 The Contractor shall prepare, submit and implement a comprehensive Configuration Management (CM) process as defined in the INCOSE Systems Engineering Handbook Rev 5.

3.4.1.3 The CM process shall include (1) planning of CM, (2), performing configuration identification (CI), (3) performing configuration change management, (4) performing configuration status accounting, (5) performing configuration evaluation, and (6) performing release control.

3.4.1.4 The Contractor shall develop a Configuration Management Plan (CfMP) that aligns with PLAN-1038.

3.4.1.5 Any deviation from PLAN-1038 shall be approved by the Authority’s Configuration Manager.

3.4.1.6 The Contractor’s CfMP shall describe the governance of tools, roles, and processes required to apply Configuration Management to project-level technical information products.

3.4.1.7 The Contractor’s CfMP shall address any variances or inconsistencies in governance and identified Configuration Items to preserve seamless integration.

3.4.1.8 The Contractor shall identify a Configuration Manager with at least 10 years of work experience in the stated field of expertise for Configuration Manager position.

3.4.1.9 The Contractor’s CfMP shall define CfM roles by functional title rather than individual name.

3.4.1.10 The Contractor’s CfMP shall identify Responsibility, accountability, and decision authority roles that are applicable to the development and approval of a Configuration Item (CI) and Baseline.

3.4.1.11 All Contractor Personnel involved in CM shall complete training in accordance with Contractor’s Competence Management Plan.

3.4.1.12 The Contractor shall develop, implement, and maintain as a CI a RACI Matrix showing Authority and contractor roles and configuration data ownership.

3.4.1.13 The Contractor shall use Document Control as a prerequisite for Configuration Management.

3.4.1.14 The Contractor shall ensure there is only a single source of truth for each CI at any given time.

3.4.2 Configuration Identification

3.4.2.1 The Contractor shall identify CIs and follow the approval process under the governance described in PLAN-1038.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 12 of 25

3.4.2.2 The Contractor shall identify and maintain as a CI all hardware, software, system architectures, and associated documentation.

3.4.2.3 The Contractor shall identify, assess, document, control, and communicate changes to the Authority that may affect:

• Scope of Work

• Requirements or Baseline Documents

• Design and Engineering Deliverables

• Configuration Items and Configuration Baselines

• Safety, RAM, or Reliability Performance

• Regulatory or Contractual Compliance

• Cost and Schedule

3.4.2.4 The Contractor shall assign attributes to each CI, including:

• Unique identifier

• Description

• Location

• Associated Configuration Baseline

• Version Number

• Intended Modification Status

• Actual Modification Status

3.4.2.5 The Contractor’s CfMP shall identify items subject to configuration control down to the Lowest Replaceable Unit.

3.4.2.6 Tools used by the Contractor to produce CIs shall be documented, with matching baselines managed in both the tool and the CfM repository.

3.4.2.7 The Contractor shall establish and maintain Systems Configuration Baselines identifying stable CIs at well-defined points in the Project Lifecycle including each SDLC Milestone.

3.4.2.8 The Contractor shall ensure that all Configuration Baselines are traceable, version-controlled, and recorded in the approved Configuration Management System or repository designated by the Authority.

3.4.2.9 The Contractor shall maintain configuration records to ensure full traceability between each CI, its associated requirements, design documents, test results, and as-built records.

3.4.3 Change Management

3.4.3.1 The Contractor’s CfMP shall follow the general provision of the latest version of FRA CFR Title 49, Parts 200-299.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 13 of 25

3.4.3.2 The Contractor shall establish an Internal Change and Configuration Board (CCB) to govern all change and configuration activities within the scope of its contract.

3.4.3.3 The Contractor CCB shall review, evaluate, and approve all planned and unplanned changes affecting the CIs.

3.4.3.4 The Contractor CCB shall initiate and assess Configuration Audits.

3.4.3.5 The Contractor CCB shall maintain minutes, action items, and decisions for all CCB meetings.

3.4.3.6 The Contractor shall define clear escalation criteria and, where necessary, submit change proposals to the Authority’s CCB for review and approval of significant configuration impacts.

3.4.3.7 The Contractor shall provide the Authority with advance notification of any CCB meetings where Authority review or concurrence is required.

3.4.3.8 The Contractor shall ensure that all change decisions, approvals, and audit outcomes are documented and linked to the corresponding Configuration Baselines.

3.4.3.9 The Contractor CfMP shall establish a Change Request Form (CRF) to document the changes to the CI.

3.4.3.10 The Contractor CRF shall align with the CRF Template in Appendix B.

3.4.3.11 The Contractor shall record all proposed changes using a CRF that includes:

• Change Description and Rationale

• Impacted Reference Documents and Configuration Items

• Affected Systems, Assets, or Interfaces

• Proposed Implementation Date

• Summary of Impact Assessment

3.4.3.12 The Contractor shall baseline CIs in compliance with PLAN-1038.

3.4.3.13 The Contractor’s CI administrative or clerical changes shall not result in a formal revision update but shall be logged in change history.

3.4.3.14 The Contractor shall distribute Change notices to the Authority after release of a

CI.

3.4.3.15 The Contractor shall perform a comprehensive Impact Assessment for each proposed change.

3.4.3.16 The CIs shall be presented in a hierarchical and structured manner enabling the identification of affected CIs and baselines for impact assessment.

3.4.3.17 The Impact Assessment shall include as a minimum:

• Technical impact (design, requirements, interfaces, configuration, including other systems impacted)

• Cost and schedule impact

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 14 of 25

• Safety and RAM impact (incl. hazard re-evaluation)

• Verification and validation consequences

• Compliance with legal, regulatory, or standards requirements

3.4.3.18 The Contractor shall ensure that approved changes are formally incorporated into

Configuration Baselines and recorded in the Configuration Management repository.

3.4.3.19 The Contractor shall establish the configuration baselines as described throughout the SDLC phases.

3.4.3.20 The Contractor shall maintain records of all approved, rejected, or pending changes and ensure they are traceable to the associated CI and baseline.

3.4.3.21 The Contractor shall cover migration between tools in the Project’s Risk Management process

3.4.4 Design Variance Request Guidelines

3.4.4.1 The Contractor shall comply with Design Variance Guideline (TM1.1.18) when requesting deviation from mandatory design criteria, contract requirements, Authority’s technical specifications or national and international standards.

3.4.4.2 The Contractor shall identify non-standard design elements requiring variance early in the design process and submit an inventory of non-standard features for Authority review.

3.4.4.3 The Contractor shall perform a preliminary assessment for each variance to determine feasibility, impacted systems, and required mitigations.

3.4.4.4 The Contractor shall prepare a Design Variance Request (DVR) as shown in Appendix C.

3.4.4.5 The Contractor shall submit DVRs for Authority review prior to:

a. Preliminary submission for Principal Design; and

b. Final Design Review (FDR) submission for Detailed Design.

3.4.4.6 The Contractor shall address all Authority review comments and resubmit revised DVRs with a new revision number where applicable.

3.4.4.7 DVRs with potential impact to scope, schedule, or budget shall be treated as Configuration Changes and processed under the Project Configuration Management Plan.

3.4.4.8 The Contractor shall ensure approved DVR notifications are distributed to all relevant stakeholders to update related documents, including Design Criteria, Standard Drawings, Specifications, and Interface Manuals.

3.4.4.9 The Contractor shall ensure that documented DVRs support the V&V process and form part of the certification evidence package.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 15 of 25

3.4.4.10 The Contractor shall provide a Design Variance Register that records all submitted, approved, and rejected variances including identifier, title, discipline, date, status, and cross-reference to associated Configuration Item or Change Record.

3.4.5 Configuration Status Accounting

3.4.5.1 The Contractor shall create, manage, and maintain a Configuration Data Accounting.

3.4.5.2 The Contractor’s Configuration Data Accounting shall include CI approval details, change descriptions, and repository locations.

3.4.5.3 The Contractor shall organize Configuration Data Accounting for transfer to the Authority.

3.4.6 Configuration Audits

3.4.6.1 The Contractor shall conduct regular Configuration Audits to verify compliance with Configuration and Change Management requirements.

3.4.6.2 The Contractor shall provide the Authority with evidence of the Configuration Audits conducted, in the form of Configuration Audit Reports.

3.4.6.3 The Contractor’s Quality Management team shall conduct audits every 6 months (unless the Authority deems more frequent) of CfM processes

3.4.6.4 The Contractor’s Subject matter experts and the Configuration Manager shall support audits as appropriate.

3.4.6.5 The Contractor’s CfMP shall be subject to Authority oversight and audit.

3.5 Systems Certification and Acceptance Plan (SCAP)

3.5.1 The Contractor shall submit a SCAP for Authority’s approval.

3.5.2 The Contractor’s SCAP shall adhere to the requirements set forth in this document, REQS-0003, and System Certification and Acceptance Plan (PLAN-1037).

3.5.3 The Contractor’s SCAP shall specify the Governing Requirements, Certification Milestones, Certification Packages (packages to receive Contractor self-certification), Certification Granularity, Certification Tools and Methods, Roles and Responsibilities, and System Certification Report Template.

3.5.4 The Contractor shall specify sources of project requirements, how the systems integration (SI) team will identify those requirements, and the process the SI team will use for managing those requirements in the Governing Requirements section of their

SCAP

3.5.5 The Contractor shall specify when the project will submit the package level System Certification Reports in the Certification Milestones section of their SCAP.

3.5.6 The Contractor shall specify to what level of granularity the project team will certify the packages in the Certification Granularity section of their SCAP.

3.5.7 The Contractor SCAP shall list these certification packages in an appendix.

3.5.8 The Contractor shall specify the planned method to create the System Certification Report, including how the SI team will use the RM Tool in the certification process, REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 16 of 25 and the contents of the System Certification Report in the Certification Tools and Methods section of their SCAP.

3.5.9 The Contractor shall specify which roles on the project team are responsible for preparing, reviewing, approving, and submitting the System Certification Report and the package of supporting documentation in the Roles and Responsibilities section of their SCAP.

3.5.10 The Contractor shall provide the System Certification Report template as an appendix to the SCAP.

3.5.11 The Contractor shall provide the Packages to Receive Certification as an appendix to the SCAP.

3.5.12 The Contractor shall provide a Case Certification with Case Certifications being as described in REQS-0003.

3.5.13 The Contractor shall provide the Design Case certification at the completion of the Final Design Review (FDR).

3.5.14 The Contractor shall certify that the Design and Implementation phase has been completed and that it conforms to the contractual requirements on their Design Case certification

3.5.15 The Contractor shall provide the Construction Case at the completion of the First Article Demonstration Review (FAR) and the Field-Testing Review (FTR).

3.5.16 The Contractor shall certify that the manufacturing and construction has been completed and that it conforms to the contractual requirements in Construction Case certification.

3.5.17 The Contractor shall provide the Test Case at the completion of the System Start-up Testing Review (STR).

3.5.18 The Contractor shall certify that the entire rail system has been integrated and that it conforms to the contractual requirements in the Test Case certification.

3.5.19 The Contractor shall provide the Operating Case at the completion of Pre-Revenue Operation (PRO).

3.5.20 The Contractor shall certify that the System Validation phase has been completed and that it conforms to the contractual requirements in the Operating Case certification.

3.5.21 The Contractor shall provide the System Safety Case at the completion of the System Certification and Acceptance Review (SCR).

3.5.22 The Contractor shall certify that the System Acceptance phase has been completed and that it conforms to the contractual requirements in the System Safety Case certification.

3.5.23 The Contractor shall use the RM Tool to manage the System Certification Metrics.

3.5.24 The Contractor shall report the progress towards system certification considering the planned Certification Granularity in the System Certification Metrics.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 17 of 25

3.5.25 The Contractor shall present the total number of certified packages and percentage of certification packages that are complete in the System Certification Metrics.

3.5.26 The Contractor shall show the number of in-progress certification packages and number of planned certification packages in the System Certification Metrics.

3.5.27 The Contractor shall provide a System Certification Report for each Certification Case.

3.5.28 The Contractor shall include an executive summary with a description of the elements subject to certification and the applicable certification case (i.e., design case, construction case, etc.) in their System Certification Report.

3.5.29 The Contractor shall include a system certification form with a completed and signed system certification form, as defined in other Contract documents, in their System Certification Report.

3.5.30 The Contractor shall include a system certification metric (Refer to section 4.5.3 of REQS-0003) in their System Certification Report.

3.5.31 The Contractor shall include the V&V Submittals (section 4.3.2 of REQS-0003) of the Technical Contract Submittal (TCS) as objective evidence in their System Certification Report.

3.5.32 The Contractor shall refer to REQS-0003 section 4.5.4 for further details regarding the System Certification Report.

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 18 of 25

APPENDIX A: REQUIREMENTS MANAGEMENT: RVTM/CIL TEMPLATE

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 19 of 25

APPENDIX B: CHANGE REQUEST FORM TEMPLATE

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 20 of 25

APPENDIX C: DVR FORM

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 21 of 25

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 22 of 25

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 23 of 25

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 24 of 25

REQS-0009 Program Technical Management of Requirements, Certification, and Assurance 25 of 25