Timeline urgency

• What is the target decision or milestone date you are preparing for?
• Which of the following best describes what is driving this timeline? Options: Milestone B or C within 12 months, A failed test event requiring repeat testing, A new OT&E requirement beyond internal capacity, Other (briefly describe)

Decision authority

• Who is the single point of decision authority for approving independent test and evaluation work on this program? Please name the role. Options: Chief Test Engineer, Program Executive Officer, Acquisition Program Manager, Other (role)
• Will that decision authority or an authorized delegate be available for an initial discovery conversation within the next two weeks? Options: Yes — decision authority will attend, Yes — delegate will attend, Not available in next two weeks, Unsure

Funding and contracting

• Is funding for external independent testing currently allocated or expected within an approved funding window? Options: Yes, funds are allocated, Funds expected but not yet allocated, No funding identified, Unsure
• Which contracting route do you expect to use if we proceed to scoped work? Options: Existing contract vehicle or task order, New competitive procurement, Sole source or directed award, Not yet decided

Security clearances and data access needs

• What is the highest security classification level of range telemetry or program data that will be required for the engagement? Options: Unclassified, Secret, Top Secret or SCI (may require special handling), Uncertain — need to confirm
• Do you already hold the range, facility, or program-level authorities required for fieldwork and classified telemetry processing? Options: Yes — all required authorities in place, Partial — some authorities in place, No — none in place, Unsure

Framing the milestone and timeline

• Briefly describe the milestone decision you are preparing for and its target date.
• Rate the urgency of the timeline for that decision. Options: Critical, within 3 months, High, within 6 months, Medium, within 9-12 months, Flexible, beyond 12 months
• Who on your team will make the final go or no-go call for releasing the evaluation report? Options: Program Executive Officer, Chief Test Engineer, Acquisition Program Manager, Developmental Test Director, Other
• Select the funding window that covers this effort and indicate whether funds are already apportioned. Options: Current fiscal year, funded, Current fiscal year, not yet funded, Next fiscal year, planned, Multi-year funds available, Unclear/not apportioned
• Do you have the cleared personnel and facility access needed to handle classified telemetry and range work at the start of the engagement? Options: Yes, enough cleared personnel and facility access, Partial, some clearances needed, No, clearances or access will be required, We expect the seller to provide cleared resources

Where data gaps have hurt you before

• If your next test series produced ambiguous telemetry, what would be the immediate program impact?
• Walk me through the last test campaign where instrumentation or telemetry problems reduced usable data, what failed and how it was discovered.
• When range scheduling compressed your available windows, how did you choose which scenarios to run and which to drop?
• Who notices missing or unusable data first within your program, and what are the typical escalation steps?
• If you had to name one data gap that would make you stop the campaign immediately, which gap is it and why?

Decision makers, reviewers, and the standards they use

• Who signs the milestone decision memo, and what specific standards would make them reject an evaluation report?
• Describe the evaluation criteria your leadership requires for a defensible report.
• Identify the named stakeholders who must be interviewed or included in the test design and reporting chain. Options: Chief Test Engineer, Operational Test Representative, Safety Office, Data Owner, Contracting Officer Representative, Other
• Across your organization, who will be accountable for data release and who will be accountable for operational safety approvals?
• If the decision authority demands additional evidence beyond your current timeline, will you pause planning or proceed with contingency steps? Options: Pause and replan, Proceed with contingency plan, Escalate for additional funding/time, Unsure

Practical showstoppers and integration constraints

• Which single integration or access constraint would stop this engagement from proceeding?
• List the external systems that must integrate with the analytics environment and note whether public APIs or secure ingest endpoints exist.
• Who owns each required interface and can those owners commit engineering time for integration and testing?
• Estimate the number of cleared staff your program can dedicate to fieldwork and classified telemetry handling. Options: 0, 1-2, 3-5, 6-10, More than 10
• List regulatory approvals or security reviews likely to gate schedule, and provide typical lead times if known.
• If access to classified telemetry cannot be granted within your timeline, do you have an acceptable alternate path or will this engagement stop? Options: Alternate path exists, Alternate path possible but costly, No alternate path, engagement stops, Undecided

