Check-in route
QR or NFC shows which points were visited, photographed or missed.
Property Management
Inspections, repairs and owner requests in one workflow.
- Inspection check-in
- Repair dispatch
- Device registry
- Owner progress
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
Inspections, repair tickets and owner updates stay on one trail, so a missed point or a lost request is visible instead of verbal.
Pain Points
- 01
Paper sign-offs do not prove the route was walked
- 02
Owners cannot see who took the repair
- 03
Equipment ledgers and maintenance contracts diverge
- 04
Billing and work orders live in different books
How the system is put together
Keep the equipment you have, connect the data first, then split the views by role. The connection layer takes the most work, and it is where most of our effort goes.
L1
Devices
- Lifts
- Pumps and water supply
- Power and fire systems
- Access and barriers
- Cameras
PLCs, meters, access control, cameras and sensors already on site. Read what is readable, add a module where it is not, and leave the existing control system alone.
L2
Connection
Modbus · OPC UA · MQTT · HTTP · GB28181 · SDK
Common protocols connect directly. The gateway handles protocol mapping, local buffering and backfill, so the data does not break.
L3
Platform
- Device registry
- Time-series data
- Alert rules
- Work orders
- Roles and audit
Device registry, time-series data, alert rules, work orders, roles and audit in one back end that serves several scenarios.
L4
Applications
- Inspection check-in
- Repair dispatch
- Device registry
- Owner progress
- Manager view
- Phone actions on site
- Narrow external lookup
Data is collected once and reused by every scenario added later, which is why the connection layer has to be done properly the first time.
What we deliver
Repair tickets
Owners can see who has the job and how far it has gone.
Equipment file
Lifts, pumps and fire gear share a file with maintenance due dates.
Bill next to ticket
Charges and related work orders can be looked up together.
Where it fits
Residential estates - inspection check-ins
Points carry a code, so visited, photographed and missed are all visible, listed by route.
Office buildings - repair dispatch
A request becomes a ticket; who holds it and how far it has gone is visible to the tenant.
Industrial parks - equipment files
Lifts, pumps, power and fire gear keep one file with due dates, warned before they pass.
Outsourced maintenance - tickets and scoring
External crews use the same tickets; response and completion times feed the scorecard instead of chat logs.
What a real day looks like
Not a feature list: what actually happens in a day. These four steps are the common shape of such projects.
- 08:10 Report
A tenant reports a leaking kitchen. The ticket routes to the on-duty plumber by building.
- 08:26 On site
The plumber checks in by QR and uploads a photo; the tenant sees "on site".
- 09:05 Done
The valve is replaced, the part cost goes on the ticket, and after confirmation it lands in billing.
- Month end
The third leak in the same layout is flagged, pointing at the riser pipe.
Delivery rhythm
Every stage has a checkable output. No six-month build followed by a single review.
- Week 1
Site survey
Walk the site, list devices, available ports and current systems, and mark what reads directly versus what needs a module.
- Week 2
Pick the first scenario
Rank the ideas by impact, feasibility and dependencies, then choose one that proves value without dragging in every department.
- Weeks 3-5
Connect and wire up
Gateways connect devices, data lands on the platform, and alert rules, roles and recipients are configured for a small internal group.
- Weeks 5-7
Pilot
One team or one building uses it for real; rules and screens change with feedback until false and missed alarms settle.
- Week 8
Accept and repeat
Check every acceptance item, finish documentation and training, then decide which buildings, lines or sites come next.
Acceptance is these three lines
The three items below come from projects of this kind and go into the acceptance sheet, instead of relying on a general impression.
Missed inspection points are listed
Repair status does not depend on phone calls
Maintenance due dates are warned in advance
Related Cases
IoT
IoT Management Platform
Scattered plant devices and protocols, brought into one platform for inventory, boards and alerts—less ad-hoc ops handoff.
Device onboarding and inventory in one place
Learn More →IoTDevice Control System
Remote device control and monitoring system
Command results can be acknowledged
Learn More →Related solutions
Questions
What if tenants will not install an app?
A WeChat mini program works after one scan, and SMS updates need no registration at all.
Old estates have no point codes?
Labels go up once, generated in bulk and printed by building and floor.
Can it connect to our billing system?
Yes. Tickets and charges link by unit number, with fields agreed together so there is only one set of books.
How are outsourced crews managed?
They get restricted accounts that see only their tickets, with response, arrival and completion times scored.
How long for one site?
Three to six weeks for one estate or building: inspections and repairs first, then the next site.
Free diagnosis
Tell us where it gets stuck
Leave one contact. We send how similar projects were handled plus a scenario list. If it is not worth doing, we say so.
- A 30-minute call to judge whether it is worth doing
- A workable scenario list and timeline
- No consulting fee up front
Get Industry-specific Solution
Phones are answered 9:00-18:00 on weekdays, or scan the WeChat code.