Elevator & Escalator Monitoring

Problem

Lift and escalator status sits in the vendor’s own system, so the control room learns about a trapped passenger or a stopped escalator by phone.

Opis rozwiązania

MILESGO gateways collect data from lift controllers, escalator controllers, run/stop and fault dry contacts over Modbus RTU / Modbus TCP / SNMP, and deliver it to the BMS, the operations / command centre, SMS, email and messaging alarms as BACnet/IP / OPC UA / MQTT. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

lift controllers
escalator controllers
run/stop and fault dry contacts

Protocol path

Modbus RTU / Modbus TCP / SNMP → BACnet/IP / OPC UA / MQTT

Implementation checklist for the project manager

Where equipment only offers a vendor API or cloud, confirm access rights, data rate and costs with the vendor before design.
Collect register maps and protocol documents from every equipment vendor early; a missing map is the most common delay.
Commission in read-only mode first; enable write / control points only after the client approves each one.
Define an alarm matrix (priority, recipient, escalation) and test every alarm end to end at SAT.
For hard-wired signals, list each DI/DO/AI/AO with its type (dry contact, 4–20 mA, 0–10 V, PT1000) and choose I/O modules accordingly.
Hand over configuration backups, point table, IP plan and as-built drawings, with a short operator training.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

Architektura systemu

Field layer: lift controllers, escalator controllers, run/stop and fault dry contacts, connected over Modbus RTU / Modbus TCP / SNMP. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: the BMS, the operations / command centre, SMS, email and messaging alarms, which receives the data as BACnet/IP / OPC UA / MQTT. Remote access for maintenance runs over VPN rather than open internet ports.

Skład systemu

Field devices: lift controllers, escalator controllers, run/stop and fault dry contacts
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: the BMS, the operations / command centre, SMS, email and messaging alarms (BACnet/IP / OPC UA / MQTT)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Możliwości oprogramowania i AI

Predictive maintenance indicators from equipment trendsW planach
Alarm noise reduction and root-cause groupingW planach

Etapy wdrożenia

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

Korzyści dla klienta

One view of all subsystems instead of separate vendor consoles
Alarms reach the right person by SMS, email or messaging apps
Monitoring added without changing existing control programs
Timestamped records for compliance and reporting

Więcej rozwiązań w obszarze Smart Building

Opowiedz nam o swoim projekcie

Prześlij protokoły, liczbę punktów i system docelowy. Każde zgłoszenie analizuje zespół handlowo-inżynierski.

Omów swój projekt