asset standards authority - transport for nsw...systems engineering standards briefing - 12 april...

April 2018

Asset Standards Authority Providing leadership, support and guidance for the public transport industry Luke Homann, Director Authorisation & Audit

April 2018

An overarching strategy supported by a suite of plans to achieve a 40 year vision for our transport system

Six outcomes

How we‘ll measure success

Transport assets by numbers

Systems Engineering Standards Briefing 12 April 2018 | 6

-Systems Engineering Standards Briefing 12 April 2018 | 7

ASA as a part of FSP • FSP’s purpose and priorities

• Leads the delivery of evidence-based transportsolutions

• Drive innovation and set strategic directions tomeet NSW’s transport needs of the future

• Our purpose “To be visionary in creating anintegrated transport system for NSW”

• Our focus is on developing integrated solutionsacross all road, rail and waterway networks

ASA’s contribution • To be visionary in creating an integrated transport system for NSW by leading and

shaping industry and our corporate and asset systems.

ASA core functions

Engineering and technical capabilities

Thank you and welcome to the Systems Engineering Seminar

Please contact us at: Level 7, 12 Help St, Chatswood

02 9422 7187

info@asa.transport.nsw.gov.au asa.transport.nsw.gov.au

-Systems Engineering Standards Briefing 12 April 2018 | 11April 2018

ASA Seminar: Systems Engineering Standards Briefing and Update Richard Fullalove, Manager Systems Engineering Process Gary Arabian, System Architecture and Requirements Manager

Systems Engineering: Seminar agenda Document Start

1 Opening and introduction 0900

2 T MU MD 00014 GU Multi Discipline Rail Infrastructure Design Management Guide v1.0 0915

3 T MU AM 06006 ST Systems Engineering Standard v2.0 1015

4 Morning Tea 1030

5 T MU AM 06006 GU Systems Engineering Guide v2.0 1045

6 T MU AM 06013 GU System Concept Development Guide v1.0 1100

7 T MU AM 06014 GU Guide to Systems Integration v1.0 1130

8 T MU AM 06016 GU Guide to Verification & Validation v1.0 1145

9 T MU AM 06015 TI Ops Concept for deployment of drones on NSW Transport network 1200

10 Close 1230

Systems Engineering: Find a standard

T MU MD 00014 GU Multi Discipline Rail Infrastructure Design Management Guide v1.0 (new)

Richard Fullalove, Manager Systems Engineering Process

April 2018

Topics of interest

• Background and purpose of this guide • TfNSW project life cycle stages • Engaging a design AEO • Design planning • Design authority & competence • Design inputs • Standards management • Safety in design • Judgement of significance (JoS)

• Value engineering • Design assurance • Design documentation & records • Dependability in design • Interface design management • Design configuration management • Design support post-AFC • Integrated design approach

Background and purpose of this guide • AEO Framework, process and requirements established 2013 • AEO assessments identified variability in rail design capability maturity • Identified “Areas of Concern” (AOCs) in many areas, especially:

• Design inputs not well defined • Interdisciplinary design not sufficiently integrated • Whole of life RAMS/Sustainability missing • Standards management (concessions/NCs) weak • Inadequate post-AFC design support

• Early engagement: Technical Forum on 4 Dec 2016, EA Chatswood • Published: Jan 2018 • Provides general and scalable guidance on the principles and practice of multi-discipline rail

infrastructure design management • Elaborates on T MU MD 00009 ST AEO Authorisation Requirements. • Informal feedback so far has been positive (ST and external to NSW) https://www.transport.nsw.gov.au/system/files/media/asa_standards/2018/t-mu-md-00014-gu.pdf

TfNSW project life cycle stages • Designers can be deployed in many of these stages:

• Concept: Technical Advisors develop feasibility/concept designs • Specify: TAs develop SRS + Reference Design • Procurement: TAs develop procurement tender, evaluate • Design: not TA (but depends on contracting model):

• Design & Construct (D&C) contract • Public Private Partnership (PPP) • Joint Venture (JV) • Alliance

• Build: Design support to constructor (RFIs, advice, witness) • Integrate: Design support during system integration & testing • Accept: Signoff of final “Work as Executed” updated designs • Dispose: Design decommissioning plans (brownfield work)

