Arkan Handover and ERP Integrations
Beyond webhooks, ArkanPM ships purpose-built integrations for six integration types: ERP, accounting, BMS (building management systems), IoT, Arkan platform, and custom. This article focuses on the Arkan Handover integration and the common ERP and BMS patterns.
The integration registry
Open Settings → Integrations. Every integration carries:
- Name and type.
- Credentials (API keys, OAuth tokens, or basic auth).
- Endpoint URL.
- Sync frequency.
- Status (active, paused, failing).
Credentials are encrypted at rest. Only tenant admins can view or edit them.
Arkan Handover integration
The Arkan Handover integration is purpose-built for receiving handover records from the Arkan platform. These records typically include:
- Defects — issues identified during handover walks.
- Snags — minor finishing items flagged by the handover team.
- Warranty items — equipment and systems covered by manufacturer or developer warranties.
How it flows
- Arkan publishes a handover payload to the configured endpoint.
- ArkanPM receives and validates the payload.
- Defects are routed into the Defect management module with category, severity, location (building/floor/unit/asset), description, and photo evidence.
- Warranty items are registered in Warranty management with provider, policy number, cost, and expiration details.
- Snags become work orders of the appropriate type (typically corrective).
Configuring the integration
- Open Settings → Integrations → Add integration.
- Pick type Arkan platform.
- Enter the Arkan endpoint URL and credentials.
- Set sync frequency (on-demand, hourly, daily).
- Map incoming defect categories to your internal defect category tree.
- Save and click Test connection.
ERP integration patterns
ERP integrations typically sync:
- Customer records — residents and owners.
- Vendor records — vendor directory and contacts.
- Purchase requests and orders — from ArkanPM's procurement module into the ERP.
- Invoices and payments — typically incoming from the ERP.
Use the Custom integration type for internal ERPs and the dedicated ERP type for shrink-wrapped systems. ArkanPM logs every sync with request and response data, status (success, error, warning), error messages, and duration in milliseconds.
Accounting integration
Accounting integrations focus on financial posting:
- Lease payment receipts.
- Work order cost postings (labor, parts, vendor).
- Owner payout calculations.
- Vendor invoice passthrough.
BMS integration
Building management system (BMS) integrations pull telemetry from HVAC, electrical, fire safety, and security systems. Typical flows:
- Meter readings — flow into asset meters. When readings cross thresholds, the preventive maintenance generator creates work orders.
- Alarms — flow into work requests, auto-escalated based on alarm severity.
- Condition data — feeds into asset condition assessments.
IoT integration
IoT integrations extend the BMS pattern to edge devices: occupancy sensors, leak detectors, smart locks, and environmental monitors. IoT events can:
- Trigger predictive work orders (a leak sensor trips → an emergency work order is created).
- Update occupancy records in real time.
- Feed into the real-time dashboard.
Integration logging and debugging
Every integration action is logged. The integration detail page shows:
- A paginated event log.
- Filters by status (success, error, warning).
- Request and response payloads (truncated).
- Duration in milliseconds.
Use the log to debug sync failures. Common patterns: expired credentials, schema drift on the external side, or rate limiting.
Best practices
- Use dedicated service accounts. Do not reuse a user account for integrations.
- Rotate credentials periodically. Set calendar reminders.
- Monitor the integration log. A silent integration is usually a broken one.
- Map categories explicitly. Default mappings are fine for day one but hurt reporting long-term.
What next
Read Authentication and MFA to see how integration credentials are protected at rest and in transit.