Operations Concept Definition - · PDF fileST v3.0, 26/10/2017 Operations Concept Definition T MU AM 06008 ST Standard . Version 2.0 . Issued Date: 26 March 2015 . Important Warning

Sup

erse

ded

by T

MU

AM

060

08 S

T v3

.0, 2

6/10

/201

7

Operations Concept Definition

T MU AM 06008 ST

Standard

Version 2.0

Issued Date: 26 March 2015

Important Warning This document is one of a set of standards developed solely and specifically for use on public transport assets which are vested in or owned, managed, controlled, commissioned or funded by the NSW Government, a NSW Government agency or a Transport Agency (as defined in the Asset Standards Authority Charter). It is not suitable for any other purpose. You must not use or adapt it or rely upon it in any way unless you are authorised in writing to do so by a relevant NSW Government agency. 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. This document may not be current. Current standards are available for download from the Asset Standards Authority website at www.asa.transport.nsw.gov.au. © State of NSW through Transport for NSW

T MU AM 06008 ST Operations Concept Definition

Version 2.0 Issued Date: 26 March 2015

Sup

erse

ded

by T

MU

AM

060

08 S

T v3

.0, 2

6/10

/201

7

Standard governance

Owner: Manager Systems Engineering Process, Asset Standards Authority

Authoriser: Principal Manager Network and Asset Strategy

Approver: Director, Asset Standards Authority on behalf of ASA Configuration Control Board

Document history

Version Summary of change

1.0 First issue

2.0 References removed

For queries regarding this document, please email the ASA at [email protected] or visit www.asa.transport.nsw.gov.au

© State of NSW through Transport for NSW

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



Preface The Asset Standards Authority (ASA) is an independent unit within Transport for NSW (TfNSW)

and is the network design and standards authority for defined NSW transport assets.

The ASA is responsible for developing engineering governance frameworks to support industry

delivery in the assurance of design, safety, integrity, construction, and commissioning of

transport assets for the whole asset life cycle. In order to achieve this, the ASA effectively

discharges obligations as the authority for various technical, process, and planning matters

across the asset life cycle.

The ASA collaborates with industry using stakeholder engagement activities to assist in

achieving its mission. These activities help align the ASA to broader government expectations of

making it clearer, simpler, and more attractive to do business within the NSW transport industry,

allowing the supply chain to deliver safe, efficient, and competent transport services.

The ASA develops, maintains, controls, and publishes a suite of standards and other

documentation for transport assets of TfNSW. Further, the ASA ensures that these standards

are performance based to create opportunities for innovation and improve access to a broader

competitive supply chain.

This document specifies the requirements for developing operations concept definitions for

transport projects.

This document is a second issue.

© State of NSW through Transport for NSW Page 3 of 14 S

uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



Foreword This operational concept definition (OCD) standard is placed within the context of systems

engineering as an integrated methodology to support the TfNSW asset management

framework.

This standard forms part of the systems engineering document hierarchy in development by the

ASA. It is the child of T MU AM 06006 ST Systems Engineering Standard.

The following documents were referred to in the development of this standard:

• AS/ISO 15288 System Life cycle Processes

• IEEE Std 1362:1998 IEEE Guide for Information Technology – System Definition –

Concept of Operations (ConOps) Document

• ISO/IEC/IEEE 29148: 2011 Systems and software engineering – Life cycle processes –

Requirements Engineering

• INCOSE Systems Engineering Handbook

• UIP1973-DTP-OMC-0001-A1, Iss1.2 Deep Tube Railway – Generic Operations and

Maintenance Concept – 2020 (London Underground)


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



Table of contents 1. Introduction ............................................................................................................................................ 6

2. Purpose ................................................................................................................................................... 62.1. Scope ..................................................................................................................................................................... 62.2. Application ............................................................................................................................................................. 6

3. Reference documents ........................................................................................................................... 7

