The product in one line and the numbers that matter

• How would you summarize the product you are planning to ramp in one sentence?
• Tell me about the current prototype maturity, specifically which functional tests and environmental tests are already passing Options: Basic functional tests only, Functional and limited environmental, Full environmental and reliability tests, Prototype still in early development
• Walk me through your target production volumes for the pilot, month 1, and month 12 Options: Pilot: under 100 units, Month 1: 100-500, Month 12: 500-2,000, Pilot: 100-500, Month 1: 500-2,000, Month 12: 2,000-10,000, Pilot: 500-2,000, Month 1: 2,000-10,000, Month 12: 10,000+
• Estimate the yield you expect at pilot start, after one month of production, and after three months Options: Pilot start: <70%, 70-85%, 86-94%, 95%+, 1 month: <80%, 80-90%, 91-96%, 97%+
• Which stakeholders will be the primary decision makers and day-to-day owners from your operations, engineering, and procurement teams? Options: VP Operations, VP Engineering, Program Manager, Procurement Lead, Quality Lead, Other
• Do you currently have a documented ramp success criterion, such as target first-pass yield or MTBF for initial production? Options: Yes, fully documented, Partially documented, No, only internal targets, No, not defined

Imagine ramp day goes wrong: the failure modes that stop progress

• Imagine ramp day arrives and yields are 30% below your target; what stops you from pausing the program or changing course immediately?
• Describe the engineering change control process you use when a critical assembly requires a design adjustment during pilot Options: Fast-track emergency ECN with 24-48 hour approval, Standard ECN with 1-2 week approval, Ad hoc verbal approvals, then formalize later, No formal ECN process
• When was the last time a supplier lead-time issue shifted your production schedule, and what operational steps followed to contain the impact?
• Tell me which single-source components you are still accepting for this product and why alternatives are not available
• Who finds out first in your leadership chain if the pilot misses quality gates, and who has final authority to pause production? Options: Program Manager, VP Operations, VP Engineering, Quality Lead, Procurement Lead

Costs that hide behind low yields and late fixes

• Name one recurring defect that, if left unresolved through pilot, would multiply your support or replacement costs
• How many engineering hours per week does your team currently spend firefighting production issues during early builds? Options: 0-10 hours, 10-40 hours, 40-80 hours, 80+ hours
• Describe how you currently measure customer-facing risk for new products, for example warranty exposure, returns, or MTTR
• Estimate your average time from detection of a production defect to deployment of the corrective change in the line Options: <48 hours, 48 hours to 7 days, 1-3 weeks, 3+ weeks
• If you could not improve that average within your launch window, would you delay the market launch, accept higher early returns, or fund parallel mitigations? Options: Delay launch, Accept higher returns, Fund expedited mitigation, Unsure

Hard gates and prerequisites that will stop us from starting

• List any regulatory approvals, export controls, or facility certifications that must be in place before pilot builds begin
• Who owns facility access, vendor badging, and safety approvals on your side, and how quickly can those be granted to a new partner? Options: Single owner with rapid access, Multiple owners, moderate lead time, No clear owner, needs setup
• Confirm whether you have named test fixtures, first-article inspection plans, and functional test scripts to hand off at project start Options: All available and validated, Some available, need finalization, None available yet
• Which integration dependencies exist for production data, for example MES, ERP, or customer acceptance systems, and are APIs or connectors available? Options: MES integration required, API available, ERP integration required, API available, Manual reporting sufficient, No integrations required
• Provide the number of full time equivalents you can commit from engineering and supply chain during pilot Options: 0-1 FTE, 2-3 FTE, 4-6 FTE, 7+ FTE

Who else could win this work and what would keep you with them

• Name the alternatives you are actively evaluating, including staying with the incumbent or keeping the work in-house Options: Incumbent contract manufacturer, Keep manufacturing in-house, New external partner, Split sourcing, Other
• For each incumbent or in-house option, what would have to be true for you to keep that approach instead of selecting an outside ramp partner?
• List the absolute must-have proof points that would make you switch to a new partner within 30 days, for example minimum yield, delivery date, or warranty terms
• Do internal teams believe they can execute the ramp without outside help, and who inside has proposed that approach? Options: Yes, confident internal team, Partially confident, need some external help, No, external help required, Proposal still under discussion
• Select the current short list status to help us prioritize next steps Options: Committed to incumbent, Leaning internal, Evaluating 1-2 external partners, Running an open RFP

