How this machine needs to perform for your business

• Tell me about the machine design or product line this project targets, including axis count, typical cycle time, and expected production volume.
• Who on your team owns controls architecture decisions for this machine family? Options: Controls engineer, Engineering manager, Plant engineer, Procurement, Third-party integrator, Other
• How many machines of this design do you expect to ship per year? Options: <10, 10-50, 51-200, 201-1000, >1000
• In your last machine release, which commissioning tasks consistently took the most time and why?
• Which PLC platform do you standardize on across these machines, and how strict is the requirement to keep that programming environment? Options: Single PLC platform across fleet, Two PLC platforms, Multiple PLC platforms (>2), Strictly must keep current programming tool, Open to tool change
• How quickly do you need a validated drive solution available on the bench to stay on your product schedule? Options: Within 1 week, Within 2-4 weeks, Within 1-2 months, No immediate urgency (>2 months)

Where the current system actually costs you time or money

• If a drive's torque control missed your target by 5 percent on a production axis, what downstream costs or risks would that create for your line or customer commitments?
• Describe the most recent commissioning failure that delayed a machine shipment, and how long the delay lasted.
• Which measurable signals do you use to decide a drive is unacceptable, select all that apply. Options: Torque deviation (percent), Settling time (ms), Commissioning hours, Energy consumption (kWh), Network packet loss or jitter, Other
• How often do you need vendor field support that your local distributor cannot provide within 48 hours? Options: Weekly, Monthly, Quarterly, Rarely or never, Unsure
• Who inside your organization feels the pain most when a drive integration stalls, and what do they typically escalate to?

The bench test that would convince you to switch

• What single bench result would make you switch platform immediately? Options: Torque within 2% RMS, Commissioning under 8 hours per axis, Deterministic jitter <1 ms on motion network, Local support response <48 hours, Other
• Walk me through the motion profile and test sequence you run on your bench for candidate drives.
• List the test instruments and data points you require during a bench trial, for example encoder traces, torque error logs, and timestamped commissioning steps. Options: High-resolution torque logger, Encoder resolution and trace, Timestamped commissioning log, Power and energy meter, Network packet capture, Other
• How long is your typical bench trial window and what turnaround do you require for a local field engineer during that window? Options: 1-3 days, engineer available within 48 hours, 1 week, engineer available within 48 hours, 2-4 weeks, engineer on-site within 72 hours, Flexible / other
• Do you have an acceptance checklist that explicitly defines pass or fail for torque control, network determinism, and commissioning time? Options: Yes, formal checklist with pass/fail, Yes, informal acceptance criteria, No, we decide case-by-case, Unsure

PLC and toolchain compatibility are often the unstated dealbreakers

• If a candidate drive required a new programming tool incompatible with your PLC, how likely would you be to proceed with adoption? Options: Not likely at all, Unlikely but possible with incentives, Likely if proven benefits exceed retraining cost, Very likely
• Tell me about any past attempts to integrate a third-party drive with your PLC and what specifically broke during commissioning.
• Name the role that manages firmware and toolchain validation for your PLC fleet today. Options: Controls engineer, Firmware engineer, Maintenance lead, IT or OT team, Third-party integrator, Other
• How many unique PLC versions and drive firmware combinations exist across the machines you are targeting? Options: 1-2 combinations, 3-5, 6-10, >10, Unknown
• What are the consequences if a new drive forces you to update PLC programs across 50 machines?

Concrete constraints that will stop a pilot cold

• Identify the single site constraint that would force you to stop a pilot, for example lack of downtime, missing test-bench access, or no spare-parts stocking. Options: No available downtime, No bench or test access, No spare-part stocking plan, Network or security restrictions, Regulatory or customer approvals, Other
• Provide a short inventory of the integration dependencies at the site, including PLCs, encoders, safety controllers, and network switches. Options: PLC, Encoders and sensors, Safety controllers, Network switches, Power infrastructure, HMI, Other
• Do you have a named owner for site access and commissioning windows, and if so, which describes the current state? Options: Yes, named owner exists, No, owner not assigned, In process of assigning an owner, Unsure
• Estimate the headcount of technicians qualified to support drive commissioning without outside help. Options: 0-1, 2-5, 6-10, >10
• When would regulatory, audit, or customer acceptance steps block a deployment timeline for this project?

Who and what you are competing against right now

• Imagine your incumbent drive stayed available indefinitely, what would it have to prove over the next 12 months for you to cancel the change?
• List the alternative solutions or classes you are evaluating, including internal redesign, low-cost imports, major automation vendors, or system integrators. Options: Incumbent vendor, Major automation vendor, Low-cost imports, In-house redesign, System integrator solution, Other
• Identify the stakeholders within procurement or engineering who are advocating for an internal fix rather than partnering with an outside vendor. Options: Procurement, Engineering manager, Plant operations, Maintenance, No internal advocate, Other
• Rank the vendor capabilities you consider must-have versus acceptable trade-offs, using these categories. Options: Local field support, Native PLC toolchain and commissioning tool, Servo precision and torque control, Commissioning time reduction, Price, Spare-parts availability, Warranty and SLA
• Estimate how long an internal team would take to develop and validate a replacement drive or integration, including requalification per machine variant. Options: <3 months, 3-6 months, 6-12 months, >12 months, Not considering internal build

The acceptance gates that release money and schedule

• Should the pilot meet your torque, commissioning, and energy targets, what internal approval is required to release funds and place an order? Options: Controls engineering sign-off, Engineering manager plus procurement, Plant operations approval, Executive approval (VP or CTO), Other
• Provide the specific acceptance metrics and numeric thresholds you will require for torque accuracy, commissioning time, and energy savings.
• Name the approvers who sign the acceptance form that triggers invoicing and any parties who approve warranty exceptions. Options: Controls engineer, Quality manager, Procurement, Operations manager, Other
• How quickly do you expect to invoice after acceptance, and what proof of test do you need attached? Options: Invoice within 0-7 days with signed test logs, Invoice within 7-30 days with signed acceptance and logs, Invoice after delivery milestones are met, Other
• What single contractual term would kill the deal for you, for example a short warranty or a delivery window that misses your production ramp? Options: Short warranty (<1 year), Delivery after production ramp, Unacceptable SLA on support response, Rigid payment terms, Other

If this all aligns, how soon can we start and who makes it happen

• Assuming the bench proves the numbers, what would move you to place an order within the month? Options: Clear acceptance metrics met, Purchase order authority available, Budget already allocated, Spare-parts and logistics confirmed, Other
• When is your production window that can accept a pilot and by when do you require full deployment to be completed? Options: Pilot within 0-4 weeks, full deployment within 3 months, Pilot 1-3 months, full deployment 3-6 months, Pilot 3-6 months, full deployment 6-12 months, Flexible / other
• Give the name and role of the day-to-day contact for the pilot and the executive sponsor we should keep informed.
• Point to the expected blockers in the first 30 days of a pilot and indicate which of them you control versus external vendors control.
• Are there any procurement lead times, import restrictions, or spare-part minimums we must factor into scheduling? Options: Yes, long lead times (>8 weeks), Yes, medium lead times (4-8 weeks), No significant lead times, Unsure

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

• Supply Variable Frequency Drive Hardware
• Supply Servo Motor and Amplifier Units
• Supply PLC and HMI Hardware Kits
• Provide Commissioning Tool License and Setup
• Execute Single-Axis Bench Test with Customer Profile
• On-Site Drive Commissioning and Motor Integration
• Port Motion Programs from Existing PLC to Platform
• Configure Deterministic Motion over Network Bus
• Torque-Loop and Servo Parameter Optimization
• Local Field Application Engineer Dispatch (48‑hour SLA)
• Spare Parts Kitting and Initial Stocking
• Execute Machine Acceptance Test and Documentation
• Provide Firmware Updates and Maintenance Agreement

Supply Variable Frequency Drive Hardware

• Specify the motor frame sizes and continuous rated power (kW) for each drive required
• List the input voltage and enclosure (IP) requirements for drives on your line Options: 230 V single-phase, 400-480 V three-phase, Other (describe)
• Identify any space or mounting constraints for cabinet or panel-mounted drives (rack depth, cutouts, or airflow limits)
• Confirm whether drives must include built-in regenerative braking or if an external braking resistor is acceptable Options: Built-in regenerative, External braking resistor acceptable, Not required
• Estimate the maximum ambient temperature and altitude the drives must tolerate at the deployment site Options: <40°C and <1,000 m, 40–50°C or 1,000–2,000 m, Other (describe)

Supply Servo Motor and Amplifier Units

• Provide the rated continuous torque and peak torque requirements for each axis (Nm) and their duty cycle
• List required feedback types and resolutions (incremental encoder, absolute encoder, resolver, CPR) Options: Incremental encoder (CPR), Absolute encoder, Resolver, Other (describe)
• Identify the absolute maximum motor current and supply voltage for amplifier selection
• Confirm if flange-mount or through-shaft mounting is required and supply mounting dimensions or drawings Options: Flange-mount (attach drawing), Through-shaft (attach drawing), Either / flexible
• Estimate expected peak inertia ratio (load reflected inertia / motor inertia) for each axis or provide CAD assembly reference Options: <5:1, 5:1–20:1, >20:1 or provide CAD

Supply PLC and HMI Hardware Kits

• Specify the PLC family or control CPU class you plan to use and required I/O counts (digital, analog, high-speed counters)
• Indicate HMI screen sizes, number of operator stations, and whether the HMI must be web-accessible Options: 1 local HMI, 1 local + remote web HMI, Multiple local HMIs (specify)
• List any required certified safety I/O or safety PLC modules and the safety category (e.g., e-stop response time and required SIL/Pld)
• Identify necessary I/O expansion or third-party gateway modules to connect legacy sensors or drives
• Confirm whether spare PLC CPUs or HMI panels should be included in the kit and how many spares you want to stock initially Options: No spares, 1 spare CPU / 1 spare HMI, Custom quantity (specify)

Provide Commissioning Tool License and Setup

• Specify the number of commissioning tool licenses and whether they must be node-locked or floating Options: Node-locked, Floating, Need recommendation
• Indicate the target workstation OS and whether the commissioning tool must be preinstalled or provided as installation media Options: Windows 10/11, Windows Server, Other (specify)
• Identify required access levels for commissioning tool users (engineer, operator, readonly) and how many user seats per level Options: Engineer / Operator / Readonly (specify counts), Single-seat
• Describe any VPN, DMZ, or air-gap constraints that affect remote commissioning or diagnostic access to the control network
• Indicate whether training on the commissioning tool is required as part of license setup and preferred delivery mode Options: Remote instructor-led, On-site training, Self-study materials

Execute Single-Axis Bench Test with Customer Profile

• Name the exact motion profile file(s) or provide a sample profile (position vs time or torque vs time) to be used on the bench
• Indicate the bench axis payload and coupling details or attach the bench wiring and mechanical connection drawing
• Specify the acceptance thresholds to validate bench torque control and responsiveness (e.g., steady-state torque error in Nm or % and settling time in ms)
• Provide the measurement instrumentation available on your bench (torque sensor model or accuracy, encoder resolution, oscilloscope availability)
• Confirm the maximum bench test duration and number of profile repetitions required for statistical assessment Options: Single run, 3 runs, 10 runs or custom (specify)

On-Site Drive Commissioning and Motor Integration

• Specify the on-site commissioning window (dates and available shift hours) and any locked-out production periods
• List the site electrical single-line diagram (SLD) and panel wiring documents you will provide prior to commissioning Options: SLD provided, Panel wiring drawings provided, Not available yet
• Identify the local safety and lockout/tagout (LOTO) procedures the commissioning team must follow
• Specify how you will validate motor-drive integration on site (e.g., zero-load spin, torque step test, full profile run) and who signs off Options: Zero-load spin, Torque step test, Full profile run, Custom (describe)
• What measurable acceptance criteria will confirm on-site commissioning is complete (limit to one response: torque error %, commissioning time vs baseline, network jitter threshold)?

Port Motion Programs from Existing PLC to Platform

• Provide the source PLC family and whether motion programs are ladder, structured text, or function block diagrams Options: Ladder, Structured Text, Function Blocks, Mixed
• Indicate how many motion routines or axes require porting and the average LOC (lines of code) or complexity per routine Options: 1-3 axes, 4-8 axes, 9+ axes
• Describe any custom motion blocks, proprietary instructions, or vendor-specific function blocks that must be re-implemented
• Identify who will own unit test cases for the ported programs and how you will provide sample inputs and expected outputs
• Select your preferred approach for program porting and verification Options: Automated conversion + manual review, Full manual rewrite by integrator, We need recommendation

Configure Deterministic Motion over Network Bus

• Specify your control network topology, including switch types, segment lengths, and whether ring or line topology is used
• Indicate target cycle time for deterministic motion (ms) and acceptable jitter or packet-loss thresholds
• Identify existing network devices that will remain on the control bus and whether firmware or configuration changes are permitted
• Describe your plan for network redundancy and failover during motion (e.g., ring redundancy, dual homing) Options: No redundancy, Ring redundancy (fast recovery), Dual homing / other (describe)
• Confirm whether you require on-site network verification using packet captures and deterministic timing reports as part of acceptance Options: Yes, include captures and reports, No, not required, Optional (discuss)

Torque-Loop and Servo Parameter Optimization

• Provide target torque-loop bandwidth and stability margins required for each axis or motor type
• List any predefined tuning recipes you expect us to follow (inertia compensation, notch filters, anti-resonance) and attach examples
• Identify whether dynamic load changes or external disturbances are common and provide representative disturbance profiles Options: Light disturbance, Moderate, Frequent/heavy (attach profile)
• Describe how you will measure and accept closed-loop torque performance on production machines (sensor placement, sampling rate, acceptance thresholds)
• Indicate if adaptive or auto-tuning modes are allowed in production or if tuning must be locked after commissioning Options: Auto-tuning allowed, Tuning locked after commissioning, Hybrid approach

Local Field Application Engineer Dispatch (48‑hour SLA)

• Specify your facility address and local contact for SLA fulfillment to verify 48-hour reachability
• Indicate preferred on-site arrival window for dispatched engineers (business hours, night shift, weekend) Options: Business hours, Night shift, Weekend, Specific window (specify)
• Identify required certifications or site clearances the field engineer must have before arrival (safety cards, badging)
• Confirm whether remote troubleshooting is acceptable as a first step prior to dispatch under the 48-hour SLA Options: Remote troubleshooting first, Immediate dispatch only, Case-by-case
• Specify any travel or site access costs that should be included in the scope versus billed as time-and-materials Options: Include travel in scope, Bill travel separately, Discuss per case

Spare Parts Kitting and Initial Stocking

• Provide the Bill of Materials (BOM) or list of critical SKUs you require stocked as spares for the first 12 months
• Indicate desired initial stocking levels for each SKU (units) and a reorder threshold Options: 1 unit each critical SKU, 2 units each, Custom (specify)
• Identify preferred warehousing location for spares (on-site, regional distributor, central warehouse) Options: On-site, Regional distributor, Central warehouse
• Describe any serialized tracking or asset-tagging policies for spare drives and controllers you require
• Confirm whether you require cold-spare (unconfigured) units or warm-spare (pre-configured to a specific machine ID) Options: Cold-spare, Warm-spare (pre-configured), Mix of both

