Beyond Compliance: Why BluB0X’s Integrated VideoVoiceText (VVT) Elevator Communication Outperforms StandAlone Systems

In 2019, ASME A17.1/CSA B44 introduced requirements for two way messaging and in car video visibility to improve accessibility and response during elevator entrapments. Jurisdictions have been adopting these requirements alongside IBC 2018+, and elevator OEMs and third party vendors now market compliant “video-and-text” offerings. Yet most of those products are singlepurpose, networkisolated solutions that leave owners paying for separate systems (intercom + monitoring + cameras + analytics + access control) and separate service contracts-while security and operations teams still work in silos. (Elevator World, Emergency Help Phones | Kings III)

BluB0X takes a different approach. Built on the BluSKY unified security platform, BluB0X’s VVT solution is natively integrated with building video, access control, destination dispatch, and an Elevator Management System (EMS)-so the same hardware and same software deliver code compliance and building intelligence (ride quality analytics, telemetry, identity management, multilingual NLP, and remote “virtual master station” operations). The result is lower total cost of ownership (TCO), stronger incident response, and measurably higher ROI versus standalone elevator offerings.

Code & Compliance Snapshot Shape

A17.12019 / B4419 Section 2.27.1 expands Emergency Communications to include:

• Two way messaging that doesn’t rely on passenger speech or hearing,

• Video means to view occupants anywhere in the car,

• Status messages (e.g., “help is on the way” above 60 ft rise),

• Communication with authorized personnel who can take action.

• IBC 2018+ aligns with these accessibility goals; A17.12022 continues enhancements to ensure communication is accessible for hearingimpaired passengers. Adoption timing varies by state and city (e.g., NYC), so owners must confirm local enforcement.

Implication: Compliance is necessary but not sufficient. Owners should choose a solution that satisfies code and integrates with building security and operations.

Market Landscape: Who Sells What

Below are representative offerings. Each meets or targets A17.12019/IBC 2018 requirements, but their integration posture and operational scope differ widely.

Elevator OEM Programs

• KONE - 24/7 Emergency Video Communications

Turnkey, monitored service with voice + text + visual communications. Runs on a standalone OEM network that explicitly does not connect to the building network (reducing cyber risk but limiting direct integration). TK Elevator - MAX Link Voice & Multimedia / MAX Video Two way voice, video, and chat; routes calls to TK’s 24/7 center or customer’s service; sold to support A17.1 compliance in North America.

• Schindler - Visual Communication System (VCS)

Voice, text, and one way video with Safe Call; positioned for A17.12019/IBC2018 compliance.

• Otis - eView / Gen3 Platform

In car display with entertainment/info that connects to OTIS LINE® in an emergency; marketed as the OEM’s integrated screen platform. (Public materials emphasize emergency calling and infotainment; depth of third party security integration is not detailed.)

Specialist ThirdParty Providers

• Kings III - CabView

Two way messaging + video to meet A17.1/IBC requirements; widely known for monitoring services and code adoption guidance.

• RATH/AVIRE - Smart View 2

Two way visual communication with Yes/No prompts and external camera; marketed for A17.12019 compliance; modular components and hub.

Common thread: These solutions focus on elevator compliance and monitoring. Public documentation often stresses network separation and dedicated monitoring rather than integration with base building security video, access control, or EMS. (Some integrations exist through fixtures and call centers, but deep, open integration into a unified security platform is generally not the primary design goal.)

BluB0X’s Integrated Approach (BluSKY + VVT + EMS)

BluSKY VideoVoiceText (VVT) Intercom

• Two way voice, in car video, and text with cloud integration, real time monitoring, multilingual support, and analytics. Designed to integrate with existing security systems and mobile devices.

• SIP/VoIPbased communications for standards driven interoperability across the building-not a siloed, OEM only network.

BluSKY Elevator Management System (EMS)

• Unifies intercom, elevator control/telemetry, security video, and access control in one platform, with lifesafety integration and real time visualizations of car status and movement.

