C.10_Program_Digital_Engineering_Requirements.pdf

IFB No.: HSR25-12 Fresno Station Early Works

C.10 Program Digital Engineering Requirements

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

California High-Speed Rail Authority

Standard Specifications REQS-0015 – Program Digital Engineering Requirements

Rev. 1.0

Authored: 12/9/2025 Patrice Letard / Basak Dogan Date

Checked for GIS/Data Management: 12/9/2025

Sridhar Arjula, Chief of Digital Delivery and Innovation Date

Checked for CADD and Plan Preparation: 12/9/2025

Nichol Bowersox, Assistant Director of Engineering Date

Checked for Asset Information: 12/9/2025

Checked for

BIM:

Suresh Venukanthan, Director of Asset Management

12/9/2025 Patrice Letard – Planning & Engineering Office Date

Approved: 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-0015 – Program Digital Engineering Requirements 2 of 75

Document Revision History – Program Digital Engineering Requirements

Second Edition

October 2025 Revision Date Revision Description

0.0 October 2025 First edition

1.0 December 2025 Reviewed/updated for clarify

REQS-0015 – Program Digital Engineering Requirements 3 of 75

TABLE OF CONTENTS

1 SCOPE OF THE DOCUMENT

1.1 SCOPE DESCRIPTION

2 REFERENCE STANDARDS AND DOCUMENTS

2.1 REFERENCE STANDARDS AND DOCUMENTS

2.2 TERM, DEFINITIONS, AND ABBREVIATIONS

3 COMMON DATA ENVIRONMENT (CDE)

3.1 CDE REQUIREMENTS

4 BUILDING INFORMATION MODELLING (BIM) REQUIREMENTS

4.1 PURPOSE

4.2 SCOPE

4.3 GOVERNANCE AND RESPONSIBILITIES

4.4 BIM PROCESSES AND EXECUTION PLANNING

4.5 MODEL REQUIREMENTS

4.6 PROJECT INFORMATION STANDARD AND DATA EXCHANGE

4.7 INFORMATION AND SYSTEM SECURITY MANAGEMENT

4.8 QUALITY ASSURANCE AND CONTROL (QA/QC)

4.9 FEDERATED MODEL AND COORDINATION

4.10 ASSET INFORMATION AND HANDOVER

4.11 AUDIT, GOVERNANCE, AND CHANGE MANAGEMENT

4.12 BIM DELIVERABLES

4.13 FEDERATED MODEL REQUIREMENTS

4.14 TRAINING AND COMPETENCY

5 ASSET INFORMATION STANDARD REQUIREMENTS

5.1 INITIAL ASSET DEFINITION AND DATA REQUIREMENTS CAPTURE

5.2 GENERAL ASSET ATTRIBUTE REQUIREMENTS

5.3 ASSET LIFE-CYCLE INFORMATION REQUIREMENTS

5.4 REGULATORY REPORTING REQUIREMENTS

5.5 ASSET CRITICALITY

5.6 ASSET IDENTIFICATION, CLASSIFICATION, AND HIERARCHY REFERENCE

5.7 ASSET CONDITION RATING

5.8 ASSET INFORMATION QUALITY STANDARDS

5.9 AUTHORITY ASSET INFORMATION MANAGEMENT PROCESSES

5.10 ROLES AND RESPONSIBILITIES

6 CADD REQUIREMENTS

6.1 CADD SOFTWARE AND FORMAT

6.2 CADD FILES MANAGEMENT

6.3 CADD RESOURCES

6.4 COORDINATE SYSTEM STANDARDS

6.5 LEVELS AND SYMBOLOGY

6.6 PLOTTING STANDARD AND RESOURCES

7 PLAN PREPARATION REQUIREMENTS

7.1 ELECTRONIC FILES

REQS-0015 – Program Digital Engineering Requirements 4 of 75

7.2 PROJECT PLAN FILE FORMAT

7.3 SOFT COPY DELIVERABLES

7.4 DETAIL MODIFICATION OF STANDARD AND DIRECTIVE DRAWINGS

7.5 CONTRACT DRAWINGS

7.6 CONSTRUCTION DRAWINGS

7.7 FACILITY NAMING CONVENTIONS

8 GIS REQUIREMENTS

8.1 COMMON REQUIREMENTS

8.2 REQUIRED GIS PROJECT DIRECTORY STRUCTURE

8.3 GEODATABASE SCHEMA REQUIREMENTS

8.4 REQUIRED NAMING CONVENTIONS

8.5 GIS DATA SHARING REQUIREMENTS

8.6 REQUIREMENTS FOR CADD CONVERSION TO GIS

8.7 GIS DATA DELIVERABLES

9 MODEL BASED SYSTEM ENGINEERING (MBSE)

9.1 COMMON REQUIREMENTS

9.2 REQUIRED STANDARDS

9.3 SOFTWARE REQUIREMENTS

9.4 MBSE SUBMITTALS

10 DATA MANAGEMENT

10.1 GENERAL

10.2 DATA OWNERSHIP AND LICENSING

10.3 DATA SUBMISSION AND ACCEPTANCE CRITERIA

10.4 INTEROPERABILITY AND OPEN STANDARDS

10.5 DATA GOVERNANCE COMPLIANCE

10.6 METADATA REQUIREMENTS

10.7 AUTOMATED DATA MANAGEMENT/HANDLING REQUIREMENT

REQS-0015 – Program Digital Engineering Requirements 5 of 75

1 SCOPE OF THE DOCUMENT

1.1 Scope Description

1.1.1 The scope of this Standard Specification is to define the California High-Speed

