homepage | transport for nsw · web viewthis document is one set of standards developed solely and...

Digital Engineering Execution Plan (DEXP) TemplateDMS-FT-532/3.0Digital Engineering Template – Applicable to Infrastructure and Place

Divisional Management SystemStatus: Final

Version: 3.0

Branch: Program Management Office

Section: Digital Engineering

Business unit: Digital Engineering

Date of issue: September 2018

Review due date: October 2019

Audience: Division wide

Asset classes: Heavy Rail; Light Rail; Multi Sites;

Systems; Fleets

Project delivery model: Not applicable

Project type: For all project types

Project lifecycle: Feasibility; Scoping; Definition;

Construction readiness; Implementation; Finalisation; Not applicable

Process owner: Director Digital Engineering

Digital Engineering Execution Plan (DEXP) TemplateProgram Management Office : Digital Engineering : Digital Engineering


Important message

This document is one set of standards developed solely and specifically for use on Transport Assets (as defined in the Asset Standards Authority Charter). It is not suitable for any other purpose.

The copyright and any other intellectual property in this document will at all times remain the property of the State of New South Wales (Transport for NSW).

You may not use or adapt this document or rely upon it in any way unless you are providing products or services to a NSW Government agency and that agency has expressly authorised you in writing to do so. If this document forms part of a contract with, or is a condition of approval by a NSW Government agency, use of the document is subject to the terms of the contract or approval. To be clear, the content of this document is not licensed under any Creative Commons Licence.

This document may contain third party material. The inclusion of third party material is for illustrative purposes only and does not represent an endorsement by NSW Government of any third party product or service.

If you use this document or rely upon it without authorisation under these terms, the State of New South Wales (including Transport for NSW) and its personnel does not accept any liability to you or any other person for any loss, damage, costs and expenses that you or anyone else may suffer or incur from your use and reliance on the content contained in this document. Users should exercise their own skill and care in the use of the document.

This document may not be current and is uncontrolled when printed or downloaded. DE Framework Standards, guidelines and tools may be accessed from the Digital Engineering website at:

www.transport.nsw.gov.au /digitalengineering

document.docx DIVISIONAL MANAGEMENT SYSTEM DMS-FT-532/3.0

© TfNSW 2019 UNCONTROLLED WHEN PRINTED Page ii of xliv

http://www.transport.nsw.gov.au/



Standard Governance

Submitter: Digital Engineering Workstream Specialists

Endorser: Program Manager Digital Engineering

Approver: Director Digital Engineering

Document history

Version Summary of Changes1.0 Interim Approach Issue

2.0 Updated to incorporate developments for Release 2 of the DE FrameworkDocument number updated to reflect DMS requirements

3.0 Updated to incorporate developments for Release 3 of the DE Framework

WARNING: This template contains guidance as hidden text. Before proceeding please ensure hidden text is visible by selecting the tick box at:

File > Options > Display > Hidden Text

To include guidance text when printing, turn on ‘Print hidden text’ in the same window.

For information regarding this document, please email the Digital Engineering Team at [email protected]

or visithttps://www.transport.nsw.gov.au/digitalengineering


© TfNSW 2019 UNCONTROLLED WHEN PRINTED Page iii of xliv

https://www.transport.nsw.gov.au/digitalengineering

http://mailto:/



Instructions for use

a. DEXP context

This Digital Engineering Execution Plan (DEXP) Template sets out the standard minimum requirements for the contents of a DEXP, and provides a standard format. The TfNSW project team is expected to make modifications to this template before it is provided to contractors as a Project DEXP Template.

The elements to be included in each Project DEXP Template are dependent on:

The project’s contract, including deed, requirements and works/services brief;

The ways of working to be adopted by the project team, appropriate to the required deliverables, project structure, available resources and tools;

Appropriate industry best practices.

The DEXP is to be influenced by and compatible with the documents shown in Figure 1 (or equivalent project contract documents).

Figure 1: Documents influencing the DEXP


© TfNSW 2019 UNCONTROLLED WHEN PRINTED Page iv of xliv



b. Using the template

Text highlighted blue is guidance text for the TfNSW project team. The TfNSW project team should remove, replace or confirm blue guidance text prior to issuing to the contractor as a Project DEXP Template. In certain instances it may be appropriate to convert blue highlights to yellow.

Text highlighted yellow is guidance text for the contractor. The contractor must remove guidance text and any place-markers designated ‘XXXX’ prior to formal issue on a project.

The structure of the template does not need to be interpreted as a rigid requirement unless the TfNSW project team specifically requests that all contractor DEXPs must align.

Figure 2 illustrates the process of the TfNSW project team preparing the Project DEXP Template to suit the project needs, and the contractor taking action to create an active Project DEXP along with other related deliverables. Each component of Figure 2 is discussed within the DEXP.

The structure of the deliverables and work packages may necessitate that a Project DEXP is supported by sub-plans, which may include specialist execution or implementation sub-plans. All supporting sub-plans must align with and enable the delivery of the governing DEXP. Where content is covered by a separate management plan it need not be repeated in the DEXP, but a cross-reference must be made.

Remove this section (up to the cover page) before submitting the DEXP.


© TfNSW 2019 UNCONTROLLED WHEN PRINTED Page v of xliv



Figure 2: Assembling the DEXP and its components


© TfNSW 2019 UNCONTROLLED WHEN PRINTED Page vi of xliv

[Doc ref/number]

Digital Engineering Execution Plan

[Project Name]

[Contract Name]Project ref: [insert project name]

Document owner: [insert owner’s name]

Authoring Company: [insert company name]