Engaging a design AEO • Design service type and deployment:

• Technical advisor: feasibility/concept/specify/procure • Design consultant: design/build/integrate/accept/dispose

• Establishing design team org structure (matrix) • Project Manager: leads project (all project team functions) • Engineering Manager: leads all engineering (design, build, test) • Design Manager: this guide is aimed at this function • Discipline Lead: lead technical SME in specific asset area • Designer: produces design in specific asset area • Checker: immediate check in specific area • Verifier: can be discipline lead (top SME) • CAD/BIM/DE specialist: may have engineering qualifications.

Design planning • Define project design scope and deliverables • Establish design work packages (DWPs) • Establish design organisation, allocate resources to DWPs • Establish design budget, allocate to DWPs • Establish design WBS and schedule • Identify design stakeholders • Identify design inputs (WEX drawings/models/survey/asset info/reqts) • Plan safety in design activities • Plan design assurance/verification activities • Plan design coordination (including IDC/IDR) activities • Plan and establish document/data/record control activities

• Design document/deliverable tree • Consider parent, peer and child plans on specific project

• Plan and establish design competency management activities Systems Engineering Standards Briefing 12 April 2018 | 19

Design authority and competence assurance • Competency Management System assures:

• trained, competent and authorised design staff • engineering management methodologies appropriate • appropriate documented CM processes, procedures, methods • appropriate design tools and competence to use them • appropriate levels of competent supervision and control

• Define competencies and proficiency levels for typical design roles: • Design Manager • Discipline Lead • Designer • Checker • Verifier • CAD/BIM developer

Design inputs • Statement of need or similar in place (and signed off!) • Business Requirements signed off! • System Requirements signed off! • Design source records (typical):

• Surveys (topographic, cadastral, geotech, hydrology, correlation) • Existing buried services location (ISS, DSS, DBYD) • Easement info (wayleaves in the UK) • As-built drawings and CAD/BIM models (brownfields) • Asset register info (existing) • Asset condition surveys (existing) • Concept or reference design (depends when engaged)

• Ensure traceability of design back to design inputs

Standards management • Identify relevant standards (ASA/Australian/International) • Agree and declare standards baseline • Monitor standards change notifications (ASA/AS/International) • Assess design change impact (safety, function, performance, cost) • Specific discipline lead SMEs to do this assessment • Brief standards changes (+ impacts) to design team • Raise project change requests (cost/time/resource) • Manage concessions and non-conformances

• Proactive, risk-based alternative to blind compliance is OK • Challenge standards – help us to improve them! • Late non-conformance applications not OK

Safety in design, judgement of significance • Safety in Design (SiD)

• SiD is just part of overall system safety assurance • Deals specifically with the designers responsibility • SiD impacts others (construction, maintenance, decommissioning) • Integrates hazard identification & risk assessment • Start early in design • SiD workshops require skilled facilitators • Involve designers, constructors, installers, testers, operators, maintainers

• Judgement of Significance (JoS) • Impact assessment of engineering change (not just design) • Safety is primary consideration • Other criteria too (e.g. cost, buildability, testability, maintainability..)

Value engineering • Links asset function and performance to asset value • Considers whole of life (WoL) asset value • Most effective in feasibility and concept phases

• Feasibility: multi-criteria analysis of multiple options • Concept: analysis of single preferred option

• Establish VE/VfM tool or workbook • Use to select preferred option • Supports “Limb 3” cost optimization in alliance model

Design assurance • Inputs and controls:

• Applicable standards • Requirements/specifications • Outputs of previous design phase • Risk register • Survey results • Design calculations • Design drawings/models

• Sustainability review: will it meet Sustainability Guidelines? • Constructability review: Can we build it? Site accessibility? Transportability? • Maintainability review: Can we maintain it? New maintainer training? • Operability review: Can we operate it? New operator training? • Disposability review: Easy to decommission and dispose of, or re-purpose? • Technical reviews and stage gates: Progressive assurance and check • Design verification: Meets requirements and complies with standards? • Design approval and acceptance: Due process demonstrated?