Acceptance criteria that would let you sign quickly

• If the pilot demonstrates target yield and a stable process for two consecutive weeks, what exactly must be true for you to approve full-rate production that same week?
• Provide the measurable acceptance criteria you will use, such as target yield, first-pass yield, supplier on-time performance, and engineering-change stability
• Identify who signs production acceptance and the approval threshold measured in dollars per week or units per week Options: Program Manager signs under $50k/week, VP Operations signs under $250k/week, Executive signoff required for any full-rate start, Other
• Choose the monitoring cadence you will require during scale up Options: Daily shift-level reporting, Daily consolidated reporting, Weekly executive summary, Bi-weekly detailed review
• Suppose the pilot meets numeric criteria but one supplier remains a single-source risk, would you proceed to full-rate production? Options: Proceed with risk acceptance, Require second source before proceeding, Proceed with escrowed inventory and mitigation plan, Unsure

Operational handoffs, governance, and who does the heavy lifting

• When a production issue arises during pilot, which current escalation path most often short-circuits resolution?
• Outline the governance model you expect for ramp cadence, including who runs the weekly meeting and which KPIs are mandatory
• Identify the three named owners we will need from your side, for example quality lead, program manager, and procurement contact
• Pick the reporting format you prefer for daily yield and defect tracking Options: CSV export to ERP, Dashboard with API feed, PDF executive summary, Shared spreadsheet
• Suppose we propose a governance cadence that requires one full day per week of your engineering time during pilot, can you commit to that level of involvement? Options: Yes, committed, Yes, with caveats, No, can only provide limited support, Need to negotiate

Timeline trade-offs and the single decision that changes everything

• Assume your launch date cannot move, what trade-off are you willing to accept between initial yield and units shipped in month one? Options: Hold yield target, accept fewer units, Hit units target, accept lower yield, Delay launch to meet both, Other
• Share the lead time for the long-lead components that will most constrain the schedule and whether second-source agreements exist
• Clarify who must approve timeline slips and what level of delay triggers executive review
• Choose the timeline outcome that best matches your appetite if a single mitigation is needed Options: Fund expedited parts, Accept lower initial volume, Delay launch, Split shipments
• Should the pilot exceed your target window, would you pause the program, pay for expedited mitigation, or accept a delayed ramp? Options: Pause program, Pay for expedited mitigation, Accept delayed ramp, Decide case by case

• Ramp Solution Walkthrough

• Confirm the current state and cost to your program
• Customer confirms the demonstrated process and pilot sequence remove the primary causes of yield instability described in Discovery.
• Deliver a tailored pilot sequencing plan with named owners, milestones, and escalation points within five business days.
• Customer agrees that the proposed supplier mitigations reduce single-source risk to an acceptable level for pilot start.
• Walk through the process engineering approach applied to your prototype
• Provide a draft supplier mitigation plan for all single-source components, including backup options and lead-time commitments.
• Customer confirms the set of measurable ramp milestones and acceptance criteria that will be used to judge pilot success.
• Review pilot sequencing and timeline tied to your milestones
• Provide the BOM with preferred and alternate suppliers, historical yield data for the prototype, and any recent ECOs affecting assembly.
• Present the supply chain ramp plan addressing single-source risk
• Confirm the acceptance criteria for pilot success, including target yield, key quality metrics, and acceptable rework rates.
• Validate mapping to your needs

• Ramp Solution Walkthrough
• Solution Experience Deck
• Ramp Solution Brief

• meeting
• slides
• document

