Technical starting point
Device models, geometry, test conditions and measured curves.
DEVICE ENGINEERING
Evaluate device characteristics against the intended operating envelope.
Discuss your requirements
Representative photograph · Cleanroom technician inspecting a sample through a microscope.
THE ENGINEERING SCOPE
Device models, geometry, test conditions and measured curves.
Bias conditions, extraction assumptions, temperature and repeatability.
Characterisation results, model comparisons and operating-range notes.
CLIENT GUIDE
Use these technical checkpoints to make the first project review productive.
HOW WE WORK
The initial review establishes the baseline using device models, geometry, test conditions and measured curves. Record gaps and dependencies before implementation.
Carry out the agreed work against the reviewed baseline. For device engineering, keep the interfaces and configuration used by this stage visible to the receiving team.
Retain the intermediate artifacts and review bias conditions, extraction assumptions, temperature and repeatability. Investigate failures before using these results as an input to the next stage.
Package characterisation results, model comparisons and operating-range notes. Review unresolved findings against the agreed acceptance criteria and assign ownership for follow-up.
PROJECT DECISIONS
Use these gates to agree readiness, review evidence and responsibility at each stage.
Are the starting inputs complete enough to proceed?
Device models, geometry, test conditions and measured curves.
Record input revisions, missing material and who can resolve each dependency.
Has the work addressed the agreed technical objective?
Evaluate device characteristics against the intended operating envelope.
Keep the intermediate artifacts with review comments and the decisions that changed the design.
Can the result be reproduced and interpreted?
Bias conditions, extraction assumptions, temperature and repeatability.
Capture the configuration, expected result, observed result and unresolved findings.
Can the receiving team use the delivery package?
Characterisation results, model comparisons and operating-range notes.
Review build or execution instructions, known limitations and ownership of follow-up actions.
INPUTS & OUTPUTS
The final statement of work defines the scope and acceptance criteria.
TECHNICAL DECISIONS
Evaluate device characteristics against the intended operating envelope.
The work starts from device models, geometry, test conditions and measured curves. The team should identify the authoritative revision of each input and record any assumptions needed to proceed. This prevents a later result from being interpreted against a different specification or configuration.
Published device conclusions should retain their measurement and modelling conditions.
The review centres on bias conditions, extraction assumptions, temperature and repeatability. Each finding should identify the input revision, observed behaviour and supporting evidence. Distinguish a confirmed defect from a configuration issue, an unsupported case or an open engineering question before deciding how to resolve it.
The practical sequence is: define characterisation; compare models and measurements; examine variation; document usable limits. Intermediate reviews allow the client to resolve decisions while changes are still manageable. If an input changes, identify the affected activities and repeat the checks that depend on it.
The expected package comprises characterisation results, model comparisons and operating-range notes. Acceptance criteria should specify what the receiving team needs to reproduce, inspect or integrate these artifacts. Include known limitations and outstanding actions in that package, rather than assuming that delivery of a file implies acceptance.
Analog results depend on operating conditions and modelling assumptions. Establish supply ranges, loading, bias conditions, temperature and the selected process models before comparing simulations. Identify which requirements concern nominal performance and which concern variation, startup, noise or stability. The intended use of each result should be clear: an exploratory sweep and a release check have different evidence requirements.
Layout choices can change the circuit through parasitics, coupling and device environment. Review matching intent, sensitive nodes, return paths, guard structures and routing symmetry with the circuit owner. A geometrically tidy layout is not necessarily an electrically suitable layout. Device placement and extraction results should be discussed together, especially when an observed shift is close to an acceptance limit.
When a model and a measurement disagree, first check units, configuration, instrument setup and the model’s range of validity. Use controlled sweeps to separate possible causes. Record solver settings, convergence concerns and any simplified boundary conditions. Circuit verification, layout verification and physical characterisation should retain their own acceptance criteria rather than allowing one successful check to stand in for all three.
A reference circuit may meet a nominal output target yet settle too slowly after a supply ramp. Review the ramp profile, load and initial conditions, then compare startup behaviour across the intended operating envelope. If extraction changes the result, identify the sensitive parasitic contribution before changing devices. This is a planning example and does not imply qualification of a specific technology.
BEFORE WE BEGIN
A clear conversation is the start of a strong engineering relationship.
The starting review needs device models, geometry, test conditions and measured curves. Share the current revision and known limitations so the scope reflects the actual design state.
The statement of work can define characterisation results, model comparisons and operating-range notes. The final package should include review results and any open actions.
Published device conclusions should retain their measurement and modelling conditions.
The first work package can be a review of the available inputs and the engineering questions that must be resolved. Agree its boundaries, access requirements and expected findings before committing to a larger implementation. A review should leave an actionable list of decisions, dependencies and next steps.
Tie each finding to the relevant revision and supporting evidence. A change should identify the affected interfaces, activities and checks. Confirm its effect on scope and delivery with the responsible owner. At handoff, distinguish closed findings, accepted limitations and open work so that a file transfer is not mistaken for technical acceptance.
PUT THE WORKFLOW IN CONTEXT
Practical reading to help prepare your project discussion. Studies are illustrative; they do not report client results.
What belongs in a turnkey IC-design project brief ↗YOUR NEXT CHAPTER STARTS HERE
Bring us your engineering challenge.
Let’s define the path from idea to implementation.