1. National Security Analysis Department HLA-E PDG Conform # 1 What is Conformance? u Specification of what it means when a piece of software claims to have adopted the Standard. v vs “Compatible” which means the software doesn’t disrupt the simultaneous use of Standard conforming software. v vs “Compliant” which means the software has followed the direction of the Standard, according to it’s authors/vendor. v Why? u Adding a Conformance requirement to the Standards gives software producers defined criteria by which their compliance can be proven.

2. National Security Analysis Department HLA-E PDG Conform # 2 What is HLA Conformance? u There are many possible conformance requirements that the PDG could choose to incorporate into our Standards. A) Complete Implementation of all features. w Most work to build. w Least differentiated. w All vendors are selling the same thing. w Most interoperable B) Implementation tailored to profiles of use. w More diversity of RTI implementations. w Vendors more responsive to market. w Less interoperable u Today HLA has (B), but everybody claims we have (A). We must choose!

3. National Security Analysis Department HLA-E PDG Conform # 3 Suppose we want (A) u We write a conformance section that says conforming RTIs must implement every feature exactly according to the specs. u Verification tests that RTIs perform in this way. u RTIs are prohibited from having features which cause them to behave in a non- conforming way. ie.: v RID file settings to enable “connectionless” operation. (VTC/SAIC) v Settings to disable RTI features or permit the user to override RTI functions (M Ä K) v Just because I can’t think of a Pitch example doesn’t mean they are immune.

4. National Security Analysis Department HLA-E PDG Conform # 4 Suppose we want (B) u We agree on a scheme for identifying RTI subsets that are useful to our communities. u We write a conformance section that states when RTIs are permitted to have subset implementations. u We define how an RTI vendor makes claims about which subsets they implement. u Verification tests that RTIs act as they claim they act. u RTIs with several profiles can be tested several times to assure that each profile works.

5. National Security Analysis Department HLA-E PDG Conform # 5 Starting Proposal 1 of 2 Set NameFunctionalityStandard § ExecutionEstablish a federation execution and have federates join it. 1516.1 § 4.2-.5 Fed SyncDefine sync points and achieve them.1516.1 § 4.6-.10; 1516.2 § 4.9 Save & RestoreRTI-managed simulation state save and restore operations. 1516.1 § 4.11-.25 Object DeclarationIdentify and express interest in object classes and their attributes. 1516.1 § 5.2-.3 & 5.6-.7; 1516.2 § 4.2 Interaction DeclarationIdentify and express interest in interaction classes and their parameters. 1516.1 § 5.4-.5 & 5.8-.9; 1516.2 § 4.3 Object ManipulationCreate, update, and delete object instances and their attributes. 1516.1 § 6.2-.7, 6.10-.13 & 6.17-.18; 1516.2 § 4.4 Interaction ManipulationSend and receive interactions and their parameters.1516.1 § 6.8-.9 & 6.14; 1516.2 § 4.5 Ownership Management Allow attributes to be updated by federates other than their object instance creator under suitably controlled conditions. 1516.1 § 7 Time MarkingAssociate a joined federate’s activities with the HLA time axis by assigning time stamps to the messages representing those activities. Timestamp parameter in the other feature sets. Time SynchronizationMaintenance of synchronized time across the federation and delivery of attributes and interactions within time constraints. 1516.1 § 8; 1516.2 § 4.7 Data Distribution Management Selective distribution and reception of attributes and parameters through dynamic spaces. 1516.1 § 9, 10.12-.15, 10.17, 10.30-.34; 1516.2 § 4.6 Lookup OperationsTransformation of names to handles and handles to names. 1516.1 § 10.2-.11, 10.16 & 10.18-.21 RTI Dynamic ControlsDynamically control the behavior of the RTI with respect to advisories, switches and callbacks. 1516.1 § 5.10-.13, 6.15-.16, 6.19-.20, 10.22-.29, 10.35-.40; 1516.2 § 4.11 Management Object Model Visibility into the RTI internal representation of objects, interactions, federates, and state. 1516.1 § 11

6. National Security Analysis Department HLA-E PDG Conform # 6 Starting Proposal 2 of 2

7. National Security Analysis Department HLA-E PDG Conform # 7 Path Ahead u Incorporate the Conformance section provided. u Expect comments to the next draft on both the feature sets identified and the rules expressed in the Conformance section.

8. National Security Analysis Department HLA-E PDG Conform # 8

9. HLA Evolved PDG Position Brief – Conformance Johns Hopkins University Applied Physics Laboratory National Security Analysis Department