Slide 1 of 17

1
GM VV and Acceptance Study Group SISO Product
Nomination 15 September 2006 Submitted byRené
JACQUART Ad Van LIER Simone YOUNGBLOODTony
MASYS TAD Jean-Louis IGARZA
2
PN Document Outline

• Product Title Guidance for a Generic Methodology
  for Verification and Validation (GM VV) and
  Acceptance of simulations
• Proponent Name(s) and Contact Information
• Type of Product
• Product Description
• Identification of the community to which product
  and its components apply
• Problem(s) and/or issue(s) that this proposed
  product addresses
• Indication of the maturity of the product- to
  include alternatives discussed, prototypes,
  impacts of product, and the impact of lack of
  product
• Planned compliance testing of the product
• Schedule for product development
• Candidate Volunteers for the Product Development
  Effort
• Suggested product periodic review cycle
  (timeline)
• End of Document
• Note Acceptance is a technical process which
  supports eg. a accreditation decision (if it
  exists)

3
PN GM VV and Acceptance

• Product Title Guidance for a Generic Methodology
  for Verification and Validation (VV) and
  Acceptance of simulations
• Proponent Name(s) and Contact Information
• Dr. René JACQUART
• ONERA/DTIM2, avenue Edouard Belin31055 TOULOUSE
  (France)
• PHONE [phone]
• FAX [phone]
• Rene.Jacquart_at_cert.fr
• Type of Product SISO Guidance document

4
PN GM VV and Acceptance

• Product Description
• This product will provide the international
  community with a proposed standard for VV and
  Acceptance methodology of data, models and
  simulations.
• The product leverages and harmonizes with the
  contributions from other national and
  international VVA initiatives such as the
  current VVA PDG efforts (dedicated to an Overlay
  of the HLA FEDEP), the REVVA 1 and REVVA 2
  projects and ITOP contributions.
• Users Manual
• Reference Manual
• Recommended Practices

5
PN GM VV and Acceptance

• Users Manual
• It describes the activities to perform and the
  products to produce, the interactions taking
  place among those involved, the flow of products,
  and how to tailor the methodology to the specific
  needs of the MS project.
• Reference Manual
• Documents the underlying concepts of the
  methodology, including the foundations of the
  chosen terminology, the explanation of the
  dependencies between activities and products,
  their meaning for the VVA endeavour, and the
  rationale for their execution and creation.
• Recommended Practices
•  Provides the user with specific guidance with
  regards to the selection and use of techniques
  and tools in support of the User Manual.

6
PN GM VV and Acceptance

• 5. Identification of the community to which
  product and its components apply
• The products stemming from this PN will serve the
  greater MS community and in particular those
  charged with the task of conducting and managing
  VVA activities. The community spans many
  different user domains (e.g. Training, Analysis,
  Acquisition) and application areas (eg. Defense,
  Entertainment, Medical, Space).

7
PN GM VV and Acceptance

• 6. Problem(s) and/or issue(s) that this proposed
  product addresses
• a. Provide details on the specific need or
  requirement for this product in the community.
• VVA is a contractual requirement for some and a
  policy mandate for others. For the US DoD,
  Instruction 5000.61 on DoD MS VVA requires that
  all MS in current use within the DoD be verified
  and validated. Additionally, all MS used to
  support major DoD decision-making, joint
  training, and joint exercises must be
  accredited. In Canada, the draft VVA policy
  states that Verification and Validation (VV)
  procedures shall be incorporated into all MS
  activities. Similar policy requirements exist
  throughout the greater MS community.
• Given that there are several communities of
  interest working collaboratively to further
  harmonize VVA methodology adds credence for this
  PN.

8
PN GM VV and Acceptance

• Problem(s) and/or issue(s) that this proposed
  product addresses
• b. Provide details on the discussion of the need
  for this product in the community.
• The requirement for VVA is well documented in
  the literature and is a recurrent theme
  throughout various MS conference venues. More
  and more we see distributed simulations spanning
  regional and national boundaries. A common
  standard for VVA methodology that provides
  guidance will surely benefit the greater MS
  community.
• c. List similar products in the community you
  have investigated to ensure that no overlap
  exists.
• The product leverages and harmonizes with the
  contributions from other VVA initiatives such as
  the current VVA PDG efforts (dedicated to an
  Overlay of the FEDEP), the REVVA 1 and REVVA 2
  projects and ITOP contributions.
• Additional products include IEEE 1278.4
  national documents (US, GE,UK, FR,CA)

9
PN GM VV and Acceptance

• 7. Indication of the maturity of the product- to
  include alternatives discussed, prototypes,
  impacts of product, and the impact of lack of
  product
• Detailed description on HOW the problem/issue
  will be solved (approach).
