Synthetic Environment Data Representation and Interchange Specification SEDRIS - PowerPoint PPT Presentation

1 / 21
About This Presentation
Title:

Synthetic Environment Data Representation and Interchange Specification SEDRIS

Description:

Synthetic Environment Data Representation and Interchange Specification (SEDRIS) ... MultiGen-Paradigm and SEDRIS (Juliana Slye, MGI/Paradigm) ... – PowerPoint PPT presentation

Number of Views:134
Avg rating:3.0/5.0
Slides: 22
Provided by: timgi3
Category:

less

Transcript and Presenter's Notes

Title: Synthetic Environment Data Representation and Interchange Specification SEDRIS


1
Synthetic Environment Data Representation and
Interchange Specification (SEDRIS)
  • Simulation Interoperability Workshop
  • September 14, 1998
  • http//www.sedris.org

2
Agenda
  • 0830 - Introductions - Graham Shanks
  • 0835 - Status DMSO Perspective - Paul Foley
  • 0850 - Project Overview - Farid Mamaghani
  • 0925 - SISO SEDRIS - Jim Shiflett
  • 0930 - SEDRIS Applications (10 mins. each)
  • Oceanographic Data Sets (Susan Starke, NRL -
    Stennis)
  • Database Content Evaluation (Bob Richbourg,
    IDA)(demo)
  • UK DERA and SEDRIS (Barry Tomlinson, DERA, UK)
  • 1000 - Break
  • 1030 - SEDRIS Applications (cont.)
  • SEDRIS Navigator (Paul Metzger, RBD) (demo)
  • SEDRIS to ModSAF (Victor Skowronski,
    Litton/TASC)
  • CCTT Interchange Experiment (Ken Donovan, LMIS)
    (demo)
  • MultiGen-Paradigm and SEDRIS (Juliana Slye,
    MGI/Paradigm)
  • SEDRIS Coordinate Conversion (Ralph Toms, SRI)
  • MEL - SEDRIS Prototype (Louis Hembree,
    NRL-Monterey) (demo)
  • SEDRIS to CCTT SAF (Jon Watkins, SAIC)
  • Object Browser Side-by-Side tools (Jesse Liu,
    AcuSoft) (demo)
  • 1150 - Question Answer Session

3
The Problem - The Solution
  • Database Interchange Today
  • Expensive, time consuming, and often unreliable
  • User systems require a unique converter for each
    source
  • Databases may undergo several conversions before
    a useable format is obtained
  • Database Interchange - SEDRIS
  • One standard method used for interchange
  • Fewer conversions, therefore, less opportunity
    for error
  • Common tools and software shared and reused
  • Reduction in conversion costs achieved

Producers NIMA AFCCC NAVO
Native database format n
Common Data Model
Native database format 3
Resource Repository
4
Why SEDRIS?
  • To Meet the Need to
  • Share common descriptions of the physical
    environment as a precondition for
    interoperability
  • By Providing
  • A uniform and effective mechanism for the
    unambiguous and loss-less interchange of
    environmental databases before simulation runtime
    execution
  • With Sponsorship from
  • Defense Modeling and Simulation Office
    (DMSO)
  • MS Executive Agents for Authoritative
    Environmental Representation
  • Defense Advanced Research Projects Agency
    (DARPA)
  • U.S. Army Simulation Training and
    Instrumentation Command (STRICOM)
  • Program Manager for the Combined
    Arms Tactical Trainer (PM CATT)

5
Project Goal
Producers NIMA AFCCC NAVO
Native database format n
Producers NIMA AFCCC NAVO
Native database format n
Native database format 3
Resource Repository
Resource Repository
Native database format 1
Native database format 2
Interchange Today
Interchange through SEDRIS
Complete Interchange Mechanism
Data Modeling API Prototyping
Format Prototyping
CY 1995 ------------------------ 1996
---------------------------- 1997
--------------------------- 1998------------------
---------- 1999
6
SEDRIS Objectives
  • Mission To provide a uniform and effective
    mechanism for clear, complete, and unambiguous
    interchange of environmental databases.
  • Primary Objectives
  • Articulate and capture the complete set of data
    elements and associated relationships needed to
    fully represent the physical environment.
  • Support the full range of simulation applications
    (e.g., computer-generated forces, manned, visual,
    and sensor systems) across all environmental
    domains (terrain, ocean, atmosphere, and space).
  • Provide a standard interchange mechanism to
    pre-distribute environmental data and promote
    database reuse and interoperability among
    heterogeneous simulations.

7
A Full Range of Applications ...
8
DB Generation Interchange - SEDRIS
maps, charts
textures, imagery
Native database format 2
Converter
Master Environmental Library
Database Generation System 1
Integrated database format 1
Native database format 3
Converter
. . .
. . .
. . .
Database Generation System n
Converter
3D models
CGF database
CIG database
Map Generation System
attributes, observations, descriptions
Sensor database
database map
9
SEDRIS Target Applications
  • DoD MS Analysis, Training, and Acquisition
    Systems
  • Sensor Systems (EO/IR, Radar, Acoustic, etc.)
  • Computer Generated Force Applications
  • Computer Image Generation
  • Virtual and Constructive Simulation Systems
  • Vehicle Dynamics Software Applications
  • Simulation Map Generation
  • Geographic Information Systems
  • DoD C4ISR Systems
  • Commercial Sector

