2004 Spring Simulation Interoperability Workshop - PowerPoint PPT Presentation

1 / 35
About This Presentation
Title:

2004 Spring Simulation Interoperability Workshop

Description:

Timeslot allocation/metering of data with nominal values or from an actual NDL ... Other datalinks will be efforts of the Study Group over the next year ... – PowerPoint PPT presentation

Number of Views:44
Avg rating:3.0/5.0
Slides: 36
Provided by: pubS5
Category:

less

Transcript and Presenter's Notes

Title: 2004 Spring Simulation Interoperability Workshop


1
2004 Spring SimulationInteroperability Workshop
  • Link 16 Product Development Group (Link 16 PDG)

2
Link 16 PDG Spring 04 SIW Afternoon Agenda
  • 1330 1400 Introduction (Joe Sorroche)
  • -Welcome
  • -Acceptance of Previous Minutes
  • -Review of Action Items (Joe Sorroche)
  • -Update on PDG Current Status
  • 1400 1500 - Review of the Draft Standard
    (Joe Sorroche)
  • - Solicitation and Resolution of Final Comments
    on Draft Standard (Joe Sorroche)
  • 1500 1530 Break

3
Link 16 PDG Spring 04 SIWAfternoon Agenda
(Contd)
  • 1530 1600 Tutorial on SISO Balloting
    Process The Link 16 PDG (Joe Sorroche/Tom
    Mullins)
  • 1600 1630 Motion to begin Balloting Process
    (Joe Sorroche)
  • -Review Ballot Message
  • 1630 1700 Meeting Wrap-up (Joe Sorroche)
  • -Review of action items (Rob Byers/Tom Brown)
  • 1700 Adjourn Spring 2004 SIW Meeting of Link 16
    PDG
  • Meeting minutes will be taken by Dr. Rob Byers
    via telecon and Mr. Tom Brown

4
Link 16 PDG Spring 04 SIWIntroductory Business
  • Acceptance of Previous Minute
  • Review of Action Items (Dr. Rob Byers/Joe
    Sorroche)

5
SISO Link 16Product Development Group
  • Introduction to
  • Product Development Group

6
Link 16 PDG Goals
  • Create Implementable SISO Standard from TDL SG
  • Nominally referred to as DIS-J and HLA-J
  • Provide DIS technical solution
  • Provide HLA technical solution
  • Provide implementation and usage information
  • Provide HLA BOM
  • Provide materials to understand usage of the
    standard
  • Provide guidance for eventual incorporation into
    IEEE standards
  • PDG will concentrate on codifying and validating
    TDL SG identified technical solutions

7
PDG Leadership
  • Joe Sorroche, DMOC/ASRCC
  • Link 16 PDG Chair
  • Adin Burroughs, Northrop Grumman IT
  • Link 16 PDG Vice Chair
  • Dr. Rob Byers, Northrop Grumman IT (DMT
    Standards)
  • Link 16 PDG Secretary
  • Neil Barrett, JITC
  • Link 16 PDG Assistant Editor
  • Graham Shanks
  • Link 16 PDG Assistant Editor

8
PDG Membership
  • Boeing
  • VWC
  • DMT
  • Lockheed Martin
  • DMT
  • TACCSF
  • Northrop Grumman
  • Information Technology
  • Integrated Systems
  • Stasys
  • TRW
  • ASTi
  • General Dynamics
  • QinetiQ
  • ASRCC
  • SRC
  • MRI
  • MsTI
  • 3Com
  • Simulation, Inc
  • APC
  • CAS
  • Marzen
  • AMS
  • Plexsys
  • Raytheon
  • USAF/AFC2TIG
  • Australia Virtual Ship
  • USAF/AFAMS
  • USAF/AFRL
  • USAF/ASC
  • USAF/ASC-TM
  • USAF/DMT
  • USAF/NAIC
  • USAF/TACCSF
  • DMSO
  • Sparta
  • US Navy
  • US Army
  • DISA/JITC

