EE-Platform: an engineering system of record
Context
Electrical design and documentation in the studio spanned CAD outputs, calculation notes, device data and correspondence. Those artefacts lived in folders that were understandable to the person who made them and opaque six months later. The platform was built as internal engineering software — see specialized software — not as a public product pitch. It remains listed under Work unless a client engages a scoped build.
Limits of this note
This write-up does not name a client, does not quote recovered hours, and does not claim a certification. It describes a studio-built store for equipment identity, documents and CAD-centric outputs. Engineers still worked in AutoCAD; the platform sat beside that session. Technical document automation meant classify and route with a human on exceptions, not an unsupervised sort presented as magic.
The useful outcome was visibility: missing keys instead of surprise mismatches on site, fewer unnamed copies of the same circuit, and a place to find the drawing that belonged to a calculation note. Jobs that did not use the platform kept their folder habits. That split is itself evidence that a system of record is a practice, not a slogan.
Neighbouring problems — bridging an analysis model to a single-line, or writing a tiny CAD utility — stayed neighbouring. Stuffing them into the platform would have recreated the weekly spreadsheet inside a larger box. The architecture choice was to keep those as separate tools with explicit mappings.
Problem
The same equipment identity appeared in a drawing, a schedule and a note with no join. Revisions were social: who had the latest file. Technical document automation (classify, route, human review) was a pile of mail. None of that is unusual. It becomes a problem when the cost of a silent mismatch is a wrong breaker or a stale single-line issued to site.
Approach
Treat identity as the first object: a device or circuit key that drawings, schedules and notes must cite. Keep CAD as the geometric authority; do not redraw the building inside a web form. Put documents on a path with a human on exceptions rather than a fully unsupervised sort. Prefer a system of record that engineers still open beside AutoCAD, not instead of it. Related thinking: internal utilities and when to automate.
Architecture
A structured store for equipment and document metadata; exporters toward AutoCAD-centric outputs; workflows for review. Integration with analysis tools is a neighbour problem, not the same component — see ETAP–AutoCAD bridge and connecting applications. No claim is made here about third-party certifications or hours recovered.
Outcome
The studio gained a place where a circuit’s documents and CAD outputs could be found without reconstructing a person’s folder habits. Mismatches became visible as missing keys rather than as surprises on site. The platform did not replace engineering judgement. It reduced the number of unnamed copies of the same object. Qualitative only: fewer “which file is true” conversations on the jobs that used it.