Identity Aware Elevator Management: Why BluSKY EMS Complements - Not Replaces - OEM Elevator Systems

Elevator OEMs-Otis, TK Elevator, Schindler, KONE, Mitsubishi Electric, and Motion Control Engineering (MCE)-build the dispatch engines and car controllers that move people efficiently. Their “destination control/dispatch” platforms (e.g., Compass® 360, AGILE, PORT, KONE Destination, ΣAI2200C/DOAS, MCE DBD) sit closest to the machinery and speak native controller protocols. That’s their half of the equation: motion control and throughput optimization.

BluB0X’s BluSKY Elevator Management System (EMS) provides the other half: identity, policy, and evidence. BluSKY EMS merges access control (“who is allowed”), actual usage (“who went where, when, and with whom”), live video/intercom inside cabs, and analytics, then correlates that with car movements coming from OEM systems. The result is a complementary, identityaware layer that OEM EMSs typically do not natively provide.

Crucially, BluSKY does not replace the OEM controller nor “drive the elevator.” For safety and code reasons, BluSKY governs access rights to floor stops and consumes OEM telemetry/commands via supported integrations; it only has a direct control path when an owner explicitly deploys BluB0X ARC/AI controllers with OEM approval. That’s why the right positioning is complementary: OEMs control motion; BluSKY controls and proves identity.

The two halves of a modern elevator stack

Movement intelligence (OEM EMS). Destination dispatch platforms minimize waits and stops by grouping passengers with similar destinations, often with mobileapp eCall. Examples:

• Otis Compass® 360 with SmartGrouping™; eCall mobile app available.
• TK Elevator AGILE Destination Controls; AGILE Mobile app; claims up to ~25% faster travel and ~30% higher capacity (vendor literature).
• Schindler PORT/myPORT; mobile eCall via ElevateMe/myPORT.
• KONE Destination and KONE Elevator Call / Office Flow apps and APIs.
• Mitsubishi ΣAI2200C with DOAS (Destination Oriented Allocation System).
• MCE DestinationBased Dispatching (DBD) for modernization and open controllers.

Identity & security intelligence (BluSKY EMS). BluSKY EMS fuses access rights, personlevel movement, video, intercom, visitor flows, schedules, and incident response with OEM elevator telemetry-giving operators “who/what/when/where/how” for every ride, plus lockdowns and proof. Key capabilities include:

• Personlevel tracking (“who is inside,” destination and disembark floors) and passenger photo IDs in live and historical views.
• Floorstop access control (card/PIN/biometric modes), lock/unlock, timed releases, schedules-without driving the elevator.
• Video, voice & text intercom integrated into cabs and lobbies.
• Analytics & reporting down to the individual: wait times by car/bank/timeofday and usage by person/floor.
• Person Readers at kiosks/turnstiles for appearance/voice/RFID/mobile credentials, with learned defaults and ghostcall reduction (~20%) when paired with destination dispatch.
• DDE Diagnostics (message traces, converter health) for integrators/operators to isolate issues fast.

Positioning in one line: OEM EMS optimizes how cars move; BluSKY EMS proves and governs who is moving, why, and whether they should-then correlates both halves in one pane of glass.

What the major OEMs provide (at a glance)

Vendor	OEM EMS / DCS	Core promise	Mobile eCall	Access control tieins
Otis	Compass® 360 (SmartGrouping™)	Shorter waits/faster journeys; virtual concierge	eCall / eCall Pro	Reader/mobile options; integrates with building systems (per product docs)
TK Elevator	AGILE Destination Controls	Fewer stops, higher capacity (vendor claim ~25%/30%)	AGILE Mobile	Integrates with building access; APIs available
Schindler	PORT / myPORT	Optimized peopleflow; personalization + access	ElevateMe/myPORT	Access verification via reader/app
KONE	KONE Destination	Clear guidance; flexible signalization	KONE Elevator Call / Office Flow	Access Control Interface for thirdparty systems
Mitsubishi	ΣAI2200C + DOAS	Allocation by destination; AI group control	(varies by deployment)	Security device triggers / presets possible
MCE (Nidec)	DestinationBased Dispatching	Efficiency via likedestination grouping	(varies)	Works with open/nonproprietary controllers; modernization focus

Note: Many OEMs offer modernization kits and smartphone eCall; several expose accesscontrol interfaces. That does not by itself deliver tenantwide, crosssystem identity analytics (who rode where correlated with badges, visitors, intercom, and video). That’s the gap BluSKY fills.

What BluSKY EMS adds to OEM EMS (the complement)

Identity becomes part of traffic.

• BluSKY knows the person (employee, contractor, visitor), their authorization, and travel history. Operators see live cars with who is inside, where they’re going, and where they exit, not just hall/car traffic.

Security controls the ride (without driving the elevator).

• BluSKY enforces floorstop permissions, lockdowns, riot/fire modes, and timebased policies; OEM dispatch still moves the car. This separation is intentional and codealigned.

Evidence and response in one place.

• Correlate badge swipes, visitor passes, person photos, incab video and intercom calls with car movement and floor stops-critical for investigations and incident response.

