Data — the portal

The portal foundation and the Data facet, screen by screen.

In detail

A site driven by configuration

The menu and the screens are not coded: they come from a list of pages, each of a known type, with its multilingual title, its position and its facet. A page belonging to an unsubscribed facet disappears from the site, and a context can hide others. Configuration is read at four levels: the platform defaults, the deployment override, the account's database, then the user's preferences.

Getting in

• Sign-in delegated to the account's identity provider, with enterprise single sign-on.
• With no session, nothing is served — no page, no interface.
• A disabled account is signed out at the next check.
• Creating an account, if open sign-up is enabled: first name, last name, address, optional telephone.
• The note is explicit: read access, which an administrator can widen.
• Neutral response, rate-limited — nothing is revealed.
• Configuration error screen: if the site cannot load its configuration, a standalone bilingual page explains it and offers to retry.
• Errors: any internal error appears under an opaque reference, the detail staying server-side.

The common frame

The header brings together the site's icon and title, the page title, the context selector, the bell, the language choice and the avatar.

• Context selector: the list of the user's scopes, with a warning on a context that selects no device. Switching does not reload the page.
• Bell: an unread counter pushed in real time.
• The panel gives level, label, timestamp and the device concerned.
• A click acknowledges; "mark all read" acts server-side.
• Language: seven languages, one of them written right to left, remembered per user — otherwise the browser's. All configured content is translated.
• Theme and branding: two colours, a light, dark or automatic mode, the site icon and the footer — per site and per context.
• Side menu: one entry per page in the configured order, with two fixed entries at the bottom — my notifications and configuration.

The foundation screens

Dashboard

A grid of widgets that adapts to the width, with a configurable automatic refresh. One dashboard per context: each scope has its own widgets or inherits the site's.

Point-of-sale record

This is the canonical route for anything with a device behind it. The header gives the label, the online or offline state expressed as a duration — "offline for 5 h 14", not a plain yes or no — the type, the status, the bound device, the organisation and the fleet.

A business block adds, depending on the facet, the lifecycle status, the site, the last sale, the day's takings, pre-filtered links to sales, alerts and logs, and actions: suspend or resume sales, restart, republish. The business site only acts on the device's business modules; infrastructure stays with the Console.

Tabs follow: a summary — a unified timeline of alerts, sales, logs and events — telemetry, configuration, then the tabs specific to the machine.

Users

Reserved for the account administrator: the list with role, status and last sign-in, creation (the account is created at the identity provider, which sends the password email), and above all the editor of context attachments, with a role per context.

Organisations

Three lists: organisations (code, label, nature, currency, status), fleets with their organisation selector, and devices with their effective organisation — flagged when inherited from the fleet, and highlighted when the device is assigned nowhere.

Points of sale

The list of business identities with their type, status and current binding. A manager's actions: qualify (the type is required), make it a point of sale if Distrib is active, edit, reject, bind to an unbound device — refused if the device's nature does not match the type — and unbind. A second block lists devices that have arrived unbound, with a reminder of the pairing rules.

Contexts

Each context shows a readable summary of its scope and its number of members. A single form brings together identity — multilingual label, overrides of title, icon, colours, theme, footer, home page — and segmentation along the eight axes, with autocompletion. The user axis accepts the special value "current user".

Viewing as a user

From a user's record, an administrator can open the portal in a context set to that person. A permanent banner announces it, access is read-only — no monetary action, no age verification — every access is logged, and exiting is clean.

My notifications

The signed-in person's preferences: a general switch then one per alert type. Each user manages only their own address.

Configuration

Always reachable, even with no page configured, and organised into tabs:

• Identity: title, icon, colours, theme, home page, footer — with a badge showing where the value comes from, and a possible return to the platform settings.
• Dashboard: the refresh rate, and the widget editor for the site or for the context override.
• Pages: their name, type, facet, position and origin.
• While the configuration comes from the platform it is read-only — a button takes over.
• Once customised, "add what's new" merges in pages published since.
• Alert types: the translation of the types raised by devices into human labels.
• Notification rules, the current context, the account settings (default sender, point-of-sale policies, retention, presence thresholds) and the context's members.

The Data facet screens

Devices

A band of indicators — device count, online, offline, alerts in the last twenty-four hours — then a list with one column per configured metric, sortable server-side, with search, status filter, pagination and export.

Device

The latest values as tiles, a range selector that drives every chart on the page, the widgets or one curve per metric, and the list of the latest readings. This is also the telemetry tab of the point-of-sale record.

Alerts

The systematic record: every alert appears, including those no rule picked up — they show greyed out, with an explicit note. A band of clickable indicators acts as a quick filter, and each row carries its episode state — "open for 5 h 14, three times" or "cleared" — as well as its delivery: how many rules, how many notifications. Refresh is in real time, and the detail shows the full payload.

Logs

Timestamp, level, device, module and message, with filters and a period. A full-text search requires a period, pre-filled to the previous day.

Data feeds

The sampling engine's screen. A banner recalls the number of unrouted records, with examples — the reminder that every feed is opt-in. The form adapts its fields to the chosen sampler, and lets you set the output feed's retention and the forwarding destination.

Notification rules

A rule is a criterion and several actions. The form asks for the organisation (pre-filled from the context), the type, the level on the scale, a label, then each action with its channel, its recipients and its texts — all composed from the event's variables.

Unsubscriptions, analysis, exports

• Unsubscriptions: one row per recipient and type. Re-subscribing means deleting the row. A plain reader sees only their own address.
• Analysis and anomaly detection: trends, comparisons, periodic reports and exploration beyond the widgets. Detected drifts appear among the alerts and follow the rule engine.
• Export and printing: every data list can be exported, a widget exports as data or image, and reports print with a dedicated stylesheet.
• Reports: the choice of report, the dates, the "as if we were at…" reading, then a printable statement with its scope header.

The widgets

The editor adapts its fields to the widget type and keeps a synchronised expert view for fine settings.

Conventions across the portal

• Device filter by autocompletion on every list, over the reference data already bounded to the context: never an identifier to type.
• Names everywhere: numeric identifiers are never displayed.
• Facet badge on every tab outside the foundation; a tab of an unsubscribed facet does not appear.
• Translation button on every configurable label, which unfolds the languages and keeps those outside the list.
• Export active on data lists and reports, absent from administration lists.
• Random business identifiers: a number does not reveal a volume of activity.
• Mobile-ready: grids of one to three columns, scrollable tabs, panels bounded to the screen height.
• Security: role, user, context and instance are set by the server on every call.
• Never by the browser, and a facet that is not deployed refuses explicitly.