fing 12 April 2018 | 25 Systems Engineering Standards Brie

Design documentation and records

NSW State Records Act 1998 and related legislation requires you to: • establish and maintain full and accurate records of activities • establish and maintain a records management procedure • protect records, ensuring safe custody and proper preservation • monitor and report on records management • provide State Records access to records to monitor compliance • maintain accessibility of technology dependent records over time

Design documentation and records (contd.)

Design records include (but are not necessarily limited to): • design management plan • safety assurance / safety in design plan • design models, simulations and analysis reports • design drawings, CAD/BIM/DE models and files • design calculation records • design verification records • interdisciplinary design check (IDC) certificates • design hazard log • design release checklists • design reports • product or equipment specifications, bills of materials (BoM)

Dependability in design • Can we depend on the system to meet its designed intent?

• Function • Performance

• Dependability in rail infrastructure design can include: • Operational safety (WoL) • Reliability, availability, maintainability (RAM) • Durability (particularly in civil/structural works) • Security (physical and cyber) • Sustainability (including climate resilience)

• RAM analysis of designs may include: • Failure Modes Effects & Criticality Analysis (FMECA) • Maintenance Requirements Analysis (MRA) • Integrated support analysis

Interface design management

• Identify technical/system interfaces between asset areas • Develop/populate interface (N2) matrix – large/complex systems • Develop high-level system context and interface architecture (large/complex) • Develop interface control agreements (high level ICDs) • Define and specify interfaces (interface requirements specs) • Analyse interfaces (functional, physical, energy, data, human, clearance) • Trace interface requirements into detailed design development • Conduct regular interface design reviews • Mostly done using collaborative BIM/DE platforms nowadays • Conduct interface design checks at key stage gates

Design configuration management • Identify design configuration/configurable items • Manage design change

• Change can occur in design, manufacture, install, integrate, test • The later the change, the more adverse impact (time, cost) • Change can be triggered by:

• Standards change • Contract work scope change • Requirements change

• RFI

• Nonconformance • Assess change impact on safety, RAM, the “ilities”

• Establish design configuration baselines • Manage design configuration status • Design configuration gates • Configuration/Change Control Boards (TNAC and Project-specific)

Design support post-AFC • During fabrication/manufacturing (off-site at factory)

• Produce product specs and BoMs • Respond to OEM/supplier queries on specs • Witness FAI/FA T tests at factory

• Construction/installation (on-site) • Design input to inspection & test plans (ITPs) • Respond to RFIs • Analyse and authorise design changes from RFIs • Provide on-site designer advice to constructor • Witness site acceptance tests (SATs) • Process construction mark-ups

• System integration & test • Witness integration testing (SITs)

• Commissioning & acceptance • Support commissioning • Process commission mark-ups (WEX)

Integrated design approach • Process model design work streams:

• Signaling and control systems • Track • Civil/structures • Stations and buildings • Low voltage power supplies • High voltage and traction power supplies • Overhead wiring • Telecommunications (/Operational Technology)

• Consider integrated design in phases: • Concept design (or 30%) • Preliminary design (or 70%) • Detailed design (or 100%)

• Individual asset design streams interact with each other • Design integration enforced via IDRs/IDCs

Integrated design approach

Discussion

T MU AM 06006 ST Systems Engineering Standard v2.0 (update)

April 2018

Gary Arabian, System Architecture and Requirements Manager

Introduction

• Mandatory requirements for SE management

• Defines responsibilities

• Supports TfNSW asset management framework

• v1.0 published March 2015 • v2.0 published November 2017

Purpose and scope of SE standard

Purpose:

To provide a structured set of requirements to manage SE activities within transport projects

Scope:

Covers requirements for planning and execution of SE activities

Version 1.0 Version 2.0

Discussion

Systems Engineering Standards Briefing - 12 April 2018 | 40

T MU AM 06006 GU Systems Engineering Guide v2.0 (update)

April 2018

Introduction Provide guidance in applying requirements in SE standard

Provides SE-101 information

• What is a system • Benefits • Outcomes of not using SE • Scaling and tailoring • Stakeholder viewpoints • Planning for SE and it’s relationship to