Person Reader (Inside the Car and at Turnstiles/Lobbies)

• All in one reader + intercom + camera + recorder + analytics, supporting appearance, voice, and name recognition, SIP two way A/V, and natural language interaction with multi language support. Reuses the same hardware for video recording and intercom, trimming devices and wiring.

Ride Quality & Telemetry (ERM)

• AI-powered Elevator Ride Monitoring (acceleration, jerk, vibration) using BluB0X AIRC edge hardware and cloud analytics-turning every intercom/camera install into a serviceable data source for operations.

Virtual Master Station & Anywhere Answering

• SIP based intercom can be answered by building security, central stations, or mobile devices via BluSKY’s virtual master station-simplifying staffing, after hours coverage, and disaster recovery.

What This Means for Owners & Managers

The Integration Dividend

• Unified response: Operators see/hear the occupant and view live video, floor position, and access events from one interface-speeding triage and reducing mis dispatch.

• Lower TCO: One standards-based device per car does 4 jobs-intercom, video surveillance, elevator analytics, and access enablement-with a single cloud platform and service wrap.

• Better occupant experience: Multilingual NLP allows voice interaction without typing; onscreen text and “help on the way” messaging meet accessibility expectations.

• Open architecture: SIP/VoIP and API driven integration mean it’s easier to tie into base building intercoms, VMS, and identity systems than with network isolated elevator OEM offerings.

Competitive Snapshot (What’s Publicly Documented)

Legend: ✅ Supported | ◐ Partial/Not Primary | - Not publicly documented