Date of issue: [insert date]

Document Control:Revision Date Description (Including Status)

XX XX-XX-XXXX XXXXXXXXXX



Preface

Transport for New South Wales (TfNSW) is developing the Digital Engineering (DE) Framework to facilitate time, cost and quality improvements to the way that projects are planned, designed, constructed, operated and maintained throughout their lifecycle. The current release of the DE Framework provides an Interim Approach, with continuous improvement towards best practice and a Transport cluster-wide fully implemented DE Framework.

DE processes included in the DE Framework provide TfNSW with an approach that creates digital information in an accessible format that will support and enhance stakeholder engagement, decision making, asset management, capability and capacity planning.

Implementing and adhering to this vision will enable individuals, who are responsible for the delivery and management of TfNSW’s assets, to make more informed decisions.

This document should be read in conjunction with all related DE Framework Interim Approach documentation. Any application of the DE Framework Interim Approach or any of its parts must be considered in a project-specific context. Adoption of the DE Framework should be undertaken in consultation with the DE Team ([email protected]) to ensure best appropriate practice.


© TfNSW 2019 UNCONTROLLED WHEN PRINTED of 44



Table of ContentsDigital Engineering Execution Plan (DEXP) Template.........................................................i1 Introduction.............................................................................................................15

1.1 Purpose of this DEXP.............................................................................................151.2 Statement of intent to comply.................................................................................151.3 Updating and developing this DEXP.......................................................................151.4 Terms and definitions.............................................................................................15

2 Project details..........................................................................................................162.1 Project scope..........................................................................................................16

2.1.1 General scope.............................................................................................162.1.2 Digital Engineering scope...........................................................................16

2.2 Scope exclusions....................................................................................................162.3 Project DE objectives and uses..............................................................................162.4 Roles and responsibilities.......................................................................................16

2.4.1 Contact details............................................................................................202.5 Project schedule.....................................................................................................202.6 Project standards....................................................................................................21

3 Project data building blocks..................................................................................223.1 Location classification and referencing...................................................................223.2 Asset classification and referencing.......................................................................223.3 Discipline classification...........................................................................................22

3.3.1 Technical discipline classification................................................................233.3.2 Business discipline classification................................................................23

3.4 Work Packages.......................................................................................................233.5 Project data schemas (PDS)..................................................................................233.6 Contractor requests for codes or schemas.............................................................23

4 Collaboration...........................................................................................................254.1 Contractor’s internal collaboration environment.....................................................25

4.1.1 Hardware / technology infrastructure requirements....................................254.1.2 Software platforms and versions.................................................................254.1.3 Common data environment configuration...................................................254.1.4 Metadata requirements...............................................................................254.1.5 Email requirements.....................................................................................264.1.6 Data security...............................................................................................264.1.7 Information management governance........................................................27

4.2 Contractor internal collaborative activities..............................................................284.2.1 Information exchange between contractor teams.......................................284.2.2 Design coordination processes...................................................................284.2.3 Internal meetings.........................................................................................284.2.4 Managing internal comments......................................................................284.2.5 Contractor validation of deliverables...........................................................284.2.6 Existing data review....................................................................................28





4.3 Contractor collaboration with TfNSW......................................................................284.3.1 Meetings with TfNSW..................................................................................284.3.2 Exchanging information with TfNSW...........................................................284.3.3 TfNSW comments and contractor responses.............................................284.3.4 Requests for information (RFI)....................................................................28

4.4 Contractor collaboration with external parties.........................................................285 DE deliverables.......................................................................................................29

5.1 Delivery strategy.....................................................................................................295.1.1 Delivering contract scope............................................................................295.1.2 Innovation and value adding opportunities..................................................29

5.2 Units of measurement.............................................................................................295.3 Project coordinates.................................................................................................29

5.3.1 Geodetic datum...........................................................................................295.3.2 Map projection.............................................................................................295.3.3 Height Datum..............................................................................................295.3.4 Assurance of project coordinates................................................................29

5.4 Systems engineering deliverables..........................................................................305.5 Digital survey deliverables including as-built information.......................................30

5.5.1 Survey strategy...........................................................................................305.5.2 Existing site and legacy data integration.....................................................305.5.3 As-built survey strategy...............................................................................30

5.6 CAD deliverables....................................................................................................305.6.1 Existing CAD review....................................................................................305.6.2 ASA submission requirements....................................................................305.6.3 Smart tags and metadata spreadsheet.......................................................305.6.4 Drawing title block.......................................................................................305.6.5 CAD layer naming.......................................................................................305.6.6 Connecting models and drawings...............................................................30

5.7 BIM deliverables.....................................................................................................305.7.1 Modelling requirements...............................................................................315.7.2 Model production and delivery table (MPDT)..............................................315.7.3 Level of definition........................................................................................315.7.4 Model property requirements......................................................................315.7.5 Review of existing models...........................................................................315.7.6 File format requirements.............................................................................315.7.7 Model coordination procedures...................................................................31

5.8 Visualisation............................................................................................................315.9 GIS Deliverables.....................................................................................................325.10 Scheduling deliverables..........................................................................................325.11 Cost deliverables....................................................................................................325.12 Asset data deliverables...........................................................................................32

5.12.1 Asset Register.............................................................................................325.12.2 Asset handover strategy.............................................................................32





6 Quality and assurance management.....................................................................326.1 Quality control strategy...........................................................................................326.2 Quality control checks and processes....................................................................326.3 Model checking guidance.......................................................................................346.4 Performance indicators...........................................................................................34

FiguresFigure 1: Documents influencing the DEXP.............................................................................iv

