Smart Building Systems Integration
智慧建築系統整合
Central monitoring, property management, digital signage, and blockchain records — deployed individually or integrated with existing equipment
Where systems integration actually breaks down
- 01
Equipment from different vendors uses different protocols; integration scope is difficult to estimate at bid stage
- 02
Most Label assessment items are mandatory — missing one scores zero for that item
- 03
Subsystems operate independently; integration gaps surface at commissioning
- 04
Software integrators change hands; no one maintains the system after handover
Subsystems
Fire Safety
Alarm signals trigger recording on linked cameras and send elevators to the ground floor
Emergency Call
Activation displays severity, floor, device, and timestamp site-wide; the view switches to the affected floor with live imagery from that location
Power
Transformer, breaker, and generator status monitoring with alarms and cross-system triggers
Energy
Shedding is triggered on projected cycle-end demand rather than instantaneous readings, with separate thresholds for trigger and recovery
Water
High-level detection starts drainage pumps; cumulative consumption and flow rate on one view
HVAC
Outdoor unit control and temperature setpoints from the platform, with indoor air quality linked to operation
Ventilation
Carbon monoxide thresholds in parking areas start exhaust fans
Lighting
Circuit status and brightness monitoring, with scheduling and ambient light control
Elevators
Current floor, direction, load, pit level, and cumulative runtime per car; fire recall on alarm
Access Control
Card readers, electronic locks, and release buttons under one system; remote unlock requires secondary confirmation
Security
Sensor and contact status monitoring with remote arm and disarm, linked to camera retrieval
Intercom
Indoor units listed by floor with connected in-unit devices
Surveillance
Cameras mapped to devices; the relevant feed appears automatically when an alarm fires
Parking
Barrier and EV charger status; charging locks out on overload
System architecture
Field equipment connects to the monitoring platform over communication protocols. The platform serves property management, signage, and record-keeping modules above, and executes automated control below.
System modules
- Monitoring
Bacco iFMS
Subsystem monitoring and cross-system automation
- Operations
SyncPMS
Property management
- Operations
E-Paper
Status display for legacy equipment
- Broadcast
DSnet
Announcements and emergency messaging across screens
- Records
SyncBC
Monitoring data and events written to blockchain, tamper-evident
- Access
Visitor Access
Visitor authorization, entry control, and elevator floor restriction
Cross-system automation
Planning
Identify which device combinations require linkage based on the assessment items, and confirm the protocols and controllable range of on-site equipment
Construction
Connect field devices over open protocols without vendor lock-in; automation rules are defined as trigger, condition, target device, action
Operation
Rules are adjustable as usage patterns change; alarms close only when the condition clears and an operator confirms — unresolved events remain in the queue
Not limited to a single product line
Ready to deploy
Features and interfaces are already defined, so deployment does not require new development — schedule and cost can be estimated up front.
Existing equipment stays
Open protocols connect to what is already installed — adopting the platform does not require replacing existing systems
Hardware and software flexibility
Our own modules and partner hardware or software can be brought into the same integration architecture
Single item or full scope
We can fill a specific assessment gap, or take on the full software integration scope