Anthony Springall

1
04E-SIW-088 Progress Reporton NATO Standards
Development for Maritime Simulation June 2004
Anthony Springall UK Defence Procurement
Agency Dr. David Hyland Detica Richard Reading
VisiTech, Ltd. David Spilling SEA Ltd.
NATO Naval Armaments Group 6 Sub-Group 61
Virtual Ships
2004 European Simulation Interoperability Workshop
2
Background

• NATO Naval Group 6 on Ship Design
• Specialist Team on Simulation Based Design and
  Virtual Prototyping (ST-SBDVP)
• ANEP 61 released in February 2001
• NATO Interoperability Re-Use Study (NIREUS)
  deployed 13-nation technology demonstrator in
  October 2001
• Sub-Group 61 Virtual Ships
• NATO Standards for SBDVP applied to ship
  acquisition
• Build upon Specialist Team results
• NIREUS testbed for exercising potential standards
  (e.g., interoperability of product information
  models and runtime simulations)
• MOU to enable formal implementation of critical
  experiments and technology developments

3
NATO Standards for Virtual Ships

• Introduction
• The ship design communities of NATO and other
  nations require a standard agreement (STANAG) to
  facilitate improved access to simulation
  technology during early phases of ship
  acquisition
• Aim
• The aim of the STANAG is to promote the use of
  simulation modules and to standardise the
  interfaces to those modules
• Objectives
• To achieve more cost efficient reuse and
  interoperability of simulation modules

4
Standard Agreement

• Participating Nations agree that the STANAG shall
  govern the development and implementation of
  interoperable and re-usable maritime simulations
• The STANAG describes the procedures and mechanics
  of how to achieve maritime simulation
  interoperability and re-use in a consistent,
  effective and expeditious manner

7 May 2004
5
STANAG Development Work Breakdown
STANAG Virtual Ship Technologies
Compilation
Data Management
Modelling Simulation
Process

• Scope
• Purpose
• Audience
• Data management
• Modelling simulation
• Process
• Lessons learned
• Drafting
• Review revision

Candidate technologies / standards
Candidate technologies / standards
Candidate technologies / standards
Standard Rules

• Standard Simulation Components
• Examples from NIREUS,
• Scenario list,

Use of Simulation within Procurement Processes

• Standard Data Model
• Standards for common names and hierarchies

• Process Guidance
• Workflow control
• FEDEP SEDEP
• Configuration management
• Fidelity granularity
• Design iteration
• Design of experiments

• Standard Support Tools
• Visualisation
• Data logging
• Scenario editor
• RTI
• Security

Information Access Software Interface Standard
6
Proposed STANAG
HLA
HLA
STANAG
Virtual Ship andEnvironment Standard
Development Process
Components FOMs Repository Template
Standard Simulation Architecture
7
STANAG Components Annex A

• Virtual Ship and environment standard development
  process
• Data management in context of ship design process
• Process activities specific to development of
  virtual maritime environment
• Described as overlay to FEDEP
• Calls for FEDEP cycles to be described as
  components within ship design process workflows

7 May 2004
8
Virtual Ship Data Layers
Runtime Infrastructure
Runtime
Simulation Federate
Simulation Federate
Simulation Federate
Simulation Federate
Simulation DataObject
Simulation DataObject
Simulation DataObject
Simulation DataObject
Simulation DataObject
Pre-Runtime
Model Data Objects
PhenomenologicalModel
Ship ProductModel
Air SystemProduct Model
9
Modellers Simulationists Worldviews
Simulationists View
Simulation Data Interface
All the answers are made here I realize the
virtual ship
Simulation Component/Federate
Simulation Component/Federate
Simulation Component/Federate
Simulation Component/Federate
Product Modellers View
Static Data
Static Data
Static Data

Tool

• Vague cloud of data sources for representing
  physical systems and phenomena
• Not much is expected in the way of central or
  common product model(s)

Product Model
Tool
Tool
All the data lives here I am the virtual ship

• Vague cloud of simulation tools, that the
  Product Model allows to borrow data from the
  virtual ship
• Not much is expected back in the way of new data

10
Ship Design and Simulation Workflows
Simulation supported ship design process Workflow
view
7 May 2004
11
STANAG Components Annex B

• Standard simulation architecture and standards
• Adopt IEEE 1516 reference and leverage existing
  IEEE and NATO documentation
• Define and adopt standard NG6 Reference FOM
• RPR FOM 2.0 plus virtual ship extensions
• Define and adopt standard NG6 Federation
  Agreement
• RPR FOM GRIM 2.0 plus virtual ship extensions

12
STANAG Components Annex C

• Repository and template for federation components
  and FOMs
• Dynamic aspects of STANAG achieved through
  Repository
• Repository and template design
• Governance structure and management process

13
Federation Component Template General
Information
7 May 2004
14
Federation Component Template Data Context
Execution
15
Processes
Ship Acquisition Process
Evolution
SG/61 STANAG Process
Proposed Common Components/FOMs
STANAG Repository
Components FOMs Repository
STANAG Reference Components FOMS Repository
Periodic Review
Mature Acceptance, Interest, Use
16
SG/61 Timetable

• STANAG draft by July 04 (Edition 0)
• Draft for internal SG/61 review completed April
  04
• STANAG first edition for ratification by Dec 05
• MOU ready for signature end March 04
• ANEP update end 2006
• Advisory, recommended practices that augment
  STANAG
• Possible NIAG study 2005-2006

17
Summary

• NATO SG61 Virtual Ships STANAG development
  underway
• First draft completed April 2004
• STANAG components
• Virtual Ship and environment standard process
• Standard simulation architecture and sim
  standards
• Repository and template for federation components
  and FOMs
• NG6/SG61 will continue to raise the level of
  awareness of the benefits, costs, and risks of
  MS for surface ship systems acquisition