Enterprise Administration

Configure the platform around your organization.

Units of measurement, data types, value lists, states, holidays and map profiles are configured once and used everywhere — by the registry, the rule engine, the dashboards and the map.

Book a DemoTalk to an Expert

 
 
 
 
 
 
 
Vision Smart Platform symbol
Defined onceReference data configured centrally and read by every module
In your languageList values defined per language, with display order and an active flag
AuditableAdministration screens carry the same audit tab as the rest of the platform

The settings every other module reads.

Administration is not a settings page bolted on the end. It is where the vocabulary of the platform lives: the units a metric can carry, the types a parameter can take, the values a dropdown can offer, the days a rule treats as holidays.

Value lists
The lists behind every selection field, each with a technical attribute name, a description, and values defined per language with their display order and active flag. Import and export included.
Units of measurement
Units defined by name and symbol, with sub-units carrying their own conversion factor, so multiples and submultiples of the same quantity stay related instead of drifting apart.
Data types
The set that governs how values in parameters, metrics and commands are read: binary, time, date, datetime, boolean, string, decimal and integer.
Company registry
One register of companies where vendor, integrator and client are roles attached to the same record. A company that is all three is entered once, not three times.
Scheduled jobs
Tasks defined by cron expressions and bound to a functional module, for work that has to happen on a clock rather than in response to an event.
Menu and settings
The application’s menu structure, shared resources and global settings, edited in the platform rather than in configuration files.

Units that carry their own conversions.

A unit is a name and a symbol, and it can hold sub-units with their own conversion factor. A data type decides how a value is read. Together they are what stops a bare number from being ambiguous.

Units of measurement
Luxlx
PascalPa
DecibeldB
Kilometre per hourkm/h
NTUNTU
Microgram per cubic metreµg/m³
Cubic metrem³
pHpH
No unit—
Each unit can hold sub-units — multiples and submultiples — with their own conversion factor.
Data types
binarytimedatedatetimebooleanstringdecimalinteger
The type is what tells the platform how to read the value a parameter, a metric or a command carries.

The units and data types listed above are the ones configured in the platform.

One company, several roles.

The company register follows an entity-plus-roles model. A company is defined once; vendor, integrator and client are distinct associations that reference the same record. The same organization can hold all three at the same time, without being entered three times and drifting out of step.

The entity
Company
Defined once in the central register, with its own record and its own audit trail.
A role on it
Vendor
The manufacturer behind a device model or a commercial version.
A role on it
Integrator
The organization that deploys and maintains equipment in the field.
A role on it
Client
The organization the installed estate belongs to.

A device offer attaches to equipment; the estimates list shows, for each IoT system, the currency and the clients and integrators involved. It is consultation-only — estimates are generated from the offers and the composition of the systems, not entered by hand.

Configured here, consumed everywhere else.

Three settings that look administrative and behave operationally. What is defined on these screens is what the dashboards colour, the rule engine evaluates, and the map lets a given user do.

States
Read by dashboards and the map
  • A name, an icon and a colour, defined once
  • Used to mark values and thresholds wherever they appear
  • The platform’s own example is a pH scale, with one state per step
Legal holidays
Read by the rule engine
  • An annual calendar alongside an administrative list
  • Filters on name, start and end date, and recurrence
  • The days defined here are exactly what the Holiday and IsHoliday operators evaluate
Map profiles
Read by the map
  • Sets of map settings applied to the users a profile covers
  • Device filters, note editing and zone display stay disabled until their parent setting is filled
  • A preview of the map sits next to the profile as it is configured

One console for the parts nobody wants in a config file.

Menus, scheduled work, organizational structure and the commercial layer are administered from the same console as everything else — by the people who run the platform, without a deployment in between.

Menu editor
The application’s menu structure, edited in the platform. A new module or a reorganized navigation is a configuration change, not a release.
Scheduled jobs
Tasks bound to a functional module and driven by cron expressions — the platform’s own example cleans up stored metrics and commands every ten minutes, Monday to Saturday.
Organization chart
The organizational structure alongside the units themselves, so the shape of the company and the accounts attached to it stay in one place.
Offers and estimates
Device offers attach to equipment, and the estimates list shows the currency, clients and integrators per IoT system. Consultation-only: estimates follow from the offers and the systems, not from manual entry.

Bring us the vocabulary your estate already uses.

Your units, your states, your holiday calendar, your organizational structure. We will show you where each one lands in the platform and what reads it afterwards.

Discuss your project