PHASE 06 ยท PROTOTYPE

Prototype build.
From design files to units on your desk.

You arrive with design files. You leave with working prototypes: built, brought up, debugged and measured, with a clear list of what to change in the next revision.

Henrik Andersen development loop: enter anywhere, stay as long as you need, exit anytime

At a glance.

You bring
  • Schematic and PCB files
  • Firmware or a test image
  • A target quantity
  • Or prototypes that do not work yet
I do
  • Fabrication and assembly
  • Board bring-up
  • Debugging and root cause
  • Functional tests
You get
  • Working prototypes
  • Bring-up and test report
  • Change list for rev. B
  • Updated design files

What is included.

Ten building blocks. Take them all, or just the ones you need.

HOW CHANGES ARE CONTROLLED

Configuration and change management.

Schematics, PCB revisions, BOMs, firmware, software and test assets are kept mutually consistent. Every change runs through an engineering change order, so you always know which versions belong together.

Configuration and change management. Left: six configuration items, schematic, PCB, BOM, firmware, software and test assets, shown in baseline 1.0 and baseline 1.1. An approved engineering change order, ECO-012, moves the schematic and PCB from revision B to C, the BOM from B.3 to C.1, the firmware from 1.3.0 to 1.4.0 and the test assets from TS-1.2 to TS-1.3, while the software stays at 2.1.0. Below: the change flow, request, impact, approve ECO, implement, verify and release. Principles: single source of truth, no silent changes, impact checked, full history. Right: the typical outputs, versioned baselines, engineering change orders and compatibility records.

HOW DEFECTS ARE CLOSED

Defect management and field feedback.

Every failure, from the bench, the production line or the field, is tracked to its root cause, and the corrective action is verified before the defect is closed.

Defect management and field feedback. Top: the closed loop for every defect from the bench, the line and the field: report, triage, root cause, fix, verify, close, with lessons fed back into design rules and tests. Left: an example defect record, DEF-027, major, closed: source a field return of 3 units; symptom the unit resets when the motor starts; root cause the supply dips below the brown-out level because the bulk capacitor is too small; corrective action a larger bulk capacitor and an adjusted brown-out level under ECO-018; verified by regression test RT-112 with no resets in 48 hours. Right: an example chart of open defects per week, rising to 9 in week 3 and falling to 0 before release, closed only after verification. Principles: every failure logged, root cause not symptom, fix verified, lessons fed back. Right: the typical outputs, defect records, root-cause reports, corrective actions and regression tests.

What you get.

Prototypes Assembled, tested units
Bring-up report Power, clocks, interfaces
Measurements Current, signals, thermal
Issue list Root cause and fix
Rev. B changes Schematic and layout updates
Test report Functional results
Duration

Agreed in your proposal

Enter with

Schematic and PCB files

Exit with

Working units

Payment

After your approval

Where to next.

Continue with me through the next phases to start of production, or leave with what you came for.

CONTACT

Ready to start at phase 06?
Or hand over the complete development? Just ask.

A new product to develop from scratch, a design that needs a second look, or a prototype that does not work yet: a few lines are enough to start.

  • A personal reply within one working day
  • No cost and no commitment up front: you only pay for work you approve
  • Your idea stays confidential, NDA on request (how I keep your project confidential)

Write to me

info@siliconmeetscode.com
Write an email

Helpful to mention: what the product does, where it is today, and your timeline. The email opens with these questions ready to fill in.

Working from Belgium and Germany with clients across Europe and Asia