Create and assign

Creating a work order turns an operational finding into tracked work. A useful record gives the receiving team enough plant, issue, timing, and impact context to act without unnecessary follow-up.

Overview

Use this workflow for an inspection finding, recurring issue, service activity, or customer request that needs formal ownership and execution tracking. Creation is available when you have permission to create work for the selected plant.

When to use this

an operator finds a defect or trend that needs intervention
a supervisor formalizes work discovered during review or reporting
a service activity needs clear priority, timing, and ownership
a customer request needs a traceable operational response

Step-by-step workflow

Select the plant.
Enter a clear subject and description.
Choose the area, category, and priority.
Confirm the requester shown by the system. It comes from the signed-in account and is not freely selected.
Add start, due, or end dates where they help plan the work.
Add relevant attachments.
Record shutdown context when the work affects a plant, inverter, string, or availability calculation.
Select an assignee if ownership is already known, then save the work order.

An open work order without an assignee is shown as New. Selecting an assignee changes it to Assigned; clearing the assignee returns open work to New.

💡 Writing a good description — include enough context that another team can act without chasing you. What did you find? Where exactly? When did it start? What have you tried so far? A description like “Inverter 3 showing fault since 09:00, tried remote restart, no change” is far more useful than “Inverter 3 fault.”

Save Draft limitation

⚠️ Save Draft creates a work order shown as Pending. The current interface does not expose a visible action for moving it into the normal active workflow, and pending work cannot be assigned, resolved, or archived through those controls. Use this option only when you must retain incomplete input — and plan to re-create the record properly later.

Expected outcomes

the issue has a structured record and stable reference
plant, scope, priority, and timing are clear
ownership is visible when an assignee is selected
the work is ready for execution updates and evidence

Caveats and operational notes

Required creation fields include plant, subject, area, category, and priority.
Keep the subject and description specific enough for another team to act.
Assignment availability is permission-dependent; it is not universally a management-only action.
A general device field is not part of the main record. Add affected-device information within shutdown context when relevant.
WorkOrder V3 does not create work orders from an alarm screen; create the record here and carry the alarm context into the description.