Work

Case study · In progress

Calibration System

Rebuilding a calibration lab's core system: from a decade-old Access database, to Power Apps, to a custom web app.

  • React
  • TypeScript
  • PostgreSQL
  • Resend
  • 10+ years on the old system
  • 3 platforms, one system
  • ISO 17025 audit-ready records

My role

Designed the data model and interface, and building the system end to end.

The journey

Three versions, each fixing the last

  1. Before · Microsoft Access

    The legacy system

    An Access database that had run the lab for over ten years. Equipment was sorted by fixed text categories, and much of the logic depended on those exact strings.

  2. Interim · Power Apps

    Into the cloud, fast

    A model-driven Power App got the data out of Access quickly. But screens had to follow the platform's layouts, and anything custom meant building complex PCF controls.

  3. Now · Custom web app

    Built around the technicians

    React and TypeScript on PostgreSQL. Full control over the interface, so screens follow how technicians actually work.

Highlights

What the rebuild made possible

Every reading checked, not the average

Torque worksheets follow ISO 6789: each reading is checked against its permitted error, so one bad reading can't hide in a good average.

Share of permitted error used, per reading Example
  • Reading 1 Pass
  • Reading 2 Pass
  • Reading 3 Fail
  • Reading 4 Pass
  • Reading 5 Pass

The average looks fine, but reading 3 is outside its limit, so this tool doesn't pass.

Categories as data, not text

Around 20 text categories became proper types like Torque and Pressure. New equipment is now a data change, not a code change.

Email that doesn't depend on Microsoft

Invites, resets and certificates send from the company's own verified domain, ready for a Microsoft Graph link-up later.

What's next

Still building

  • More worksheet types beyond torque
  • Two-way email with Microsoft Graph
  • Moving the rest off Power Apps