Asset board
The assets that must be watched together sit on one map.
Smart City
Municipal assets and alarms on one board for the duty desk.
- Facility dashboard
- Alert handoff
- Event replay
- Single data source
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
Existing systems stay. The duty desk gets one board for the status and alarms that need to be seen together, then handed on and reviewed.
Pain Points
- 01
Lights, covers, pumps and environment each have their own screen
- 02
An alarm has no clear department to receive it
- 03
Closed events leave no shared record
- 04
Management figures and the duty desk figures differ
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
- Street lights
- Manholes and flooding
- Waste stations
- Cameras
- Environment sensors
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
- Facility dashboard
- Alert handoff
- Event replay
- Single data source
- 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
Alarm handoff
Alarms go to the right crew, and progress can be checked.
Event history
Raise, handoff and close stay on one event.
One data set
The wall screen and the duty desk read the same feed.
Where it fits
- Municipal duty rooms
- City-operations teams
- Public-asset supervision
- Emergency watch
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.
- 06:30 Lights still on
A road keeps its lights on past sunrise; the circuit points to one transformer box.
- 07:10 Dispatched
A ticket goes to the lighting crew with the circuit and the last three faults.
- Same day
Current returns, the ticket closes, and uptime enters the weekly report.
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.
Duty staff are not switching among many systems
Alarms have an owner and a record
Reports and the floor share one feed
Related Cases
General
Data Visualization Screen
Duty and reports relied on last-minute sheets; configurable rotating boards replace screenshot-and-verbal numbers.
Key metrics on one screen
Learn More →CampusDigital Twin Campus System
Campus assets and energy need a 3D map tied to the site; twin views map devices and alerts for duty and emergency.
Campus assets in one ops view
Learn More →Related solutions
Questions
Where does this industry get stuck?
Lights, covers, pumps and environment each have their own screen An alarm has no clear department to receive it Closed events leave no shared record Management figures and the duty desk figures differ
What does Yifu do here?
Asset board: The assets that must be watched together sit on one map. Alarm handoff: Alarms go to the right crew, and progress can be checked. Event history: Raise, handoff and close stay on one event. One data set: The wall screen and the duty desk read the same feed.
What changes after it is in place?
Duty staff are not switching among many systems Alarms have an owner and a record Reports and the floor share one feed
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.