The following requirements and sample contracting language should be included in all xAPI Simulation content acquisitions. The samples below can be used without modification, but it is expected that updates may be required based on specific requirements of the xAPI content.

Requirements & Contracting Language Samples

ID Requirement Contracting Language Sample
AR-4.1 Conformance with the Navy Simulation Profile The Contractor SHALL implement all the relevant requirements in the Simulation Base Profile. There is currently no automated test for Simulation Profile conformance. The contractor SHALL prove conformance by providing sample xAPI statements for manual validation.
AR-4.2 Initialize Values via Launch If the simulation is web-based and will be launched from the LMS, the Contractor SHALL develop the content such that it supports the web-based launch mechanism and associated data initialization requirements defined in the Navy Core xAPI Profile.
AR-4.3 Authentication, Authorization, and xAPI Actor Initialization If the simulation is a native application and/or will not be launched from the LMS, the Contractor SHALL authenticate the user and use the data returned to create the xAPI Actor as defined in the Navy Core xAPI Profile.
AR-4.4 Initialize and Terminate Tracking The Contractor SHALL develop the simulation such that it tracks an Initialize Statement when the simulation begins and a Terminate Statement when the simulation ends as defined in the Simulation Base Profile.
AR-4.5 Learner Interaction Data Tracking The Contractor SHALL track relevant learning and training related events as the learner experiences the simulation. These events SHALL be tracked in accordance with the best practices in the Simulation Base Profile for extending the profile for additional learner interaction data.
AR-4.6 Simulation State Tracking The Contractor SHALL track simulation state that is relevant to learning and training events as the learner experiences the simulation. State SHALL be tracked in accordance with the best practices in the Simulation Base Profile for extending the profile for simulation state.
The Contractor SHALL NOT use the xAPI to manage the overall simulation state or the syncing of simulation clients.

Task Trainers comprise a category of simulation used to train maintenance or operation skills in accordance with documented, well-defined procedures. The three classes of Task Trainers include:

  • Web-based or desktop virtual simulation (VSIM) maintenance task trainers
  • Web-based or desktop VSIM operator trainers
  • Part task trainers

The following requirements and sample contracting language should be included in all xAPI Task Trainer Simulation content acquisitions. The samples below can be used without modification, but it is expected that updates may be required based on specific requirements of the xAPI content.

Requirements & Contracting Language Samples

ID Requirement Contracting Language Sample
AR-5.1 Conformance with the Task Trainer Simulation Profile The Contractor SHALL implement all the relevant requirements in the Task Trainer Simulation Profile. There is currently no automated test for Task Trainer Simulation Profile conformance. The contractor SHALL prove conformance by providing sample xAPI statements for manual validation.
AR-5.2 LMS Launch Initialization Data If the simulation is web-based and will be launched from the LMS, the Contractor SHALL develop the content such that it supports the web-based launch mechanism and associated data initialization requirements defined in the Navy Core xAPI Profile.
AR-5.3 Non-LMS Actor Initialization Data If the simulation is a native application and/or will not be launched from the LMS, the Contractor SHALL authenticate the user and use the data returned to create the xAPI Actor, as defined in the Navy Core xAPI Profile.
OR
If the simulation is a native application and/or will not be launched from the LMS, the Contractor SHALL conform to the requirements in the Navy Core xAPI Profile for the xAPI Actor.
AR-5.4 Initialize and Terminate Task Trainer Simulation Tracking The Contractor SHALL develop the task trainer simulation such that it tracks an Initialize Statement when the simulation begins and a Terminate Statement when the simulation ends, as defined in the Task Trainer Simulation Profile.
AR-5.5 Initialize and Terminate Task Trainer Scenario Tracking The Contractor SHALL develop the task trainer simulation such that it tracks an Initialize Statement when a scenario begins and a Terminate Statement when the scenario ends, as defined in the Task Trainer Simulation Profile.
AR-5.6 Initialize and Terminate Task Trainer Task Tracking The Contractor SHALL develop the task trainer simulation such that it tracks an Initialize Statement when a task begins and a Terminate Statement when the task ends, as defined in the Task Trainer Simulation Profile.
AR-5.7 Learner Interaction Data Tracking The Contractor SHALL track relevant learning and training related events as the learner experiences the task trainer simulation. These events SHALL be tracked in accordance with the xAPI Statement Requirements & Examples documented in the Task Trainer Simulation Profile.
AR-5.8 Task Trainer Simulation State Tracking The Contractor SHALL track task trainer simulation state data that is relevant to activities as the learner experiences the simulation. State SHALL be tracked in accordance with the xAPI Statement Requirements & Examples documented in the Task Trainer Simulation Profile.

The Contractor SHALL NOT use the xAPI to manage the overall task trainer simulation state or the syncing of task trainer simulation clients.