Who Should Provide the FCT Fixture for PCB Assembly?

Overview

There is no universal rule that says the OEM must provide the FCT fixture, or that the EMS provider should always build it.

For a PCB assembly test fixture, the OEM or design owner should normally define or approve the product-specific functional requirements and acceptance criteria. The physical fixture may then be supplied by the customer, developed as part of the EMS project, or engineered with a specialist test-equipment partner.

Those decisions should be separated early. Fixture design, test software, non-recurring engineering (NRE), ownership, maintenance, revision changes, and future transfer are related, but they are not the same responsibility.

If all of that is buried inside a quotation line that simply says FCT included, there is still work to do before the test scope is ready for production.

"Who Provides the Fixture?" Is Not Really One Question

A quotation may contain a line such as:

FCT fixture: supplier provided

That looks straightforward. Once engineering starts, however, "provided" can mean several different things.

Those responsibilities do not have to sit with one company.

The OEM may approve the test requirement while the EMS provider develops the manufacturing fixture. A specialist test integrator may supply a more complex test system while the EMS factory operates it in production.

The useful question is not simply who supplies the hardware. It is who owns each decision required to make the test repeatable.

 

First, Separate the Fixture From the Test Station

This is one of the easiest distinctions to lose during quotation.

The fixture is normally the DUT-specific mechanical and electrical interface between the PCB assembly and the test resources.

Depending on the product, it may include:

• a mechanical nest;
• pogo probes;
• fixture plates;
• wiring;
• mating connectors;
• harnesses;
• product-specific adapters;
• actuators or access mechanisms.

The test station may include reusable equipment that serves many products:

• a computer;
• power supplies;
• a digital multimeter (DMM);
• an oscilloscope;
• programmable loads;
• switching hardware;
• communication interfaces;
• common rack hardware;
• test software infrastructure.

The difference usually becomes obvious when fixture NRE appears on the quotation.

A customer may pay for a product-specific fixture without purchasing the instruments, computers, software licenses, or reusable test platform used to run it.

If ownership matters, do not leave the purchase order to define that boundary by accident.

A Fixture Is Not the Test Specification

A fixture can make a test repeatable.

It cannot decide what the product is supposed to do.

Depending on the PCB assembly, Functional Testing may use pogo probes, a bed-of-nails arrangement, wiring harnesses, edge connectors, existing product connectors, mechanical nests, or several interfaces together.

Those are ways to reach and operate the DUT. They are not the functional requirement.

Before fixture engineering is ready to freeze, the project may need answers to questions such as:

• What operating state should the board enter?
• What inputs or commands should be applied?
• Which outputs or responses need to be checked?
• Is firmware or configuration required?
• Does the test need an external load, simulator, sensor, peripheral, or communication partner?
• Which measurements have limits?
• What constitutes PASS?
• Which failures should go to rework, retest, or engineering review?

Define the test first. Then design the fixture around it.

If the required behavior is still unclear, the fixture engineer is still missing part of the job.

 

If the Test Scope Is Not Defined, the Fixture Price Is Still Assumption-Based

This situation comes up early in many RFQs.

A buyer asks:

How much will the FCT fixture cost?

But the project has not yet established:

• what functions need to be tested;
• how the board can be accessed;
• which external devices or loads are required;
• whether programming is part of the station;
• what instruments are needed;
• whether test software already exists;
• what data needs to be recorded;
• what acceptance criteria apply.

A supplier can still provide a budgetary estimate. That may be useful for planning.

Until the test scope is defined, however, the fixture price should be treated as budgetary and assumption-based, not as a fully frozen tooling scope.

The reverse situation deserves just as much attention.

If nobody has asked about startup states, loads, firmware, interfaces, test access, and pass/fail criteria, the FCT scope is not ready to freeze.

 

NRE Is a Cost Line. Ownership Is a Contract Term.

Fixture-related non-recurring engineering may cover some combination of:

• fixture design;
• mechanical fabrication;
• wiring;
• adapters;
• software setup;
• integration;
• debug;
• documentation;
• validation work.

Paying that charge answers one question:

Who funded the project-specific work?

It does not automatically answer another:

Who owns every asset associated with the test?

Depending on the commercial agreement, the customer-owned deliverables might include:

• the physical DUT fixture;
• custom adapters;
• mechanical drawings;
• wiring documentation;
• fixture-specific software;
• configuration files;
• source code where it is specifically included in scope;
• spare or wear components.

Other equipment may remain part of the factory's reusable infrastructure:

• test instruments;
• computers;
• common racks;
• switching systems;
• licensed software;
• shared test platforms.

A paid NRE invoice is not, by itself, a tooling-ownership specification.

If ownership, storage, reuse, or supplier transfer matters, put it in the quotation, tooling agreement, purchase order, or another controlled project record.

A Fixture Can Still Fit the Board and Still Be Wrong

Fixture revision control is not only about mechanical fit.

Some board changes have obvious physical consequences.

A connector moves.
A test point disappears.
A component becomes taller.
A locating feature changes.

Others are less visible.

The board may still sit perfectly in the fixture while a change to power architecture, firmware, communications, sensors, or I/O makes the existing test sequence incomplete or incorrect.

Before production relies on a changed board or fixture, the setup should be checked against the approved hardware revision, test definition, software dependencies, and acceptance criteria.

Physical fit is necessary. It is not enough.

Fixture Maintenance and Fixture Modification Are Different Jobs

Pogo probes, connectors, cables, clamps, and other fixture contacts are wear items.

There is no useful universal rule that says every probe should be replaced after the same number of cycles. Probe life depends on the specific hardware and how the fixture is used.

In production, warning signs are more useful than a copied cycle count:

• unstable contact;
• intermittent results;
• recurring false failures around the same contact;
• contamination;
• damaged probe tips;
• poor plunger return;
• damaged connectors or cables.

Replacing a worn probe is maintenance.

Moving that probe because a new PCB revision relocated the test pad is an engineering change.

They need different controls.

 

Supplier Transfer Is Where Fixture Ownership Becomes Real

Fixture ownership can feel straightforward while one supplier is producing the board successfully.

A transfer exposes the details.

Suppose the OEM owns the physical fixture and wants to move production to another EMS provider. The receiving site may still need:

• the functional test requirement;
• fixture revision information;
• wiring documentation;
• cables and adapters;
• test software;
• software dependencies;
• required instruments;
• firmware or configuration;
• maintenance information;
• acceptance criteria.

Owning the fixture hardware is not always the same as owning a transferable test process.

A customer can own the physical fixture and still lack enough information to reproduce the test elsewhere.

The opposite can happen too. A well-documented test requirement may allow a new fixture to be recreated even when the original hardware cannot be reused.

If second sourcing or future factory transfer matters, that should influence the fixture agreement from the beginning.

 

How STHL Fits Into the Fixture Discussion

Shenzhen STHL Technology Co., Ltd. (STHL) includes Functional Testing within its Testing and Inspection service scope.

For an applicable PCB assembly project, fixture planning can begin by reviewing the functional requirement, current board revision, available test access, firmware or configuration dependencies, production stage, and any existing fixture or test documentation supplied by the customer.

The project scope can then clarify:

• whether an existing fixture can be reused;
• what fixture or interface preparation is required;
• what test equipment is needed;
• what information the customer needs to provide;
• whether programming is part of the test flow;
• what test records are expected;
• what fixture-related NRE is included or excluded.

Fixture design, fabrication, test software, tooling ownership, maintenance, and future transfer should be confirmed for the individual project rather than assumed from a generic statement that "FCT is included."

 

Conclusion

Who should provide the FCT fixture for PCB assembly?

There is no automatic OEM-versus-EMS answer.

The OEM or design owner should define or approve what correct product behavior means. The physical PCB assembly test fixture may then come from the customer, be developed within the EMS project, or involve a specialist test partner.

Before fixture development begins, five decisions should be clear:

• what must be tested;
• who engineers the DUT-specific fixture;
• who pays for the project-specific work;
• who owns the agreed deliverables;
• who maintains, changes, and transfers them later.

When those responsibilities are explicit, the fixture becomes a controlled engineering deliverable rather than an assumption hidden inside the quotation.

For a project requiring fixture-based Functional Testing, include the available PCB files, current board revision, functional test requirements, firmware information where applicable, and any existing fixture documentation when you submit your project details.

For test-specific questions, contact STHL at info@pcba-china.com.