Clients
| Client | ID | Status | Created |
|---|
| Client | ID | Status | Created |
|---|
Create a client so their team can register with a code.
Team, wear materials, the plant hierarchy and the condition scale
| Name | Role |
|---|
| Name | Role | Status |
|---|
| Material | Code | Notes |
|---|
Register the wear materials your plates are made of.
Plant → Unit → Machine. A layout hangs off a machine; plates live inside the layout. A node can only be deleted once it is empty.
| Layout | Plates | Machine |
|---|
The condition scale both the panel and the mobile app render. Editing it here changes what an inspector sees on the next launch — no new app release, no redeploy. Listed from healthiest to worst; the order decides how a report sorts and which condition wins on a plate with several records.
Stored value is what is written on every inspection point, so it
cannot be renamed — a record already saved as replace would
stop resolving. Label, colour, meaning and order are yours to change.
| Condition | Stored value | Meaning | Last change |
|---|
Inspections cannot be labelled until the scale exists. Seed it with
migrations/006_condition_scale.sql, then reload this page.
From an empty plant to a printed report — who does what, and where
MVP traceability — web panel and Android app
Every requirement of the consolidated MVP list (11/08/2026), traced to what the web panel and the Android app do today. Sources: Kick Off [KO], post-PoC scope summary [ESC], initial requirements Rev.3 [REQ]. Where the documents disagree, [ESC] prevails.
No requirement matches this filter.
Upload a DXF file to process it and start annotating plates.
Share this registration code with the client's administrator. It is the only way their inspection and maintenance team can create accounts.