# Resin EDA Technical Evaluation Brief

Schema: `technical-evaluation-v1`

Template version: `2026-07-13`

Record status: `Blank template`

Use this worksheet to define a focused evaluation before a demo or hands-on test. Do not include confidential design files, credentials, export-controlled data, or proprietary implementation details in the initial request.

## Dossier identity

- Organization:
- Evaluation ID:
- Project alias:
- Build or release reviewed:
- Evidence custodian:
- Decision owner:
- Supersedes record ID:

Use the same evaluation ID, project alias, build or release, and record references in the security, procurement, and handoff worksheets so the files form one review dossier.

## Evaluation owner

- Technical owner:
- Participants and roles:
- Target decision date:
- Current EDA tools and versions:

## Representative project

- Product or board category:
- Schematic sheet count:
- Component and unique-part counts:
- PCB layer, net, and footprint counts:
- Required source/import format:
- Required fabrication, assembly, BOM, drawing, or mechanical outputs:

## Task execution record

Before execution, complete the fixture or starting state, exact procedure or controls, expected observable result, and task-specific stop condition for every required task. Refine each planned criterion before execution. Leave the executed build, observed result, evidence reference, issue IDs, owner, and review date blank until reviewed; every disposition starts as Pending.

| Task ID | Task | Fixture or starting state | Exact procedure or controls | Planned criterion | Expected observable result | Task-specific stop condition | Executed build or revision | Observed result | Evidence reference | Issue IDs | Owner | Disposition | Review date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| T01 | Create or import a project | | | Open the agreed source project and account for importer messages, dependencies, object counts, and fidelity checks against the approved baseline. | | | | | | | | Pending | |
| T02 | Edit hierarchical schematic content | | | Complete the agreed connectivity and hierarchy edit, then verify the intended electrical result against the planned change. | | | | | | | | Pending | |
| T03 | Create or qualify a component record | | | Verify manufacturer and part identity, required managed fields, ratings, lifecycle or sourcing basis, and the approved symbol and footprint associations. | | | | | | | | Pending | |
| T03S | Create or qualify a symbol | | | Verify symbol identity, units, graphics, pin names, numbers, electrical types, hidden state, and component association against the approved source. | | | | | | | | Pending | |
| T03F | Create or qualify a footprint | | | Verify footprint identity, pad numbers and geometry, drill and layer definitions, courtyard and assembly data, pin-to-pad mapping, and model association against the approved source. | | | | | | | | Pending | |
| T04 | Synchronize schematic and PCB data | | | Transfer the approved design change and account for every expected addition, removal, and mismatch before accepting the synchronized state. | | | | | | | | Pending | |
| T05 | Place, route, and edit board objects | | | Complete the representative placement, routing, and geometry edits under the agreed layer, clearance, and constraint conditions. | | | | | | | | Pending | |
| T06 | Configure and run ERC | | | Run the agreed schematic check scope, retain the rule and waiver context, inspect every finding, correct one controlled electrical issue, rerun, and reconcile the row-level result change. | | | | | | | | Pending | |
| T06D | Configure and run DRC | | | Run the agreed board check scope, retain the rule, layer, and waiver context, inspect every finding, correct one controlled physical issue, rerun, and reconcile the row-level result change. | | | | | | | | Pending | |
| T07 | Review changes, comments, or project history | | | Create the agreed review handoff and demonstrate that reviewers can identify the evaluated revision, changes, comments, dispositions, and retained history. | | | | | | | | Pending | |
| T08 | Use an AI-assisted task and inspect the result | | | Run one bounded engineering task, inspect its available sources and reasoning, and independently verify the result before disposition. | | | | | | | | Pending | |
| T09 | Generate and inspect required outputs | | | Generate every required fabrication, assembly, BOM, drawing, or mechanical output and inspect each file in its named receiving tool. | | | | | | | | Pending | |

## Issue register

Reference these stable IDs from the task records. Leave execution and evidence fields blank until an issue is observed; severity and disposition remain Pending until reviewed.

| Issue ID | Related task IDs | Issue summary | Severity | Observed build or revision | Evidence reference | Decision impact | Owner | Disposition | Review date | Closure evidence |
|---|---|---|---|---|---|---|---|---|---|---|
| TE-I01 | | | Pending | | | | | Pending | | |
| TE-I02 | | | Pending | | | | | Pending | | |
| TE-I03 | | | Pending | | | | | Pending | | |
| TE-I04 | | | Pending | | | | | Pending | | |
| TE-I05 | | | Pending | | | | | Pending | | |
| TE-I06 | | | Pending | | | | | Pending | | |
| TE-I07 | | | Pending | | | | | Pending | | |
| TE-I08 | | | Pending | | | | | Pending | | |
| TE-I09 | | | Pending | | | | | Pending | | |
| TE-I10 | | | Pending | | | | | Pending | | |

