Start: Tell Us About the Program

• Help us get oriented — what's the program name, its primary objective, and the hardware you're characterizing?
• Who should we treat as the program owner or primary point of contact? Options: Senior RF Engineer, Test Engineering Manager, Program Manager, Procurement, Lab Manager, Other
• Which vertical best describes this program? Options: Aerospace/Space, Defense, Wireless / 5G, Telecom Infrastructure, Automotive, Other
• What is the target launch or critical milestone date for this program? Options: Within 2 weeks, Within 1 month, 1–3 months, 3–6 months, 6+ months, No set deadline
• What instruments are you using today, and in one sentence, where do they fall short for this program?

Why Change Now? The Pressure You're Facing

• If your current instruments can't make the measurement, what's the real cost to the program—missed milestones, failed qualification, rework, or worse? Options: Missed delivery milestones, Failed qualification, Design rework, Program cost overruns, Loss of contract, Schedule slippage to next phase, Other
• Which specific measurement gap or frequency limit triggered this evaluation? Options: Upper frequency limit (mmWave), Phase noise floor, Dynamic range / sensitivity, Pulse/timing analysis, Modulation/analysis software missing, Other
• Who raised the requirement—an external customer, internal design, supplier test spec, or a regulatory body? Options: External customer, Internal design team, Supplier/partner, Regulatory/standard body, Other
• How long has this limitation been affecting your ability to meet program goals? Options: Just discovered, Weeks, Months, Long-standing (years)
• If you had to prioritize fixing this now versus later, where would it fall? Options: Critical — must fix immediately, High — within weeks, Medium — within months, Low — exploratory

The One Measurement That Could Break the Deal

• Which single parameter — and its numeric threshold — would immediately disqualify an instrument if missed? Options: Phase noise (please specify dBc/Hz), Dynamic range (dB), Amplitude accuracy (dB/%), Frequency coverage (GHz), Pulse analysis timing (ns), Other — please specify
• List the top 5 parameters you will evaluate and the target value or tolerance for each.
• For those parameters, do you require specific test conditions (IFBW, averaging, temperature, DUT load)? Please specify which parameters map to which conditions.
• Which DUT ports, interfaces, and connector types must be supported natively? Options: SMA, 2.92mm (K), 3.5mm, APC-7, Waveguide (specify), Optical RF interface, Custom fixture
• Do these measurements need to be standards-compliant (e.g., MIL‑STD, 3GPP) or are lab-standard procedures acceptable? Options: Standards-compliant — will specify standard, Lab-standard with documented procedure, Both — critical ones must be standards-compliant
• Will you require time-domain or pulse-specific analysis for the DUT, and how critical is it relative to CW/continuous measurements? Options: Yes — pulse analysis is critical, Yes — time-domain occasionally required, No — CW measurements only, Depends on test case

What Proof Will Let You Say 'Yes'?

• If I handed you a test report right now, what exact evidence (numbers, traces, raw files) and signatures would make you accept the instrument?
• Do you require raw measurement files, plots, or both as part of acceptance deliverables? Options: Plots only, Raw data files, Both plots and raw files, Summary report with raw on request
• Who must sign the acceptance (roles) and who has final technical sign-off? Options: Senior RF Engineer, Test Engineering Manager, Program Manager, Procurement, Quality/Compliance, Customer representative, Other
• Do you expect strict pass/fail for each parameter, a weighted scoring rubric, or critical-parameter pass/fail plus soft metrics? Options: Pass/fail per parameter, Weighted scoring rubric, Hybrid — critical pass/fail + weighted others
• How many representative DUTs or repeat test cases are required to consider acceptance robust? Options: Single DUT/sample, 3–5 DUTs, 6–10 DUTs, More than 10, Depends on test complexity
• Will you require the signed calibration certificate and instrument history attached to the acceptance package? Options: Yes — full history and ISO17025 cal cert, Yes — current cal cert only, No — not required for acceptance

Don’t Let Calibration Kill the Deal

