Integration

System Integration: Access Control, Campus Cards, ERP and OA

“Can it connect to our existing systems?” is the most frequent question at procurement. Here is the integration capability, the list of systems we can integrate with, the standard process and the data-security boundary.

Hongzhida Technology

1. Integration capability

Cabinets connect to your systems through REST APIs, with gateways for distributed sites. Three kinds of data move across the boundary: identity and credentials, approval and workflow records, and notifications. The interface list is defined and confirmed in the proposal stage.

2. Systems we can integrate with

Systems we can integrate with
ERPKingdee CloudAsset ledger and approval sync
OAFanweiWorkflow approval and forms
IMWeCom / DingTalk / FeishuOrg structure, notifications
WeChat official accountWeChat official accountMobile queries and alerts

Systems not on this list are still connectable — the REST API is open and custom connectors are developed per project.

3. Typical integration scenarios

  • Access control / campus card: credential sync so one card works across doors and cabinets.
  • ERP / OA: approvals and asset ledgers flow both ways, no double entry.
  • IM: open records and alarms pushed to admins in real time.

4. Standard integration process

Interface definition

Confirm fields, direction and frequency with your IT team.

Joint testing

Test against your staging environment.

Go live

Cut over by site, with rollback ready.

Operations

Interface monitoring, logs and version upgrades.

5. Data security

On-premise deployment keeps data inside your network, with permission models and audit logs for compliance. Records cache locally when the network drops and sync on reconnection. See theintegration FAQ, and the wider IoT picture on theIoT solutions page.

Systems to integrate?

Tell us which systems to connect and we will assess the interface plan.