Defining what success looks like for the milestone

• What would a test outcome look like that clearly demonstrates your system meets its Key Performance Parameters?
• Walk me through the mission or operational scenarios that matter most to your milestone authorities and why they matter.
• Identify the threat representations that must be simulated, and note any that must intentionally be omitted.
• Describe the telemetry types and minimum sampling or fidelity requirements you consider required for defensible analysis.
• If achieving statistically meaningful results requires more runs than your available range window allows, would you trade scenario breadth for statistical depth or request additional range time? Options: Trade breadth for depth, Request additional range time, Adjust acceptance criteria, Undecided

Instrumentation, data channels, and handoffs

• If instrumentation misses even one critical data field during live events, what impact would that have on your milestone decision?
• Name the sensors and data channels that are nonnegotiable for your analysis and explain why.
• Describe your current process for validating sensor health and telemetry integrity before and during events.
• Tell me about your existing data pipelines, from collection to secure storage, and any known handoff points that will affect the seller.
• Select the data delivery model that best matches your program's preference. Options: Direct secure ingest to vendor analytics environment, Encrypted handoff to program-managed environment, On-site processing with sanitized deliverables, Hybrid approach, Other

Scheduling, safety approvals, and real-time contingencies

• What is the single range or safety risk that would force you to cancel a scheduled live event?
• When you prepare contingencies for live-fire tests, which failure modes tend to be underplanned?
• Who signs off on safety waivers and emergency response plans, and can they meet the timeframes required for your timeline?
• Name the real-time telemetry checks you require during execution to support immediate go or no-go calls.
• If a critical safety approval slips beyond your acceptable window, will you accept a reschedule, pursue an exception, or stop the program? Options: Accept reschedule, Pursue exception, Stop program, Undecided

The competitive landscape and internal alternatives

• Which alternative do you believe will produce a defensible evaluation that milestone authorities will accept?
• Tell me which external providers or approaches you are actively considering and why.
• Do any internal teams propose solving this without an outside partner, and if so who and what solution have they proposed?
• What would have to be true about your incumbent approach for you to remain with it rather than change vendors?
• Rank the reasons you would change providers, from strongest to weakest. Options: Data independence and credibility, Faster schedule, Lower overall cost, Better instrumentation and data fidelity, Stronger safety processes, Other
• If the incumbent committed to equivalent instrumentation and an independent data pipeline, would you likely stay with them? Options: Yes, No, Maybe, depending on contract terms, Unsure

Acceptance criteria, reporting cadence, and review gates

• If the test shows marginal compliance on a primary KPP, what concrete evidence would convince leadership to accept it?
• List the acceptance metrics that must appear in the final report for you to sign off and trigger billing.
• What is your required draft report delivery time after test completion, in calendar days? Options: 3 days, 7 days, 14 days, 30 days, Other
• Who will perform the technical quality review of the report before it reaches decision authorities? Options: Chief Test Engineer, Independent reviewer, Program technical lead, OT&E representative, Other
• If the draft report raises more than three clarifying questions, will you delay sign-off or accept a post-acceptance clarification process? Options: Delay sign-off until clarified, Accept post-acceptance clarifications, Require a rapid follow-up review, Undecided

Signals that accelerate the deal and next steps

• If a pilot proves the performance numbers you need, what would make you sign an engagement within the same week?
• Which actions from the seller would increase your confidence to proceed now? Options: Detailed test plan within two weeks, Named test director and resumes, Signed SOW template, Proof of cleared data environment and access, Other
• Who needs to be present at a kickoff and can those people be available within two weeks of contract award?
• Select your preferred contracting vehicle or procurement path. Options: Existing IDIQ or BPA task order, Firm fixed price task order, Cost reimbursable task order, Sole source justification, Other
• What single contractual or budget obstacle would stop you from signing within your target window?

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Data Access and Classified Telemetry Processing Agreement
• Range Access and Safety Compliance Agreement
• Facility Clearance and Personnel Vetting Addendum
• Payment Schedule & Initial Deposit Authorization
• Change Order Agreement

