Upload BOM & Gerber
-
Mobile: +86 13312967631
-
Email: sales@suga-pcba.com
Prototype PCB Assembly Services
PCB Prototype Manufacturer in China
SUGA has developed controlled prototype PCB assembly services to support OEM teams in the EVT, DVT, bring-up, and validation of their products. We provide support by reviewing your BOM, Gerber files, centroid, assembly notes, component readiness, and project-specific test requirements before your assembly is built.
Prototype Scope Review
Quantity, design revision level, assembly model, and any low-volume review boundary that may apply are reviewed during the prototype preparation phase.
Data Package Readiness
Each BOM, Gerber file, centroid, assembly drawing, polarity designation, reference designation, and revision note is reviewed to clarify RFQ details.
Engineering Feedback Loop
DFM/EQ feedback helps identify assembly and engineering issues before assembly and during prototype assembly and verification.
Project-Specified Verification
Based on project requirements, AOI, X-ray inspection, flying probe testing, functional testing, ICT testing, or ATE testing may be performed when required by the project scope, and relevant test data may be provided upon completion.
What Is Prototype PCB Assembly?
Prototype PCB assembly is the procedure followed to create prototype PCBAs from approved design files. This occurs prior to creating low-volume or production runs when the design has not been completely validated and may require design revisions, testing feedback, part changes, or clearer assembly instructions.
For OEM teams, this process provides value not simply by delivering assembled boards to the customer. During this development process, design files, part status, assembly assumptions, and verification expectations can be confirmed prior to the beginning of a controlled assembly process.
Prototype Assembly vs PCB Fabrication
PCB fabrication results in the creation of a bare printed circuit board, while prototype PCB assembly results in component assembly, soldering, inspection, and project-defined verification.
When a Project Moves Beyond Prototype Assembly
The prototype project should remain focused on learning, correcting, and gathering controlled build feedback from the assembled prototypes. If, however, the project progresses into a situation where higher quantities are created, many revisions occur, stable releases are established, or production planning is undertaken, the project should enter into a low-volume production review process rather than remain within the framework of the prototype process.
SUGA Prototype RFQ Review Thresholds
These thresholds assist in determining whether prototypes will be placed in the prototype workflow or reviewed under a related production workflow. They do not represent universal industry limits and do not impose limits on production quantities.
Prototype Scope Boundary
| Parameter | Value | Unit | Stage | Constraint |
|---|---|---|---|---|
| Order quantity | 1-25 | pcs | Prototype RFQ | 25 pcs is upper-limit review point |
| Low-volume review trigger | 25 pcs review point, 26+ pcs transfer | condition | RFQ review | Low-Volume workflow review |
| Revision review trigger | More than 3 revisions | revisions | EVT DVT iteration | Low-Volume workflow review |
| Minimum order quantity | 1 | pc | Prototype RFQ | No production MOQ claim |
| Build objective | EVT, DVT, bring-up, validation | phase | Pre-production verification | Not unit-cost optimization |
| BOM complexity | Design-dependent | count | BOM review | No public upper-limit claim |
| Sourcing mix | Turnkey, partial turnkey, consigned | model | RFQ and kitting | See Turnkey and Consigned pages |
| Mixed technology | SMT, THT, hand soldering, manual fit-up | process | Prototype assembly | |
| Revision flow | Rev A, Rev B, Rev C | status | Design iteration | Not production ECO governance |
| Engineering changes | Allowed before build release | status | Customer approval required | |
| Prototype stencil | Project-specific tooling | tool | SMT prototype build | No lifecycle tooling claim |
| Cost optimization | Out of scope | status | After design freeze | See Low-Volume and High-Volume pages |
| Production transfer | Design freeze and release pack | gate | Prototype exit | See Low-Volume Production page |
How to Use These Thresholds
These thresholds assist in the triage process for RFQs. If a project is not eligible due to the signals shown above, it may still be eligible for support by SUGA, but may require an adjustment of the operating model.
Preventing RFQ Delays from Incomplete Prototype Data
A prototype PCB assembly quote can only move through the process quickly if the engineering data is clear enough to review. Therefore, this section focuses on RFQ speed and release clarity with respect to the types of files that are required to generate the RFQ.
Material risk and substitution policies relating to the BOM are addressed later in the BOM risk section; therefore, the focus here will be file readiness, including BOMs, Gerber files, centroid files, assembly drawings, polarity, RefDes designations, DNP status, revision notes, and test requirements.
Prototype Data Package Readiness
| Input Item | Required Level | Accepted Format | Key Fields | Impact |
|---|---|---|---|---|
| BOM | Mandatory | XLSX, CSV | MPN, manufacturer, RefDes, quantity, description, DNP | Stop sourcing cannot begin |
| BOM silkscreen consistency | Mandatory | BOM, silkscreen, assembly drawing | RefDes match across BOM, PCB silkscreen, placement data | Delay RefDes reconciliation required |
| Approved alternates | Conditional | XLSX, CSV | Approved substitute MPN, approval rule, no-substitution items | Delay substitution approval required |
| Preferred distributor | Recommended | BOM field, RFQ note | DigiKey, Mouser, Arrow, Avnet, customer-approved source | Delay slower sourcing decision |
| Gerber data | Mandatory | RS-274X, Gerber X2 | Copper, solder mask, silkscreen, drill, outline | Stop PCB fabrication cannot begin |
| ODB data | Alternative | ODB++ | CAD-to-manufacturing data package | Delay CAM conversion if unavailable |
| IPC data | Alternative | IPC-2581, IPC-DPMX | PCB and assembly manufacturing data package | Delay data conversion if unavailable |
| Centroid file | Mandatory for SMT | CSV, TXT | RefDes, X, Y, rotation, side | Delay manual placement programming |
| Assembly drawing | Mandatory | Polarity, Pin 1, orientation, mounting notes | Risk reverse mounting or assembly ambiguity | |
| Fabrication drawing | Conditional | Stack-up, finish, tolerance, impedance, drill notes | Delay fabrication clarification | |
| Mechanical outline | Conditional | DXF, DWG, PDF | Board outline, mounting holes, keep-outs, enclosure interface | Risk mechanical fit issue |
| Netlist | Recommended | IPC-D-356, CAD export | Connectivity reference, test points, nets | Risk slower electrical verification |
| Schematic | Recommended | Debug reference, power rails, interfaces | Delay slower bring-up support | |
| Test plan | Conditional | PDF, XLSX | Pass criteria, measurement points, sequence, class if specified | Delay functional test cannot be executed |
| Firmware file | Conditional | HEX, BIN, ELF, project file | Version, checksum, programming method | Stop programming or FCT blocked |
| Known-risk list | Recommended | PDF, TXT | Experimental circuits, thermal zones, marginal clearances | Risk weak engineering feedback loop |
| Revision note | Mandatory when changed | ECO, read-me | Revision change, DNP, jumper, rework instructions | Risk wrong revision built |
What the Table Is Meant to Prevent
The data package table is a build-readiness filter, not a list of paperwork. Missing or inconsistent files could cause stop, delay, or risk conditions with respect to the quote for a prototype, even when the number of PCBs required is small.
Application Scenarios
Prototype PCB assembly is most useful when OEM engineering teams require physical copies of their designs for the purpose of engineering learning, design validation, decision-making prior to commencing full production. The following project scenarios assist customers in assessing whether they can use the prototype assembly process and whether it is a viable solution for their specific build application.
EVT Builds
Typical Fit
Early engineering validation of the design while the design is still being developed and has not yet been launched into full production.
Problem This Helps Solve
This project scenario provides OEM engineering personnel with the ability to confirm that the released files, BOM, and first assembled prototypes are adequate to support the engineering plans for the next version of the design.
DVT Iteration
Typical Fit
Repeated review of engineering drafts before the design is frozen and/or prior to transferring production of the design to a low-volume manufacturing process.
Problem This Helps Solve
This project scenario allows OEMs to control revisions, customer approvals, and feedback about the assemblies created during the prototype build process.
Mixed-Technology Prototypes
Typical Fit
Prototypes that have more than one technology on the same PCB assembly, including surface mount technology (SMT), through-hole technology (THT), manual assembly, hand soldering, manual connector assembly, quad flat no-lead (QFN), or ball grid array (BGA) technology.
Problem This Helps Solve
This project scenario provides OEM engineering with the ability to determine how to collect and document assembly data, package orientation, inspection methods, and assembly fit-up risk.
Prototype Builds with Component Sourcing Risk
Typical Fit
Prototype builds that are affected by approved alternate part numbers, long lead times for parts, obsolete parts, or the inability to obtain a manufacturer-approved equivalent.
Problem This Helps Solve
This project scenario allows OEMs to prevent sourcing exceptions from turning into a de facto substitution or delaying prototype builds.
Prototype Builds with Project-Specified Test Scope
Typical Fit
Each prototype has a different testing scope required by OEMs and must be agreed upon prior to quotation. Examples of testing scope include automated optical inspection (AOI), X-ray inspection, flying probe testing, functional testing, in-circuit testing (ICT), automated test equipment (ATE), programming, and aging testing.
Problem This Helps Solve
This project scenario allows OEMs to identify test data, firmware status, test fixture needs, and pass/fail criteria for quotes before prototype builds.
Prototype-to-Low-Volume Transition Review
Typical Fit
Projects that have 26+ pieces, have multiple changes occurring through the build process, and/or are approaching design freeze.
Problem This Helps Solve
This project scenario allows OEMs to determine when their project shifts from prototype validation planning to low-volume manufacturing preparation.
Engineering Feedback and Revision Control
By assembling prototypes, the team can identify build-related risks early and prevent the same issues from being repeated across prototype revisions. The DFM/EQ feedback process is there to allow team members access to feedback associated with design for manufacturability and engineering questions before the customer approval stage, allowing for the resolution of assembly, sourcing, and verification problems as they arise during the early stages of design.
DFM/EQ Feedback Before Build Release
DFM/EQ feedback generally is related to problems with polarity, footprint concerns, Bill of Materials (BOM) and Reference Designator (RefDes) mismatches, solderability areas where soldering may be difficult, insufficient test access before assembly, missing placement information, and questionable component availability. The goal of the feedback process is to provide customers with enough information to make a better decision about the product before its assembly.
Customer Approval for Changes and Substitutions
Whenever a change occurs in the BOM, layout, component selection, DNP status, jumper instructions, firmware version, or test requirements, the updated release information must be verified again before continuing assembly to prevent assembling a quantity of product with incorrect revision data.
Build Feedback for the Next Revision
The results from inspections, notes made during the bring-up phase, observations made during testing, problems experienced with programming, sourcing exceptions, and assembly issues may influence the design of the next revision of a product. This controlled feedback loop provides the engineering team with the ability to determine the future course of action for a particular product: whether to modify the design, assemble an additional quantity of the same product, or move forward with a low-volume review version of the design.
Verification and Test Scope by Project Requirement
The verification of the assembled prototype printed circuit board assembly (PCBA) should be defined by project goals, released test data, customer acceptance criteria, and the terms of the request for quote (RFQ) agreement. Some builds require only visual inspection and automated optical inspection (AOI), while others may also require X-ray, flying probe, programming, functional test, in-circuit test (ICT), automated test equipment (ATE), aging test, or customer-defined acceptance criteria.
Verification method descriptions are established in accordance with the RFQ scope, released test data, customer acceptance criteria, and project agreement. Not every item listed below is the standard for every prototype assembly.
Verification Method Acceptance Basis
| Verification Item | Method | Acceptance Basis | Fixture | Trigger | Prototype Reason | Boundary |
|---|---|---|---|---|---|---|
| Workmanship inspection | Visual and microscope inspection | IPC-A-610J class by RFQ | No | Project inspection requirement | Fast visual acceptability check | Class 3 requires RFQ agreement |
| Soldering process control | Process review | IPC J-STD-001J by RFQ | No | Project soldering requirement | Project process requirement is separate from inspection | Does not replace A-610 acceptance |
| SMT placement check | AOI program using customer drawings and polarity data | Customer drawing and polarity data | No | SMT components, polarity, and orientation | Catches placement and orientation issues without fixture | Not a claim of placement machine capability |
| BOM silkscreen check | Manual review and first article check | BOM, silkscreen, and assembly drawing | No | Prototype release and first article | Prevents reference designator (RefDes) mismatch between first and subsequent assembly builds | Requires aligned source files to perform comparison |
| Hidden solder joints | 2D X-ray is commonly used when ball grid arrays (BGAs) are assembled, and 3D automatic X-ray inspection (AXI) is available upon request | Customer acceptance criteria or IPC class as defined in RFQ | No | BGA, QFN, LGA, and bottom-terminated components | 2D X-ray supports solder-joint evaluation; 3D AXI provides more extensive analysis | Refer to the BGA Assembly page for process detail |
| Bare PCB electrical test | Flying probe testing of the netlist as defined in IPC-9252B for unpopulated boards | IPC-9252B for unpopulated boards | No | Prototype PCB fabrication | No fixture needed to verify low-quantity PCB fabrication | Not assembled PCBA FCT standard verification |
| Prototype electrical check | Flying probe or probe-based test using a customer-provided netlist | Customer test access and netlist | No | Accessible nets and test points | Avoids the use of an ICT fixture when designs are not yet stable | Does not provide full ICT verification coverage |
| ICT | Not a standard default | Customer test specification | Yes | Stable design and fixture justification | Usually, prototypes do not justify using ICT fixtures | Refer to Low-Volume and High-Volume pages |
| Functional test | Benchtop and customer-defined functional test | Written customer test plan with pass criteria | Conditional | Firmware version, test fixture, and test method must be released and approved | The functional test protocol for prototypes is typically benchtop or semi-manual rather than fully automated | Not automatic system integration |
| Programming | Manual or semi-automatic programming | Customer firmware file and checksum | Conditional | Firmware and programming method must be released and approved | Supports the testing and troubleshooting of prototypes without the use of a production programming line | Box build integration is outside this prototype assembly scope |
| MSD handling | Dry storage and baking are required when components are classified according to J-STD-020F and handled according to J-STD-033D | J-STD-020F classification and J-STD-033D handling | No | MSL-labelled SMDs | Prevents moisture-related reflow damage to prototypes | MSL handling is not component qualification |
| Incoming part check | Label, manufacturer part number (MPN), date code, and packaging review | Customer sourcing requirement | No | Turnkey or mixed sourcing | Reduces the risk of receiving or using incorrect parts and counterfeit-risk exposure | AS6081 process can be used only for high-risk sourcing upon request |
What Is Not Default
ICT, ATE, custom fixtures, functional test, aging test, and 3D AXI should be defined by the project, customer requirements, or agreement. This table will assist in preventing the prototype assembly scope from becoming an undefined production test package.
BOM Availability, Obsolescence, and Substitution Control
This section addresses material risks, whereas the RFQ file checklist deals with file readiness. An accurate BOM will not address these important issues if there are no available parts, if the parts are obsolete, if there are rules that prevent substitutions of parts, or if the BOM does not list customer-approved alternate parts.
01
Obsolete or Long-Lead Components
Parts that are obsolete or have a long lead time will affect the timing for the assembly of prototypes; even when manufacturing capacity is available, prototype project schedules may be impacted. Examples of actions needed to resolve issues created by obsolete or long-lead parts would be sourcing review, finding alternate part(s), correcting BOM(s), or waiting for customer decisions prior to being able to release builds.
02
Approved Alternates and No-Substitution Items
When customer-approved alternates are used, this can expedite the part sourcing process if the original part(s) are not available at the time of prototype production; however, the approved alternate part(s) must be defined prior to build release. In the event that a no-substitution part affects firmware behavior, analog performance, radio frequency (RF) behavior, safety review, regulatory planning, or customer validation, it will also be necessary to identify the no-substitution parts that affect the items listed above.
Sourcing Model Clarity
There are several different sourcing models used to manufacture prototypes: full turnkey, partial turnkey, and consigned sourcing models. The customer and all parties involved must be aware of material responsibility, substitution approval, shortage handling, and the customer’s responsibilities for providing the customer-supplied kits used during assembly.
Prototype PCB Assembly Cost and Lead Time Factors
When assembling the prototype of a PCB, it is not only the number of boards that determines how long it is going to take and how much it will cost. Even with a small prototype quantity, you could have to spend extra time double-checking everything if the BOM consists of many different components, components aren’t available, testing isn’t defined, and/or the design build data needs clarification prior to release for build.
The timeframes identified above only apply if all the identified prerequisites are satisfied. For example, if you create a project that contains missing data, has limited availability of components, has delays in obtaining approvals, has upcoming holidays, has component backorders or customs delays, or has custom test requirements, the project could incur additional delays.
Prototype Lead Time Matrix
| Stage | Standard Window | Fast Window | Unit | Prerequisite | Exclusion | Logic |
|---|---|---|---|---|---|---|
| DFM file review | 1-2 | 0.5-1 | working days | Clean data pack | Unresolved drawings or missing BOM | Pre-requisite |
| Prototype PCB fabrication | 3-5 | 1-2 | working days | Standard rigid PCB and standard finish | HDI, impedance stack-up, special laminate | Parallel with sourcing |
| Custom PCB fabrication | Project-dependent | Project-dependent | working days | Reviewed stack-up and fabrication drawing | No fixed public lead time | Risk extension |
| Component sourcing kitting | 2-5 | 1-2 | working days | Distributor stock parts and approved alternates | Long-lead parts or blocked substitutions | Major prototype bottleneck |
| Component shortage exception | Project-dependent | Project-dependent | working days | Confirmed shortage or obsolete part | Standard lead time no longer applies | Sourcing-defined schedule |
| Assembly programming | 0.5-1 | Project-dependent | working days | BOM, centroid, assembly drawing released | Missing RefDes, rotation, side, or polarity data | Before SMT |
| SMT THT assembly | 1-2 | 0.5-1 | working days | PCB and complete kit released | Incomplete kit or late substitution | Fixed process step |
| AOI visual inspection | 0.5-1 | 0.5 | working days | Assembly complete | Project-specific inspection hold | Post-assembly gate |
| Flying probe electrical check | Project-dependent | Project-dependent | working days | Test access and netlist available | No probe access or missing netlist | No ICT fixture by default |
| Functional test | Project-dependent | Project-dependent | working days | Test plan, firmware, and pass criteria released | Missing fixture, firmware, or customer approval | Customer-defined scope |
| Total turnkey prototype | 5-10 | 3-5 | working days | Standard rigid PCB, HASL or ENIG finish, fewer than 100 components, distributor stock parts, clean data pack | BGA, QFN, HDI, custom fixture, customs delay, holidays, approval hold | Not arithmetic sum |
| Assembly-only prototype | 24-48 | RFQ-confirmed | hours | Released PCB, complete kit, centroid, assembly drawing | Missing kit, missing PnP, or unresolved polarity | Not full turnkey |
How to Read Lead Time Windows
The standard and fast lead time windows are not unconditional guarantees, but rather they depend upon the following items: clean data, released PCB status, availability of components, approved substitutions, completed kits, clear testing scope. For assembly-only timing, the PCB, kit, centroid file, and assembly drawing must have been released before being reviewed.
Prototype-Friendly Manufacturing Support
Instead, the essential information that buyers will want to know will be related to the availability of resources, including SMT, DIP, assembly, inspection, and testing, that can be evaluated based on the prototype’s complexity and project requirements.
Manufacturing Resources for Prototype Complexity
Design data released by the customer will dictate SUGA’s process flow, which may include SMT, DIP, assembly, conformal coating, aging, AOI, FAI, X-ray, ICT, ATE, and project-specific verification resources. In addition to design data, SUGA’s process flow will be dependent on component package types, assembly drawings, inspection requirements, and the agreed testing scope.
Management Systems Supporting Controlled Builds
SUGA’s management system information includes ISO9001:2015, ISO14001:2015, QC080000:2017, ISO13485:2016, and ISO45001:2018, and will help to provide the necessary support for the development of controlled communication and documentation discipline. The existence of ISO management systems does not imply that all prototypes produced by SUGA will satisfy a particular product approval, audit outcome, and/or regulatory certification.
Request a Prototype PCB Assembly Quote
To obtain an accurate and useful prototype PCB assembly quote, it is important to provide more than just a target quantity. SUGA needs to have access to all necessary information about the board files, BOM status, assembly model, revision stage, component sourcing requirements, and any inspection/test expectations that will occur prior to build release in order to properly review and assess the project.
To prevent unnecessary delays with the RFQ, make sure to select a sourcing model and set forth all information about any released test plan, firmware status, fixture information, or acceptance criteria for programming, functional test, X-ray, ICT, ATE, or aging test requirements.
What We Need for a Prototype PCBA Quote
To prepare an accurate prototype PCB assembly quote, please submit available project files and requirements.
- BOM with MPN, manufacturer, quantity, RefDes, and DNP status
- Gerber files and drill / stackup information when available
- Centroid or XY placement data
- Assembly drawings with polarity, orientation, and revision notes
- Prototype quantity, revision stage, and target schedule
- Inspection, programming, functional test, ICT, ATE, X-ray, or aging requirements when applicable
Submit any available project files and/or requirementsSUGA can review available files and clarify missing items during follow-up
Upload BOM and Files
What Happens Next
1Initial Engineering Review
2BOM and Data Package Check
3Quote and Lead-Time Review
4Follow-Up to Confirm Build Scope
FAQ for Prototype PCB Assembly Buyers
If your product is still under development and in the process of verification, validation, bring-up, or revision learning, it is likely still in the prototype phase. If your product is moving into 26+ pcs, repeated revisions, design freeze, or scheduled repeat builds, it should enter the low-volume workflow.
Prototype boards may fail during validation for many reasons. Some reasons may include design errors, component selection errors, inaccurate assembly instructions or assembly data, polarity errors, footprint issues, soldering defects, lack of firmware readiness, lack of test access, or incomplete functional test criteria.
In this situation, the RFQ may need sourcing review, approved substitutions, no-substitution confirmation, customer approval, or BOM correction before assembly release. Additionally, when a controlled component is listed in the BOM as obsolete and/or long-lead, SUGA cannot substitute the controlled component without customer approval.
Prototype PCB assembly can use several testing methods. The type of testing employed will be determined by the testing requirement of the prototype PCB assembly. There are several types of testing methods to look at, including but not limited to: visual inspection, AOI, X-ray, flying probe checks, programming, functional testing, in-circuit testing, automated test equipment, and aging tests. There are many factors that come into play to determine what types of testing methods will be used for your prototype PCB assembly, such as board design, test access, firmware status, fixture availability, and acceptance criteria.
Yes, SUGA can review cost-sensitive prototype PCB assembly projects; however, it cannot be positioned as a low-cost/low-end prototype assembly option. The review of costs for a prototype will depend on the number of pieces, BOM status, PCB requirements, inspection scope, testing requirements, and sourcing model.
Yes. SUGA does not claim local manufacturing in other regions unless a local facility or regional capability is confirmed.
Still have questions?
If you have a specific question that we did not answer, please reach out directly to our engineering team or send your BOM and Gerber files so that we can review them.
Technical Standards Scope Control
The standards below clarify which technical references may apply to a prototype PCB assembly project based on RFQ requirements, customer specifications, project agreement, and applicable documentation.
Standards Scope Control
| Standard | Status | Scope | Prototype Use | Boundary |
|---|---|---|---|---|
| IPC-A-610J | Current revision 2024 | Acceptability of electronic assemblies | Class 2 or Class 3 acceptance by RFQ | Do not imply universal Class 3 |
| IPC J-STD-001J | Current revision 2024 | Soldering process and materials | Project-specified soldering requirement | Does not replace A-610 acceptance |
| IPC-7351B | Current official revision | SMD land pattern reference | DFM reference for footprints and pads | Do not write IPC-7351C or IPC-7351D unless officially verified |
| IPC-9252B | Referenced revision | Electrical testing of unpopulated printed boards | Prototype PCB netlist test reference | Do not use as assembled PCBA FCT standard |
| IPC-6012F | Current rigid PCB performance reference | Rigid printed board fabrication requirement | Brief fabrication coordination reference | |
| IPC-6012DS | Special addendum | Space and military avionics PCB applications | Only when customer requires it | Do not use as general prototype standard |
| IPC-JEDEC J-STD-020F | Current revision 2022 | Moisture reflow sensitivity classification for nonhermetic SMDs | MSL classification reference | Do not use as handling process alone |
| IPC-JEDEC J-STD-033D | Current handling standard | Handling, packing, shipping, and use of moisture-sensitive components | MSD handling process control | Do not use for component qualification |
| IPC-2581 | Accepted data exchange standard | PCB and assembly manufacturing description data transfer | Accepted data package option | Do not force IPC-2581B version claim |
| IPC-DPMX | Accepted data exchange name | Digital Product Model Exchange | Equivalent data package reference for IPC-2581 | Do not duplicate as separate process capability |
| Gerber RS-274X | Current Gerber layer format | PCB image layer data with embedded apertures | Accepted fabrication data | Do not use RS-274-D as current format |
| Gerber X2 | Preferred Gerber attribute format | RS-274X with standard attributes | Preferred CAM data when available | Do not require it if RS-274X package is complete |
| RoHS REACH | Project-dependent compliance status | Material and substance compliance | Controlled by customer BOM, solder, and sourcing requirement | |
| AS6081 | High-risk sourcing reference | Counterfeit parts avoidance and mitigation | Upon request for high-risk sourcing | Do not use as default prototype inspection standard |