• Could a missing traceable calibration certificate or the wrong calibration source stop approval even if measurements meet your specs? Options: Yes — will stop approval, Possibly — needs review, No — measurements matter more than vendor cal
• Is the instrument required to appear on an approved-equipment list for this program, and if so who manages that list?
• What calibration traceability level do you require (select all that apply)? Options: NIST-traceable, ISO17025-accredited lab, Manufacturer calibration certificate, Internal lab calibration acceptable, Other — specify
• How recent must the delivered calibration be (at time of delivery)? Options: Within 3 months, Within 6 months, Within 12 months, Not specified / negotiable
• Do you require calibration interval recommendations and a documented plan for future recalibrations? Options: Yes — required, Prefer recommendation from supplier, No — we'll manage separately
• Are there export controls, ITAR/EAR restrictions, or special handling rules we must know about before shipping? Options: ITAR/EAR controls apply, Export license required, No special constraints, Other — specify

Procurement Reality Check — Where Dates, Budgets, and Risk Collide

• If a 6‑week instrument lead time slipped to 12 weeks, what would the program do—delay, replan, or abort? Options: Delay launch, Replan tests with alternatives, Cut scope or use interim equipment, Program at risk of losing contract, Other
• What procurement route will you use for this purchase? Options: Direct purchase (CAPEX), Program/contract budget, Lease or rental, Loaner-to-purchase trial, Third-party buy via contractor
• Is there an approved supplier/vendor list, PO process, or procurement constraint we must follow? Options: Yes — internal approved list, Yes — customer-approved only, No constraints, Other — specify
• Do you expect to request a loaner for verification before purchase, and if so, what duration and timing do you need? Options: No loaner, Yes — 1 week, Yes — 2–4 weeks, Yes — 1–3 months, Need urgent short-term loan (<1 week)
• What is the approximate procurement budget range for this instrument/solution? Options: Under $50k, $50k–$150k, $150k–$500k, Over $500k, Undecided / depends on options
• Who in procurement or finance will originate and approve the PO (name/role and expected lead times)?

Lab & Test Readiness — Can We Run Your Critical Tests?

• What's the one hidden lab or DUT detail that has caused validations to fail on day one in the past?
• Where will the verification tests run: your lab, our lab, remotely with support, or at a third‑party test house? Options: Customer lab (on-site), Supplier lab (on-site), Remote validation with supplier support, Third-party test house, Hybrid arrangement
• Do you have the required test fixtures, attenuators, cables, and adapters on hand, or should we include them with a loaner? Options: All available, Some available — will specify which, None — need supplier to provide accessories, Prefer loaner with accessories
• What physical or environmental constraints in your lab (RF shielding, temperature control, vibration, DC power quality) could affect measurement fidelity?
• Who will be the hands-on test lead during verification and what are their core responsibilities? Options: Senior RF Engineer, Test Engineer, Lab Technician, Third-party test house, Other
• Do you require on-site setup, firmware/software handoff, and training during delivery, or is documentation enough? Options: Full on-site setup & training, Remote setup & live training, Documentation and self-training, Combination — specify

Stakeholders, Sign-Offs, and Communication Rhythm

• If a decision must be made quickly with incomplete data, who is empowered to sign off and accept the risk?
• Please list all stakeholders who must be informed or approve the purchase (name, role, and approval authority).
• How would you prefer progress updates during evaluation and verification? Options: Weekly call, Twice-weekly check-ins, Email summary, Shared dashboard with live status, Ad-hoc as needed, Other
• Are there compliance reviews (security, procurement, export control, quality) that require additional lead time before acceptance? Options: Security review required, Export control review required, Legal/compliance sign-off required, Quality assurance/process audit required, No additional reviews
• What is your preferred acceptance timeline after delivery and verification (when should final sign-off occur)? Options: Same day (immediate), Within 1 week, 1–2 weeks, 2–4 weeks, Depends on test complexity
• Is there anything else we should know now that would help us avoid surprises during evaluation, delivery, or acceptance?

• Measurement Requirements Confirmation (Kickoff)
• Critical Test Case Definition Workshop
• Loaner Selection & Evaluation Plan
• Measurement Procedure Dry Run & Script Validation
• Acceptance Criteria Finalization & Sign‑off Alignment

