Footfall by zone
Entrances and floors are visible the same day.
Shopping Mall
Footfall, public-area equipment and energy on one mall operations page.
- Footfall by zone
- Device alerts
- Energy by zone
- Event comparison
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
Footfall, public-area equipment and energy sit on one operations page, so a busy floor, a stopped machine and a high-use zone are compared on the same clock.
Pain Points
- 01
Footfall arrives the next day from another vendor
- 02
Engineering and operations each know half of a breakdown
- 03
Energy is “the mall is high”, not where
- 04
A campaign has no before-and-after footfall
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
- Central HVAC
- Escalators
- Lighting
- Footfall
- Parking
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
- Footfall by zone
- Device alerts
- Energy by zone
- Event comparison
- 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
Public equipment
Escalator, HVAC and lighting alarms become jobs both teams can see.
Energy by zone
Power is split by floor or system, and high zones are listed.
Campaign compare
Footfall before and after an event uses the same count.
Where it fits
- Shopping centres
- Retail streets
- Transit retail
- Neighbourhood retail
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.
- 10:00 Before opening
Cooling runs ahead of opening, and low-traffic floors start later.
- 15:20 Escalator noise
An escalator on level 3 reports unusual noise; a ticket goes to the on-site crew.
- Same day
The repair enters the equipment file, and the monthly report shows the fault spread.
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.
Same-day footfall by floor
Equipment alarms and jobs are one item
High-use zones are named
Related Cases
Retail
Smart Retail Management System
New retail solution with omnichannel experience
Footfall and inventory can be compared
Learn More →EnergyEnergy Management System
Campus utilities were opaque and waste found late; unified metering and boards locate peak periods and circuits.
Usage split by area; waste easier to find
Learn More →Related solutions
Questions
Where does this industry get stuck?
Footfall arrives the next day from another vendor Engineering and operations each know half of a breakdown Energy is “the mall is high”, not where A campaign has no before-and-after footfall
What does Yifu do here?
Footfall by zone: Entrances and floors are visible the same day. Public equipment: Escalator, HVAC and lighting alarms become jobs both teams can see. Energy by zone: Power is split by floor or system, and high zones are listed. Campaign compare: Footfall before and after an event uses the same count.
What changes after it is in place?
Same-day footfall by floor Equipment alarms and jobs are one item High-use zones are named
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.