• Kickoff Assumptions and Test Objectives Workshop
• Threat-Representative Scenario Co-design Workshop
• Telemetry Schema and Instrumentation Requirements Design
• Evaluation Criteria, Analysis Plan, and Deliverable Agreement

• Document the contingency decision rules for incomplete data and schedule any required follow-up decision meetings.
• Document the list of required threat assets, instrumentation checkpoints, and range constraints for each scenario.
• Confirm preliminary range windows and threat asset availability or flag schedule conflicts for mitigation.
• Review scenario measurement points and data needs
• A complete telemetry specification document with fields, sampling, and time synchronization requirements.
• A sensor placement and interface plan that supports all scenario measurement points and identifies calibration and redundancy needs.
• A documented data flow diagram including ingest endpoints, processing handoffs, security levels, and validation checks.
• Produce and circulate the telemetry schema and sensor placement draft for technical review.
• Inventory required sensors, cabling, and spare parts and flag any procurement lead times that affect the schedule.
• Schedule an instrumentation dry run and data ingest test before range execution windows.
• Recap objectives, scenarios, and telemetry constraints
• A ratified evaluation plan that maps metrics to KPPs and specifies calculation methods.
• Agreed pass/fail thresholds, statistical confidence requirements, and the definition of acceptable data completeness.
• A documented deliverable list with formats, review cycles, acceptance gates, and the billing trigger.
• Publish the evaluation plan and report deliverable checklist for formal sign-off.
• Confirm analytic tool endpoints, access requirements, and data format expectations for ingestion into the processing environment.
• Confirm engagement scope and decision drivers
• A finalized list of test objectives mapped to KPPs with named owners and target dates.
• A prioritized objective list showing which objectives are in-scope for the upcoming test window and which are deferred.
• A documented list of open assumptions and missing inputs that must be provided before the scenario workshop.
• Publish the prioritized test objectives summary with owners and target dates for asynchronous review.
• Collect and circulate the authoritative KPP definitions and any existing test artifacts referenced during the session.
• Schedule the Threat-Representative Scenario Co-design Workshop and circulate required pre-work materials.
• Recap prioritized objectives and required decision evidence
• A scenario matrix listing each threat-representative scenario with fidelity level and scenario narrative.
• Clear acceptance criteria and measurement points for every scenario, with named owners and an execution timeline.
• A list of scenario dependencies and risks that could affect schedule or fidelity.
• Publish the scenario matrix, including narratives, fidelity levels, acceptance criteria, and owners.
• Specify telemetry schema, sampling rates, and timestamps
• Define evaluation metrics and mapping to KPPs
• Map program decisions and KPPs to candidate test objectives
• Define threat models and fidelity requirements
• Define sensor placements, interfaces, and calibration needs
• Prioritize objectives by decision impact and schedule risk
• Set performance thresholds, pass/fail rules, and statistical requirements
• Draft scenario narratives and event sequencing
• Agree report deliverables, formats, and acceptance gates
• Design data flow, ingest endpoints, and processing handoffs
• Assign owners and target completion dates
• Set scenario acceptance criteria and measurement points
• Assign scenario owners and timeline to execute
• Agree data security, retention, and validation checks
• Document contingencies and decision paths for incomplete data
• Confirm open assumptions and next steps

• Range Instrumentation and Sensor Installation
• High-Speed Telemetry Data-Acquisition Integration
• Ballistic and Flight Sensor Calibration Verification
• Threat-Representative Target and Munition Deployment
• Operational Scenario Fielding and Adversary Simulation
• On-Range Test Direction and Live-Fire Execution
• On-Range Safety Officer and Range Clearance Liaison
• Secure Telemetry Ingest to FedRAMP Analytics
• Telemetry Data Reduction and KPP Metric Extraction
• Anomaly Reconstruction and Forensic Data Package
• Decision-Ready Milestone Test Report with Appendices
• Raw Telemetry Archival and Classified Deliverable Transfer

Range Instrumentation and Sensor Installation

• Provide the range layout diagram with grid coordinates and planned sensor locations (attach CAD, KML, or PDF).
• List available power and network drop locations by grid coordinate and voltage level (for example 120VAC, 48V DC).
• Confirm power conditioning or uninterruptible power supply (UPS) requirements for instrumentation racks. Options: Yes, No
• Which sensor models or part numbers (inertial measurement unit, pressure transducer, high-speed camera) do you require installed? Provide serial numbers if available.
• Who is the onsite range liaison or range master providing electronic access credentials and schedule approvals?
• Specify mounting interfaces and fixture drawings for each sensor placement (pole mount, tower bracket, vehicle-mount drawing references).

High-Speed Telemetry Data-Acquisition Integration

• Attach the telemetry schema or example binary packet definition, including schema version and field names (CSV, JSON schema, Protocol Buffers).
• Indicate preferred data-acquisition sample rates per channel (for example 100 kHz for accelerometers, 500 Hz for GPS). Options: Provide rates, We need recommendation, Other
• Identify any proprietary DAQ drivers, middleware, or firmware versions we must integrate with and provide driver version and build artifacts.
• Describe your onboard time synchronization method and required timestamp accuracy (GPS pulse-per-second (PPS), Precision Time Protocol (PTP), Network Time Protocol (NTP); specify jitter tolerance in microseconds or milliseconds). Options: GPS PPS, Precision Time Protocol (PTP), Network Time Protocol (NTP), Other
• State the maximum sustained data throughput expected to the ingest endpoint in megabits per second (Mbps).
• Estimate cable run lengths from each instrument to the DAQ rack by grid coordinate or route ID.

Ballistic and Flight Sensor Calibration Verification

• Select required calibration standards or procedures (for example National Institute of Standards and Technology traceable, factory calibration, in-field check). Options: NIST-traceable, Factory calibration, In-field check, Other
• Are there existing calibration certificates for the sensor serial numbers to be used? If yes, provide certificate identifiers. Options: Yes, No
• When was the last calibration performed for each ballistic or flight sensor? Provide serial number and calibration date.
• What calibration tolerances are acceptable for gyroscopes and accelerometers (for example bias drift in deg/hr, scale-factor percent)?
• How will environmental factors be validated during calibration (for example thermocouple placements, thermal chamber logs, vibration profile references)?
• Name the laboratory or technician performing calibration and provide the calibration procedure document reference or revision.

Threat-Representative Target and Munition Deployment

• Choose primary target types and identify target serial numbers or asset IDs planned for the campaign.
• Detail munitions lot numbers, fuzing profiles, and delivery platform identifiers that will be used in threat-representative engagements.
• Will inert, live, or telemetry-equipped munitions be used? Select all that apply. Options: Inert, Live, Telemetry-equipped
• Specify target emplacement instructions and spawn parameters for threat generation (elevation, aspect angle, radial distance, scripted waypoint IDs).
• Who is responsible for ordnance handling, including credentials and weapons-specific certifications on-range (provide credential titles and expiry dates)?
• Provide required handling and storage constraints for munitions (temperature range, magazine spacing, chain-of-custody requirements) and any explosive safety data sheet references.

Operational Scenario Fielding and Adversary Simulation

• List the operational scenarios by name and attach the scenario script or mission timeline (include threat script IDs where applicable).
• Confirm adversary simulation fidelity requirements such as radar cross-section signature profiles, electronic warfare waveform catalogs, or decoy behavioral models. Options: High fidelity, Moderate fidelity, Low fidelity
• Which communications interfaces must be simulated (for example Link-16, SINCGARS, custom datalink)? Provide waveform or protocol specification documents.
• Identify required validation traces for scenario fidelity such as synthetic RCS logs, RF waveform captures, or signature replay logs.
• Describe collision and deconfliction rules for maneuvering targets and free-flight assets in the scenario, including separation minima and safety buffers.
• State any classification level or handling instructions for adversary software, threat libraries, or scenario content. Options: Unclassified, Confidential, Secret, Top Secret

On-Range Test Direction and Live-Fire Execution

• Estimate the number and roles of onsite direction staff you will provide (for example test director, safety officer, telemetry engineer). Options: 1-2, 3-5, 6+
• Attach the statement of work (SOW) tasking for on-range test direction, if available, including deliverable milestones and acceptance gates.
• Indicate required environmental windows (wind speed, sea state, visibility) and pass/fail thresholds to be enforced in the test plan.
• What real-time telemetry dashboards or specific performance indicators must be visible to range leadership during live-fire (list dashboard IDs or KPIs)?
• How many discrete live-fire events or shots are planned in the campaign? Options: 1-5, 6-20, 21+
• Provide names and certification levels of the proposed test director and range safety lead and attach credentials.

On-Range Safety Officer and Range Clearance Liaison

• List serial numbers or identifiers for any high-risk assets requiring special safety handling (for example propellant lots, energized systems).
• Confirm required range safety approvals and expected delivery dates for the range safety authorization paperwork. Options: Pre-approved, Pending, Buyer to procure
• Which ammunition types require site-specific explosive safety submissions and quantity-distance (QD) analyses? Provide the QD study reference if available.
• Describe emergency response plans and medical evacuation (MEDEVAC) coordination required on-range, including nearest medical facility and response times.
• Name the primary on-range safety officer and backup, including contact information and credential expiration dates.
• Specify the chain-of-custody and handoff procedure for ordnance from storage to firing point, including required signatures and documentation fields.

Secure Telemetry Ingest to FedRAMP Analytics

• Provide the ingest endpoint URL, transport protocol (for example SFTP, HTTPS, AMQP), and expected authentication method (certificate, token).
• List the Federal Risk and Authorization Management Program (FedRAMP) authorization level and artifacts required for the analytics environment. Options: FedRAMP Low, FedRAMP Moderate, FedRAMP High, Not required
• Confirm encryption at rest and in transit requirements, including required cipher suites or key management service (KMS) specifications.
• Which firewall and VPN tunnel configurations must be established (provide IP ranges, port lists, and VPN profile names)?
• Identify expected file formats and compression for ingest (for example JSON, Protocol Buffers, TAR.GZ) and any expected partitioning scheme.
• Provide acceptance criteria for successful ingest to the Federal Risk and Authorization Management Program (FedRAMP) analytics environment (acceptable packet loss percentage, time-to-first-byte, and data integrity checksum thresholds).

Telemetry Data Reduction and KPP Metric Extraction

• State the Key Performance Parameters (KPP) and their measurable metrics, including numeric target thresholds and explicit pass/fail logic for each KPP.
• What data reduction algorithms and specific filter parameters are mandated (for example Kalman filter state dimension, low-pass cutoff frequency in Hz)?
• How will timebase alignment be validated between flight sensors and ground telemetry? Provide expected jitter tolerance in milliseconds.
• Which quality-assurance flags or rejection rules should be applied to sensor channels (for example saturation threshold, dropout duration, clock slip limits)?
• Provide a representative reduced-data product schema and attach one example output row for a single event (field names, units, and types).
• Identify baseline performance cases or historical runs to be used as control comparisons for metric extraction (provide run IDs or dates).

Anomaly Reconstruction and Forensic Data Package

