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.
- Smart Building Management
- Features
- Operational Events
Operational Events
Record the site condition, acknowledge its actual start and retain when the event is resolved.
OverviewResolved Event History×
Smart Building Management · Operational Events
New
Resolved Event History
Operational events
| Site | Event type | Description | Started at | Ended at | Status | |
|---|---|---|---|---|---|---|
| STS-8797 | Outage | Cut to length | 10 Oct | 19 Oct | Resolved | |
| STS-5544 | Maintenance | Weld frame | 25 Oct | 28 Oct | Resolved | |
| STS-5590 | Alarm | Drill and tap | 15 Oct | 24 Oct | Resolved | |
| STS-4278 | Curtailment | Deburr | 14 Oct | 16 Oct | Resolved | |
| STS-1265 | Outage | Assemble | 14 Oct | 21 Oct | Resolved |
6 of 6 records
Cut to lengthOperational events · OE-77859
OutageSiteSTS-8797
Started at10 Oct
Ended at19 Oct
StatusResolved
What you can do
Give the building condition an identifiable record
Site Operator records an operating event against the site, choosing Outage, Maintenance, Alarm or Curtailment and describing the condition. Open identifies work still needing acknowledgment. The description should help the Facilities Manager understand what is happening at the building and where the response needs attention.
Acknowledgment records the actual start and assigns a maintenance task to an active responder. The event then remains visible as Acknowledged until it is resolved, when the end is recorded. These dates describe the event history the team will examine during its operating review.
How the work is organized
- Event capture. Site Operator identifies the site and event type, then records a description that distinguishes the condition from other work at the building. A clear description helps the responder recognize the situation on arrival.
- Acknowledgment and response. Facilities Manager acknowledges the event and selects an active responder for the site’s maintenance work. The acknowledgment retains the actual start, while the assigned task carries its own due date and progress.
- Resolution history. Facilities Manager records resolution through the event process and retains the actual end. The event state and the maintenance-task state remain separate operating facts for the team to review.
What to agree during setup
Agree what each event type means for the pilot building and who may acknowledge or resolve it. Define the evidence staff use to record the actual start and end. A late acknowledgment should not quietly substitute the time someone opened the screen for the time the condition actually began.
Confirm how active responders are identified and how Facilities Manager checks that assigned work has reached the right person. Agree the operating practice for reviewing task progress alongside the event without assuming that a task’s completion automatically resolves the condition. The team should know which decision remains with the event owner.
Check the handoff on an actual case
Use an alarm concerning ventilation in the east lobby. Site Operator creates the event at the intended building and describes the affected zone clearly. Facilities Manager acknowledges it using the actual start and assigns the response task to the selected active person.
Sign in as Maintenance Technician and check that the site task appears with the correct description and due date. While work proceeds, inspect the event as Facilities Manager and confirm that its Acknowledged state remains understandable alongside the task’s progress. Record the event’s resolution with the actual end when the operating condition has been addressed under the agreed practice.
Repeat the acknowledgment attempt with a responder who does not meet the active-person rule and confirm that the assignment cannot proceed as valid work. Finally, review the event history from another authorized account. The reader should be able to identify the site, condition and actual event period without relying on the person who first reported it.
What your team sees
- Open Operating Events — Open and acknowledged site conditions with their type and recorded period.
- Resolved Event History — Resolved conditions with the start and end retained for review.
- Active Maintenance Tasks — Outstanding site work with its assigned person and due date.
Follow the work through
Use Event acknowledgment to resolution, alongside Assigned work to completion.
What it keeps track of
Data model- Operational events
- Outages, alarms, curtailments and maintenance events at sites.
- Sites
- Managed buildings and facilities in the portfolio.
- Maintenance tasks
- Assigned maintenance work for sites.
- People
- Staff and operators linked to platform users.
Who uses it
Permissions- Facilities Manager
- , Site Operator, Maintenance Technician.
- Site Operator
- Records the condition, Facilities Manager owns the event review, and Maintenance Technician carries out the assigned site work.
Set up Smart Building Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.