Machine location
Key machines show their current project, and transfers are recorded.
Construction
Site equipment, conditions and material movements on the project.
- Device-to-site map
- Environment thresholds
- Material checkout
- Maintenance by device
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
Three things: which site a machine is on, whether site conditions crossed a line, and whether materials were signed out. It does not replace the whole construction suite.
Pain Points
- 01
Crane and hoist locations are confirmed by phone
- 02
Dust and noise breaches arrive as a notice from outside
- 03
Material issues have no record at settlement
- 04
Maintenance notes stay on personal phones
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
- Tower cranes
- Dust and noise
- Hoists
- Distribution boxes
- Video
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
- Device-to-site map
- Environment thresholds
- Material checkout
- Maintenance by device
- 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
Site conditions
Dust and noise notify the site when a line is crossed.
Material trail
Issues name the project and the use, for later settlement.
Maintenance on the asset
Service records stay on the machine across projects.
Where it fits
- Building sites
- Civil sites
- Equipment hire
- Project materials
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:00 Dust over limit
PM10 passes the limit, spray starts and the safety officer is notified.
- 08:20 Confirmed
The officer uploads a photo and the record enters the environmental log.
- Monthly
Exceedance windows export with the spray records for regulatory filing.
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.
Machine location does not need a phone call
The site hears a condition breach first
Material issues match at settlement
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
Where does this industry get stuck?
Crane and hoist locations are confirmed by phone Dust and noise breaches arrive as a notice from outside Material issues have no record at settlement Maintenance notes stay on personal phones
What does Yifu do here?
Machine location: Key machines show their current project, and transfers are recorded. Site conditions: Dust and noise notify the site when a line is crossed. Material trail: Issues name the project and the use, for later settlement. Maintenance on the asset: Service records stay on the machine across projects.
What changes after it is in place?
Machine location does not need a phone call The site hears a condition breach first Material issues match at settlement
Do we have to replace our current systems?
No. The platform reads through interfaces or gateways and the existing systems stay in use. Only modules nobody maintains are worth replacing.
What does it cost, and how soon is it live?
Priced by scenarios and device connection points: a site survey produces the list, then a quote and schedule. Most projects have a first scenario live in four to eight weeks.
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.