Rail Authority’s Program Digital Engineering Requirements for Contractor(s) (Contractor), including Building Information Modelling (BIM), Computer Aided Design and Drawing (CADD), Plan Preparation (PP), Geographic Information System (GIS), Asset Information Standard (AIS), Model Based System Engineering (MBSE) and Data Management.

1.1.2 These requirements shall be implemented and managed in conjunction with the Contract Technical Requirements – Scope of Work document.

1.1.3 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-0015 – Program Digital Engineering Requirements 6 of 75

2 REFERENCE STANDARDS AND DOCUMENTS

2.1 Reference Standards and Documents

2.1.1 The Contractor shall comply with the following standards and guidance documents:

2.1.2 Where conflicts arise between this document and other documents, the California High-Speed Rail Authority’s (Authority) requirements prevail.

TABLE 1 - REFERENCE STANDARDS & DOCUMENTS

ID Reference Document Details 1 MANUAL-0003 Building Information Modeling (BIM) Manual 2 MANUAL-0004 Computer- Aided Design and Drafting (CADD) Manual 3 MANUAL-0001 Geographic Information Systems (GIS) Requirements Manual 4 MANUAL-0002 Plans Preparation Manual 5 GUIDE-0007 Asset Information Standard

6 GNRL-PWD-DC-MAN-

00001-R1-ACHSR Document and Drawing Numbering Manual

7 ISO 19650-1:2018

Organization and digitization of information about buildings and civil engineering works, including Building Information Modelling (BIM) -- Information management using building information modelling -- Part 1:

Concepts and principles.

8 ISO 19650-2:2018

Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) -- Information management using building information modelling -- Part 2:

Delivery phase of the assets.

9 ISO 19650-5:2020

Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) -- Information management using building information modelling modeling -- Part 5: Security-minded approach to information management.

10 ISO 16739:2017 Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries (ISO 16739:2013).

11 ISO 29481-1:2018 Building information models - Information delivery manual - Part 1: Methodology and format (ISO 29481-1:2016).

12 ISO 29481-2:2017 Building information models - Information delivery manual - Part 2:

Interaction framework (ISO 29481-2:2012).

13 ISO 12006-3:2017 Building construction - Organization of information about construction works

- Part 3: Framework for object-oriented information (ISO 12006- 3:2007).

14 ISO 12911:2012 Framework for building information modelling (BIM) guidance

15 ISO 12006-2:2015 Building construction - Organization of information about construction works

- Part 2: Framework for classification.

16 National BIM Standard United States Version 3 (NBIMS-US V3).

17 ISO/IEC 27001-27002 Information Security Management Systems and Cybersecurity.

18 NIST 800-53 Security and Privacy Controls for Information Systems and Organizations.

19 California SAM § 8651 California State Administrative Manual § 8651 20 MIDP Master Information Delivery Plan 21 DCM Design Criteria Manual

REQS-0015 – Program Digital Engineering Requirements 7 of 75

2.2 Term, Definitions, and Abbreviations

2.2.1 All the terms, definitions and abbreviations are provided in SPEC-0024 –

Glossary of Terms, Abbreviations and Definitions.

REQS-0015 – Program Digital Engineering Requirements 8 of 75

3 COMMON DATA ENVIRONMENT (CDE)

3.1 CDE Requirements

3.1.1 The Contractor shall be responsible for defining, developing, and maintaining a Common Data Environment (CDE) for the Work.

3.1.2 The Contractor shall be responsible for defining the information workflows, revision reviews, and profile authorization in the CDE.

3.1.3 The Contractor shall develop, submit, and implement a CDE solution, in which the collection, management, and exchange of information is performed.

3.1.4 The Contractor’s CDE shall comply with the information flow described in ISO- 19650.

3.1.5 The Contractor’s CDE solution shall enable the development of a project federated information model.

3.1.6 The Contractor shall develop and submit an Information Handover Plan to the Authority.

3.1.7 The Contractor’s CDE shall follow ISO 19650.

3.1.8 The Contractor shall test the project’s information production methods and procedures in accordance with mobilization procedures defined in ISO 19650-2 (5.5).

3.1.9 The Contractor shall provide the necessary resources to perform information exchange activities with other CDEs (CADD files, BIM models, IFC files, PDF files, and any other related files), including the Authority’s CDE or any other stakeholders/third-parties CDE’s appointed by the Authority.

3.1.10 The Contractor shall follow the GNRL-PWD-DC-MAN-00001-R1-ACHSR, that follows the nomenclature and versioning to be used following the fields defined in the ISO 19650. The Master Information Delivery Plan (MIDP) shall reflect the defined nomenclature.

3.1.11 The Contractor shall align the information review flows with the states and information containers described in ISO 19650.

3.1.12 The Contractor shall obtain the licenses for the software, platform, and tools to be used, including the CDE.

3.1.13 The Contractor shall define the information workflows and revision reviews for approval by the Authority.

3.1.14 The Contractor’s CDE shall allow and manage the addition of attributes (metadata) to each of the stored files.

REQS-0015 – Program Digital Engineering Requirements 9 of 75

3.1.15 The Contractor shall manage the versioning of the documentation and the approval workflow within the CDE.

This Section 3 defines the contractual CDE requirements applicable to the Project. These requirements are derived from MANUAL-0003 and its Appendices. Where additional detail is needed for implementation, the Contractor shall refer to MANUAL-0003 as reference guidance;

however, the obligations stated herein shall prevail and are contractually binding.

REQS-0015 – Program Digital Engineering Requirements 10 of 75

4 BUILDING INFORMATION MODELLING (BIM) REQUIREMENTS

4.1 Purpose

