Governance & Program Info

Predictive Logistics & Maintenance — Governance

Cross-builder institution context and per-item ownership, due dates, status, and next actions for the governance-relevant checklist items in this builder.

← Back to checklist
Institution context
Program info
Applies across every builder in the app. Stored locally; nothing leaves the browser.
Checklist governance
Items (0 of 17 marked complete)
Annotate ownership, due date, status, and next action. Items on the left come from the builder's governance / compliance phases.
05 · Governance & Compliance
DFARS 252.204-7012 CUI safeguarding assessment
required
Confirm training data, feature store, inference runtime, and audit log satisfy DFARS 252.204-7012 safeguarding of Covered Defense Information.
05 · Governance & Compliance
NIST SP 800-171 control mapping for the ML stack
required
Formally map the 110 SP 800-171 controls to the training, feature store, and inference runtime components.
05 · Governance & Compliance
Confirm training-data residency and cross-border constraints
requiredtrinidy
CUI must remain inside US / cleared-vendor perimeters. Coalition data must respect releasability markings.
05 · Governance & Compliance
DFARS 252.211-7003 IUID compliance in training pipeline
required
Unique Item Identification tracking for qualifying components is mandatory — confirm the ML pipeline consumes IUID at the correct serialization.
05 · Governance & Compliance
DFARS 252.246-7007 counterfeit electronic part controls
required
Contractor programs for detection and avoidance of counterfeit electronic parts must be in place, with suspect-counterfeit items segregated in training data.
05 · Governance & Compliance
NIST SP 800-161 supply chain risk management
required
C-SCRM controls applied to model training data, dependencies, and ML vendor software bill.
05 · Governance & Compliance
NDAA Section 889 prohibited-vendor screening
required
Confirm that no Section 889–prohibited vendors appear in the ML hardware, software, or telecommunications stack.
05 · Governance & Compliance
E.O. 14028 SBOM for ML software components
required
Maintain a Software Bill of Materials for the training, serving, and inference stack per E.O. 14028 (May 2021) and NTIA minimum SBOM elements.
05 · Governance & Compliance
DoDI 4151.22 CBM+ governance alignment
required
Program documentation aligned to DoDI 4151.22 Condition-Based Maintenance Plus governance — reliability-centered, evidence-based.
05 · Governance & Compliance
MIL-STD-3034 Reliability Centered Maintenance alignment
required
Model logic and recommendations align to the RCM framework the sustainment community already operates under.
05 · Governance & Compliance
Independent model validation
required
Second-line or external independent team validates model logic, training data, assumptions, and performance claims — independent of model development.
05 · Governance & Compliance
Full decision audit trail per recommendation
requiredtrinidy
Every recommendation logs model version, feature snapshot, sub-model scores, and SHAP-style attribution — supports airworthiness and program audit.
05 · Governance & Compliance
Model change management and versioning
required
Who approves model updates, what test is required, how changes are versioned, what airworthiness re-verification is triggered.
05 · Governance & Compliance
Program-office and PEO-level reporting
recommended
Readiness uplift, NFF rate, cost-of-action, and model-performance metrics appear in program-office and PEO dashboards, not only ops views.
05 · Governance & Compliance
OEM data-rights review for training telemetry
required
Confirm technical data rights for every sensor stream used in training — limited, restricted, government-purpose, or unlimited.
05 · Governance & Compliance
JEDMICS technical-data integration authority
recommended
Linkage to Joint Engineering Data Management Information and Control System for authoritative technical-data references.
05 · Governance & Compliance
MIL-STD-1388 LSAR legacy data handling
optional
MIL-STD-1388 is superseded but LSAR data persists on legacy platforms. Confirm how legacy LSAR is handled when it appears in training data.