Figure 2: Assembling the DEXP and its components..............................................................vi

Figure 3: DE Reporting Structure...........................................................................................18

TablesTable 1: Project summary.......................................................................................................16

Table 2: Project objectives and uses of DE............................................................................16

Table 3: Project team behaviours...........................................................................................17

Table 4: DE responsibilities and authorities............................................................................18

Table 5: Project stakeholders contact details.........................................................................20

Table 6: Project schedule and milestones..............................................................................20

Table 7: DE project data schemas..........................................................................................23

Table 8: Agreed software versions and information exchange...............................................25

Table 9: Access to project information by staff and sub-contractors......................................26

Table 10: Protection of project information.............................................................................27

Table 11: Governance of information management processes..............................................27

Table 12: Meetings with TfNSW.............................................................................................28

Table 13: Units of measurement.............................................................................................29

Table 14: Record of information for model positioning and orientation..................................29

Table 15: Survey strategy.......................................................................................................30

Table 16: General quality control checks................................................................................33

Table 17: Model checking guidance.......................................................................................34

Table 18: Performance indicators...........................................................................................34

Table 19: DEXP terms and definitions....................................................................................35

Table 20: Applicable standards and guides............................................................................37





AppendicesAppendix A Terms and definitions

Appendix B Applicable standards and guides

Appendix C Master Information Delivery Plan (MIDP) [template]

Appendix D Model Production and Delivery Table (MPDT) [template]

Appendix E Enterprise Content Management (ECM) Schema and Specification

Appendix F Requirements Schema and Specification

Appendix G CAD Schema and Specification

Appendix H BIM Schema and Specification

Appendix I Scheduling Schema and Specification

Appendix J Cost Breakdown Structure (CBS)

Appendix K Asset register [template]





1. Introduction1.1. Purpose of this DEXPDMS-ST-207 Digital Engineering Standard, Part 2 - Requirements

The purpose of this Digital Engineering Execution Plan (DEXP) is as follows:1. To demonstrate to TfNSW the contractor’s interpretation of the Digital Engineering

(DE) requirements;2. To provide assurance to TfNSW that the DE requirements will be met, by setting

out how DE will be executed;3. To form a basis of agreement between TfNSW and the contractor on how to

proceed;4. To define for the contractor’s team how project information will be produced,

coordinated and delivered.

1.2. Statement of intent to complyDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 4

As required by the Digital Engineering Standard (DMS-ST-202), the contractor will adopt the following principles to support TfNSW’s commitment to implementing best practice data and information management enabled in a digital environment:

Single Source – Ensuring service and asset data is accurate, current, reliable and not duplicated

Collaboration – Increasing access and sharing, reducing latency for improved decision making

Automation – Reducing or eliminating manual work associated with creating or sharing data

Interoperability – Reducing or eliminating double handling of data between systems

Mobility – Enabling access to and input of data from multiple locations including the field

Visualisation – Incorporating methods to develop, coordinate and check service and asset data spatially

Data Governance – Comply with information management policies, including open data, data information custodianship and information security

1.3. Updating and developing this DEXPDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 5.2.

The DEXP is a live document, and will be maintained by the contractor throughout the course of the project. An updated version will be submitted for TfNSW review at each major project milestone, and at appropriate intermediate instances as changes occur. The current project phase and scope, project team structure and capabilities will be kept appropriately up to date.

1.4. Terms and definitionsDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Appendix B Terms and Definitions

Terms and definitions are given in Error: Reference source not found, and align with terms used in DMS-ST-202 Digital Engineering Standard.





2. Project detailsA summary of key project information is provided in Table 1.

Table 1: Project summary

Project Details

Project Name [insert project name]

Project Address/Location [insert project name]

TfNSW Project Number [insert project number]

Contractor Project Number [insert project number]

Design Start Date [insert date]

Construction Start Date [insert date]

Completion / Handover Date [insert date]

Procurement Method [Design Services or D & C or other]

Project Description [insert here project description]

2.1. Project scope2.1.1. General scope

2.1.2. Digital Engineering scope

2.2. Scope exclusions

2.3. Project DE objectives and usesDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 3

This section outlines the DE objectives for the Project, and the intended DE uses in achieving those objectives.

Table 2: Project objectives and uses of DE

Project Objective DE Use Benefits

XXXXX XXXXX XXXXXXXXXX XXXXX XXXXXXXXXX XXXXX XXXXXXXXXX XXXXX XXXXXXXXXX XXXXX XXXXXXXXXX XXXXX XXXXXXXXXX XXXXX XXXXX

2.4. Roles and responsibilitiesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 7

All personnel delivering and managing assets for the project play an important role in the production of reliable, consistent information. All project personnel will adopt the behaviours listed below in Table 3 to help build an appropriate working culture to facilitate successful DE.





Table 3: Project team behaviours

Ref Activities Description

1 Share, collaborate, deliver

All personnel have a responsibility to share information, and where required, coordinate and collaborate to deliver TfNSW’s required Digital Engineering outcomes.

2 Use common language Use a common language so people can effectively exchange information.

3 Demonstrate an auditable assurance pathway

Resolve issues collaboratively, manage risks and track decisions to provide a traceable and auditable pathway through design development up until asset disposal.

4 Provide and use digital tools to support decision making

Implement effective tools and provide training so personnel are empowered to make decisions using the best available information.

5 Support and strive to adopt best practice

Use Digital Engineering tools and processes to drive innovation in the way projects are delivered.

This section provides details of the resources within the Project Team with specific DE responsibilities and authority.

