RF & Microwave Test
Complex technical sales and manufacturing engagements across the global electronics supply chain.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Technical Requirements Discovery
Confirm the buyer's measurement requirements, pass/fail acceptance criteria, stakeholders, and any calibration traceability or approved-equipment constraints.
Discovery Questions
Quick technical snapshot
- Tell me which instrument categories and maximum frequency range you need for this program.
- Which specific parameters (example: dynamic range, phase noise, measurement bandwidth) are deal-breakers for qualification?
- How many devices under test per week will need measurements at those frequencies?
- Describe the typical DUT interfaces and connectors your team uses for high-frequency measurements.
- When do you need the capability available relative to your next program milestone?
- Decide whether inability to obtain the required frequency capability within your timeline would force you to pause the program or seek alternative designs.
Where the lab is hitting limits
- What single instrument shortfall today would cause you to disqualify a supplier immediately?
- Walk me through the last time a measurement failed to meet a spec, including root cause and program impact.
- Which measurement conditions have historically driven inconsistent results, for example temperature, source power, or pulse profile?
- How often do ambiguous measurement results force rework or additional measurement steps?
- Who in your engineering chain owns final technical acceptance of an instrument?
Assumptions that hide procurement risk
- If a datasheet matches your spec exactly, what operational reality would still make you reject the instrument?
- List the calibration traceability or approved-equipment list requirements that procurement enforces for defense programs.
- Do you already have an approved-equipment registry entry required for procurement, or will adding one be necessary?
- Specify the maximum acceptable calibration interval your program requires before recalibration is mandatory.
- Name the accrediting bodies or lab standards that calibration certificates must reference.
Prove it in your lab
- Define the pass/fail outcomes a loaner must demonstrate in your lab to trigger procurement within weeks.
- Name the DUT models and reference standards you will use during the loaner evaluation.
- Estimate the number of days of hands-on access required to complete verification of your critical parameters.
- Describe the exact acceptance test sequence and measurement settings you will run on the loaner.
- Who must sign the test report for the evaluation to be considered successful?
Lab readiness that often trips delivery
- List the lab infrastructure gaps that would block delivery, setup, or verification of a millimeter-wave instrument.
- Are RF shielding, dedicated power circuits, or controlled environment conditions required that your lab currently lacks?
- Count the on-site staff roles and typical availability windows you can assign for receiving and initial verification.
- Do you have a preferred on-site team for installation, or will you require the seller's field engineer to perform setup?
- Identify the single infrastructure gap that would stop the project immediately if it is not resolved.
Alternatives you're weighing
- Outline the conditions under which you would stay with your incumbent, buy a competitor product, or build an internal test solution.
- Select the types of alternatives you are actively evaluating
- For each selected alternative, specify what performance, lead time, or calibration traceability would make it acceptable.
- Has anyone on your team proposed solving the measurement gap by changing test methodology rather than acquiring new hardware?
- What single advantage from a competitor, incumbent, or internal program would cause you to cancel a planned external evaluation?
Acceptance criteria that close the deal
- State the non-negotiable contract clauses, calibration evidence, and delivery terms that must be in place for procurement to proceed immediately.
- Provide the numeric pass/fail thresholds for the top parameters, for example phase noise at defined offsets and dynamic range at frequency points.
- Identify the procurement and engineering roles that must sign the acceptance certificate at delivery.
- Indicate how soon after successful hands-on verification your team can issue a purchase order.
- Decide whether a delivery delay beyond your program window would stop procurement even if the instrument passes all acceptance tests.
Operational gates and compliance
- Pinpoint the single compliance or access gate that would prevent vendor personnel from completing on-site setup.
- Provide the list of lab access approvals, security clearances, or export controls required for on-site work.
- Does your facility require background checks, ITAR controls, or additional legal reviews before external engineers can operate instruments?
- Specify the on-site contact role responsible for scheduling delivery, coordinating setup, and signing acceptance.
- Assess the accessibility and condition of your reference standards and calibration artifacts for initial verification.
- Choose whether unresolved compliance gates will trigger a program delay or allow reduced verification to proceed.
Configuration, firmware, and records required
- State the exact configuration values, firmware versions, software options, and calibration numbers you require documented before shipment.
- Select the file formats and delivery channels you require for configuration files and calibration certificates.
- Confirm whether you require signed traceability chains from origin labs for calibration certificates.
- Indicate the number of unique configuration snapshots that must be archived for audit, and the roles that need access.
- Explain the approval step you will require if delivered firmware differs from your lab standard.
- Will missing any required documentation on delivery be a fatal condition for acceptance?
Next steps and timeline to decision
- If we meet your acceptance thresholds and delivery window, what remaining obstacle would still stop you from approving a purchase within seven days?
- Share the names and roles of decision-makers and procurement signatories required to keep the timeline within weeks.
- Estimate the number of procurement approvals or internal reviews that typically add more than two weeks to the decision.
- Pinpoint the top risks in the evaluation or delivery timeline that most commonly push decisions past your program deadline.
- Choose the next concrete step you want from the seller this week, loaner delivery, technical call, or draft contract?
-
Hands-on Evaluation
Provide a loaner or test unit for verification of the buyer's critical parameters in their lab and capture objective acceptance results against documented criteria.
- current_state
- stakeholders
- desired_state
- gaps
- success_criteria
- decision_readiness
- desired_state
- decision_readiness
- current_state
- success_criteria
- gaps
- stakeholders
- desired_state
- success_criteria
- stakeholders
- gaps
- current_state
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Solution Scope
Define the exact configuration, options, calibration services, delivery lead times, and acceptance tests required to meet the buyer's spec-driven needs.
Scope Configuration
- Deliver and Install Test Instrument
- Provide Factory Calibration with Traceable Certificate
- Deploy Loaner Evaluation Unit
- Install Millimeter-Wave Testhead Hardware Upgrade
- Activate Phase-Noise Measurement Option
- Install Pulse-Analysis Measurement Software
- Deploy Standards-Compliant Measurement Suite
- On-Site Verification Measurement on DUT
- Provide Annual Calibration and Recertification
- Provide Extended Warranty and Service Contract
- Deliver Firmware and Software Updates with Validation
- Repair and RMA with Priority Loaner Support
- Supply Calibration Kits and Reference Standards
- Deliver On-Site Measurement Training Workshop
Scope Questions
Deliver and Install Test Instrument
- Which rack unit (U) height and bench footprint will you allocate for the instrument?
- Specify the DUT interfaces and connector types the instrument must support (for example 2.92 mm, 1.85 mm, 50 ohm SMA, or WR-28 waveguide).
- Confirm required environmental operating ranges for the instrument during measurements (ambient temperature and relative humidity bounds).
- Who will be the named on-site owner for physical receipt, unpacking, and signature of the installation checklist?
- When must the instrument be delivered to meet your program milestones (target week) and what is the maximum acceptable lead time in weeks?
Provide Factory Calibration with Traceable Certificate
- Which traceability regime do you require for the calibration certificate (for example NIST traceable, ISO/IEC 17025 accredited lab, or another national lab)?
- Provide the maximum allowed calibration uncertainty or tolerance for key parameters (for example S21 magnitude ±dB at 26 GHz, phase noise at 10 kHz offset in dBc/Hz).
- Is a full factory calibration certificate with serial numbers and traceable standard IDs required at delivery?
- Which document will serve as evidence of traceability for procurement review (for example ISO/IEC 17025 certificate number, NIST calibration report ID, or specific standard serials)?
- Specify the desired calibration interval and whether calibration on receipt or re-certification within X months is required.
Deploy Loaner Evaluation Unit
- Select the purpose of the loaner unit in your lab (for example validate phase noise at 10 kHz, verify dynamic range for S21 at 39 GHz, or confirm pulse analysis on DUT).
- Provide the DUT model or fixture you will use with the loaner so we can confirm connector adapters and testhead compatibility.
- Do you require on-site setup support for the loaner evaluation or will your test engineer perform installation using supplied instructions?
- Indicate the minimum evaluation window needed in your lab (number of business days) to complete the critical measurements on your DUT.
- Provide any site constraints for loaner delivery such as export control handling, access restrictions, or approved-equipment list screening prior to shipment.
Install Millimeter-Wave Testhead Hardware Upgrade
- Identify the frequency bands the testhead upgrade must cover (for example 26.5–40 GHz, 60–90 GHz) and the highest frequency required.
- Provide the connector family and power handling requirements for the testhead (for example 2.4 mm, waveguide, DC bias pass-through up to X volts).
- Are there mechanical interface constraints such as a custom DUT fixture, probe station compatibility, or specific mounting orientation?
- Specify any controlled routing or RF cable length limits that affect mmWave loss budgets in your test setup.
- Indicate whether an on-site hardware installation window with access to the probe station or test bench is available and provide preferred dates.
Activate Phase-Noise Measurement Option
- State the phase noise performance you require at key offsets (for example -120 dBc/Hz at 10 kHz offset at 10 GHz) and for which carrier frequencies.
- Choose the measurement standard or routine you will validate against (for example single-sideband phase noise, integrated phase noise over 1 kHz–10 MHz).
- Provide the reference source or DUT signal level and impedance used for phase noise verification (for example -10 dBm into 50 ohm).
- Do you require real-time phase noise traces and raw data export for your lab analysis?
- Indicate whether you need phase-noise option activation at time of delivery or as a later license activation.
Install Pulse-Analysis Measurement Software
- Provide the pulse parameters you must analyze (for example pulse width 10 ns, rise/fall times, repetition frequency 10 kHz, and peak power range).
- Which pulse-analysis routines do you require (for example pulse profile, AM/PM conversion, gated FFT, time-domain power vs time)?
- Specify the software license term preferred for the pulse-analysis module (for example perpetual, 1 year, or subscription).
- Do you need integration of pulse-analysis results into your existing automation scripts or test executive via API or CSV export?
- List any regulatory or program constraints that affect pulse testing such as peak-power exposure limits or sealed test enclosures.
Deploy Standards-Compliant Measurement Suite
- Which measurement standards must the suite conform to for your program (for example MIL-STD measurement methods, 3GPP RF test cases, or IEEE test procedures)?
- Provide the list of specific measurements required from the suite (for example S-parameters, group delay, insertion loss up to 40 GHz, ACLR).
- Indicate whether you require test automation scripts or measurement sequences that run unattended and produce standardized test reports.
- Specify the required report format and content (for example CSV raw data, PDF summary with pass/fail against spec, or XML for automated ingestion).
- Name the acceptance thresholds for each critical measurement that the suite must test against (for example S21 insertion loss < 1 dB at 26 GHz or phase noise < -110 dBc/Hz at 10 kHz).
On-Site Verification Measurement on DUT
- Please describe the DUT type, model, and critical measurement points to verify on-site (for example mmWave front-end, model X, verify S11 at 39 GHz and phase noise at carrier).
- Provide the pass/fail acceptance thresholds for the on-site verification for each parameter (for example receiver NF < 4 dB at 28 GHz, or S21 dynamic range > 80 dB).
- How will you verify and sign off the on-site measurement results: an annotated PDF test report, raw data files, or a signed acceptance form?
- Indicate the named engineering attendees required for the on-site verification and their roles (for example RF engineer to witness, QA to sign acceptance).
- Specify any fixture, biasing, or power supply requirements for the DUT during verification (for example DC bias up to 5 V, custom fixture with SMA inputs).
Provide Annual Calibration and Recertification
- State the expected annual calibration scope you require (full calibration of RF paths, only frequency response, or verification of options such as phase-noise module).
- Indicate whether on-site calibration service is required or if you will ship the instrument to the calibration facility.
- Provide the acceptable turnaround time for annual recertification (for example 2 weeks, 4 weeks, or expedited 5 business days).
- Specify whether you require calibration certificates to include measurement uncertainty tables and reference standard serial numbers.
- List any government-approved-equipment list numbers or program audit requirements that must be referenced on the recertification paperwork.
Provide Extended Warranty and Service Contract
- Select the service contract level you prefer for the instrument (for example next-business-day onsite, 4-hour response, or parts-only warranty).
- Provide the desired contract term for the extended warranty (for example 1 year extension, 3 years, or multi-year support).
- Identify whether loaner coverage must be included for repair RMA events and whether priority loaners are required.
- Please indicate any site security or personnel vetting requirements for service technicians (for example cleared visitor badge, background check).
- Specify billing preferences for the service contract (annual invoice, purchase order on renewal, or cost center charge).
Deliver Firmware and Software Updates with Validation
- Provide the required baseline firmware and software versions that must be present on delivery for your validation baseline.
- Indicate whether you require a validation checklist for each firmware/software update that covers regression tests such as S-parameter repeatability and phase-noise stability.
- Choose the update delivery method you prefer: pre-installed at factory, delivered as installer with validation report, or pushed via secure network update.
- State any software qualification processes your QA group requires (for example signed SHA256 installer, reproducible test script results).
- Specify whether rollback images and versioned release notes must be retained in your lab archive for audit purposes.
Repair and RMA with Priority Loaner Support
- Describe your expected RMA workflow including purchase order requirements, RMA authorization process, and shipping address for returns.
- Indicate whether priority loaner dispatch is required within a specific SLA (for example shipped within 48 hours of RMA approval).
- Provide any program restrictions on repair routing such as ITAR-controlled spares or forced domestic repair only.
- Name the contact for RMA approvals and the authorized signer for repair charges exceeding a threshold.
- Estimate the maximum downtime tolerance for the instrument before a loaner must be provided (for example 5 business days).
-
Mutual Commit
Finalize commercial and contractual terms, calibration traceability clauses, delivery schedule, and formal acceptance criteria for procurement.
Agreement Modules
- Purchase Agreement
- Order Confirmation
- Acceptance Test Plan
- Calibration Traceability Addendum
- Delivery & Lead Time Schedule
- Payment & Invoice Schedule
- Regulatory & Procurement Compliance Addendum
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Capture concrete readiness facts the deployment depends on — lab access, power/environment constraints, DUT fixtures, and named owners for receipt and verification.
Pre-Deployment Questions
Environment and site access
- Primary deployment site name and physical location (lab/room/building). Please use the site name we should reference in shipping and access requests so we can coordinate logistics.
- Is physical access for delivery and on-site setup already approved for the target delivery window? (If 'No' or 'Restricted', we'll need the date/access owner to schedule.)
- Named site sponsor / receiving owner for delivery and engineer access (name and role). This person will be the receiving contact and will clear badges/escorts.
Power, environment, and physical constraints
- Is the required electrical provision available at the installation location (correct voltage, dedicated circuit, and verified grounding)? (Answer so we know if facilities work is needed.)
- Environmental or site constraints at the instrument bench/rack that affect setup (select all that apply). Pick all that apply so we can plan handling and transport.
- If you selected 'Other' or need to provide specifics about environmental constraints (why they matter and who verifies), please describe them and name the owner who will confirm readiness.
DUT fixtures, connectivity, and calibration requirements
- Are DUT fixtures, adapters, and mounting hardware available and compatible with the instrument connector families? (This determines whether we must ship adapters or plan fixture design.)
- Does this deployment require the instrument to be included on an approved equipment list or require a specific calibration traceability chain? (If yes, name the approval owner who will provide the requirements.)
- List the system categories or integration endpoints the instrument will attach to (e.g., reference clock input, lab LAN for data export, control automation endpoint) and the owner responsible for each. Plain category names only — exact addresses or credentials come later.
People, timing, and constraints
- Named owners for receipt, on-site setup verification, and final acceptance (provide name and role for each). These people will be primary escalation points during deployment.
- Are there blackout windows, scheduled test campaigns, or compliance gates that block delivery or setup? If yes, state who must approve a work window so we can avoid missed deadlines.
- Target readiness date when all the items above (access, power, fixtures, owners, and approvals) will be in place so we can schedule delivery and on-site setup. If unknown, enter 'TBD'.
-
Configuration & Calibration Details
Record exact configuration values, firmware/options, software licenses, calibration certificates and traceability numbers, and required measurement software modules.
Configuration Details
Firmware & Instrument Identity
- Instrument model identifier (exact string from the unit label) — consumed by provisioning and firmware selection (format: e.g., X1000A)
- Instrument serial number (exact, alphanumeric) — consumed by calibration record linkage (format example: SN-ABC12345)
- Firmware image version to install (enter exact MAJOR.MINOR.PATCH or enter 'latest-stable' to use the platform default) — consumed by the image deployment step (Default: 'latest-stable')
Software Licenses & Measurement Modules
- Measurement software module to enable (select all required) — consumed by license activation and module download
- Primary license identifier (non-secret ID shown on your license agreement). Do NOT paste license keys or secrets — enter the non-secret ID exactly (if none, enter 'none')
Calibration & Traceability
- Calibration certificate number for this instrument (exact identifier printed on certificate; enter 'none' if uncalibrated) — consumed by certificate import
- Traceability authority declared on the certificate (select one) — consumed by procurement traceability checks
- Calibration interval in months (numeric) — interval used to schedule next calibration (Default: 12)
Configuration Values & Artifacts
- 10 MHz reference selection — choose the hardware reference wiring the instrument should use at setup (consumed by front-panel config)
- Default instrument region code for regulatory/default settings (enter ISO 2-letter code; Default: 'US') — consumed by region/regulatory config
-
Instrument Delivery & Setup
Schedule and execute delivery, on-site setup, calibration, and initial verification measurements with clear owners, dates, and escalation paths.
-
-
Success
Validate outcomes against the buyer's acceptance criteria, capture lessons learned, and maintain a shared channel for issues, calibration renewals, and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate Review (around day 90)
- Quarterly Success Review
Issues & Enhancements
- Update the shared support channel runbook with current escalation contacts and response SLAs.
- Deliver a measurement report with raw traces, test setup logs, and comparison to Solution Scope targets.
- Schedule and execute agreed re-test runs and deliver updated results before the Acceptance Gate.
- Record any calibration or configuration changes applied during retests in the deployment record.
- Restate acceptance criteria and numeric targets
- Document a clear pass/fail result for every acceptance criterion recorded in Solution Scope.
- Capture the formal acceptance decision with a named signatory when required and publish the acceptance record.
- Agree remediation tasks, timelines, and verification steps for any failed criteria and confirm incumbent wind-down status.
- Publish the acceptance decision document including pass/fail matrix, evidence links, and named signatory.
- Create remediation tickets for failed criteria with resolution dates and verification steps.
- Execute or confirm the incumbent wind-down plan and archive migration records as documented.
- Open-issue burn-down
- Reduce the number of open issues older than 30 days and agree owners and dates for remaining items.
- Ensure calibration renewal compliance rate meets the target recorded in Solution Scope and schedule upcoming renewals.
- Confirm mean time to resolution for operational issues is within acceptable bounds and document any process improvements required.
- Publish the open-issue burn-down with owners and committed resolution dates.
- Schedule required recalibrations and attach traceability certificates to the deployment record before expiry dates.
- Re-confirm acceptance criteria and owners
- Deployment is validated or a clear remediation plan is in place with owners and target dates.
- All parties confirm where the numeric acceptance criteria are recorded in Solution Scope and who will own measurement execution.
- High-priority blockers are identified and assigned for remediation before the first measurement review.
- Publish deployment validation summary including calibration certificate IDs and initial verification test log.
- Create remediation tasks for each blocker with a target resolution date and escalate any schedule risks.
- Confirm schedule and data requirements for the first measurement review.
- Present measured results vs Solution Scope targets
- Establish whether the pass rate of acceptance criteria, phase noise margin, and dynamic range margin are trending to meet Solution Scope targets.
- Document root causes for any shortfalls and agree remediation tasks with resolution dates.
- Confirm data package and test re-run schedule required for the Acceptance Gate meeting.
- Deployment and calibration verification
- Calibration renewal and traceability status
- Present final outcome data, pass/fail per criterion
- Diagnose gaps and root causes
- Corrective action plan
- Early verification signals
- Formal acceptance decision and signatory capture
- Operational performance spot-checks
- Enhancement and issue-handling cadence
- Calibration and traceability check
- Remediation plan for failed criteria
- Open issues and blockers
- Agree immediate remediation actions
- Runbook and escalation path verification
- Confirm timeline to Acceptance Gate
- Incumbent instrument wind-down
- Calibration traceability and certificate final confirmation