Horizon

MOV'SMART, Smart Access, Infomedia, Horizon CRM, Smart Space and Smart Transportation are not six separate products bolted together. They are six domains of a single platform, sharing the same accounts, the same permission model, the same equipment registry and the same audit trail.

In practice, an operator signs in once and switches domain from a single selector, instead of juggling six tools with six passwords and six versions of the truth. A vehicle recognised at a barrier, a subscription renewed online and a message pushed to a display are all the same customer record.

Most parking software is built for one car park. Horizon is built for an operator running dozens across several countries — which requires a hierarchy rather than a flat list:

Organisation. The legal entity: its own address, its own languages, its own multi-factor authentication policy, and its own trees. A group operating through several subsidiaries keeps them properly separated.

Project. A deployment perimeter — a city, a client site, a contract — with its start and end dates, its own set of software modules and connected devices, and its own sender and support addresses.

Tree node. Nested car park structure: a district holds car parks, a car park holds levels. This is where access rights, tariffs and reports attach, and they cascade down the branch.

Device. Every connected unit is registered individually and placed on the map: barriers, ANPR cameras, payment kiosks, screens, RFID readers, QR scanners, IO boards, printers, media players.

The consequence is practical: an operator responsible for one district sees exactly that district. A retention rule set at organisation level applies everywhere; the same rule set on one car park applies only there.

Because the domains sit on one platform, the administration that usually gets duplicated six times is done once:

Users and roles. Permissions are granted per feature, with create, update and delete distinguished, then scoped to specific projects and tree nodes. A report-only role for an accountant is a matter of minutes.

Multi-factor authentication. Enforced at organisation or project level, by email or authenticator app, for perimeters that require it.

Equipment registry. Each device carries a live status — production, test, demo, debug, registered — so a terminal being commissioned never pollutes production figures.

Languages. English, French, Dutch and German, set per organisation and per device: a terminal in Flanders and one in Wallonia serve the same operator from the same configuration.

Message templates. Email and SMS templates per domain, per language and per tree node — subscription renewals, unpaid invoices, document verification, reservation confirmations.

Claiming GDPR compliance is easy; demonstrating it is not. Horizon makes the retention policy an operational setting rather than a paragraph in a contract.

Retention rules per data category. Subscriptions, permits, plate-recognition files and transaction records each get their own retention period, defined in days, months or years.

An explicit action at expiry. Delete, encrypt, archive or anonymise — chosen per rule. Analytics keep working on anonymised data long after the identifying records are gone.

Applied at the right level. A rule attaches to an organisation, a project or a single tree node, so a site under a stricter contract can hold a shorter retention period than the rest of the estate.

Horizon is assembled from services that are declared, versioned and addressable — which is what makes integrating third-party systems configuration work rather than a project.

A documented API. Horizon API and Horizon Provider expose the platform to your own systems: accounting, ticketing, building management, mobility apps.

A software registry. Every module — park broker, local park manager, payment service, file server, cashier terminal, mobile applications — is registered with its server, its base URL and its validity dates.

Third-party clients welcome. A partner's application joins the registry the same way ours does, with the same rights model and the same audit trail.