SYNTHETIC NATURAL ENVIRONMENT MODELING CONCEPTUAL REFERENCE MODEL

1
SYNTHETIC NATURAL ENVIRONMENT MODELING CONCEPTUAL
REFERENCE MODEL Guo Gang, Ph.D Huang
Kedi ggwyh_at_yahoo.com Military Simulation
Laboratory College of Mechaeronics Engineering
and Automation National University of Defense
Technology Changsha, Hunan, China, 410073
2003 European Simulation Interoperability
Workshop, 16-19 June 2003, Stockholm, Sweden
2
Presentation Outlines

• Backgrounds of Synthetic Natural Environment
  (SNE) Modeling
• Definition of Conceptual Reference Model (CRM)
• Why its needed, What it is and How it is formed
• SNE Rational CRM
• Diagram representation, Formalizations, as well
  as some technical considerations critical when
  concerning with realizations
• SNE Technical CRM
• The technical requirements and foundations that
  embrace the full spectrum of SNE and support the
  full scope of todays MS systems

3
Presentation Outlines

• SNE Operational CRM
• Using IDEF0 models to capture the pre-runtime
  data requirements and processes from a high
  conceptual level
• SNE Runtime CRM
• Establish a standard and reusable reference
  runtime system architecture or framework of
  environment federation with dynamic and total
  environment domain simulation capabilities
• Conclusions
• Some conclusions and considerations of further
  research works

4
Synthetic Natural Environment (SNE)

• SNE modeling and simulation
• Full SNE domain including terrain, ocean,
  atmosphere and space
• Full spectrum of environmental data including
  visual, infrared, radar and so on
• Full scope of MS community applications
  including training, analysis, test and experiment
• With the aims of interoperability, reuse,
  credibility and high simulation fidelity
• DMSO MSMP
• acquiring timely and authoritative natural
  environment representations
• Integrated Natural Environment (INE) program

5
SNE and Conceptual Reference Model (CRM)

• Difficulties in SNE modeling and simulation
• a complete representation of the total SNE
  domains
• a standard mechanism to exchange data
• polymorphic data representations to meet visual,
  radar, infrared and CGF requirements
• So, we need Conceptual Reference Model (CRM) to
• provide high level views from different aspects
  of the total SNE modeling and simulations
• define rational infrastructure, technical
  framework, operational concepts, application
  patterns as well as the principles, methods,
  technologies, processes, models and simulations
• communicate and understand

difficult and complicated
6
Conceptual Reference Model

• Definition of concept
• Concept is the abstract, denotation, delegation
  of the existence, entity, process and concretion
  instead of the detailed things or implementations
  themselves
• a mean to understand and communicate
• a denotation to represent some details or
  processes
• a method to classify and organize some
  hierarchies and structures
• also a blueprint to guide analysis, design and
  implementations or to gestate visions

7
Conceptual Reference Model

• SNE CRM
• a reference model that establishes, describes,
  organizes and standardizes the concepts from the
  rational, technical, operational and runtime
  aspects of the SNE modeling
• and thus captures a high level view for the
  purpose to abstract, understand, communicate,
  represent, organize and guide the system
  analysis, design and implementation

8
Why the Conceptual Reference Model

• To understand and communicate
• To capture the concepts of the SNE modeling and
  provide high level views
• To promote and facilitate high interoperability,
  reuse, credibility and fidelity
• To build up a reference framework and a blueprint
  for system develop

9
What and how the Conceptual Reference Model

• Complete, unambiguous, brief when design the CRM
• The whole CRM is composed of four parts with each
  according to one aspect
• the rational CRM rational basis
• the technical CRM technical requirements
• the operational CRM pre-runtime data process
• the runtime CRM runtime framework

These together provide a brief and complete
abstract of the SNE modeling
10
SNE Rational CRM

• derived from the one that proposed by Paul A.
  Birkel in 98F-SIW-018
