Box Build & System Integration
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
-
Production Outcome Discovery
Align on desired production outcomes, quality acceptance signals, variant counts, constraints, and stakeholders across manufacturing and supply chain.
Discovery Questions
Start: Your current final assembly picture
- Tell me about your current final assembly process for the product you plan to move to an external integrator.
- How often does your internal line run into capacity constraints that trigger outsourcing?
- Describe the typical complexity of a unit, in count of mechanical and electrical assembly operations and distinct labor steps.
- Who in your organization currently owns final assembly quality decisions and final signoff?
- In your last production ramp, how many product variants did you manage concurrently at peak?
- What single production outcome gap would make you pause moving assembly offsite?
Where assemblies break and why it matters
- If a single recurring workmanship issue were costing you field returns or rework, which issue would it be and how much does it cost monthly?
- Give an example of the last five defects found in your final audit and which operation they traced to.
- How often do configuration errors, such as wrong firmware or incorrect wiring, occur during final integration?
- Who currently performs cross-variant configuration control and gate releases on your line?
- Estimate the fully burdened cost per unit of a mislabeled or misconfigured shipment, including returns and field fixes.
- If an integrator failed to meet your torque, routing, or label placement tolerances on the pilot, how quickly would you escalate to halt production?
Variant control and BOM risks you cannot accept
- How would an uncontrolled BOM revision during pilot undermine your ability to ship correct variants, and where does that risk live today?
- Describe the process you use to lock BOM revisions and firmware-to-variant mapping before each build, and where that process breaks down.
- How many distinct SKUs or variants share the same enclosure but change internal wiring or firmware?
- Which roles authorize BOM changes and what is the typical approval lead time?
- When does your team require serialized tracking versus batch-level control for variants?
- List the top three supplier-managed components whose revision errors have caused the most line stoppages.
Pilot build: the test that decides production transfer
- Would you treat a pilot that misses target measurements on more than five critical operations as a disqualifier, or would you iterate?
- Tell me the specific acceptance checks you will run on pilot units, including dimensional, routing, torque, label placement, and functional tests.
- How many sample reference units will you provide and do you expect them returned after audit?
- Which failure modes would require a full root cause analysis and a written corrective action before a second pilot?
- When do you expect to sign off on pilot results if all acceptance gates pass?
Supply and inbound chain that must not break
- How long of a buffer does your supply chain require to absorb a 20 percent inbound delay before the integration line stops?
- Identify the inbound part types that are single-source and would immediately block production if delayed.
- Do you have long-term agreements or blanket purchase orders with your harness and enclosure suppliers that an integrator would need to honor?
- Assign the role or function that will own supplier change notifications and nonconformance claims during the pilot.
- What single inbound lead time or supplier credential that you do not have today would prevent meeting your pilot schedule?
Readiness gates and must-have constraints
- Identify the one readiness item missing today that would block a pilot starting within 4 weeks.
- Do you have a named owner or dedicated headcount to coordinate daily with the integrator during the pilot?
- Estimate the minimum uptime or capacity the line must achieve during pilot to convince you of production viability.
- List any regulatory or audit approvals that must be completed before production transfer.
- Can your team provide serialized device tracing and controlled manufacturing records within 8 weeks if requested?
Alternatives on the table
- Under which conditions would you keep final assembly in-house instead of engaging an external integrator?
- Name the alternative supplier options you are evaluating, for example incumbent outside manufacturers, other contract manufacturers, or expanding internal lines.
- Specify the maximum acceptable increase in unit cost for moving to an external integrator before you reject the change.
- Has anyone inside procurement or operations proposed solving capacity or quality gaps by hiring and retraining instead of outsourcing?
- Confirm the job title or function that can approve a production transfer if the pilot meets your acceptance gates.
Decision triggers, timing, and next steps
- Assuming pilot success, what is the earliest contractual milestone you would require to convert to production?
- Specify the payment and commercial terms that would accelerate award.
- Provide target monthly volumes for month one, month three, and month six after approval.
- Detail any required insurance, audit, or contractual clauses that could delay award beyond eight weeks.
- Confirm the single metric that, if achieved by the pilot, would allow your procurement function to approve a production award immediately.
- Select your preferred pilot reporting and escalation cadence.
-
Solution Experience
Walk through how full box-build and system integration will deliver the buyer's quality, configuration control, and fulfillment needs using their real scenarios.
Solution Experience
- Solution Experience — Box-Build & Integration Walkthrough
- Confirm the current state and its cost
- You confirm the restated current state and its operational cost to quality, delivery, and customer risk.
- Deliver a runbook that maps the buyer's reference unit checklist to the seller's inspection steps and propose a pilot audit plan within five business days.
- You confirm the demonstrated end-to-end workflow eliminates the rework and wrong-variant shipment risk you described.
- Walk through your pilot scenario end-to-end
- Provide one assembled reference unit, the BOM with variant matrix, and your written pilot acceptance criteria before the pilot kick-off.
- Provide a sample pilot quality audit report template and proposed acceptance gate scoring before the next meeting.
- You agree on concrete pilot acceptance thresholds and the specific evidence required to convert pilot results into a production commitment.
- Demonstrate configuration control and variant mapping
- Live quality audit vs your reference unit
- You confirm the next seller deliverable and the next buyer inputs needed before the pilot start.
- Confirm pilot quantity, availability of any test fixtures, and a target pilot start date.
- Validate acceptance criteria and decision gates
- Agree immediate next evidence and timeline
- Solution Experience — Box-Build & Integration Walkthrough
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define scope boundaries, BOM and supplier responsibilities, variant configuration controls, pilot quantity, test plans, and acceptance criteria.
Scope Configuration
- Incoming goods inspection and production kitting
- PCB installation and connector mating
- Wire-harness termination, routing, and securing
- Sub-assembly mechanical assembly and enclosure installation
- Controlled torque fastening and fastening verification
- Conformal coating application and cure
- Potting and encapsulation
- Firmware programming, configuration, and verification
- Functional test, custom fixture execution, and burn-in
- Variant build execution with BOM configuration control
- Labeling, serialization, and UID assignment
- Traceability record generation and batch documentation
- Final protective packaging and kit assembly for shipment
- Direct fulfillment and end-customer shipping
Scope Questions
Incoming goods inspection and production kitting
- Which inbound part types must receive 100% inspection on receipt (for example wire-harnesses, power supplies, custom assemblies)?
- How many supplier lots per SKU will you accept before requiring re-inspection or quarantine?
- Specify the lot acceptance criteria to apply at receiving for cable harnesses and PCBA lots (for example AQL, zero critical defects per 50 samples, visual-only).
- Provide the inspection standard to apply on incoming electronics and harnesses (for example IPC-A-610 Class 2, IPC-A-610 Class 3, internal visual standard).
- List the mandatory kit contents per build unit that must travel to the line (BOM revision, firmware image filename, label artwork ID, connector kit), and indicate file or doc IDs.
- Who is your listed quality contact for inbound nonconformance and what document do they require for an RMA (for example supplier NCR form or vendor corrective action request)?
PCB installation and connector mating
- Which PCB assembly SKUs and reference designators are included in the top-level assembly for the pilot run (list PCB SKU or drawing number)?
- Which specific connectors require controlled torque or crimp control during mating (for example J1 power input, J2 ribbon connector)?
- Specify connector orientation and cable strain-relief routing for the primary harness per your assembly drawing number or ECO.
- How many PCB touch points require ESD-protected handling and what ESD standard must be enforced (for example ANSI/ESD S20.20)?
- Which fastener types are captive on the PCB-to-enclosure interface versus supplied loose (for example captive standoffs, M2 screws)?
- Provide the PCB revision number and ECO ID that must be used for pilot units.
Wire-harness termination, routing, and securing
- List each wire-harness SKU and map it to the product variants that will use it for the pilot (for example harness A -> variants 1,2).
- Which termination standard and tooling must be used for crimped contacts (for example IPC/WHMA-A-620, specified crimp gauge)?
- Specify cable routing restraints and minimum bend radius constraints for harness runs through the enclosure per drawing callouts.
- How many harnesses per unit require 100% continuity or in-circuit test after termination before kitting to the line?
- Identify the inspection checklist or harness routing photos to be used as the quality reference (document ID or filename).
- Who is authorized to sign off on harness readiness for assembly and what sign-off artifact do they use?
Sub-assembly mechanical assembly and enclosure installation
- Which sub-assemblies will arrive pre-assembled and which will be built on the integration line (list sub-assembly IDs)?
- Specify the enclosure finish acceptance criteria and cosmetic defect thresholds (for example maximum 1 scratch < 1 cm, no dents) and reference the drawing or standard.
- Provide the hardware torque specs and fastening sequence for enclosure installation in Nm or in-lb and reference the assembly drawing number.
- Are any safety interlocks or lockout/tagout (LOTO) verifications required after enclosure assembly?
- Which alignment or fit tolerances must be met on assembled enclosures (for example panel-gap < 0.5 mm)?
- How many variants share the same enclosure and which front-panel cutouts differ by variant (list variant IDs and differences)?
Controlled torque fastening and fastening verification
- Which fasteners require calibrated torque drivers and what are the required torque values per fastener (provide fastener ID and torque in Nm or in-lb)?
- Specify the torque verification sampling plan for pilot units (for example 100% torque capture, 1 in 5 sampling, SPC-based plan).
- Indicate how torque evidence should be recorded and delivered (for example digital export from tool, barcode tie to serial UID, torque stickers).
- Who provides calibration certificates for torque tools and what interval is required for re-calibration (months)?
- Which threaded joints require threadlocker, torque-plus-turn, or locking washer per drawing callouts?
Conformal coating application and cure
- Which assemblies require conformal coating and what coating type or standard applies (for example acrylic, silicone, IPC-CC-830)?
- Specify masking boundaries and reference masking drawings or photos to preserve connectors and test points.
- Provide the required cure profile (time and temperature) and the document used to validate the cure for coated assemblies.
- How should coating thickness be measured and what acceptance threshold in microns is required?
- Are touch-up or rework allowances permitted after coating and who must approve the rework (role or document)?
- Provide the Material Safety Data Sheet (MSDS) and batch traceability requirements for the coating compound (document ID or upload path).
Potting and encapsulation
- Which assemblies require potting and what potting compound and hardener ratio or product ID must be used?
- Specify allowable pot volume tolerance per unit and acceptable void percentage after cure (for example volume ±5%, voids <2%).
- Which fixtures are required to hold parts during potting and will you supply those fixtures or expect them to be built?
- Describe the cure verification method required for potting (for example Shore hardness test, visual cross-sectioning) and acceptance thresholds.
- Who is responsible for substrate cleaning and surface prep before potting and what evidence of prep is required?
Firmware programming, configuration, and verification
- Provide firmware image filenames and SHA-256 hashes for each variant image to be provisioned in the pilot.
- Which programming interface must be used for flashing (for example JTAG, SWD, UART bootloader) and provide the pinout or connector drawing.
- Who is the named handoff owner for firmware images and what secure transfer method will you use (for example SFTP, signed artifact)?
- Which per-unit configuration variables must be written during programming (for example MAC address, serial UID, calibration table) and in what CSV format do you supply them?
- What acceptance criteria define successful firmware provisioning for pilot units (for example boots to UI, reports version string X.Y.Z, network join within 30 seconds)?
Functional test, custom fixture execution, and burn-in
- Provide the functional test procedure document name and the step IDs used for reference-unit comparison during the pilot.
- Which measurements and signals must the custom test fixture capture (for example power rail voltages, UART response, RF power out) and in what numeric tolerances?
- What automated failure modes on the fixture should trigger engineering hold for investigation (for example UART timeout, torque out-of-spec, missing UID)?
- What pilot-run acceptance rate must be met against your internally assembled reference units (for example 25/25, 24/25), and which defects are immediate rejects?
- Which burn-in profile should be executed for pilot units (hours, temperature, and test load) and reference the burn-in spec document ID.
- How should intermittent or non-deterministic failures be reported and what log format is required for failure analysis?
Variant build execution with BOM configuration control
- Provide the Bill of Materials (BOM) revision mapping for each product variant included in the pilot (list BOM revision or ECO ID per variant).
- Which BOM items are controlled parts that must not be substituted (list part numbers or designators)?
- Which field in your PLM/ERP denotes the BOM freeze (for example revision number, ECO ID) and what value indicates freeze to use in pilot kitting?
- Who is the authorized change approver for BOM revisions and provide the contact or role that will sign off change orders during pilot?
- How should part substitutions be documented in the kit (for example alternate part note on packing slip, documented ECO) and do you permit pre-approved alternates?
- Describe the software or CSV format you will provide for variant pick logic (for example BOM line to SKU mapping file format).
Labeling, serialization, and UID assignment
- Which label templates must be printed on each unit (for example regulatory label, serial number label, packing label) and provide artwork IDs or file names.
- What serialization scheme do you require for UID assignment (for example numeric length, alphanumeric with check digit, GS1 serialized trade item number)?
- Which printer technology and label materials are acceptable for your labels (for example thermal transfer on polyester, tamper-evident material)?
-
Pilot Build Evaluation
Run a defined pilot build (e.g., 25 units) and perform a quality audit against the buyer's reference units to validate workmanship and configuration control.
- stakeholders
- success_criteria
- gaps
- current_state
- decision_readiness
- desired_state
- current_state
- success_criteria
- desired_state
- gaps
- stakeholders
- decision_readiness
- current_state
- stakeholders
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Mutual Commit
Finalize commercial and legal terms, acceptance gates, SLAs for workmanship, configuration-management obligations, and pilot-to-production conversion triggers.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW) — Pilot and Production Onramp
- Service Level Agreement (SLA) — Workmanship & Operational SLAs
- Pilot Acceptance Protocol and Certificate
- Production Order / Order Confirmation
- Configuration Management & Change Control Agreement
- Workmanship Warranty and Remedies
- Firmware/Image Handoff and Escrow Agreement
- Change Order Agreement
- Regulatory Compliance Addendum (conditional)
-
Production Launch
Lock readiness facts and configuration values before execution and ramp into production.
-
Pre-Deployment Readiness
Capture concrete readiness facts — inbound supplier lead times, firmware/image handoffs, test fixture availability, line capacity, schedules, and named owners — before execution begins.
Pre-Deployment Questions
Environment and site access
- Production site(s) for the pilot and ramp (name each site and indicate which is primary) — this tells us where to stage crews and fixtures
- Is site access for the seller's execution team (badging, visitor registration, vendor insurance) fully arranged?
- If site access is not fully arranged, who owns the action and what is the expected ready date? (owner name, role, expected date)
Materials and inbound supply
- Are all BOM suppliers confirmed and scheduled to deliver pilot quantities on time?
- Have critical long-lead items been identified and their inbound lead times confirmed for the pilot?
- If any supplier or part is pending, list the part reference and the named owner responsible for resolving it (owner name and contact)
Firmware, test, and configuration artifacts
- Are firmware/images and the mapping of firmware-to-variant finalized and handed off to the seller?
- Are functional test procedures, pass/fail criteria, and test fixture availability confirmed for the pilot?
- If fixtures or test procedures are pending, who owns delivery (name and role) and what is the expected ready date?
People, capacity, and schedule
- Named owners: provide the primary seller execution owner and the buyer's pilot acceptance owner (name, role, contact) — we use these to route approvals and escalations
- Is pilot line capacity, shift plan, and target daily throughput confirmed for the pilot quantity?
- Are there schedule constraints, blackout windows, regulatory audits, or shipment restrictions during the pilot window? If yes, list the constraint and the owner who manages it.
-
Configuration Details
Lock exact production configuration values: BOM revisions, torque and routing specs, label templates, firmware-to-variant mapping, test sequences, and packing instructions.
Configuration Details
BOM & Revision Control
- Enter the exact production BOM revision identifier the assembly line will consume (format example: BOM-2026-04-R2). Default: BOM-0001 — change only if you are locking a specific revision.
- Enter the authoritative BOM file location (format: URL, s3 path, or network path — e.g., https://... or s3://bucket/path/bom.xlsx or \\share\bom.xlsx).
- Who is the BOM change approver (enter role/title that will approve any revision after freeze, e.g., 'Buyer PLM Owner' or 'Seller Manufacturing Engineer')?
Mechanical & Assembly Specifications
- Select torque specification units used on production traveler (Default: Nm).
- Enter the numeric torque value for the primary chassis fasteners (numeric only; do not include unit — the unit above will be applied; example: 5.2).
- Provide the cable routing reference drawing file location (format: URL or file path to PDF/DWG used by assemblers).
Labeling & Identification
- Enter the exact serial-number format string the line must apply (use tokens {YYYY},{MM},{SEQ:n}; example default: PROD-{YYYY}-{SEQ:6}). Default: PROD-{YYYY}-{SEQ:6}.
- Provide the label template/artwork file location (format: URL or file path to PDF/AI file the label applicator will use).
- Provide the packing instruction file location (format: URL or file path to the packing spec used to pack units for shipment).
Firmware & Variant Mapping
- Provide the firmware manifest location (format: URL or file path to manifest JSON/CSV listing image name, version, and checksum). Do not paste image binaries or secrets here.
- Select the firmware-to-variant mapping method the line will use (Default: Variant ID lookup in manifest).
- Who is the role responsible for firmware approval/sign‑off (enter role/title; e.g., 'Buyer Firmware Owner' or 'Seller Build Manager')?
Test Sequences & Acceptance
- Enter the exact production test sequence identifier or file name the test fixture will call (format example: TESTSEQ-V1 or /path/to/testseq.json).
- Enter the functional pass threshold percentage the build must meet at acceptance (numeric percent, Default: 98). Example: 98
Packing & Fulfillment
- Enter units per shipping carton (numeric; the pack station will pack to this exact quantity per carton). Default: 10.
Configuration Freeze & Owners
- Enter the production configuration freeze date (format YYYY-MM-DD; this is the date after which the values above are locked; Default: next business day).
- Enter the single point of contact role/title who owns this configuration sheet (enter role/title only; example: 'Seller Production Manager').
-
Production Ramp
Execute the assembly, test, labeling, and fulfillment sequence with clear owners, sequencing, quality checkpoints, and escalation paths.
-
-
Success
Confirm production acceptance metrics, monitor yield and defect trends, and maintain a shared channel for issues, corrective actions, and enhancement requests.
Success Reviews
- Go-live health check (weeks 1-4)
- First measurement review (weeks 4-10)
- Production acceptance gate (around day 90)
- Quarterly operational review (ongoing)
Issues & Enhancements
- Escalate any corrective actions overdue by more than the agreed threshold and document next steps for resolution.
- Restate acceptance criteria and evidence required
- Produce a documented pass, conditional pass with remediation plan, or fail per acceptance criterion recorded in Solution Scope.
- Capture the named signatory or owner who will record final acceptance once remediation is complete.
- Confirm the incumbent wind-down status or formally document retention as read-only with data archiving and fallback closure.
- Publish the acceptance decision record, including pass/fail per criterion and any remediation timeline, with the named signatory noted.
- If conditional, open remediation tickets with verification evidence requirements and target close dates.
- Complete the incumbent decommissioning checklist or document retention terms and archive transferred data.
- Trend review for defects and yield
- Confirm whether defects per unit and on-time fulfillment rate are on track relative to Solution Scope targets or need further action.
- Ensure all high-priority corrective actions have owners, verification evidence, and target close dates.
- Keep a single shared channel for issues, corrective actions, and enhancement requests updated with current status.
- Publish the quarterly trend packet with unit-level defect breakdown and corrective-action status for shared reference.
- Update the shared issue channel with new enhancement requests and assign target delivery windows.
- Reconfirm acceptance criteria and owners
- All high-risk deployment blockers are documented with owners and target resolution dates.
- Production tooling, test fixtures, and firmware handoffs are validated as ready or flagged with corrective actions.
- Acceptance criteria recorded in Solution Scope are confirmed and owners acknowledged for the measurement phase.
- Publish the confirmed list of acceptance criteria and named owners that live in Solution Scope.
- Create a short remediation ticket for each high-priority blocker with a target resolution date.
- Verify test fixture calibration and firmware image availability before the next production run.
- Present first-run data against targets
- Establish whether first-pass yield and functional test pass rate are improving toward the Solution Scope targets and document deviations.
- Assign corrective actions with verification steps and dates that close gaps before the acceptance gate.
- Confirm timeline to the Production Acceptance Gate meeting and required evidence package.
- Deliver a data package of unit-level test logs, defect categorization, and sample photos for acceptance gate review.
- Open containment actions for any wrong-variant shipments and implement immediate checks at packing.
- Schedule verification builds or additional audits if remediation requires repeat measurement.
- Deployment and tooling validation
- Configuration control and wrong-variant incidents
- Root-cause analysis for metric gaps
- Present outcome data per criterion
- Corrective actions and verification plan
- Document pass or conditional pass per criterion
- Open issues and corrective action burn-down
- Early workmanship and process adherence check
- Risk review for configuration control and logistics
- Inbound supply and schedule check
- Wind-down of incumbent assembly (one-time checkpoint)
- Enhancement requests and operational changes
- Agree remediation plan and named signatory for acceptance
- Blockers and immediate remediation actions