Skip to content

Core records and entities

WorkOrder V3 is built around a main work order and supporting records for attachments, optional subtasks, delete requests, and timeline events.

These records keep the main issue readable, store evidence in the right place, and give teams a supplementary operational history alongside it.

  • The main record remains focused on the issue, owner, timing, and impact.
  • Attachments keep supporting evidence with the work.
  • Delete requests separate ordinary removal requests from destructive deletion.
  • Timeline events provide useful context while the record still exists.

The work order is the main operational record. It carries plant context, subject, description, area, category, priority, requester, assignee, dates, status, and shutdown-related details where relevant.

Requester identity and record identifiers are managed by the system. General device context is not a standalone main field; affected-device information belongs to shutdown context.

Attachments store supporting images, PDFs, spreadsheets, and CSV files. They can be added while work is active, subject to access and lifecycle constraints. Attachment deletion is an admin or supervisor action and is unavailable once the work is resolved or archived.

Subtasks carry a title, description, assignee, due date, and execution state, and stay ordered under the parent work order. Subtasks are an optional capability that is not enabled in every deployment.

Users without direct-delete access can create a pending delete request. Admin or supervisor users can approve or reject that request; rejection requires a reason. Approval or direct deletion removes the work order and its dependent records.

The timeline records creation, assignment, resolution, archive, updates, shutdown changes, subtasks, attachments, and delete actions. It is supplementary context and may not capture every event. It is available only while the parent work order exists; hard deletion removes access to both detail and timeline.