4.1.1 The Contractor shall implement Building Information Modelling (BIM) as the principal method for creating, coordinating, managing, and delivering all project information throughout design, construction, testing, commissioning, and handover.

4.1.2 The Contractor shall use BIM to support the Authority’s digital-delivery objectives of integration, traceability, and asset lifecycle management.

4.1.3 The Contractor’s BIM processes shall provide a single source of truth for project information, such that consistency can be guaranteed across all contracts and systems.

4.1.4 The Contractor shall use BIM to facilitate the resolution of interfaces.

4.1.5 The Contractor shall participate in the Authority’s BIM coordination meetings, as requested by the Authority.

4.2 Scope

4.2.1 The Contractor shall apply BIM requirements to all design, engineering, construction, systems, and facility elements within its scope of work.

4.2.2 The Contractor shall extend these requirements to subconsultants, suppliers, and partners producing BIM deliverables.

4.2.3 The Contractor’s interoperability of digital information shall be in alignment with Authority-defined standards and templates.

4.2.4 The Contractor shall apply BIM requirements to both geometric and non-geometric information used for design coordination, asset management, and verification activities.

4.3 Governance and Responsibilities

4.3.1 The Contractor shall develop and submit a BIM Governance structure to be approved by the Authority defining roles, responsibilities, and reporting relationships.

4.3.2 The Contractor shall appoint a BIM Manager.

4.3.3 The Contractor’s BIM Manager shall be responsible for ensuring compliance with BIM requirements and for managing information management activities.

4.3.4 The Contractor’s BIM Manager shall provide signed certificates of compliance, consistent with Section 10 of this document.

4.3.5 The Contractor shall designate Information Managers and Discipline Leads to manage model creation, data quality, and information exchange for their respective domains.

REQS-0015 – Program Digital Engineering Requirements 11 of 75

4.3.6 The Contractor shall document and submit all BIM roles and responsibilities in a Responsibility Matrix aligned with ISO 19650-2.

4.3.7 The Contractor shall be responsible for subconsultants and design partners adopting and complying with the approved BIM Execution Plan (BEP).

4.3.8 The Contractor shall participate in Authority-led Information-Management workshops and coordination meetings.

4.3.9 The Contractor shall coordinate with interfacing contractors and the Authority.

4.3.10 The Contractor’s personnel, undertaking BIM tasks, shall be trained and competent for their assigned roles.

4.4 BIM Processes and Execution Planning

4.4.1 The Contractor shall develop, submit, and implement BIM processes consistent with ISO 19650 Parts 1 and 2 and MANUAL-0003.

4.4.2 The Contractor shall submit a BEP for Authority review and approval within the period stipulated in the Contract.

4.4.3 The Contractor shall follow the Authority’s BEP template provided as an appendix to the MANUAL-0003.

4.4.4 The Contractor’s BEP shall include, as a minimum:

• Information management, governance, and responsibilities.

• Model-development strategy and software platforms.

• Information workflow for creation, review, authorization, and delivery.

• Quality-assurance and model-validation procedures.

• Schedule of deliverables and milestones.

• Training and competency plan.

4.4.5 The Contractor shall develop and submit a Master Information Delivery Plan (MIDP) integrating Task Information Delivery Plans (TIDPs) from all discipline teams for Authority approval.

4.4.6 The Contractor shall produce and submit a TIDP for each discipline team.

4.4.7 Each of the Contractor’s TIDPs shall identify for each deliverable: name, data type, format, responsible author, checker, approver, acceptance criteria, and delivery date.

4.4.8 The Contractor shall follow the Authority’s MIDP template, as provided in the appendix of the MANUAL-0003.

4.4.9 The Contractor shall maintain the BEP, MIDP, and TIDPs as controlled documents within the Common Data Environment (CDE).

REQS-0015 – Program Digital Engineering Requirements 12 of 75

4.4.10 The Contractor shall coordinate with the Authority’s Project Controls team so that BIM data is integrated for schedule (4D), cost (5D), risk, and quality management.

4.4.11 The Contractor shall verify that model data supports progressive assurance and Verification & Validation (V&V) activities.

4.4.12 The Contractor shall not modify approved BIM processes without prior written Authority approval.

4.4.13 The Contractor shall monitor implementation of the BEP and MIDP and submit status updates that identify achieved and outstanding milestones, as requested by the Authority, project milestone, or change.

4.4.14 The Contractor shall coordinate with the Authority to ensure alignment of BIM processes with the Authority’s strategies.

4.4.15 The Contractor’s BEP shall describe its OpenBIM strategy, detailing how the Contractor shall ensure consistency in the attributes within Industry Foundation Class (IFC), Version 4.3.

4.5 Model Requirements

4.5.1 The Contractor shall develop and submit discipline-specific models complying with the Authority’s BIM modeling requirements and CADD requirements.

4.5.2 The Contractor’s models shall use the coordinate system defined by the Authority to maintain geospatial consistency across all contracts.

4.5.3 The Contractor shall define and document the Level of Information Need (LOIN) and Level of Development (LOD) for each deliverable consistent with the approved BEP and MIDP.

4.5.4 The Contractor shall develop and submit, for the Authority’s review and approval, a Model Content Matrix (MCM) following the template that is provided in the MANUAL-0003.

4.5.5 Each of the Contractor’s model object shall contain metadata for unique identifier, discipline, system, Omni-Class code, Asset Definition (AD4) reference, and applicable specification linkage.

4.5.6 The Contractor shall use Authority-approved authoring software platforms.

4.5.7 Where Section 4.5.6 is not possible, the Contractor shall submit a software platform proposal that guarantees interoperability with the Authority’s CDE, for Authority approval.

