Identify the standard and its scope

NASA-STD-7009B is NASA's Standard for Models and Simulations. NASA's registry lists revision B as active, with an approval date of 5 March 2024. Those are the document's status and date; this article's October 2026 review does not turn it into a newly issued standard.

Section 1.2 describes its applicability to NASA modeling and simulation work. Required application comes through the relevant directives or agreements; citing it does not establish a universal obligation for every aerospace supplier. For a reader assessing a published claim, the useful starting point is the particular analysis and the decision it is intended to inform.

Revision B separates capability from results

A central revision-B change separates assessment of model development from assessment of its use. The capability assessment considers development data, verification, validation, technical review and management. The results assessment examines use suitability, input pedigree, uncertainty, robustness, review and management of the analysis. Appendix E explains the two structures; section 4.3.8 brings both into reporting to decision makers.

This distinction makes a reference to the standard more informative than an unexplained credibility label. Section 4.3.6 does not prescribe universal passing levels. A citation alone therefore cannot tell us that NASA certified a commercial model or approved the conclusion of a particular report.

Use the companion handbook for explanation

NASA-HDBK-7009B is the companion implementation guide. Its registry lists it as active, dated 3 February 2026. The standard sets requirements and recommendations; the handbook supplies explanations, examples and approaches to applying them. The two document identifiers should remain distinct in an article, proposal or reading list.

Handbook section 5.1.1.2 explains the statement of intended use: what the model is meant to do, its broad limits and the kinds of results or functions expected. It also discusses identifying situations to avoid. This is a useful entry point before reading detailed assessment tables, because it establishes what the modeled work is for.

A reader's example: one model, two claims

Consider a hypothetical museum evaluating visitor queues. One report compares two ordinary weekday entrance layouts; another uses the same software to promise that a crowded exhibition opening will have no delays. Both reports display an attractive animation and mention NASA-STD-7009B. As readers, we would first describe the two claims separately. The first concerns a comparison between layouts. The second makes a much broader promise about a special event. Sharing software does not make those statements identical, and we would not merge their evidence into one endorsement.

We would ask what information each report actually provides about arrivals, opening hours and visitor behavior. We might find that the exhibition report supplies no account of how its event assumptions were chosen. That would leave an unanswered question, even if the weekday report were detailed. We would also distinguish a planning comparison from an operational guarantee. This example is an editorial reading exercise, not a NASA case study, an acceptance method or a claim that a particular museum model meets the standard.

Follow the reference back to the evidence

The handbook explicitly addresses people receiving results, including technical reviewers and decision makers, as well as developers. Section 1.2 describes using its worksheet to understand a presented analysis or structure a review. That makes the companion useful to someone reading a report without building the model themselves: it offers a route into the supporting record and the questions the presentation leaves open.

For our coverage, the editorial task is to state the claimed result, identify the document and revision being invoked, and distinguish supplied evidence from unanswered questions. A named standard gives the reader somewhere concrete to investigate. The strength of the published claim still needs its own explanation.

Evidence note

Reviewed against NASA's active-document listings and the linked approved documents on 30 October 2026. Dates identify document approval, not this review. The museum example is hypothetical; this explainer does not assess a model's compliance.

SOURCE REGISTER

Read the evidence.

  1. 01
  2. 02
  3. 03
  4. 04

Continue reading

A prototype is a question being tested

More records in this topic

These records share a broad topic. They do not imply that a program uses the technology described above.

DragonFire →Sentinel-1C →All program records →