• Identify any gaps (fixtures, SW options, automation) and schedule corrective actions before formal testing.
• Customer: Confirm which single test or parameter must be proven first to unblock procurement (top gating criterion).
• Both: Identify and list required adapters, fixtures, and environmental controls and who will supply them.
• Instrument Model & Option Mapping
• Select and lock the loaner instrument model(s) and required software options that can execute the agreed tests.
• Agree the calibration and traceability documentation needed for defense/approved-equipment compliance.
• Define the exact evidence package required to accept the loaner verification results.
• Resolve logistics and contingency plans to avoid schedule slips during the loaner period.
• Seller: Reserve the selected loaner model(s) and provide provisional shipping dates and calibration certificates.
• Seller: Prepare a loaner evaluation agreement that includes liability, duration, and acceptance evidence requirements for customer signature.
• Customer: Confirm any internal approved-equipment-list or procurement forms required to receive the loaner on site.
• Lab/Remote Setup Walkthrough
• Prove that the measurement procedure reproducibly generates the required evidence to meet acceptance signals.
• Lock the test scripts and runbook to eliminate ambiguity during formal validation.
• One‑sentence Current State
• Seller: Deliver finalized test scripts, runbook, and an example evidence package (raw files + annotated plots).
• Customer: Validate and sign off that the dry-run outputs meet the acceptance evidence requirements or list required adjustments.
• Both: Schedule the formal validation window and confirm personnel/room access for the test dates.
• Review Dry‑Run Results vs Pass/Fail Criteria
• Produce a locked acceptance checklist that, when completed, triggers formal sign-off and procurement decisions.
• Define and agree remediation steps and timelines for failed tests to prevent schedule drift.
• Confirm signatories, approval flow, and the date by which the acceptance decision will be made after formal testing.
• Seller: Package and deliver the formal acceptance packet template (checklist + evidence submission instructions + calibration docs).
• Customer: Confirm the internal approvers and provide any required procurement identifiers (PO number, AEL entry) needed to complete acceptance.
• Both: Agree a contingency re-test window and who will fund/coordinate additional measurements if remediation is required.
• Establish and record a single-sentence current state that everyone can repeat and validate.
• Surface and quantify the consequence of not meeting the measurement needs (time/cost/risk).
• Agree a one-sentence future state (outcome) that test plans must prove.
• Capture the DUT context and the explicit acceptance signals that will gate buy/no-buy.
• List required pre-work items and data the team needs to build the validation plan.
• Customer: Provide DUT datasheet, block diagrams, and two representative waveforms/logs for the critical parameters.
• Seller: Draft and circulate the agreed one-sentence current state and future-state statements for confirmation.
• Seller: Create a shared requirements-to-parameter checklist to drive the test matrix in the next meeting.
• Review Requirements-to-Parameter Checklist
• Produce a complete test-case inventory tied directly to each critical parameter and failure mode.
• Agree explicit numerical pass/fail criteria that map to the customer's acceptance signal.
• Specify the exact measurement configurations, calibration state, and accessories required for each test case.
• Create a prioritized test matrix with owners and estimated run times.
• Seller: Create the test-case matrix spreadsheet with fields for evidence artifacts and share with the team.
• Calibration Level & Traceability Requirements
• Consequence Mapping
• Execute Representative Critical Tests
• Map Failure Modes to Test Cases
• Finalize the Acceptance Checklist
• Define Pass/Fail Criteria & Margins
• Loaner Terms & Logistics
• Remediation & Escalation Path
• Live Analysis & Evidence Review
• Define Future State (One Sentence)
• Data Capture & Evidence Package
• DUT Context & Critical Parameters
• Lock Formal Validation Schedule & Logistics
• Specify Measurement Configuration & Accessories
• Finalize Test Scripts, Templates & Runbook
• Force Validation Check: Customer Confirmation
• Acceptance Signals & Decision Rules
• Acceptance Decision Flow
• Assemble Test Matrix & Assign Owners
• Sign-off Confirmation (Pre-Sign)
• Risk & Contingency Plan

