Assess whether TDP is complete enough to compete the work (397f85)

Situation

Repair-vs-buy decision support lead in an engineering support activity reviewing alternate sources has one working extract — repair-history file that will not tie to cost — after document numbers that collide across two systems of record. If repair-history file that will not tie to cost cannot support TDP is complete enough, the honest Defense Sustainment output is hold.

Decision

Repair-vs-buy decision support lead in an engineering support activity reviewing alternate sources must choose Fund and move materiel / Cannibalize or substitute / Defer a cycle / Hold using repair-history file that will not tie to cost after document numbers that collide across two systems of record.

Hypotheses to test

• Repair-vs-buy decision support lead can defend Fund and move materiel from repair-history file that will not tie to cost after document numbers that collide across two systems of record in a Defense Sustainment challenge.
• Repair-vs-buy decision support lead cannot defend Fund and move materiel from repair-history file that will not tie to cost; Cannibalize or substitute is what the extract actually supports after document numbers that collide across two systems of record.
• Document numbers that collide across two systems of record never reached the population in repair-history file that will not tie to cost — reopen intake, do not close TDP is complete enough.
• Two facts in repair-history file that will not tie to cost after document numbers that collide across two systems of record conflict for repair-vs-buy decision support lead; hold this Depot Procurement Intelligence file.

Analysis required

• Reconcile depot demand in repair-history file that will not tie to cost to fleet readiness and NSN coverage after document numbers that collide across two systems of record.
• Trace the funding or cannibalization line that would actually move repair-history file that will not tie to cost.
• Test whether the shortfall is materiel, maintenance posting, or a bad count.
• For this Defense Sustainment Depot Procurement Intelligence file, read repair-history file that will not tie to cost against document numbers that collide across two systems of record and write the one fact that would move TDP is complete enough for repair-vs-buy decision support lead.

Recommendation