Assess whether a DMSMS hit is already a stock-out risk (e6651b)

SITUATION The working file is repair-history file that will not tie to cost after UCAs older than the local policy cap. Vendor-base mapper in a sustainment cell after a failed repair turnaround has to name Fund and move materiel or Cannibalize or substitute for this Defense Sustainment Depot Procurement Intelligence file.

DECISION Vendor-base mapper in a sustainment cell after a failed repair turnaround must choose Fund and move materiel / Cannibalize or substitute / Defer a cycle / Hold using repair-history file that will not tie to cost after UCAs older than the local policy cap.

HYPOTHESES TO TEST 1. The population in repair-history file that will not tie to cost is the one UCAs older than the local policy cap named, so Fund and move materiel follows for this Depot Procurement Intelligence file. 2. The population in repair-history file that will not tie to cost is adjacent only to UCAs older than the local policy cap; Cannibalize or substitute is the honest Defense Sustainment call. 3. A sustainment cell after a failed repair turnaround already contained UCAs older than the local policy cap before repair-history file that will not tie to cost arrived; no new Depot Procurement Intelligence path. 4. Provenance on repair-history file that will not tie to cost after UCAs older than the local policy cap is broken; do not pick Fund and move materiel or Cannibalize or substitute yet.

ANALYSIS REQUIRED 1. Compare on-hand, due-in, and condemned quantities in repair-history file that will not tie to cost. 2. Quantify mission impact if a DMSMS hit is is deferred one cycle in a sustainment cell after a failed repair turnaround. 3. Reconcile depot demand in repair-history file that will not tie to cost to fleet readiness and NSN coverage after UCAs older than the local policy cap. 4. For this Defense Sustainment Depot Procurement Intelligence file, read repair-history file that will not tie to cost against UCAs older than the local policy cap and write the one fact that would move a DMSMS hit is for vendor-base mapper.

RECOMMENDATION Choose Fund and move materiel / Cannibalize or substitute / Defer a cycle / Hold on this Defense Sustainment / Depot Procurement Intelligence packet (repair-history file that will not tie to cost after UCAs older than the local policy cap). The follow-on Depot Procurement Intelligence action is what vendor-base mapper does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Defense Sustainment option on a DMSMS hit is, then the evidence in repair-history file that will not tie to cost, then the action for vendor-base mapper - Hypothesis scorecard against repair-history file that will not tie to cost: supported / rejected / untestable - Depot Procurement Intelligence finding in repair-history file that will not tie to cost that a second reviewer can re-perform - Missing page in repair-history file that will not tie to cost after UCAs older than the local policy cap, if any