Where it is
Department, status and owner are on the file, and transfers are recorded.
Healthcare
Medical equipment and hospital energy, with use and maintenance on record.
- Device registry
- Service due
- Repair ticketing
- Zoned energy
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
This stays on equipment and energy: which department, last maintenance, and whether checks were recorded. It does not replace clinical systems.
Pain Points
- 01
The ledger lags behind which department actually has the device
- 02
Maintenance and calibration due dates are remembered by people
- 03
Repairs are separate from the equipment file
- 04
Energy is a site total, not theatres and wards
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
- Medical gas
- HVAC and clean rooms
- Lifts
- Queue systems
- Medical devices
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 registry
- Service due
- Repair ticketing
- Zoned energy
- 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
Due dates
Maintenance and calibration show up before they expire.
Repair on the file
A repair stays on that asset for the next lookup.
Energy by area
Power and steam by building or large department, with odd usage marked.
Where it fits
Outpatient building - air handling
Fresh air follows clinic hours and floor traffic, so waiting areas are adjusted on data.
Wards - call and rounds
Bedside calls and nursing rounds reconcile, so response times are checkable at handover.
Facilities - gas and power
Gas pressure, backup power and critical circuits are watched together; alarms reach the duty room first.
Biomed - files and maintenance
Files, due dates and faults for medical devices sit together, so annual checks leave the spreadsheet.
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.
- 07:30 Before the list
The theatre pre-cools, and the schedule opens only once temperature and humidity are in range.
- 08:12 Pressure alarm
Theatre 3 loses differential pressure; the notice reaches biomed and the nurse station together.
- 08:20 Handled
The engineer finds a sticking damper and the fix lands on the unit file.
- Monthly
Repeat alarms feed the maintenance report and decide the actuator replacement.
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.
Department and owner are on record
Due maintenance is a list, not a memory
Repair history stays on the asset
Related Cases
Healthcare
Smart Healthcare Platform
Healthcare management platform for quality and efficiency
Appointments and equipment status aligned
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
Can medical device data be connected?
Through the vendor interface where one exists, otherwise a vendor gateway or manual entry. The device itself is not modified.
What about compliance?
Data stays inside the hospital network zone, accounts use hospital SSO, and every action is audited.
Will it disturb clinical work?
Read-only collection, work scheduled outside clinic hours, and clean-area changes planned around shutdown windows.
Does it replace HIS or facilities systems?
No. It reads through interfaces and only covers the facilities and equipment view.
How long does it take?
Six to ten weeks per building, with clean-area or gas work following the shutdown window.
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.