Work Orders
Graph-connected maintenance and operational tasks.
Every work order is a node in the knowledge graph, connected to the asset it concerns and through that asset to sensor data, maintenance history, and documents. All of that context is one hop away.
When you type @digel in a work order comment, the agent already knows which machine, what the history is, and what documents are linked. It reads the graph edges from the issue.
The human approval step
Issues move through statuses (triage, backlog, in progress, completed, canceled), but the important transition is from triage to backlog. That is where an agent-proposed finding becomes real work that a person has committed to.
Field use
Every machine has a QR code. Scan it to jump directly to that machine's open issues and context. The interface is designed for the floor.