Quick readiness snapshot

• Give a two-sentence summary of why fleet readiness is a concern right now.
• In the last 12 months, how many percentage points has your reported fleet availability dropped relative to the program KPP? Options: Less than 3 points, 3–7 points, 8–15 points, More than 15 points, Don't have a consolidated number
• Which trigger most closely matches why you opened this review? Options: Readiness below Key Performance Parameter (KPP), Deployment surge with 90-day readiness target, Sustainment contract recompete, Reactive high failure rate or safety issue, Other
• Who on your team will be the final approver for a contractor assumption of sustainment responsibility? Options: Program Manager / PM, Product Support Manager, Logistics Colonel / equivalent, Depot Maintenance Director, Program Executive Officer (PEO), Other
• If availability improved to your target within 90 days, what immediate operational capability or mission would that restore?

Where availability is actually slipping

• Which single maintenance shortfall, if fixed this week, would raise your fleet availability above the program KPP?
• Walk me through a recent failure event: what failed, where (depot, field site, or supply node), and how long did it take to detect and route the repair?
• How many maintenance man-hours per platform are currently backloged beyond your SLA at depot and at forward sites? Options: <10 hours, 10–50 hours, 51–200 hours, >200 hours, Not measured
• What breaks downstream when depot throughput drops by about 20 percent, in terms of sortie rate, training readiness, or mission staging?
• Which specific platform variants or subsystems are contributing most to the availability shortfall? Options: Full platform fleet, Specific variant(s), Engine/propulsion, Avionics/electronics, Weapon or mission systems, Other

Parts, obsolescence, and the supply pinch

• If a critical part went obsolete today, how long until mission-capable rates would meaningfully drop for the affected units? Options: Within weeks, 1–3 months, 3–6 months, More than 6 months, Unsure
• Which spare parts families currently create the longest lead times at forward locations? Options: Electronic modules and PCBs, Hydraulic components, Avionics LRUs, Specialized fasteners/structural, Proprietary consumables, Other
• Describe your current parts provisioning model for forward sites and who owns replenishment decisions.
• What would need to change for you to accept a vendor-managed pre-positioned inventory model as the primary provisioning strategy?
• What single parts constraint would stop you from moving to a contractor-led sustainment model?

People, skills, and the knowledge handoff

• When the incumbent workforce does not transfer, what operational capability disappears first?
• List the certifications, clearances, and MOS/AFSC or equivalent skill codes your frontline technicians must hold to operate at your sites. Options: DoD security clearance, Military MOS/AFSC required, Manufacturer/OEM certification, Avionics/flight line certs, Electrical/mechanical trade certs, Other
• How many technicians would you need onsite at a typical deployed location to meet a 90-day surge maintenance target? Options: Fewer than 10, 10–25, 26–50, 51–100, More than 100, Varies by site
• Who will retain institutional knowledge inside your organization if the incumbent moves on and key personnel do not transfer?
• If less than half of the incumbent technicians accepted transfer, would you still proceed with contractor assumption? Options: Yes, proceed, No, pause transition, Proceed only with mitigation plan, Unsure

What risks are keeping leadership up at night

• Which single program risk could cause leadership to pause or cancel a transition?
• Rank the top three risk categories that concern you most right now. Options: People and workforce transfer, Parts and obsolescence, Depot throughput, Data ownership and transfer, Contracting and governance, Funding and budget timing
• Walk me through the last close call where readiness nearly failed—what intervened and why did it come close?
• Are there any regulatory approvals, ongoing legal reviews, or classified handling requirements that would block a 90-day transition? Options: Yes, regulatory approvals pending, Yes, legal or contracting review pending, Yes, classified handling constraints, No known gating approvals, Unsure
• What contingency would you require to accept schedule slippage of more than 30 days on a transition?

The alternatives you're weighing

• Why would you keep the incumbent or attempt to solve this internally instead of moving to an external sustainment partner?
• Which alternatives are you actively evaluating right now? Options: Incumbent contract renewal, Internal capability build, Another external contractor, Hybrid partner model, OEM sustainment arrangement, No decision yet
• What would have to be true about your current approach for you to stay with it instead of switching to an external partner?
• Has anyone on your staff proposed solving this without an outside vendor, and if so, who owns that proposal and the budget estimate? Options: Yes, program office owns it, Yes, maintenance command owns it, No internal proposal, Other
• If a pilot restored availability on a representative cluster to target, what would stop leadership from approving a full transition within 30 days?

