Model-Based Concept Development

Transcription

1 INNOVATIONS IN ENGINEERING Model-Based Concept Development Brian London Draper Laboratory (617) NDIA Systems Engineering Conference 22 October 2012 San Diego, CA

2 Agenda Problem Statement Model-Based Engineering Overview Model-Based Concept Development Framework Description Implementation Benefits and Challenges 2

3 Design Assurance Why is this Required? Tomorrow Today Time NEED: To reduce the cost and time required to develop and verify systems by effectively generating, capturing, organizing, sharing, and evaluating information using interconnected electronic models across the development lifecycle 3

4 Traditional Design Practices Software Design Controls Design Electrical Design Packaging Design 4

5 MBE Integrates Design and Verification Execution Simulation Prelim. Architectural Design System Requirements Architectural Design Prelim. Software Design Prelim. Packaging Design Prelim. Electrical Design Software Design Packaging Design Electrical Design 5

6 Concept Development Methodology Define Problem Identify Problem Define Architecture Evaluate Options Identify Possible Solutions 6

7 Model-Based Problem Definition ibd [SysML Internal Block] Design Model [System Context Pictured] User Storage and Transportation Environment Define System Boundary Develop Use Cases UAV Develop Requirements Operational Environment Prioritize Requirements Sponsor req [Package] MOEs [Actors] Attributes - Composition - Heat Signature Range Define Stakeholders Create Project Glossary TRADOC Commander «express» «express» «express» notes The UAV shall have a range of 60 km. Time To Target Identify notes Verification notes Method The UAV shall Enemy reach the target position within 20 minutes. Availability Req. Docs. The UAV shall support day and night operation. «express» Endurance «express» notes The UAV shall have a minimum loiter time of 60 minutes. Ground Assets Developers Maintainer Transportability Storage and Transportation Env ironment «express» notes The UAVs shall be carried with (infantry) battle units. 7

8 Defining System Architectures sd 1_Basic_Path composite bdd [Package] structure Subsystems QuickLook [UAV Subsystems] act Launch Data FastLook :User :UAV «flowport» Launcher I/O 1..* :UAV Define Behavior 1.The User power the UAV() UAV Develop Activity Diagrams 5.The User «flowport» places the UAV Camera in/on a launcher() Start Lift Supplier Thrust Supplier Recovery Element 2.The UAV performs a self test and report the status() «flowport» GPS Camera : GB The User provides configurations (including MET data, payload, mission, etc) and inializes GPS : FastLook Avionics «flowport» Telemetry & Commands :User 4.The UAV :UAV acknowledges :GPS 0..* 0..* reception of 1 data() 1..* 1..* Containment Develop State Diagrams Power the UAV stm [Package] System Behav ior [System Behav ior] 7.The User launches UAV () Prov ide configurations Initial (including Off MET data, payload, mission, etc) and :Tail Fin Assembly inializes GPS On «flowport» GPS Antenna «flowport» Control Actuator Perform a self test and report the status 6.The UAV indicates readiness for launch() Acknowledge reception of data Power Removed Power is Received Develop «flowport» Commands Sequence Diagrams Observ e Set Status EntryPoint «datatype» Self Test Results «datatype» Initialization Data «datatype» Status «flowport» Setter :GPS Communications Subsystem «flowport» Data : C-Band LOS Data Link «flowport» Antenna «flowport» Communication Antenna :Launcher Surveillance Supplier * Steering ActivityInitial Mechanism 0..1 Controls Subsystem Allocate Behavior to 1 Structure GN&C Subsystem 1..2 Power Subsystem Support UAV Launch UAV Trigger Detected :UAV Checkout Pace the UAV in/on a launcher Observe Status «datatype» Status Nav Error Detected Define Components Navigation Solution Obtained (Blocks) Launch Command [UAV Set] Initiate UAV Launch Guidance End Else Initialization Nav Error Detected Search Command Received Acquire GPS «continuous» Define Structure Tracking [GPS Acquired] Indicate readiness for launch Track Command Received Search «datatype» GPS P(Y) Code, «datatype» GPS M-code Broadcast Position Data Define Connections ActivityFinal (IBD) Define Data/ Object Exchanged 8

9 Effective Collaboration Information is captured once - then shared and reused by all stakeholders 9

10 Link Attribute Across Domains bdd [Package] FastLook [FastLook] UAV +Launched By FastLook «interface» 155mm Howitzer 2 Wing Inflatable Wing ::Lift Supplier + Lift coefficient :newton + Width :meters + Mass :kilograms = Length :centimeter = Power Subsystem2.0 Surveillance :kilograms Supplier Communications Subsystem QL Power Subsystem 20.0 :centimeters EO/IR C-Band LOS Data Link GN&C Subsystem QuickLook Av ionics Surveillance Supplier Laser Designator constraints ::Lift Supplier { Mass } { Length } Power Distributor QuickLook PDU Battery QL-BTRY-22 Autopilot {0..1} Accelerometer {0..*} Gyroscope {0..*} GPS Antenna {0..*} 10

11 Why Model-Based Engineering? Benefits Error checking/ design verification Evaluate model completeness Determine impact of changes Improve decision making Unambiguous, precise descriptions Reduce effort duplication Challenges Manual linking Tool/ model integration Data configuration/ ownership Requires new skillsets New tool/ infrastructure costs Benefits lead to costs and schedule reductions Challenges can be overcome with planning, technology advancements 11

12 Summary Model-Based Design Enables Cost and Schedule Reductions Reduce errors by capturing data once reusing across design Verify designs earlier by enforcing consistency Simplify tracing between requirements and design Enables early assessments and detailed analyses Obtain a better change impact assessment 12

13 Backup

14 Assess Change Impacts Verify Requirements Automatically Identify Design Margin or Issues Quickly Assess the Impact of a Change 14 Phoenix Integration