CIGI Study Group CloseOut Meeting Agenda

1
CIGI Study Group Close-Out Meeting Agenda

• Introduction and Welcome
• Review CIGI Study Group Charter and Goals
• Goal
• Product
• Schedule
• Update of Boeing CIGI
• Review CIGI Survey of Interest Results
• Review recommendations
• Close CIGI Study Group
• Adjourn

2
Common Image Generator Interface (CIGI)Study
Group (SG)

• SG Leadership
• Chair Ronald Moore
• Vice Chair Willard Phelps
• Secretary Michael Butterworth
• Purpose
• Evaluate industry and government interest in
  developing a standard image generator interface
• Product
• Report evaluation, alternatives, recommendation
• Schedule
• Complete Study Spring 2004

3
CIGI Study Group Background

• Typically today's Image Generator (IG) vendors
  have their own closed, proprietary run-time
  interfaces.  At I/ITSEC'02 Boeing proposed their
  Open Source Common Image Generator Interface
  (CIGI) as a run-time interface that could be
  adopted by the simulation community.  Boeing
  indicated that they would like to see a standard
  organization adopt CIGI, and develop it into a
  robust and broadly accepted simulation industry
  image generator run-time interface standard.
• A panel discussion was held at SIW Spring03,
  with Boeing presenting a summary of CIGI to the
  SNE group.  Following the Boeing presentation we
  discussed SISO SNE championing CIGI as a
  simulation interoperability standard.  The SNE
  members (in attendance) accepted the
  recommendation to form a SISO Study Group to
  pursue the Boeing proposal.
• US Navy has selected CIGI as an image generator
  standard interface on a number of new programs
  and projects
• Multiple vendors have begun offering CIGI as an
  optional interface
• 2003 Fall SIW, Orlando, FL Study Group Kickoff
  Meeting

4
Update of Boeing CIGI

• Bill Phelps
• Version 3.0 status update

5
Survey of Interest Results

• Responses
• Government 3
• Government Organizations
• Prime Contractor 2
• Companies building simulators incorporating IGs
• Vendor 2
• Companies building Image Generators

6
Survey of Interest (2)
1) Have you reviewed the CIGI documentation?
7
Survey of Interest (3)
1a) What do you think of the CIGI concept?
8
Survey of Interest (4)
1b) What do you think of the CIGI Interface
Control Document (ICD)?
9
Survey of Interest (5)
1c) What do you think of the CIGI Software
Development Kit (SDK)?
10
Survey of Interest (6)
1d) What do you think of the CIGI interface
emulator (host emulator)?
11
Survey of Interest (7)
2) Should SISO take-on the task of developing
CIGI into an ISO or IEEE standard?
12
Survey of Interest (8)
3) Would your company be willing to support CIGI
as an Open Source initiative? 3) Would your
government organization be willing to support
CIGI as an Open Source initiative?
13
Survey of Interest (8)
4) Is your company planning to implement CIGI?
Or has your company implemented CIGI?
14
Survey of Interest (9)
5) Comments
15
Survey of Interest (10)

• Minimal response
• Suggests minimal interest
• (Too busy to respond?)
• (Not authorized to respond?)
• Clear interest and willingness to support (from
  those who responded)
• Clear benefit to Government stake holders

16
CIGI Study Group Products

• The product of the study group will be a report
  that addresses
• The results of a survey of interests
• A top level technical review of the current
  Boeing CIGI
• Hardware interface
• Interface Control Document (ICD)
• Application Programmers Interface (API)
• Software Development Kit (SDK)
• Interface (host) Emulator and Test Tools
• Review of relevant industry organizations and
  standards
• Disposition of Open Source software
• Enforcing interface compliance
• Next step recommendation

17
Relevant Industry Organizations and Standards
Discussion

• SISO
• Least cost as a standards effort
• IEEE
• Costly in time and effort
• ISO
• Most costly in time and effort
• Industry Consortium
• Not likely a large enough community of interest
  to fund a independent organization
• Open Source Community
• Not controlled as a standard
• Easy to extend without compatibility
• Most progressive

18
Open Source Discussion

• Boeing is posting the CIGI software as Open
  Source
• The Open Source communities are succeeding by
  allowing others to produce code - using a
  controlling body to gate what is posted
• Believed to be a very cost effective model for
  sharing
• They are not standards, but cost leveraging
  others work

19
Compliance Discussion

• This is a very costly concern
• Not realistic to stand up a testing organization
  for such a small user community
• Could be government funded
• Not viable as a consortium funded activity

20
Recommendation

• Standard
• Make the ICD a SISO standard
• Small community of interest , must be minimal
  cost
• Do not attempt to make CIGI a SISO standard
• Too small community of interest (go small, go
  home)
• Open Source
• Pursue CIGI as an Open Source product
• Establish a Community of Interest (COI)
• Establish methods for guidance
• Establish a process for multiple developers to
  contribute to the Open Source
• Establish a testing process for Open Source
  contributions
• Use SISO SIW as a forum to host the CIGI Open
  Source Community meetings