Based Reference FOM and a System-of - Simulation Interoperability ...

1 downloads 0 Views 1MB Size Report
Common Design Principles, A Component-. Based Reference FOM and a. System-of-Systems Federation Development. Process. Dr. Judith S. Dahmann. MITRE.
Creating System Integration Simulation Environments: Common Design Principles, A ComponentBased Reference FOM and a System-of-Systems Federation Development Process Dr. Judith S. Dahmann MITRE Gunnar Öhlund Swedish Defence Materiel Administration Björn Löfstrand, Staffan Löf Pitch Dr. Gary Eiserman, Jayne Talbott Virtual Technology Corporation 2003 Euro SIW

Background





Development, deployment, and employment of forces today is a coalition enterprise • Agile and effective interoperability is key to responding quickly to crisis situations • Individual national C4ISR and force development and employment stategies pose obstacles to effective coalition operations M&S supported by international commercial standards (e.g. IEEE 1516 HLA) provides the technical means to create collaborative environments that can be used to ensure that systems deployed by partner nations can effectively work together

2003 Euro SIW

Background





This paper presents the results of a collaborative effort between teams from Sweden and the United States • Our goal was to create a set of supporting capabilities that facilitate the development of simulation based environments to address systems interoperability issues The technical issues that face development of System Interoperability Simulation Environments (SISE) are the same whether the systems come from different nations or different organizations within a single nation

2003 Euro SIW

SISE Design Package





This effort produced a initial SISE “Design Package” • Systems Interoperability Reference FOM • SISE Design Principles Document • SISE Development Process The package is intended to collect the lessons learned by the Swedish and US teams during previous federation development efforts and to organize this information into a structured process that can be used by new federations

2003 Euro SIW

SISE Design Package



Systems Interoperability Reference FOM • Serves as a reference and starting point for creation of a FOM for a particular federation • Based on lessons learned from a number of Swedish and US federations • Reduces the time and effort required for FOM development • Aids in more efficient reuse of components from prior federations

2003 Euro SIW

SISE Design Package





SISE Design Principles • Designing a federation involves much more than just developing a FOM. The SISE team has documented an initial set of design issues that should be considered during the development of a SISE SISE Development Process • Process for applying the reference FOM and design issues to the design of a SISE • An overlay on the first three steps of the standard FEDEP process

2003 Euro SIW

SISE Development Process



The SISE process focuses on the first three steps of the standard 7 step FEDEP Process

7 step FEDEP Process 1 Define Federation Objectives

2 Perform Conceptual Analyses

3 Design Federation

4 Develop Federation

5 Plan, Integrate and Test Federation

6 Execute Federation and Prepare Outputs

7 Analyze Data and Prepare Results

Depict User Problem Space Federation System Engineering

2003 Euro SIW

Federation Development, Execution and Analysis

SISE Development Process





The first three steps of the FEDEP are supported by two sequential and overlapping activities • Depicting the User Problem Space • Federation System Engineering These two activities revolve around two different sets of people and expertise. This separation enables • Better use of scarce experts in the User Domain • More effective technical engineering of the federation

2003 Euro SIW

Depict the User Problem Space •

Sequentially develop and refine the description of the problem space independent of its eventual federation implementation

Define federation objective(s)

Statement of Objectives including • Question to be addressed • Analysis to be supported by federation data • Metrics to be applied in the analysis 2003 Euro SIW

Develop first order problem depiction

Develop detailed problem depiction

Level 1 Depiction

Level 2 Depiction

including • Systems • Interactions • Analysis/metrics • Vignettes

including • System elements • federate options • Element/activity sequences • Critical scenario elements • Data generation collection points • End-to-end walk-through

Level 1 Problem Depiction

• • • • •

What systems are to be included What actions the systems will take Vignettes What data will be generated by the federation • How it will be used in the analysis • What metrics will be applied Level 1 is typically recorded as a graphic depiction of the systems and their interactions • Accompanied by notes and definitions

2003 Euro SIW

Level 1 Example IFF

Data link Detection

Red Air (Targets)

Ownship Nav

2003 Euro SIW

Blue Ground

Level 2 Problem Depiction

• • • • •

