05FSIW020 NATO Standards for Virtual Ships September 2005

1
05F-SIW-020NATO Standards for Virtual
ShipsSeptember 2005

• Dr. Klaas Jan de KrakerTNO, The Netherlands
• Dr. John DuncanChairman, SG61 Defence
  Procurement Agency, UK
• Ernst-Wichard BuddeIABG, Germany
• Rich ReadingVisiTech, Ltd., USA

NATO Naval Armaments Group 6 Sub-Group 61
Virtual Ships
2005 Fall Simulation Interoperability Workshop
2
SG/61 on Virtual Ships History

• In 1997 the NATO Naval Armaments Group
  established a Specialist Team on Simulation Based
  Design and Virtual Prototyping under Naval Group
  6 (Ship Design) to develop guidance (ANEP 61) on
  the use of simulation to support ship design
• The 13-nation HLA-based NIREUS technology
  demonstrator was created under leadership of this
  team

In 2001 a follow-on committee Sub-Group 61 was
established with the task of formulating
technical standards (STANAG) to enable the
delivery of Virtual Ship technology to reduced
timescale, risk, and cost
3
SG/61 Virtual Ship Simulations
NATO Naval Armaments Group (NNAG)
NG/1 Above Water Warfare
NG/2 Undersea Warfare
NG/3 Mines And MCM
NG/4 Maritime Air
NG/6 Ship Design
NG/5 Tactical Control And Data Handling
SWG/4 Electronic Warfare
SG 61 Virtual Ships
SG 4 Electrical Power
SG 7 Ship Survivability
SWG/12 Maritime Environmental Protection
ST Seaway Mobility
SWG/10 Naval Electromagnetic Environment
PG35 Maritime UAV Systems
4
Virtual Ship Becomes Reality
Ship motion
Ship control
Signature
Visualisation
Motion forward prediction
Navigation
Vulnerability
Run Time Infrastructure
Gun
Command Control
ECM
Missile
External Systems
Torpedo
Radar
Sonar
The Virtual Ship may be described as an
Architecture and a Digital Infrastructure where
simulation models representing Naval systems and
functions can work together
5
Interoperability Requirements

• Requirements can only be met if existing and new
  simulation tools can be applied in many
  applications (re-usability)
• To achieve re-usability, we need interoperability
  of simulation components
• Non-runtime interoperability can be achieved
  through use of shared databases, Product Data
  Management (PDM) systems
• Runtime interoperability requires time-managed
  communication between simulations running on
  different computer hardware, with different
  operating systems and different compiler languages

6
Virtual Ship Architecture
Complementary to continued development and use of
open standards for simulation
7
Virtual Ship Rules

• Integration with Ship Design Process
• (VS1) The Ship Design Process shall be considered
  the User of the Virtual Ship and provide the
  User Need Statement
• (VS2) The Ship Design Process shall provide
  access to Ship Design information required by the
  Virtual Ship and the Virtual Ship shall establish
  means to access Ship Design data
• (VS3) The Virtual Ship shall provide simulation
  results for use in the Ship Design Process
• VS Reference FOM usage
• (VS4) The Virtual Ship Reference FOM (VS R-FOM)
  shall be adopted where possible
• The Virtual Ship Repository shall be consulted
  before new federations are developed. Any
  deviations from the VSR FOM for a Virtual Ship
  federation implementation shall be formally
  documented and submitted to the Virtual Ship
  Repository.

8
Virtual Ship Rules

• VS Repository usage
• (VS5) The Virtual Ship Repository shall be
  consulted before new simulations are developed.
  Wherever possible, Virtual Ship applications
  shall use the Virtual Ship data structures. New
  or modified data structures shall be submitted to
  the Virtual Ship Repository.
• (VS7) The Virtual Ship Repository shall be
  consulted before Maritime Natural Environment
  representations are developed. Wherever possible,
  Virtual Ship federations shall implement Virtual
  Ship MNE representations. New or modified MNE
  representations shall be submitted to the Virtual
  Ship Repository.
• (VS8) The Virtual Ship Repository shall be
  consulted before new scenarios are developed.
  Wherever possible, Virtual Ship federations shall
  use scenarios documented in the Virtual Ship
  Repository. New or modified scenarios shall be
  submitted to the Virtual Ship Repository.

9
Virtual Ship Development Process

• Founded on the HLA FEDEP
• Additional overlays that outline
• Product Data Management
• Maritime Natural Environment
• Verification, Validation, and Accreditation (VVA)

10
Design Data Access
ProductData Management System
HLA RTI
11
VS Development ProcessUsage of STANAG Component
Usage of the STANAG component
Feedback to STANAG repository
12
Virtual Ship Reference FOM

• The VIRTUAL SHIP R-FOM comprises
• Real Time Platform Reference Federation Object
  Model (RPR FOM) v2.0
• VIRTUAL SHIP RPR FOM extensions
• VIRTUAL SHIP Federation Agreement(VS extensions
  to the RPR-FOM GRIM)
• Any deviations from the Virtual Ship R-FOM for a
  Virtual Ship federation implementation shall be
  formally documented

13
Virtual Ship Repository

• Simulation components
• Federation Object Models
• Data structures
• Scenarios
• Maritime natural environment

Web-based repository with specific templates for
each repository item
14
Virtual Ship Web Page (1)
15
Virtual Ship Web Page (2)
16
PROCESS Governance
Ship Design Process
Evolution
Virtual Ship Process
Design Supporting Simulations
Proposed Common Components FOMs
STANAG ReferenceComponents FOMs
VS STANAG Template
VSEG
Mature Acceptance, Interest, Use
Components FOMs Repository
17
Way Forward

• Virtual Ships STANAG Study Draft released for
  national review in May 2005
• Prototype Virtual Ships Repository website under
  development
• NATO Industry Advisory Group Study initiated
• Considers Virtual Ships in context of a
  hypothetical ship acquisition
• STANAG planned to enter NATO ratification process
  in 2006 once national and NIAG inputs are
  incorporated