In this article
Structured engineering advice for decisions in an ASIC program. It can address technical feasibility, architecture, IP selection, implementation risks, production strategy or project planning.
Consulting should resolve a decision
ASIC consulting is most useful when it answers a specific engineering or program question. Examples include whether a workload justifies custom silicon, which process options are feasible, or whether a design is ready for a physical implementation handover. Define the decision, the available evidence and the required output before starting. A report that repeats general semiconductor terminology is less useful than one that identifies assumptions, evaluates alternatives and explains what additional evidence would change the recommendation. The scope can be short and focused or part of a larger development engagement.
Start with the system problem
Bring the product requirements, expected volumes, power envelope, interfaces and lifecycle expectations into the review. A chip-level optimization can be unattractive once software, packaging, cooling or board changes are included. The consultant should ask which limits are firm and which are negotiable. For an early product, a programmable solution may preserve valuable flexibility. For a stable high-volume workload, an ASIC may offer a stronger case. These are scenarios to analyze, not automatic conclusions attached to a particular customer size or industry.
Make the analysis reproducible
A feasibility review should record the inputs and explain the reasoning behind its estimates. If area depends on a preliminary RTL model, say so. If a schedule assumes available IP and an established package, identify those dependencies. Distinguish a measured result from an engineering estimate and a supplier quotation. This makes the output usable when the design changes or a second reviewer joins. It also helps the customer compare alternatives without treating numbers produced under different assumptions as directly equivalent.
Convert recommendations into ownership
The end of a consulting assignment should leave clear next steps. A recommendation to perform a power study needs an owner, representative workloads and an acceptance question. A concern about an IP block needs an evaluation plan. A suggested manufacturing route needs confirmation from the appropriate supplier. Group issues by impact and urgency, and record unresolved items without disguising them as completed work. A practical review reduces uncertainty in a way the engineering and business teams can act on together.
Questions about consulting scope
Can consulting begin before the specification is complete?
Yes. Early work can help define the specification and identify the most important unknowns. Its conclusions should reflect the limited maturity of the available inputs.
Does a feasibility study replace detailed design verification?
No. Feasibility establishes whether a proposed approach is plausible under stated assumptions. Verification, implementation sign-off and silicon characterization provide different evidence later in the development lifecycle.
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.