The contractor DE team structure is shown in Figure 3, including relevant interfaces with TfNSW roles.

Figure 3: DE Reporting Structure

The DE responsibilities and authorities of the roles in Figure 3 are provided in Table 4. All nominated roles will have completed the appropriate and relevant training prior to project commencement.





Table 4: DE responsibilities and authorities

Project Role Core DE Responsibilities DE Authority

TfNSW Project Manager

Manages and coordinates project execution and DE to meet procurement strategy and cost containment.

Adoption of DE Behaviours

Approval of DEXP in consultation with the TfNSW DE Manager

TfNSW acceptance/ approval of project deliverables

TfNSW DE Manager

Champion the adoption of and actively demonstrate the DE Behaviours within the project team.

Provide support to the TfNSW Project Manager and contract team in the delivery of DE in accordance with the TfNSW DE Standard (DMS-ST-202).

Responsible for overall project DE strategy, procurement and implementation.

Support TfNSW personnel’s review of project DE deliverables.

Review compliance with DEXP and project contract to ensure work processes and deliverables are completed as required.

Approval of DEXP in consultation with the TfNSW Project Manager

Contractor Project Manager

Manages and coordinates project execution and DE to meet procurement strategy and cost containment.


Approval of project deliverables, reports and submission packages for upload to TfNSW CDE.

Contractor DE Manager

Champion the adoption of and actively demonstrate the DE Behaviours within the project team.

Responsible for the setup and delivery of the project from a DE perspective. This includes setup and management of the Project Data Schemas and CDE tools.

Responsible for the data validation and review of DE submissions prior to upload to the TfNSW-CDE.

Monitor and review compliance with this DEXP to ensure work processes and deliverables are completed as required.

Works in conjunction with the TfNSW DE Manager.

Approval and data validation of DE project deliverables, reports and submission packages, as designated by the Project Manager, for upload to the TfNSW CDE.

Contractor Information Manager

Responsible for initiation, agreement, implementation and change control of the ECM tool.

Ensures compliance for information management in accordance with the Contract, legislation and relevant ASA and Industry Standards


Approval of project deliverables, reports and submission packages





Project Role Core DE Responsibilities DE Authority

Contractor Document Controller

Responsible for the day-to-day implementation of document control processes and system support. Also responsible for validating ECM Metadata.


Upload of approved datasets/ deliverables to the TfNSW CDE.

Contractor Systems Assurance Manager

Responsible for developing system requirements in the format specified by the DE Standard

Responsible for demonstrating satisfaction of the requirements utilising best appropriate digital engineering practices.

Review/approval of systems engineering deliverables, reports and submission packages.

Contractor Design Manager

Responsible for management of project design deliverables


Review/approval of project deliverables, reports and submission packages

Contractor CAD Manager

Management CAD implementation and usage on the project

Review/approval of CAD deliverables, reports and submission packages

Contractor BIM Manager

Management of model creation and information exchanges with collaborating parties

Review/approval of BIM deliverables, reports and submission packages

Contractor GIS Manager

Manage GIS implementation and usage on the project

Review/approval of GIS in accordance with Project Requirements

Contractor Scheduler

Manage Scheduling implementation and usage on the project

Review/approval of time deliverables in accordance with Project Requirements

Contractor Cost Estimator

Manage costing implementation and usage on the project


Review/approval of cost deliverables in accordance with Project Requirements

Contractor Project Team Member

Adoption of DE Behaviours Creation of documentation in accordance with DE requirements.

Review/approval of technical deliverables as appropriate.

2.4.1. Contact details

Table 5: Project stakeholders contact details

DE Role Contact Name Company Contact DetailsTfNSW Project Manager XXXX TfNSW XXXX

TfNSW DE Manager XXXX TfNSW XXXX

Project Manager XXXX XXXX XXXX

Engineering Manager XXXX XXXX XXXX

DE Lead XXXX XXXX XXXX

Document Controller XXXX XXXX XXXX





DE Role Contact Name Company Contact DetailsInsert additional DE roles if applicable XXXX XXXX XXXX

2.5. Project scheduleDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 5.1

Table 6 provides a high level summary of major milestones only. Refer to the project schedule for the latest information and full detail.

Table 6: Project schedule and milestones

Project Phase Main Project Milestone Approximate Start Date

Approximate Submission Date

Options Design XX/XX/XXXX XX/XX/XXXX

Feasibility CM Gate 1 XX/XX/XXXX XX/XX/XXXX

Preliminary Design System Concept Review XX/XX/XXXX XX/XX/XXXX

CM Gate 2 XX/XX/XXXX XX/XX/XXXX

Detail Design / Approved for Construction

System Definition Review XX/XX/XXXX XX/XX/XXXX

Preliminary Design Review XX/XX/XXXX XX/XX/XXXX

Critical/(Detail) Design Review XX/XX/XXXX XX/XX/XXXX

System Verification Review XX/XX/XXXX XX/XX/XXXX


Ready for Testing Physical Configuration Audit XX/XX/XXXX XX/XX/XXXX


Handover Finalisation XX/XX/XXXX XX/XX/XXXX


2.6. Project standardsDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 2.5 and Part 2 – Requirements, Appendix A

Appendix B lists the applicable Digital Engineering standards and guides for this contract.

3. Project data building blocksDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Sections 6 and 7 and Part 2 – Requirements, Sections 4 and 5.3

This section defines how the TfNSW project classification systems and data schemas are applied. The consistent application of structured data results in a more coherent digital twin, enabling efficient computational management of project information and, ultimately, the physical assets. All project participants work to the same Project Data Schemas (PDS), which are generated from a set of Project Data Building Blocks (PDBB) owned by the TfNSW project team. Governed datasets include:

