systems engineering onasew.com.au/wp-content/uploads/2017/11/systems... · · 2017-11-08•...

Systems Engineering on Parramatta Light Rail Project

Agenda

• What is Parramatta Light Rail and why is it important?

• System Engineering objectives and tools

• System elements

• Deliver Model and implications

• Key Messages

Greater Sydney Commission

5Parramatta Light Rail

PLR Route – Stage One

PLR….the transport project

• Transport for NSW considers you a customer from door to door to door

• The transport network of interest considers bus, ferry, light rail, heavy

rail, active transport and road traffic (including taxis and ride share).

• Interchanges are important - ideally people do not notice these.

• Special events

Current Status

• Environmental Impact Statement public consultation closed.

• Procurement of main works contractors commenced.

• Enabling works to start in 2018.

• System opening in 2023.

Objective for Systems Engineering on PLR

• Safe, reliable, customer focussed and integrated system of systems.

• Meets the project objectives, our responsibilities to the community and the

needs of stakeholders.

• Backbone of our quality and assurance process.

• Robust contract documentation that considers who is “best placed” to

make decisions.

Business Requirements Specification

• Business and stakeholders needs and objectives for the PLR Project

• Describes the change required to the existing Transport System

• Requirements elicited from all divisions within TfNSW, making them

“contributors” as opposed to “reviewers”

• Audience was Transport for NSW, which included Roads and Maritime

Services (RMS)

• BRS approved by the Project Control Group and Light Rail Change Control

Group

• Single source of requirements used to develop the solution. Document

configuration controlled, with process to change and approve modifications

Business Requirements Specification (cont.)

Different types of requirements


System Requirements Specification

informs

Technical specification for the system• Description of what it should do (functions)• Interactions with interfaces and external environment• Constraints on the system

The BRS precedes the development of the system requirements specification (SRS) and is a subset of the total requirements needed to characterise the

solution.

Defines the business opportunity or problem space• Business goals• Business needs• Business capabilities• Customer requirements

Business Requirements Specification (cont.)

informsinforms informs


informsPLR Customer

Service Specification

TfNSW PLR Project Land Use & Urban Design

Objective

TfNSWParramatta Light

Rail - Industry Briefing

TfNSW Parramatta

Strategic Business Case

TfNSW Parramatta Light Rail

Objectives

TfNSW PLR Project

Sustainability Objectives

TfNSWCustomer &

Product Strategy

PLR Operational Concept

Document

Greater Sydney

Commission

PLR Fleet Requirements

PLR Sustainability Requirements

PLR Urban Design Requirements

informsinforms

TfNSW Stakeholder Requirements

Iterative process

Problem Space

Solution Space

The approved BRS provides the single source of requirements that describes the PLR product.

Definition Design

NSW Government

Announcement

PLR Constructability Report

informs

Wider Stakeholder Requirements


TfNSW Asset Management Framework

Decision Management

Technical Decisions captured in Product Definition Sheet (or Technical Issues

Register) which utilised the project governance structure to confirm decisions

• Project Control Group

• TfNSW Project Team

• Authorised Engineering Organisation

Multi-criteria Analysis to determine route alignment to meet project objectives of:

• City shaping

• Connectivity

• Place

• Choice

Systems Architecture

• View of the PLR system to meet the business requirements, without

specifying the detailed design, including:

• Logical description

• Physical description

• Interface definition

Systems Architecture -Logical

Developed scenarios to understand the users interfaces, including

• Passenger or Customer using the system

• Light Rail Vehicle Driver driving the Light Rail Vehicle

• Operations Control Centre role in the operations of the system

• Road Drivers, Cyclists and Pedestrian interactions with the light rail

system as a complete transport system

Systems

Architecture -

Logical (cont.)

Activity Diagram of Customers

travelling on PLR

Systems Architecture –Logical (cont.)

Scenarios help by:

• Understanding the touch points of the

users with the light rail system

• Ensure the system is adequately

specified and implemented to meet user

needs

Systems Architecture –PhysicalSystems of Systems thinking applied to Transport Systems

Parramatta Light Rail

Light Rail System

Road System Active Transport Public Domain Utilities

Systems Architecture –Interface

• N2 to systematically identify interfaces

• Definition of interface with requirements

Systems Architecture –Physical & Digital Engineering• Digital Engineering is the enabler for asset information to be collated in a

consistent format which is understood by industry.

• Creating a link between the System Breakdown Structure at project conception, to

an Asset Information Model to associate O&M data to.

System Breakdown Structure

Project Information

Model

Asset Information Model

Project Life

Systems Architecture –Physical & Digital Engineering

• Late developing System Breakdown Structure for the project to use

• System Breakdown Structure relatively immature, even though systems being

