How MBSE is used in Rail

Transcription

1 How MBSE is used in Rail INCOSE International Workshop Jan 2014 Dr. Mike Brownsword Atkins

2 Overview Introduction Company overview Using MBSE Process definition Requirements Architecture V&V/assurance Delivering MBSE 2

3 Introduction Model-based Systems Engineer - Rail London Underground, Network Rail, HSL Zuid, MARTA. Atkins Consultant Requirements, Architecture, Information, Architecture Frameworks, Process definition. 3

4 Company overview Atkins 2014

5 At a glance Atkins is one of the world s leading design, engineering and project management consultancies. We have the depth and breadth of expertise to respond to the most technically challenging and time-critical infrastructure projects and the urgent transition to a low carbon economy. In 2013 Atkins is celebrated 75 years in business. 5

6 Our clients Revenue by client type Key Transport clients include: Network Rail Texas Dept of Transportation UK Highways Agency Florida Department of Transportation Transport for London Trafikverket BAM Group (UK) Banedanmark (RailDenmark) New York City Transit MTR Corporation Ltd Etihad Rail Company PJSC Jernbaneverket (Rail Norway) Ministry of Municipality & Urban Planning (MMUP) Qatar Crossrail MARTA Public sector: local government 28% Public sector: national government 21% Regulated 16% Private sector 35% 6

7 Crossrail United Kingdom Detailed design of twin bored tunnels, and design and specification Tottenham Court Road and Custom House stations and Plumstead depot Image courtesy of Crossrail

8 Birmingham New Street Station United Kingdom Lead consultant, design management and urban planning Image courtesy of Network Rail

9 European Rail Traffic Management System Denmark Client advisor for the design, implementation and testing of ERTMS on the entire Danish rail network (3200km)

10 Using MBSE Process Modelling Atkins 2014

11 Process definition Aim Identify the right process Understand the information and activities to be delivered Ensure consistency between activities and information Focus on Activities not documents Approach Take multiple views of a process Combine/contrast views to provide consistency. Be pragmatic regarding rigour and maturity of information. Expect repetition of processes, not one shot. 11

12 Process definition class Process Content View Process List Process Requirements Planning Requirements Elicitation Requirements Development act Requirements Dev elopment Requirements Manager Requirements Engineer Requirements Approver ActivityInitial class Information View - Requirements Elicitation Define purpose of this dev elopment (Requirements Development::) Context Source Documentation Perform analysis (Requirements Development::) constrains is source of Prepare for the rev iew of requirements, ADCs, relationships and SAs (Requirements Development::) Ensure traceability relationships are established and verifiable (Requirements Development::) Analysis completed [No] to defined purpose? [Yes] Formalise requirements, ADCs, relationships and SAs (Requirements Development::) Requirements Management Processes, Guidance and Examples Document Requirements Management Plan Scenario guides elicitation of defines methodology for eliciting aids Requirements Elicitation Output Standards are a source of Project Documentation Requirements Elicitation Stakeholders aids elicitation of Prev ious project documentation Checklists and aides for elicitation Rev iew the requirements, ADCs, relationships and SAs (Requirements Development::) [No] Approval gained from all reviewers? [Yes] Requirements reports Requirements specifications Assumptions, Dependencies and Cav eats Requirements Trace documents Stores and enables management of Repository Approv e requirements, ADCs, relationships and SAs (Requirements Development::) Elicitation Record ActivityFinal Process Flow Process Information 12

13 Process definition Benefits Cross domain application Enables balance between generic process and specific technique. Relevant to people with differing levels of expertise. Consistent activities and information 13

14 Using MBSE Requirements Modelling Atkins 2014

15 Requirements Analysis Aim Ensure requirements have a home Understand the essence of the requirements To support the development of the whole set of requirements not just individual statements. Understand the problem and whether it is being solved. Differentiate between different types of requirement (Stakeholder vs System) Approach Provide relationships between requirements within a set Clearly separate requirements into contexts 15

