Skip to content

Work order lifecycle

SolarSENS Work Orders provide operations teams with a shared framework to track operational issues from intake through resolution. The status model clearly distinguishes active field execution from retained historical records without unnecessary approval overhead.

Overview

Section titled “Overview”

A work order’s status indicates its readiness for action and operational ownership. Active display status is derived directly from assignment: open work displays as New when unassigned and Assigned once an owner is designated.

flowchart LR
    P["Pending draft"]
    N["New"]
    A["Assigned"]
    R["Resolved"]
    H["Archived"]

    N -->|Assign| A
    A -->|Clear assignee| N
    N -->|Resolve| R
    A -->|Resolve| R
    N -->|Archive| H
    A -->|Archive| H
    R -->|Archive| H
    H -->|Unarchive| N
    H -.->|If prior display status was Assigned| A

Pending is handled separately because drafts saved before official submission do not participate in active operational dispatch.

Why it matters

Section titled “Why it matters”

Each status answers a distinct operational question:

  • New — What needs ownership? Unassigned work is visible across the team queue, highlighting unaddressed findings.
  • Assigned — Who owns this? Makes technician or contractor accountability explicit for scheduling and follow-up.
  • Resolved — Is the issue fixed? Formally records completion and captures outage duration, man-hours, and final evidence.
  • Archived — Where is the record? Removes completed tickets from active lists while keeping all history, attachments, and timestamps fully searchable.

This standardized status progression underpins portfolio analytics, including team turnaround time, backlog aging, and potential energy loss.

How it works in SolarSENS

Section titled “How it works in SolarSENS”

Active work states

Section titled “Active work states”
  • New: The ticket is open, validated, and awaiting an assigned technician or contractor.
  • Assigned: The ticket has an active owner responsible for execution. Clearing the assignee returns the ticket to New.
  • Resolved: Field or remote intervention is complete. Resolved work orders lock further edits and attachments, remaining searchable until archived.

Draft records

Section titled “Draft records”

Archiving and active-queue restoration

Section titled “Archiving and active-queue restoration”

Archiving removes records from default list views while retaining all underlying telemetry timestamps and attached files. When a ticket is unarchived:

  • If the ticket was in Assigned status immediately prior to archiving, it restores to Assigned.
  • Otherwise, it restores to New.
  • A previously resolved ticket unarchives into active status (Assigned or New) for renewed execution rather than returning to Resolved.
Section titled “Related concepts”