4. Terms and definitions ........................................................................................................................... 8

5. Operations concept definition development ...................................................................................... 9

6. Operational performance capability .................................................................................................. 10

7. Operational constraints ...................................................................................................................... 10

8. Operational service levels .................................................................................................................. 11

9. Operational assets and facilities ........................................................................................................ 11

10. Operational process scenarios .......................................................................................................... 12

11. Operational users ................................................................................................................................ 12

12. Operations migration .......................................................................................................................... 13

13. Operational interfaces ......................................................................................................................... 13

14. Operating modes ................................................................................................................................. 14


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



1. Introduction Development of operational concepts, as articulated in an operations concept definition (OCD)

is a key activity to be undertaken in the concept stage of the TfNSW system life cycle.

An OCD is required in order to understand how the new or altered system will be operated, and

therefore how much it will cost to operate over the expected system life time until retirement.

The OCD is a strategic guide and reference for maintaining focus on how the need or demand

will be achieved over the full life cycle, and not just an enabler for the business requirements.

2. Purpose The purpose of this standard is to provide a structured, repeatable approach to developing

OCDs on transport projects ranging from simple to complex new or altered systems.

2.1. Scope This document is a management standard for developing OCDs for TfNSW transport projects.

It defines key requirements for ensuring that all operational aspects of a transport project are

considered and fully defined, prior to the development of a supportable business case.

The scope of this standard is valid for TfNSW public and freight transport systems; initially

heavy rail, with planned future extension to other transport modes.

While this standard describes requirements for defining whole of life operation of new or altered

assets, it does not describe how life cycle costs are derived. For information on how life cycle

costs are derived, refer to T MU AM 01001 ST Life Cycle Costing.

This standard and the OCD in general shall be supported by a maintenance concept definition

(MCD), which addresses topics including maintenance support, spares and product type

approvals.

2.2. Application This standard is to be applied at the following operational levels:

• transport network level, for example all transport modes

• transport mode level, for example rail passenger and freight transport

• transport corridor level, for example North Shore Line, Southern Line

• local sites, for example transport interchanges, stations, yards, depots, control centres and

junctions


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



The initial objective is to develop and apply this standard to rail passenger and freight transport

projects, and then to extend application of this standard to other transport modes. This standard

is structured to ensure that its principles can be applied to other modes.

This standard is intended for application and compliance by entities responsible for planning,

investment and delivery of TfNSW transport systems, including the following entities:

• Transport Services (TSD), TfNSW

• Customer Experience (CED), TfNSW

• Planning and Programs (PPD), TfNSW

• Freight and Regional Development (FRD), TfNSW

• Transport Projects (TPD), TfNSW

• Transport Operators and Maintainers (OpCo)

• contracted AEOs providing support to TfNSW entities in preparing an OCD

This standard shall be applied in the plan (concept and specify) phase of the system life cycle,

prior to finalising the business case and the requesting of funding from NSW Treasury.

The OCD is a predecessor to preparing a business case and associated business requirements

specification (BRS). The OCD is a dynamic document that should be reviewed and if necessary

updated as the need is translated from a concept to a realised system.

The OCD is used to derive the business requirements in the BRS, which is further derived into

solution requirements in the system requirements specification (SRS). The OCD may be used

as the basis for validation throughout the system life cycle and as the point of reference where

conflicts with the BRS and SRS cannot be resolved. Business and system requirements are

defined and addressed in TS 10505 AEO Guide to Requirements Definition and Analysis.

Topics described in this standard are to be tailored and scaled to suit the particular needs of

each transport project. In this context, a 'project' applies to a portfolio, program or project level.

3. Reference documents International standards

AS/ISO 15288 System Life Cycle Processes

IEEE Std 1362: 1998 IEEE Guide for Information Technology – System Definition – Concept of

Operations (ConOps) Document

ISO/IEC/IEEE 29148: 2011 Systems and software engineering – Life cycle processes –

