Cloud platform · system layer · planned
From individual readings
to system reports and risk forecasts.
This is the aim of our planned SaaS + AI cloud engine; work has not started. Today, our own management platform and customer portal are in use.
- Stage
- Planned, not started
- In use today
- Management platform, customer portal and AI data interfaces
- Foundation
- Signal-layer outputs
- Data location
- Hong Kong
Current position
Three parts already in use
-
In use
Management platform
We built our own management platform. It supports company projects and business records.
-
In use
Customer portal
The portal serves an existing software project. Customers can check progress, milestones, invoices and reports.
-
In use
AI data interfaces
Data access is controlled by permissions. AI assistants can query records with read-only access.
We built and operate this platform ourselves; its experience informs development of the sensor data platform.
Cloud engine
Planned analysis across sensors
-
Inputs
Signal-layer outputs
Readings and confidence assessments form the basis of analysis. Cloud reports would build on these measurement outputs.
Planned -
Connections
System topology
Use pipe and equipment connections to relate sensors. Flow, infrared and other types would share one system model.
Planned -
Analysis
Reports and risk forecasting
AI agents would analyse across sensors, report and forecast risks. Each conclusion would give its basis for people to confirm.
Planned
Example report
Questions a system report should answer
These examples use example data, not the output of a real device.
-
Example
Where is water flowing outside scheduled use?
Example: branch 2 flows at 0.80 m³/h from 02:00 to 05:00.
-
Example
Do intake and branch readings agree?
Example: intake 128 m³, branches 121 m³ in total, a difference of 7 m³.
-
Example
Which sensor is offline?
Example: sensor 3 is offline for 6 hours; check its network switch port first.
Data rules
Every number states its source.
-
Separate records
Real device readings and example data are stored separately and always labelled.
-
Visible sources
Every number carries its source or an example label.
-
Project use
Customer readings are used only for that customer’s own project.
-
Stored in Hong Kong
Systems and data are held in Hong Kong under the Personal Data (Privacy) Ordinance.
Next steps