Operations
An event is only the start of the story.
Connect an alarm, its acknowledgement, the people investigating it, and the update everyone needs.
An alarm tells a team that something needs attention. It rarely tells the entire team what is happening next. Someone may already be looking at the system, another operator may be on site, and an administrator may still be trying to find out whether anyone has responded.
Nimrod brings system events and operator activity into the same operational context. The equipment event stays connected to the people investigating it and the information they share.
Start with the equipment event.
In the example, chilled-water supply temperature rises above its target. The event identifies the system that needs attention. Related dashboards give operators a way to inspect the current condition and its trend.
The readings and people in this storyboard are demonstration data. The sequence illustrates the relationship between the event and the response, rather than prescribing a cooling-plant troubleshooting procedure.
[ 06 / OPERATOR AWARENESS ]
An event.
A team in sync.
See who’s online, who acknowledged the event, and what they’ve learned. Operator activity and comments give everyone the context behind the event.
District cooling
“On site. Checking CHW-1 staging. I’ll post an update here in 10 minutes.”
Shared with 2 admins · Central plantAn illustrative chilled-water incident. Replay the story or choose a step to see how acknowledgement and operator activity build a shared picture.
Record the acknowledgement.
An acknowledgement records that a named person has seen the event. Its time and user identity become part of the incident context. Other members of the team can see that response without having to infer it from a separate conversation.
Acknowledgement is different from clearing the underlying condition. The storyboard deliberately keeps the temperature event active after Alex acknowledges it. Recognizing an event and resolving its cause are separate parts of the operating record.
Show who is looking.
Operator presence and page-view activity add another useful piece of information. A manager can see that people have signed in and opened related views. Operators can understand when colleagues are working with the same system.
Activity is context for coordination. Opening a dashboard alone does not establish that equipment has been checked or that a corrective action succeeded. The explicit acknowledgement and subsequent update provide the more specific record of what the team knows.