The measurement that started this search

• Tell me about the signal or measurement that triggered this search.
• How often does that measurement or event show up during a typical design sprint? Options: Multiple times per week, Once per week, A few times per month, Rarely, but when it appears it is critical
• When you try to capture that signal today, which instrument class and probe type do you default to? Options: 4-channel oscilloscope with passive probes, High-speed scope with active probes, Spectrum analyzer, Logic analyzer/protocol tool, Other - please describe
• What specific measurement output or visual would convince you this new instrument is adding unique value vs your current bench?
• Who on your team would cite the measurement success as sufficient justification to move toward purchase? Options: Design engineer (requester), Lab manager, Engineering director, Procurement/Finance, Other
• If this measurement were reliably solved tomorrow, what immediate project schedule or cost change would you expect?

How your current bench actually performs

• What important signal or behavior do you suspect your current instruments are failing to show?
• Describe the last time a debug extended beyond its expected window because of instrument limits, and what remained unresolved.
• How often during a normal release cycle do you hit bandwidth, sample-rate, or noise-floor limits that force a workaround? Options: Every sprint, Often, Occasionally, Rarely
• Which class of measurements do you keep returning to because your current toolchain is inconsistent (for example, high-speed serial jitter, sub-mV power noise, long-duration captures)? Options: High-speed serial timing/jitter, Power integrity (sub-mV), Wideband spectrum, Protocol decode and cross-trigger, Other
• Name one project consequence you expect in the next 3 months if these instrument limitations remain unaddressed.

When measurement limits become project risk

• When a measurement is ambiguous or missing, which downstream decision is most likely to be wrong as a result? Options: Go/no-go on a release, Component selection, Board spin schedule, Customer-facing demo readiness, Other
• Quantify the typical delay, rework hours, or cost you see when a critical signal is unclear. Options: <8 hours, 1-2 days, 3-7 days, >1 week or costly rework
• Which roles need definitive trace data to green-light a technical decision? Options: Design engineer, System architect, Lab manager, Verification engineer, Other
• Tell me about a recent trace that led the team to the wrong conclusion and what changed after you learned the truth.
• Name one acceptance failure or measurement gap that would stop an evaluation in its tracks.

Who must be convinced, and what will stop them

• Name the person or role most likely to block approval, and what evidence would persuade them.
• In practical terms, what budget or procurement criteria will the reviewer use to choose between instrument options? Options: Capital cost/PO limits, Total cost of ownership (probes/licenses), Vendor warranty and support, Standardization with existing platform, Other
• List the roles that need hands-on access to the demo unit during evaluation. Options: Requesting engineer(s), Lab technicians, Verification team, Lab manager, Procurement observer
• Assuming the engineer testing the demo says the instrument 'shows the problem', what remaining approvals or paperwork would still prevent ordering that week? Options: Capital approval, PO approval, Competitive bid requirement, Budget reallocation, None, we could order
• Identify the role that typically prepares the capital justification or purchase order in your organization. Options: Lab manager, Engineering director, Procurement, Finance, Requesting engineer

Defining a bench trial that proves something real

• Describe one hands-on test and its pass criteria that would make the evaluation conclusive for your team.
• List the probes, accessories, or fixtures that are essential to run that test on your board.
• Select the trial duration that fits your team's schedule. Options: 3 days, 1 week, 2 weeks, Longer than 2 weeks
• Assign the owner for data collection and pass/fail analysis during the trial. Options: Requesting engineer, Verification engineer, Lab technician, Third-party test lab
• Assuming the pass criteria are met during the bench trial, what would still prevent your lab from purchasing within 30 days? Options: Budget cycle timing, Procurement gate/competitive bid, Stakeholder sign-off missing, Probe or license budget, Nothing would stop it
• Choose the acceptance metrics that matter most for this trial. Options: Measured bandwidth fidelity, Noise floor (dBV or mVpp), Protocol decode accuracy, Setup time to first meaningful trace, Probe compatibility with board, Analysis repeatability

Practical constraints we must clear first

• Identify any integration, facility, or scheduling gap that would immediately disqualify your lab from running a demo.
• Provide a short inventory of the instrument licenses, software keys, and probe inventory that would need replacing or reconciling for a new platform.
• Point to the person who owns physical bench space, power, and network access, and indicate whether delivery can be scheduled within your target window. Options: Yes, within 1 week, Yes, within 2-4 weeks, No, requires planning >4 weeks
• Are there regulatory, safety, or facility reviews that could block installation of a demo unit? Options: Yes - safety/facility review, Yes - IT/network security review, No formal reviews required, Unsure, need to check
• Indicate which single constraint, if any, would prevent a demo within 4 weeks. Options: Bench space, Power or cooling, Procurement timing, Software license transfer, Nothing prevents it

Other options on the table

• Paint the conditions under which you would keep your current instruments rather than change to a new platform.
• Select the alternatives you are evaluating alongside this demo. Options: Internal instrument upgrade, Competitor demo loaner, Lower-cost alternative, Software-only analysis upgrade, Maintain current setup
• Has anyone on the team proposed solving this internally without an outside vendor or partner? If yes, briefly describe the proposed approach. Options: Yes - internal hardware tweak, Yes - custom analysis scripts, No one has proposed in-house fix, Unsure
• Indicate what would have to be true about your current approach for you to stay with it instead of changing platforms. Options: No additional cost, Equal or better measurement fidelity, Probe and software reuse, Faster time-to-result, Other
• Imagine a competitor matched the measurement fidelity but required replacing probes and software, would that cause you to switch? Options: Yes, if fidelity is equal or better, Maybe, depending on total cost, No, probe/software replacement barrier is too high

How we'll know the trial succeeded and what happens next

• Outline the exact decision you plan to make if the trial meets the agreed measurements, and the target date for that decision.
• Choose the acceptance metrics below that must be met to call the trial a pass. Options: Bandwidth and rise-time fidelity, Noise floor threshold, Protocol decode reliability, Repeatability across captures, Setup time to first valid result
• Point to the role that will sign the purchase order if the trial succeeds. Options: Lab manager, Engineering director, Procurement, Finance
• Provide the procurement gates or required documents that would be needed to convert trial success into an order (for example, PO template, capital approval form, competitive-bid waiver).
• Realistically, what is your ideal timeline to start the bench trial and reach a purchase decision? Options: Start within 1 week, decision within 4 weeks, Start within 2-4 weeks, decision in 1-2 months, Start in >4 weeks, decision in 2-3 months, Unsure / depends on approvals

• Deliver oscilloscope, spectrum analyzer, or generator unit
• Provide demo/loaner evaluation unit
• Install probes, cables, and accessory kit
• Perform factory calibration and verification
• Commission instrument on the bench (connect and verify DUT)
• Load and activate analysis applications and protocol decodes
• Deploy measurement automation scripts and templates
• Train engineers on instrument UI and common workflows
• Provision probe compatibility adapters and differential probe setup
• Configure fleet standardization profile across instruments
• Enable data export, waveform capture, and PC integration
• Provide extended warranty, onsite service, and repair plans
• Offer financing and capital-purchase options

Deliver oscilloscope, spectrum analyzer, or generator unit

• Specify the instrument family and model range you need for the evaluation (for example: 4-channel 8 GHz oscilloscope, 26 GHz spectrum analyzer, 1 GHz signal generator).
• Do you require a particular front-end configuration such as channel count, analog bandwidth, input impedance, or ADC resolution? Options: Yes, No
• List the DUT interfaces and connector types on your board that the instrument must support (examples: SMA, Samtec high-speed connector, dedicated probe pads).
• Confirm the minimum performance thresholds required: minimum bandwidth (GHz), minimum real-time sample rate (GS/s), and acceptable noise floor (mV RMS).
• How soon do you need the unit delivered to your lab bench (lead time in business days)? Options: 1-3 business days, 4-7 business days, 8-15 business days, More than 15 business days

Provide demo/loaner evaluation unit

• Do you prefer a shipped demo unit, an on-site loaner, or lab pickup for the hands-on evaluation? Options: Shipped demo unit, On-site loaner, Lab pickup
• How long should the loaner evaluation period be to validate measurements on your project (typical options: 3 days, 7 days, 14 days)? Options: 3 days, 7 days, 14 days, Other (specify)
• Who will be the primary engineer responsible for running the hands-on trial and creating the evaluation notes or sign-off?
• What objective acceptance criteria will confirm the loaner evaluation is successful for your design (provide measurable targets such as captured 5 GHz bandwidth with SNR > X dB, protocol decode error rate < Y%, or power noise < Z mV)?
• Are there regulatory, export control, or site access constraints we must meet to deliver or install the loaner unit (examples: EHS clearance, export license, delivery time windows)? Options: Yes, No

Install probes, cables, and accessory kit

• Specify the probe models and probe tip types you require (examples: passive 10x, 1 GHz differential probe, active high-impedance probe, current probe rated to X A).
• Select the cable types and lengths needed for connecting your DUT (examples: SMA 50 ohm coax 0.5 m, 1 m, micro-coax breakout). Options: SMA 0.5 m, SMA 1 m, Micro-coax breakout, USB-C power lead, Other (specify)
• Will you need probe accessories for signal redrive, compensation, or fragile test points (examples: probe amplifiers, ground springs, attenuation adapters)? Options: Yes, No
• Verify that probe tip impedance and attenuation match your high-speed test points (examples: 50 ohm, 10:1) and list any fragile micro-pad areas requiring special fixtures.
• Do you require probe inventory labeling or kitting to match your lab's probe matrix and storage conventions? Options: Yes, No

Perform factory calibration and verification

• When do you require the instrument calibration date to be relative to delivery (examples: calibration within 3 months, 6 months, 12 months)? Options: Within 3 months, Within 6 months, Within 12 months, Other (specify)
• Are you requiring a traceable calibration certificate to a national metrology institute for the instrument front end and probes? Options: Yes, No
• Identify specific verification tests you want run at delivery such as bandwidth verification with step-response, noise-floor measurement, or channel-to-channel skew.
• Estimate acceptable measurement tolerances for calibration verification (for example: bandwidth within ±5%, noise floor within X dB, channel skew within Y ps).
• Do you require a signed calibration certificate and measurement report to be uploaded to your asset management system? Options: Yes, No

Commission instrument on the bench (connect and verify DUT)

• Who will own bench commissioning tasks and final approval (examples: lead design engineer, lab manager, facilities coordinator)?
• How will you verify commissioning against your DUT: list measurable pass/fail checks such as capture of the target 5 GHz signal with specified amplitude accuracy (mV), timing alignment within Y ps, and probe compensation within Z%.
• Describe the DUT connection sequence and any special fixtures, ground references, or grounding procedures required for safe probing (include lockout/tagout if used).
• Select required safety and electrostatic discharge (ESD) controls we must follow during commissioning. Options: ESD mat and wrist strap, Ground isolation, Lockout/Tagout (LOTO), No special controls
• Are there DUT operating conditions we must reproduce during commissioning (examples: specific supply voltages, clock rates, thermal soak)? Options: Yes, No

Load and activate analysis applications and protocol decodes

• Identify the protocol decodes or software applications you need activated on the instrument for evaluation (examples: PCI Express, USB, I2C, DDR analysis).
• What decode accuracy or application validation threshold will you accept for sign-off (examples: protocol decode correlation > 99%, decode error rate < 1%, eye mask margin > X unit intervals)? Options: Decode correlation > 99%, Decode correlation 95-99%, Decode correlation < 95%, Custom threshold (specify)
• Will you need offline PC integration for captured waveforms and analysis logs (export to CSV, VCD, MAT, or import into MATLAB/LabVIEW)? Options: Yes, No
• Provide the file formats and host integration endpoints your team uses for waveform analysis and archival (examples: CSV, vendor waveform format, MATLAB MAT, NAS path).
• Do you require license activation for specific analysis modules during the demo (examples: protocol decode license, jitter analysis, power integrity suite)? Options: Yes, No