• Describe the minimum contents required in a forensic package (for example raw waveforms, trigger logs, time-synced video, chain-of-custody manifest).
• Which sensors' raw streams must be preserved at full fidelity for reconstruction? List channel names and sensor serial numbers.
• Are there legal holds, investigative holds, or classification constraints that will impact the timing or format of forensic exports? Options: Yes, No
• What timeline do you require for delivery of an initial forensic package after an anomaly (select fastest acceptable option)? Options: Within 4 hours, Within 24 hours, Within 72 hours, Custom
• Who is the designated anomaly review authority that will accept the forensic package and sign the chain-of-custody?
• Provide the preferred forensic archive format and checksum method (for example SHA-256 on TAR.GZ) for transfer and long-term storage.

• desired_state
• current_state
• stakeholders
• gaps
• success_criteria
• decision_readiness
• desired_state
• decision_readiness
• current_state
• success_criteria
• gaps
• stakeholders
• desired_state
• success_criteria
• decision_readiness
• stakeholders
• gaps
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Receive written acceptance sign-off for the final evaluation report from the designated buyer approver(s)
• Resolve and close all buyer clarifying questions logged during the report review
• Confirm final report file is versioned and archived in the platform-controlled repository
• Obtain written range and safety authority approval for inclusion and distribution of telemetry or controlled test data
• Verify classification and distribution permissions for all report attachments are documented
• Issue invoice tied to the formal acceptance sign-off to trigger billing
• Submit the final report and required compliance package to the applicable oversight authority(ies)
• Obtain and attach acknowledgment of receipt from oversight authority(ies)
• Record formal sign-off, invoice reference, and submission evidence in the shared journey workspace log
• Export and transfer open post-delivery issues to the Sustain & Support stage

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• 90-day Remediation and Incumbent Wind-down Review (around day 90)
• Quarterly Sustain & Support Review (ongoing quarterly)

• Circulate a quarterly sustainment summary that includes the trends for unresolved issues and mean time to resolve.
• Remediation closure review
• All remediation items are closed or have firm conditional closure plans with dates, moving the engagement to sustainment.
• The incumbent validation process is either decommissioned or formally retained read-only with archival and contract closure documented.
• Publish remediation closure evidence and update the project tracker to reflect closed and conditional items.
• Record the incumbent wind-down decision, archive legacy data as required, and document fallback procedures if retained read-only.
• Produce a short lessons-learned brief with three prioritized improvements and recommended implementation owners for follow-on planning.
• Trend review for core sustainment metrics
• Sustainment metrics show improving or acceptable trends or have documented remediation plans to return them to target.
• A near-term support backlog with prioritized items and expected resolution dates is agreed for the quarter.
• Update the support backlog with prioritized remediation tasks and publish expected resolution dates for the quarter.
• Schedule any preventive instrumentation maintenance or configuration updates required before the next test window.
• Reconfirm success criteria and owners
• All critical data-access and ingestion paths are confirmed operational or have an agreed remediation plan.
• A prioritized list of open blockers with remediation owners and target close dates is agreed.
• Publish the deployment validation checklist and telemetry sample summary for async review within 48 hours.
• Document each open blocker with impact, priority, and a target resolution date in the shared workspace.
• Schedule the first measurement review once at least 80 percent of critical blockers are trending to closure.
• Present first-window metrics vs targets
• Quantified gaps against the targets in Test & Reporting Scope are documented with root causes identified.
• Concrete remediation plan and timeline for each shortfall, including any required repeat-test window, are agreed.
• Produce a remediation tracker listing each metric shortfall, root cause, remediation tasks, and target close dates.
• Publish a schedule request for any repeat-test windows needed to collect missing telemetry, with preferred ranges and constraints.
• Confirm archival location and access permissions for the initial-event raw telemetry and metadata.
• Deployment and data-access validation
• Incumbent wind-down status
• Instrumentation maintenance and configuration drift
• Root-cause diagnosis for gaps
• Agree corrective actions and deadlines
• Early telemetry sanity checks
• Open support queue triage
• Follow-on instrumentation or repeat-test commitments
• Confirm data archival and chain-of-custody status
• Capture specific lessons learned
• Capture continuous-improvement items
• Open issues and blockers