16 Where to start? Simulate Retain Migrate between Link to 5.11 Maintenance Informs future service plan and scheduling of future service plans Receiv e Transport Planning Service plans have an element of recovery built into them links to performance Administer the Service Plan Modify Schedule Deploy Current «Constrain» «Constrain» «Constrain» «Constrain» Planned Maintenance Both condition based maintenance and re-active maintenance change in planned availability may not constrain mode of operation Long term Passenger Demand Emergency comms Amend Emergency Serv ices Receiv e feedback Duty staff Link to org P1+P2 Auto Ability for RCO to Interv ene «Constrain» P2 Auto/manual Recov er Current Service Plan Need to clarify diff between current and active with RH P4 Link to 5.11 Maintenance> asset availability Continue serv ice Identify best plan deliv ery possible service Link to reactive maintenance P3 Allow communication External Deliv er Serv ice Plan Internal Passenger Deliv er the Serv ice Ability for RCO to Interv ene Identify cause/nature Staff outside of DTP, Alien Railway Prov ide info on Service Delivery Changes in serv ice «Constrain» Determine duration Determine impact Links to schedules and planing service Dynamically prov ide Statically prov ide Prov ision of routine information Modes of operation Railway States Recov ery and maintain Serv ice Plan Note CGL is this the "current" service plan? If so, remove "Current" use case. Direct Unattended Remote P4 Location of People Understand State of Line Link to 5.11 Maintenance> Minimum Ops disruption Automated action Effect states differently Understand asset condition P1 P2 Predict Serv ice leav ing P1 (and inform) P3 Prev ent/mitigate the effects of anything other than P1 Link to amend service plan in short term Identifying Complexity 16

17 The Tail of the Brontosaurus 17

18 Comparing contexts Safety Officer's Requirements Context Systems Engineer's Requirements Context Ensure Safety Ensure Safety of Equipment Ensure Safety of People «Stakeholder» Escapologist Demonstrate Usefulness of Modelling Engineer System Show Systems Approach Analyse Context Analyse System «Stakeholder» Systems Engineer «Stakeholder» Safety Officer «Stakeholder» Marketing Escaplologist's Requirements Context Marketing Requirements Context Look Great Don't Die Create leads Promote Services «Stakeholder» Film-maker «extend» «extend» Demonstrate Usefulness of Modelling Be interesting Escape «extend»... Promote tools «Stakeholder» Assistant Set-up Get-out «extend» Make People Sweat «Stakeholder» Audience Promote SysML 18

19 The Tail of the Brontosaurus Regulation Legislation Manadatory standards Admin Serv ice Plan Deliv er Current Serv ice Plan Standards Policy Recov er Serv ice Plan comply with standards Constraint relationship Deliv er the serv ice Understnad State of the Line Non- Functional Requirement Allow Communication State of Serv ice operate the railway serv ice Manage Information Monitor Data ability for 24/7 Maintain Asset Minimum Operations Disruption Feedback Information Process Data Plan Maintenance Manage Maintenance Locations Control Assets Access Assets A Asset Maintenance Regime Functional Requirement 19

20 Requirements Analysis Benefits Enables well structured requirement sets to be developed Enables visualisation of requirements including relationships between functional and non-functional. Model-based view validates text Improves communication and engagement with stakeholders Enables conflict resolution Enables levelling of requirements 20

21 Using MBSE Architecture Modelling Atkins 2014

22 Architecture Aim Facilitate development of and capture design information To answer specific stakeholder questions/issues/concerns, i.e. How do we migrate? Deliver facts aligned with fuzzy pictures Ensure it isn t just another railway Understand boundaries and interfaces Ensure structure and function are consistent Approach Deliver information in the best way for the stakeholder to understand. Provide multiple representations of information where appropriate. Ensure consistency between information. 22

