Skip to the stories
Electronics & Semiconductors

Second-Source MCU Approval: Build a Complete AVL Evidence Packet

  • laura-garcia
  • 695 reads

A complete technical, quality and cost packet can help teams review a second MCU source in one pass, with fewer avoidable returns.

Second-Source MCU Approval: Build a Complete AVL Evidence Packet

Adding a second microcontroller (MCU) source depends on more than finding a compatible part. The request must also give engineering, quality, procurement and the Approved Vendor List (AVL) owner the evidence each needs to approve the part and the supply channel. A complete packet can prevent avoidable review returns; it can’t guarantee approval.

Getting a Second MCU Source Approved in One Cycle The Pulse

EETech Research’s 2026 Buyer Journey Study highlights the handoff problem: 71% of engineers help recommend the final component, but 31% take part in approving its purchase. Although 84% are decision-makers or strong influencers in component selection, their recommendation can lose momentum as procurement and sourcing decisions proceed.

AVL rules are common, but a fully locked list is not. The study reports that 62% of engineers work under some form of AVL constraint, while only 5% can choose exclusively from listed vendors. Among engineers working with an AVL, 99% would advocate adding a vendor. The challenge is assembling a specific, defensible case that addresses supply, cost or technical capability.

What the approval handoff needs to resolve

Most purchases proceed without issue: 64% of engineers said their preferred component was purchased as selected. For the other 36%, availability drove a change in 10.6% of cases; the final decision was outside the engineer’s control in 8.0%; procurement suggested an alternative in 7.6%; cost led to a change in 4.8%; a difficult ordering or documentation experience caused delay or change in 3.7%; and AVL restrictions did so in 1.7%.

That breakdown points to the evidence a second-source request should bring forward. The AVL itself was cited as the reason for a change less than 2% of the time, so the request needs to show how the alternative addresses supply, cost and procurement concerns, as well as list eligibility.

“One cycle” means one complete pass through the review, without a return for missing information. It doesn’t mean automatic or guaranteed approval. The request can cover a different part number from the same MCU maker or a part from another manufacturer, and it must identify the channel through which the component will be purchased.

Match the evidence to the approver

Review typically proceeds through four roles. In a smaller organization, one person may cover several of them, but the questions still need answers. If the company requires additional customer or export reviews, include those steps before the AVL owner’s decision.

StageApproverQuestionEvidence to include
1Engineering sponsorWill the MCU work without a redesign?Functional and pin-level comparison, peripheral mapping, and expected firmware changes.
2Quality assuranceCan we verify the source and the parts received?Channel verification and an incoming inspection plan. For authorized distributors, document franchise status. For independent channels, provide SAE AS6081A evidence and distinguish it from buyer-side SAE AS5553E programs and SAE AS6171 test methods.
3Procurement or sourcingWhat will it cost, and what supply risk does it reduce?Total landed cost, including unit price, freight, tariffs and minimum order quantities (MOQs); single-source exposure, lead-time differences and material planning (MRP) allocation history.
4AVL ownerCan the addition be defended, and what risk remains?Approval precedent and remaining audit exposure, including whether the change can withstand customer review.

Submissions often return when information arrives piecemeal, when a role is asked to create data outside its remit, or when source verification consists only of a link or screenshot that doesn’t establish authorization. Routing to the AVL owner before quality confirms source legitimacy can also send the review back to the start. Assemble the technical, quality and commercial sections in parallel, then route one complete packet.

Make the supply case measurable

Lead with the reason that best supports the proposed source: supply stability, lower cost or a distinct technical capability. A statement that the MCU is “comparable” doesn’t quantify the benefit. A stronger case ties the alternative to exposure the company can measure, while acknowledging the work it will require.

For example, the source describes an incumbent MCU used across four products representing $3.2M in annual revenue. Over 24 months, quoted lead times ranged from 14 to 39 weeks against a planned 12 weeks, with three allocation events. At current inventory levels, an interruption could halt production of two products within nine weeks. Splitting purchase volumes between two sources could reduce dependence on one supplier, but firmware porting and requalification would still need attention.

Document the supply channel

Quality needs channel evidence in the initial packet. For an authorized route, compare the distributor with the component maker’s distributor listings. Confirm that authorization covers the relevant product line and region, and check the listing when submitting because it can change. If the part number isn’t explicitly covered, obtain written confirmation from the manufacturer or distributor.

Attach a dated PDF or screenshot that shows the distributor, product line or region, and access date; keep the page address as well. A link by itself doesn’t document what was verified. Manufacturer locator pages include Microchip, STMicroelectronics, NXP, Texas Instruments, Infineon, Nordic Semiconductor, Renesas, Silicon Labs, GigaDevice, Nuvoton and Espressif.

If an authorized channel can’t supply the part, the packet should document current SAE AS6081A accreditation for counterfeit avoidance, detection, mitigation and disposition. Ask the distributor’s quality contact for the active certificate and its scope. Confirm with the certification body that the certificate is active and covers the claimed site and work. Cross-check its number and the underlying quality-system certificate, such as ISO 9001 or AS9120, against the issuing registrar or IAF CertSearch. Attach the verified documents.

Use a checklist to keep the packet together

SectionOwnerIncludeComplete when
Technical equivalenceEngineeringSide-by-side datasheet comparison, pin and function matrix, and explicit firmware changes.Every difference has a disposition: none, accepted or mitigated.
Source legitimacyQualityAuthorization proof or the complete active SAE AS6081A certificate, plus an incoming inspection protocol.Documents carry a verification date, and the inspection plan names tests for the channel.
Supply riskProcurementSingle-source exposure, revenue at risk, single point of failure (SPOF) rating and historical allocation records from ERP or MRP systems.Figures identify their sources; available stock and lead times are documented.
Commercial modelProcurementLanded cost, including freight, duties, tariffs, MOQs and testing fees.Both options use the same volume assumptions and comparison date.
Sign-off recordAll approversName, role, date and decision for every review stage.All four decisions refer to the same packet version.

Attach the evidence itself rather than relying on links. Compile the five sections into one file, such as a PDF, and retain an editable version for updates. Number channel documents to match the checklist, and keep all decisions against the same packet version. Partial routing invites partial reviews and can restart the process. A blank team template in a product lifecycle management (PLM) system or shared drive gives the next request a consistent starting point.

Plan review time around the work

A sample timeline in the source is a planning model, not a survey result. It assumes the technical evaluation, samples and source checks are complete before routing, and should be adjusted to fit actual reviewer schedules:

  • Week 0: Engineering completes the equivalence matrix while procurement assembles risk and commercial data.
  • Week 1: Quality reviews the complete packet and confirms inspection needs.
  • Week 2: Procurement checks landed-cost calculations and current supply availability.
  • Week 3: The AVL owner reviews the consolidated case and records a decision.

This schedule excludes firmware porting, board-level qualification, reliability testing, customer approval and export review. Missing evidence may lead to a condition, delay or another review pass. Before submission, confirm the alternative’s authorized-channel availability, lifecycle status and lead times. Those details connect the engineering case to the supply conditions procurement will have to manage.

Getting a Second MCU Source Approved in One Cycle Cover

Source: laura-garcia · resources.altium.com

From the same set