[ In progress ]
built-asset information management system
Design of the naming canon, the ETL, and the governance rules that turned a 317,633-element archive into an auditable base. Zero reliance on individuals to know what exists and where. Public sector, operational phase, ISO 19650-3.
- 317,633
- items inventoried
- 104,821
- redundant copies (MD5)
- 40
- dated snapshots over 89 days
- 1.26 TiB
- in a single personal bottleneck
context
A public-sector body that keeps the register of built assets: dozens of buildings across several campuses, and decades of documentation piled into a shared drive with no common grammar.
problem
Nobody could know with certainty, at any moment, what existed without asking a specific person. Knowledge lived in heads, not in the system, and every absence or change of staff opened a gap no one could measure.
decisions
-
Grammar before movement
No file moves until the naming convention exists in writing. Tidying without a grammar first only moves the mess somewhere else.
-
Space as the axis, topic as the shortcut
The atom is the built unit and the organisation follows real geography. Thematic views exist as links, never as copies.
-
Every action reversible and provable
Immutable snapshots and MD5 as proof. Nothing is deleted: it is moved. The diff between two states is the record: not anyone's memory.
-
Automation proposes, a person executes
Scripts generate the proposal and the log; destructive execution always passes through a human hand. In a public body that is not friction, it is control.
system
A closed loop: photograph the state, compare it to the previous one, decide on the difference, execute through a reviewed script, log the dated decision. Once a month, the harvest turns the log into documents: dossier, status, handover.
CAMPUS _ BUILDING _ TYPE _ DATE _ VERSION
outcome
Zero reliance on individuals to know what exists and where. The system documents itself: whoever arrives tomorrow reads the log, not my calendar.