• Loaner Vector Network Analyzer with Lab Setup
• On-site Calibration with Traceable Certificate
• Millimeter-Wave Frequency Extension Hardware Install
• Phase Noise Measurement Option Activation
• High-Dynamic-Range RF Front-End Deployment
• Pulse Analysis and Time-Domain Option Enablement
• Standards-Compliant 5G NR Measurement Suite Install
• Automated S-Parameter Test Script Deployment
• Remote Instrument Control and Data Streaming Setup
• Environmental Chamber Integration for Temperature Tests
• Turnkey Antenna Pattern Measurement Deployment
• Firmware, Driver, and Software Update Installation
• VNA Thermal Stabilization Module Installation

Loaner Vector Network Analyzer with Lab Setup

• Do you require a loaner VNA for hands-on validation? Options: Yes, No
• Which frequency range must the loaner cover for your tests? Options: DC-3 GHz, 3-26.5 GHz, 26.5-50 GHz, 50-110 GHz, Other (specify)
• Which connector types and adapters are needed in the lab setup? Options: SMA, 3.5 mm, 2.92 mm, 2.4 mm, Waveguide / horn, Other (specify)
• How many loaner units and for what duration do you need them? Options: One unit for 1-2 weeks, One unit for 3-6 weeks, Multiple units (specify), Other (specify)
• Will you require on-site engineer assistance to set up the loaner in your lab? Options: Yes, full on-site setup, Remote setup assistance only, No assistance required
• What are the pass/fail acceptance criteria we should validate on your DUT with the loaner (list specific parameters and limits)?

On-site Calibration with Traceable Certificate

• Do you require on-site calibration with a traceable certificate? Options: Yes, No
• Which traceability standard must the certificate satisfy? Options: ISO/IEC 17025, NIST-traceable, Manufacturer traceable, Customer-specified / other
• Which calibration scope do you require? Options: Full frequency calibration, Limited verification (select parameters), Power/level calibration only, Other (specify)
• What frequency bands and parameter points must the calibration cover?
• Is inclusion on an approved-equipment list required after calibration? Options: Yes, include all required docs, No, standard certificate is sufficient, Unsure - advise
• Do you require calibration labels, asset tagging, or record upload into a specific system? Options: Yes - provide labels and record upload, Labels only, No

Millimeter-Wave Frequency Extension Hardware Install

• Do you need millimeter-wave extension hardware installed on an instrument? Options: Yes, No
• Which target frequency band(s) will the extension cover? Options: 26.5-40 GHz, 40-67 GHz, 67-110 GHz, Custom band (specify)
• Does your DUT require waveguide interfaces, horn antennas, or coax transitions? Options: Coax connectors/adapters, Waveguide interfaces, Horn antenna mounting, Other (specify)
• Are there mechanical or environmental constraints for installing the extension (rack space, weight, temperature)?
• Will the extension require additional calibration or verification after install? Options: Yes - on-site verification required, No - factory calibration sufficient, Unsure - advise required
• What is the preferred installation window or delivery lead time constraint? Options: Within 2 weeks, 2-6 weeks, 6-12 weeks, Flexible / contact me

Phase Noise Measurement Option Activation

• Do you want the phase noise measurement option activated on the instrument? Options: Yes, No
• What phase noise performance targets do you require (give dBc/Hz targets at specific offsets)?
• Which offset ranges and carrier frequencies are critical for your program? Options: Close offsets (1 Hz - 10 kHz), Mid offsets (10 kHz - 1 MHz), Far offsets (>1 MHz), Specify exact offsets
• Will you use an external reference clock or the instrument internal reference? Options: Internal reference, External 10 MHz reference, GPS-disciplined reference, Other (specify)
• Do you require cross-correlation, averaging, or other special acquisition modes for phase noise? Options: Yes - cross-correlation, Yes - extended averaging, No special modes required
• Is there a documented acceptance limit for phase noise that will be used to qualify the measurement? Options: Yes - provide limits, No - we will define during validation, Unsure

High-Dynamic-Range RF Front-End Deployment

• Do you require a high-dynamic-range RF front-end to capture low-level and high-level signals? Options: Yes, No
• What dynamic range or noise-floor specification is required (dB or dBm)?
• Will you require external low-noise preamps or switchable attenuators as part of the front end? Options: Low-noise preamp, Switchable attenuator, Both, Neither
• What maximum input power levels and expected signal amplitudes should the front end support?
• Are there required EMC or shielding constraints for your test environment? Options: Yes - provide details, No
• Do you need front-end deployment verified with specific DUT test cases and acceptance criteria? Options: Yes - provide test cases, No - general verification only

