2024-08-01_Draft_Traction_Power_Scope_of_Work.pdf
PDF 12 MB Posted
- Attached to
- Notification to the Industry on Draft Traction Power Request - TIME EXTENDED for Proposals
- Solicitation number
- 0000032160
- Issued by
- Fresno County, Kern County, Kings County, Madera County, Merced County, Sacramento County, Tulare County, Fresno City, Kingsburg City, Kernville CDP, Madera City, Madera Acres CDP, Madera Ranchos CDP, Corte Madera Town, Merced City, University of California-Merced CDP, Kings Beach CDP, Sacramento City, East Tulare Villa CDP, Tulare City, California
About this file
This document is a notice from the California High-Speed Rail Authority (Authority) inviting interested industry participants to submit comments and feedback on a draft Request for Proposals (RFP) for the upcoming Traction Power, Solar Photovoltaic, and Battery Energy Storage Systems (Traction Power) procurement. The Authority anticipates delivering this project utilizing a progressive design-build method. The industry review period will take place from August 1 through August 12, 2024, with industry one-on-one meetings held thereafter through August 22. Firms that provide comments will be eligible for one-on-one meetings with the Authority. The RFP is anticipated to be released in Fall 2024, with proposals due in Late Winter 2025 and the contractor selected in Summer 2025.
The document states that all comments submitted and any accompanying materials will become property of the Authority and are subject to open government laws. Firms are advised that the Authority will not be liable for the disclosure of any information submitted, including any materials designated as "TRADE SECRET" or "CONFIDENTIAL." The Authority does not guarantee that it will have meetings with all firms, and such meetings will be at the Authority's discretion.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PDB Traction Power Procurement
RFP No.:
Request for Proposals for Progressive Design Build Services for Traction Power, Solar Photovoltaic, and Battery Energy Storage Systems
DRAFT SUBJECT TO CHANGE AND
AUTHORITY BOARD APPROVAL
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
/2
Exhibit A Scope of Work
Draft Scope of Work
SCOPE OF WORK
This document provides the scope of work for the Contractor, including the areas of responsibility as described below.
Introduction to Scope of Work
The Authority intends to use solar farms and energy storage systems to enable full operation of the traction energy used by its high-speed trains and rail system installations. This will include provision of power to the passenger stations, including building, site lighting and public bus EV charging. While the goal is for these energy generating methods to sustain all these required energy needs, the traction power substations (TPSS) will also be connected to the power grid to ensure sufficient energy at all times of operation and provide a redundant source of power for full operational loads.
The Work is the progressive design and build of the Authority’s traction power, solar photovoltaic (PV) and Battery Energy Storage Systems (BESS), including all design, construction and testing activities required to complete the requirements of the Work.
The Work also includes ongoing maintenance of all assets constructed and tested as part of the Work until the commencement of revenue service, plus a maintenance period of 5 years of revenue service, with Contractor maintenance commencing from the completion date of dynamic testing and Final Acceptance of the 119-mile First Construction Section (FCS). This period includes all required documentation and training to facilitate the handover of maintenance responsibilities. Operations of the Work is not included in this Contract.
The traction power system will be a 25-0-25 kV auto-transformer (AT) system fed from static converters and operated as a closed synchronous mesh. The static converters will be supplied from a 3-phase 34.5 kV sub-transmission system which will interconnect the PV and BESS distributed energy resources (DER), and the bulk supply utility connections with Pacific Gas & Electric (PG&E).
Static converters are proposed at the TPSSs to address traction power phase imbalance and harmonics, under acceleration and regenerative braking, and to facilitate the integration of PV power to achieve carbon neutral traction power, and a battery energy storage system to mitigate peak demand impact to the grid and associated costs.
The Work also includes proactive engagement with the Interfacing Contractors and the Authority to ensure the successful identification of all technical and non-technical interfaces across the Interfacing Contracts and to ensure that interfaces are integrated consistently. The Contractor shall work with the Authority to develop the Authority’s
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Program Integration Management Requirements document. The Contractor shall follow a holistic, structured, and interdisciplinary engineering management process to achieve the performance requirements set forth in the Authority’s Systems Development Life Cycle (SDLC) requirements in this Contract.
As further described in the General Terms and Conditions, the Work shall be performed in a progressive manner by the Contractor in two phases:
1. Phase 1 – Preconstruction Phase, consisting of (a) Phase 1A – Preliminary Design (also referred to as the “Design Principles” Phase), and (b) Phase 1B – Detailed Design; and
2. Phase 2 – Construction, Testing, and Maintenance Phase, consisting of (a) Phase 2A – Construction and Testing, and (b) Phase 2B – Maintenance.
The Phase 1 Work will include the preparation of the designs for the Phase 2 Work, the provision of recommendations regarding constructability, risk allocation, cost, and schedule; and preparation and submittal to the Authority of Work Package Proposals for the Phase 2 Work. As more fully described in the General Terms and Conditions, the Phase 1 Work will also include: recommendations to the Authority on the planning, design, and proposed construction of the Project; participation in partnering workshops;
design and estimate coordination meetings and formal milestone review meetings;
recommendations for offsite manufacturing and early works; subcontracting plan development; and coordination with the Interfacing Contractors.
This Scope of Work describes the detailed activities to be performed as part of the Phase 1 Work and the scope for the Phase 2 Work. The parties will negotiate the specific scope of each Work Package for the Phase 2 Work as part of Phase 1.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Project Sites and Geographical Limits of Work
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Each TPSS site comprises:
• Utility connection with PG&E, including any utility owned assets that the utility will permit the project to construct and transfer to the utility for 4 of the 6 TPSS necessary to power the EOS (TPSS 7, 9, 10 & 12).
• Sites for TPSS 8 & 11 shall be designed for connection to the OCS. Provisions for future connections to PG&E, BESS, distributed PV and train stations with ZEV bus charging loads will be provided;
• Sub-transmission busbar (presently proposed to be 34.5 kV, to be confirmed by the Contractor) for the connection of utility connections, PV systems, BESS, train station loads including ZEV bus charging and static converters for traction;
• Static converters for traction (minimum 2 units on an n-1 basis);
• 25-0-25 kV traction busbar;
• High and medium voltage interconnecting cables for all assets;
• Grounding system for power system faults and lightning discharges;
• Auxiliary supply transformers;
• Compounds and buildings, staff amenities, building services, civil works, fire protection, etc.;
• BESS for generation collection and dispatch
• Secondary systems including station battery system, protection, and supervisory control and data acquisition (SCADA) as needed; and
• Access road for heavy equipment and emergency services (Transformers…)
• PV systems including solar tracking mounting structures, inverters and MV transformers;
• Interconnecting cables up to 34.5KV switchgear connecting the PV farms to the
TPSS
• Control logic hardware and software necessary for integration with the master control center at the associated TPSS.
• Grounding system for power system faults and lightning discharges;
• Auxiliary supply transformers;
• Compounds and buildings, staff amenities, building services, civil works, fire protection, etc.;
• Access road for heavy equipment and emergency services (Transformers…).
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
During the design process, the Contractor will study all possible interactions between solar PV, BESS, utility (PG&E), and the OCS and propose the most optimum system combination possible (Coupling Solar PV and BESS at DC level or AC level - usage of static convertors in different configurations; location of BESS with TPSS or Solar PV farms…). The Contractor shall consider the available land owned by the Authority to evaluate and identify the most optimum solution for the solar PV and BESS configuration.
• Auto transformer and 25-0-25 kV traction busbar;
• Interconnecting cables;
• Grounding system for power system faults and lightning discharges;
• Auxiliary supply transformers;
• Cabinets and building services, civil works, fire protection, etc.;
• Secondary systems including station battery system, protection, and supervisory control and data acquisition (SCADA) as needed; and
• Access road for heavy equipment and emergency services (Transformers…).
Standards to be complied with
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. EN 50119:2020
b. EN 50122-1:2022
c. EN 50149:2012
d. EN 50206-1:2010
e. EN 50317:2012+A1:2022
f. EN 50318:2018+A1:2022
g. EN 50367:2020+A1:2022
h. EN 50488:2021
i. EN 50124-1:2017
j. EN 50124-2:2017
a. EN 13674-1:2011+A1:2017
b. EN 13674-2:2019
c. EN 13715:2020
d. EN 13848-1:2019
e. EN 13848-3:2021
f. EN 13848-4:2011
g. EN 13848-5:2017
h. EN 15273-3:2013+A1:2016
i. EN 15302:2021
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
j. EN 14363:2016+A1:2022
k. EN 13230-1:2016
l. EN 13230-2:2016
m. EN 13230-3:2016
n. EN 13230-4:2016+A1:2020
o. EN 13230-5:2016
p. EN 13230-6:2020
q. EN 13450:2013
a. EN 50121-1:2017
b. EN 50121-2:2017
c. EN 50121-5:2017
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
General Requirements and Deliverables
This section describes general deliverables and requirements the Contractor shall comply with for each Phase of the Contract.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. A design narrative with each design submission, which shall include:
1. List of applied standards.
2. List of standard variances/non-conformances.
3. Designer’s risk assessment.
4. Design decision log.
b. Typical drawings/models for:
1. Single line diagrams
2. Control diagrams
3. Site plan playout with integration to the line
4. Cable routes.
5. Under track ducting.
6. Fencing, gates, locking system and Signage.
7. Access road surfacing.
8. Equipment cabinets and Buildings.
9. Grounding and Bonding.
10. Switchgear
c. Technology selection(s).
d. Design simulations for train operations.
e. Design simulations for Solar energy production and storage.
f. System Architecture Drawing(s).
g. Major Feeding diagram.
h. Proposed list of mock-ups for Authority inspection.
i. Alternative feeding scenarios.
j. Initial schedule of quantities.
k. Preliminary cost estimate for construction.
l. Buy America compliance plan.
m. Long Lead Item Identification and Procurement Plan
n. Cyber Security Management Plan (In collaboration with the Authority).
o. EMC Management Plan.
p. Fire and Life Safety Management Plan.
q. Safety and Security Plan
r. System Certification Management Plan
s. Human Factors Integration Plan.
t. High level testing and commissioning strategies.
u. Strategy for obtaining FRA certification.
v. Asset naming/Identification strategy.
w. Signage proposal/strategy.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. A review meeting schedule accounting for key milestones in the software development cycles.
b. An action list with allocated responsibilities for resolution, to be actively managed by the Contractor.
c. A Contractor managed tracker document or dashboard covering the following key areas:
i. Key Issues
ii. Key achievements
iii. Organization
iv. Process
v. Risk Management
vi. Scope Status and Scope Changes
vii. Personnel Competency
viii. Resourcing
ix. Schedule
x. Progress recording and reporting
xi. Configuration Management Status
xii. Complexity and novelty assessment(s)
xiii. Metrics for software production, inspection and testing to facilitate trend monitoring and issue identification, including:
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Design logs.
b. Test logs.
c. Technical Queries raised to the Authority.
a. A test sequence for all relevant systems
b. A list of all applicable test specifications
c. Description of all planned site and factory acceptance tests
d. Description of all planned laboratory/factory acceptance testing
e. Format of test specifications and testing certificates
f. Any requirements for facilities, materials, equipment, or personnel required from Third Parties (including the Authority)
g. Requirements and recommendations for witnessing testing activities by Authority representatives.
h. Outline Testing Schedule
i. Proposed Organizational Chart for Contractors Testing Organization
a. A design report with each submittal, which shall include:
1. Site specific design drawings/details.
2. Designers risk assessment.
3. List of standard variances/non-conformances.
4. Design decision log.
b. Maintenance procedures and plans.
c. Final design simulations for train operations
d. Final design simulations for Solar energy production and storage
e. Testing and commissioning plan(s).
f. Final schedule of quantities.
g. Final list of mock-ups for Authority inspection.
h. Final cost estimate for construction.
i. Final circuit allocation schedule.
j. Alarm schedule.
k. Cable schematics.
l. Cable allocation drawings.
m. Detailed system designs.
n. Detailed Design Safety Case
o. Ready for construction designs/drawings.
p. Construction management plan(s).
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
q. Construction methodologies including staging plan.
r. Obsolescence Management Plan
s. Training Program Plan
t. Warranty Management Plan
u. Construction Access and Site Safety Plan
v. Method statements.
w. Detail drawings/models for:
1. Single line diagrams.
2. Site plan playout with integration to the line
3. Cable routes.
4. Under track ducting.
5. Fencing, gates, locking system and Signage.
6. Emergency access walkways.
7. Emergency exits.
8. Access road surfacing.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. A review meeting schedule accounting for key milestones in the software development cycles.
b. An action list with allocated responsibilities for resolution, to be actively managed by the Contractor.
c. A Contractor managed tracker document or dashboard covering the following key areas:
i. Key Issues
ii. Key achievements
iii. Organization
iv. Process
v. Risk Management
vi. Scope Status and Scope Changes
vii. Personnel Competency
viii. Resourcing
ix. Schedule
x. Progress recording and reporting
xi. Configuration Management Status
xii. Complexity and novelty assessment(s)
xiii. Metrics for software production, inspection and testing to facilitate trend monitoring and issue identification, including:
d. Design logs.
e. Test logs.
f. Technical Queries raised to the Authority.
a. Staging Plan
b. Testing Methodology
c. Detailed testing schedule
d. Testing hazard identification and mitigation measures
e. Format of test specifications and testing certificates
f. Organizational chart for Contractor’s testing organization
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Appropriate quality standards of the installation/fabrication
b. Correct identification of all components
c. Verification of compliance with design
a. Factory Acceptance Testing (FAT)
b. Unit and functional testing.
c. Static testing.
d. Site Acceptance Testing (SAT).
e. Integration testing.
f. Dynamic testing.
g. Soak testing/Trial Running.
h. Alternate feeding scenarios.
i. Short circuit testing.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Interface Management
This section describes specific interface requirements for the Contractor to adhere to throughout the duration of the Work.
a. How the Contractor shall interface constructively and proactively with Interfacing Contractors and the Authority in accordance with the Program Integration Management Requirements.
b. Identification of stakeholder needs and requirements
c. How the system integration and interoperability concept shall be applied.
d. Interfacing Parties and how these shall be managed; and
e. Key exchange of information and documentation with Interfacing Parties and when these are required with a give-gets register.
The System Integration Management Plan shall be submitted for review in accordance with the Systems Engineering Management Requirements.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Civil Works including Grounding and Bonding
This section describes specific requirements for civil works that the Contractor shall comply with.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Power & SCADA Works
This section describes specific requirements for traction power and SCADA works for both Phases of the Work.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Terminal and systems located at the OCC: 20 years.
b. Switchgear: 25 years.
c. Transformers: 50 years.
d. PV panel: 25 years,
e. BESS module including batteries: 15 years
f. Invertors / convertor AC / DC: 15 years.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
The Contractor shall provide inputs to a Rail Infrastructure Information Management (RIIM) system provided by Interfacing Contractors that shall enable remote condition monitoring of equipment and assets to enable rapid-response to failures and a predict-and-prevent maintenance regime to avoid failures where possible.
a. Environmental sensors (including temperature, humidity, water levels);
b. Shelter and wayside cabinet monitoring – alarms from shelters and wayside cabinets shall be as defined in the NPSTC PSGSF.
c. All power supplies (including monitoring for heartbeats, power outages, circuit breaker trips, frequency and phase, earth leakage and battery condition notifications).
d. Switch current during switch operation.
e. Heating, Ventilation and Air Conditioning (HVAC) equipment.
f. Electrical distribution systems.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
g. Critical drainage systems.
h. Movement and settlement of earthworks; and
i. Any other systems critical to the operation of train movements or required to comply with the Asset Management Plans.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Technical staff training
b. Operations staff training
c. Train-the-trainer
Project Management
This section covers project management requirements applicable for the entire duration of the Work.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Safety Case
This section describes Contractor requirements for the duration of the Work to facilitate the production and approval of the project safety case.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Safety and Security Requirements
Program and Project Integration Requirements
This section describes integration requirements the Contractor shall comply with for the duration of the Work.
a. Mobilization Phase,
b. System Definition and Operational Context Phase,
c. System Requirements Phase,
d. System Architecture Phase, and
e. Final Design Phase.
f. Manufacturing and Construction Phase
g. Testing Phases (Field/site testing, System Integration Testing, System start-up testing)
h. Pre-revenue Operation Phase
i. System Certification and Acceptance Phase
j. Operation and Maintenance Phase ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Mobilization Phase Review,
b. System Definition Review,
c. System Requirements Review,
d. Preliminary Design Review,
e. Final Design Review,
f. First Article Demonstration Review,
g. Field Testing Review,
h. System Integration Testing Review,
i. Pre-Revenue Operation Review, and
j. System Certification and Acceptance Review
The respective roles and responsibilities of the Authority, the Contractor, and the other Interfacing Contractors in relation to the integration and interfacing requirements of the Project are further described in the Program Integration Management Requirements. The Contractor shall comply with the Program Integration Management Requirements document as applicable to this Contract, except as modified herein, including:
a. Integrated Master Plan,
b. Integrated Master Schedule, and
c. Integrated Organization.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
a. Integrated Business Processes and
b. Project Integration Group.
a. System Architecture,
b. Interface Register
c. Interface Control Documents, and
d. Integrated Systems Designs.
a. Common Data Environment,
b. Federated DOORS Database,
c. Federated EMMA Database,
d. Federated Systems Model, and
e. Federated BIM Model.
f. Asset Management System
g. Document Management System
a. Interface Responsibility Matrix and
b. Design Integration.
a. Common Data Environment ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
b. Project and Federated BIM Model
a. Program Integration Management Requirements, and
b. Systems Development Life Cycle requirements.
RAM Requirements
a. Contractor RAM Management Plan
b. Validation Plan for RAM requirements
c. RAM Allocation Report
d. Historical Product Maintainability Report
e. Preliminary RAM Report
f. Reliability Centered Maintenance Report
g. Preventive Maintenance Analysis
h. Corrective Maintenance Analysis
i. RAM Prediction Report
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
j. Maintainability Demonstration Test Plan and Procedures
k. RAM performance Demonstration Plan
l. FRACAS Implementation Plan
m. Maintainability Demonstration Test Reports
n. RAM Performance Demonstration Reports
a. MTBSF = 4,855 hrs.
b. MTTRS = 2.22 hrs.
c. Percentage of missed stops = 0.0012%
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
d. Percentage of late stops = 0.045%
BIM Requirements
Coordination with other Interfacing Contractors ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Interfacing Contractors Collaboration Requirements
a. Ensure design compliance and interoperability between all onboard and wayside systems; with simulation models and
b. reduce timescales and re-work cycles.
a. attend and actively participate in design development meetings and working groups with the Contractor, the Authority, the Interfacing Contractors and other third parties;
b. attend and actively participate in such interface definition and coordination working group meetings as required or as may be reasonably requested by
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 the Authority, the Contractor or another Interfacing Contractor or that are otherwise necessary to perform interface coordination and comply with any interface requirements;
c. review schedules and plans provided by the Contractor to confirm that they adequately allow for the performance of the Interfacing Contractor’s work; and
d. provide constructability reviews and feedback to the Authority and the Contractor to identify opportunities to innovate and improve the design, and to bring best value to the Authority through cost savings and schedule savings.
a. Fully complying with the requirements of the Governance Framework document;
b. Attending and actively participating in the meetings, working groups, and workshops described above and within the Governance Framework document, including ensuring that any applicable subcontractors attend;
c. Making proper allowance in all schedules and plans for the Interfacing Contractor's work;
d. Reviewing schedules and plans provided by the Interfacing Contractors to confirm that it adequately allows for the performance of the Work;
e. Reviewing and resolving all comments to the design Work performed by the Contractor;
f. Collaborating with Interfacing Contractors on interface issues;
g. Being responsive to requests for information received from the Interfacing Contractors, including responding to the queries within five Working Days, however, if Authority input is required an additional five Working Days shall be added to permit time for the Authority’s response;
h. Coordinate and cooperate with Interfacing Contractors with respect to third party liaison and coordination necessary to the performance of both the Work and the Interfacing Contractors' work;
i. Notify the Authority of any interface or sequence of activities under Interfacing Contractor's work that may affect the progress of the Work or the schedule for the delivery of the Project overall;
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
j. Ensure the effective coordination of the design and construction of the elements included under the Work;
k. Obtain approval from the Authority on change requests from the Contractor prior to commencing any work on them;
l. Seek value engineering opportunities and discuss them collectively with the Authority, and any relevant Interfacing Contractors;
m. Fully assess any proposed scope reduction for impact prior to collective discussion with the Authority (and Authority approval shall be obtained);
n. In accordance with the Authority’s Enterprise Risk Management Policy and the Authority’s Program Risk Management Plan, attend and actively participate in monthly risk management working groups and/or periodic risk workshops, led by the Authority to assist with identifying, quantifying, and implementing risk avoidance and mitigation strategies as related to the Work. The Contractor will participate in the preparation, modification and maintenance of Authority’s risk registers related to the Work and will continuously provide feedback on Project risk as the final design progresses. The Contractor will assist the Authority in quantitative risk analysis to establish cost and schedule contingencies needed to cover the potentially adverse effects of risk events and other unknowns.
INITIAL DELIVERABLES
Upon receiving a Notice to Proceed (NTP) and initial task order from the Authority, the Contractor shall submit for approval, and implement, upon Authority’s approval, the following plans and schedule, consistent with the Authority’s policies, plans, procedures, and guidelines, including the Authority’s SDLC, within 60 days of NTP.
Engineering Management Plan. This shall include:
This plan shall detail how the Contractor will ensure that the individuals undertaking, checking and approving the design are suitably qualified, resourced and informed to undertake the roles and responsibilities satisfactorily.
It shall include details of the Contractor’s competency management process including how competencies are regularly checked and updated.
ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
This plan shall include the processes for creation, submission and control of all documents required as part of the Work. It shall include references to the Authority’s document management system and processes.
This shall detail how the Contractor will follow the Systems Engineering Management Plan requirements set forth in the SDLC document, including sustainability submittals related to this Work.
This plan shall include the RAM approach implemented for the Work and describe the organization, responsibilities, tasks, deliverables, activities, procedures, tools, and techniques to meet its RAM targets.
This plan shall include the process to be followed for the designers’ risk assessments, generation of mitigations and methods of handover of residual risks to the Authority and/or Interfacing Contractors.
The Contractor shall prepare a Sustainability Management Plan (SMP) in accordance with the applicable version of the Design Criteria Manual. This SMP shall be submitted in the Design Principles stage and shall be updated as required through the life of the Project. The SMP shall demonstrate how the Contractor will meet or exceed sustainability-related regulatory and Contract requirements of the project during design and construction activities.
The Contractor shall establish and implement a comprehensive Project Management Plan (PMP) that includes management tools, processes, and procedures and details how Contractor will plan, execute and control the Work.
The PMP shall include, but not be limited to:
The Organizational Management Plan will describe the Contractor’s organizational structure and internal management protocols. The plan shall include a description of the composition of the Contractor’s team, how activities will be assigned, and an organizational chart indicating all personnel.
The Contractor shall develop a Quality Management Plan (QMP) that includes the Contractor’s policies, and resources for comprehensive quality management
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 of all activities. At a minimum, it shall be consistent with ISO 9000 and the Authority’s Quality Manual.
The Contractor shall include a WBS which shall be agreed with the Authority.
Detailed Design Schedule
a. The number of proposed designs, and their geographical limits.
b. The order in which they will be delivered.
c. A list of proposed deliverables for each design.
d. The planned date for each design deliverable.
e. Designs shall be produced in a manner to allow the Contractor to comply with the Buy America provisions set forth in 49 U.S.C. 22905(a) and work collaboratively with the Interfacing Contractors on issues related to such.
Design Management Plan
Once approved, the Contractor will maintain the documents throughout the term of the Contract, updating as required or annually at a minimum, with updates to be approved by the Authority.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Exhibit A, Attachment 1: Definitions
EXHIBIT A, ATTACHMENT 1: DEFINITIONS
Whenever used in this Contract, the following terms have the definitions indicated.
Definitions for capitalized terms used but not defined in this Scope of Work can be found in the General Terms and Conditions, Appendix A.
Authority: The California High-Speed Rail Authority.
Commercially Useful Function: The Authority will uniformly apply best practices standards in collective consideration of Commercially Useful Function (CUF) standards set forth by 49 C.F.R. Part 26.55 (c)-(d), Government Code section 14837, California Code of Regulations title 2 section 1896.4(h), and Military and Veterans Code section 999(b)(5). A Small Business (SB), Small Business for the Purpose of Public Works (SB-PW), Disadvantaged Business Enterprise (DBE), Disabled Veteran Business Enterprise (DVBE), or Microbusiness (MB) is deemed to perform a CUF if the business meets the following CUF standards:
1. Performs a CUF when an SB/SB-PW/MB/DBE/DVBE is responsible for the execution of a distinct element of work of this Contract and is carrying out its responsibilities by actually performing, managing, and supervising the Work involved.
2. Performs work that is normal for its business services and functions.
3. Is responsible, with respect, to materials and supplies used on this Contract, for negotiating price, determining quality and quantity, ordering the material, and installing and paying for the material itself.
A firm does not perform a CUF if the business:
1. Is an SB/SB-PW/MB/DBE/DVBE that is limited to that of an extra participant in a transaction, contract, or project through which funds are passed to obtain the appearance of participation.
2. Is a DBE that does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own workforce, or the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved.
Construction Contractor: The construction contractor performing the design and construction work for the Construction Package as detailed in the applicable design-build or other type of contract.
Construction Package 1: The portion of the System’s First Construction Section currently bounded by Avenue 19 in the County of Madera to the north, and by East American Avenue in the County of Fresno to the south.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Construction Package 2-3: The portion of the System’s First Construction Section currently bounded by East American Avenue in the County of Fresno to the north, and a point approximately one mile north of the Tulare/Kern county line in the County of Tulare to the south.
Construction Package 4: The portion of the System’s First Construction Section currently bounded by a point approximately one mile north of the Tulare/Kern county line in the County of Tulare to the north, and Poplar Avenue in the County of Kern to the south.
Contractor: The party entering into this Contract with the Authority.
Day or day: Calendar day, unless otherwise noted.
Design Management Plan: Document detailing how the Contractor process for managing design resourcing, schedule, competence assessment, production, review and approval of design documents.
Design Principles: High level design(s) that conceptualizes a system or sub-system, defines the configuration of a system or sub-system and creates a general framework for a project to develop from.
Detailed Design: A design package that is the final 100% complete design for a given discipline and is ready for construction.
Direct Fixed Track: Trackwork that utilizes a pre-cast unit or in-situ poured concrete to support the track, commonly referred to as ‘slab track’, also called HSR non-ballasted track in the DCM.
Disabled Veteran Business Enterprise: A for-profit business concern that meets the certification requirements set forth in California Military and Veterans Code section 999(b)(7), including at least 51 percent ownership by a veteran of the United States Military who has at least a 10 percent service-connected disability. To be counted towards meeting the goals of the SB Program, a DVBE must (1) be certified by the California Department of General Services (DGS)’ Office of Small Business and Disabled Veteran Business Enterprise Services, and (2) perform a CUF, as defined herein, in providing services or goods that contribute to the fulfillment of the contract requirements for this procurement.
Disadvantaged Business Enterprise: A for-profit business concern that meets the requirements of Title 49, Part 26.61 through 26.73 inclusive of the Code of Federal Regulations including at least 51 percent ownership by individuals who are both socially and economically disadvantaged. To be counted towards meeting the goals of the SB Program, a DBE must be certified by the California Uniform Certification Program.
Early Operating Segment (EOS): The fully electrified, dedicated segment of the System upon which the Authority will conduct initial passenger revenue operations. It
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1 is approximately 171 miles in length beginning on the north side of Merced Station at R street in Merced and extending to the south side of the Bakersfield Station at Chester Avenue in Bakersfield, as set forth in Exhibit A, Section 2.2.
First Construction Section (FCS): A component of the EOS over which the Authority will complete testing and commissioning activities necessary to certify the System. It is approximately 119 miles in length beginning at Avenue 19 in the County of Madera and extending to Poplar Avenue in the County of Kern, as set forth in Exhibit A, Section 2.2.
Governance Framework: The governance and collaboration requirements, structures, and procedures for the Project, and ultimately the System, that are specified in the governance framework document maintained and provided by the Authority, which will be finalized following development and input from Interfacing Contractors and updated from time to time.
Interfacing Contractor: A Person engaged or to be engaged with the Authority to design, deliver, manufacturer, construct, and/or maintain or conduct other activities related or adjacent to any portion of the System that interfaces or could interface with the Work.
Key Personnel: The individuals identified in Exhibit A, Attachment 3 of this Contract, subject to change as permitted under this Contract.
LGA (Locally Generated Alternative): The southern extension of the Project included in the approved 2018 and 2019 Fresno to Bakersfield Environmental Documents spanning 18.48 miles, beginning at the southern limit of high-speed rail Construction Package 4 at Poplar Avenue in the City of Shafter and ending at the Bakersfield high-speed rail station at F Street.
Linear Referencing System: Linear referencing is the method of storing geographic locations by using relative positions along an already existing measured line feature.
Distance measures and a known line feature are used to locate other features along the line.
M-M (Merced to Madera): The northern extension of the Project included in the approved 2020 Central Valley Wye Environmental Documents spanning 33.9 miles, beginning at the northern limit of high-speed rail Construction Package 1 at Avenue 19 in Madera and ending in downtown Merced to the north and at Carlucci Road to the northeast.
Microbusiness: A for-profit SB concern that meets the certification requirements set forth in California Government Code section 14837(d) and California Code of Regulations title 2 sections 1896.4 (Definitions) and 1896.12 (Eligibility) including its principal office is located in California, its owners reside in California, it is not dominant in its field, and it has an average gross annual revenue of $5 million or less over the previous three tax years. To be counted towards meeting the goals of the SB Program, a Microbusiness must be certified by DGS.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
Party or Parties: Individually referring to the Authority or the Contractor or collectively referring to the Authority and the Contractor, as the context permits.
Person: Any individual or entity, including corporation, limited liability company, sole proprietorship, joint venture, partnership, trust, voluntary association, unincorporated organization, or governmental agency including the Authority.
Project: The 171-mile Early Operating Segment of the System between the cities of Merced and Bakersfield.
Rail Infrastructure Information Management: A system that facilitates remote condition monitoring of rail infrastructure and/or systems to enable rapid-response to failures and a predict-and-prevent maintenance regime whose aim is to avoid failures where possible.
Safety Case: The structured argument, supported by evidence, intended to justify that a system is acceptably safe for a specific application in a specific operating environment. Specifically in this case the operation of the railroad at 220mph using Tier III trainsets.
SB Program: The Authority’s Revised Small and Disadvantaged Business Enterprise Program for Professional Services Contracts, August 2012.
Small Business: A for-profit business concern that meets the certification requirements set forth in the California Small Business Procurement and Contract Act in California Government Code section 14837(d) and California Code of Regulations title 2 sections 1896.4 (Definitions) and 1896.12 (Eligibility) including that its principal office is located in California, its owners reside in California, and it is not dominant in its field and it has average gross annual revenue of $15 million or less over the previous three tax years. To be counted towards meeting the goals of the SB Program, a Small Business must be certified by the California Department of General Services.
Small Business for the Purpose of Public Works: A for-profit small business that is independently owned and operated, with its principal office located in California, and with owners, officers, members/managers, partners living in California, has an average of $37 million or less in gross annual receipts over the previous three tax years, is not dominant in its field of operations and has 200 or fewer employees. This certification is issued by the California Department of General Services.
System: The entire California high-speed rail system as described in California Proposition 1A (2008), including Phase 1, which shall run from the San Francisco Bay Area to the Los Angeles basin, and Phase 2, which shall run from Sacramento to San Diego.
Technical Contract Requirements: The requirements determined by the Contractor and captured in the System Requirements Baseline that the traction power, solar PV
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
/2 http://www.hsr.ca.gov/wp-content/uploads/2022/04/SB_ProfServ_ProgramPlan-202202-RFQ-A11Y.pdf http://www.hsr.ca.gov/wp-content/uploads/2022/04/SB_ProfServ_ProgramPlan-202202-RFQ-A11Y.pdf and BESS component systems, subsystems, elements, or components shall achieve in order to meet the Contract Requirements.
Work: All of the services, tasks, and deliverables to be provided by the Contractor and its subcontractors as required under the terms of this Contract.
Working Day: Monday through Friday, except for federal and/or state holidays, between the hours of 8:00 a.m. and 5:00 p.m., Pacific Time. Lists of federal and state holidays can be found at the websites for the U.S. Office of Personnel Management and California Department of Human Resources, respectively.
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
/2 http://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview http://www.calhr.ca.gov/employees/pages/state-holidays.aspx
Exhibit A, Attachment 2: Acronyms
EXHIBIT A, ATTACHMENT 2: ACRONYMS
AT Auto-transformer BESS Battery Energy Storage Systems BIM Building Information Modeling CP 1 Construction Package 1 CP 2-3 Construction Package 2-3 CP 4 Construction Package 4 C.F.R. Code of Federal Regulations CUF Commercially Useful Function DB Design-Build DBE Disadvantaged Business Enterprise DER Distributed Energy Resources DGS California Department of General Services DVBE Disabled Veteran Business Enterprise EOS Early Operating Segment FAT Factory Acceptance Testing FCS First Construction Section FRA Federal Railroad Administration ISO International Organization for Standardization MB Microbusiness MTBSF Mean Time Between Service Failures MTTRS Mean Time to Restore Service NTP Notice to Proceed OCC Operations Control Center OCS Overhead Contact System PG&E Pacific Gas & Electric PV Photovoltaic RIIM Rail Infrastructure Information Management RAMS Reliability, Availability, Maintainability, Safety RFQ Request for Qualifications SAT Site Acceptance Testing SB Small Business SB-PW Small Business for the Purpose of Public Works SCADA Supervisory Control and Data Acquisition TO Task Order TPSS Traction Power Substations TSI Technical Specification for Interoperability
D ra ft P
D B
T ra ct io n P ow er
S co pe o f W or k fo r
In du st ry
R ev ie w
/1
| 1 Scope of Work |
| 1.1 Introduction to Scope of Work |
| 1.1.1 The Work includes the production of designs of systems elements that cover all the operation stages and the detailed design and construction for the EOS (Early Operation Segment), including the elements of those systems inside facilities such as... |
| 1.1.2 The as-built information from the Construction Contractors for CP 1, CP 2-3, and CP 4 and track and OCS design(s) provided by the Authority shall be used by the Contractor as the baseline information to produce the designs under this Contract. T... |
| 1.1.3 The Contractor will use the high-speed train model of the selected Trainsets contractor in all simulations and design work. |
| 1.1.4 The Contractor is responsible for informing the Authority of deficiencies in the design(s) from the Track and OCS Design Contractor that would prevent the Contractor from meeting the design requirements herein. |
| 1.1.5 The Contractor shall promptly notify the Authority of any changes to the DCM that may impact the Contractor’s design and shall coordinate with the Authority regarding any updates to the design required by the Authority. |
| 1.1.6 All designs shall include provision for the future expansion of the System towards San Francisco, Los Angeles, and Sacramento without substantial re-work and with minimal impact on the operational infrastructure. All designs shall include passiv... |
| 1.1.7 S.I. units of measurement (metric) shall be used for all survey, design, and engineering data. Standard unit may be used for informative purposes only and shall be indicated as such. |
| 1.2 Project Sites and Geographical Limits of Work |
| 1.2.1 The limits of the Work are from the north side of Merced Station at R street in Merced (northern limits of the M-M project section), to Carlucci Road to the west of Chowchilla in Madera County (the western limit of the Central Valley Wye), to th... |
| 1.2.2 The Work must take into consideration the areas directly north of Merced Station, south of Bakersfield Station, and the western legs of the Wye, as is necessary to produce the designs for the EOS from Merced to Bakersfield ensuring passive provi... |
| 1.2.3 There are six TPSS sites, one each at TPSS sites 7, 8, 9, 10, 11, and 12. These are spaced approximately 30 miles apart. |
| 1.2.4 Solar PV Farms shall be connected to TPSS and will include: |
| 1.2.5 There are 24 to 36 AT sites identified in the footprint included in the Work. The final number will depend on a value engineering exercise to be undertaken by the Contractor during Phase 1A. These are spaced approximately 5 miles apart in betwe... |
| 1.2.6 Each NTP (and Task Order) for Phase 1 and Work Package for Phase 2 shall include precise geographical limitations for Work (as applicable). |
| 1.2.7 Refer to the Systemwide Alignment Schematic for operational layout, including indicative location of special trackwork. |
| 1.3 Standards to be complied with |
| 1.3.1 The designs shall, at a minimum, comply with: |
| 1.3.1.1 California Public Utilities Commission General Order 176 |
| 1.3.1.2 National Electric Safety Code |
| 1.3.1.3 Applicable C.F.R.s including 49 C.F.R. Part 236. |
| 1.3.1.4 The technical requirements of the Energy TSI (Commission Regulation (EU) No 1301/2014 of 18 November 2014), including the following European Standards: |
| 1.3.1.5 The technical requirements of the Infrastructure TSI (Commission Regulation (EU) No 1299/2014 of 18 November 2014), including the following European Standards: |
| 1.3.1.6 Railway applications – Electromagnetic compatibility: |
| 1.3.1.7 Railway applications – Supply voltages of traction systems EN 50163:2004. |
| 1.3.1.8 Railway application – Fixed installations: |
| a. EN 50152-1:2013 |
| b. EN 50152-2:2013 |
| c. EN 50152-3-1:2017 |
| d. EN 50152-3-2:2016 |
| e. EN 50152-3-3:2016 |
| 1.3.1.9 EN IEC 60255 parts 1 through 27 2023. |
| 1.3.1.10 The technical requirements of the Energy TSI (Commission Regulation (EU) No 1301/2014 of 18 November 2014). |
| 1.3.1.11 The technical requirements of the Locomotive and Passenger Stock TSI (Commission Regulation (EU) No 1302/2014 of 18 November 2014). |
| 1.3.1.12 The technical requirements of the Command, Control and Signaling TSI (Commission Regulation (EU) 2016/919 of 27 May 2016). |
| 1.3.1.13 The technical requirements of the Noise TSI (Commission Implementing Regulation (EU) 2023/1694 of 10 August 2023). |
| 1.3.1.14 The technical requirements of the Safety in Railway Tunnels TSI (Commission Regulation (EU) No 1303/2014 of 18 November 2014). |
| 1.3.1.15 EN 50126 – Part 1, Railway applications – The specification and demonstration of RAMS Part 1: Basic requirements and generic process. |
| 1.3.1.16 EN50562 2020 - Process, measures and demonstration of safety for electric traction systems. |
| 1.3.1.17 EN50716 2023 – Railway applications, requirements for software development |
| 1.3.1.18 AREMA Standards Chapter 17 – High-Speed Rail Systems |
| 1.3.1.19 The Authority’s Design Criteria Manual and Directive Drawings. |
| 1.3.1.20 Information security standards NIST 800-53, ISO 27001 & 27002 |
| 1.3.1.21 IEC 62443 Security for industrial automation and control systems |
| 1.3.1.22 TS50701 2021 – Railway applications – Cyber Security |
| 1.3.1.23 All applicable IEEE standards and |
| 1.3.1.24 All applicable laws and regulations. |
| 1.3.1.25 Where there are differences, conflicts or contradictory requirements between European standards and US standards, these shall be dealt with on a case-by-case basis in consultation with the Authority. US legislative standards shall be prioriti... |
| 1.3.2 The Contractor shall comply with the following Authority documentation: |
| 1.3.2.1 Authority BIM Manual |
| 1.3.2.2 Authority CADD Manual |
| 1.3.2.3 Authority Concept of Operations |
| 1.3.2.4 Authority Configuration Management Policy |
| 1.3.2.5 Authority Design Criteria Manual, Version 6 |
| 1.3.2.6 Authority DOORS Manual, Version 4 |
| 1.3.2.7 Authority Enterprise Risk Management Policy |
| 1.3.2.8 Authority FRA Program Management Plan, submitted 2023 |
| 1.3.2.9 Authority GIS Manual |
| 1.3.2.10 Authority Network Integration Policy |
| 1.3.2.11 Authority Program Integration Management Requirements (and resulting Integration Master Plan) |
| 1.3.2.12 Authority Program Risk Management Plan |
| 1.3.2.13 Authority RAM Management Plan |
| 1.3.2.14 Authority Quality Manual |
| 1.3.2.15 Authority Safety and Security Management Plan |
| 1.3.2.16 Authority Systemwide Alignment Schematic |
| 1.3.2.17 Authority Systems Engineering Plan |
| 1.3.2.18 Authority SDLC Requirements |
| 1.3.2.19 Authority Strategic Asset Management Plan |
| 1.3.2.20 Authority Governance Framework |
| 1.3.2.21 Authority Asset Information Standard |
| 1.3.2.22 Authority Sustainability Management Plan |
| 1.3.2.23 Authority Matrix of Presently Known Environmental Obligations |
| 1.4 General Requirements and Deliverables |
| 1.4.1 Phase 1A - Design Principles |
| 1.4.1.1 The deliverables the Contractor shall submit during the Phase 1A shall include, but are not limited to: |
| 1.4.1.2 The Phase 1A design submittals will include all drawings (single line diagram, control diagram, site plan layout and profiles…), models, calculations or simulations (Traction power load flow analysis, trains load simulation, solar production s... |
| 1.4.1.3 The Contractor shall provide all relevant information as required by the Authority to support the Authority in the production of the System and Operational Safety Cases. |
| 1.4.1.4 The Contractor shall submit a design log with all submissions. |
| 1.4.1.5 Design deliverables shall be subject to an interdisciplinary design review with Interfacing Contractors and the Authority to identify and address design and construction interfaces across contracts prior to submission of the deliverable(s) to ... |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .