Ontomatoby UinoProgress69%Solutions / Operations
An asset list answers “what exists.” A connected model can describe where an asset operates, the work open against it, and the team responsible.
Sample content for this design. This resource is coming soon.
The question
Illustrative model design. This preview does not connect to live equipment, dispatch work orders, or predict failures.
Use one asset ID across the register, maintenance records and location data. Do not infer identity from a display name alone.
For a simple model: a work order is overdue when its due date is before the selected reporting date and its status is not closed. Agree on time zone and paused work separately.
Link Work order to Asset and Team, then Asset to Site. Preserve the source record for the status and due date.
| Include in the answer | Why it matters |
|---|---|
| Asset and work-order IDs | Identify the records to act on. |
| Due date and reporting date | Make the time boundary inspectable. |
| Assigned team and site | Route the question to the right people. |
| Source status | Avoid presenting closed work as outstanding. |
Fictional records and a fixed reporting date. Live asset data is coming soon.
Two open work orders match. Both belong to North Workshop and had a due date before 23 September. A closed work order is excluded.
| Work order | Asset | Due date | Owner |
|---|---|---|---|
| WO-018 | Pump P-07 | 2026-09-20 | Mechanical team |
| WO-026 | Motor M-12 | 2026-09-22 | Electrical team |
Due date < reporting date, status ≠ closed, site = North Workshop. No failure prediction or automatic work dispatch is implied.
Start with the working example. No account needed.
Illustrative model. A connected walkthrough will be available here.