SynOne — Integrated Building Platform

In a typical building, access control, HVAC and lighting, parking, management fees and meters mean five vendors, five programs and five passwords. SynOne puts them on one platform — one sign-in, one set of permissions, one alarm centre — with people, doors, units and devices entered once. Switch on the modules you need and add more later without changing systems.

• Buildings consolidating several systems onto one screen
  • Office
  • Mixed-use
  • Residential

  The overview shows each floor and the location of alarms on a 3D building model; access, monitoring, property, parking and energy sit in one menu instead of five logins.

• Control rooms that need to see what needs attention now

  Alarms are graded, pop up full-screen with sound and open the nearest camera, and every acknowledgement is recorded; linkage rules can notify, locate and bring up video when a condition is met.

• Integrators rolling out site after site

  A new site needs no code changes: settings forms, site configuration files, Excel import of the IO point table, exportable graphic screens, and an acceptance report at handover.

SynOne is installed on the site’s own Windows server, with PostgreSQL as its database. Fire, smoke-extraction and other life-safety interlocks stay with the on-site hardware; the platform monitors, notifies and records, and does not replace them.

• Modules on demand

  Access, monitoring, property, parking, energy, video recognition and other modules are switched on per licence and need; disabled modules vanish from the menu and their interfaces stay closed.

• Permissions down to each door

  Administrator, operator and viewer roles come built in, with custom roles on top; 72 fine-grained permissions, and accounts can be limited to particular doors. Every action is written to the audit log.

• Graphics and a 3D overview

  Upload a floor plan (PDF works), drag icons, bind points and control equipment on the drawing; the home page builds a 3D model of the building from its floor settings and marks alarms on the floor where they happen.

• Automation with a dry run

  Schedules, linkage and demand shedding start by logging the commands they would have sent; real control is enabled once checked on site.

• Updates that roll themselves back

  Each update backs up, swaps files, restarts and runs a health check, reverting automatically if any step fails; the check covers services, databases, licence, backup freshness and disk space.

Shared platform capabilities below; see each product page for module functions.

• Accounts and sign-in
  What it covers

  Three built-in roles plus custom roles, 72 permissions, door scoping, audit log
  Notes

  Five failures lock for 15 minutes; idle sessions sign out; first sign-in forces a password change.
• Alarms and linkage
  What it covers

  Graded alarms, full-screen pop-up, sound, nearest camera, acknowledgement; condition-triggered notification, location, video and recording
  Notes

  Notifications by email, LINE and webhook; control actions start in dry run.
• Reports and history
  What it covers

  Automatic daily and monthly reports (printable to PDF) and CSV, optionally emailed; history of points, connectivity, plates and swipes
  Notes

  History is kept for 400 days by default.
• Device connectivity
  What it covers

  Gateway drivers for Modbus TCP / RTU, BACnet/IP, Siemens S7 and MQTT; access readers, DI/DO, two-wire lighting, air-con bus, plate cameras, RTSP cameras
  Notes

  Each brand and model is verified on site before rollout.
• Rollout tools
  What it covers

  Settings forms, site configuration files, Excel import of the IO point table (preview before writing), graphics export and import, acceptance report
  Notes

  No code changes for a new site.
• Server and operations
  What it covers

  Windows server, PostgreSQL, auto-start and watchdog, daily backups (30 kept), health checks, one-step updates
  Notes

  Each module has its own database account; updates are run by us.

1. 01
   Survey devices and needs

   List the brands, models and protocols of readers, controllers, meters and cameras on site, and decide which modules to enable.

2. 02
   Install the server

   Install the platform, database and services on the site’s Windows server, with auto-start and daily backups.

3. 03
   Import points and screens

   Import the IO point table from Excel, previewing the changes first; upload floor plans, place icons and bind points.

4. 04
   Dry run and on-site checks

   Automation runs in dry-run mode first; logs are checked against what happens on site before going live.

5. 05
   Acceptance and handover

   Produce the acceptance report and hand over accounts and permissions; health checks and daily backups keep watch from then on.

Do we have to buy every module?

No. Each module can be bought on its own and the platform enables it per licence; adding one later is a switch on the same platform, with no new system or data rebuild.

Where is the data? Is it a cloud subscription?

No. SynOne is a perpetual licence installed on the site’s own Windows server, with databases and video kept on site; it backs up daily and can write to a separate disk.

Can it replace fire or smoke-extraction interlocks?

No, and it should not. Life-safety interlocks stay with the on-site hardware; SynOne monitors, alarms, notifies and records so the people on duty know at once.

What happens if the licence fails or the server is copied?

The licence is bound to the server’s hardware. If it fails, only configuration changes are locked — doors, alarms and other site operations carry on — and a server or motherboard swap just needs a reissued licence from us. See the software licence terms.

Licensing

Sold under a perpetual licence for one site and one server, bound to that server’s hardware by a digitally signed licence file. Copying it to other machines or sites, reselling or lending it, reverse engineering it or circumventing the licence check is prohibited, and infringements are pursued under the Copyright Act. Full licence terms (Chinese) →