Home/Glossary/ASIC Design Services
Semiconductor knowledge

ASIC Design Services

A descriptive phrase for ASIC engineering that introduces a useful architecture, circuit technique or implementation approach. Innovation should be tied to a demonstrated project benefit rather than novelty alone.

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

A descriptive phrase for ASIC engineering that introduces a useful architecture, circuit technique or implementation approach. Innovation should be tied to a demonstrated project benefit rather than novelty alone.

An iterative ASIC development flow
Reviews and feedback connect the stages. This conceptual flow is not a fixed project schedule.

Define the service entry point

ASIC design services help translate product requirements into a custom integrated circuit. The engagement can begin with an application concept, an architecture, RTL or an existing netlist. These starting points require different work and different evidence. A proposal should identify the actual entry point and the state of the supplied material. A customer-provided RTL package may still need integration or verification work before physical implementation can begin. Clear acceptance criteria prevent a nominally narrow service from acquiring hidden responsibilities late in the schedule.

Connect engineering disciplines

Architecture, RTL development, verification, physical design and product engineering influence one another. Interface selection can affect package cost; a power target can change memory architecture; manufacturing test can require additional logic and pins. A useful design-services plan connects these disciplines instead of presenting a list of isolated tasks. Define the technical lead, review cadence and escalation path. The customer should know how a design decision is approved and how its consequences are reflected in the specification, schedule and downstream deliverables.

Ask for observable milestones

Milestones should describe evidence rather than elapsed effort. Examples include an approved architecture, a reviewed verification plan, a controlled implementation handover and a sign-off package. Each milestone should identify its inputs, outputs and unresolved items. Avoid treating a percentage-complete figure as sufficient evidence of readiness. A design can contain most of its source code while lacking critical error-handling behavior or implementation constraints. Agree what must be demonstrated before the next stage begins, including how exceptions are reviewed and who can accept them.

Prepare a productive project enquiry

Provide the application, major functions, interfaces, power and performance goals, expected production profile and intended lifetime. Identify existing source code, IP commitments and technology preferences. If some information is uncertain, state the range and the decision it affects. This enables an engineering discussion about feasibility and scope rather than a superficial price comparison. Avnet's ASIC design services page and RFQ form provide routes for discussing its published offering; specific capabilities, deliverables and commercial terms should be confirmed for the individual project.

Questions about design services

Can a service provider work from customer RTL?

Yes, when that entry point is included in the engagement and the handover meets the agreed requirements. The provider must still review constraints, IP, verification status and integration assumptions.

Does a design-services quotation include manufacturing?

Only if that scope is stated. Design, masks, wafer fabrication, packaging, test and ongoing supply can be contracted in different ways, so they should be listed explicitly.

Requirements that can be checked

Turn each important behavior into a requirement with an observable result. Describe valid inputs, invalid inputs, ordering rules, throughput expectations and the response to interrupted transactions. Identify which clocks and resets are involved. A good review asks whether another engineer could write an independent test from the description. Where the answer is unclear, improve the requirement before adding more implementation detail. Keep assumptions about the surrounding system visible, including how long an interface can stall and whether input data can arrive while a block is unavailable. These details determine whether the implementation and its test environment are solving the same problem.

Verification across normal and unusual operation

Check ordinary workloads alongside stressful combinations of events. Reset during activity, a full queue, simultaneous requests and an error response can expose behavior that an ideal sequence misses. Use appropriate simulation, assertions or formal methods for the properties being examined. Preserve reproducible inputs and expected results. If a check is excluded, record why and who reviewed the decision. Coverage helps organize evidence, but its interpretation depends on what the tests actually check. A regression that executes many cycles without observing meaningful outcomes can provide less confidence than a smaller set of well-targeted checks tied to requirements.

Implementation handover

The source design needs constraints, technology assumptions and integration context before a receiving team can use it reliably. Include the intended operating modes, clock relationships, IP versions and any known limitations. Check that source files, models and reports describe the same configuration. Define how changes are communicated while implementation is in progress. When physical results challenge an assumption, route the finding back to the responsible architecture or logic owner. A controlled handover keeps the project from optimizing an obsolete version or interpreting an undocumented exception as an intentional requirement.

Evidence for the next decision

Separate predicted results from measured behavior and state the conditions behind both. An early synthesis estimate can support architecture exploration, but it is not equivalent to a final implemented result. A prototype can support software integration without proving final ASIC timing. Before a release, identify the evidence required for the particular stage and list unresolved issues with owners. Preserve the approved revision and enough context to reproduce the relevant checks. This makes later debugging, engineering changes and product maintenance more efficient than relying on a single successful run whose inputs are no longer clear.

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 →