Level 1 depiction is extended to provide the information needed to engineer the federation More detailed descriptions of each system • Focus on the elements that are directly relevant to the federation objectives Sequence diagrams of the state changes and interactions among systems and subsystems Details of the scenario(s) that are necessary for the federation to address its objectives The data needed for analysis will be defined in detail and located within the level 2 depiction • Which interactions will provide what data • Specific data elements required for each interaction

2003 Euro SIW

Level 2 Problem Depiction

• • •

The Level 2 depiction will produce an end-to-end detailed storyboard of the federation and its dynamics Level 2 analysis also includes identification of candidate federates Level 2 is not completed until it is possible to completely map the data needed for analysis to specific system characteristics and/or interactions among system elements

2003 Euro SIW

Level 2 Example: Local Track Formation Nav Source

Mission Computer (MC)

MC Data Link

MC Radar

Targets

Other Blue Radar

Other Blue Data Link

Other Blue Mission Computer

Other Blue Platform

1.1 Initialize Radar 1.2 Control Radar 1.3 Reports Status

1.4 Emits RF Energy 1.6 Platform Position

1.5 Reflects RF Energy 1.7 Reports Detection 1.8 Senses IFF from Blue Aircraft for local Track creation and ID 1.9 IFF Information

1.10 Forms Track

2003 Euro SIW

Transmission through tactical network (including environment) Transmission through Air Inter-system Communication

Federation Systems Engineering



Technical design of the federation begins with the Level 2 analysis results and any candidate federates User Problem Space Depiction Level 2 Depiction • System elements • federate options • Element/Activity sequences • Critical scenario elements • Data generation collection points

Federation System Engineering • Select Federates • Create Federation Sequence Diagrams

• Identify FOM elements 2003 Euro SIW

• Apply Reference FOM and Guidance • Apply Design Principles

• FOM

• Federation Agreements

Federation System Engineering

• • • • •

Identify the full set of required federates Map element/activity sequence information to federation specific sequence diagrams Map sequence diagram data exchanges to FOM elements • Clarifies the scope and level of fidelity Map sequence diagrams and FOM elements to federates • Identifies shortfalls in existing federates Apply the reference FOM and design guidance documentation

2003 Euro SIW

Federation Design Principles

• •

Beyond the FOM, there are design decisions that must be made for any federation The SISE guidance document groups these decisions into a number of categories

• • • • •



Representation issues Information exchange issues Federation and Scenario Management Data Collection and Analysis Requirements Performance

In each category, a set of related sub-issues is discussed

• • •

The issue and its importance are defined Different potential solutions are discussed If the authors have a recommended solution it is given

2003 Euro SIW

Reference FOM

• •



Today FOM development is often a collaborative ‘bottom up’ process, which can be labor intensive, time consuming, and frustrating An alternative is to create and use a Reference FOM that can be used as an independent starting point for developing federations



Design tool for developing a FOM tailored to the specific needs of a federation



It is a starting point, NOT a ‘one size fits all’ solution

The accompanying SISE design guidance document explains the organization and contents of the reference FOM

• •

Includes recommendations for extending the FOM Helps ensure that the tailoring is done in a consistent and thorough manner

2003 Euro SIW

Reference FOM



Use of a reference FOM provides several benefits • Reduced time to develop a federation • Federations independently developed using the same reference FOM will require less effort to interoperate • Design documents, analysis products, and simulation components designed in one federation are more likely to be reusable in others developed from the same reference FOM • Experiences from successive federations can be fed back into the reference FOM and design document to further improve the process

2003 Euro SIW



The Systems Interoperability Reference FOM Object Classes

• • •

Model persistent things Reflect real world distinctions and interfaces Separate federation management from the things being simulated

2003 Euro SIW



The Systems Interoperability Reference FOM Interaction Classes

• • • •

Model messages and transient events Reflect real world distinctions and interfaces Allow for non real-world message passing between federates Separate federation management from the things being simulated

2003 Euro SIW

Summary



• •

The Sweden/US collaborative effort developed an initial set of products and capabilities that support the efficient development of HLA federations to deal with system of systems interoperability issues • A structured process overlay to the FEDEP • A set of design principles • A reference FOM Several federations have successfully adopted these products and processes The authors hope to be able to feed the lessons learned from these and other efforts back into the SISE products to continue their evolution

2003 Euro SIW