Core records and entities
WorkOrder V3 is more than a single ticket record. It is a small operational system made up of the main work order and a set of supporting records that capture execution detail, review activity, evidence, and history.
Overview
Section titled “Overview”Understanding the core records helps teams use WorkOrder V3 consistently. It explains where to put the main issue description, where to store evidence, how to break work into smaller actions, and where to look when someone asks what happened.
Why it matters
Section titled “Why it matters”- It keeps the primary work order readable instead of overloaded with every detail.
- It makes review easier because evidence and supporting tasks are attached to the same record.
- It preserves an audit trail for closure, rework, archive, and deletion decisions.
- It gives managers better confidence in backlog and resolution reporting.
How it works in SolarSENS
Section titled “How it works in SolarSENS”Work order
Section titled “Work order”The work order is the main operational record. It usually carries the plant or asset context, subject, description, area, category, priority, requester, assignee, dates, status, and shutdown-related details where relevant.
This is the record operators, supervisors, and managers use to understand what happened, who owns it, and whether it is still open.
Subtasks
Section titled “Subtasks”Subtasks break a larger work order into smaller actions. They are useful when a single issue needs multiple checks, field steps, or handoffs before the main work can be resolved.
Each subtask can carry its own assignee, due date, order, and status.
Attachments and evidence
Section titled “Attachments and evidence”Attachments store the files that support execution and review. In practice, this is where teams keep photos, reports, screenshots, or other evidence needed to explain what was found and what was done.
Attachments strengthen closure quality because reviewers do not have to rely on notes alone.
Approval history
Section titled “Approval history”Approval records capture whether a resolved work order was approved or sent back as Action Needed, along with who reviewed it and when. This gives teams a formal record of closure decisions instead of relying on informal approval.
Delete requests
Section titled “Delete requests”Delete requests provide governance for removing work orders. Instead of deleting records immediately, teams can route deletion through a controlled review step.
Timeline and history
Section titled “Timeline and history”Timeline history records important lifecycle events such as creation, assignment changes, resolution, approval, archive, delete decisions, and attachment activity. It is the best place to answer questions like who changed this, when did it move, and why is it in this state now?