Voltrus OEE Documentation

Installation

Voltrus OEE is a hosted SaaS — there is nothing to install, self-host, or maintain. You sign in at oee.voltrus.id from any browser (phone, tablet, or desktop). The hardware kit is rented and optional; you can also bridge existing PLC/HMI signals with no hardware at all.

Get access

Requirements

RequirementDetails
BrowserAny modern browser — Chrome, Safari, Firefox, Edge. Mobile and tablet supported.
AccountEmail-based sign-up; unlimited users per site
Hardware kit (optional)3 rented devices per machine — Digital Andon, Scrap Counter, Sensor Node. Shipped pre-configured.
Or: bridge existing gearIf you already have a PLC/HMI with a dry-contact or 24 V cycle signal, no Voltrus hardware is required.

First login

After your account is provisioned, sign in at oee.voltrus.id. The dashboard loads empty on purpose — Voltrus OEE never invents data. Machines appear the moment you connect a signal (sensor node or PLC bridge).

No self-hosting, no server to run. Setup, integration, hosting, and updates are included. The first year for 10 machines is $3,600 (or $27/machine/mo billed yearly) — vs $25K–$80K+ for a conventional OEE/MES rollout.

Quick Start

1. Create an account

Sign up with your email at oee.voltrus.id. Your site is live in about 30 seconds. Request access first if your workspace isn't provisioned yet.

2. Tell us how many machines to monitor

From Settings → Machines, add each machine (e.g. M-101, M-102). Pick a machine type and a default status set. You're billed per active machine — add or remove machines at any time.

3. Connect the floor (hardware kit or existing PLC)

Two paths, same result — the dashboard lights up:

  • Rented hardware kit: mount the Sensor Node near the machine's mold-close / cycle sensor (dry contact or 24 V via optocoupler). It sends cycle data wirelessly to the Digital Andon tower lamp. The Scrap Counter handheld (or the mobile app) logs reject ticks.
  • Bridge existing PLC/HMI: if you already have a cycle signal, wire or map it into Voltrus OEE. No PLC programming on your side — we handle the integration.

4. See everything live

Open the dashboard. Every machine shows a live status (Running, Changeover, Breakdown, Micro-Stop, Slow Cycle, Process Defect, Planned Stop), a rolling OEE gauge with Availability / Performance / Quality, and a downtime log with reason codes. The floor goes live within roughly 24 hours of the kit arriving.

Configuration

Statuses (shape + color coded)

Voltrus OEE classifies every machine state. Each status maps to a color and a shape (circle, square, triangle, diamond) so it's readable across the floor and colorblind-safe.

StatusClassificationOEE impact
RunningProductive (green circle)Counts toward run time
Planned StopPlanned (grey square)Excluded from OEE (break, meeting)
ChangeoverChangeover (blue rounded square)Availability loss
BreakdownBreakdown (orange triangle)Availability loss
Micro StopMicro-stop (yellow dot)Availability/performance loss
Slow CycleSpeed loss (cyan diamond)Performance loss
Process DefectQuality loss (red triangle)Quality loss

Reason codes

Every stop captures a reason code and a duration automatically. Reason codes are configurable and unbounded — add as many reject / downtime reasons as your process needs; you're not limited to fixed slots.

OEE formula

The OEE formula is editable per site to match your definition. The default is the standard product:

OEE = Availability × Performance × Quality
Availability = Run Time / Planned Production Time
Performance  = (Ideal Cycle Time × Total Count) / Run Time
Quality      = Good Count / Total Count

Tweak what counts as planned time, ideal cycle time, and good vs scrap per machine in Settings → OEE.

Pricing & billing

PlanPrice
Monthly$30 per machine / month
Yearly (save 10%)$27 per machine / month, billed annually

Both tiers include unlimited machines and users, OEE + scrap analytics, configurable statuses and reasons, and the option to use the rented hardware kit or go mobile-app-only. The hardware kit is rented (not bought) and stays with you while subscribed.

Hardware kit (3 rented devices per machine)

DeviceRole
Digital AndonLED tower lamp — broadcasts machine status, visible across the floor
Scrap Counter5-button handheld (or station-mounted) — each button = +1 to a scrap category
Sensor NodeIoT transmitter reading the cycle input (dry contact / 24 V); sends data wirelessly to the tower lamp

Key Features

Live, plant-wide dashboard

Every machine's status in real time, shape-and-color coded, from any browser. Open it on a wall-mounted tablet for the floor, or your phone from the office. No client install, no kiosk to maintain.

Automatic downtime tracking

Every stop is captured with a reason code and a duration automatically — operators don't have to log downtime by hand. The Pareto of reasons shows you exactly where the hours went each shift.

OEE + scrap analytics

Site, building, and machine-level OEE broken into Availability, Performance, and Quality. Scrap Pareto by reason code. Shift and day reports without an Excel export step.

Rented hardware, never bought

Three pre-configured devices per machine, included while subscribed. Ship, mount, go live — no integration project, no PLC programming on your side. Prefer zero hardware? Use the mobile app for scrap logging and bridge an existing cycle signal.

Configurable, not fixed

Statuses, the OEE formula, reject buckets, and reason codes are all editable. No code, no migration. Adapt the system to your process instead of bending your process to the software.

Unlimited machines & users

Pricing is per machine, not per user. Add every operator, supervisor, and manager without a per-seat tax. The dashboard scales from one machine to an entire plant.

Troubleshooting

Machine shows "unknown" / no status

Symptom: A machine tile is grey/blank or reads "unknown".
Fix: The sensor node (or PLC bridge) isn't delivering cycle data. Check the sensor node is powered (battery or 24 V), that the dry-contact/24 V input is wired to the actual cycle signal, and that it has joined the wireless mesh to the tower lamp. If bridging a PLC, confirm the signal toggles on each cycle.

OEE looks too high (or too low)

Symptom: OEE reads 100% during a clearly imperfect shift, or unrealistically low on a good one.
Fix: The formula inputs are off. In Settings → OEE, check ideal cycle time (too low inflates Performance), what's counted as planned production time (excludes breaks/changeovers), and that planned stops are classified correctly so they're excluded. Recompute after each change.

Downtime reason not captured

Symptom: A stop is logged but the reason code is blank.
Fix: Reason assignment defaults to "unspecified" until an operator picks one. If most stops come back unspecified, simplify the reason list and surface a prompt on the andon or mobile app right when the stop occurs — reasons captured live are far more accurate than end-of-shift recall.

Tower lamp not updating

Symptom: The Digital Andon shows the wrong color or lags the dashboard.
Fix: The lamp receives status wirelessly from the sensor node. Check the lamp is powered and within mesh range, and that the sensor node is online. If the dashboard is correct but the lamp is stale, power-cycle the lamp so it re-joins the mesh.

Can't sign in / new device

Symptom: "Invalid credentials" or the dashboard won't load.
Fix: Use the email and password you signed up with at oee.voltrus.id. If you've forgotten it, use the reset link on the sign-in page. Confirm your workspace is provisioned — if you just requested access, onboarding may still be in progress; contact hello@voltrus.id.

Scrap count not incrementing

Symptom: Tapping the Scrap Counter buttons doesn't add rejects.
Fix: Confirm the handheld is paired to the correct machine ID and online. As a fallback, log scrap from the mobile app, which writes the same record. If the buttons fire but quality stays 100%, verify the reject category is mapped to a quality-loss status.

Support

Voltrus OEE is a hosted service, so most issues (status gaps, hardware pairing, OEE formula) are configuration rather than bugs. When you write in, name the machine ID, the shift/time window, and what you expected vs. what you saw — that's usually enough to resolve it the same day.