Home/Glossary/Customer Owned Tooling: COT Model
Semiconductor knowledge

Customer Owned Tooling: COT Model

Customer Owned Tooling (COT) is a semiconductor business model in which the customer retains responsibility for key design and tooling decisions. The division of design, foundry and production responsibilities depends on the agreement.

← All glossary termsTechnical guide · 5 min read
In this article

Customer Owned Tooling (COT) is a semiconductor business model in which the customer retains responsibility for key design and tooling decisions. The division of design, foundry and production responsibilities depends on the agreement.

Responsibilities in an ASIC engagement
A scope checklist rather than a certification or a promise that every service is included.

What the model allocates

Customer Owned Tooling describes an engagement in which the customer retains important design and tooling responsibilities. It is a business arrangement, not a particular transistor technology or a guarantee that every activity stays inside the customer organization. The useful question is who owns each deliverable and each decision. A customer may bring a verified netlist while a partner handles physical implementation, or bring a completed layout while requesting productization assistance. The statement of work must explain these boundaries rather than relying on the acronym alone.

What must be handed over

A COT handover can include RTL, gate-level netlists, timing constraints, power intent, IP documentation and verification reports. The exact set depends on the agreed entry point. Each item needs a version and an acceptance criterion. For example, an implementation team needs to know whether a clock relationship is intentional, whether a timing exception has been reviewed and which operating modes require sign-off. Open issues should be listed with owners. Unrecorded assumptions tend to become integration disputes when a downstream result differs from expectations.

COT-Plus in a project discussion

Avnet's published COT-Plus model describes support beginning with customer RTL or a netlist and continuing toward implementation and manufacturing management. The commercial scope still needs project-specific confirmation. Discuss how engineering changes are approved, whether IP licenses permit the proposed flow, and which party can authorize tape-out. Clarify the treatment of design data, foundry submissions, test-program development and production changes. A model description helps start the discussion; it does not replace the signed technical and commercial responsibilities for an individual program.

Ownership throughout the lifecycle

Keeping design ownership creates continuing responsibilities. Someone must maintain the authoritative source revision, approve bug fixes and preserve the information needed to reproduce the chip. Ask what happens if an IP block becomes unavailable, a process changes or a product requires a second source. A practical ownership plan also covers tools and formats: having an output file is different from having the licenses and expertise needed to modify it. Plan support, archive access and change control alongside the initial engineering effort.

Questions about COT engagements

Does COT mean the customer must operate a fab?

No. Design ownership and tooling responsibilities are separate from owning manufacturing facilities. Fabrication can be performed by a foundry under the agreed supply arrangement.

Is COT always cheaper than a turnkey model?

No universal comparison is meaningful. Evaluate internal engineering effort, external scope, licensing, project risk and production responsibilities. A lower quoted service fee may exclude work that the customer must fund or perform elsewhere.

Write a responsibility matrix

For each major activity, identify who supplies the input, performs the work, reviews the result and authorizes the next step. Include requirements, IP, verification, implementation, manufacturing preparation and product release where relevant. A broad service label cannot answer these questions by itself. Make customer dependencies visible and define how incomplete or changed inputs affect the plan. This gives both organizations a practical basis for managing handovers and prevents important work from being assumed to belong to the other party when a project reaches a difficult decision.

Use milestones with acceptance evidence

Describe deliverables and checks, not only dates or percentage-complete estimates. An architecture review should leave an approved specification and open-issue record. An implementation handover should identify the source revision, constraints and supporting reports. A manufacturing release should name the required evidence and authorization. The appropriate details vary by engagement, but the principle is consistent: progress should be observable and reviewable. If an exception is accepted, preserve its scope and approval so later teams understand the intended limitation rather than rediscovering it as an unexplained inconsistency.

Manage changes without losing context

Requirements and technical assumptions can evolve. Define how a proposed change is evaluated for engineering, verification, schedule and commercial impact. Keep the approved decision connected to the affected design and documentation revisions. This avoids treating an informal conversation as a replacement for the source of truth. An escalation path is useful when teams disagree or when a supplier dependency affects several activities. Good coordination does not mean avoiding difficult findings; it means bringing them to the right decision-makers with enough evidence to choose a practical next step.

Review ownership and continuing support

Clarify the rights and deliverables associated with source data, licensed IP, models and production information. Identify what the customer will need to maintain or revise the product later. Ask how errata, personnel changes, tool dependencies and supplier changes are handled. Current program participation or a certificate can support an evaluation, but its actual scope should be checked rather than assumed. A strong engagement leaves the customer with an understandable engineering record and a clear support path, in addition to the immediate deliverables described in the proposal.

A practical cross-discipline review

Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.

Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.

Explore the related Avnet offering or discuss your project requirements.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →