Rail Operation Centre
Model Based Systems Engineering and Design
v 4.21
John Forrest
Solution Integration Program Manager
Agenda
25/03/2015
Systems Engineering Technical Forum Presentation
• ROC Program Background
• Systems Design Contexts
• MBSE Approach
2
Rail Operations Centre
ROC PROGRAM BACKGROUND
3
Meeting the expectations of our customers requires effective and
efficient management of the rail network
Improving the customer
experience in the face of
increasing demand
•
•
•
Increasing customer numbers
(100,000 during peak),
Increasing trains (60%
increase),
Increasing Freight numbers
(almost doubling by 2031)
Our response to incidents on
the network has a major impact
on the overall customer
experience
Paper based systems, email, fax,
phone communication and
manual updating of systems are
still the prevalent ways of
working. This has left our
processes fragmented, rigid and
inconsistent
Implement the ROC to
transform day of operations
management
•
•
•
•
4
Infrastructure (control
centre)
Technology (dynamic
timetabling, incident
management, customer
information)
Processes (‘day of
operations activities’
Way of working (customer
focussed and continuously
improving)
The ROC represents an opportunity to align our ‘day of
operations’ with the growing needs of customers
In collaboration with TfNSW, Sydney Trains & NSW Trains, our aim is to create a customer
focused and world class Rail Operations Centre
Benefits
Transformation
The ROC will deliver a number of
benefits to customers
1
Reduced delay time and improved customer
information
2
Faster development and communication of revised
timetable
3
Faster resolution of incidents, minimising delay times
for customers
4
More accurate, timely and consistent customer
information during delays
5
Faster restoration of service and communication
through collaborative working
The ROC will also benefit staff
Staff will benefit from better communication/ quality of
information to enable better decision making and relay of
information during ‘day of operations’.
5
Social Media
Process scope – ‘day of operations’ operating model
The below figure represents an overview of the ‘day of operations’ roles and infrastructure on the Sydney Rail Network
Management Key
Customer
NSW Trains
Maintenance
External Contractor
B
C
Service monitoring and incident
response coordination
Inputs into Day
of Operations
RMC
Crew Roster
Train
Crewing
CIU
SCC
NSWT
Fleet
Crewing
EOC
IOC
RTOC
TLS Screen
Train Control
Decision Capture
Network
diagrams
Overview Boards
Line Information Controllers
Incident response (site)
RERU
Train Crew Offices
Emergency Response
Train Crew Standards
NSW Train Crew Depots
Train Crew Compliance
Crew allocation
SMF
Crew co-ord
CCTV Monitoring
Crew attesting
Footage retrieval
ATRICS
Overview
Maintenance Activities
Network Bases
Technical
Electrical Maint support
Phones Maint support
Civil Maint support
Fibre Maint support
Signalling Maint support
Control Systems
Lifts and Escalators
SMS
Phone
Phone
CCTV
Alarm Systems
Phone
Stations
Desk systems
Train location
system (TLS)
IIMS
Customer Service Activities
Desk systems
Desk systems
Train Radio
Applications
and Systems
Crew Attesting
Crew Coordination
IRC
Coordinate
Network
rules and
procedures
Train Crew Depots
Manual Signalling
IRC RERU
Computer assisted signal control
Manage ATRICS, TLS and TVS systems
Manage network Communications systems
Manage Civil Infrastructure
Manage Signalling Infrastructure
Balance power supply
Manage high voltage network
Attest and assign crew
Allocate/ Reallocate Crew
Manage Fleet availability
Manage Waratah Fleet availability
NSWTrainlink Service coordination
Respond to alarms and calls
Coordinate Security Response
Crew
rosters
VCS
Train Graphs
Inputs into Day of
Operations
Train Operations Activities
Manual Signalling
Plan and Organise Alternate Transport
Prepare and Disseminate Customer information
Manage Journey Specific Customer Information
Instruct Train Crew
TCLO
Liaise with Train Crew
TMO
Transpose trains
Develop alternative train plans
Monitor Rail Network
Assess service impact of disruptions
Authorise work on track authorities
Functional Groupings and
Capabilities
input
Daily working timetable
Train
Planning
Equipment
and Tools
Planned Track work
Train Control
Dispatch Centres and Incident
Resolution
Signal
box
TCAC ICON
Attribute delays to incidents
Possessions
Track and manage customer feedback
A
Operations
PIMG
Transmission
Management
Systems
SMOI
LLDVA
OpCrew
ATRICS Panel
SCADA
MetroNet
DWDM network
management tool
LICS
Station Operations
Day of operations
Station Support
PICS (SPI screens)
Trains (guards and drivers)
Customer Service
Customer information
Customer Flow
Customer flow
ATRICS
TLS
LICS
SMARTS
Customer Information
FARS
SRS
TLS
Condition Monitoring
Network Management
IASS
6
6
The ROC will bring together a number of ‘day of
operations’ groups to centralise network control
7
RMC
Network control and customer
information
ICON
Network maintenance and
infrastructure control
SMF
Security incident management
and customer safety
Signal boxes
Advanced signaling functions
Rail Operations Centre
single control room
ROC Program Workstreams
Program Office
Scheduling, Budget,
Governance, Reporting
Solution Integration
Program Design & Delivery
Compliance & Assurance
Interrelated Projects
Infrastructure
Property
Construction
Facility Development
Control Systems
End to End Testing
Information Technology
Business Systems:
Daily Timetable
Incident Management
Customer Information
Legacy Integration
Transformation & Change
Organisation Design
Business Process Management
Training
Change Management
8
Disaster Recovery
Day of Operations Operating Model
Program Delivery Model
Rail Operations Centre
SYSTEMS DESIGN CONTEXTS
9
Service Design
• Service design is the activity of planning and
organising people, infrastructure, technology,
communication and materiel components of a service
in order to improve its quality and the interaction
between the service provider and customers
• We are viewing Sydney Trains Day of Operations as
a ‘Whole System’, comprising of numerous subsystems, which is designed to deliver a safe and
efficient customer service
10
Service Delivery Blueprint Detail
Transformation &
Change
11
Compliance &
Assurance
Process &
Schedule
Technology
Benefits
Strategy
Infrastructure
ROC Operational ‘Systems’
Information Systems
Architecture
Infrastructure
Control Systems Architecture
Business
Architecture
Infrastructure
Facility Design Architecture
12
Performance
Architecture
Organisation
Design
ROC Program Delivery Lifecycle
Current State Operating Models Future State Operating Models
Infrastructure
Control Systems Architecture Business
Architecture
Information Systems
Architecture
Performance Organisation
Architecture
Design
Infrastructure
Facility Design Architecture
Infrastructure
Control Systems Architecture Business
Architecture
Program
Delivery Model
Information Systems
Architecture
Performance Organisation
Architecture
Design
Infrastructure
Facility Design Architecture
Operation and
Maintenance
Concept of Operations
Requirements
Integrate,
Test, Verify
Detailed Design
13
Implementation
Requirements, Verification and Assurance
• There are a variety of requirements domains
–
–
–
–
Rail technology, control system and sub-system
Property, construction, building services, facilities
Business technology and enterprise integration
Organisation roles, processes, procedures
• There are a variety of assurance domains
–
–
–
–
–
14
Asset Management
Human Factors
Safety, Quality, Environment, Risk
3rd Party technology delivery
Benefits Realisation
• We have many concurrent “V”s evolving across a
number of integrated releases over the next 3 years
Assurance Case Approach
• One integrated Goal Structured
Notation model to establish scope
and traceability across all
requirements and assurance
domains
• Support for different types of
assurance ‘Cases’ and solution /
evidence sources
15
Rail Operations Centre
MBSE APPROACH
16
System of Systems
Semantic Meta-Model
M3 Model
M2 Model
M1 Model
Program Office
Infrastructure
Information Technology
Transformation & Change
M0 Model
Repositories, Artefacts and Proxies
17
Meta Object Facility (MOF)
Solution Integration
Example M1 Meta-Models
• OMG Business Motivation Model (Business
Architecture)
• UML 2.0 (General purpose technology and technical
business analysis)
• COSO (Risk)
• Prince2/MSP~PMLC~PEFm (Program management)
• Goal Structured Notation (Assurance)
• TRAK, MODAF, DODAF, TOGAF…
• ROC – bridging concepts, specialisation and
additional concepts to achieve end to end design
traceability
18
Example Meta Model
GSN_Claim Class (Abstract)
The GSN_Claim Class is used to record the
propositions of
GSN arguments. The GSN_Claim Class
extends the SACM Claim Class.
19
Superclass: Claim
Attributes: tobeInstantiated: Boolean
Semantics: As part of a pattern, any claim may
be declared as to be instantiated.
Example Blueprint Design Element Types
(M0)
• Organisation Model
–
Organisation Chart, Business Unit Structure, Establishment Positions, Position Descriptions, Skill
Sets
• Process Model
–
Performer Roles, Activities, Processes, Process Areas, Scenarios, Performance Metrics
• Assurance Model
–
Verification and Testing: Quality, Risk, Safety
• Program Model
–
Capabilities, Projects, Delivery Releases
• Benefit Model
–
Measures, Metrics, Business Requirements, Business Changes, Program Outcomes, Benefits,
Business Requirements
• Infrastructure Model
–
Floor Plans, Workstations, Collaboration Flows, Requirements (Comms, Power, Rail Technology &
Control Systems
• Technology Model
–
20
Required System Capabilities and High Level Functional Requirements (IMS, DTTS, CIMS), NonFunctional Requirements, System Use Cases, User Interfaces, System Interfaces, Solution
Architecture
Applying MBSE
• Design Schema (Reference)
– Define scope of operating and program models through explicit
design elements
– Enforce traceability, manage dependencies and change impact
across management viewpoints
• Implementation specifications (Artefacts)
–
–
–
–
–
Assurance cases
Business process models
Functional, non-functional requirements, use cases
Benefit map and realisation logic
…
• Integration and Reuse
21
– Position a single design element in multiple management
domains, notation views, and artefacts
– Release integrity tested ‘bottom up and across’ design
Design Element Type Example
• A ‘Workstation’ is a desk on the floor of the Operation Centre
fitted with technology which enables operators in the ROC to
perform their function
• Workstation Furniture & Fittings provide the operator with an
ergonomic setting in which to perform their function
• Workstation ICT elements provide access to information and
communication services
• A Workstation is situated at a Location which is specified on the
Operation Centre Floor Plan
• Workstation Tasks describe the various activities which each
type of operator performs at the Workstation
• A Human Factors Assessment assures the Workstation for use
by the operator for certain Tasks
22
Workstation Dependencies
UML, GSN, ROC
CLASSES
T&C
ROC Performer
Role
Technology
DTTS System
Requirements
INSTANCES
Solution
Integration
Deliverable
23
Infrastructure
Furniture and
Fittings
WORK PACKAGES
Rail Operation Centre
Model Based Systems Engineering and Design
Thank You
John Forrest
Solution Integration Program Manager
john.forrest@transport.nsw.gov.au
v 4.224