• fundamental and graphical
• more explicit internal relationships
• data flow and time/event drive between SNE
  representations and military systems
• separation of data and model
• distinguish environment effects from military
  impacts

11
(No Transcript)
12
Formalization of SNE Rational CRM

• System, model and simulation
• model is a kind of physical, mathematical or
  logical description or representation of system
• the model must have correct and unambiguous
  interpretations responding to system for
  similarity, consistency, functionality and
  utility
• simulation is running a model over a period of
  time with given data

13
Formalization of SNE Rational CRM

• For SNE systems and models, we have
• natural environment exists as continuous spatial
  domains which can be denoted by
• the time axis is usually be defined as a period
  of continuous and even time flows denoted by
• In facts, the data used to represent SNE states
  are essentially properties related with a special
  spatial point, area or domain and a time point or
  period and many properties are derived from
  others or overlapped. So, we only focus on higher
  levels and define those properties of interest as
  

14
Formalization of SNE Rational CRM

• Now we can denote the environmental states as a
  model with the form of
• The internal environment models are used to
  describe relations between environment physical
  properties, environment dynamics along time and
  statistics with respect to phenomenon or
  procedures. We can formalize these models as

15
Technical considerations of SNE Rational CRM

• the resolution and granularity of the space
  domain and the time axis
• reasonable partition of space domain, time axis
  and property space
• multi-representations
• correlations and consistence of databases
• although the SEDRIS Data Representation Model
  (DRM), but a common environment data model is
  great needed
• data flow or event drive between the military
  system models and the natural environment

16
SNE Technical CRM

• the common supporting technologies that implement
  the rational CRM
• common data model and data representation and
  interchange
• environment library
• environment scenario generation
• environment effect and impact models
• environment federates or federations, tools and
  utilities

17
SNE Technical CRM
18
SNE Operational CRM

• simulation is running a model over a period of
  time with given data
• to capture the pre-runtime data requirements and
  processes from a high conceptual level
• using IDEF0 models to capture the process, steps,
  participants, constrains, mechanisms, inputs and
  outputs
• top level actions
• analyze the requirements
• acquire source data
• produce the deliverable authoritative SNE
  transmittals
• compile into runtime format

19
SNE Operational CRM
more elaborate depictions when decomposed
20
SNE Runtime CRM

• SNE simulation with given models and data,
  running along time axis
• a reference model of the framework of the
  environment federation utilizing the concepts and
  technologies in SNE modeling and adopting HLA
  jointly
• to establish a reference model of standard and
  reusable system architecture
• System architecture
• OASE server what is a sound design?
• dynamic terrain surface and subsurface dynamic
  effects and impacts as well as hydrology how
  about internal relations, function divisions and
  protocols?
• 3D Viewer, the 2D Display and AAR functions FOM
  agility

21
SNE Runtime CRM
22
Conclusions

• the SNE modeling and simulation domain is more
  and more becoming a common infrastructure that
  support the DoD wide modeling and simulation
  communities
• a complete, standard, brief and unambiguous
  reference model is greatly needed to establish,
  describe, organize and understand the concepts,
  frameworks and hierarchies when modeling the SNE
• we view from the rational, technical, pre-runtime
  and runtime aspect
• more need to be done, formalizations and so on

23
Conclusions

• critical technical focuses
• complete, unambiguous, effective representation
  and interchange
• common lexicons, syntax and semantics and common
  data models
• correlations and consistency of both pre-runtime
  and runtime SNE models and states
• multiple and polymorphic representation in SNE
  modeling
• dynamic environment and standard models of
  effects and impacts
• authoritative and timely SNE data acquirement,
  automatic, rapid and cost effective

24
Thanks!
Ph.D Guo Gang ggwyh_at_yahoo.com Military
Simulation Laboratory College of Mechaeronics
Engineering and Automation National University of
Defence Technology Changsha, Hunan, China, 410073