Requirements engineering


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



Transport for NSW standards

T MU AM 01001 ST Life Cycle Costing standard

T MU AM 06006 ST Systems Engineering Standard

TS 10505 AEO Guide to Requirements Definition and Analysis

Other references

INCOSE Systems Engineering Handbook

London Underground, Iss1.2 Deep Tube Railway – Generic Operations and Maintenance

Concept – 2020, UIP1973-DTP-OMC-0001-A1

4. Terms and definitions The following terms and definitions apply in this document:

AEO Authorised Engineering Organisation

BRS business requirements specification

CED Customer Experience division (of TfNSW)

FRD Freight and Regional Development (of TfNSW)

ICD interface control document

INCOSE International Council on Systems Engineering

MCD maintenance concept definition

OpCo operations and maintenance company

OCD operations concept definition

PPD Planning and Programs division (of TfNSW)

SE systems engineering

SEMP systems engineering management plan

SRS system requirements specification

TfNSW Transport for New South Wales

TSD Transport Services division (of TfNSW)


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



5. Operations concept definition development Planning and Programs division (PPD) of TfNSW shall be responsible for producing the OCD

and business requirements that support it.

The OCD shall be prepared by authorised staff with appropriate competencies.

Authorised and relevant stakeholders shall be consulted during development of an OCD.

Key authorised stakeholders (as applicable to a proposed new or altered system) may include

but are not limited to the following:

• Transport Services (TSD), TfNSW

• Customer Experience (CED), TfNSW

• Planning and Programs (PPD), TfNSW

• Freight and Regional Development (FRD), TfNSW

• Transport Projects (TPD), TfNSW

• Transport Operators/Maintainers (OpCo)

• Asset Standards Authority (ASA), TfNSW

• Roads and Maritime Services (RMS), TfNSW

• other transport operators

• local Councils

The OCD shall be reviewed and approved by the authorised and relevant stakeholders.

Operational concepts and associated operational performance capabilities defined in the OCD

shall be developed and verified using suitable transport performance modelling tools.

Development of individual project and program OCDs shall be coordinated with other OCDs that

are in development or may already exist, to ensure that optimisation of one element of the rail

network does not adversely affect other elements of the network.

OCD information for all rail projects and programs shall be coordinated and managed by PPD.


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



6. Operational performance capability The OCD shall ensure that TfNSW enterprise level goals and objectives are identified and

traced to the required operational capabilities, operational concept activities, organisation and

assets.

Operational capability metrics shall be defined to support the operational concepts in the OCD.

Operational capability metrics may include, and are not limited to the following:

• system-level capability metrics, at transport network or mode level

• fleet capability metrics

• station and transport interchange capability metrics

• infrastructure capability metrics

• control and communications capability metrics

• stabling yard capability metrics

• maintenance depot capability metrics

• rail freight terminal capability metrics

The OCD shall justify the rationale and expected performance capability benefits of a proposed

operational change to the transport network.

The assumptions that underpin the rationale and expected performance capabilities shall be

identified.

7. Operational constraints The OCD shall describe any constraints applicable to a proposed operational change.

Operational constraints may include, and are not limited to the following:

• service operating hours, for example peak, off-peak, weekend, holiday, special timetables

• operating staff constraints, for example shift durations or planned changes to staff

operations at the site

• operating staff facilities, for example size, accommodation, travel distance, services

• easy access or disabled access constraints

• transport interchange access constraints, for example crowd capacity, passenger flow

rates

• security issues, for example those identified by risk assessment or notification by external

agency or from internal or external incident information © State of NSW through Transport for NSW Page 10 of 14 S

uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



• geographic limits

• flood and drainage constraints

• environmental constraints

• heritage constraints

There may be additional operating constraints unique to a specific project.

8. Operational service levels The OCD shall adopt a layered approach to transport operational service levels for planning and

decision-making.