Execute Machine Acceptance Test and Documentation

• State the final acceptance tests you require on the integrated machine (list specific profile runs, throughput targets, quality metrics)
• Provide the format and minimum contents required for acceptance documentation (test logs, oscilloscope screenshots, firmware versions, sign-off sheet)
• Indicate who in your organization is authorized to sign acceptance and their title or role
• What evidence will validate that the machine acceptance tests meet your success signals (examples: torque error < X Nm, commissioning time reduced by Y%, energy consumption per cycle)
• Confirm any post-acceptance warranty start conditions or burn-in period requirements that affect invoicing or SLA start dates Options: Warranty starts at sign-off, Warranty starts after 30-day burn-in, Custom (specify)

• Purchase Agreement
• Order Confirmation & Payment Schedule
• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Service Level Agreement (SLA)
• Product Warranty
• Delivery and Milestone Schedule
• Acceptance Test Protocol
• Spare-Parts & Stocking Agreement
• Change Order Agreement
• Regulatory Compliance Addendum (conditional)
• Termination Agreement

• Go-live Health Check (week 1-4)
• First Measurement Review (week 4-10)
• Quarterly Operational Review
• Annual Success Retrospective

• Document the enhancement request intake and triage process and circulate it to operational teams.
• Verify commissioning time and energy consumption metrics remain within tolerances relative to the targets recorded in Solution Scope.
• Close or re-prioritize persistent tickets and document remaining blockers with resolution dates.
• Ensure spare-parts stocking and maintenance windows are aligned with upcoming rollout needs.
• Publish the ticket burn-down summary with updated target resolution dates.
• Place orders or reserve inventory for identified spare-part SKUs to meet the stocking plan.
• Schedule the next maintenance / firmware update window and communicate expected impacts.
• 12-month outcomes versus targets
• Confirm whether cumulative energy savings and mean commissioning time per machine meet the targets recorded in Solution Scope.
• Produce a prioritized lessons-learned backlog with clear remediation tasks and timelines.
• Agree the ongoing issue and enhancement request channel and triage SLAs for the next 12 months.
• Publish the annual outcomes report comparing realized metrics to Solution Scope targets.
• Create the prioritized lessons-learned backlog and schedule the top three improvement items into the next quarter.
• Re-confirm success criteria and owners
• Deployment confirmed complete and acceptance tests executed according to the sequencing recorded in Deployment.
• Legacy system decommissioning status documented and fallback habit closed.
• All critical open issues captured with remediation tasks and resolution windows.
• Publish the deployment verification log and updated runbook for commissioning within 3 business days.
• Archive or migrate legacy drive configuration and logs and confirm archive location.
• Create remediation tasks for each open issue with target completion dates.
• Present first data for torque accuracy and commissioning time
• Determine whether RMS torque error and average commissioning time per axis are trending toward the numeric targets recorded in Solution Scope.
• Identify root causes for any gaps and commit to concrete corrective actions with target dates.
• Confirm that local support responsiveness meets the expected 48-hour field response window or document required changes to meet it.
• Schedule a bench re-run using the updated tuning parameters and the buyer's motion profiles, and record the results.
• Update the commissioning checklist to reflect discovered configuration adjustments and distribute it to the field team.
• Collect and circulate the field support response log covering the first 30 days for audit.
• Metric trend review
• Deployment and commissioning validation
• Persistent issues and ticket burn-down
• Lessons learned and retrospective
• Diagnose root causes for any metric gaps
• Ongoing issues and enhancement channel
• Assess local support responsiveness
• Early adoption signals and usage patterns
• Spare-parts and maintenance readiness
• Agree corrective actions and timeline to the next checkpoint
• Enhancement request triage
• Long-term risk and obsolescence planning
• Incumbent system decommissioning and fallback closure
• Open issues and immediate remediation actions