4.5.8 The Contractor’s models shall be developed and submitted, for Authority review, in native formats (DGN, RVT, DWG).

REQS-0015 – Program Digital Engineering Requirements 13 of 75

4.5.9 The Contractor’s models shall also be developed and submitted, for Authority review, in open exchange format (IFC, Version 4.3).

4.5.10 The Contractor shall maintain model segregation by discipline, phase, and contract package to facilitate federation and coordination.

4.5.11 The Contractor shall update models after each approved design change and retain revision history within the CDE.

4.5.12 The Contractor’s model geometry shall represent constructible conditions and tolerances, consistent with Authority requirements.

4.5.13 The Contractor shall perform multi-discipline model coordination at each stage (or phase) and record actions and resolutions in the CDE.

4.5.14 The Contractor shall develop and submit model review reports and quality summaries with each deliverable submission.

4.5.15 The Contractor’s As-Built models shall be submitted for the Authority’s approval and accurately represent constructed conditions using verified field survey data.

4.5.16 The BIM models produced by the Contractor containing National Computerized Maintenance Management System (NCMMS) data shall be provided in the open standard Construction-Operations Building Information Exchange (COBie) format.

4.5.17 The Contractor shall use the following BIM Uses and include them and any other approved uses in the Contractor’s BEP:

Capture Existing Conditions

• Modeling Existing Conditions

• Design Authoring

• 2D Drawing Production from the Design Technical Models

• Review Design Models

• 3D Coordination—Clash Detection

• Preparation of Asset Classification for Operations and Maintenance

• BIM-GIS Integration

• Quantity Takeoff

• Programmatic Cost estimation

• Site safety Planning

• As-built Models

• Other BIM Uses, which can be used as optional in different phases of the projects, are gathered in the following matrix. The Contractor shall inform the Authority for any optional and other BIM Uses not reflected in the table below.

REQS-0015 – Program Digital Engineering Requirements 14 of 75

TABLE 2 : OTHER BIM USES

4.6 Project Information Standard and Data Exchange

4.6.1 The Contractor shall adopt and adhere to the project information standards defined in here, any Authority-issued data dictionaries or metadata schemas and in ISO 19650 to govern data structure, nomenclature, and metadata.

4.6.2 The Contractor’s data exchange formats shall comply with Authority requirements: PDF (for documents), DGN/RVT/DWG (for models), IFC Version

4.3 (open exchange), and File Geodatabase (for GIS data).

4.6.3 The Contractor shall apply file-naming and numbering conventions consistent with MANUAL-0004 and GNRL-PWD-DC-MAN-00001-R1-ACHSR.

STAGES OF THE CONTRACT DESIGN CONSTRUCTION OPERATIONS

BIM USES

1 CAPTURE EXISTING CONDITIONS M M TBD

2 MODELING OF EXISTING CONDITIONS M M TBD

3 TAKING MEASUREMENTS - COST ESTIMATION

4 4D PHASE PLANNING

5 BIM – GIS INTEGRATION M M TBD

6 PROGRAMMING

7 SITE ANALYSIS

8 REVIEW DESIGN MODELS M M TBD

9 DESIGN AUTHORING M M TBD

10 2D DRAWING PRODUCTION M M TBD

11 ENGINEERING ANALYSIS – ENERGY, STRUCTURAL,

MECHANICAL…

12 ENGINEERING ANALYSIS - OTHER ANALYSIS

13 SUSTAINABILITY ASSESSMENT 6D

14 CODE VALIDATION

15 3D COORDINATION M M

16 PREPARATION OF ASSET CLASSIFICATION FOR O&M M TBD

17 DESIGN OF THE CONSTRUCTION SYSTEM

18 DIGITAL PRODUCTION

19 3D CONTROL AND PLANNING

20 AS-BUILT MODELS M TBD

21 REGISTRATION OF THE MODEL

22 MAINTENANCE SCHEDULING

23 BUILDING SYSTEM ANALYSIS

24 ASSET MANAGEMENT

25 EMERGENCY PLANNING

26 PROGRAMMATIC COST ESTIMATION M TBD

27 SITE SAFETY PLANNING M TBD

Legend: Mandatory: M / Relevancy: Low Medium High

REQS-0015 – Program Digital Engineering Requirements 15 of 75

4.6.4 The Contractor shall manage information exchange through the CDE using the ISO 19650 workflow states (Work in Progress (WIP), Shared, Published, and Archived).

4.6.5 The Contractor’s CDE records shall include metadata for originator, discipline, revision, status, and purpose of issue.

4.6.6 The Contractor folder structures and permission levels shall be in compliance with the Authority CADD requirements and coordinated with the Authority before mobilization.

4.6.7 The Contractor shall maintain audit trails within the CDE to record document creation, review, approval, and status changes.

4.6.8 The Contractor shall implement version control and ensure that only the latest approved information is accessible for use.

4.6.9 The Contractor shall submit monthly CDE and information-delivery status reports summarizing key submissions and outstanding actions.

4.6.10 The Contractor shall develop document-control procedures that complies with the Authority’s PLAN-1038.

4.6.11 The Contractor’s BIM-related documents and records shall be configuration-controlled and stored within the CDE.

4.6.12 The Contractor’s documents and models shall include a unique identifier, revision number, status code, author, checker, approver, and issue date.

4.6.13 The Contractor shall submit a monthly Document Control Report, summarizing approved revisions, pending changes, and archived files.

4.6.14 The Contractor shall obtain prior written Authority approval for any modification to approved BIM processes, data structures, or metadata schemas, with all approved changes fully documented and traceable.

4.6.15 The Contractor’s superseded documents and models shall be clearly marked and moved to the Archived state in the CDE to prevent unauthorized use.

