Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

Similar presentations


Presentation on theme: "1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications."— Presentation transcript:

1 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications to Systems Engineering November 8–9

2 2 Thesis Application of a Model Based Systems Engineering method can contribute to the implementation of an effective risk management program because…

3 3 Agenda Systems Engineering Objective Systems Engineering Challenge Essential Elements of a Model Based Systems Engineering Method MBSE Application Example Conclusion

4 4 Systems Engineerings Objective Translate user operational needs into an efficient and cost-effective system solution Capture the solution in a complete and coherent* system documentation** needed to design, integrate, test, operate and logistically support a system that fully meets user operational needs –Specification –Design –Test –Operation –Support –Other Supporting Work Products: Trade Studies, Analyses, Technical Reports, Meeting Minutes… * Coherent: Composed of mutually dependent parts; making a logical whole; consistent; as a coherent plan, argument, or discourse. Webster Dictionary ** Also known as work products

5 5 Systems Engineerings Challenge Capture the solution in a complete and coherent system documentation needed to design, integrate, test, operate and logistically support a system… Systems Engineering Processes

6 6 Systems Engineerings Challenge System requirements, design data, and information relevant to a wide variety of engineering, technical and domain disciplines –Totality of requirements in the thousands (possibly tens of thousands); Often changing, sometimes well into design –Dozens (possibly hundreds) of scientists, specialists, engineers, designers, testers, manufacturers…, from multiple & diverse technical disciplines –Customers, operators, maintainers, suppliers… with great domain expertise, little engineering expertise (and vice versa) –Should tie together into a unified whole –Should always be traceable to User Operational Needs Hundreds to thousands of components employing a wide variety of technologies manufactured throughout the country, possibly the world (ex. International Space Station) Never ending issues and risks associated at varying development levels that span a wide range of technical and domain expertise

7 7 Application of a MBSE Method to Partially Address the Challenge Systems Engineering Processes Model Based Systems Engineering Method supports