Operational service levels may include the following:

• Level 1 Strategic: policy-based, high complexity, network or mode-wide scope, network or

mode-wide impacts, long-term change, and non-routine

• Level 2 Tactical or management: procedure-based, how to achieve policy, medium

complexity, medium-term, operational arrangements for achieving service and timetables,

routing and regulation

• Level 3 Operational: routine operations and decisions in each operational area of the

transport mode, including degraded and emergency operations, short-term change, and

routine

9. Operational assets and facilities The OCD shall describe operational assets and facilities affected by the proposed operational

change.

Operational assets and facilities may include, but are not limited to the following:

• fleet stabling facilities, for example stabling yards

• fleet assets, for example rolling stock

• maintenance depot facilities

• infrastructure assets, for example track, bridges and structures

• station and transport interchange assets

• control and communications assets, for example signalling and optical fibre network

• electrification assets, for example feeders, substations and overhead wiring

• freight terminal facilities


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



10. Operational process scenarios The OCD shall identify and describe relevant operational process scenarios.

Operational process scenarios to be defined in the OCD may include, but are not limited to the

following:

• network management operations

• line management operations

• area control operations

• electrical switching operations

• stabling yard operations

• fleet depot operations

• train operations

• station and interchange operations

• freight terminal operations

• Incident management and response operations

This section will typically form the bulk of the OCD.

11. Operational users The OCD shall identify and describe roles and responsibilities of operational users, as

applicable in their interactions with the proposed new or altered system.

Operational users to be identified in an OCD may include the following:

• network management operators

• line management operators

• signal and area control operators

• electrical switching operators

• fleet maintenance operators

• stabling yard operators

• fleet depot operators

• freight terminal operators

• train operators


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



• station operators

• maintainers, including infrastructure, control systems and fleet

• infrastructure delivery projects

• customers, including passenger and freight

• emergency services

• security control, monitoring and contract guard operators

• other transport owners and operators, for example Australian Rail Track Corporation

(ARTC)

The OCD shall relate responsibilities, accountabilities and informing of operational users to the

operational process scenarios.

The OCD shall consider the implications on operational staff skills and any training or retraining

needed due to the operational changes resulting from the introduction of new or altered assets.

12. Operations migration The OCD shall describe how operations will be safely migrated from existing operations to the

future operations, including possible interim operations so far as is reasonably practical at this

stage of knowledge of the technology related to the new or altered assets.

The OCD shall describe arrangements to preserve acceptable levels of safety, timetabled

services, efficiency, asset integrity, and service availability during operations migration.

13. Operational interfaces The OCD shall identify and describe operational interfaces.

Operational interface attributes may include, but are not limited to the following:

• who or what organisations share the operational interface

• how information is communicated and coordinated across the operational interface

• what information is communicated across the interface

• categorisation of the operating interfaces as internal or external to the transport mode

Interfaces with internal or external organisations associated with assets across the interface

shall be identified.

The parties associated with the internal and external parties associated with all assets at and

across the interfaces should be identified.


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017



14. Operating modes The OCD shall describe how the system will operate under different operating modes so far as

is reasonably practical at this stage of knowledge of the technology related to the new or altered

assets.

Operating modes may include the following:

• normal mode

• interim or abnormal mode, for example special sporting events

• degraded mode

• emergency mode, for example incident recovery, security, backup control

• maintenance or possession mode

The OCD shall describe arrangements that will be implemented following an incident or when

the service deviates from normal to abnormal, degraded or emergency levels.

The OCD shall describe the incident management organisation required to implement special

command and control processes.


uper

sede

d by

T M

U A

M 0

6008

ST

v3.0

, 26/

10/2

017

Documents

Operations Concept Definition - · PDF fileST v3.0, 26/10/2017 Operations Concept Definition T MU AM 06008 ST Standard . Version 2.0 . Issued Date: 26 March 2015 . Important Warning