A quick inventory snapshot

• Tell me which manufacturing site or production line this BOM applies to and how many unique part numbers it contains.
• How many of those part numbers are active production parts, and how many are long term spares? Options: Mostly active (<10% spares), Balanced (~10–30% spares), High spares (>30%), Unknown / not tracked
• Walk me through a recent week where a component shortage forced a production change, emergency buy, or schedule slip.
• On average, how many unique component purchase orders do you place per month for this line? Options: <50, 50–200, 200–500, >500

Where shortages hurt most

• Which single part family, or specific part number, caused a line stop, emergency buy, or design workaround in the last 12 months?
• How often do allocation events for that family disrupt your planned builds? Options: Weekly, Monthly, Quarterly, Less than quarterly, Irregular / unpredictable
• Who on your team is first notified when an allocation or shortage threatens a build, and how do they communicate the risk? Options: Procurement, Materials planning, Production supervisor, Quality, Cross functional alert (email/ERP), Other
• What downstream operations or customer commitments break when that family becomes unavailable?
• If that family stayed supplied at forecasted levels, what immediate operational decision would you make next quarter?

Supply lead times and hidden wait costs

• How many of your top 50 parts regularly exceed their published lead time by more than 50 percent? Options: None, 1–5 parts, 6–15 parts, 16–30 parts, More than 30
• Which semiconductor or long lead category creates the single biggest schedule risk for your production? Options: High‑end microcontrollers/MCUs, FPGAs/SoCs, Power management ICs, Custom discretes, Passive components, Other
• Where do you absorb extra cost when lead times spike, expedited freight, overtime, or schedule slips? Options: Expedited freight, Overtime labor, Subcontract assembly, Customer penalties, Reserve inventory, Other
• What is the longest lead time you must plan around today, in weeks? Options: <4 weeks, 4–12 weeks, 13–26 weeks, 27–52 weeks, >52 weeks
• What single lead time failure would make you stop onboarding a new supplier for this line?

Counterfeit and quality, not excuses

• When was the last time a suspect or failed component forced rework, scrap, or a line hold? Options: Within 30 days, Last 3 months, Last 12 months, More than 12 months, Never / unknown
• Which incoming inspections do you run on that product family, and which are performed by a third party? Options: Incoming visual/lot trace, Electrical test, X ray / XRF, Decapsulation / lab test, No inspections, Third party testing
• Do your acceptance criteria require vendor certification to AS6081 or AS6171, third party testing, or only internal batch documentation? Options: AS6081/AS6171 required, Third party test report required, Internal batch paperwork sufficient, Varies by part family, Unknown
• What processes or inspection failures would cause you to reject a shipment on first article inspection?
• What single quality or certification gap would make you rule a supplier out entirely?

Decision map, approvals, and who moves the needle

• Who signs final approval for new vendors, purchasing thresholds, and engineering part exceptions in your organization? Options: Procurement director, VP Supply Chain, Head of Engineering, Quality director, Cross functional committee, Other
• Describe the typical approval timeline for an emergency purchase versus a planned supplier addition. Options: Hours to 24 hours, 1–3 days, 1–2 weeks, 3–6 weeks, Longer / varies
• How quickly can procurement, engineering, and quality sign off on a lifecycle change or part substitution during an allocation event? Options: Same day, 1–3 days, One week, 2–4 weeks, Longer
• Which organizational blocker would stop a supplier pilot from moving to production within 90 days? Options: No budget approval, Missing quality certs, Integration unavailable, Stakeholder conflict, Other

The other options on your shortlist

• If you stayed with your current supplier or chose to manage parts internally, what would have to be true for you to stick with that choice?
• Which alternatives are you actively evaluating now? Options: Incumbent distributor / franchised partner, Direct factory purchases, Broker or open market, Bring kitting and testing in house, Multiple niche distributors, Other
• Has anyone on your team proposed solving this without an outside vendor, for example by expanding buyer‑managed inventory or building in-house kitting? Options: Yes, actively proposing internal solution, Yes, discussed but no plan, No, not proposed, Unsure
• What pricing, lead time, or quality evidence would make you switch this quarter rather than later?
• Which single proof point from a pilot would make your procurement team change vendor within 30 days? Options: Sustained on time fill >95%, Zero counterfeit incidents, Measured lower landed cost, Smooth EDI integration, Other

Practical gates we must clear

