8+ typical DI points and Modbus registers attached to BOM.
Kembali ke Penyelesaian
Diagnostik selepas jualan · ringkasan tender
Topik kejuruteraan diagnostik selepas jualan dan operasi.
- 8+Typical alarm points
Table with BOM - DI/ModbusConnect to RCU
Terminal definition - TempatanScene persistence
Control continues offline - Pilihanoperasi jarak jauh
not included in hardware purchase
Alarm input · model entry
Alarms from hardware DI — NOC dashboard by integrator, Poin Tulen Pintarprovides terminal definitions.
Tender citation · three-step method
Ops chapter defines alarm tiers and response duty; remote ops is optional add-on.
P1/P2/P3 vs response SLA and responsible department.
Local scene persistence standard; cloud NOC not default purchase item.
* Remote ops and work orders by integrator or third-party platform; Poin Tulen Pintar provides hardware event sources and API docs.
Alarm tier matrix
Ops tender chapter by P1/P2/P3 defines response scope — specify local action, remote push and Poin Tulen Pintar delivery boundary.
Typical alarms
SOS pressed · vacant illegal entry · RCU property-wide batch offline
Local action
DO audible/visual / corridor full bright · local scene persistence · alarm bit write
Remote response
Front-desk popup < 30s· NOC phone escalation · security recording linkage (integrator)
Responsibility boundary
Poin Tulen Pintar provides DI/DO terminals; dashboard / work orders / SLA by integrator or MSP
Typical alarms
Lock low battery · module RS485 timeout · card-power status fault
Local action
Dry contact log · fault circuit isolation · room-status bit correction
Remote response
Work order within 4h· email to engineering · spare prediction (optional)
Responsibility boundary
Poin Tulen Pintar provides register table and modules; work order system not included
Typical alarms
DND/MUR status · firmware updatable · energy over threshold (platform side)
Local action
Scenes run normally · DI report · no control interruption
Remote response
Housekeeping dispatch · OTA schedule window · report rollup (integrator)
Responsibility boundary
Poin Tulen Pintar optional remote ops interface; OTA policy by integrator platform
After-sales diagnostic point table · by deployment scale
Commissioning doc core — cite by single property / chain / managed; addresses per project register table.
| Amaran | DI / register | RCU action | Platform |
|---|---|---|---|
| RCU offline | Heartbeat /0x0000 | Local scenes continue | Email engineering |
| Lock low battery | DI-05 | Dry contact log | Pesanan kerja |
| SOS urgent | DI-08 | DO alarm output | Front-desk popup |
| Card power fault | DI-01 | Bit status | Room status correction |
| Amaran | DI / register | RCU action | Platform |
|---|---|---|---|
| Batch offline | Heartbeat aggregation | Local persistence | NOC tiered push |
| Illegal entry | Door sensor DI-02 | Vacant alarm | Security linkage |
| Module comm failure | RS485 timeout | Fault isolation | Segmented troubleshooting |
| DND / MUR | DI-03 | scene linkage | Housekeeping dispatch |
| Firmware OTA | — | — | Integrator platform (optional) |
| Amaran | DI / register | RCU action | Platform |
|---|---|---|---|
| SLA response | Heartbeat + log | — | MSP NOC |
| Remote diagnostics | Modbus read-only | No control interruption | operasi jarak jauh |
| Spare prediction | Low battery / life bit | Log | Cross-property inventory |
| Boundary notes | — | — | Poin Tulen Pintar is not a SaaS ops vendor |