Smarter journeys with fewer “ghost calls.”

• BluSKY’s Person Readers learn default/common floors and can autoassign or confirm destinations, reducing duplicate or mistaken calls (~20% reduction cited) and improving lobby flow.

Operatorgrade diagnostics.

• With DDE Diagnostics (message traces, converter health, realtime streaming), BluSKY speeds rootcause analysis across brands-useful for owners, integrators, and OEM service teams alike.

Analytics that speak both “elevator” and “security.”

• From percar/bank wait times to perperson usage, scheduled reports, and predictive placement-driven by the BluSKY Data Lake and dashboarding.

Where OEM EMS ends and BluSKY EMS takes over (typical gaps BluSKY closes)

Operational question	OEM EMS alone	With BluSKY EMS added
Who exactly rode to Floor 37 at 10:14?	Usually N/A (traffic only)	Personlevel identity from badges/visitors + correlated car movement & video
Can we lock out Floors 12-15 for a security event now?	Recall/priority modes exist, but identityaware lockouts are not typical	Yes, floorstop access control + policies + audit trail
Why is car B overloaded at 8:55?	Traffic metrics	Traffic + people data (tenants, visitors, patterns) + video evidence
Are kiosks creating duplicate ‘ghost calls’?	Dispatch logic tries to cope	Reduce at source via Person Reader defaults/confirmation; report on reduction (~20%)
Can we audit an incident with video + intercom + ride log together?	Typically siloed	Yes, single platform correlation

Sources: BluSKY EMS, Elevator Control, Person Reader documentation, and “How BluB0X Destination Dispatch Works” white paper.

Complementary deployment patterns & ROI levers

• Securityled modernization: Keep OEM dispatch; add BluSKY EMS + Person Readers to gain identity assurance, reduce ghost calls, and unify incident response with video/intercom.
• Twobutton fleet uplift: Enforce floorstop permissions, add visitor workflows, and capture ride histories; preserve OEM control.
• Highrise performance tuning: Use BluSKY analytics to expose bottlenecks by bank/interval/person and test policy changes; employ DDE Diagnostics with OEM teams to accelerate fixes.

Market context: representative OEM highlights

• Otis Compass® 360: SmartGrouping™, mobile eCall (eCall/eCall Pro), reader/mobile integrations.
• TK Elevator AGILE: Destination grouping, designable terminals, AGILE Mobile app; vendor claims ~25% faster travel and ~30% capacity gain.
• Schindler PORT/myPORT: Destination control with access features and mobile app options.
• KONE Destination & Office Flow: Elevator Call app and Access Control Interface to thirdparty access control.
• Mitsubishi ΣAI2200C/DOAS: AI group control; DOAS disperses passengers by destination; security devices can trigger elevator actions.
• MCE (Nidec) DBD: Likedestination grouping, open/nonproprietary modernization focus.

Risks of mispositioning (and how to avoid them)

• “Replacement” framing invites safety and warranty pushback. Use “complement” language and emphasize that BluSKY manages access to floor stops and identity-not hoistway motion.
• Unclear data ownership can stall projects. Clarify early that BluSKY ingests security/dispatch events into a Data Lake for authorized analytics and compliance reporting.
• Siloed UIs frustrate operators. Demonstrate the single BluSKY pane for cars, people, events, video, and intercom with scheduled reports.

Pulling it together-model language you can use

• BluSKY EMS augments OEM elevator systems by bringing identity, security policy, and forensic evidence to every ride. We keep OEM dispatch in the loop and enrich it with who/what/when/where/how-tying badges, visitors, Person Readers, video, and intercom to car movement. The result is safer, faster, auditable vertical mobility-without touching your elevator controller.

Appendix A - BluSKY EMS feature checklist (abbrev.)

• Comprehensive elevator configuration (groups/cars/floors/doors/security)
• Realtime and historical car visualization with optional passenger photo IDs
• Floorstop access modes (card, PIN, biometric), schedules, overrides, lockdowns
• Person Reader kiosks (appearance, voice, RFID, Apple/Google Wallet, BLE)
• Ghostcall reduction and learned defaults
• VVT emergency communication (video/voice/text) across cabs and lobbies
• DDE Diagnostics for traceability and fast rootcause analysis
• Analytics & reporting (wait/ride times; usage by person/car/floor/time of day
• Cloud updates; Data Lake ingestion for enterprise analytics

Sources & further reading

• BluSKY EMS datasheet & pages (features, analytics, personlevel views, lifesafety, updates).
• Elevator Control guide (access rights vs. elevator control).
• EMS video/overview (who is inside / where they disembark).
• VVT Emergency Communication (video/voice/text in cabs and lobbies).
• How BluB0X Destination Dispatch Works (DDE Diagnostics; ghostcall reduction).
• KONE Access Control Interface (3rdparty access link).
• OEM destination dispatch: Otis Compass 360; TKE AGILE; Schindler PORT/myPORT; KONE Destination; Mitsubishi ΣAI2200C/DOAS; MCE DBD.