Deploy measurement automation scripts and templates

• Identify the automation language or API your team uses for bench scripting (examples: Python with VISA, SCPI/IVI, LXI HTTP).
• Are prebuilt templates required for common tests such as power integrity sweeps, DDR eye scans, or protocol-conformance tests? Options: Yes, No
• State the pass/fail thresholds automation should enforce (examples: jitter < X ps, eye height > Y mV, protocol error count = 0).
• Will automation need to log raw waveforms and measurement metadata to your network storage or laboratory information management system (LIMS)? Options: Yes, No
• Which execution cadence do you expect for automated runs (ad-hoc, nightly, triggered by CI build, scheduled weekly)? Options: Ad-hoc/manual, Scheduled nightly, Triggered by CI/build, Other (specify)

Train engineers on instrument UI and common workflows

• How many engineers require hands-on training and what are their typical experience levels (examples: junior, intermediate, senior)? Options: 1-2 engineers, 3-5 engineers, 6+ engineers
• Select the training format you prefer: on-site instructor-led, remote live workshop, or recorded self-paced modules. Options: On-site instructor-led, Remote live workshop, Recorded modules
• Would you like custom lab exercises that use your DUT to reproduce a key measurement such as a 5 GHz capture or a power integrity sweep? Options: Yes, No
• Provide the success criteria for training (examples: an engineer can set up a 4-channel capture, run a protocol decode, and export waveforms without assistance).
• Do you require training materials and step-by-step lab guides to be uploaded to your internal knowledge base after the session? Options: Yes, No

Provision probe compatibility adapters and differential probe setup

• List the differential probe impedance and bandwidth requirements for your measurement points (for example: 1 GHz differential, 50 ohm, DC to 1 GHz).
• Indicate whether special probe adapters are required for micro-coax, high-density board connectors, or probe-on-pad fixtures on your DUT. Options: Yes, No
• Verify probe polarity and grounding constraints for differential measurements to avoid ground loops on your board and note any special grounding fixtures required.
• Choose the passive or active probe types and quantities needed from the compatibility kit. Options: Passive 10x probe, Active high-impedance probe, 1 GHz differential probe, Current probe, High-voltage probe, Other (specify)
• Are any custom probe shims, pogo fixtures, or PCB testpoint adapters required to access your high-speed nets? Options: Yes, No

Configure fleet standardization profile across instruments

• Indicate if a fleet standardization profile is required (same firmware, app set, probe matrix across multiple instruments). Options: Yes, No
• State the configuration items that must be identical across instruments (examples: firmware version, analysis app list, probe naming convention, calibration windows).
• Assign the owner responsible for maintaining the standardization profile and rolling out firmware or app updates.
• How will you measure configuration drift across instruments (examples: periodic audit, CI/CD firmware checks, automated health reports)? Options: Periodic audit, Automated health reports, CI/CD firmware checks, Other (specify)
• Do you require a rollback plan for firmware or app changes in case an update breaks a validated measurement workflow? Options: Yes, No

Enable data export, waveform capture, and PC integration

• Choose the export formats required for waveform analysis and archival (examples: CSV, vendor waveform file, MAT, VCD). Options: CSV, Vendor waveform format, MAT (MATLAB), VCD, Other (specify)
• Are there automated capture triggers you need such as pre-trigger buffer, level-crossing, or protocol-error triggers to drive waveform storage? Options: Yes, No
• What retention policy and storage endpoint do you use for captured waveforms (examples: NAS path, LIMS project code, cloud bucket)?
• Describe the PC integration workflow for post-processing (examples: direct USB transfer, Ethernet remote control, SCPI-based capture, automated waveform sync to NAS).
• Do you require metadata tagging of captures (examples: board revision, firmware revision, test ID) to be embedded with each waveform file? Options: Yes, No

Provide extended warranty, onsite service, and repair plans

• State your preferred service level agreement (SLA) tier for instrument uptime and repair response times (examples: return-to-factory 10 business days, onsite 5 business days, next-business-day onsite). Options: Return-to-factory (10 business days), Onsite repair (5 business days), Next-business-day onsite, Custom (specify)
• Is loaner coverage required during repairs to avoid project delays? Options: Yes, No
• Note any internal approval thresholds we must meet for repairs to proceed (examples: capital budget limits, PO approval thresholds, fixed-asset tagging).
• Are there preferred technician access windows or site scheduling constraints for onsite service visits? Options: Yes, No
• Do you require periodic preventative maintenance visits and, if so, what frequency (examples: annual, biannual)? Options: Annual, Biannual, Quarterly, Not required

• desired_state
• current_state
• stakeholders
• 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

• Commercial Quote
• Product Purchase Agreement
• Order Confirmation
• Software License Agreement
• Warranty Statement
• Maintenance & Support Agreement
• Probe & Accessory Order Addendum
• Capital Approval & PO Process Confirmation
• Export, Trade Controls & End-Use Declaration
• Data Processing Addendum (conditional)

• Go-live Health Check
• First Measurement Review
• Adoption and Realization Review, 90-day
• Quarterly Operational Review

• Confirm probe replenishment or calibration orders to maintain required probe availability.
• Run and record reproducibility checks for the top 3 use-cases showing variance and share results.
• Present aggregated outcome data vs Solution Scope targets
• Confirm whether the percent of measurement use-cases meeting the acceptance criteria recorded in Solution Scope meets expectations and document any shortfalls.
• Validate trained-user proficiency rate and adoption coverage across the team, and identify training follow-ups if needed.
• Complete the incumbent wind-down checklist or document reasons for formal retention and next steps.
• Produce an adoption report listing active users, proficiency checks, and coverage per lab area.
• Execute incumbent decommissioning tasks or confirm read-only retention and archive completion with documentation.
• List remaining remediation items with completion dates and circulate the remediation plan for acknowledgement.
• Review open issues and support ticket backlog
• Reduce high-severity open support tickets and drive median time-to-resolution below the agreed SLA.
• Ensure planned firmware or software changes that affect measurement fidelity have target delivery windows.
• Confirm probe inventory and calibration planning to support continued adoption.
• Publish the prioritized support backlog with expected resolution dates and severity labels.
• Share the planned firmware/software release schedule and its scope for measurement-impacting fixes.
• Re-confirm acceptance criteria and owners
• Confirm the instrument and software are deployed and configured per the deployment checklist and Solution Scope.
• Identify and document all early blockers with remediation actions and timelines.
• Agree date and data deliverables for the first measurement review.
• Document deployment defects and circulate a remediation summary for async updates.
• Provision any missing probes, accessories, or license entitlements required for the evaluation.
• Schedule the First Measurement Review with required measurement data uploaded to the shared channel.
• Present first measurement results vs Solution Scope targets
• Determine whether the percent of evaluated measurement use-cases meeting the acceptance criteria recorded in Solution Scope is tracking toward the target.
• Identify root causes for any gaps and agree concrete remediation steps with deadlines.
• Confirm reproducibility checks and data to be delivered for the 90-day adoption review.
• Deliver a measurement results package with annotated waveforms, pass/fail markers vs Solution Scope criteria, and raw data links.
• Document and execute agreed configuration or probe changes, then re-run the affected test cases.
• Adoption and training effectiveness
• Deployment and configuration validation
• Firmware, software, and enhancement request status
• Diagnose gaps and root causes
• Agree corrective actions and short-term experiments
• Early adoption signals and usage patterns
• Incumbent system wind-down or retention status
• Operational health of probes and accessories
• Short operational items and next quarter checkpoints
• Open issues, remediation closure plan, and timeline
• Validate calibration and reproducibility checks
• Open issues and blockers
• Confirm timeline to follow-up adoption review
• Agree immediate remediation actions and next checkpoint
• Confirm operational cadence going forward