• To facilitate the development of the GM VV and
  Acceptance documents, the stakeholders and
  participants of various national and
  international VVA initiatives (described in
  paragraph 6c) have been engaged in order to
  ensure harmonization and eliminate duplication of
  effort. As a starting point, the REVVA 2 project
  has re-aligned its deliverable schedule to
  coincide with the SISO timeline thereby creating
  a harmonized roadmap of products, work share and
  schedule. Similarly, to ensure transparency and
  encourage alignment of concepts and methodology
  participants within the various groups maintain
  active and advisory roles across the spectrum of
  VVA groups.

10
PN GM VV and Acceptance

• 7. Indication of the maturity of the product- to
  include alternatives discussed, prototypes,
  impacts of product, and the impact of lack of
  product
• Brief Discussion on the Maturity of the proposed
  product.
• The proposed product builds upon the
  contributions of mature national and
  international VVA projects such as
• ITOP official release no. 1-1-002, May 2004
• NATO Task Groups (NMSG 019 and 054) and SISO
  VVA overlay of the HLA FEDEP document
• REVVA approach (SISO publications, many case
  studies, reports)
• 04S-SIW-005, 04S-SIW-152, 04S-SIW-153,
  05S-SIW-040, 05S-SIW-041, 05E-SIW-021, 06S-SIW
  (VVA Forum)
• SISO papers in the context of the VVA forum
• International VVA processes (eg. DoD, Canada DND
  SECO, various MoDs)

11
PN GM VV and Acceptance

• c. Brief Discussion on alternative approaches to
  the proposed product
• There is currently no internationally recognized
  VVA guidance available and therefore no
  alternative approach.
• d. Provide examples of prototypes of the proposed
  product or reasons why this product will not be
  prototyped.
• The use of Case studies in lieu of prototyping
  and testing will be conducted and documented to
  demonstrate the efficacy of the guidance
  documents. These case studies will be included
  within the Recommended Practices documentation.
• e. What impact will the proposed product have on
  the MS community.
• The GM VV and Acceptance products (aligned with
  the established REVVA 2 deliverables) will
  provide a comprehensive VV standard
  methodology thereby improving opportunities for
  interoperability and reuse. In addition, it will
  draw international attention to the issues
  associated with VVA and the importance it has
  with regards to risk and decision making.

12
PN GM VV and Acceptance

• f. What impact will this proposed product have on
  the SISO community?
• The GM VV and Acceptance product will enlarge
  the scope of MS VV to new application domains
  as well as increase the visibility and role of
  SISO within the international community. It will
  complement the current VVA PDG efforts mainly
  related to the VV of federations of simulation.
• g. What is the impact to the community if this
  proposed product is not developed?
• Not developing the standard will perpetuate the
  stove piped approach to VVA thereby making
  interoperability and reuse problematic.
• h. What are the domain implications for this
  proposed product?
• The products are applicable to all simulation
  domains that currently or will in the future
  embrace VVA as an integrated process
• i. State which SIW Conference forum(s) take an
  active interest in the development of this
  proposed product?
• This product is particularly associated with the
  well established VVA forum. It is also of
  interest among the other forums within SISO, as
  VVA transcends all MS domain applications.
  These include such forums as DSPT and Space.

13
PN GM VV and Acceptance

• 8. Planned compliance testing of the product
• The REVVA 2 case study work packages will provide
  an avenue for test and evaluation of the VVA
  methodology.

14
PN GM VV and Acceptance

• 9. Schedule for Product development

15
PN GM VV and Acceptance

• Euro-SIW 2006 presentation of a draft PN
  document
• Fall SIW 2006 complete, finalize PN for GM VV
  and Acceptance PDG, increase awareness
• January 2007 draft standardization progress
  report
• Spring SIW 2007 formal presentation of the PDG
  to SISO mbrs scope, timeframe, expected
  outcomes, working mode, election of PDG officers,
  designation of a drafting group
• Euro-SIW 2007 formal presentation of the PDG
  presentation of the first draft skeleton of the
  methodology content
• Fall SIW 2007 presentation of a first draft of
  the methodology organization of a first round
  Comment Round
• Dec 2007 resolution of comments production of
  second draft
• January 2008 standardization report
• Spring SIW 2008 detailed presentation of the GM
  VV and Acceptance organization of a second
  Comment Round
• May 2008 Resolution of comments
• Euro SIW 2008 detailed presentation of the new
  GM VV and Acceptance release
• Fall SIW 2008 presentation of the final PDG
  products
• January 2009 consolidated report to the SAC
• Spring SIW 2009 Feedback of SISO and balloting
  process

16
PN GM VV and Acceptance

• 10. Candidate Volunteers for the PDG effort

17
PN GM VV and Acceptance

• 11. Suggested product periodic review cycle
  (timeline)
• Periodic Review date(s)
• Possibility to establish a PSG.
• b. Review Activity Description
• Enrich the document with the last finding from
  WG.
• End of Document