9
PDG History
  • Oct 01 Formed grass roots working group after
    community response to informal inquiries
  • Nov 01 Meeting at I/ITSEC
  • Initial Presentation of ideas, technical
    discussion
  • Decided to pursue becoming official SISO Study
    Group
  • Dec 01 SISO EXCOM Approves TDL SG TOR
  • Feb 02 SG Reflector, AFAMS webpage established
  • Mar 02 First official meeting of TDL SG (Fall
    SIW)
  • Jun 02 Interim SG meeting at TACCSF
  • Jul 02 SG Meeting at Euro-SIW
  • Sep 02 SG Meeting at Fall SIW
  • Oct 02 Link 16 PDG Kickoff
  • Nov 02 Link 16 PDG I/ITSEC Meeting
  • Mar 03 PDG Meeting at Spring SIW

10
PDG Current Status (Since Fall 03)
  • Submitted changes to DIS-EBV
  • Except for additions to Radio Category,
    Nomenclature in the Transmitter PDU
  • Completed Link 16 Simulation Standard Second
    Draft
  • Third Draft reviewed at Fall 03 SIW
  • Minor editorial changes
  • Addition of Radio Category/Nomenclature
  • Clarification Correction of Spread Spectrum
    Type
  • Changed JTIDS/MIDS type to 8
  • Changed Input Source to 8
  • Transmitter PDU text made consistent with table
  • Will NATO C3A TDL ITS on 17 May 04

11
PDG Current Status
continued
  • Reference Implementation by Northrop Grumman IT
  • Funded by USAF Agency for Modeling and Simulation
    under Joint Synthetic Battlespace Infrastructure
    Initiative
  • DIS version implemented in CCD Product
  • Fidelity Level 3 testing completed

12
Link 16 PDGUpcoming Events
  • Complete Final Draft of Link 16 Simulation
    Standard (April 04)
  • Technical Methods Complete
  • Final Review at Spring 04 SIW
  • Form/Send Ballot Announcement
  • Form Ballot Groups (May/June 04)
  • Accepted as an Experiment in JEFX 04
  • Will test 10 15 May 04, 12 18 July 04
  • Product Approval Package (July 04?)
  • Standard! (September 04?)

13
Challenges with CurrentDIS/HLA Standards
  • DIS Standard lacks detail for interoperability
  • DIS was never finished
  • No standard enumeration list for TDL types within
    DIS
  • Multiple DIS implementations in the wild
  • Ability to exchange TADIL J messages, no ability
    to simulate JTIDS networks
  • No methodology defined for HLA

14
Goals for New Standard
  • Standard, interoperable implementation
  • Easy initial implementation
  • Minimal impact on current users, e.g. NATO SIMPLE
    Standard
  • Ability to ease transition from old formats to
    new
  • Effects level simulation of JTIDS net
  • Ability to route datalink data separately from
    truth data
  • Minimize bandwidth utilization
  • Discrete definitions of fidelity
  • Identify FOM/SOM data items for HLA JTIDS
    emulation

15
Goals for New StandardEffects to Be Simulated
  • Timeslot allocation/metering of data with nominal
    values or from an actual NDL
  • Segmenting of data into NPGs
  • Segmenting of data into Nets
  • Multi-netting
  • Crypto-netting
  • Net entry procedures
  • Synchronization
  • Multiple NTRs

16
Goals for New StandardEffects to Be Simulated
continued
  • Relnav
  • Multiple JTIDS units transmitting at same time
  • Waveform/RF simulation
  • Antenna, propagation details
  • Additional JTIDS Datatypes
  • Link 16 Enhanced Throughput
  • VMF
  • Free Text (Voice/Imagery)

17
Goals for New StandardEffects Not Covered
  • Individual Pulses
  • Effects of conflicting pulses if hopping patterns
    coincide

18
PDG On-Line Resources
  • SISO Reflectors
  • http//www.sisostds.org (go to reflectors)
  • All discussions and documents from the SG and PDG
    are available from the reflector page
  • AFAMS Hosted Discussion Server and Document
    Repository
  • http//www.afams.af.mil
  • Click on programs and exercises, listed on this
    page
  • DMSO Reflector
  • Currently not in use, has archives for Nov-Jan 01

