using model-based systems engineering for rig-level safety automation
TRANSCRIPT
SPE/IADC-173087-MS
Using Model-Based Systems Engineering for Rig-Level Safety Automation
David Hetherington
Asatte Press
Ford Vehicle vs High-Specification Jackup
Paper # • Paper Title • Presenter Name
Slide 2
Is a high-specification jackup really several orders of magnitude simpler than a Ford minivan?
Limitations of Document Approach
Paper # • Paper Title • Presenter Name
Slide 3
Requirements Requirements Requirements Requirements Requirements Requirements
Requirements Requirements
System Specification
System Specification
Sub-System Specification Sub-System Specification
Sub-System Specification Sub-System Specification
Sub-System Specification Sub-System Specification
Component Specification
Component Specification Component
Specification
Component Specification Component
Specification
Component Specification Component
Specification
Component Specification
Component Specification
Component Specification Component
Specification
Component Specification Component
Specification
Component Specification
Component Specification
Component Specification Component
Specification
Component Specification Component
Specification
Component Specification Component
Specification
Component Specification
CHANGE!!
Requirements Requirements
Once the first wave of specifications have been generated, changes are very painful. As such, specifications are never revised. Instead, an avalanche of “TQ”s (“technical queries”) ensues.
Model-Based Systems Engineering Approach
Paper # • Paper Title • Presenter Name
Slide 4
Structure
Requirements
Behavior
The “Model-Based Systems Engineering” approach uses a sophisticated model database to keep track of all of the complex interlocking relationships in the system.
Model Contains Large Number of Simple Views
Paper # • Paper Title • Presenter Name
Slide 5
Diagrams are simple. Only the detail relevant to one stakeholder is shown. Underneath, the model database ties it all together.
Model Describes System Structure
Paper # • Paper Title • Presenter Name
Slide 6
Arbitrarily complex system structures can be modeled..
Model Describes Behavior
Paper # • Paper Title • Presenter Name
Slide 7
Behaviors and interactions can be modeled in detail.
MBSE – The Single Version of the Truth
Paper # • Paper Title • Presenter Name
Slide 8
MBSE is NOT:•A replacement for CAD tools•A replacement for specialized mathematical simulation tools•A replacement for existing software development tools
MBSE is:•A method of keeping all the key interlocking project assumptions in one place•A method of avoiding the “Death by Technical Query Avalanche” syndrome•A solid approach to automating the production of specifications and plans…•…Which in turn makes it practical to update all of those documents on a predictable, regular basis•…and in turn keep all of the different teams “On the Same Page”
MBSE – Two Main Approaches
Slide 9
Paper # • Paper Title • Presenter Name
SysML (Systems Modeling Language)
DSL (Domain Specific Language)
Cross industry standard. Used by defense, aerospace,
automotive, railroads, medical device makers.
SPE DSATS working on a SysML model.
Multiple tool vendors. Very powerful. Steep learning curve.
Customized for your team. Tools are actually “tool
workbenches” Workbench makes a graphic tool
that works with the symbols and rules your team already uses.
Very easy for your team to learn. No standardization.
Which Approach is Right for my Organization?
Slide 10
Paper # • Paper Title • Presenter Name
Organizations that Might be Best Served with SysML
Organizations that Might be Best Served with a DSL
Very large team. Large powerful IT tools support
organization. Strong preference for established
industry standards. Prefer tools from leading large
software vendors. No programming experts in the
team. Willing to invest in signicant
training.
Small, autonomous team. No centralized IT support. Strong focus on meeting team
objectives. Not so concerned about interoperation with the industry.
Can allocate one team member with strong programming skills to be the Toolsmith and support the rest of the team.
No time for training. Tools must look intuitively familiar.
Acknowledgements / Thank You / Questions
Slide 11
• Project was with Athens Group
• For more information on Model-Based Systems Engineering refer to: INCOSE Systems Engineering Handbook Version 3.2.2ISBN 978-1-937076-02-3
• For more information on SysML refer to: SysML Distilled by Lenny Delligatti ISBN 978-0-321-92786-9
• For more information on Domain Specific Languages refer to: Domain Specific Modeling by Steven Kelly and Juha-Pekka Tolvanen ISBN 978-0-470-03666-2
• Other questions can be directed to: [email protected]