Operational readiness and integration constraints

• Which integration failure, such as broken API, missing data feeds, or incompatible CMMS formats, would force you to halt a contractor takeover immediately?
• Which core systems must we integrate with to operate successfully (select all that apply)? Options: Logistics ERP / financial system, CMMS / maintenance information system, Inventory management system, Predictive analytics/health monitoring, Supply chain EDI / parts ordering, Other
• Please name the organization or office that owns each critical integration and provide the contact role that can provide API credentials and access.
• Is the maintenance and supply data you depend on timestamped, versioned, and extractable; if not, what percentage would you estimate is usable within two weeks? Options: >90% usable, 60–90% usable, 30–59% usable, <30% usable, Unknown
• What infrastructure prerequisites must be in place before physical transition begins (site access, IT network changes, classified enclaves, security clearances)?
• Are there contractual clauses, union constraints, or funding windows that would legally prevent a contractor from assuming responsibility within 90 days? Options: Yes, contractual constraints, Yes, union/HR constraints, Yes, funding window mismatch, No legal obstacles identified, Unsure

How you will know we succeeded

• What exact availability number, measured how, would prove to your boss that the change worked?
• Which KPIs do you currently report monthly that would be part of an acceptance package? Options: Fleet availability, Mean time to repair (MTTR), Depot turnaround time, Forward fill rate, Technician retention, Predictive failure accuracy
• How often does leadership require a readiness report and which formats are acceptable (briefing slides, live dashboard, formal report)? Options: Daily, Weekly, Bi-weekly, Monthly, Quarterly
• If a pilot met the KPIs but the incumbent refused to transfer workforce, would you still accept contractor responsibility for sustainment? Options: Yes, with mitigation, No, workforce transfer required, Only for a limited scope, Unsure
• What acceptance test or verification would you require at day 90 to sign the handover as complete? Options: Operational availability threshold met, Workforce absorption verified, Inventory and parts staged, Data and access handed over, All of the above

Decisions, timing, and next steps

• If everything aligned, what is the earliest calendar date you could commit to contractor assumption of sustainment responsibility?
• Which resources can you commit now to shorten the schedule (site badges, prioritized data extracts, transitional funding, onboarding liaisons)? Options: Site access and badges, Priority data extracts, Transitional funding, Onboarding liaison/team, None available now
• Walk me through your internal approval chain and typical lead times from the program office up to the service acquisition executive.
• If a short pilot proved the numbers on readiness and cost, would your approval chain allow signature within 30 days? Options: Yes, signature within 30 days, No, requires longer review, Only with executive-level buy-in, Unsure
• Which single deliverable or piece of evidence would accelerate your decision to a 'yes' this quarter?

• Solution Experience, Readiness Recovery Walkthrough

• Confirm the current state and what it is costing you
• You confirm the demonstrated workflow removes the depot throughput and parts lead-time failures you described.
• Provide the canonical operational scenario details to be used for the model, including unit, mission timeline, readiness target, and top failure modes.
• You accept the modeled time-to-availability for the chosen scenario and note any remaining gaps to decision.
• Agree the scenario we will test
• Share current depot throughput metrics, average repair turnaround times, and spare parts lead-time data for the tested platform.
• Map the scenario across depot, field, and supply chain
• Run the scenario through the sustainment model and deliver a validated readiness recovery plan with timeline and key risk mitigations before the follow-up session.
• You validate the assumptions and list any constraints that would prevent implementation within the 90-day window.
• Prove the sustainment flow end-to-end on the scenario
• Identify any site access, regulatory, or workforce-transfer constraints that could affect the transition plan.
• Show supporting evidence and expected outcomes
• Validate assumptions and constraints
• Validate the future state outcome