• Engineering validation build production run
• Pilot production line setup and commissioning
• SMT and through-hole PCB assembly
• Electromechanical box build and system integration
• Manufacturing process documentation and control
• Process validation and capability qualification
• Functional test fixture and test software delivery
• In-line functional testing and final test execution
• Root-cause investigation and corrective-action implementation
• Component sourcing and secondary-source establishment
• Engineering change (ECN) implementation on production line
• Traceability, serialization, and lot management
• Initial production packaging, kitting, and shipment
• Production transfer execution and operator training

Engineering validation build production run

• Describe the engineering validation build (EVB) units required by assembly variant and PCB revision.
• Provide the Bill of Materials (BOM) revision, Gerber/ODB++ file version, and assembly drawing revision to be used for the EVB.
• Identify required test coverage for EVB units (in-circuit test ICT, boundary scan, smoke/functional test) and target pass rates. Options: ICT+functional, AOI + functional, Boundary-scan heavy, Functional only, Custom - describe below
• List critical long-lead components and single-source parts that must be included in the EVB procurement plan (part number list or description).
• What acceptance criteria (yield threshold, functional pass rate, and sign-off deliverables) will define EVB success and who will approve the EVB report?

Pilot production line setup and commissioning

• Outline the pilot line footprint, target takt time, and number of stations for the pilot shift. Options: Single-shift pilot, Two-shift pilot, Three-shift pilot, Custom - describe
• Supply the list of tooling and fixtures required for line commissioning, including SMT stencil frames, assembly jigs, and PCB loaders.
• Name required machine capability metrics (SMT placement accuracy in mm, reflow oven zone counts, printer throughput CPM) and current calibration status.
• Itemize facility needs such as ESD-protected workcells, compressed air points, 120/240V power drops, and LAN connectivity for test stations.
• How will operator training and first-article assembly walkthroughs be scheduled and recorded (LMS, training signoffs, competency checklists)? Options: Learning management system (LMS), Paper/printed travelers, Digital tablet work instructions, Hybrid - describe

SMT and through-hole PCB assembly

• Specify PCB file versions, panelization details, stencil aperture spec, and pick-and-place feeder configuration for each PCB assembly.
• Indicate preferred solder paste alloy, flux class, and reference to solder process standard (for example IPC J-STD-001 or customer spec). Options: Sn63/Pb37, SAC305, Low-silver SAC, Custom alloy - describe
• Outline inspection points including automated optical inspection AOI and X-ray positions and target defect thresholds per 1,000 boards. Options: AOI only, AOI + X-ray for BGA, 100% X-ray for selected assemblies, Custom - describe
• State expected reflow thermal profiles, peak ramp rates, and any post-reflow thermal process such as conformal coating or cure cycles.
• How many PCB variants and controlled-revision assemblies will be included in the pilot? Options: 1 variant, 2-5 variants, 6-10 variants, 10+ variants

Electromechanical box build and system integration

• Enumerate mechanical assembly drawings, torque specifications, cable routing diagrams, and connector mating sequences required for box build.
• Specify required cable-harness part numbers, crimp specifications, and continuity or hi-pot test points for each harness assembly.
• Define environmental test requirements (vibration profile, thermal cycling range, ingress protection IP rating) and target pass criteria. Options: Vibration per customer spec, Thermal cycling -40C to +85C, IP54/IP65, None / not required
• Supply required assembly fixtures, alignment gauges, and any PCB-to-mechanical datum drawings with revision references.
• Explain the firmware loading procedure, burn-in steps, and first-article system functional checks that must occur during integration.

Manufacturing process documentation and control

• Which process documents will you supply (work instructions, standard operating procedures SOPs, process flow diagrams PFDs) and what are their revision numbers?
• Specify required acceptance gates and control-plan elements, including critical-to-quality CTQ checkpoints, measurement methods, and defect limits. Options: First-article inspection (FAI), SPC gate, AQL sampling, Custom - describe
• Share examples of change-control forms or engineering change order ECO templates that must integrate with the production ECN workflow.
• Indicate expected revision-control cadence for work instructions when engineering changes occur during ramp (immediate, daily batch, weekly release). Options: Immediate, Daily batch, Weekly release, Other - describe
• Do you require electronic work-instruction delivery (tablet) or printed travelers at the pilot line? Options: Electronic only, Printed travelers only, Hybrid (both)