Pulse Analysis and Time-Domain Option Enablement

• Do you need pulse analysis / time-domain option enabled? Options: Yes, No
• What pulse parameters must be measured (pulse width, rise/fall time, repetition rate, duty cycle)?
• What trigger types and interfaces are available on the DUT (TTL, LVTTL, analog, RF trigger)? Options: TTL/LVTTL, Analog trigger, RF trigger, Other (specify)
• What bandwidth and sample-rate capabilities are required to resolve your pulses? Options: Low bandwidth (≤100 MHz), Medium (100 MHz - 1 GHz), High (>1 GHz), Specify exact bandwidth
• Do you require automated pulse acceptance criteria (timing jitter limits, amplitude thresholds) to be part of validation? Options: Yes, No
• Will pulse validation be performed onsite with our engineer or remotely by your team? Options: Onsite with engineer, Remote assistance, Your team only

Standards-Compliant 5G NR Measurement Suite Install

• Do you require the 5G NR measurement suite installed and licensed? Options: Yes, No
• Which 3GPP release and NR bands must be supported? Options: 3GPP Release 15, Release 16, Release 17+, Specific bands (specify)
• Which conformance metrics are required (EVM, ACLR, SEM, SSB, RSRP, others)? Options: EVM, ACLR, Spectrum Emission Mask, SSB/SSB beam measurement, Other (specify)
• Do you require automated 5G test cases or a manual measurement workflow? Options: Automated test cases, Manual workflow, Both
• Are baseband IQ capture/transfer interfaces available and what format do you need for results? Options: IQ files (binary), CSV/text summary, Proprietary / other, Not applicable
• Will the suite be used for R&D, production test, or compliance lab verification? Options: R&D, Production test, Compliance lab, Multiple

Automated S-Parameter Test Script Deployment

• Do you need automated S-parameter test scripts deployed and validated? Options: Yes, No
• Which S-parameter sets and port counts must be supported? Options: S11 / S21 (1-2 port), Full 2-port S-parameters, Multiport (3+ ports), Custom (specify)
• What frequency sweep plan or discrete frequency points are required?
• Do you require integration with lab automation tools (Python, LabVIEW, TestStand)? Options: Python, LabVIEW, TestStand, Other / custom
• What pass/fail logic or data acceptance criteria should the scripts enforce?
• Do you need on-site validation of scripts using your DUT and fixtures? Options: Yes - on-site validation, No - remote validation, Optional

Remote Instrument Control and Data Streaming Setup

• Do you require remote control and live data streaming from the instrument? Options: Yes, No
• What network environment will the instrument be on? Options: On-prem LAN (no internet), VPN from corporate network, Public internet with firewall, Other (specify)
• What data throughput and retention requirements do you have for streaming? Options: Low (logs only), Medium (periodic traces), High (continuous IQ/data), Specify exact rates
• Are there security or compliance requirements for remote access (VPN, mTLS, FIPS, etc.)? Options: VPN, mTLS / TLS, FIPS-compliant, No special requirements, Other (specify)
• Who will need access and what role levels are required (view only, control, admin)?
• Do you need integration with an existing data pipeline or lab data management (LIMS, cloud storage)? Options: Yes - LIMS, Yes - cloud storage, Custom integration, No

Environmental Chamber Integration for Temperature Tests

• Will you run temperature chamber tests that require instrument-chamber integration? Options: Yes, No
• What temperature range and ramp rates are required for your tests?
• What chamber feedthroughs are required for RF (coax, waveguide, fiber, bulkhead)? Options: RF coax feedthrough, Waveguide feedthrough, Fiber/other, No feedthroughs required
• Do you need synchronized control between chamber and instrument (temperature triggers, dwell timing)? Options: Yes - full sync, Partial sync, No
• Are there specific DUT mounting, cable length, or isolation constraints inside the chamber?
• Is on-site integration and verification with your chamber required? Options: Yes - on-site, Remote assistance, No

• Statement of Work (SOW)
• Commercial Terms & Quote
• Purchase Order Acceptance
• Delivery & Acceptance Schedule
• Calibration Traceability & Certification
• Approved Equipment List (AEL) Compliance
• Loaner Evaluation & Trial Terms
• Payment Terms & Invoicing
• Warranty, Support & Maintenance Agreement
• Software License & Options Order
• Export Control & ITAR Compliance
• Data Privacy & Security Addendum
• Change Order & Scope Variation
• Termination & Cancellation Terms
• Mutual Commitment Signature

• Acceptance Confirmation & Sign‑Off
• Lessons Learned & Process Improvement
• Operational Handoff & Shared Channel Provisioning
• Post‑Deployment Performance Review (Operational Validation)
• Product Enhancement & Roadmap Input Workshop

• Confirm whether additional support or on-site assistance is required and schedule it if needed.
• One‑sentence Current State and Consequence
• Publish a Lessons Learned report summarizing root causes, consequences, and assigned actions within 3 business days.
• Update the Journey Template and acceptance checklist to include any mandatory pre-checks identified (e.g., lab access windows, calibration cut-offs).
• Schedule the 60-day review to validate that process changes reduced recurrence.
• Current State and Handoff Objective
• Provision and validate a shared channel with correct permissions and artifact structure.
• Assign clear owners and SLAs so both parties know how issues are triaged and escalated.
• Ensure the customer can open reproducible tickets and receives initial training/materials to use the instrument effectively.
• Provision shared channel rights and confirm access for named customer and seller participants.
• Create initial verification ticket and attach acceptance artifacts to validate workflow.
• Distribute a one‑page escalation contact list and SLA summary to all participants.
• Recap Future State Definition
• Validate that the instrument delivers the future-state outcomes in production test scenarios.
• Identify and prioritize any operational defects and enhancement requests with concrete owners.
• Opening and Objectives
• Customer to supply representative run logs and a short video or screen capture of failure cases (if any) within 3 business days.
• Seller to triage defects and provide either a mitigation, patch timetable, or scheduled site visit.
• Log prioritized enhancement requests into the shared channel with customer business impact descriptions.
• Current State and Business Consequence
• Capture enhancement requests that are clearly tied to business consequences and rank them for action.
• Obtain engineering feasibility feedback and preliminary timelines for high-priority items.
• Set concrete validation criteria so future demonstrations prove the future-state outcome, not just features.
• Product team to log prioritized enhancement requests with estimated effort and target milestone within 5 business days.
• Customer to provide quantifiable acceptance criteria for each high-priority enhancement.
• Schedule a roadmap review with customer stakeholders to confirm alignment on timelines and deliverables.
• Confirm whether the instrument meets each documented acceptance criterion and obtain formal sign-off if met.
• If any criteria are unmet, agree a remediation plan with owners, timeline, and retest conditions.
• Ensure complete calibration traceability and acceptance artifacts are recorded in the shared channel.
• Upload signed acceptance form, final test logs, and calibration certificates to the shared folder.
• If failed/marginal items exist, owner to create remediation ticket with root cause hypothesis and proposed corrective action within 48 hours.
• Schedule retest window and assign test owner and acceptance witness for the retest.
• Agree a short roadmap of process improvements and schedule a follow-up check.
• Document actionable lessons with clear owners and deadlines to prevent recurrence.
• Quantify the business consequence of issues to prioritize process changes.
• Current State Summary (one sentence)
• Operational Performance Data (Proof)
• Shared Channel Walkthrough (Proof)
• What Worked (Info Sharing)
• Technical Impact Assessment
• Issue Lifecycle & SLAs (Tie-back)
• Acceptance Criteria Recap
• What Broke or Hurt Schedule (Input Gathering)
• Customer Validation & Use Cases
• Value Prioritization (Decision Making)
• Prioritize Issues vs Enhancements
• Root Cause and Consequence Analysis
• Escalation Path and Owners
• Test Results Presentation (Proof)
• Customer Validation Criteria for Enhancements
• Live Validation & Tie-back
• Initial Ticket Creation and Access
• Define Preventive Actions and Owners
• Agree Next Steps
• Commitments and Follow-up
• Discrepancy Analysis & Consequence
• Agree Metrics and Follow-up
• Training & Handoff Artifacts
• Decision and Sign-off
• Next Steps and Documentation