• Solution Experience: Readiness Recovery Walkthrough
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Depot Overhaul and Component Refurbishment
• Field Service Repair and On-Site Maintenance
• Deploy Embedded Technician Teams
• Predictive Failure Alerts and Automated Work Orders
• Spare Parts Kitting and Forward Pre-Positioning
• Procure and Expedite Critical Spare Parts
• Reverse-Engineer and Fabricate Obsolete Components
• Qualification Testing for Repaired or Fabricated Parts
• Develop and Deliver Technical Repair Manuals
• Manage Forward Inventory Replenishment to 98% Fill
• Depot Functional Test, Calibration, and Certification
• 90-Day Workforce Knowledge Transfer and Handoff
• Implement Field Modifications and Engineering Changes
• Deliver Fleet Availability and Readiness Reporting

Depot Overhaul and Component Refurbishment

• Which component families (by National Stock Number or part number) do you expect to route to depot overhaul under your Performance Work Statement (PWS)?
• How many maintenance work orders per month for depot-level overhaul does your program currently generate for the affected platform? Options: Less than 50, 50-200, 201-500, More than 500
• List the governing technical manuals, technical data packages, or OEM specifications that must be followed during depot refurbishment (for example document IDs or revision numbers).
• Identify required traceability markings and serialization requirements for refurbished components (for example serial number retention, date codes, or CAGE traceability).
• Specify the maximum acceptable depot turnaround time (TAT) per overhaul work order that the contract must meet (hours or calendar days). Options: 7 days, 14 days, 30 days, Custom
• Which depot facilities, test benches, or National Institute of Standards and Technology traceable (NIST-traceable) calibration labs are prequalified to perform the refurbishment work on your platform?

Field Service Repair and On-Site Maintenance

• Which on-site maintenance activities from the maintenance allocation chart (MAC) do you require at forward locations (for example replace assemblies, alignment, software load)?
• How many field service events per quarter do you forecast at each forward operating location based on your historical maintenance logs? Options: 0-10, 11-50, 51-200, 200+
• Who on your operations team will provide site access approvals and local point-of-contact for lockout/tagout and hazardous material handling during on-site repairs?
• Describe required environmental or handling constraints for field repairs (for example temperature range, clean room level, or corrosive atmosphere controls).
• Which Maintenance Work Order (MWO) or work request codes must field technicians reference when completing on-site repairs for your records?
• Which consumable and support kit items must be staged with each field team per dispatch (for example fasteners by part number, seal kits by NSN, calibration gas cylinders)?

Deploy Embedded Technician Teams

• How many embedded technicians do you expect to be colocated at each site, and what is the desired shift coverage (for example 8-hour, 12-hour, 24/7)? Options: 1-2 per site, 3-5 per site, 6-10 per site, Custom
• Which personnel qualifications or certifications must embedded technicians hold (for example military occupational specialty code, civilian certification, security clearance level)?
• Who on your side will manage onboarding steps such as base access, visitor credentials, and system accounts for embedded technicians?
• Specify required equipment and tooling that must accompany embedded teams (for example calibrated torque tools, portable test sets, laptop with CMMS credentials).
• Where will technician workspace and secure storage be located on site for government-furnished equipment and contractor property?
• What minimum retention or tour length do you require for embedded technicians to preserve institutional knowledge (months)? Options: 3 months, 6 months, 12 months, Other

Predictive Failure Alerts and Automated Work Orders

• Which telemetry types from your platforms will feed predictive analytics (for example vibration spectra, oil debris sensors, temperature logs, hours-run counters)?
• Which integration endpoint should receive automated work orders from predictive alerts (for example your current computerized maintenance management system CMMS endpoint or API)?
• How much lead time from an automated alert to required intervention is acceptable for your operations (for example 2 weeks, 1 week, 72 hours)? Options: 2 weeks, 1 week, 72 hours, 24 hours
• Identify the failure modes or fault signatures you prioritize for predictive monitoring (for example bearing wear, hydraulic leak signatures, avionics bit-errors).
• Describe the format and minimum fields your work order must contain when created automatically (for example NSN, part number, priority code, site location, symptom code).
• Which access method or protocol does your telemetry endpoint use for ingestion (for example secure FTP, REST API with token, MQTT over TLS)? Options: Secure FTP, REST API (token), MQTT over TLS, Other

Spare Parts Kitting and Forward Pre-Positioning

