WorkOrder V3

WorkOrder V3 is the SolarSENS operational workspace for turning detected issues into accountable action. It helps teams move from alarm or inspection finding to assignment, tracked execution, review, and documented closure.

Overview

WorkOrder V3 is used when a plant issue cannot stop at monitoring alone. Once a team decides that an alarm, recurring defect, inspection finding, or service activity needs follow-up, WorkOrder becomes the system of action.

It is the workflow area that keeps issues from remaining as observations in dashboards, message threads, or spreadsheets. Teams use it to formalize ownership, capture execution detail, review outcomes, and maintain a usable historical record.

When to use this

Use WorkOrder V3 when teams need to:

• create structured work from alarms or operational findings
• assign responsibility to field or support teams
• track execution status across the work lifecycle
• capture notes, evidence, and shutdown context alongside the work
• review resolved work before treating it as complete
• preserve history for audit, reporting, and customer communication
• improve response discipline across multiple plants or portfolios

How the workflow area is organized

WorkOrder V3 is documented as a set of operational workflows so readers can go directly to the job they need to complete:

• Create and assign
• Resolve, review, and close
• Subtasks, attachments, and evidence
• Archive, delete, and history
• Dashboard and filters
• Work order details and permalink

Typical operating flow

1. An operator or supervisor identifies a condition that requires follow-up.
2. The team creates a work order with plant context, subject, priority, and ownership.
3. A supervisor or admin assigns the work to the responsible person or team.
4. The assigned team performs the work, adds evidence, and resolves the record.
5. A reviewer approves the outcome or returns it as Action Needed for rework.
6. The closed record remains available for history, reporting, and audit.

Stable concepts behind the workflow

If you are evaluating the process or aligning teams, start with these concept pages:

• Work order lifecycle
• Roles and permissions
• Core records and entities

What teams should track

• open work by priority and owner
• overdue actions and aging backlog
• repeat issues that generate repeated work
• work waiting for approval or rework
• closure quality, including notes, evidence, and final outcome

Expected outcomes

• faster handoff from monitoring to execution
• clearer accountability for each operational issue
• better visibility into status, aging, and backlog
• stronger reporting for customers and internal stakeholders

Operational notes

• WorkOrder V3 is intended to be read as a multi-page workflow area, not a single feature page.
• my-tasks can be mentioned as a beta convenience view, but it should not be treated as the primary operating model.
• Developer and API material is intentionally excluded from this section.

Next pages

• Start with Create and assign if you are setting up new work.
• Go to Resolve, review, and close if you are managing completion and approval.
• Use Dashboard and filters if you are monitoring backlog and portfolio trends.