Roadmap
Actively developed. Honestly labelled.
Amberhold grows by what running plants prove they need — not by feature checklists. Three states, no spin: live means live in production; in development means being built right now; on the road means sequenced, and re-sequenced when real sites show us better.
Live today
- ✓Guided operator rounds with expected bands, previous readings and trends
- ✓Scheduling, due windows, and an overdue/missed board that tells the truth
- ✓Temporary controls: declared, a check is scheduled each shift, cleared by a recorded act
- ✓Equipment register and plant model, built in your site's own words
- ✓QR and NFC identity tags — a tag identifies, never authenticates
- ✓Append-only evidence with attributable entries and honest skips
- ✓Evidence export from inside the product: the complete site record as a ZIP, its manifest stating exactly what is and isn't included, every run audited
- ✓Governed, versioned round definitions with an immutable audit trail
- ✓Role-based access, time-boxed guest membership, next-request leaver revocation
- ✓Single sign-on with Microsoft Entra ID — signing in never grants access on its own
- ✓Read-only Readings API and CSV export — one versioned projection for your own reporting and dashboards
- ✓Microsoft Teams operational notifications, delivered periodically after evidence reaches Amberhold — not alarms or a safety system; your plant's alarms are unchanged
On the road
- →Starting a round, and checking its tags, when there is no signal at all. Today a walk that loses signal keeps its readings, findings and photographs on the phone and sends them itself when signal returns, while Amberhold is open, with the times they were captured; starting a round needs a connection. We will describe it here once it has been proven on a real plant.
- →Specialist registers — lifting equipment, PRVs, gas detectors, emergency showers
The long-term vision
- ◦Routines: recurring non-round work — duty swaps, fire-pump tests, valve exercising
- ◦Controlled documents linked to the plant model
- ◦Plant reconciliation at scale: every description of your plant, reconciled into one governed model — proposals ranked by real operational evidence
- ◦Working alongside your CMMS — SAP-aware vocabulary, never SAP-lite
States reviewed with each release. Nothing here is a contractual commitment — sequencing follows the evidence from live sites, which is the whole philosophy.