• Which bill of materials or kit lists (by assembly PN or NSN) should be converted into forward pre-positioned kits?
• How many supply nodes will hold pre-positioned kits and what are their storage constraints (for example temperature-controlled, explosive safety distance)?
• Specify the required packaging and labeling standard for kits (for example MIL-STD packaging, tamper-evident seals, NSN and CAGE on label).
• Which required stockage objective or reorder point methodology do you use today (for example RSO by NSN, min-max, demand-driven forecasting)? Options: Required Stockage Objective (RSO), Min-Max, Demand-driven forecast, Custom
• Which hazardous or shelf-life-limited items appear in kits and what shelf-life rotation policy must apply (for example chemical agent, batteries by lot and expiration date)?
• Who on your logistics team approves kit compositions and change notices to the kit BOM?

Procure and Expedite Critical Spare Parts

• Which critical parts are single-source or at risk of diminishing manufacturing sources (list NSNs or part numbers and CAGE codes where known)?
• How many days is your acceptable procurement lead time for critical spares under expedited conditions? Options: 3 days, 7 days, 14 days, 30+ days
• Which contracting vehicle or purchase order type must be used for expedited buys (for example government purchase order, blanket purchase agreement), and who issues it?
• Specify required vendor qualifications for critical items (for example ISO 9001, AS9100, ITAR compliance, source inspection).
• Which shipping priorities and routing preferences must be used for expedited shipments to forward locations (for example military airlift, commercial overnight with customs brokerage)?
• What acceptance documentation must accompany procured parts at receipt (for example Certificate of Conformance, test report, packing list with NSN)?

Reverse-Engineer and Fabricate Obsolete Components

• Which obsolete parts (by part number or NSN) lack a usable technical data package and therefore require reverse engineering?
• What physical artifacts can you provide for reverse engineering (for example representative serviceable units, teardown samples, engineering drawings)?
• Specify intellectual property or data rights constraints that bound reverse engineering and on what authority they are documented (for example licensing limitations in the contract or existing data rights statements).
• Which fabrication technologies are acceptable for producing legacy parts (for example CNC machining to specified tolerances, additive manufacturing with material certification)? Options: CNC machining, Additive manufacturing (3D printing), Sheet metal forming, Hybrid processes
• Identify the dimensional tolerances, material specifications, and acceptance test points that must be preserved when fabricating replacements.
• Who on your engineering staff will approve reverse-engineered drawings and release a new drawing revision for production?

Qualification Testing for Repaired or Fabricated Parts

• Which test standards or qualification regimes apply to repaired or fabricated parts (for example MIL-STD environmental tests, SAE standards, OEM bench test procedures)?
• Which test fixtures, harnesses, or functional test benches will be used and where are they located (provide lab IDs or location names)?
• Describe minimum documentation that must accompany qualified parts (for example signed test report with serial number, calibration sticker, lot traceability).
• Which environmental and stress tests must be performed during qualification (for example vibration, thermal cycling, humidity, EMI/EMC), and to which test levels?
• Who must witness qualification tests or accept test results on behalf of the customer (for example government test witness, third-party lab)?
• Specify whether sample sizes for qualification are single-unit, lot-sample, or full-run acceptance and any associated acceptance thresholds. Options: Single-unit, Lot sampling, Full-run

Develop and Deliver Technical Repair Manuals

• Which existing technical manuals or technical data packages (list identifiers and revision numbers) must be updated or converted as part of this scope?
• Which formats do you require for repair documentation delivery (for example searchable PDF with bookmarks, interactive electronic technical manual, paper binders)? Options: Searchable PDF, Interactive electronic technical manual, Paper binder, Other
• Identify mandatory content elements for each repair procedure (for example safety warnings, step-by-step torque values, required tool part numbers, illustrations).
• What configuration management process must be used for revision control of manuals (for example change notice number, revision tree, controlled distribution list)?
• Who on your logistics or engineering staff will sign off on technical manual revisions prior to field release?
• Specify any export control or redaction requirements for delivered technical publications (for example remove cryptographic detail, redact restricted schematics).

Manage Forward Inventory Replenishment to 98% Fill