Process validation and capability qualification

• State target process capability indices (Cp/Cpk) or minimum first-pass-yield targets for solder joints, assembly torque, and test pass rates.
• Which statistical sample plans (AQL level, MIL-STD-105, or 100% inspection) do you expect for process validation runs? Options: AQL sampling, MIL-STD-105, 100% inspection, Custom plan - describe
• Explain how accepted tolerance bands and control charts for key parameters will be defined and who will approve the SPC control limits.
• What evidence (process capability report, SPC charts, test vector logs) will you accept to declare capability qualification complete?
• Enumerate required external standards or certifications to be demonstrated during validation (for example IPC-A-610 class, ISO audit artifacts, customer FAI form).

Functional test fixture and test software delivery

• Detail the functional test vectors, input stimulus, and pass/fail thresholds the test fixture must exercise for system-level verification.
• Include fixture mechanical drawings, connector pinouts, boundary-scan access points, and probe-card requirements for testbed design.
• List the programming interfaces and communication protocols the test software must support (UART, JTAG, Ethernet, USB). Options: UART, JTAG, Ethernet, USB, SPI/I2C, Other - describe
• Describe how test logs and failure-data capture will be performed and the export format required for root-cause analysis (CSV, XML, database export). Options: CSV, JSON, Database export (SQL), Custom - describe
• Assign personnel ownership for test-software maintenance and field-update cadence (patch schedule, emergency fixes).

In-line functional testing and final test execution

• Itemize the in-line test stations, their cycle times, and the maximum acceptable test bottleneck per hour.
• Define final-test coverage including power sequencing, environmental conditions during test, and functional script length.
• Are in-circuit test ICT gates required prior to functional test for PCBA units? Options: Yes - ICT required, No - skip ICT, Optional - only for select SKUs
• Provide expected test throughput targets for pilot shifts and initial weekly volumes (units per hour, per shift).
• Identify the evidence (test logs, fail-mode distribution, retest rates) you will require to accept the final test run.

Root-cause investigation and corrective-action implementation

• Select preferred failure-analysis artifacts for root cause work (X-ray images, cross-section micrographs, thermal imaging, electrical waveforms). Options: X-ray, Cross-section report, Thermal imaging, Electrical waveform capture, Other - describe
• Clarify escalation timing and the problem-review cadence for critical defects found during pilot (immediate containment, daily review, weekly RCA). Options: Immediate containment + daily review, Daily review only, Weekly RCA, Custom - describe
• Name expected corrective-action deliverables (8D report, containment plan, permanent corrective action) and target closure SLAs.
• Who will track change verification on the line (inspection spec updates, SPC entries, test vector changes) after corrective action? Options: Quality engineer, Process engineer, Production supervisor, Shared ownership - describe
• Confirm retention timeframe for corrective-action records and supporting evidence required for quality audits. Options: 1 year, 3 years, 5 years, Customer-specified

Component sourcing and secondary-source establishment

• Submit the current approved vendor list AVL items and their forecasted consumption for the pilot period.
• Flag part numbers that are single-source today and indicate priority for secondary-source qualification. Options: High priority (qualify immediately), Medium priority, Low priority, None
• Call out long-lead or custom components that require footprint or supplier requalification during the ramp and provide lead-time estimates.
• Recommend lead-time buffers and safety-stock levels for the initial production weeks (days or weeks of buffer). Options: 2 weeks, 4 weeks, 6+ weeks, Custom - describe
• Do you require a supplier quality agreement SQA or PPAP-style deliverables for any new component sources? Options: Yes - SQA required, Yes - PPAP-style deliverables required, No

Engineering change (ECN) implementation on production line

• Catalog types of engineering change notices expected during the ramp (BOM updates, hardware reflows, firmware revisions) and typical turnaround.
• Share your preferred ECN approval workflow and required sign-offs for production-impacting changes (e.g., engineering, quality, production).
• Clarify how firmware and test-vector version control will be handled to avoid production mismatches. Options: Tagged releases with checksum, Central firmware server with controlled deploy, Manual load via USB - controlled
• Who will own urgent ECNs that must be implemented within a single shift?
• Document rollback procedures and traceability requirements if an ECN needs to be reverted during the pilot period.