other plans• Exa mples

v1.0 published May 2015v2.0 published March 2018

Purpose and scope of SE Guide

Purpose:

To provide guidance on complying with the mandatory requirements of the SE Std.

Scope:

Set the structure and practice for carrying our SE activities associated with planning, acquisition, development, utilisation and disposal of new or altered transport systems.

Version 2.0

Discussion

T MU AM 06013 GU System Concept Development Guide v1.0 (new) Gary Arabian, System Architecture and Requirements Manager

April 2018

Introduction

• Referred to as ConOps

• describes the problems it seeks to solve

• describes high-level operational scenarios

• Enterprise level measures

Currently v0.3v1.0 to be published June 2018

Purpose and scope of ‘System Concept’ Guide

Purpose:

Provide guidance to TfNSW, agencies and the AEO supply chain in delivering a system concept (or ConOps) on behalf of TfNSW.

Scope:

This document is a guide for developing enterprise and strategic level system concepts for complex TfNSW projects.

Applies to TfNSW, transport agencies and contracted AEOs – Multi-modal

Proposed System Concept table of contents

Discussion

T MU AM 06014 GU Guide to Systems Integration v1.0 (update & new code)

April 2018

Introduction Purpose:

Establishes the recommended interface management and systems integration management principles and methodologies for transport agencies and AEOs

Scope:

Our interpretation of the interfacemanagement and systems integration technical processes in ISO/IEC 15288.

Multi-modal and covers plan stage up until operate/maintain

TS 10507 v1.0 published August 2013T MU AM 06014 GU v1.0 published Mar 2018

Key changes to ‘Guide to Systems Integration’ • Remove ‘AEO’ from title and make it applicable to transport agencies

• Clearly explain; interface management / systems integration

• Include references to latest SE guides/standards

• Reference to ENM4 and ENM5 AEO requirements

Discussion

T MU AM 06016 GU Guide to Verification & Validation v1.0 (update & new code)

April 2018

Introduction Purpose:

Describes the V&V process, including key responsibilities that TfNSW, transport agencies and AEO is expected to implement in managing V&V

Scope:

Our interpretation of the V&V technical processes in ISO/IEC 15288.

Multi-modal and covers plan stage up until operate/maintain

TS 10506 v1.0 published August 2013T MU AM 06016 GU v1.0 expected June 2018

Key changes to ‘Guide to V&V’

• R emove ‘AEO’ from title and make it applicable to TfNSW/transport agencies

• Link guide to ENM11/12 and relevant CM gate deliverable

• Include references to latest SE guides/standards

• Update content wherever possible and make it multi-modal

Discussion

T MU AM 06015 TI

Ops Concept for deployment of drones on NSW Transport network v1.0 (expect to publish May 2018) Richard Fullalove, Manager Systems Engineering Process

April 2018

Drones Operational Concept – key topics

• Operational benefits

• Operational risks and dis-benefits

• Operational context and environment

• Operational constraints

• Operational actors/users

• Operational assets/facilities

• Operational use cases

• Operational interfaces

• Operational modes

• Operational scenarios

Drones Operational Concept – context

Drones Operational Concept - Interfaces

Drones Operational Concept - Scenarios

Discussion

asset standards authority - transport for nsw...systems engineering standards briefing - 12 april...

Documents

nelson city council engineering standards...

in systems engineering standards and models? - defense

lanl engineering standards manual std-342-100 chapter 20...

edi standards development pamela a. grosze, manager of...

developing standards for systems of systems (sos...

ics – software engineering group 1 sns control systems...

smc specs & standards initiative dave davis chief, systems...

international standards for systems of systems engineering

city of prescott general engineering standards...general...

dod role in standards and models...- weapon systems...

towards integrated systems and software engineering...

what ˇs all this churn ˇ in systems engineering standards...

systems engineering standards & process architectures · pdf...

systems engineering standards landscape - elysium ·...

towards integrated systems and software engineering...

engineering standards for ohsu projects engineering...

national grid gas engineering standards printing...

establishing profiles for systems engineering standards: a

programme standards: engineering and engineering technology...

systems engineering standards: status and needs · pdf...