Simulation Guide
Knowledge Guides /How do you define scope and acceptance criteria for an AFSIM operational simulation project?
Last updated: · New Horizon Digital Outsourcing Team
An AFSIM project must first specify whether it supports public research, teaching demonstrations, or authorized mission analysis, and confirm rights to use the software, models, and data. Acceptance focuses on reproducible scenarios, explainable assumptions, and consistent statistical definitions. A 3D situation display must not be equated directly with effectiveness validation.
Define the analysis question before choosing scenario scale
- Limit the question to an inspectable scope, such as task workflows, resource coordination, or information exchange, and record what is excluded. More platforms do not make an analysis more reliable; if basic behaviors and inputs lack supporting evidence, expanding the scenario only amplifies uncertainty. Demonstration and analysis projects should be quoted and accepted separately.
Check input assets and permissions
- Organize public or authorized terrain data, abstract platform models, behavior rules, time ranges, and event definitions. Do not treat unknown performance parameters as actual equipment data. Controlled materials must be supplied by entities with the appropriate permissions; assembling information from the internet does not replace authorization.
Make run results reproducible
- Record software and plugin versions, model versions, random seeds, and run configurations. Verify event ordering and logs in a minimal scenario before repeated runs. Keep shared conditions consistent when comparing alternatives, and retain incomplete and abnormal runs rather than selecting only the most visually impressive clips.
Deliverable inventory and limits of conclusions
- Recommended deliverables include scenario projects, parameter-source tables, event dictionaries, batch configurations, and explanations of results. During acceptance, the recipient reruns representative scenarios and checks the logs. Conclusions apply only to the stated models and assumptions and must not be presented as guarantees of real mission outcomes.