NG6SG61

1
NATO STANDARDS FOR VIRTUAL SHIPS
Anthony Springall Defence Procurement
Agency SG61 U.K. Representative Dr. David
Hyland Detica SG61 U.K. Industry
Representative Richard Reading VisiTech
Ltd. SG61 U.S. Industry Representative
NG6/SG-61
NATO Naval Armaments Group 6 Sub-Group 61
Virtual Ships
2003 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)

3
NATO STANDARDS FOR VIRTUAL SHIPS

• Three primary tracks to STANAG development
• Data modelling and management
• Includes product models, common object models,
  and taxonomies
• Simulation
• Includes architectures (e.g., HLA), common
  simulation components, and support tools
• Process
• Includes process guidance for development and use
  of simulation and data modelling (e.g., FEDEP
  SEDEP)
• Includes guidance on use of simulation within
  acquisition processes

4
STANAG DEVELOPMENTWORK BREAKDOWN
5
SIMULATION STANDARDISATION WORK BREAKDOWN
6
QUESTIONNAIRE

• Questionnaire distributed November 2002
• Ascertain what national interests were in STANAG
  topic areas
• Use information to
• direct STANAG development
• constrain scope
• develop SG/61 contacts
• Attempt to capture existing technology

7
QUESTIONNAIRE REVIEW

• Lack of consistent overview of simulation
• Physical simulations neglected
• Large number of stand alone simulation tools for
  specific application domains
• Preliminary findings
• Simulation technology lies both in
  industry/government
• Varies from nation to nation
• Poor awareness of simulation possibilities
  amongst government procurement personnel

8
SIMULATION CHALLENGES

• Awareness of technologies
• Current view of simulation
• 3D CAD walkthroughs
• Discrete problem specific tools
• Cost and perceived cost
• Timespan (want to access quickly)
• Processes crucial

9
SIMULATION BENEFITS OF APPROACH

• Reuse of simulation resources
• Only build problem specific components
• Reduction in lead times / risk
• Standardisation of interfaces
• Interoperability improved from common baseline
• Risk management for system integration improved
• Better VVA confidence
• Fidelity / limitations / assumptions / validity

10
ANALYSIS

• SG Exercise to define potentially baseline
  federations
• Previous knowledge/SG/61 information
• Set of constraints defined
• Distributed / generic
• Focussed on platform issues
• Domains where several organisations/nations need
  to participate
• List of known simulation scenarios compared
• Basic federation architectures postulated
• More specific scenarios can be developed from
  generic baseline

11
SIMULATION STRATEGY

• Looking at distributed simulations where there
  are behavioural interactions between
  bodies/systems
• High level view not necessarily technology
  dependent at this stage
• Problem domains can be rationalised down to about
  20 key federates
• Resulting generic baseline federations can then
  be extended to cover most desired scenarios

12
SIMULATION SUPPORT

• STANAG also needs to address the support tools
  and integration necessary to establish standard
  simulation framework architecture
• Visualisation
• Simulation management
• Data logging
• Interface to modelling area (data management)

13
BASELINE FEDERATES

• Ship
• Environment
• Other platforms
• Additional Ships
• Air vehicle
• Underwater bodies
• Other systems
• Cables/winches
• Handling systems
• Automated controllers

14
BASELINE FEDERATIONS AND USE CASE APPLICATIONS

• Ship-Ship
• Replenishment at Sea (two similar sized
  platforms)
• Ship-Small Craft, e.g., LPD/LCU (small platform
  and large platform)
• Ship-Air vehicle
• Manned HELO, UAV / Ship interoperability
• AV/Ship post touchdown
• NIREUS/Coupled Air Wake
• Ship-Ship Systems
• Equipment handling/operations
• Signature management
• Recoverability

15
FEDERATE DEVELOPMENT

• Federate overlap
• Different applications require additional
  functionality
• Current SG/61 exercise
• which federates exist?
• which may partially exist?
• Which need to be developed?
• Context problem domains
• Conceptual models
• Methodology for documentation

