English
Team and reports
Team
The member list with workload and roles.
| Shown | What it holds |
|---|---|
| Members | Who is on this team |
| Workload | How much work is currently assigned |
| Role | Their authority in Opsira |
| Presence | Online, on site, away, or offline |
Read workload before assigning, not after
This screen is most useful while assigning new work — to see who still has room.
Opened after everything has been handed out, it only tells you that one person is already overloaded.
Reports
Results against operational targets.
| Shown | Answers |
|---|---|
| Progress against target | Are we on plan |
| Work completed | How much finished in this period |
| Work distribution | Which stage it is piling up in |
| Equipment condition | How much is operational, due for repair, faulty |
Exporting
Project Managers and Ops Admins can export reports. Planners and Viewers can only read them on screen.
Reading reports honestly
A lot of "completed" work is not necessarily good news
A rise in completed work can mean the team is working better — or that work is being split into smaller pieces, so the count rises without the output rising.
Read it alongside stage distribution and equipment condition. If completed work rises while faulty equipment also rises, what is happening is not progress.
Three questions worth asking every month:
Is the "in review" column growing? If so, the bottleneck is in checking, not in doing.
Does the same equipment keep reappearing in repair history? If so, repeatedly repairing it may cost more than replacing it.
Is workload concentrated on one or two people? If so, the team's results report is hiding a risk: one person leaving would stop a great deal.