4.6.16 The Contractor shall follow Authority-approved conventions for version-naming and file-status codes throughout the project lifecycle.

4.6.17 The Contractor shall ensure all documented changes are traceable to their originating requests and associated deliverables.

4.6.18 The Contractor shall demonstrate configuration compliance when audited.

4.7 Information and System Security Management

4.7.1 The Contractor shall implement a security-minded approach to information and system management consistent with the Authority’s Information Security Management Plan (ISMP).

REQS-0015 – Program Digital Engineering Requirements 16 of 75

4.7.2 The Contractor shall conduct a Security Triage to determine the appropriate security level for all information assets.

4.7.3 The Contractor shall implement controls according to the security levels determined by the Security Triage.

4.7.4 The Contractor’s information systems used for BIM and CDE activities shall comply with ISO/IEC 27001 and 27002 standards and be maintained with current security patches.

4.7.5 The Contractor shall enable Multi-Factor Authentication (MFA) for user access to the CDE and related digital platforms.

4.7.6 The Contractor shall ensure encryption of data in transit and at rest using Authority-approved methods.

4.7.7 The Contractor shall develop and submit a Security Architecture Diagram in the Contractor’s BEP showing all connections, servers, and network protections prior to system use.

4.7.8 The Contractor shall perform quarterly security vulnerability assessments and report findings shall be communicated to the Authority with remediation plans.

4.7.9 The Contractor shall report all security incidents within 48 hours of discovery.

4.7.10 The Contractor shall submit reporting on security incidents within five (5) working days that include, at minimum, root-cause analysis and corrective actions.

4.7.11 The Contractor shall train project personnel on information-security awareness and roles-specific protocols.

4.7.12 The Contractor’s back-up and disaster-recovery mechanisms shall protect data from loss beyond the approved Recovery Point Objective (RPO).

4.7.13 The Contractor shall retain audit records of system access, changes, and security events for the period specified in the ISMP.

4.7.14 The Contractor’s third-party platforms used for project information shall demonstrate compliance with Authority cybersecurity requirements and provide evidence of independent certification.

4.7.15 The Contractor shall develop and submit a Project Information Security Plan detailing data classification, access controls, encryption protocols, and incident-response procedures.

4.8 Quality Assurance and Control (QA/QC)

4.8.1 The Contractor shall establish a BIM Quality Management System (QMS) aligned with ISO 9001 and the Authority’s Quality Management Plan.

REQS-0015 – Program Digital Engineering Requirements 17 of 75

4.8.2 The Contractor shall develop and submit a BIM QA/QC Plan defining model-checking, review, and approval procedures to verify data accuracy and compliance.

4.8.3 The Contractor shall validate models for completeness, accuracy, and naming convention conformance prior to each submission.

4.8.4 The Contractor shall perform clash-detection and coordination at every Authority project Lifecyle milestone and at least 30%, 60%, 90%, Ready for Construction (RFC), and As-Built stages with results logged in the CDE.

4.8.5 The Contractor shall develop and submit Model Quality Reports and QA/QC Checklists as define in the BEP with each BIM deliverable.

4.8.6 The Contractor shall resolve all identified quality issues before submitting to the Authority for review and document closure of each non-conformance.

4.8.7 The Contractor shall use automated and manual model-validation tools to verify geometry, metadata, and attribute integrity.

4.8.8 The Contractor shall participate in Authority-led model-review workshops and address comments to the Authority’s satisfaction prior to acceptance.

4.8.9 The Contractor shall maintain records of reviews and corrective actions for audit purposes and progressive assurance evidence.

4.8.10 The Contractor shall track non-conformances through closure and summarize them in the monthly quality status reports.

4.8.11 The Contractor shall develop and submit the quality status reports monthly.

4.9 Federated Model and Coordination

4.9.1 The Contractor shall develop, maintain, and submit for Authority’s review a

Federated Model integrating all discipline models and interface boundaries.

4.9.2 The Contractor shall update and submit, for Authority’s review, the Federated Model at the agreed frequency and, at minimum, for each design and construction milestone (30%, 60%, 90%, RFC, and As-Built).

4.9.3 The Contractor shall coordinate with interfacing contractors and the Authority to ensure geometric and data alignment.

4.9.4 The Contractor shall use the Federated Model to coordinate interfaces identified in the Interface Control Documents (ICDs).

4.9.5 The Contractor shall perform clash-detection within the Federated Model and record findings and resolutions in the Contractor’s CDE Clash Log.

4.9.6 The Contractor shall use the Federated Model for 4D schedule simulation and 5D cost evaluation to support constructability review.

REQS-0015 – Program Digital Engineering Requirements 18 of 75

4.9.7 The Contractor shall define model ownership and update responsibilities in the BEP and Responsibility Matrix.

4.9.8 The Contractor shall develop and submit the Federated Model in open BIM format (IFC 4.3) compatible with the Authority’s CDE.

4.9.9 The Contractor shall participate in coordination meetings and resolve all deficiencies identified by the Authority before final model approval.

4.10 Asset Information and Handover

4.10.1 The Contractor shall create and maintain Asset Information in accordance with the Authority’s Asset Information Standard and Asset Data Dictionary Definition Documents (AD4s).

4.10.2 The Contractor shall integrate asset data within the Project Information Model (PIM) to enable transition to the Asset Information Model (AIM), per ISO 19650.

4.10.3 The Contractor’s asset objects shall include metadata for type, system, location, serial number, manufacturer, warranty, maintenance frequency, and supplier details.

4.10.4 The Contractor shall provide geospatial coordinates for each asset in a File Geodatabase compatible with the Authority’s GIS system.

