Assign site work, set deadlines and track progress from open to completed.
Actions turns an observation into work that someone owns. In asset-monitoring mode, actions are organized around sites. An action can follow an alarm, a performance investigation or planned work.
There are two places to organize follow-up. They serve different purposes and should not be treated as one automatically synchronized task list.
| Place | Use it for | Ownership and completion |
|---|---|---|
| Alarm management: incident follow-up and follow-up tasks | Record who is investigating an incident, discuss the evidence, and set a later reminder. | Claim the incident with I'll handle this. A follow-up task has its own owner and reminder time, and remains open when its associated alarm recovers. |
| Actions: Action board and Agenda | Plan site work with an assignee, priority, deadline, optional planned visit and discussion. | Assign an authorized person and move the work through Open, Planned, In progress and Done. Finishing the work does not itself establish alarm recovery. |
For example, an operator may claim the inverter incident in Alarm management and create a reminder to recheck fresh production tomorrow. If a technician's visit also needs planning, create a separate action in Actions, select the site, and include the affected inverter and observation period in its description. Record enough context for the technician to find the same measurements.
Creating an incident follow-up task does not automatically create an Action board card. Likewise, assigning a board action does not automatically claim the incident. Some alarm workflows provide a direct action control; use an existing link when one is present, but do not assume that independently created records are linked or will close together.
For recurring work across several installations, use the multiple-sites/template workflow. Check the selected scope before creating the actions so unrelated sites do not receive the same task.
Link an action to a site, assign an owner and set its priority and deadline. Save after completing the required fields. Fictional demonstration data.
Use the board to review actions by progress. Use the agenda for deadline-oriented follow-up. Search and filter by site, person, priority or category. The assigned-to-me summary helps focus on your own queue.
An estimated saving, if entered, is a planning estimate. It is not a measured recovery of lost production. Energy, financial and carbon estimates depend on their input factors and should not be read as verified performance results.
The fictional portfolio contains 12 example actions across several sites. These are a work-planning example, not an automatically generated copy of the 18 incidents in the alarm example. One investigation can require several tasks, while another can be resolved without a site visit.
The Action board groups the example work by progress. The account has 360 sites; the number of action cards is a separate count.
For a daily handover, filter by the responsible person and inspect Open and Planned work first. A useful card names the equipment and intended result, such as “Check the inverter connection and verify fresh production”, rather than just “PV alarm”. Use the description to state when the issue was observed and which comparison was made.
Move a card to Planned when its intervention is arranged and to In progress when the work starts. The status can be changed inside the action; the board also supports moving cards between columns. Keep the assignee and deadline current instead of creating a second card for the same work.
Open Agenda to review Visits and deadlines for the selected month. The same site, person, priority and category filters continue to determine which actions are shown.
The agenda lists dated work for the current selection. This example shows deadlines; a planned visit appears as its own dated entry when one is recorded.
A planned visit answers “When will someone attend the site?” A deadline answers “By when should this work be completed?” They need not be the same date, and an action with both can appear twice in the agenda. For example, plan a connection check on Thursday and set Friday as the deadline for confirming stable production.
After the visit, record the finding and the verification interval in the action discussion. Then revisit Alarm management and review fresh measurements. Complete the action when its work is finished, and separately complete any reminder task that no longer needs follow-up. Do not use a Done card as proof that an alarm is healthy, or disable a rule merely to make an unresolved problem disappear from the work queue.
Record what was found and what changed. Revisit the relevant chart or alarm after the intervention, then complete the action when the work is finished. Completing an action does not necessarily clear an ongoing alarm condition; the alarm reflects its measurements and rule.
Export the filtered action list when you need a working list outside the portal. If an action appears missing, clear filters and check the account before creating a duplicate.