23 A Many Views make lite work System Context Traceability Station Infrastructure (Fabric) Tenants Emergency Serv ices General public (non passenger) Org Internal Group Services Neighbour Local Conditions External Gov ernance Railway Line Passenger Alien Railway Gov ernance Interaction Utility Local Conditions Track Train Control System Comms Network Alien Ops Alien Asset par [Instruct] Determine Train Movement Required() Alien Maintenance move(effort, direction) alt move(traction) Brake(Brake) Determines Instruction has been executed() [Maintain Safety] Determine Movement is safe() Regulation Legislation Manadatory standards [Adhesion] calculate slip/slide() Standards Asset Reliability Asset Maintenance Function Asset Av ailability Availability Service Target comply with standards Capacity Targets Policy Admin Serv ice Plan Deliv er Current Service Plan Recov er Service Plan Adhesion() Adhesion() calculate Adhesion(WSP) Command and control «Interface» Control - Train Rolling Stock Organisation Performance Env ironmental Performance Operate Asset provide performance Serv ice Targets operate the railway serv ice Understnad Deliver the service State of the Line Allow operate/access Communication station Monitor Data Control System communicates via Comms Infrastructure communicates via controls defines kinematic envelope of heats Train State of Serv ice ability for 24/7 Plan Minimum Operations Disruption Maintain Asset Asset Maintenance Regime Manage Information Feedback Information Process Data communicates via Infrastructure Platform Edge equipment resides in Civil Infrastructure Power Distribution powers Reactiv e Understand Asset Planned Maintenance Locations Control of Assets Access Assets maybe in communicates via Station Equipment Infrastructure Cooling monitors, runs on Depot maybe in Track Requirements Interfaces 23

24 Architecture Benefits Enables confidence in design Facilitates focused technical discussion. Enables re-use of information Provides consistency Supports demonstration of performance 24

25 Using MBSE V&V/Assurance Atkins 2014

26 V&V/Assurance Aims Ensure all requirements are met Reduce manual application of traceability Increase consistency Approach Provide rich traceability Integrate Requirements and Architecture 26

27 Tracing distributed systems Requirement Minimise environmental impact type a) Requirement W10 structure gauge type b) traces to traces to Each of these links must be independently verified for full technical assurance Requirement No impact piling near Mr X s house type c) traces to Physical OLE Structure GW/00/01 Physical OLE Production Unit GW/00 Physical OLE Structure GW/00/02 Physical OLE Structure GW/01/01 Physical OLE Production Unit GW/01 27

28 Multi-level applicability of requirements Requirement Type a) requirement All elements traces to Physical T00 Generic design element is a Requirement Type b) requirement All elements of type traces to Physical T03 OLE Structure is a Requirement Type c) requirement location specific traces to Physical GW/00/01 structure 28

29 Inferred applicability Requirement Type b) requirement All elements of type traces to Physical T03 OLE Structure Inferred trace is a Inference: If Signal Head traces to Requirement 1 and colour light signal is a type of Signal Head then a colour light signal traces to Requirement 1 Physical GW/00/01 structure 29

30 V&V/Assurance Benefit Integrates Architecture and Requirements Enables re-use and normalisation information Provides consistency of traceability and approach Delivery of information to conform with stakeholder need 30

31 Delivering MBSE Information Modelling Atkins 2014

32 Information Modelling Aim Understand the information required Understand the relationship between the information Understand how it all fits together Enable successful delivery to stakeholders. Approach Organise information for the business Use the businesses terminology 32

33 What are the Views Defines the requirements of the element. Discipline View Set Defines the hierarchy of the elements. Technical View Asset Breakdown View shows layout of Technical View Physical View Functional View Functional Needs View Interface View defines need for Asset Agent Shows relationships between defines functions of considers transition to Functional View Asset functionality View Technical View Asset Migration View considers transition to Defines the relationships between the elements as pictures, tables and matrices Atkins 2014 Shows what the element does and the information flow between elements. The Context of a set of information 33

34 What is the Information The problem the asset has to solve Requirement Satisfaction The element in the system Functional allocation The things the element does technical requirement defines need for Asset is performed by Function relates to Requirement traceability Asset decomposition communicates information to Asset Interaction Interface Functional decomposition The way the information is passed Atkins

35 Information Modelling Benefit Enables consistent information definition Enables Impact analysis Assessment of information maturity Enables consistency of approach Brings together process, Architecture, Requirements and Assurance 35

36 Questions 36