4.10.5 The Contractor shall classify all assets using Omni-Class codes and the AD4 hierarchical structure.

4.10.6 The Contractor shall develop and submit Asset Information Compliance Reports demonstrating data accuracy and completeness before handover.

4.10.7 The Contractor shall develop and submit As-Built Models within 60 days of construction completion.

4.10.8 The Contractor shall transfer electronically asset information to the Authority’s Enterprise Asset Management System (Maximo or successor) in approved exchange format.

4.10.9 The Contractor shall archive final models and records in the CDE in accordance with Authority record-retention requirements.

4.10.10 The Contractor shall support Authority lessons-learned and knowledge-transfer activities at project close-out.

4.11 Audit, Governance, and Change Management

4.11.1 The Contractor shall provide the Authority with access to records, systems, models, and personnel as required for audits or reviews.

4.11.2 The Contractor shall record audit findings and non-conformances in the CDE and tracked to closure within Authority-defined timeframes.

REQS-0015 – Program Digital Engineering Requirements 19 of 75

4.11.3 The Contractor shall implement corrective and preventive actions and report progress in monthly coordination meetings.

4.11.4 The Contractor shall submit proposed changes to approved BIM processes or deliverables via a Change Request Form to the Authority for approval prior to implementation.

4.11.5 The Contractor shall maintain traceability between approved changes and revised documents or models within the CDE.

4.11.6 The Contractor shall cooperate with the Authority in continuous-improvement activities and submit recommendations for process enhancements when identified.

4.12 BIM Deliverables

4.12.1 The Contractor shall develop and submit all BIM outputs identified in the approved BEP and MIDP.

4.12.2 The Contractor shall develop and submit the BEP, MIDP and MCM (Model Content Matrix) and to be updated at least once a year or as agreed.

4.12.3 The Contractor shall submit each deliverable with complete metadata and revision control.

4.12.4 The Contractor’s required BIM deliverables shall include:

• Discipline design models for civil, architectural, structural, systems and mechanical works where contract defines the scope.

• Coordinated and federated models showing resolved interfaces across contracts.

• 2-D drawings extracted from approved models at Authority-specified milestones.

• Schedules, quantities and cost data linked to model objects (4-D / 5-D integration).

• Clash-detection and coordination reports.

• Asset Information aligned with the Authority’s Asset Information Standard and

AD4 definitions.

• As-Built models and record drawings after construction completion.

• GIS deliverables, a file geodatabase containing converted CADD drawings and associated geospatial datasets, developed in compliance with the Authority’s GIS Requirements Manual to ensure seamless integration between GIS and BIM. Deliverables shall be provided on a periodical basis as agreed with the Authority (weekly, biweekly, monthly) and along with each official submission.

REQS-0015 – Program Digital Engineering Requirements 20 of 75

4.12.5 The Contractor’s BIM submissions shall be accompanied by a Model Data Compliance Statement verifying that it meets the defined LOIN and LOD and acceptance criteria.

4.12.6 The Contractor’s BIM deliverables shall include standardized facility asset data in IFC-based (Industry Foundation Class) Building Information Models, along with the native BIM files. The BIM models containing National Computerized Maintenance Management System (NCMMS) data shall be provided in the open standard Construction-Operations Building Information Exchange (COBie) format.

4.13 Federated Model Requirements

4.13.1 The Contractor shall create and maintain a Federated Model combining discipline models and interface boundaries throughout design and construction.

4.13.2 The Contractor’s Federated Model shall reflect the status of coordination and be updated at each submission milestone.

4.13.3 The Contractor shall coordinate model origins, reference systems and data structures with interfacing contractors to ensure geometric and data alignment.

4.13.4 The Contractor’s Federated Model shall be used to verify interfaces identified in the Interface Management Plan and Interface Control Documents (ICDs).

4.13.5 The Contractor shall use the Federated Model to support 4-D simulation, 5-D cost integration and constructability validation.

4.13.6 The Contractor’s Federated Model shall be delivered in open BIM format (IFC 4.3) and be fully compatible with the Authority’s CDE.

4.13.7 The Contractor shall define model accountability, update frequency and coordination responsibilities in the BEP and Responsibility Matrix.

REQS-0015 – Program Digital Engineering Requirements 21 of 75

4.13.8 The Contractor shall document federation tests to confirm file alignment and reference integrity before Authority review.

4.13.9 The Contractor shall participate in Authority-led coordination sessions to resolve integration issues.

4.14 Training and Competency

4.14.1 The Contractor’s personnel involved in BIM and Information Management shall be are trained and competent for their assigned tasks.

4.14.2 The Contractor shall develop and submit a Training Plan specifying required courses, competency levels, and assessment methods.

4.14.3 The Contractor shall develop and submit project-specific training on software tools, Authority standards and information-security requirements.

4.14.4 The Contractor shall maintain and make available records of training completion and qualifications for Authority audit.

4.14.5 The Contractor shall implement a train-the-trainer program to ensure knowledge transfer across its organization and supply chain.

4.14.6 The Contractor shall update training materials to reflect changes in Authority standards or software versions and brief affected staff accordingly.

This Section 4 defines the contractual BIM requirements applicable to the Project. These requirements are derived from MANUAL-0003 and its Appendices. Where additional detail is needed for implementation, the Contractor shall refer to MANUAL-0003 as reference guidance;

however, the obligations stated herein shall prevail and are contractually binding.

REQS-0015 – Program Digital Engineering Requirements 22 of 75

5 Asset Information Standard Requirements

5.1 Initial Asset Definition and Data Requirements Capture

5.1.1 The Contractor shall capture and submit asset data in accordance with the Authority’s