## Acceptance criteria

A criterion passes only when the named owner accepts the retained evidence. Conditional results need a dated closure action; a workaround is not a pass unless it was explicitly allowed in advance. Leave evidence and owner fields blank until reviewed; every decision starts as Pending.

| Criterion | Minimum passing condition | Evidence or artifact | Pass/fail owner | Decision |
|---|---|---|---|---|
| Import fidelity | Required sheets, connectivity, identities, geometry, rules, and dependencies match the approved source baseline. | | | Pending |
| Editing completeness | The team completes the agreed schematic and PCB edits without an undocumented workaround. | | | Pending |
| Check behavior | Configured checks run, findings identify useful design context, and the controlled correction is reflected in a rerun. | | | Pending |
| Output usability | Every required output opens in the named receiving tool and passes the receiver's inspection checklist. | | | Pending |
| Review traceability | The retained record connects the evaluated revision, reviewer disposition, and final decision. | | | Pending |
| Operational fit | The representative browser, network, access, and collaboration environment completes the agreed workflow. | | | Pending |

### Decision rules

- Overall pass rule:
- Stop conditions:
- Pre-approved workarounds:
- Limits on the conclusion:

## Evidence package register

Retain enough material for someone outside the session to audit the result. Keep exact files, settings, counts, exceptions, and receiver results in an approved location. Leave storage and owner fields blank until assigned.

| Package item | Required contents | Storage location or record ID | Artifact owner |
|---|---|---|---|
| Input baseline | Immutable source archive, source-tool version, dependency inventory, checksum, and expected object counts. | | |
| Session record | Dated notes, evaluated Resin revision or environment, settings, warnings, and deviations from the plan. | | |
| Task evidence | Screenshots or short recordings that show the input, action, observable result, and relevant product state. | | |
| Comparison data | Before-and-after counts, connectivity or geometry comparisons, check results, and exception dispositions. | | |
| Generated outputs | Exact evaluated files, generation settings, checksum manifest, and receiving-tool inspection results. | | |
| Decision record | Criterion-level pass/fail decisions, open risks, named approvers, follow-up owner, and target date. | | |

## Owner questions requiring a written response

The public site does not answer these questions. Keep written answers, owner/source details, versions, dates, inspected evidence, and controlling-record references blank until authorized material is received. Response progress and evaluator disposition start as Pending.

| Topic to confirm | Required answer | Response progress | Authorized owner and source | Written answer | Source or document version | Answer date | Evidence inspected | Evaluator disposition | Controlling security or procurement record |
|---|---|---|---|---|---|---|---|---|---|
| Security assurance | Certifications, independent audits, report availability, and customer review process. | Pending | | | | | | Pending | |
| Infrastructure | Hosting providers, tenant architecture, encryption details, key management, and processing regions. | Pending | | | | | | Pending | |
| Identity and access | Enterprise identity, provisioning, role guarantees, access reviews, and administrative audit history. | Pending | | | | | | Pending | |
| Resilience | Backup scope, recovery objectives, incident commitments, service levels, and status communication. | Pending | | | | | | Pending | |
| Data lifecycle | Plan-specific retention, export completeness, deletion timing, backups, and account-closure behavior. | Pending | | | | | | Pending | |
| AI processing | Provider names, model-training use, provider retention, opt-out controls, and regional processing. | Pending | | | | | | Pending | |
| Commercial terms | Plan entitlements, usage limits, pricing, support response, procurement terms, and contract precedence. | Pending | | | | | | Pending | |

## Questions and boundaries

- Formats and versions that must be tested:
- Objects or properties that must retain fidelity:
- Collaboration and permission requirements:
- Security, data, AI, and retention questions:
- Known workflow constraints:
- Follow-up evidence required after the session:

## Related review paths

Carry the completed technical record and its evidence into both owner-controlled reviews. Keep their outcomes Pending until the accountable reviewers approve them.

- [Security & Data Review](/new/resources/security-data-review) - page path: `/new/resources/security-data-review`; blank Markdown worksheet: `/marketing/commercial/security-data-review.md`
- [Procurement Review](/new/resources/procurement-review) - page path: `/new/resources/procurement-review`; blank Markdown worksheet: `/marketing/commercial/procurement-requirements.md`

## Final decision, approvals, and follow-up

- Overall technical decision: Pending
- Decision recorded on:
- Decision rationale:
- Blocking gaps or accepted limitations:
- Follow-up actions:
- Retest scope:
- Technical approver and date:
- Security or data approver and date:
- Commercial or procurement approver and date:
- Next review date: