1 developing the mbse approach tony ramanathan principal engineer network rail

20
1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

Upload: tobias-hart

Post on 25-Dec-2015

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

1

Developing the MBSEApproach

Tony RamanathanPrincipal EngineerNetwork Rail

Page 2: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

2

The Railway System

Investment Governance GRIP

Asst Life

Models / Analysis used

Interface Management – why we need Modelling

Modelling Tools

Design Handbook inc the Building Blocks

Agenda

Page 3: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

3

The people, The process applied,

The systems used

Page 4: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

4

Project Governance - GRIP“Project Life-Cycle”Governance for Railway Investment Projects (GRIP)There are Eight GRIP Stages

A RUS scheme is outside of Project Governanceand is between 5 to 7 years prior to GRIP 1Pre-GRIP

Page 5: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

5

Passenger Demand

SafetyRisk

TimetableRobustness

SystemReliability

Life Cycle Costs

Infrastructure Loading

ElectrificationCapacity

SignallingCapacity

LayoutCapacity

SystemCapability

Analyses Used in Systems Engineering

LayoutCapacity

TimetableDevelopment

Performance Evaluation

TrainService

Specification

Page 6: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

6

Asset Life

Railway System - Designed Asset Life

Structures 120Y Track / Signal

30 to 35 Y

Network RUS

6 to 20 Y Trains35Y

020406080

100120140

Asset Types

Yea

rs

TOC Franchise Between 5Y to 18 Y

Page 7: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

7

Interface Management - train infrastructure interfaces

• OLE Contact• Traction Power• EMC

• Platform Occupation/ Dwell Times

• Platform Length/SDO

• Stepping Distance• Station/ DDA Compliance

• Wheel/ Rail Interface• Axle Load• Route availability

(RA) / Allowable Speeds

• Train Detection • Track Conditions• Track Design/Quality• Drainage• Tonnage passing (load)

• Gauging Clearance• Kinematic Envelope (KE)

• Customer Information Systems (CIS)

• Lineside Infrastructure• Signalling & Telecoms

• Passengers behaviour

Page 8: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

Modelling ToolsSystems Analysis

Section number to go here

Page 9: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

9

VTSIM

Models often consider differing Time Horizons

Spatial Representation*

Analysis Time Horizon

Mins Hours Days Periods Years MultiYears

EMI

RailSys

Pedflow

OSLO

ICM

Scheme level

Route level

Full UK

CUI

Asset level

TRAIL

SPA

* Spatial representation within a single model

Page 10: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

10

SA Approach towards Option Selection

Option 1 Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

Option X Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

‘Favoured Option’

Option Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

OptionSelection

SPA

RailSys

TRAIL

TIP

OSLO

LCC

Legion

Option 1 Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

Option X Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

Requirements& Option

Validation:

Ops & Perf. EngineeringEng PolicyFeasibility

SystemsCapability Modelling

PreliminaryAssessment

??

?

Option 2 Capability:CapacityJourney TimesPowerReliabilityMaintenanceConstructionWhole life cost

?

?

Page 11: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

11

Typical System Breakdown Structure (SBS)

Page 12: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

12

TRAIL (Transportation Reliability, Availability and Integrated Logistics)

Infrastructure

TRAIL discrete event simulator

OperationsRolling stockTimetable

Lateness Analysis

Delay Analysis

PPMInfrastructurePerformance

OperationsPerformance

Page 13: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

13

What about RailSys?• RailSys is used to provide the ‘operations tick in the box’ for any scheme

• Provides a very powerful visualisation of a timetable

• Can be used to identify detailed train path routeing and permits detailed event scenario modelling

• It does not do PPM

• Of note for engineers; the complexity within the model can vary (even if the model is compliant to NR Opns Build Ver6)

• Simple models are normally optimistic

• trains may exhibit movement behaviour which the driver / signaller might not be able to emulate in real life

Page 14: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

14

Capacity Modelling

Existing Layout Proposed Layout

Thameslink KO2 – The need for ATO Crossrail – Scheme Performance Assessment

ERTMS – Braking Curve Reading – Capacity Utilisation Index

Page 15: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

Date 00.00.00 Presentation title to go here 15

Scheme Performance Assessment

Report

Scheme Model

Technical Headway

Junction Margin

Technical Platform

Reoccupation

Journey Times

Sectional Running Times

Rules Of The Plan (ROTP)

Calculation Database

Signalled Infrastructure

Train Service Specification

Rolling Stock Performance

Professional Driving Policy

Signalling Controls

Capacity Utilisation

Model Build SPAR Build

Capacity Utilisation

Timetabled Model

Additional Timetable /

Infrastructure

OSLO Support

Scheme Performance Assessment

Report

Scheme Model

Technical Headway

Junction Margin

Technical Platform

Reoccupation

Journey Times

Sectional Running Times

Rules Of The Plan (ROTP)

Calculation Database

Signalled Infrastructure

Train Service Specification

Rolling Stock Performance

Professional Driving Policy

Signalling Controls

Capacity Utilisation

Model Build SPAR Build

Capacity Utilisation

Timetabled Model

Additional Timetable /

Infrastructure

OSLO Support

SPA Process

Page 16: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

16

Key contacts

Specialist within Network Rail

Nigel Best – TRAIL, RAILSYS, RAM, FMECAClare Waller – TimetableMaya Petkova – EMCMark Burstow – Wheel / rail dynamicsCaroline Lowe – Climate+ Asset specialist

GaugingPowerSignallingTelecomsLevel Crossings

Page 17: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

17

The people, The process applied,

The systems used

Section 1 What is SE

Section 2Intro to SE Teams

Section 3GRIP, P Approval & Acceptance

Section 4System Integration

Section 5Building Blocks

Section 6Requirements

System Design Handbook

Links work only in Presentation Mode

Page 18: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

18

PSE – Building Blocks (guidance)(Links work in Presentation Mode)

Junction Evaluation + Presentation

Terminal Stations

Line Speed & Journey Time Improvements + Presentation

Consideration for Gradients / Curves + Presentation

Layout Development Workshops

PRS user guide

Light Rail + Presentation

Rail Maintenance Depots

Introduction to Building Blocks

PSE Schemes Resource estimating

Route Integration

Application of Standard Designs

Passenger Capacity

SystemSafety

TimetableRobustness

SystemReliability

Life Cycle Cost

SystemMaintenance

ElectrificationCapacity

SignallingCapacity

LayoutCapacity

SystemCapability

Undertaking a Pre Grip Evaluation

Freight Distribution Depots

Main Line Stabling Sidings

Generic Train InfrastructureInterface Specification +Presentation

Introduction To Station Design

Equality Act 2002 (DDA)

Page 19: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

19

Operators MMI

Cab DMI

EVCTrainborne GSM-

R data radioBalise readerOdometry

Trainborne

JRU

Balise

TracksideGSM-R

FTN

Interface to tractionand braking

Trainborne GSM-R voice radio

Signallers interface panel orVDU including train describer

CCTV level crossingsupervision

FTN

Operators RBC interface

Linesidetelephones

Signallers operational voicecomms MMI

FTN

Public Switched TelephoneNetwork

BTS

Handportable

Voice calllogger

Business systems and train planning including passenger information systems

SMART/TRUST/CCF

Automatic train managementsystems e.g ARS

Driver

Trackworker

Technician

Signaller

Controller

Operational Rules

PossessionMangement

Operational Rules

PossessionMangement

Signallers GSM-Rvoice interface

Train control system -indoor equipment

Signalling System Interlocking RBC

TechniciansInterlocking data logger

RBC datalogger

Outdoor train controlsystem equipment

FTN FTN

PointsTrain

detectionLevel

crossings

Othertracksidecontrolled

objects

Level crossingCCTV

Units likely to be be co-located

BSC

MSC

FTN

FTN

FTN

ERTMS Train Control System Operational Architecture - basicarrangement

Typical System Level Railway Functional Block Diagram (FBD)

Page 20: 1 Developing the MBSE Approach Tony Ramanathan Principal Engineer Network Rail

20

DESIGN forRELIABILITY

Modify System Configuration

Use alternative Asset types

Control Key Processes

Introduce Condition Monitoring

Enhance Maintenance

Improve Operational Plans

DESIGN forRELIABILITY

Modify System Configuration

Use alternative Asset types

Control Key Processes

Introduce Condition Monitoring

Enhance Maintenance

Improve Operational Plans

System Diagrams

FMS / TRUST Data

Reliability Data Hdbk

Route FMECA (Tech. & Ops)

Design for Reliability

Cause & EffectWorkshops:Engineering

Maintenance Operations

TRAIL Model:Options Evaluation