Scene design and point layout
Design the scene and the point list from the actual assets; sites, devices and owners go into one ledger.
Scene Solutions
Packaged Solutions
Start from the scene: select hardware, configure the platform, commission on site, and bring field assets into one ledger, alarm and operations loop.
Who it is for
- System integrators
- Maintenance service providers
- Parks and property management
- Government and public-facility operators
- Energy users
- Agri-aquaculture operators
Site visible, anomalies known, handling traceable, results verifiable
The problem
What you are dealing with now
Many sites, scattered equipment, rounds done by hand; alarms miss the owner and duplicates pile up; work orders, inspection, feedback and monthly reports never line up, so service results cannot be verified.
- Many sites and scattered assets; rounds are manual, so status and risk cannot be seen in one place.
- Alarms miss the owner, duplicates pile up, and escalation has no clear owner.
- Work orders, inspection, feedback and monthly reports sit apart, so results cannot be checked.
The difficulty is the data, not the device
Why this is not solved by adding a sensor
Each site brings different brands, protocols, networks and power, and legacy projects leave disconnected systems and point tables. Packaged solutions start with scene and point design, then hardware and platform, so the field lands in one ledger and one rule set — not a new system per scene.
Standard capability
What this line includes by default
This is the standard scope. Protocol adaptation, custom development, OEM pages, third-party integrations and advanced reporting are scoped and quoted separately.
Central monitoring and tiered alarms
Multi-site dashboards, online and trend views; alarms tiered, de-duplicated and routed to a named owner.
Work orders, inspection and mobile
Alarm to work order, mobile acceptance, on-site photos and closure — the handling is on record.
Reports and open API
Monthly reports, fault statistics and verifiable service evidence; data and events can also feed the customer's existing platform.
How we work
The path for this line
Diagnosis → single-site pilot → multi-site copy. We can take the whole job or only design and product complement. Multi-site operations is the typical form of this line: demonstrable, quotable, acceptable, repeatable.
Mature scenes
Six scenes inside packaged solutions
What changes is the points and the rules, not a new system. Scenes with a page can be opened directly.
Equipment rooms and critical environment
Telecom rooms, data centres, integrated cabinets, substations, archives
Temperature, humidity, leaks, smoke, access, UPS, power and HVAC status
Smart restrooms and sanitation
Public toilets, sanitation assets, scenic spots and venues
Stall occupancy and wayfinding, footfall, odour, consumables, cleaning work orders
Building automation
Offices, public buildings, park common areas and commercial sites
Lighting, HVAC, water, lifts and common-area equipment — monitor and interlock
Energy efficiency
Industry, parks, public buildings, chain venues
Electricity, water, gas, cooling, heat, PV/storage/charging; sub-metering, unit consumption and time-of-use
Smart agriculture and aquaculture
Greenhouses, farms, ponds and modern fishery parks
Water quality, weather, soil, irrigation, aeration and feeding with fewer people on site
Urban ecology and public infrastructure
Hydrology, gardens, manholes, grain stores, scenic spots and parks
Scattered environment and asset status in one view, filed into the operations record
Architecture
How data travels from the field into the loop
- 01
Per-site equipment, meters, sensors, environment and energy assets
- 02
SG / BEC gateway and SDS / IOC modules per site
- 03
AIoT platform: ledger, alarms, work orders, inspection, access
- 04
PC / video wall / app / mini program
- 05
Reports, open API and ongoing service
How to verify
What you can check yourself during the pilot
We do not substitute percentage promises for acceptance. Each item below can be checked by you during the PoC, and used to decide whether to widen scope.
- Finish the scene point design and import the site ledger; verify point counts and owners.
- Trigger a real anomaly and confirm the alarm reaches the right owner by severity.
- Run one work order end to end: dispatch, acceptance, field feedback, closure.
- Export the operations report and check alarm counts, handling time and open items.
Scope limits for this solution
We can take the whole job or only the design and product complement. Protocol and point scope, remote-control permissions, implementation split, acceptance criteria and SLA are confirmed in writing at project stage.
FAQ
What customers ask most during evaluation
Must Tongwei take the whole project?
No. We can take the whole job or only the design and product complement, with the integrator or owner doing the rest. Protocol and point scope, remote-control permissions, implementation split, acceptance and SLA are confirmed in writing.
We already run another monitoring system — must we replace it?
No. Start with sites and devices not yet covered; bring the existing system into the unified view through APIs or data integration. We recommend a single-site, verifiable pilot before copying to more sites.
Are energy, equipment rooms and restrooms three separate businesses?
No. They are scenes inside packaged solutions. What changes is the points and the rules, not a new system. Energy management sits at data acquisition, efficiency analysis and operations — it is not a full EMS and does not do real-time dispatch, production control or safety interlocking.
What if a site has no reliable network?
Gateways support 4G and wired uplinks, buffer data locally during outages and backfill on recovery. Critical interlocks run at the edge and do not depend on cloud connectivity.