Design and work packages,





Technical and business disciplines, Locations (classification and reference), Assets (classification and reference), Other document metadata, Other model object properties, Other CAD layer naming metadata.

3.1. Location classification and referencingDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 7.2 and Part 2 – Requirements, Section 4.1

ClassificationUniclass 2015 will be adopted for the classification of all project locations, utilising Complexes (Co), Entities (En) and Spaces (SL) tables. ReferenceIndividual instances of each location classification (type) also require a specific location reference (instance) code. Location reference codes are to be coordinated across the project.

3.2. Asset classification and referencingDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 7.3 and Part 2 – Requirements, Section 4.2

ClassificationUniclass 2015 will be adopted for the classification of all assets, utilising the Elements/Functions (EF), Systems (Ss) and Products (Pr) tables as specified by the Digital Engineering Standard DMS-ST-202/DMS-ST-207. Reference

3.3. Discipline classificationDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 7.4 and Part 2 – Requirements, Section 4.3

3.3.1. Technical discipline classification

3.3.2. Business discipline classification

3.4. Work PackagesDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 7.4.3

3.5. Project data schemas (PDS)DMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 6

Project Data Schemas (PDS) for specific applications are shown in Table 7.





Table 7: DE project data schemas

DE Deliverable PDS Title TfNSW Template

Project Reference

Key Project Data Building Blocks

Documents and Correspondence

ECM Schema and Specification

DMS-FT-533

Program, Project, Contract, Project Milestone, Discipline, Location

Systems Engineering

Requirements Schema and Specification

DMS-FT-563

Project, Contract, Project Milestone, Work Package, Discipline, Location, Asset Classification

Surveys Use BIM PDS where appropriate NA NA

Discipline, Location, Asset and Location Classification

CAD CAD Schema and Specification

DMS-FT-562

Discipline and Asset Classification

BIM BIM Schema and Specification

DMS-FT-516


Visualisation Use BIM PDS where appropriate NA NA


GIS Use BIM PDS where appropriate NA NA


Scheduling Scheduling Schema and Specification

DMS-FT-520

Discipline, Location, Asset Classification

Cost Estimating Use Scheduling PDS where appropriate NA NA Discipline, Location,

Asset Classification

Asset Data Asset Register Template

DMS-FT-537


3.6. Contractor requests for codes or schemasIf an appropriate classification or reference code or schema cannot be determined, the contractor will request a new code from TfNSW via the DE Code Request Form (DMS-FT-374), submitted by your TfNSW DE Manager to the TfNSW DE Team at [email protected].

4. Collaboration4.1. Contractor’s internal collaboration environmentDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 9 and Part 2 – Requirements, Section 3

4.1.1. Hardware / technology infrastructure requirements





4.1.2. Software platforms and versions

Table 8lists the key software applications used for producing and managing DE deliverables, and the exchange formats to be used including formats required by TfNSW for delivery.

Table 8: Agreed software versions and information exchange

Party Purpose Software Version Native Format

Exchange Formats

Comments

TfNSW Document Management

XXX XXX N/A XXX XXX

TfNSW Model Review XXX XXX XXX XXX XXX

TfNSW Geospatial Information System

XXX XXX XXX XXX XXX

XXX Documents XXX XXX XXX PDF XXX

XXX Drawings XXX XXX XXX PDF, DWG

XXX

XXX Models XXX XXX XXX IFC, NWC, NWD

XXX

XXX Point clouds XXX XXX XXX XXX XXX

XXX GIS data XXX XXX XXX XXX XXX

XXX XXX XXX XXX XXX XXX XXX

4.1.3. Common data environment configurationDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.1 and 3.2

4.1.4. Metadata requirementsDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.3

4.1.4.1. Deliverables metadata

All artefacts submitted to TfNSW must align with the Enterprise Content Management (ECM) metadata schema, which governs document numbering, revision and version control, state and suitability codes. Metadata fields and values are defined in and summarised below.

4.1.4.2. Document numbering and naming

Consistent document numbering and naming conventions must be applied to all artefacts submitted to TfNSW, including drawings, reports, specifications, models, visualisations and any other deliverables.The document number printed on each document or drawing shall correspond with the document number assigned in the TfNSW-CDE upon submission.





4.1.4.3. State, suitability and review status

TfNSW uses state, suitability and review status to describe the level of approval and limits of appropriate use for all project files. Work In Progress, Shared, Client Shared, Published and other terms provided in are considered defined terms for the project, according to the Digital Engineering Standard (DMS-ST-202/DMS-ST-207).

4.1.4.4. Revisions and versions

The revision and version numbering of artefacts uploaded to the TfNSW-CDE is to be in accordance with the Digital Engineering Standard (DMS-ST-202/DMS-ST-207) and as per the ECM schema included in .The revision number printed on each document or drawing shall correspond with the revision number assigned in the TfNSW-CDE upon submission.

4.1.4.5. Other file metadata

4.1.5. Email requirementsDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.6

4.1.6. Data securityDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.8

Table 9 details how access to project information is managed.

Table 9: Access to project information by staff and sub-contractors

User role or security band

Access to project information

Company member not approved for this project

No access to project information

Standard approved project team member

Password protected access to background information from TfNSW, design information, and incoming documents approved for use.

Document controller Password protected access to all information received by the project apart from executive folders.

Executive access Password protected access to all information received by the project.Authority to commission user profiles for new approved project team members.