16
SG 61 STANAG DEVELOPMENT - FEDERATIONS
Standard Simulation Components for the Family of
Federations
17
REPLENISHMENT AT SEA USE CASE 1
Problem Space Determine the RAS Equipment
Specification for jackstay, inhaul and out-haul
winches. Assume the ships are able to maintain
course.
Ship
Air Vehicle
Other RAS Ship has same components
Speed/Course Controller
Ship Motion
Manoeuvring
Speed/Course Controller
AV Motion / Dynamics
Rotor Flow Field
Hydro. Flow Field
Radar IR Signature
Capture System
Wheel contact dynamics
Air Wake
Structure Pre / Post Damage
Systems Pre / Post Damage
Soft / Hard Kill System
Small Craft
Landing Aids
UAV Telemetry
Helo Capture Recovery
Speed/Course Controller
Ship Motion
Manoeuvring
Lift / Move Equipment
Sensors
Bridge Simulator
Environment
Wind/Sea State etc.
Flow Field Interaction
RAS - Cable Model and Inhaul / Outhaul Winches
etc.
18
REPLENISHMENT AT SEA USE CASE 3
Problem Space Determine the training and human
factors necessary to perform successful RAS.
Assume the ships are fully manoeuvring in the
seaway.
Ship
Air Vehicle
Other RAS Ship has same components
Speed/Course Controller
Ship Motion
Manoeuvring
Speed/Course Controller
AV Motion / Dynamics
Rotor Flow Field
Hydro. Flow Field
Radar IR Signature
Capture System
Wheel contact dynamics
Air Wake
Structure Pre / Post Damage
Systems Pre / Post Damage
Soft / Hard Kill System
Small Craft
Landing Aids
UAV Telemetry
Helo Capture Recovery
Speed/Course Controller
Ship Motion
Manoeuvring
Lift / Move Equipment
Sensors
Bridge Simulator
Environment
Wind/Sea State etc.
Flow Field Interaction
RAS - Cable Model
19
REPLENISHMENT AT SEA USE CASE 4
Problem Space Determine the limiting
operational constraints including the effects of
interaction between hydrodynamic pressure fields
of both vessels. Assume the ships are fully
manoeuvring in the seaway.
Ship
Air Vehicle
Other RAS Ship has same components
Speed/Course Controller
Ship Motion
Manoeuvring
Speed/Course Controller
AV Motion / Dynamics
Rotor Flow Field
Hydro. Flow Field
Radar IR Signature
Capture System
Wheel contact dynamics
Air Wake
Structure Pre / Post Damage
Systems Pre / Post Damage
Soft / Hard Kill System
Small Craft
Landing Aids
UAV Telemetry
Helo Capture Recovery
Speed/Course Controller
Ship Motion
Manoeuvring
Lift / Move Equipment
Sensors
Bridge Simulator
Environment
Wind/Sea State etc.
Flow Field Interaction
RAS - Cable Model
20
NIREUS LINKAGE

• NIREUS Framework role Technology demonstrator
  and exerciser of candidate standards
• Natural linkage through STANAG development work
  in federate area
• Define parameters
• Build federates
• Demonstrate
• MOU between nations to be signed Dec 2003
• Enables specific project work

21
NIREUS COMMON SIMULUATION FRAMEWORK - MUAV
APPLICATION
OPERATIONAL CONTEXT
SIMULATION SPACE
PROBLEM SPACE
complex system-of-systems
VisiTech-14-02-V014
22
ACQUISITION MS TOOLS REFERENCE FRAMEWORK
Wide Area Network
Product Information Models
CM database
Analysis Tools
Data Reduction
Integration Test Tools
Network Management Tools
FEDEP Tools
Local Area Network
Interoperating Platform or System Could be
deployed on the same or separate network
2003 European Simulation Interoperability Workshop
23
REUSABLE AND INTEROPERABLE FRAMEWORKS
24
SHIP-AIR VEHICLE INTEROPERABILITY USE CASE COMMON
FRAMEWORK
Ship Product Model
Geometry, performance data (e.g., motion), etc.
Design of Experiments Translator Layer
Take off Landing Performance Federation
Ship Representation
Federation Management Tool
scenario, tactics, operational limits
Simulation Data Out
HLA Run Time Infrastructure
Data requirements, performance measures
Data Collection Tools
Other Federates
Air Vehicle Represenation
Design of Experiments Translator Layer
Geometry, performance data, etc.
Air Vehicle Product Model
Performance data fed back for analysis, design
iteration, etc.
25
WAY FORWARD

• NG6/SG-61 will continue to raise the level of
  awareness of the benefits, costs, and risks of
  MS for surface ship systems acquisition
• STANAG development underway
• Common frameworks, such as NIREUS, should be
  exploited to enable
• multi-nation collaboration and interoperability
• cooperative simulation development that amplifies
  individual investments
• simulation re-use
• improved system designs
• important contributions to improved military
  operations