10
Primary Aspects of SEDRIS
  • Unambiguous representation of environmental data
  • Semantics and relationships of data elements
  • All environmental domains
  • Expressed in the SEDRIS data representation
    model
  • Efficient interchange of environmental data
  • Sharing and re-use
  • Ease of access and software development (API)
  • Tools and applications

11
SEDRIS Consists of...
  • Common data representation model for all
    environmental domains (terrain, ocean,
    atmosphere, and space)
  • Read and Write APIs at multiple levels of
    complexity
  • SEDRIS Transmittal Format
  • Tools and Utilities
  • Support from the principal (DoD, Federal,
    Commercial, and International) resource providers
  • Standards for data representation and interchange

12
SEDRIS Data Representation Model
  • Geometry type objects (such as 3D polygons,
    patches, lines, and points which provide the
    physical/surface representation of real world
    objects)
  • Feature type objects (such as areal, linear, and
    point features which represent higher level
    abstraction of real world objects)
  • Topology (which allows concise, mathematical
    definition of inter-Feature or inter-Geometry
    object relationships)
  • Attributes (such as location, time, color,
    sound, width, etc.)
  • Libraries (that store a copy of any instanceable
    object)
  • Explicit relationships among feature objects,
    among geometry objects, or between geometry and
    feature objects
  • Organizational schemes that allow well-described
    hierarchical configuration of geometry and
    feature objects

13
The SEDRIS APIs
  • Uses a Layered Software Model
  • Deals with Missing or Wrong Format Data
  • Provides Context-Sensitive Access to Data
  • Supports Multi-Path Access

14
SEDRIS Transmittal Format Characteristics
  • Supports the full range of environmental data
  • Efficiently enables users (producers and
    consumers) conversion software to pass data
    through the SEDRIS data model
  • Is transparent to the end user
  • Does not mandate any specific hardware platform
    dependency

15
SEDRIS Class Attribute State Coding Standard
  • Separates enumerations from the data model and
    data dictionary
  • Evolve at different rates and times
  • Allows better leverage of external standards
  • Increased flexibility/extensibility
  • Applies to
  • Classification (and Features) -? SEDRIS
    Classification Codes (SCC)
  • Attributes (and Values) -gt SEDRIS
    Attribute Codes (SAC)
  • States -? SEDRIS State Codes (SSC)
  • Leverages and extends NATO STANAG 7074
  • Alphanumeric codes
  • Shallow hierarchy (not clear theres a better
    approach)
  • Comprehensive documentation
  • nOT CasE SeNsitIvE

16
Technical Development Process
  • Open forum and process for technical development
  • Each new data subject area is addressed by first
    developing a mapping document to the data
    representation model to ensure the model is
    complete
  • Make the best decisions in balancing design
    elegance with operational practicality
  • Spiral development process characterized by
  • Formal SEDRIS Change Request (SCR) management
    process
  • Use of specialty groups (Ocean/Atmosphere,
    Visualization, Metadata, Coordinates,
    Documentation, Interchange Format)
  • Interchange Experimentation and Validation

17
Successful Teamwork
  • Excellent example of teamwork across the board
    (associates, management, government agencies,
    etc.)
  • Cross-pollination and cooperation among
    competitors
  • Innovative successful process management
  • Diligent management of twenty-two organizations
  • Increased level of understanding in the community
    on environmental issues

18
What SEDRIS Is Not
  • The solution to interoperability (but it is a
    critical precondition)
  • A database generation system
  • An enforcement method for building databases
  • A value judgment on database content
  • A validation and verification methodology
    (but it helps)
  • A proprietary interchange mechanism
  • Just a data interchange format (DIF)

19
FY96-98 Activities Accomplishments
1996 1997
1998 1999
Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1
Q2 Q3 Q4 Q1
SEDRIS ASSOCIATE 1
2 3 4 5 6 7 8
9 MEETINGS (SAMs) ?
? ? ? ? ? ?
? ?
DATA MODEL 1.0 1.01 1.02
1.03 1.04d 1.05c
1.33 RELEASES ?
? ? ? ? ?
? ?? 1.06a 1.34
SHOWS, SIW I/ITSEC SIW
ID NATO SIW OH ESRI CONFERENCES
? ? ? ?
? ? ? ? OH SEDRIS
Open house
?? ? ? ID
DMSO Industry Days
OH/SIW ITEC ID
? I/ITSEC
20
Review
  • The SEDRIS technology contains
  • a comprehensive data representation model for all
    domains of environmental data
  • a specified interchange format and a powerful API
    for interchanging databases
  • tools, utilities, and conversion applications
  • and will provide
  • complete and unambiguous descriptions to
    represent the environment
  • loss-less interchange
  • a standard interface and interchange format
  • reusable applications
  • an initial commercial support capability for
    SEDRIS databases and interchange

21
FY 99 Projected Milestones
1998
1999 2000
OCT NOV DEC JAN FEB MAR APR MAY JUN JUL
AUG SEP OCT NOV DEC JAN
SEDRIS Associates 10 Meeting
?
Data Model 2.0
2.5
3.0 Releases ?
?
?
Training
? ? ?
? ?
Shows, I/ITSEC
SIW ITEC/UC ID SIW
UC Conferences ?
? ?? ?
? ? UC SEDRIS Users Conference ID
DMSO Industry Days
  • Release 2.0 (initial formal release) November
    1998
  • Release 2.5 March 1999
  • Release 3.0 September 1999
  • SEDRIS Users Conferences and Training Sessions
    in 1999
  • Will be developing technical specification
    suited for standardization in 1999
Write a Comment
User Comments (0)
About PowerShow.com