19
Link 16 PDG
  • The SISO Balloting Process
  • The next step for the Link 16 PDG
  • Joe Sorroche, Tom Mullins

20
SISO Balloting Process
  • SISO Balloting Products Development Process
  • SISO promotes the development of products that
    support simulation interoperability
  • The SISO SAC manages the development of SISO
    Products according to the SISO Operating
    Principles, Technical Acceptance, Principles and
    Standards Principles as stated in the SISO PP.
  • Operating Principles determine the overall
    conduct of the organization during the
    development of the product.
  • Balloted Products Development Process (BPDB),
    SISO-ADM-003-2002
  • Operating Principles
  • Responsiveness and Responsibility
  • Quality
  • Discipline
  • Fairness
  • Openness
  • Consensus

21
SISO Balloting Process
Process
Results
Approved Product Nomination
Product Nomination
Activity Approved
1. PDG Infrastructure 2. Final Draft Product
Product Development
1.Balloting Group 2.Balloting Results 3.Balloting
Product
Product Balloting
22
Balloting Process
  • SISO Balloted products required formal balloting
    process to ensure community consensus
  • The PDG must develop a product in the minimum
    time that represents the consensus view of the
    SISO Community
  • The SISO Community must balance between rapid
    decision making and open participation
  • Steps in the Balloting Process
  • Form a Balloting Group
  • Conduct an initial ballot
  • Resolve Balloting Group Member Comments
  • Conduct a Re-Circulation Ballot
  • Only necessary if combined total of 75 of
    Ballots are not returned or are not Yes, without
    comments.
  • Closure Activities

23
Forming a Ballot Group
24
Conducting the Initial Ballot
Commercial
Government
Academic
Ballot Group
PDG
Ballot Period 30 45 Days
  • Create Distribution Package
  • Balloted Product
  • Product Nomination
  • Instructions
  • Additional Documentation

25
Completing the Ballot
At Least 75 of ballots shall be returned for a
valid Ballot
Commercial
Government
Academic
Ballot Group
PDG
26
Comment Resolution
Commercial
Government
Academic
Ballot Group
PDG
Editor Assessment
Accept as is Accept with Change Accept, Change
Needed Need more Information Hold for
Resolution Withdraw Decline
PDG Review
  • Face to Face PDG Meeting
  • Euro SIW 04??

27
Final Resolution
PDG
Editor Assessment
PDG Review
  • Resolution Codes are assigned to each comment
  • Conducting a Re-Circulation Ballot
  • Only if previous ballot is unsuccessful, and if
    the PDG or SAC agree that the process continue

28
Process Closure
Submit Product for Final Approval
EXCOM
SAC
PDG
Editor Assessment
PDG Review
29
Balloting Process
  • Questions ????

30
Link 16 PDG Spring 04 SIW
  • Final Review of Draft SISO STD 002

31
Link 16 PDG Spring 04 SIW
  • Transmitter PDU
  • Radio Identifier (Category/Nomenclature)
  • System ID
  • New Text on Byte Ordering Clarity?
  • HLA BOM 1.3 vs 1516

32
Link 16 PDG
  • Motion to release standard to Balloting

33
Link 16 PDG Wrap-up
  • Action Item Review
  • Review of upcoming schedule
  • Volunteers for new TDL SG?
  • Requests for L11A/B, SADL (EPLRS) in next TDL SG

34
Link 16 PDG
  • Backup Slides

35
Comparison/Contrast of DIS-J to SIMPLE
  • SIMPLE encompasses and wraps around DIS
  • Not only TADIL, but environment as well
  • TADIL-TALES is a part of DIS and HLA
  • TADIL-TALES currently only addresses Link 16
  • Other datalinks will be efforts of the Study
    Group over the next year
  • Does not address additional needs in the
    environment generation
  • TADIL-TALES addresses needs of higher fidelity
    Link 16 RF simulation
Write a Comment
User Comments (0)
About PowerShow.com