• Which integrations or systems must be connected before a launch, your ERP, EDI/API, plant receiving, or quality systems? Options: ERP (inventory/P.O.), EDI/API order exchange, Plant receiving and scheduling, Quality management system, None required, Other
• Do you have EDI or API endpoints available today, and who owns them on your side? Options: Yes, fully available and owned by IT, Yes, available but owned by supply chain, Partially available, No, need to be built, Unknown
• Is your BOM data consolidated and production cleaned in a single file or system we can consume, or will it require mapping and cleanup? Options: Clean, single source file, Single system but needs mapping, Multiple files, needs cleanup, Not consolidated, Unknown
• Name the teams that will own integration, test, and go decisions on your side. Options: IT, Supply chain / procurement, Quality, Production / operations, Third party integrator, Other
• Which integration dependency would prevent go‑live within 60 days if it was not resolved? Options: ERP order exchange, EDI/API credentials, Plant receiving window availability, Quality acceptance certs, None critical
• What single integration or compliance gating item would stop deployment completely?

What success actually looks like

• If a pilot proves a sustained 98 percent on time fill and zero counterfeit incidents, what must happen that week to finalize terms?
• Which KPIs will you require for acceptance and what are your target thresholds? Options: On time fill %, Quality rejects / ppm, Lead time adherence, Allocation response time, Inventory days on hand, Total landed cost
• Name the roles required to sign off on those KPIs and accept the supplier into production. Options: Procurement lead, Quality engineer, Production manager, Engineering approver, Finance / legal, Other
• What contractual or SLA clause would be a deal breaker for you in a standard distributor agreement?
• If the pilot meets the targets, what internal step would make you ready to sign within 14 days?

Next practical steps and timeline

• What is the earliest date you could commit internal resources to run a pilot for 60 days? Options: Immediately, Within 2 weeks, Within 30 days, Within 60 days, Later than 60 days
• Which internal deadline or customer commitment creates the hard project timeline for the next 90 days? Options: Customer delivery date, Audit or qualification window, Budget quarter close, New product launch, No hard deadline
• Identify the role or procurement threshold required to approve a pilot purchase immediately. Options: Procurement manager with approval under threshold, Director level approval, VP level approval, Cross functional committee, Other
• What open questions or risks do you want resolved before we build a pilot statement of work?

• Solution Experience: BOM Risk and Fulfillment Scenarios

• Confirm the current state and its cost
• You confirm the demonstrated BOM workflow eliminates the last-minute sourcing and counterfeit exposures you reported.
• Deliver a scoped proof-of-concept run on the provided BOM lines, including sample kitting and visibility reports, by the agreed follow-up date.
• You agree on measurable acceptance criteria for availability, lead time, and counterfeit mitigation that will be used to validate pilots and go-live.
• Walk a representative BOM scenario end-to-end
• Provide three representative BOM line items, including lifecycle status, current suppliers, and recent allocation incidents for the proof run.
• You identify remaining evidence required to finalize commercial terms and a go-live schedule.
• Demonstrate lead-time and allocation handling
• Share target production windows and acceptable lead-time thresholds for the identified lines.
• Agree measurable acceptance criteria
• Prepare a draft acceptance criteria matrix mapping availability thresholds, counterfeit screening steps, and SLA targets for review.
• Validate the future state

• Solution Experience: BOM Risk and Fulfillment Scenarios
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Device Programming and Firmware Provisioning
• Tape-and-Reel Conversion and Packaging
• Custom Labeling and Part Marking
• MSL Packaging, Vacuum Sealing, and Baking
• Component Electrical Testing and Functional Screening
• Counterfeit Screening and AS6081 Authentication
• Production Kitting and Line-Ready Kit Assembly
• Bonded Inventory Storage and Release Management
• Vendor-Managed Inventory Replenishment
• Allocation Management and Priority Order Release
• BOM Consolidation and Single-PO Fulfillment
• BOM Quoting and Consolidated Pricing Delivery
• Real-Time Inventory Portal Access and Reporting
• Automated Reorder Execution and Replenishment

Device Programming and Firmware Provisioning

• Do you require programming of devices by part number (use BOM line-item references)? Options: Yes, No
• Which device families or microcontroller (MCU) part-number prefixes need on-site firmware flashing?
• How many unique firmware images map to the production BOM (count distinct image-file names or image IDs)? Options: 1-5, 6-25, 26-100, 100+
• Provide the required validation checksum method for programmed devices (for example CRC32, SHA256) and the acceptance threshold.
• Who will provide golden firmware images and release notes for each BOM line item (role or document type)?
• Specify the programming interface and fixtures required per part number (e.g., SWD header, JTAG pogo adapter, ISP pads).

Tape-and-Reel Conversion and Packaging

• Which part numbers from your BOM require tape-and-reel conversion (include manufacturer part numbers and package codes)?
• Indicate preferred reel specifications per part-number family (reel diameter, reel width, carrier pitch) when converting to tape and reel.
• How should leads and orientation be recorded on the pick map for SMT feeders (e.g., pin 1 orientation, short-side lead)?
• Are there JEDEC or customer-specific packing instructions to follow for moisture sensitive parts during taping? Options: Yes, No
• Which lot traceability fields must be affixed to each reel label (for example lot number, date code, PO number)?
• Do you require anti-static or ESD-certified carrier tape and packaging for specific components? Options: Yes, No

Custom Labeling and Part Marking

• Which BOM items require custom labels or barcode formats (specify part numbers and desired barcode symbology)?
• Specify the label data fields required per kit or reel (for example part number, manufacturer, lot, date code, work order).
• Do you have label artwork templates or GS1 requirements to follow for serialized labeling? Options: Yes, No
• Identify any on-part marking standards to preserve (for example manufacturer laser mark expected on IC lids) versus custom overprint needs.
• When scanning labels at receiving, which barcode fields must populate your ERP or MES fields (list ERP field names if known)?
• Are there regulatory or customer audits that require label retention or a label-printing audit trail? Options: Yes, No

MSL Packaging, Vacuum Sealing, and Baking

• Which BOM parts carry a moisture sensitivity level (MSL) rating and what MSL levels are documented on the BOM lines?
• Specify required dry-pack materials and desiccant counts per JEDEC or your internal standard for each MSL level.
• How often should we provide humidity indicator cards (HIC) and what HIC states are acceptable at handoff? Options: HIC shows <5% RH, HIC shows 5-10% RH, Custom
• When baked parts are required, provide the bake profile per part family (temperature, time, rehydration allowance) that your production accepts.
• Do you require documentation of vacuum-seal pack serial numbers and seal integrity photos for each shipment? Options: Yes, No
• Is on-demand baking at the seller's site acceptable before shipment, or must baking occur at your receiving plant (select one)? Options: Seller-site baking acceptable, Buyer-site baking required, Case-by-case

Component Electrical Testing and Functional Screening

• Which part numbers require incoming sample electrical testing versus lot acceptance testing (reference BOM line items)?
• Specify the test vectors or functional test steps required per device family (for example power-up current, ID code read, functional handshake).
• How many units per lot must be electrically tested to satisfy your acceptance (for example 1%, fixed N, or sample plan reference)? Options: Fixed N, Percentage, AQL plan
• Do you require test reports with per-lot pass/fail data and individual serial or lot traceability back to the BOM line? Options: Yes, No
• Will you accept fixtures and test programs supplied by you, or should we develop and qualify tester programs? Options: You supply fixtures, We develop tester programs, Hybrid
• Are environmental stress screening or burn-in procedures required for any part numbers (specify temperature and duration)? Options: Yes, No

Counterfeit Screening and AS6081 Authentication

• Which BOM part numbers must be covered by AS6081-compliant authentication and what documentation do you require with each lot (for example COA, traceability to franchised lot)?
• Describe the minimum evidence you accept for authenticity per part family (for example manufacturer pedigree, lot trace to authorized shipper, X-ray image).
• How should suspect parts be handled at receiving — hold for inspection, reject on arrival, or return to shipper — for defined counterfeit-risk SKUs? Options: Hold for inspection, Reject on arrival, Return to shipper
• Which inspection methods are mandatory for high-risk parts (for example decapsulation, X-ray, scanning electron microscopy, marking verification)?
• What evidence will validate AS6081 authentication for each lot at handoff (for example manufacturer pedigree plus lab report)?
• Are there any regulatory or customer-specific counterfeit-reporting templates we must populate when an issue is found? Options: Yes, No

Production Kitting and Line-Ready Kit Assembly

• Which assemblies or work orders from your BOM require single-line kits versus multi-level kits (list assembly references)?
• Specify kit contents rules — per-assembly part counts, allowable substitutions, and maximum missing-tolerance per kit.
• How should pick-face packaging be organized for the line (for example bag-and-tag, foam trays, feeder-ready reels)?
• What acceptance checklist items must be completed for a kit to be considered line-ready (for example part counts verified, labels applied, MSL status recorded)?
• Who is authorized to sign kit acceptance at handoff and what documentation must accompany the kit (for example packing list, lot traceability)?
• What is the maximum acceptable kit build lead time from order confirmation to ship for scheduled production runs? Options: <24 hours, 24-72 hours, >72 hours

Bonded Inventory Storage and Release Management

• Which SKUs or part families should be held in bonded storage under duty-deferral or customs control (list tariff-line or part references)?
• Specify the release triggers for bonded inventory (for example release on PO, release on ASN, release on customs clearance). Options: PO release, ASN release, Customs clearance, Other
• How must bonded releases be documented to meet your customs and audit needs (for example release certificate, customs MRN, signed release form)?
• What acceptance criteria will confirm a bonded-lot is cleared for release to production (for example customs MRN plus lot trace and COA)?
• Who within your organization will be the customs contact and what paperwork formats do they expect (electronic PDF, XML, or paper originals)? Options: Electronic PDF, XML, Paper originals, Other
• Do you require inventory valuation or duty-reporting on a per-lot basis while in bonded storage? Options: Yes, No

Vendor-Managed Inventory Replenishment

• Which BOM part numbers are candidates for vendor-managed inventory (VMI) and what min/max stocking levels do you expect per SKU?
• How should consumption be reported back to us (for example daily usage CSV, weekly ASN, API feed) to drive replenishment? Options: Daily CSV, Weekly ASN, API feed, Other
• Describe your expected reorder lead-time policy for VMI SKUs (for example reorder at forecasted 14-day coverage).
• Who owns safety stock calculation and what service level target do you require for VMI items (for example 95% fill rate)?
• Will you provide cycle-count results for VMI locations or do you want us to perform cycle counts and report discrepancies? Options: You provide cycle counts, We perform cycle counts, Hybrid
• Indicate the integration method for inventory updates (select preferred): Options: API endpoint for inventory, EDI 846, Portal upload, Manual reporting

Allocation Management and Priority Order Release

• Which BOM lines are subject to allocation risk and how do you prioritize orders across programs (for example priority by product line, by PO type)?
• Describe the priority-release rules you want applied during allocation events (for example critical production orders first, allocate to safety stock levels).
• How should we report allocation status to you (for example daily allocation ledger, weekly executive summary, API alerts)? Options: Daily ledger, Weekly summary, API alerts, Other
• Who is the authorized approver for allocation exceptions and what evidence must they provide to change allocation priority?
• Do you require automatic substitution rules for allocated parts (for example last-time-buy alternatives or approved cross-references)? Options: Yes, No
• Will allocation decisions feed back into your MRP or ERP system and by which interface (for example API, EDI, portal)? Options: API, EDI, Portal upload, Manual

• Purchase Agreement
• Order Confirmation
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Quality & Counterfeit Mitigation Addendum
• Allocation & Lead‑Time Management Addendum
• Inventory Program Agreement
• Pricing & Payment Terms Schedule
• Governance & Cadence Plan
• Integration & Data Exchange Addendum
• Warranty, Returns & RMA Policy
• Confidentiality & Data Security Agreement

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate and Formal Acceptance (around day 90)
• Quarterly Operational Review (ongoing)

• Produce a short quarterly metrics summary and distribute to stakeholders for asynchronous review.
• Restate acceptance criteria and numeric targets
• Produce a documented pass or fail for each acceptance criterion recorded in Solution Scope.
• Capture the formal acceptance decision with a named signatory or the buyer owner as required by the deal type.
• Agree remediation items and timelines for any failed or conditional criteria.
• Publish the acceptance record showing pass/fail per criterion and include the signatory statement.
• Add any remediation tasks to the shared backlog with owners and completion dates.
• If accepted, transition ownership to the ongoing operational cadence and share the quarterly review schedule.
• Metric trends and variance review
• Ensure inventory allocation accuracy and integration uptime remain within acceptable ranges compared to Solution Scope targets.
• Ensure all high-severity quality or allocation incidents have remediation owners and closure dates.
• Agree the prioritized backlog for the coming quarter and the expected delivery windows for top items.
• Update the shared backlog with priorities and expected completion dates for the quarter.
• Create incident postmortems for any high-severity allocation or quality events and assign remediation tasks.
• Re-confirm success criteria and owners
• Confirm deployment completed and integrations are functionally live.
• Capture all critical issues with owners and target resolution dates for the next 30 days.
• Confirm who will own tracking of each acceptance criterion recorded in Solution Scope.
• Document and circulate the 30-day remediation plan with owners and dates.
• Create tickets for all critical defects and link them to the shared backlog.
• Provide an export of initial integration logs and the first inventory import for review.
• Open targeted tickets for each root-cause action and add them to the shared backlog with resolution dates.
• Present first outcome data
• Determine whether inventory allocation accuracy and order throughput are tracking toward the Solution Scope targets.
• Agree a prioritized remediation plan with owners and dates to close identified gaps before the acceptance gate.
• Confirm integration uptime is acceptable or schedule a technical escalation if it is not.
• Publish the measurement report showing metric baselines, variance to Solution Scope targets, and proposed remediations.
• Schedule a technical detailed review if integration uptime is below the agreed threshold.
• Present outcome data against each criterion
• Deployment and integration validation
• Quality and allocation incidents
• Diagnose gaps and root causes
• Agree corrective actions and timelines
• Early adoption and usage signals
• Document pass/fail per criterion
• Shared backlog grooming and prioritization
• Operational risks and process improvements
• Formal acceptance decision and signatory
• Blockers and open issues
• Confirm readiness for acceptance gate
• Immediate remediation and short-term plan
• Remediation plan for failed or conditional items