Core records and entities

A work order is the main record for an operational issue. Attachments, optional subtasks, delete requests, and timeline events support that record without replacing it.

Overview

Use the work order to describe the issue, its ownership, timing, and impact. Add evidence and execution detail to its supporting records. Archive work when it should leave the active queue; delete it only when the complete record must be removed.

flowchart TD
    W[Work order] --> A[Attachments]
    W --> S[Optional subtasks]
    W --> T[Timeline events]
    W --> D[Delete request]
    D -->|Rejected with a reason| W
    D -->|Approved| X[Work order and dependent records removed]

What belongs where

Record	Use it for	Important boundary
Work order	The plant, issue, owner, priority, dates, status, and relevant shutdown details	It is the parent record for supporting work and history
Attachment	Images, PDFs, spreadsheets, and CSV files that support the work	Add them while work is active. Only administrators or supervisors can delete them, and not after resolution or archive
Optional subtask	A separately assigned piece of execution work with its own title, due date, and state	Subtasks stay ordered under the parent work order and are not enabled in every deployment
Delete request	A request to remove a work order when the requester does not have direct-delete access	Approval removes the work order and its dependent records; rejection requires a reason
Timeline	A supplementary history of work-order activity	It is available only while the parent work order exists and may not capture every event

How the records work together

The work order carries the operational context: plant, subject, description, area, category, priority, requester, assignee, dates, status, and shutdown-related details where relevant. SolarSENS manages requester identity and record identifiers.

Affected-device information belongs to shutdown context rather than a separate general device field. Keep the main record focused on the operational issue, then add supporting evidence or execution detail to the related record.

The timeline can record creation, assignment, resolution, archive, updates, shutdown changes, subtasks, attachments, and delete actions. Use it as useful context for the record, not as a complete event audit.

Archive and deletion

Action	What happens	When it is the right choice
Archive	The work order leaves the active queue but remains available with its history and supporting detail	The work is complete or no longer active, but may need later reference
Delete	The work order and its dependent records are removed. Its detail and timeline are no longer available	The record must be removed entirely and the scope is understood