Based Reference FOM and a System-of - Simulation Interoperability ...
Recommend Documents
Feb 4, 2013 - article (e.g. in Word or Tex form) to their personal website or ...... used to check the simulation status via the GET channel to URI. ''. ..... [35] C. Seo, B. Zeigler, Automating the DEVS modeling and simulation interface to web ...
Mark Ryan, Doug Hill, and Dennis McGrath. Institute for Security Technology Studies. Dartmouth College .... forensic methods of comparing Linux honeypot.
Optimierung der chemischen Einflüsse bei der mechanischen Politur von Glas.
Abschlussbericht zum Forschungsvorhaben in Zusammenarbeit mit der.
Apr 9, 2018 - Aspermont Managing Director Alex Kent said: âWe sold our 60% share ... Gustavo Vieira (Chief Information
Keywords:Decision Support System, Production Schedulling, Herb, GTMMP;. 1. Introduction ... This is in line with business policies that enable efficient ... Batavia, Benneth, Labe, Liao, Nigam,&Oh, 2002), AT&T(Ambs, Cwilich, Deng, Houck,.
Mar 24, 2006 - hts in th is d ocu m en. t a nd in th e in. - fo rm atio n co nta in ed th ere in . R ep .... No. Revision Page. A. 5/47. Our Ref. Doc. No. BBSE951112-BNA ... Name (id) of the Induction Machine AC Train, must start with a letter. ... r
Toolkit) is a custom environment in which multiple ... data are often incompatible with simulation software. ... specific data sharing, a custom-designed building.
Orlando, FL, 38826. USA ... significant technical progress has been made, cultural and policy issues ..... governing the Verification, Validation, and Accreditation.
MIL STD 2525C icon or NATO APP-6C; (2) command relationships (parent and ... Experience to date in development of BML indicates that the language will ...
line telephone call; and. 3. Discussion, where interested parties subscribe to an automated Email program that relays th
This paper leverages the work of the NCES program and the XMSF community to
..... OSD(NII), given to the M&S COI on 16 Nov, 2004. .... described various
concepts of the Similarly, a question in the Service section reads: ..... Report",
Simulation
DATA-CENTRIC SIMULATION INTEROPERABILITY USING THE DeST. SIMULATION ..... Inadequate Interoperability in the U.S. Capital. Facilities Industry.
9. 4.1.3.7. Planned Compliance Testing. ...... Discussion, where interested parties subscribe to an automated Email prog
Abstractâ Weather predictions are used in various sectors viz. agriculture, air traffic, ..... Knowledge Systems Laboratory Technical Report KSL-01-05, vol. 32( 1) ...
Space Center, MS 39529 USA â (robert.ryan, slawomir.blonski)@ssc.nasa.gov c Information Systems Directorate, Lockheed Martin Space Operations â Stennis ...
Supply Chain Execution (SCE), Advanced Planning Scheduling system ... (business/manufacturing), and using different concepts, different modeling rules and concerns. ERP. APS. CRM .... In the HLA, each simulation or other software system.
SMN deployment, and monitoring.5. Manufacturing ..... simulation and monitoring tools. We integrated these ... tion on the Nagios open source mon- itoring tool ...
4.3.2 Development of a phytoplankton index for ecological assessment ............51 ...... 2001. Spring. 2002. Summer. 2002. Summer. 2003. Acrow. CE. 18/04/02. 04/09/02. Ahalia ...... on a division of the index into 5 evenly spaced classes. Figure 4.
(business/manufacturing), and using different concepts, different modeling rules and concerns. .... In the HLA, each simulation or other software system is run as ...
Apr 4, 2001 - whatsoever for loss or damage occasioned or claimed to have been occasioned, ... the National Development Plan 2000-2006. ... Lough Rea Anglers associations, the Newport, Ballinahinch, ...... EQR for Lake X. Scale may range from high st
ARCHITECTURES. A software reference architecture describes a software sys- ... tion, manufacturing intelligence, and analytics for imple- menting open ...
An empirical study of a global automotive brand. Arbeitspapier ..... degree of CS might be influenced by previous contacts with FMC's retailers, especially if the first contact ...... international bekannte Grade wie Bachelor und Master erwer- ben.
of matching service descriptions in order to find suitable available services for a .... a Service Message Ontology (SMO), that provides knowledge on the ...
1 Introduction. In recent years, the area of e-commerce has become an important domain for enterprises. ... different enterprises in the business-to-business (B2B) field. Modern ... vendor's system expects it to be in the BMEcat format. ... the diffe
Based Reference FOM and a System-of - Simulation Interoperability ...
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
• 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