These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Power Plant Operations
- Features
- Sites and personnel
Sites and personnel
Keep plant locations and the people responsible for site work clear.
OverviewActive Sites×
Power Plant Operations · Sites and personnel
New
Active Sites
Sites
| Id | Site name | Location | Timezone | Status | |
|---|---|---|---|---|---|
| IDD-974 | Site 111 | X-8 | TMZ-901 | Active | |
| IDD-701 | Site 348 | L-1 | TMZ-804 | Active | |
| IDD-894 | Site 142 | X-20 | TMZ-819 | Active | |
| IDD-755 | Site 786 | G-23 | TMZ-616 | Active | |
| IDD-285 | Site 568 | R-6 | TMZ-412 | Active |
6 of 6 records
IDD-974Sites · STS-30250
ActiveSite nameSite 111
LocationX-8
TimezoneTMZ-901
What you can do
Sites and personnel in daily work
Start with a site record that the plant team can recognize. Its name, location and timezone identify where an event happened, where a meter is installed and where maintenance is due. An active site is available for current operations. A site in maintenance needs deliberate review before staff continue recording ordinary work there. The site record ties together events, meters, tasks and effective rates; people give tasks a named assignee rather than a free text owner.
Sites are the shared point of reference for the other modules. Keep each site name stable enough for shift teams and reviewers to recognize it. Record the local timezone before reviewing interval boundaries from different locations. Staff may have an active or inactive People record, and that record connects to a Users account. That connection matters when the manager checks which person has a task: a name alone cannot identify the linked account.
How the work is organized
- Site register. Give each location a recognizable name, timezone and operating state before staff attach events or meters.
- Personnel directory. Link each active person to the correct user account before assigning work.
- Cross-site check. Compare the task site with the event and meter site when several facilities have similar names.
What to agree during setup
- Site identity. Agree a name and location that distinguish facilities with similar labels; confirm which timezone operations use for day boundaries.
- People identity. Match each person to the right user account and keep inactive personnel out of new assignments.
- Operating state. Decide who can change a site between Active, Maintenance and Closed, and what the change means for open work.
Check the handoff on an actual case
The Operations Manager checks a task raised at the North Plant after a unit alarm. The task must point to that site and the intended person, so the manager and technician can identify the same assignment. Before treating a due task as complete, the manager checks its completion time and the site it was performed at. A similarly named person at another location should not inherit the assignment. The site remains the common reference when the manager reviews the event and the meter installed there. At handover, the Admin checks the People record against the correct Users account, then the Operations Manager checks the task assignee and site. If a staff member has left, mark that person Inactive and choose an active assignee for new work. Keep the earlier task record intact so the team can still understand who was responsible at the time.
What your team sees
- Active Sites — Sites ready for current plant records.
- My Personnel Record — The signed-in person’s identity and account link.
Follow the work through
See the related operating process and data model when agreeing who records each step.
What it keeps track of
Data model- Sites
- Generating sites and their operating status.
- People
- Plant personnel referenced by operational work and resolved to authenticated users.
- Users
- Users
Who uses it
Permissions- Admin
- , Operations Manager, Maintenance Technician.
Set up Power Plant Operations your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.