Embed Size (px)
Citation preview
1
Rail Operation Centre
Model Based Systems Engineering and Design
John Forrest
Solution Integration Program Manager
v 4.2
2
Agenda 25/03/2015
Systems Engineering Technical Forum Presentation
• ROC Program Background
• Systems Design Contexts
• MBSE Approach
3
Rail Operations Centre
ROC PROGRAM BACKGROUND
4
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
• Infrastructure (control
centre)
• Technology (dynamic
timetabling, incident
management, customer
information)
• Processes (‘day of
operations activities’
• Way of working (customer
focussed and continuously
improving)
5
The ROC represents an opportunity to align our ‘day of
operations’ with the growing needs of customers
Social Media
In collaboration with TfNSW, Sydney Trains & NSW Trains, our aim is to create a customer
focused and world class Rail Operations Centre
Benefits
The ROC will deliver a number of
benefits to customers
Reduced delay time and improved customer 1 information
Faster development and communication of revised 2 timetable
Faster resolution of incidents, minimising delay times 3 for customers
More accurate, timely and consistent customer 4 information during delays
Faster restoration of service and communication 5 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’.
Transformation
6
Dispatch Centres and Incident
Resolution
Manual Signalling
Manual Signalling
Electrical Maint support
Network Bases
Emergency Response
RERU
Customer Service
Customer Information
Stations Station Operations
Civil Maint support
Customer Flow
Day of operations
Station Support
Crew Coordination
Train Crew Depots
Crew Attesting
Train Crew Compliance
Train Crew Offices
Train Crew Standards
Technical
NSW Train Crew Depots
Crew co-ord
Crew attesting
Crew allocation
Signalling Maint support
Fibre Maint support
Phones Maint support
Control Systems
Lifts and Escalators
SMF
CCTV Monitoring
Service monitoring and incident
response coordination
Co
ord
inate
input
Inputs into Day
of Operations
Pla
nn
ed
Tra
ck
wo
rkD
ail
y w
ork
ing
tim
eta
ble
Train
Planning
Cre
w R
os
ter
Train
Crewing
Possessions
Fu
nct
ion
al G
rou
pin
gs
an
d
Ca
pa
bili
ties
Eq
uip
me
nt
an
d T
oo
ls
RMCNSWT
NS
WT
rain
lin
kS
erv
ice
co
ord
ina
tio
n
Train location
system (TLS)IIMS
LLDVA
FARSSRS
ICON
Transmission
Management
Systems
DWDM network
management toolSMARTS
Condition Monitoring
Network Management
MetroNet
LICS
SCADA
Signal
box
SMOI
IASS
TCAC
OpCrew
TLS
All
oc
ate
/ R
ea
llo
ca
te C
rew
Att
es
t a
nd
as
sig
n c
rew
Crewing
Footage retrieval
Ap
plic
atio
ns
an
d S
yste
ms
Inputs into Day of
Operations
VCS
Alarm Systems
Network
rules and
procedures
Desk systems
Network
diagrams
Crew
rosters
SMS
TLS Screen
Train Operations Activities
Maintenance Activities
Customer Service ActivitiesCCTV
IRC
Co
mp
ute
r a
ss
iste
d s
ign
al
co
ntr
ol
RERU
Lin
e I
nfo
rma
tio
n C
on
tro
lle
rs
Au
tho
ris
e w
ork
on
tra
ck
au
tho
riti
es
Train Control
Mo
nit
or
Ra
il N
etw
ork
As
se
ss
se
rvic
e i
mp
ac
t o
f d
isru
pti
on
s
De
ve
lop
alt
ern
ati
ve
tra
in p
lan
s
Tra
ns
po
se
tra
ins
TMO
Att
rib
ute
de
lays
to
in
cid
en
ts
TCLO
Lia
ise
wit
h T
rain
Cre
w
Ins
tru
ct
Tra
in C
rew
CIU
Pre
pa
re a
nd
Dis
se
min
ate
Cu
sto
me
r in
form
ati
on
Ma
na
ge
Jo
urn
ey S
pe
cif
ic C
us
tom
er
Info
rma
tio
n
Pla
n a
nd
Org
an
ise
Alt
ern
ate
Tra
ns
po
rt
Tra
ck
an
d m
an
ag
e c
us
tom
er
fee
db
ac
k
Re
sp
on
d t
o a
larm
s a
nd
ca
lls
SCC
Co
ord
ina
te S
ec
uri
ty R
es
po
ns
e
Ma
na
ge
Fle
et
ava
ila
bil
ity
Fleet
Ma
na
ge
Wa
rata
h F
lee
t a
va
ila
bil
ity
Management Key
Customer Operations NSW Trains Maintenance External Contractor
EOC
Ma
na
ge
hig
h v
olt
ag
e n
etw
ork
Ba
lan
ce
po
we
r s
up
ply
IOC
Ma
na
ge
Civ
il I
nfr
as
tru
ctu
re
Ma
na
ge
Sig
na
llin
g I
nfr
as
tru
ctu
re
RTOC
Ma
na
ge
ne
two
rk C
om
mu
nic
ati
on
s s
ys
tem
s
Ma
na
ge
AT
RIC
S,
TL
S a
nd
TV
S s
ys
tem
s
Trains (guards and drivers)
Customer information
Customer flow
Phone
Phone
Phone
Desk systems
Overview Boards
Train Graphs
Train Radio
Desk systems
PIMG
TLS
Train Control
Decision Capture
A B C
Incident response (site)
IRC
ATRICS
Overview
ATRICS
ATRICS Panel
LICS
PICS (SPI screens)
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
Current Day of Operations Model
6
7
The ROC will bring together a number of ‘day of
operations’ groups to centralise network control
Rail Operations Centre single control room
RMC
ICON
SMF
Signal boxes
Network control and customer
information
Network maintenance and
infrastructure control
Security incident management
and customer safety
Advanced signaling functions
8
Program Design & Delivery Compliance & Assurance Interrelated Projects Disaster Recovery End to End Testing
Solution Integration
Program Office
Scheduling, Budget, Governance, Reporting
Information Technology
Business Systems: Daily Timetable
Incident Management
Customer Information
Legacy Integration
ROC Program Workstreams
Infrastructure
Property
Construction
Facility Development
Control Systems
Transformation & Change
Organisation Design
Business Process Management
Training
Change Management
9
Day of Operations Operating Model
Program Delivery Model
Rail Operations Centre
SYSTEMS DESIGN CONTEXTS
10
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 sub-
systems, which is designed to deliver a safe and
efficient customer service
11
Se
rvic
e D
eliv
ery
Blu
ep
rin
t D
eta
il
Technology
Transformation &
Change
Infrastructure
Strategy
Compliance &
Assurance Process &
Schedule
Benefits
12
ROC Operational ‘Systems’
Infrastructure
Control Systems Architecture
Information Systems
Architecture
Business
Architecture
Infrastructure
Facility Design Architecture
Organisation
Design
Performance
Architecture
13
ROC Program Delivery Lifecycle
Infrastructure
Control Systems Architecture
Information Systems
Architecture
Business
Architecture
Infrastructure
Facility Design Architecture
Organisation
Design
Performance
Architecture
Infrastructure
Control Systems Architecture
Information Systems
Architecture
Business
Architecture
Infrastructure
Facility Design Architecture
Organisation
Design
Performance
Architecture
Current State Operating Models Future State Operating Models
Program
Delivery Model
Concept of Operations
Requirements
Detailed Design
Implementation
Integrate,
Test, Verify
Operation and
Maintenance
14
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
– 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
15
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
16
Rail Operations Centre
MBSE APPROACH
17
System of Systems
Semantic Meta-Model
M2 Model
M3 Model
M1 Model
M0 Model
Meta
Obje
ct F
acility
(MO
F)
Information Technology
Infrastructure
Transformation & Change
Solution Integration
Program Office
Repositories, Artefacts and Proxies
18
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
19
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.
Superclass: Claim
Attributes: tobeInstantiated: Boolean
Semantics: As part of a pattern, any claim may
be declared as to be instantiated.
20
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
– Required System Capabilities and High Level Functional Requirements (IMS, DTTS, CIMS), Non-
Functional Requirements, System Use Cases, User Interfaces, System Interfaces, Solution
Architecture
21
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
– Position a single design element in multiple management
domains, notation views, and artefacts
– Release integrity tested ‘bottom up and across’ design
22
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
23
Workstation Dependencies
Infrastructure
Furniture and
Fittings
Technology
DTTS System
Requirements T&C
ROC Performer
Role
Solution
Integration
Deliverable
CLASSES
INSTANCES
WORK PACKAGES
UML, GSN, ROC
24
Rail Operation Centre
Model Based Systems Engineering and Design
v 4.2
Thank You
John Forrest
Solution Integration Program Manager