Capability (selected)	BluB0X (BluSKY VVT + EMS + Person Reader)	KONE 24/7 EVC	TK Elevator MAX Link / MAX Video	Schindler VCS	Kings III Cab View	RATH/AVIRE Smart View 2
Twoway voice + twoway messaging	✅	✅	✅	✅	✅	✅ (BluINFO, KONE U.S., TK Elevator, Elevator Solutions USA, [Emergency Help Phones
Incar video to view occupants	✅	✅	✅	✅ (oneway video)	✅	✅ (BluINFO, KONE U.S., TK Elevator, Elevator Solutions USA, [Emergency Help Phones
Multilingual user interaction	✅ (NLP, multilanguage)	-	-	-	-	- (BluINFO)
NLP (voice commands, language detection)	✅	-	-	-	-	- (BluINFO)
Uses SIP/VoIP (standards)	✅	◐ (OEM network; integration not primary)	-	-	-	- (BluINFO, KONE U.S.)
Reuse same camera for VVT and security recording	✅	-	-	-	-	◐ (camera integrated for SmartView) (BluINFO)
Ride quality analytics (ERM)	✅	-	-	-	-	- (BluINFO)
Integrated with building video & access (one platform)	✅	◐ (OEM ecosystem focus)	◐ (OEM ecosystem focus)	◐ (OEM ecosystem focus)	◐ (monitoring focus; fixtures partners)	◐ (elevatorcentric) (BluINFO, KONE U.S., TK Elevator, Elevator Solutions USA, [Emergency Help Phones
Virtual master station / answer anywhere	✅	✅ (OEM center)	✅ (OEM center)	✅ (SafeCall)	✅ (monitoring center)	◐ (hub/call center) (BluINFO, KONE U.S., TK Elevator, Elevator Solutions USA, [Emergency Help Phones
Network posture	Open (SIP) + Building IT	Standalone OEM network	OEM network	OEM/SafeCall	3rdparty monitored	Elevatorcentric (BluINFO, KONE U.S.)

Notes: The table reflects publicly available documentation as of Aug 24, 2025; depth of third party security integrations is not always specified by OEMs or monitoring providers. Always verify specific project requirements.

ROI & TCO Model (Illustrative) Shape

Scenario: 10 cabs in a mid ise modernized building.

Standalone stack (typical): elevator intercom + separate compliant video/messaging kit + elevator monitoring subscription + separate incar camera for security + separate analytics/ride monitoring + base building intercom/VMS/access (unrelated).

BluB0X stack: One SIPcapable VVT/Person Reader device per cab + existing (or added) camera leveraged for both security and VVT + BluSKY for intercom, video, analytics (ERM), access/identity, and EMS.

Expected effects (5year horizon):

• CapEx: Fewer devices/cable runs and shared edge hardware (intercom + camera + analytics) → 15-30% project savings (range depends on modernization scope).

• OpEx: One cloud platform + fewer service contracts + remote support → 20-40% service/monitoring savings (range depends on current call center contracts).

• Risk: Faster, richer incident response (voice + text + video + telemetry) reduces false dispatch and liability exposure.

These figures are assumptions based on typical line items and device counts; actual savings depend on site conditions, labor rates, and existing infrastructure. Use this framework to create a buildingspecific pro forma.

Implementation Blueprint Shape

1. Assessment & Code Check: Confirm local adoption of A17.12019/IBC2018+ (e.g., NYC follows enhanced requirements).

2. Network & Cyber: Use building IT with SIP/VoIP; segment by VLAN; coordinate with BluB0X AIRC edge device plan where ride analytics or local recording are desired.

3. Hardware Plan (Per Car): Person Reader or equivalent VVT endpoint; reuse camera as security + VVT sensor; add ERM sensors if deeper analytics desired.

4. Platform Setup: Enable BluSKY EMS, intercom routing (security desk/central station), virtual master station, and event logging/retention.

5. Enable AI/NLP & Multilingual: Turn on language detection and NLP to meet accessibility goals without typing.

6. Test & Drill: Validate “help on the way” messaging, camera coverage, and escalations; run stakeholder drills to measure time to response.

RFP/Spec Checklist (CutandPaste Ready)

Code Compliance

• Meets A17.12019/IBS 2018+ two way messaging and in car video visibility requirements.

• Displays “help is on the way” message when required (rise ≥ 60 ft).

Interoperability & Integration

• SIP/VoIP two way audio/video; routing to security desk, call center, or mobile.

• Native integration with building video (VMS), access control, destination dispatch/EMS, and event logging (single platform).

User Experience & Accessibility

• Multilingual interaction with NLP voice interface; touch/text fallback and Yes/No prompts.

• Live video view of the entire cab; privacy and audit controls.

Operations & Analytics

• Ride quality KPIs (acceleration, jerk, vibration) and car telemetry mapped to incidents.

• Cloud updates, remote diagnostics, and unified reporting.

Why BluB0X Wins

• Four systems for the price of one: Intercom + Security Video + Elevator Analytics + Access/Identity-on one platform.

• Not a silo: SIP/VoIP + APIfirst architecture integrates with base building systems (intercom, VMS, access) instead of isolating on an OEM network.

• Smarter response: Operators see/hear occupants and context (car position, occupancy, access events). EMS + ERM elevate service levels and SLA accountability.

• Better experience: NLP + multilingual interface removes the need to type; supports passengers who are deaf/hard of hearing, nonverbal, or stressed.

Appendix A - Code References (PlainLanguage Summary)

• A17.12019 §2.27.1 expands car Emergency Communications to ensure responders can view and message passengers who cannot speak/hear and to display status (e.g., “help on the way”).

• A17.12022 continues accessibility improvements; IBC 2018+ aligns with visual/two way communication mandates. Adoption can vary by jurisdiction and date.

Appendix B - Competitor Citations

• KONE 24/7 Emergency Video Communications (turnkey, standalone OEM network; IBC/A17.1 references).

• TK Elevator MAX Link / MAX Video (two way voice/video/chat, 24/7 routing; compliance positioning).

• Schindler VCS (voice, text, one way video; code references).

• Otis eView/Gen3 (incar display; emergency connection to OTIS LINE).

• Kings III CabView (video + two way messaging; code adoption resources).

• RATH/AVIRE SmartView 2 (two way visual communication; datasheet and modular components).

BluB0X/BluSKY References (BluINFO): VVT Intercom, EMS, Person Reader, ERM, Virtual Master Station.