Asset Data Dictionary Definition Document (AD4), using Authority approved templates and formats.

5.1.2 The Contractor shall structure all data to support ingestion into the Authority’s Enterprise Asset Management (EAM) system.

5.1.3 The Contractor shall be responsible for submitting a draft AD4 during the acquisition phase prior to completion of final design.

5.1.4 The Contractor shall submit to the Authority an AD4 for each asset class.

5.2 General Asset Attribute Requirements

5.2.1 The Contractor shall make provisions to capture, validate, store, maintain, and make available on a timely basis the following information as defined in this section:

• General asset information to identify, classify, and locate the asset;

• General asset attribute information to describe asset characteristics and properties;

• Asset life-cycle information to support whole-life asset management; and

• Information required for NBIS and other regulatory reporting requirements;

5.2.2 The Contractor shall develop, maintain, and submit an Asset Registry to serve as the single source of asset information related to asset data over an asset’s lifecycle.

5.2.3 The Contractor’s Asset Registry shall:

• Define and identify each asset for which the contractor is responsible.

• Provide descriptive and general reference information on each asset.

• Classify each asset based on the Authority’s standard classifications (see Section

4.4 of GUIDE-0007.

5.2.4 The Contractor’s Asset Registry shall contain the following general asset information:

• The Contractor’s Asset Registry shall have a unique asset identification (ID) number to identify the asset in the asset registry.

• Asset names should contain identifying noun/modifier/attribute data based on the naming convention being used (see Section 4.3 of the GUIDE-0007).

• Asset classification shall be designated based on the Authority’s standard classification hierarchy standards (see Sections 4.4 and 4.5 of the GUIDE-0007).

• Asset location shall be designated based on the Authority’s location reference data consistent with location referencing standards as defined in Section 4.6 of GUIDE-

REQS-0015 – Program Digital Engineering Requirements 23 of 75

0007. Location may be designated using multiple referencing methods, such as GIS (Geographical Information System) coordinates, longitude/latitude, address, and milepost/offset. However, the different referencing methods must yield to the same physical location.

5.2.5 The Contractor shall follow asset and location naming conventions outlined in Section 4 of GUIDE-0007.

5.2.6 The Contractor shall follow the file numbering and naming conventions outlined in

GNRL-PWD-DC-MAN-00001-R1-ACHSR.

5.2.7 The Contractor shall develop and maintain the following asset attribute data for each asset:

• Asset status: shall designate the current service status of the asset. Status shall be one of the values defined in Table 1 Asset Status Values of GUIDE-0007.

• Asset value: shall equal the actual purchase or construction price of the asset to the Authority or its contractors. If the acquisition cost is not available, the Contractor may estimate the current value or the replacement cost of the asset based on industry accepted practices for the asset class.

• Manufacture/construction date: shall be the appropriate date used to determine the age of the asset (such as purchase date, construction date, acceptance date, etc.).

• Asset in-service date: shall be the initial date given that the asset is placed in service by the Authority.

• Multiple dates shall be retained as appropriate to track different acquisition events for the asset. There shall be a clear indication of the date which is designated as the beginning of the asset’s life.

• Expected life (measured in years) shall be the anticipated duration in which the assets will be available for service to the Authority.

o UNDER EXPECTED LIFE!!! Expected life shall be stated in time intervals, usage (such as number of cycles/transactions/miles), or other unit of measure.

o Expected life shall include planned major work to the asset over the asset’s life.

For example, the expected life of a train should include a mid-life overhaul.

o If expected life is modified based on actual experience or major unscheduled events (such as accidents, technology improvements, etc.), then expected life shall be updated to the new expected life. Contractors should retain the original expected life for reference.

o Manufacturer/vendor designated identification: shall be the identification designated by the manufacturer or vendor to specify the assets, for example

REQS-0015 – Program Digital Engineering Requirements 24 of 75 make, model, series, release or version. Manufacturer identification should be based on type of asset.

o Asset specific characteristics (and corresponding unit of measure): shall be defined based on the type of asset and shall consist of the relevant measures required to support asset management activities. Size may be expressed as a combination of multiple measures (for example height, width, length) or a single measure (gallon capacity) as appropriate for the asset class and type.

o Asset Condition rating: shall be assigned based on a normalized condition rating reference that is consistent across asset classes and across Contractors (see Section 5 of GUIDE-0007).

o Asset operations responsibility: shall be the entity responsible for the operations of the asset.

o Asset maintenance responsibility: shall be the entity responsible for the asset maintenance.

o Asset ownership: shall be the entity designated as the asset’s owner. This designation may also refer to an external entity if the asset is not owned by the Authority (i.e. PG&E).

o The Contractor shall develop and store other standard condition rating values and definitions within specific asset classes and types for their internal asset management purposes.

o If these ratings are reported to the Authority the Contractor shall translate or map data to the Authority’s rating scale.

5.2.8 The Contractor shall use the Authority’s Asset Management Section (AMS) definitions for the attributes that represent the primary specifications for the asset and are standardized within the asset’s class and type.

5.2.9 The Contractor shall capture the primary specifications attributes within the AD4.

5.2.10 The Contractor shall develop and maintain the primary specifications for each asset.

5.3 Asset Life-Cycle Information Requirements

5.3.1 Asset Handover Information Requirements

• The Contractor shall deliver asset data at handover to the Authority.

• The Contractor shall capture a complete inventory of all assets being constructed (including child assets, components, etc.) with the primary descriptive information and attributes required to add the assets to the Contractor’s Asset Registry.

• The Contractor shall ensure that the level of detail for child assets and components is consistent with the Authority’s established hierarchy for the asset class.

REQS-0015 – Program Digital Engineering Requirements 25 of 75

• The Contractor shall maintain and update the following asset information upon receival of an asset.

• The Contractor shall obtain this information for existing assets if it is missing:

• Design documentation and asset specifications, including drawings and graphical data.

• Asset design life/life expectancy: the service life of the asset based on the design.

• Acquisition cost: the total cost to the Authority to acquire the asset, including design, construction or project costs, purchase price, etc.

• Acquisition date: the date the Authority formally took ownership of the asset. For example, depending on the situation, this could be purchase date, received date, or acceptance date.

• Manufacturer/vendor/contractor that provided or constructed the asset. This information should relate to the entity on the procurement or contract document for the asset and the associated vendor file in procurement and/or project management systems (e.g., vendor ID, vendor name).

• Qualified Manufacturer list for any replaceable components. Qualified vendor list for replaceable components.

• Method of acquisition (purchase, construction, donated, etc.) and the source of the acquisition such as purchase order number, contract number, or project number.

• The Contractor shall also capture and maintain the following upon receiving an asset:

• Asset warranty information: warranty contracts and terms, warranty dates, warranty claims, and warranty recovery.

• Asset planned maintenance and servicing requirements: preventive maintenance and inspection jobs and frequencies.

• Asset configuration structure with acceptable parts identified (i.e. Bill of Materials).

• Parent-Child Relationship, including the asset ID of current child assets installed on the asset and the asset’s parent ID.

• The Contractor shall capture the following information upon commissioning the asset for service:

• Service location.

• Service function/assignment: the function of the asset when placed into service.

• Installation date.

• In-Service date.

• The Contractor shall be responsible for developing and submitting a Maintenance Digital plan covering the Maintenance phase.

REQS-0015 – Program Digital Engineering Requirements 26 of 75

• The Contractor’s Maintenance Digital plan shall describe each application, functional, technical and a general overview, architecture view and integration view of the suite of systems envisioned for the Maintenance activity, with the minimal functional scope:

• Asset Maintenance

• Planning & Scheduling

• Field Execution

• People Management

• Inventory Parts

• Safety & Quality Hazard Reporter,

• Analytics & Dashboard,

• Documentation & Training

• Integration & Support

5.3.2 Asset Operations and Maintenance Information Requirements

• The Contractor shall develop, maintain, and submit records of all planned and actual maintenance, inspection, and service activity for all assets.

• The Contractor’s records shall cover all work performed.

• The Contractor’s records data shall include the following information on all performed activities:

The asset on which the work is performed.

The date, time (from-to), and location of the work.

The total estimated level of effort and cost for the work.

The type of work based on Authority-wide references for work type (i.e. inspection, preventive maintenance, predictive maintenance, corrective maintenance, trouble ticket/ incident, major overhaul/renewal/refurbish, campaign, modification).

Maintenance work steps/tasks.

Work resources (labor, materials, and special equipment) required and consumed.

Work cost for labor, material, special equipment, and other charges.

Failure category for corrective work based on standard failure modes for the asset class and type.

Funding category for the work (capital or operating).

Whether the work is covered under warranty.

Problem/cause/remedy for corrective work and root cause analysis, if performed.

Asset system/subsystem/component upon which work is performed.

Position of the component work was performed.

Personnel performing and approving the work (for those assets where the information is mandatory).

REQS-0015 – Program Digital Engineering Requirements 27 of 75

Meter readings and measurements associated with the work.

Links to the work records of any follow-up work.

Link to performance issue or condition corrected.

• The Contractor shall link the record of all defects, issues, and problems for an asset to related work, including the following:

Date reported.

Asset ID.

Defect/problem code based on defined codes by asset class/type.

Person reporting (employee ID, customer name, etc.).

Text description of defect/issue.

Status of defect (open, work-in-process, closed).

• The Contractor shall develop asset configuration models to validate that child assets are installed on the correct parent asset type.

• The Contractor shall update and maintain the asset’s status regarding its availability for service based on standard categories that identify the reason for unserviceable assets (i.e. waiting for parts).

• The Contractor shall develop asset performance and reliability measures consistent with Schedule 1.

• The Contractor shall capture and monitor performance and reliability data to assess the effectiveness of maintenance activity and to inform the use and assignment of assets for service annually or as directed by the Authority.

• The Contractor shall develop standard criteria consistent with Schedule 1 to determine asset criticality and risk.

• The Contractor shall monitor the criticality and risk criteria to inform maintenance priorities and safety/security decisions annually or as directed by the Authority.

5.3.3 Asset Disposal Requirements

• The Contractor shall comply with information requirements identified in the Authority’s process for decommissioning and disposal of an asset.

• The Contractor shall record the following minimum information on disposed assets:

Disposal date.

Disposal method (from a standardized reference list).

Disposal cost.

Actual salvage value.

• If an asset is sold, the Contractor shall record buyer information and record revenue from the sale.

REQS-0015 – Program Digital Engineering Requirements 28 of 75

5.4 Regulatory Reporting Requirements

5.4.1 The Contractor shall ensure asset information meets all requirements set forth by regulatory authorities.

• The Contractor shall perform appropriate maintenance of Authority assets in compliance with the condition assessment requirements set by the California State Administrative Manual (see Section 5 of GUIDE-0007.)

• The Contractor shall submit asset information to the Authority to satisfy the Federal Railroad Administration’s safety requirements.

• The Contractor shall submit asset information to the Authority to satisfy the Federal Highway Administration’s NBIS requirements. (assets information must satisfy)

• The Contractor shall perform appropriate maintenance of Authority assets in compliance with the condition assessment requirements set by the Governmental Accounting Standards Board Statement No.