Traceability, serialization, and lot management

• Select the serialization schema (unique identifier UID, GS1, or custom serial) to be used for PCBA and finished-unit traceability. Options: UID, GS1, Custom schema, No serialization required
• Map expected barcode or 2D marking locations, human-readable fields, and label formats for pallets, cartons, and unit labels.
• Recommend lot-control granularity required (per-PCBA lot, per-box, per-shift) and retention policy for trace data. Options: Per-PCBA lot, Per-box, Per-shift, Mixed - describe
• Are serialization and trace-data exports required in a specific format (CSV, JSON, EDI) for downstream systems? Options: CSV, JSON, EDI, No specific format required
• Document systems or middleware that will capture serialized data and where label printing will be hosted (line-level printer, central labeling station).

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Pricing & Payment Schedule (Order Form)
• Quality Agreement
• Tooling, Fixtures & Capital Equipment Agreement
• Supply Chain & Component Sourcing Addendum
• Change Order & Engineering Change Control Agreement
• Governance and Escalation Plan
• Intellectual Property & Confidentiality Addendum
• Termination & Exit Plan

• Go-live Health Check (weeks 1-4)
• First Performance Measurement (weeks 4-10)
• Monthly Operational Review (ongoing until steady-state)
• Quarterly Sustainment and Continuous Improvement Review

• Document supplier long-lead mitigation actions and expected coverage dates for the next quarter.
• Re-confirm acceptance criteria and owners
• Schedule the next performance checkpoint and confirm required data extracts.
• Trend review of key metrics
• Ensure top production and supply issues are progressing to closure and that trends for first-pass yield (%) and engineering change cycle time (days) are improving.
• Validate that supplier mitigations are reducing supply interruptions as measured by supplier on-time delivery (%).
• Keep the open-issue backlog prioritized and time-boxed to prevent regression during ramp.
• Produce a ranked list of current critical defect modes and their target resolution dates.
• Document supplier mitigation actions and expected delivery improvement milestones.
• Record the measured impact of each recent engineering change on yield for the next review.
• Quarterly outcome verification
• Formally confirm whether unit yield stability (%) and DPM are on track to meet Solution Scope steady-state targets or require escalation.
• Agree the prioritized CI projects for the coming quarter and the timeline for each.
• Ensure supplier risk items have time-bound mitigation plans to prevent production disruption.
• Publish the quarterly outcome report with trend charts, variance to Solution Scope targets, and top risks.
• Update the CI backlog with committed start and completion quarters for prioritized items.
• Document immediate containment plans for current critical defects and circulate for comment.
• Confirm that deployment elements required to produce valid outcome data are complete or have named remediation tasks.
• Establish the data feed and reporting cadence for ramp metrics used in the next measurement meeting.
• Agree containment actions for any showstopper issues preventing production or metric collection.
• Publish the deployment validation checklist with status and remediation tasks.
• Enable and verify metric data feeds for ramp yield, supplier deliveries, and change logs ahead of the next meeting.
• Present first-period outcome data vs Solution Scope targets
• Decide whether current ramp yield rate (%) and supplier on-time delivery (%) are on an acceptable trajectory toward Solution Scope targets, or require remediation.
• Document a time-bound corrective action plan for each failed or at-risk metric from the data review.
• Confirm the date and data requirements for the next operational checkpoint.
• Publish the metric report packet showing data sources, calculations, and variance to Solution Scope targets.
• Create and circulate corrective action tickets for identified root causes with target completion dates.
• Continuous improvement backlog review
• Open issue burn-down
• Root cause diagnosis for metric gaps
• Deployment and facility validation
• Supply chain health and mitigations
• Supply risk and long-lead items audit
• Early production run walkthrough
• Agree corrective actions and timelines
• Engineering change impact update
• Open issues and immediate remediation
• Process control and change management summary
• Confirm path to stabilization and next checkpoint
• Confirm measurement sources and cadence
• Short action sync
• Quarter plan and governance adjustments