Events vs. Event History Discrepancy

All the Places Events Are Generated

Events originate both in the building hardware and in the BluSKY cloud. Below is a complete list of the devices and systems that generate events:

Local (Building Hardware)

• Person Readers
• Mercury Controllers
• AIRC Controllers
• Destination Dispatch Elevator (DDE) Processors
• Elevator Relay Devices
• Network Video Recorders (NVRs)
• Intercom Systems
• Power Management Devices
• Third-Party Alarm Panels
• Gunshot Detection Sensors
• Other Third-Party Peripheral Devices

Cloud (BluSKY Services)

• Visitor Events
• Certain Alarm Events
• Personnel Updates (additions, deletions, modifications)
• AI-Generated or AI-Augmented Events

Event Flow

Local Event Creation

• Each device listed above generates an event.
• Events are timestamped immediately at the source when they occur.

Transmission to the Cloud

• Events are sent upstream to BluSKY.
• This process is asynchronous, meaning events arrive at different times due to:
  • Internet hiccups or dropouts
  • Circuitous network routing
  • Device processing speeds
  • Power interruptions
  • Temporary event payload errors

Event Aggregator (Cloud)

• Once events reach BluSKY, they are aggregated into a unified stream.
• This ensures that both cloud-generated and building-generated events flow into the same database.

Event Analyzer (Cloud)

• Events are enriched before display:
  • Person images are attached
  • Database lookups add context (access levels, schedules, locations)
  • AI adds scene interpretation or behavioral tags
• This augmentation step takes additional time, further adding to the asynchronicity.

Presentation to the User Interface

• Events are displayed on workstations and mobile clients, which are windows into the BluSKY cloud.
• The Events screen shows real-time incoming data.
• The Event History screen shows the authoritative, complete, fully processed dataset.

Why Discrepancies Appear

• Because every device/system listed above operates independently and events travel across the network in different ways, timing mismatches occur.
• An event may be generated at time T0, but not reach BluSKY until a few seconds (or rarely, minutes) later.
• If the Events screen has already passed that time window, the event may appear “missing” until it is slotted into place.
• The Event History always reflects the full, corrected record, since it queries historical data, not just live feeds.

Timestamps and Ordering

• Event Timestamp: Exact moment the event occurred (recorded at the device).
• Cloud Timestamp: When BluSKY received and processed the event.
• All events are ultimately sorted into their proper order by their event timestamp, even if they arrive later than expected.

Practical Effect

• Events Screen: Real-time feed. Sometimes incomplete or out of order for short periods.
• Event History: Authoritative record. Always complete, always properly ordered.

Frequency

• This discrepancy is exceedingly rare — a fraction of a fraction of one percent of all events. It is a normal behavior of distributed, asynchronous systems and does not indicate a defect.