Build a consistent plant structure, from one site to many

What it covers

• Secure sign-in and session control Security policy is enforced by the system itself, including lockout after failed sign-in attempts, password expiry, and password resets that only an administrator can perform. An AI Assistant is also available to help find information such as KPIs, orders, and downtime using everyday language.
• Role-Based Access Control (RBAC) Set permissions by role and scope of work, so each user can only do what they are actually responsible for. Access control is applied consistently across the operation and supports the controls relevant to regulated environments.
• Centralised, controlled master data Manage master data in one consistent structure, with changes recorded so every piece of data stays traceable and auditable.
• Plant and infrastructure model Run many plants on one platform, with area hierarchies that can be nested to match each site's structure, and storage locations whose capacity and utilization can be monitored.

One platform, many plants, no copied records

Every record belongs to one plant or is Global, shared by every plant. A user only ever sees the plants they are assigned to.

• One switcher for every screen The Plant Scope Switcher in the header sets the scope for every screen at once.
• Local versions without forking the master A plant can define its own version of a Global record under the same name, such as a shift, a hold reason, a numbering pattern or a calendar event.
• The same answer for every user For single-value settings such as standard rates, changeover entries and BOM revisions, the plant's own row wins and Global is the fallback. The key is the record's plant, never the viewer's, so a calculation gives every user the same result.
• Calendars combine, rotations replace A national holiday and a plant shutdown both block time. A plant's team rotation replaces the Global one, so labour capacity is never counted twice.

The plant structure follows ISA-95

Equipment is more than an asset list. VECHR models it in a hierarchy that follows ISA-95 principles, so scheduling, access control, and performance reporting can all work from the same structure.

Because this structure is shared, context stays consistent across the system. The line you scheduled against is the same line you see in OEE (Overall Equipment Effectiveness) and the same line you scope access control to.

Access control ready for audit

• Enforced server-side Every action is checked against the user's permissions on the server, not merely by hiding a button or a menu in the interface.
• Access scoped per plant Permissions can be scoped by plant, so a user with supervisor access at one site does not automatically get the same rights at another.
• Credential policy enforced by the system Password complexity, expiry, lockout after repeated failed attempts, and reset mechanisms can all be applied as system policy.
• Access activity is recorded Sign-ins, sign-outs, failed attempts, and lockouts are written to the system access log, so access activity can be reviewed later.
• Permissions, roles and role groups Permissions are fine-grained grants per service, action and entity. Roles bundle permissions, and role groups bundle roles for a job function. Users are given role groups.
• Licence and access are checked together A menu, screen or action appears only when the licence includes the feature and the user's role allows it.
• Sessions an administrator can end The Active Sessions table shows each user, IP address, sign-in time and device. An administrator can terminate a session, and the forced logout is logged.
• A recovery path for the last administrator A forgotten administrator password is reset with an offline command-line tool, not through a back door in the application.

Load master data in bulk, without surprises

Supported master-data screens round-trip through CSV. Download the template, fill it in and import it, or export what is already there.

• A preview before anything changes Choose Update or Create-Only mode and review a preview before the import runs.
• Problems reported where they are The validator lists file-level problems, per-row problems and warnings separately.
• Spreadsheets from any locale Headers do not depend on the language setting. Separators, decimal marks, Yes/No columns and blank cells are handled explicitly.
• Numbers that labels can trust A Numbering Pattern can append a GS1 mod-10 check digit, and a pattern marked for SSCC issues the plant's pallet SSCC (Serial Shipping Container Code) numbers.

Run the system from inside the app

• A System Admin console per service Each backend service has a status card, a read-only configuration panel, resource figures and Restart or Shutdown controls.
• Licence and seats in one place License & Session shows the licence state, enabled features, seat consumption and active seats.
• The browser's own connection A separate Connection screen shows the health of the real-time link between the browser and the platform, with metrics and a manual reconnect.