Model-Based System of Systems Engineering (MBSoSE) Workshop by Tonex
Duration: 2 Days | Format: In-Person / Virtual / Hybrid
Level: Intermediate to Advanced
Credential: Certificate of Completion (Optional)
This hands-on workshop equips systems engineers, architects, and program integrators with practical skills to model and manage System of Systems (SoS) using Model-Based Systems Engineering (MBSE) methodologies. It covers architecture modeling, data exchange, interoperability, emergent behavior, and mission assurance using tools such as SysML, DoDAF, UAF, and frameworks like ISO/IEC/IEEE 21839 and 15288.
Learning Objectives
By the end of this workshop, participants will be able to:
- Define and characterize SoS structures, behaviors, and lifecycle phases.
- Apply MBSE techniques to model SoS architectures, interfaces, and dependencies.
- Use SysML/UAF to represent capabilities, mission threads, and operational scenarios.
- Manage complexity across federated, directed, collaborative, and virtual SoS.
- Identify emergent behavior, resilience challenges, and risk mitigation strategies.
- Support digital engineering transformation for multi-domain SoS programs.
- Integrate SoS engineering with enterprise and mission objectives.
Target Audience:
- Systems Engineers and Architects
- Enterprise Architects and Digital Engineers
- Acquisition Managers and Program Integrators
- Mission Analysts and Warfighter Engineers
- Technical Leads in Defense, Aerospace, Civil Systems
- MBSE/MBSoSE Tool Users (Cameo, Enterprise Architect, Rhapsody, etc.)
Workshop Agenda:
Day 1 – Foundations of System of Systems Engineering + Modeling
Module 1: Introduction to System of Systems Engineering (SoSE)
- What is a System of Systems?
- Characteristics: operational independence, evolutionary development, emergent behavior
- Types of SoS: directed, acknowledged, collaborative, virtual
- Standards: ISO/IEC/IEEE 21839, 15288, DoD DAG SoS Appendix
Module 2: SoSE Lifecycle and Mission Engineering
- SoS architecture lifecycle phases
- Mapping stakeholders, capabilities, and objectives
- SoS vs single-system engineering
- Mission engineering and CONOPS integration
Module 3: MBSE for SoS
- Why model-based?
- SysML/UAF/DoDAF views for SoS
- Linking operational, functional, and physical architecture
- Tools and repositories (Cameo, Rhapsody, Sparx, etc.)
Module 4: SoS Architecture Modeling
- High-level capability modeling across systems
- Interoperability and interfaces
- Mission thread development and allocation
- Behavioral modeling: activity, sequence, state machine
Day 2 – SoS Integration, Emergent Behavior, and Digital Engineering
Module 5: Managing Emergence and Interoperability
- Emergent properties and SoS failure modes
- Synchronization, timing, and interface coordination
- Technical authority and integration contracts
- Risk and reliability in SoS contexts
Module 6: Model Integration & Data Federation
- Use of digital twins and digital threads in SoS
- Cross-system traceability (requirements, interfaces, performance)
- MBSE to support Joint All-Domain Command and Control (JADC2)
- Role of standards: OSLC, XMI, and XML schemas
Module 7: Tools and Practices for SoS MBSE
- Toolchains for SoS modeling and simulation
- Federation and co-simulation practices (e.g., HLA, FMI)
- Model configuration, versioning, and governance
- Metrics and KPIs for SoS model quality
Module 8: Workshop Exercise & Wrap-Up
- Case scenario: modeling an SoS for multi-domain operations (e.g., maritime ISR + space comms + ground C2)
- Teams define SoS architecture, model behavior, and analyze emergent outcomes
- Group debrief and lessons learned
Workshop Tools & Templates
- SysML/UAF modeling templates
- SoS capability mapping worksheets
- Emergence risk log template
- Interface definition and dependency matrix
- Use case scenario: Joint ISR & Fires SoS
- Digital engineering thread diagram template