• What is the current fill rate at each forward supply point by NSN, and which nodes fall below the 98% target?
• Which inventory tracking system will be the authoritative source for fill-rate calculations (for example your current supply system or CMMS inventory module)?
• Which reorder policy and lead-time assumptions should be used to sustain a 98% fill rate at the required nodes (for example safety stock days, reorder point formula)?
• What evidence will validate 98% fill at each forward supply point (for example weekly inventory snapshot by NSN signed by your supply officer)?
• Which exceptions are allowable against 98% fill (for example non-repairable items, prohibited-for-sale items, long-lead obsolescence), and how should they be reported?
• Who on your supply chain team will receive and approve fill-rate exception reports and periodic reconciliations?

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Performance Metrics & Payment Matrix
• Transition Services Agreement (TSA) & Milestone Schedule
• Transition Acceptance Certificate
• Governance and Escalation Agreement
• Workforce Transfer and Labor Assurance Agreement
• Parts Provisioning & Inventory Agreement
• Change Order and Modification Agreement
• Security, Procurement and Performance Compliance Rider

• Go-live Health Check (weeks 1-4)
• First Measurement Review (30-60 days)
• Operational Readiness Quarterly Review
• Annual Readiness Review and Compliance Check

• Produce a compliance summary demonstrating incumbent decommissioning status and archival integrity for audit purposes.
• Produce an incumbent wind-down confirmation package showing decommissioning actions, archived datasets, and access controls.
• Schedule a technical detailed review for any root causes requiring tooling or integration fixes within 7 business days.
• Rolling 90-day KPI performance vs Solution Scope targets
• Validate whether quarter-to-date fleet operational readiness rate and mean time to repair meet acceptable variance from Solution Scope targets.
• Reduce the critical ticket backlog and confirm SLA adherence improvements for recurring incident types.
• Approve a prioritized short list of operational improvements with timeline commitments for the next quarter.
• Move top 5 critical tickets into an agreed-resolution sprint with target dates and measurable acceptance criteria.
• Execute the next-stage parts procurement accelerations for long-lead items and publish expected in-stock dates.
• Schedule and record a workforce skills refresh session for technicians identified as below proficiency thresholds.
• Executive KPI summary vs Solution Scope targets
• Formally confirm whether annual performance meets the Solution Scope targets or document approved exceptions and remediation timelines.
• Close out high-impact incidents with documented root-cause fixes and evidence of sustained remediation.
• Agree the upcoming year review cadence and any SLA changes required to sustain target performance.
• Publish the annual KPI dossier with evidence and variance analysis into the shared workspace.
• Convert approved enhancements into project or ticket workstreams with delivery windows for the next 12 months.
• Reconfirm success criteria and owners
• Confirm the deployment components listed in Transition Configuration are present and functioning.
• Surface and document the top 5 operational blockers with target resolution dates.
• Agree immediate remediation actions to prevent mission-impacting outages during the onboarding window.
• Publish a go-live validation report documenting current state, open issues, and owners into the shared ticketing cadence.
• Log critical blockers into the shared ticketing system with severity and target resolution dates.
• Confirm site access, tooling credentials, and inventory staging readiness and record any outstanding access gaps.
• Present first-period KPI performance
• Determine whether fleet operational readiness rate and forward location parts fill rate are on trajectory to meet Solution Scope targets and document any shortfalls.
• Close the incumbent wind-down loop by confirming decommissioning, archived data integrity, and the absence of legacy fallback activity.
• Agree corrective actions with owners and firm resolution dates to drive metrics to the acceptance window.
• Record corrective actions with owners and due dates in the shared ticketing system and set SLA expectations for each item.
• Initiate expedited parts provisioning steps for any items causing low fill rates and document expected replenishment dates.
• Deployment and migration validation
• Major incidents and root-cause review
• Root-cause diagnosis for KPI gaps
• Ticketing and SLA cadence review
• Early adoption and workforce onboarding signals
• Incumbent wind-down and data migration status
• Obsolescence and parts backlog assessment
• Enhancements and backlog ratification
• Corrective action plan and timeline to acceptance
• Workforce health and retention status
• Compliance and contractual obligations check
• Open issues and blockers
• Next-year monitoring cadence and SLA confirmations
• Prioritized operational action plan
• Immediate remediation plan
• Ticket burn-down and enhancement request review