Connect the equipment you already own, then see what is happening
Your machines already produce their own data. VECHR MES reads it over the protocols the equipment supports, attaches it to the relevant order, unit, and lot, then turns it into operational information you can use straight away.
Read live data from the machines you already own over OPC UA, MQTT and Modbus TCP. See OEE (Overall Equipment Effectiveness), MTTR and MTBF without a spreadsheet.
Today OEE is a spreadsheet built at month end.
With VECHR MES Availability, performance and quality, calculated live.
Today A dropped connection goes unnoticed.
With VECHR MES Connection health is visible, with automatic reconnect.
Today A breakdown is retyped into a work order.
With VECHR MES One click turns the event into a work order.
What assets and IIoT cover
- Production-ready IIoT connectivity Connect equipment over industrial protocols such as OPC UA, MQTT, and Modbus TCP directly at the resource. Connections come with auto-retry and real-time data point visibility, so machine data is usable by the MES immediately.
- OEE & reliability analytics Compute Availability × Performance × Quality continuously, complete with downtime categories, MTTR (Mean Time To Repair), MTBF (Mean Time Between Failures), and the history of operational state changes, to see how equipment really performs.
- Preventive maintenance based on real condition Use reusable procedure templates, structured spare-part checklists, and maintenance schedules driven by time or by actual equipment usage.
- Operator certification control Restrict operator access to machines based on valid certification, complete with expiry dates and certification history.
Five views of one piece of equipment
One machine, one source of information. Its configuration, live condition, history, and performance all sit in the same context.
| View | What it holds |
|---|---|
| General | Basic equipment information such as manufacturer, model, serial number, installation date, and capacity. |
| Monitor | Connection status and live data point values, including reading history so you can see previous conditions. |
| KPI | MTTR, MTBF, and availability for that equipment and for the resources beneath it. |
| OEE | Availability × Performance × Quality, displayed and trended continuously. |
| Data Points | Connection and data point configuration: protocol, tags, and read frequency. |
What happens once the equipment starts talking
- Three protocols, straight from the resource OPC UA, MQTT, and Modbus TCP are available directly at resource level, with no additional gateway project required for basic connectivity.
- Connections recover on their own When a connection drops, the status updates immediately and the system attempts to reconnect automatically.
- More than one connection per machine A single resource can hold several connections, for example OPC UA to the main PLC (Programmable Logic Controller) and Modbus TCP to a tank controller.
- Every reading carries a quality flag Data is marked good, bad, or uncertain, so its condition stays visible and it is never quietly treated as valid.
- From anomaly to work order A detected event or anomaly can be used directly to raise a maintenance work order, complete with the context of the equipment involved.
OEE you can trace back to its inputs
OEE is built from a full time hierarchy, from calendar time down to fully productive time.
- Four figures, each with its inputs Availability, Performance, Quality and OEE each have a documented input. A time category counts only when it is flagged Include in OEE.
- Microstops are counted Short stops are detected with a threshold per resource, so they do not disappear inside running time.
- Performance uses the right rate Performance is measured against the plant-resolved Standard Rate for that resource.
- Reliability next to OEE MTBF and MTTR are computed alongside. The KPI and OEE tabs report Availability differently, and the reason is documented.
Connection settings for each protocol
| Protocol | Default port | What you configure |
|---|---|---|
| OPC UA | 4840 | Security policy and mode, application URI and name, session timeout, keep-alive, credentials, certificate. |
| MQTT | 1883 | Client ID, protocol version 3, 3.1.1 or 5, credentials, clean session, keep-alive, timeouts, reconnect period, certificate. |
| Modbus TCP | 502 | Unit ID, endianness, timeout, TLS, certificate. |
Every protocol has a retry policy. Data points can be defined one by one or bulk-loaded from CSV.
Frequently Asked Questions
What automation and IT teams usually ask about connectivity.
Do we have to replace our PLCs or SCADA?
No. VECHR MES connects over OPC UA, MQTT, and Modbus TCP. Equipment that already supports one of those protocols can be connected without replacing the PLCs or the SCADA (Supervisory Control and Data Acquisition) system already running.
What happens if the connection to a machine drops?
The connection status changes immediately and the system attempts to reconnect automatically. Data in a degraded state still carries its quality flag, so it is never treated the same as valid data.
Is OEE calculated live?
Yes. Availability, Performance, and Quality are computed from recorded equipment states and events, then displayed and trended over whatever time range you choose.