System administrator Password protected access to all information received by the project.Authority to create user profiles following approval by the project executive.

Table 10 details the protection measures applied to mitigate the risk of breaches to project data security.

Table 10: Protection of project information

Risk Applied protection measures

Accidental loss

File corruption (malware, viruses)





Risk Applied protection measures

Misuse, negligence

Unauthorized conveyance

Deliberate attack

4.1.7. Information management governanceDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.9

Table 11 demonstrates that information management processes are appropriately governed to protect security of project information.

Table 11: Governance of information management processes

Action Process and governance measures

Granting new team member access to project information

Ensuring access to project information is withdrawn when a team member leaves the project

Exchange of project information between team members

Exchange of project information with sub-contractors

Exchange of project information with TfNSW

Archiving and backing up project information

4.2. Contractor internal collaborative activitiesDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Sections 7 and 8 and Part 2 – Requirements, Section 3

4.2.1. Information exchange between contractor teams

4.2.2. Design coordination processes

4.2.3. Internal meetings

4.2.4. Managing internal comments

4.2.5. Contractor validation of deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.5





A validation process for deliverables shall be implemented to ensure that all information submitted to TfNSW is correct, accurate, complete, coordinated and in line with the project data schemas.

4.2.6. Existing data reviewDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.4

4.3. Contractor collaboration with TfNSWDMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Section 8

4.3.1. Meetings with TfNSW

Table 12: Meetings with TfNSW

Meeting Type Frequency Facilitator Attendees

Client Brief TfNSW Project Manager XXXDE Initiation Meeting TfNSW DE Manager XXXDE Execution Plan Review

TfNSW DE Manager XXX

Client and contractor design working group(s)

XXX XXX XXX

Multiple contractor DE workshops

XXX XXX XXX

Safety in design workshops

XXX XXX XXX

4.3.2. Exchanging information with TfNSW

4.3.3. TfNSW comments and contractor responses

4.3.4. Requests for information (RFI)DMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 3.7

4.4. Contractor collaboration with external partiesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 2

5. DE deliverables5.1. Delivery strategy5.1.1. Delivering contract scope

5.1.2. Innovation and value adding opportunities

5.2. Units of measurementThe units of measurements in Table 13 are to be used on this project.





Table 13: Units of measurement

Dimension Measurement Abbreviation Degree of Accuracy

Length Millimeters (Building specific)Meters(Infrastructure specific)

mmm

0

Area Square meters m² .00Volume Cubic meters m³ .00Angle Degrees Minutes Seconds1 ⁰ ‘ “ .00Weight Kilograms /Tons Kg / T 0Slope Percent % 0

5.3. Project coordinates

5.3.1. Geodetic datum

The geodetic datum shall be GDA____.

5.3.2. Map projection

The map projection shall be _____.

5.3.3. Height Datum

The height datum shall be the Australian Height Datum.

5.3.4. Assurance of project coordinates

Any spatial dataset provided to TfNSW must have an associated Metadata Statement detailing what projection, datum and epoch (where appropriate) has been used. If data has been transformed the Metadata Statement should detail which transformation model has been used (e.g. GDA94 to GDA2020 via 7Parameter; NTv2 CON; or NTv2 CPD). For vertical GNSS data related to the Australian Height Datum the Metadata Statement must also detail the version of AUSGeoid2020 used to derive height information.A GDA2020 logo1 as defined by the ICMS must be used on all drawings that have adopted the GDA2020 datum.

Table 14: Record of information for model positioning and orientation

Point Location Description

Easting (m) Northing (m) Elevation or Site Datum

[Site local benchmark origin]

XXX XXX XXX XXX

[Grid Intersection (A and 1)] XXX XXX XXX XXX

[Project Angle to True North]

XXX XXX XXX XXX

5.4. Systems engineering deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.1

1 https://www.icsm.gov.au/gda2020/using-gda2020-logo





5.5. Digital survey deliverables including as-built informationDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.2

5.5.1. Survey strategy

Table 15: Survey strategy

Survey Method Delivery Format Survey Origin Details/Notes

Feature Survey XXX XXX XXXPoint Cloud XXX XXX XXXLight Detecting and Ranging (LIDAR)

XXX XXX XXX

Global Navigation Satellite Systems (GNSS)

XXX XXX XXX

Utility Mapping XXX XXX XXX

5.5.2. Existing site and legacy data integration

5.5.3. As-built survey strategy

5.6. CAD deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.3

5.6.1. Existing CAD review

5.6.2. ASA submission requirements

5.6.3. Smart tags and metadata spreadsheet

5.6.4. Drawing title block

5.6.5. CAD layer naming

5.6.6. Connecting models and drawings

5.7. BIM deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.4

5.7.1. Modelling requirements

5.7.1.1. Model structuring

5.7.1.2. General principles

5.7.1.3. Design contractor modelling guidelines

5.7.1.4. Construction contractor modelling guidelines

5.7.2. Model production and delivery table (MPDT)

5.7.3. Level of definition





5.7.4. Model property requirements

TfNSW specifies requirements for asset properties in the project’s BIM Schema and Specification, . Some of the required asset properties are written directly to the Asset Register () as attributes in a spreadsheet or database, but some are to be included within the project’s BIM models. Refer to the BIM Schema and Specification () for model property requirements, which vary throughout the lifecycle of the project.

5.7.4.1. General model properties

5.7.4.2. Model object properties

5.7.4.3. Properties in open data format models

5.7.5. Review of existing models

5.7.6. File format requirements

Table 8

5.7.7. Model coordination procedures

5.7.7.1. Model federation and sharing

5.7.7.2. Clash detection and reporting

