1. 2003 Spring SIW Outbrief 2003 Spring Simulation Interoperability Workshop

2. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Chair: Jim Coolahan Vice Chair: Tim Jahren Total attendance:30-38 per session Number of Papers presented:6 Panel discussions: after first 2 sessions (by speakers) OTHER MEMBERS: Judith Dahmann, Ron Hofer, Jim Hollenbach, Dave Thomen, Phil Zimmerman

3. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Goals for this Workshop SAPD focuses on M&S as part of a transformed, integrated enterprise responsible for the entire system/product life cycle, as well as the interoperability of systems of systems. Subjects include: policy and process approaches; establishment of business cases for M&S and solutions to intellectual property issues; and the value of standards, information sharing, reuse, collaboration, and work force perspectives. For the Spring 2003 workshop, SAPD was particularly interested in papers on actual experiences from both industry and government in applying M&S to the above, approaches to key issues, and lessons learned.

4. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Key Points FEDEP embellishment may be needed, depending on system/product problem domain Cost-performance HLA federation approaches appear to be viable Product data representation work is advancing – a Study Group is recommended to consider need for standards Administrative – forum location and duration

5. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Key Point 1: FEDEP embellishment may be needed Explanation: The Joint Distributed Engineering Plant (JDEP), in its Single Integrated Air Picture (SIAP) pilot effort, worked with users to establish guidance for the federation, and then employed a “systems engineering team” in establishing the Federation Object Model (FOM) (vs. having a “FOM-arama” FOM development meeting). Such “persistent” system-of-system domains may need to “embellish” the early part of the FEDEP process. Recommendation: The Distributed Simulation Development Process (PROC) Forum should establish a collection mechanism for capturing such lessons learned.

6. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Key Point 2: Cost-performance HLA federations appear to be viable Explanation: Cost-performance trades are essential to the SAPD process. A new UK HLA federation combining mission performance and cumulated incurred costs, in a helicopter application, was reported. This is the second such application known to the forum. The UK federation also employed a “dual FOM” with a separate encrypted connection for cost information. Recommendation: The SAPD Forum will solicit, promote and publicize cost-performance trade uses of interoperable simulation.

7. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Key Point 3: Product data representation work is advancing Explanation: Information and data are a significant program cost that acquisition programs need to actively manage. Work on product data representations and information management is advancing in major programs (e.g., JSF). The need for coupling M&S and information management with the systems engineering process is apparent. Recommendation: The SAPD Forum PRP intends to formulate and submit a recommendation for a Study Group to Assess the Need for Product Data Representation Standards, with a first meeting targeted for the 2003 Fall workshop.

8. 2003 Spring SIW Outbrief System Acquisition and Product Development (SAPD) Forum Key Point 4: Administrative issues Explanation – “whines” about this workshop Layout of breakout rooms made SAPD “hidden” at the end of the back corridor (not sure how this contributed to lower than usual attendance) Audiovisual support could be better (had no lapel microphone for speakers) Forum needs a full day (lost 2 “prime” hours to Standards Plenary) Recommendation: The Conference Committee should not schedule the Standards Plenary on the sole User Community Forum day – use one of the two Specialty Forum days.