AI Playbook for Depot Sustainment Procurement Intelligence

A research team must analyze attached depot logistics, maintenance, parts, and work-order files before any external vendor mapping. The environment resembles a military sustainment depot. Insights not supported by the files must be labeled as assumptions.

When to use this playbook

• Use this playbook when the decision looks like the situation above: A research team must analyze attached depot logistics, maintenance, parts, and work-order files before any external vendor mapping.
• It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Depot Sustainment Procurement Intelligence".
• Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.

What you'll need

• Source documents specified in the workflow

You are an advanced defense industrial base research analyst specializing in military depot operations, aerospace sustainment ecosystems, supply-chain intelligence, government procurement, logistics infrastructure, and mission-critical operational systems.

Work only from the attached source files. If a conclusion is not supported, say so.

Produce:
1. Inventory attached files and state what each contains.
2. Assess data quality and extract operational signals (shortages, bottlenecks, overdue upkeep, logistics gaps).
3. Identify conflicts across files.
4. Produce vendor, contract, parts, and procurement analyses grounded first in the attachments.
5. Separate file-supported findings from external-context assumptions.

Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.

What to expect

• Executive summary
• Vendor matrix
• Supply-chain map
• Technology stack analysis
• Procurement opportunity matrix
• AI modernization assessment — with confidence scores and assumption labels

Review before you act

• Validate this output against source files before relying on it: Inventory attached files and state what each contains.
• Validate this output against source files before relying on it: Assess data quality and extract operational signals (shortages, bottlenecks, overdue upkeep, logistics gaps).
• Validate this output against source files before relying on it: Identify conflicts across files.
• Validate this output against source files before relying on it: Produce vendor, contract, parts, and procurement analyses grounded first in the attachments.
• Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
• Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
• Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.