5.7.7.3. Level of accuracy and construction tolerance

5.7.7.4. Contractor model review workshops

5.7.7.5. Stakeholder model review workshops

5.7.7.6. Validation and verification

Section 6 of this DEXP outlines the contractor’s quality assurance procedures. A template Model Validation Certificate is provided in , for sign-off and submission by the relevant technical lead along with each model at every formal milestone submission. The Model Validation Certificate is the means by which the contractor provides assurance to TfNSW that the model’s coordination, completeness, detail and model properties have been compared against all applicable requirements and found to be satisfactory.

5.8. VisualisationDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.5

Section 6.5 of the Digital Engineering Standard (DMS-ST-207) describes the deliverable requirement for example visualisation types that may be procured for a project. TfNSW requires the contractor to deliver the visualisation output and all the files and content used to develop the final deliverable.

5.9. GIS DeliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.6

5.10. Scheduling deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.7





5.11. Cost deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.8

5.12. Asset data deliverablesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 6.9

5.12.1. Asset Register

The Digital Engineering Standard (DMS-ST-202/DMS-ST-207) describes how TfNSW records asset information for development and use using an Asset Register. At certain milestones, TfNSW requires the contractor to deliver an Asset Register which captures the development of the asset information. The Asset Register must be up to date with the federated model submitted at the same phase. An Asset Register template is provided in .

5.12.2. Asset handover strategy

6. Quality and assurance management6.1. Quality control strategyDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 8.1

6.2. Quality control checks and processesDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 8.1

Table 16: General quality control checks

Checks Definition Responsible Party

Software Programs

Frequency

Technical check Assessment for technical accuracy, correctness, coordination and completeness.

Technical checker XXXX Each share

Visual check Assessment for visual cues, including presentation, references, unintended components, coordination issues, feasibility, safety, level of detail and other factors.

Model Manager for each discipline

XXXX Weekly

Clash detection Detect problems in the model where two components are clashing: including soft and hard clashes.


XXXX Bi-weekly

Model data check

Assessment for model properties against the Information BIM Schema and Specification and any other relevant project requirements.


XXXX Each delivery

Rendition check Assessment of renditions from Person responsible XXXX Each





Checks Definition Responsible Party

Software Programs

Frequency

the native file to ensure they accurately and completely represent the native. For example PDFs generated from Word, or IFCs generated from a modelling tool.

for the deliverable delivery

Model validation Assessment to confirm all relevant checks have been completed correctly, and the model meets all applicable requirements for the phase, including conformity to the Information BIM Schema and Specification and the MPDT. Model Validation Certificate is signed off for submission.

Contractor DE Lead

XXXX Each milestone

TfNSW Audits Check against contract and TfNSW requirements

TfNSW DE Manager and Technical Managers

Each milestone

6.3. Model checking guidanceTable 17 provides guidance for assessments to undertake in different model checking situations.

Table 17: Model checking guidance

Model State Suitability Status Responsible Checkers

Assessments required

Model checking for sharing internally

S1 – For Coordination XXXX XXXX

S2 – For Information XXXX XXXX

S3 – For Review and Comment

XXXX XXXX

Model validation prior to delivery

S1 – For Coordination XXXX XXXX

S2 – For Information XXXX XXXX

S3 – For Review and Comment

XXXX XXXX

S4 – For Stage Approval

XXXX XXXX

6.4. Performance indicatorsDMS-ST-207 Digital Engineering Standard, Part 2 – Requirements, Section 8.2

Table 18 contains the key performance indicators and methods of measuring the success of DE which will be applied on the project, and provided to TfNSW.





Table 18: Performance indicators

Performance Indicator Measurement Success Criteria

XXXX XXXX XXXX

XXXX XXXX XXXX

XXXX XXXX XXXX

XXXX XXXX XXXX

XXXX XXXX XXXX





Appendix A Terms and definitionsRefer to DMS-ST-202 Digital Engineering Standard, Part 1 – Concepts and principles, Appendix B for standard terms and definitions.Table 19 contains terms and definitions specific to this DEXP.

Table 19: DEXP terms and definitions

Terms & Acronyms Definition Reference

ASAAsset Standards Authority is an independent unit within Transport for NSW (TfNSW) and is the network design and standards authority for defined NSW transport assets.

Australian Height Datum (AHD)

A geodetic datum for altitude measurement in Australia.

Building Information Modelling (BIM)

Process of designing and constructing a building or infrastructure asset using object-based 3D modelling. TfNSW

Common Data Environment(CDE)

Single source of information for any given project or asset, used to collect, manage and disseminate all relevant approved project documents for multi-disciplinary teams in a managed process.

PAS 1192-2:2013

Computer Aided Drafting(CAD)

Typically digital 2D or 3D drawings that replicate manual drafting techniques. This often involves using disconnected drawings that are manually drafted using lines, arcs and circles, which are then overlaid and coordinated in two dimensions.

T MU MD 00006 ST

Cost Breakdown Structure(CBS)

A breakdown of project expenditure that provides meaningful groupings of capital (and sometimes operational) expenditure.The CBS is often associated with the lowest level of the WBS.

Digital Engineering (DE)

A collaborative way of working, using digital processes, to enable more productive methods of planning, designing, constructing, operating and maintaining assets.

TfNSW

Digital Engineering Execution Plan (DEXP)

A plan that delivers and explains how the digital information management aspects of the appointment will be carried out by the service provider over the design and construction stages of a project.

TfNSW

Digital Engineering Framework (DE Framework)

