NORTH ATLANTIC TREATY SCIENCE AND TECHNOLOGY ORGANIZATION ORGANIZATION AC/323(MSG-086)TP/562 www.sto.nato.int STO TECHNICAL REPORT TR-MSG-086-Part-II Guideline on Scenario Development for (Distributed) Simulation Environments (Guide en vue du développement de scénario dans le cadre de simulation distribuée) Part of the Final Report of MSG-086. Published January 2015 Distribution and Availability on Back Cover NORTH ATLANTIC TREATY SCIENCE AND TECHNOLOGY ORGANIZATION ORGANIZATION AC/323(MSG-086)TP/562 www.sto.nato.int STO TECHNICAL REPORT TR-MSG-086-Part-II Guideline on Scenario Development for (Distributed) Simulation Environments (Guide en vue du développement de scénario dans le cadre de simulation distribuée) Part of the Final Report of MSG-086. The NATO Science and Technology Organization Science & Technology (S&T) in the NATO context is defined as the selective and rigorous generation and application of state-of-the-art, validated knowledge for defence and security purposes. S&T activities embrace scientific research, technology development, transition, application and field-testing, experimentation and a range of related scientific activities that include systems engineering, operational research and analysis, synthesis, integration and validation of knowledge derived through the scientific method. In NATO, S&T is addressed using different business models, namely a collaborative business model where NATO provides a forum where NATO Nations and partner Nations elect to use their national resources to define, conduct and promote cooperative research and information exchange, and secondly an in-house delivery business model where S&T activities are conducted in a NATO dedicated executive body, having its own personnel, capabilities and infrastructure. The mission of the NATO Science & Technology Organization (STO) is to help position the Nations’ and NATO’s S&T investments as a strategic enabler of the knowledge and technology advantage for the defence and security posture of NATO Nations and partner Nations, by conducting and promoting S&T activities that augment and leverage the capabilities and programmes of the Alliance, of the NATO Nations and the partner Nations, in support of NATO’s objectives, and contributing to NATO’s ability to enable and influence security and defence related capability development and threat mitigation in NATO Nations and partner Nations, in accordance with NATO policies. The total spectrum of this collaborative effort is addressed by six Technical Panels who manage a wide range of scientific research activities, a Group specialising in modelling and simulation, plus a Committee dedicated to supporting the information management needs of the organization. • AVT Applied Vehicle Technology Panel • HFM Human Factors and Medicine Panel • IST Information Systems Technology Panel • NMSG NATO Modelling and Simulation Group • SAS System Analysis and Studies Panel • SCI Systems Concepts and Integration Panel • SET Sensors and Electronics Technology Panel These Panels and Group are the power-house of the collaborative model and are made up of national representatives as well as recognised world-class scientists, engineers and information specialists. In addition to providing critical technical oversight, they also provide a communication link to military users and other NATO bodies. The scientific and technological work is carried out by Technical Teams, created under one or more of these eight bodies, for specific research activities which have a defined duration. These research activities can take a variety of forms, including Task Groups, Workshops, Symposia, Specialists’ Meetings, Lecture Series and Technical Courses. The content of this publication has been reproduced directly from material supplied by STO or the authors. Published January 2015 Copyright © STO/NATO 2015 All Rights Reserved ISBN 978-92-837-0201-2 Single copies of this publication or of a part of it may be made for individual use only by those organisations or individuals in NATO Nations defined by the limitation notice printed on the front cover. The approval of the STO Information Management Systems Branch is required for more than one copy to be made or an extract included in another publication. Requests to do so should be sent to the address on the back cover. ii STO-TR-MSG-086-Part-II Table of Contents Page List of Figures vii List of Tables viii List of Acronyms ix MSG-086 Membership List x Executive Summary and Synthèse ES-1 Chapter 1 – Introduction 1-1 1.1 Motivation 1-1 1.2 Purpose 1-1 1.3 Scope 1-1 1.4 Intended Audience 1-2 1.5 Document Outline 1-2 Chapter 2 – Scenarios in Distributed Simulation Environments 2-1 2.1 Definition “Scenario” 2-1 2.2 Scenario Development Process 2-1 2.2.1 Operational Scenario 2-3 2.2.2 Conceptual Scenario 2-5 2.2.2.1 Relation of Conceptual Scenario and Operational Scenario 2-6 2.2.2.2 Relation of Conceptual Scenario and Conceptual Model 2-6 2.2.3 Executable Scenario 2-7 2.3 Auxiliary Terms 2-10 2.3.1 Vignettes 2-10 2.3.2 Scenario Variants 2-10 2.3.3 MEL/MIL 2-10 Chapter 3 – Content of a Scenario 3-1 3.1 Preliminary Remarks 3-1 3.2 Initial State 3-2 3.2.1 Objects and Units 3-2 3.2.2 Forces and Force Structure 3-3 3.2.3 Geography 3-3 3.2.4 Date/Time 3-4 3.2.5 Surrounding Conditions 3-4 3.2.6 Rules of Engagement 3-4 STO-TR-MSG-086-Part-II iii 3.3 Course of Events 3-4 3.3.1 Communication Events 3-5 3.3.2 Interaction Events 3-5 3.3.3 State Change Events 3-5 3.3.4 Environmental Events 3-5 3.4 Termination Conditions 3-5 3.5 Reuse in the Scenario Development Process 3-5 3.5.1 Components Regarding Initial State of a Scenario 3-6 3.5.2 Components Regarding Course of Events of a Scenario 3-6 3.5.3 Components Regarding Termination Conditions of a Scenario 3-8 Chapter 4 – Maturity Levels of Scenario Specification 4-1 4.1 Level 0 – No Written Scenario Specification 4-1 4.2 Level 1 – Non-Standardized Scenario Specification 4-2 4.3 Level 2 – Standardized Scenario Specification 4-2 4.4 Level 3 – Formal Scenario Specification 4-3 4.5 Relation of Maturity Levels to Scenario Types 4-3 Chapter 5 – Standards and Tools for Scenario Specification 5-1 5.1 Standards and Tools for Operational Scenarios 5-2 5.1.1 DSEEP 5-2 5.1.2 NATO Comprehensive Operations Planning Directive 5-2 5.1.3 General Purpose Software 5-2 5.1.4 Joint C3 Information Exchange Data Model (JC3IEDM) 5-2 5.1.5 Allied Data Publication 3 (ADatP-3) 5-3 5.1.6 Coalition-Battle Management Language (C-BML) 5-3 5.2 Standards and Tools for Conceptual Scenarios 5-3 5.2.1 NATO Architecture Framework (NAF) 5-3 5.2.2 Unified Modeling Language (UML) 5-3 5.2.3 Systems Modelling Language (SysML) 5-4 5.2.4 Base Object Models (BOMs) 5-4 5.2.5 VEVA Process Model 5-4 5.2.6 Joint Exercise Management Module (JEMM) 5-4 5.3 Standards and Tools for Executable Scenarios 5-5 5.3.1 Military Scenario Definition Language (MSDL) 5-5 5.3.2 Order of Battle Service (OBS) 5-5 Chapter 6 – References 6-1 Annex A – Scenario Specification Using the NATO Architecture Framework A-1 A.1 Rationale A-1 A.2 Architectures in the Scenario Development Process A-2 A.3 NAF Templates for Conceptual Scenarios A-2 iv STO-TR-MSG-086-Part-II A.3.1 NOV Operational View A-3 A.3.2 NSV System View A-4 A.3.3 Other Views and Templates A-6 Annex B – Scenario Specification Using Base Object Models B-1 B.1 Overview of the BOM Standard B-1 B.1.1 Model Identification B-1 B.1.2 Conceptual Model Definition B-1 B.1.3 Object Model Definition B-2 B.1.4 Model Mapping B-2 B.1.5 Documentation of BOMs B-2 B.2 Evaluation B-3 B.2.1 Positive Experiences B-3 B.2.2 Negative Experiences B-3 B.2.3 Ideas for Improving the BOM Standard B-3 Annex C – Example Scenario “Air Defence” C-1 C.1 Description of the Operational Scenario C-1 C.2 Textual Description of the Conceptual Scenario C-2 C.2.1 Initial State C-2 C.2.1.1 Units C-2 C.2.1.2 Forces and Force Structure C-2 C.2.1.3 Geography C-3 C.2.1.4 Surrounding Conditions C-3 C.2.1.5 Rules of Engagement C-3 C.2.2 Course of Events C-3 C.2.2.1 Communication Events C-3 C.2.2.2 Interaction Events C-3 C.2.3 Termination Conditions C-4 C.3 Using BOMS for Scenario Specification C-4 C.3.1 Model Identification C-4 C.3.2 Conceptual Model Definition C-5 C.3.2.1 Entity Types C-5 C.3.2.2 Pattern of Interplay C-6 C.3.2.3 State Machines C-8 C.3.3 Object Model Definition and Model Mapping C-11 Annex D – Example Scenario “Close Air Support” D-1 D.1 Operational Scenario D-1 D.2 Conceptual Scenario D-1 D.2.1 Initial State D-1 D.2.1.1 F-16 Flight D-1 D.2.1.2 FAC Team D-2 D.2.1.3 Infantry Unit D-3 STO-TR-MSG-086-Part-II v D.2.1.4 Insurgents D-3 D.2.1.5 Geography, Date/Time D-3 D.2.1.6 Surrounding Conditions D-3 D.2.1.7 Rules of Engagement D-3 D.2.2 Course of Action D-3 D.2.2.1 Communication Events D-3 D.2.2.2 Interaction Events D-3 D.2.2.3 Environmental Events D-4 D.2.3 Termination Criteria D-5 D.3 Discussion D-5 vi STO-TR-MSG-086-Part-II List of Figures Figure Page Figure 2-1 Types of Scenarios in the Simulation Environment Engineering Process 2-2 Figure 2-2 Role of Operational Scenarios in the Early Steps of a Simulation Environment 2-3 Engineering Process Figure 2-3 Relation of Conceptual Scenario and Conceptual Model Regarding Entity Classes 2-7 and Entities and Example Figure 2-4 Allocation of Entities to Federates of a Simulation Environment for Different 2-8 Executions of the Simulation Environment Figure 2-5 Allocation of Values to Attributes of Entities to be Represented by the Different 2-9 Federates for Different Simulation Environment Executions Figure 3-1 Refinement and Extension of the Content of a Scenario Along the Scenario 3-1 Development Process Figure 3-2 Relationship between Vignettes and Vignette Configurations for Composing a 3-7 Scenario Figure A-1 NOV-5 Operational Activity Tree for Scenario Example from Annex C A-4 Figure A-2 NOV-2 Operational Nodes for Scenario Example from Annex C A-4 Figure A-3 NSV-2 System Communication Template for Scenario Example from Annex C A-6 Figure B-1 Example Specification of State Machine as a Table and as a Diagram B-2 Figure C-1 Area of Interest C-1 Figure C-2 Overview of Pattern of Interplay in Example Scenario “Air Defence” C-7 Figure C-3 State Machine of ManPAD Commander C-8 Figure C-4 State Machine of ManPAD Observer C-9 Figure C-5 State Machine of ManPAD Gunner C-9 Figure C-6 State Machine of Target C-10 Figure C-7 State Machine of Missile C-11 Figure D-1 Actors D-2 Figure D-2 Two Roles in the FAC Team D-2 Figure D-3 Scenario Interactions Between Different Actors D-4 STO-TR-MSG-086-Part-II vii List of Tables Table Page Table 2-1 Types of Scenarios and Their Relation to DSEEP Activities 2-2 Table 2-2 Example of Scenario Variants 2-10 Table 3-1 Example Information Set for Describing Units and Objects 3-3 Table 4-1 Maturity Levels of Scenario Specification 4-1 Table 4-2 Relation of Maturity Levels to the Different Types of Scenarios 4-4 Table 5-1 Standards and Tools for Scenario Specification 5-1 Table A-1 Usability of NAF Operational View Templates for the Description of Scenarios A-3 Table A-2 Usability of NAF System View Templates for the Description of Scenarios A-5 Table A-3 NSV-5 Operational Activities to System Function Traceability Matrix for A-5 Scenario Example from Annex C viii STO-TR-MSG-086-Part-II