8 8 Essential Elements of a MBSE Method 1.Use of models as the central and unifying element to the development of a system* 2.Application across SE processes 3.Application down and up development levels 4.Application throughout system lifecycle 5.Use of computerized SE tools to support the method * …model-based [systems] engineering is about elevating models in the engineering process to a central and governing role in the specification, design, integration, validation, and operation of a system. Estefan, J.A., Survey of Model Based Systems Engineering Methodologies, INCOSE MBSE Focus Group ( http://syseng.omg.org/MBSE_Methodology_Survey_RevA.pdf)

9 9 1. Models as Central and Unifying Element Well defined, unambiguous language/notation, understood by all stakeholders, to describe and analyze the system Multiple system views to fully communicate system requirements and design –Requirements, Behavioral, Structure, Performance, Data, Managerial… –Integrated/Traceable; Complimentary; Consistent…non contradictory Underlying structure (or schema) to define model elements, attributes and relationships – Information Model Executability Models are the primary means of communication with clients, builders, and users; models are the language of the architect. The Art of Systems Architecting, Maier, M., Rechtin, E., CRC Press, 2002

10 10 Multiple System Views to Communicate Requirements & Design* Physical Hierarchy (System Structure) Physical Block Diagram (System Interconnection) Requirements Hierarchy (System Traceability) *Views produced by CORE Verification Requirements Operations & Logical/Functional (System Behavior)

11 11 Integrated! allocated to functional I/O implemented by trace to verified by Additional Views used as required to communicate other relevant system characteristics

12 12 Information Model Example* * Partial View of CORE Schema Risk causes Organization assigned to Program Activity resolved by Document documented by causes basis of performed by Component built from Interface joined to Function decomposed by Requirement refined by causes results in Verification Requirement verified by causes Verification Event fulfilled by

13 13 Information Model Example* * Partial View of CORE Schema Issue generates Organization assigned to Program Activity resolved by Document documented by generates basis of performed by Component built from Interface joined to Function decomposed by Requirement refined by generates Verification Requirement verified by generates Verification Event fulfilled by results in

14 14 * Trade-off Studies, Risk Management, Interface Management, Configuration Management… 2. Application Across SE Processes Requirements Models Behavioral Models Physical Models Assessment Results Requirements Analysis Functional Analysis Design/Synthesis Assessment Systems Engineering Process Model System Analysis & Control* To Next Development Level...... Safety Analysis Human Factors RAM Analysis Logistic Analysis EMI Analysis …

15 15 3. Application Down & Up Development Phases Decomposition & Design Integration & Verification System Design Product Design Subsystem Design Component Design HW Fab & Assembly; SW Code Part & CSU Verification Component Integration & Verification Subsystem Integration & Verification Product Integration & Verification System Integration & Verification Verification Requirements Verification Results Verification Requirements Verification Results Verification Requirements Verification Results Verification Requirements Verification Results Concept Operational Test Validation Requirements Validation Results

16 16 4. Application Throughout Acquisition Lifecycle Concept Refinement SyS Prod 3 Prod 2Prod 1 … Advanced Development Engineering Design Integration & Evaluation Production Operation & Support Increasing Model Complexity Sys Prod 3Prod 2Prod 1 Subsys 3.1Subsys 1.2 Subsys 1.1 Subsys 3.2 … … … Sys Prod 3Prod 2Prod 1 Subsys 3.1Subsys 1.2 Subsys 1.1 Subsys 3.2 … … … Comp 3.1.1Comp 1.1.2 Comp 1.1.1 Comp 3.1.2 … … … Sys Prod 3Prod 2Prod 1 Subsys 3.1Subsys 1.2Subsys 3.2 … … … Comp 3.1.1Comp 1.1.2Comp 3.1.2.a … … Comp 3.1.3 Subsys 1.1 Comp 1.1.1

17 17 System Development History Maintained Accumulated System Data & Information (History) Concept Refinement Advanced Development Engineering Design Integration & Evaluation Production Operation & Support Sys Prod 3Prod 2Prod 1 Subsys 3.1Subsys 1.2Subsys 3.2 … … … Comp 3.1.1Comp 1.1.2Comp 3.1.2.a … … Comp 3.1.3 Subsys 1.1 Comp 1.1.1

18 18 5. Use of Computerized SE Tools to Support the MBSE Method Modeling –Support the modeling language and schema; produce the needed system views –Maintain horizontal and vertical traceability Data Management –Single, central repository to manage all related system data and information Document Generation –Automated generation of formal documentation & work products (drawn from central model repository) System/Segment Specification (SSS); Interface Requirements Specification (IRS); Test & Evaluation Plan (TEP); Software Requirements Specification (SRS)... Integral to the SE Environment to support the MBSE method See Survey of Model Based Systems Engineering Methodologies (http://syseng.omg.org/MBSE_Methodology_Survey_RevA.pdf) for a discussion of commercial tools available that could be used to support MBSE method applicationhttp://syseng.omg.org/MBSE_Methodology_Survey_RevA.pdf

19 19 MBSE Application Example

20 20 Waste Management System (WMS) System Mission* - Accept, transport, & dispose of hazardous material in a manner that protects health, safety and the environment; and merits public confidence System Concept Interface between Waste Production Sites & Disposal System Receive and dispose of hazardous material Transport hazardous material from Waste Generation Sites to Disposal System WMS Transportation System Waste Acceptance System Disposal System *Documented in WMS Requirements Document

21 21 WMS Concept of Operations Maintenance Facility Disposal System Waste Generation Site Operations Center Unloaded waste containers Loaded waste containers Unloaded waste containers* Equipment flow Information flow *Transportation modes include rail, truck, barge; possibly a combination of all three depending upon OS location

22 22 Transportation System Concept Model Maintenance Facility Disposal Facility Ops Waste Generation Site Ops Operations Center Existing Infrastructure utilizes maintains coordinates/ controls Waste xports loaded containers to stores generates coordinates/ controls Transportation System Components Disposal Facility xports unloaded containers to Waste Generation Site Waste Container Rail or Truck Equipment Transport Equip carries contains

23 23 WMS Transportation System Development Phase

24 24 System Model Views * All views produced by the CORE SE Tool

25 25 System Requirements (sample) The system shall be capable of: –Accepting and receiving 400 tons of waste in 1 st year of operations –Accepting and receiving 3800 tons in 2 nd year of operations –… Shall be capable of accommodating a range of waste storage and transportation technologies Shall comply with the applicable provisions of: –Legislation –Code of Federal Regulations (CFR) –EPA Standards –DoT Regulations –Association of American Railroads (AAR) Regs –…

26 26 Requirements Model Development The WMS shall be capable of receiving waste, mostly by rail, at the system operating conditions and receipt rates specified in… The Transportation System shall have the capability to store (TBD)% of the waste container inventory. The WMS shall comply with the waste material transportation practices documented in the … The Transportation System shall have the capability to store (TBD)% of the rolling stock inventory. The Transportation System shall be capable of voice communications with rail consists at all times throughout shipment operations.

27 27 System Behavior Model Development Transportation System Functional Context Diagram

28 28 Transportation System Functional Context Diagram System Behavior Model Development – Decomposition Perform Transportation System Operations Operate & Maintain Transportation System

29 29 System Behavior Model Development – Functional I/O Functional I/O Includes Data, Information, Material

30 30 Physical Model Development Transportation System Physical Context Diagram

31 31 Physical Model Development Transportation System Physical Hierarchy …

32 32 Functional Allocation Functions from Behavior Model Allocated to the Operations Center Subsystem … Subsystem

33 33 Subsystem … Requirements Traceability Requirements from Requirements Model Trace to Operations Center Functions

34 34 Structural Model Development – Interconnection Diagram Functional I/O Items from Behavior Model Transferred by Interface Links Operations Center

35 35 System Specification *Document generated by Computerized SE tool (CORE), drawing data from Central Repository SYSTEM SPECIFICATION FOR THE Transportation System Prepared For: Prepared By: System Performance Specification Documents Requirements*

36 36 Conclusion Application of a Model Based Systems Engineering methodology can contribute to the implementation of an effective Risk Management program because: –Models can effectively communicate system requirements and design detail to all disciplines, at all system levels; Simultaneously accessible to all team members (IPTs, special study groups, analysis teams, etc.) (identification) Executable models allow analysis of system behavior (assessment and analysis) –Risk documentation products - identified risks, assessment results, mitigation plans etc. – can become an integral part of the system models, maintained in central repository (management) –Risk documentation products can be automatically generated from tools supporting SE environment drawing model data from central repository (management) MBSE methodology allows Risk Management to become an integral part of the overall system development effort, throughout all development phases/levels, throughout the system lifecycle (management)

37 37 Questions

38 38 Backup

39 39 Other Model Based Initiatives (you may have heard of) Model Driven Engineering (MDE) Model Driven Architecture (MDA) 1,2 Model Driven Development (MDD) 1,2 Model Based Application Development 1 Model Based Programming 1 Object Oriented Systems Engineering Method (OOSEM) using SySML 1 Rational Unified Process for Systems Engineering (RUP SE) 3 1. Object Management Group (OMG) trademarks (http://www.omg.org/legal/tm_list.htm)http://www.omg.org/legal/tm_list.htm 2. MDA & MDD are actually implementations of MDE 3. IBM Rational trademark How do these differ from MBSE? or MBE or MDSD


Download ppt "1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications."

Similar presentations


Ads by Google