specified are mature and well know

• Wider TfNSW review and acceptance of System Breakdown Structure for

transport systems for utilisation by projects.


• Originally two System Requirements Specifications:

• Infrastructure

• Light Rail Vehicle (LRV)

• Decomposition from vague and unverifiable Business Requirements to

verifiable System Requirements

• Captures system definition from Systems Architecture

(Infrastructure + LRV) + Operations

Scope and Performance Specification



informs

Scope and Performance Requirements

informs

Stakeholder needs

System Definition

Contract Specification

Scope and Performance Specification (cont.)• Subject Matter Expert (SME) write requirements in template and rules on writing

requirements provided. Challenges include:• SME reverting back to old and familiar ways of writing requirement, which did not follow

Systems Engineering approach

• Modifying existing specifications from other light rail projects as systems specified are

we understood

• Traceability from SPR to existing requirements – BRS and SRS, not retained

• Review of SPR through tool Respecify – a new requirements engineering tool,

which supports the requirement authoring process.

• Activity ongoing to complete SPR and complete traceability:

BRS SRS SPR

Light Rail Vehicle

RoadLight Rail

Public Domain

Drainage

Street

Utilities≠

Parramatta Light Rail 26

The Light Rail System


• 100% low floor , air conditioned light rail vehicles

• Capacity seated and standing:

• 250 @ 3 people / m2

• 300 @ 4 people / m2

• Proven “off the shelf” technology

The Light Rail System

Stabling and maintenance facility


Lennox Bridge

Structures


James Ruse Drive Bridge Parramatta River Bridge at Camellia

Structures (cont.)

Catenary FreeCatenary

Proposed Catenary Free Sections

Westmead Station

to Cumberland

Hospital Stop

Prince Alfred Square

to Tramway Avenue


The Road System


• Need to satisfy both the Roads Act and Rail

National Safety Law

• Road Rules apply

• Freight and Servicing requirements identified

• Design and check vehicles established

• Swept path checks to ensure safe movements

• Driveways under assessment

• Authority Approval from Roads and Maritime

Services

The Road System


• Enabling works to build road

capacity for construction and

operation of the light rail

• O’Connell St – extending 2 lanes

each way

• George St (west of Harris St) – 1

lane each way

The Road System


Urban Design

‘Eat Street’


Westmead


Female Factory Precinct

Stop integration


April 1998

DownstreamUpstream

Flooding and Drainage


• Impact requirement: No impact in

all events up to the 1% Annual

Exceedance Probability (AEP)

event.

• Immunity requirement:

uninterrupted operation in every

event up to 5% AEP event.

• Targeting better immunity with

consideration of climate change

and future proofing for upstream

and downstream upgrades.

Flooding and Drainage


Utilities Church and Victoria St

• Specialist utilities management team as

part of the integrated team

• Utilities assessment – entire alignment

• All utilities identified to AS5488 Quality

Level B or better

• Basis of design manuals – all utilities

• Treatment Option papers developed

Utilities


Electromagnetic Compatibility (EMC)


Human Factors


• Sustainability must be incorporated into all of our activities.

• Sustainability has taken a materiality and life cycle assessment.

• Important issues include

• climate risk

• energy use

• water use

• materials use

• discharges to the environment during

construction

• heritage and workforce .

• ISCA Ratings tool will be used to measure sustainable outcomes

Sustainability


The delivery strategy


• Supply, Operate and Maintain (SOM) Contractor

will be responsible for Systems Integration.

• SOM contractor inputs into Infrastructure (INF)

Contractor specification during tender phase.

• Nomination of design stages to have a common

language and milestones.

• Delivery of interface information will be specified.

• Performance specifications need to be

reconsidered.

The Implications


• SOM will act as integrating

Authorised Engineering

Organisation (AEO).

• INF responsible for assurance of

their works.

• SOM can benefit from INF

assurance.

• Configuration Management

responsibilities on SOM.

From ASA Charter

The Implications

Key Messages

Systems engineering and systems thinking will be inherent to the success of

the Parramatta Light Rail Project

Systems engineers bring a valuable skillset and toolkit that client and

delivery organisations needs to be resource appropriately

Systems engineering activities need to consider the existing constraints and

also the commercial environment

Balance of innovation vs prescription and “best placed” decision making

Thank you and Questions

2. System Requirements Specification (cont.)

Light Rail

Operators & Maintainers

Passengers or Customers

Community & Surrounding area

2. System Requirements Specification (cont.)

Community & Surrounding area

Operators & Maintainers

Passengers or Customers

Light Rail

System of Interest

systems engineering onasew.com.au/wp-content/uploads/2017/11/systems... · · 2017-11-08•...

Documents