Is an integrated management system that comprises of a set of documents including standards, guidelines, templates and training that provide the strategy to support a culture that enables the implementation of Digital Engineering.

TfNSW

Digital Engineering Standard (DES)

The Digital Engineering Standard is the lead document in the DE Framework, providing the minimum requirements for the adoption of Digital Engineering processes.

TfNSW

Geographic Information Systems(GIS)

Systems that manage site cadastral data and associated information.






Level of Definition

The collective term used for and including the 'Level of Detail' (Graphical/Geometrical) and 'Level of Information' (non-graphical/ non-geometrical). This is equivalent to the US BIM Forum (Building SMART US Chapter) Level of Development definition commonly used in Australia.

PAS 1192-2:2013

Level of Detail (LoD) Level of Detail is the amount of geometrical (graphical) information contained in a 3D model.

PS 1192-2:2013

Level of Information (LoI)

Level of Information is the amount of non-geometrical (non-graphical) data embedded within an Information Model.

Location Classification

Location classifications identify and group places and spaces. They are used to indicate where an asset is in relation to other assets and/or where activities take place.

Metadata Information about a document, model, drawing, object, asset, or other thing.

Model Production and Delivery Table (MPDT)

A schedule of elements noted in a spreadsheet format to define the Level of Model Detail (geometrical) and the Level of Model Information (Non- geometrical) per element at any given stage of a project.

PAS 1192-2:2013

Navisworks Cache (NWC)

An Autodesk Navisworks file containing a single model file cached in this format for speed of use by the software. An NWC is created automatically when opening another file format in Navisworks. Cannot be opened in Navisworks Freedom.

Navisworks Document (NWD)

An Autodesk Navisworks file format which consolidates all merged or appended models into a single read-only file, including Navisworks viewpoints, tags and review mark-ups. Can be opened in Navisworks Freedom.

Navisworks File Set (NWF)

An Autodesk Navisworks file format for managing appended references as separate NWC files. Cannot be opened in Navisworks Freedom.

Project Data Schemas (PDS)

The common language and structure for all project data associated with particular activities, for example ECM, CAD, BIM, etc.

Request for Information(RFI)

Formal project specific process, whereby the Contractor may request specific information from TfNSW. The project-specific process should be documented in the DEXP

Transport for New South Wales(TfNSW)

Organisation who lead the development of safe, integrated and efficient transport systems for the people of NSW. TfNSW customers are at the centre of all activities, including transport planning, strategy, policy, procurement and other non-service delivery functions across all modes of transport - roads, rail, ferries, light rail and point to point.

TfNSW

Uniclass 2015 A unified classification system covering all construction sectors and items for the Construction Industry. NBS






Work Breakdown Structure (WBS)

The WBS decomposes or subdivides the scope into more discreet and manageable, deliverable based packages of works. This provides the framework from which the project management and project control systems will be set-up to facilitate the tracking and reporting of the project status and cost (CBS).The primary method used for grouping, sorting and organising project schedules.

DMS-ST-123





Appendix B Applicable standards and guidesTable 20: Applicable standards and guides

M = MandatoryC = Mandatory with concessionsR = Recommended

Standards

Gui

danc

e

Engi

neer

ing/

Des

ign

Info

rmat

ion

Man

agem

ent /

CD

EA

sset

Info

rmat

ion

Cos

ting

Sche

dulin

g

DE Framework

DMS-ST-202

Digital Engineering Standard - Part 1, Concepts & principles

M M M R R

DMS-ST-207

Digital Engineering Standard - Part 2, Requirements

M M M R R

ASA T MU AM 01001 ST Life Cycle Costing R R

T MU AM 01005 ST

Asset Handover Requirements M

T MU AM 01006 ST Asset Reference Codes M

T MU AM 01006 F1

Asset Location Classification Code Form M

T MU AM 01007 TI

Asset Reference Codes Register M

T MU AM 01008 ST

Technical Maintenance Plans and Coding System M

T MU AM 01012 ST

Engineering Document Requirements M

T MU AM 01012 F1

Metadata Spreadsheet for Engineering Documents M

T MU AM 02001 ST

Asset Information and Register Requirements M

T MU AM 02002 TI Asset Classification System M

T MU AM 02004 ST

Management of Asset Information M

T MU AM 04001 PL

TfNSW Configuration Management Plan M

T MU AM 06006 ST

Systems Engineering Standard

M





M = MandatoryC = Mandatory with concessionsR = Recommended

Standards

Gui

danc

e

Engi

neer

ing/

Des

ign

Info

rmat

ion

Man

agem

ent /

CD

EA

sset

Info

rmat

ion

Cos

ting

Sche

dulin

g

T MU AM 06006 GU

Systems Engineering Guideline M

T MU MD 00006 ST

Engineering Drawings and CAD Requirements C

T MU MD 00006 F1

Metadata Spreadsheet for Engineering Drawings C

T MU MD 00006 TI

Technical Information for CAD and Engineering Drawings

C

Industry Uniclass 2015

Universal Classification System for the Construction Industry

M M

Enter Here Enter Here


Project Specific









Appendix C Master Information Delivery Plan (MIDP) [template]





Appendix D Model Production and Delivery Table (MPDT) [template]





Appendix E Enterprise Content Management (ECM) Schema and Specification





Appendix F Requirements Schema and Specification





Appendix G CAD Schema and Specification

CAD layer naming table

Project title block





Appendix H BIM Schema and Specification

BIM Schema and Specification

Model Validation Certificate Template





Appendix I Scheduling Schema and Specification





Appendix J Cost Breakdown Structure (CBS)





Appendix K Asset register [template]

