Skip to main content

Frequently Asked Questions

Operator​

A stop is not validated: how do I validate it?​

Go to Production → Operator Screen, find the stop event in the downtime list, and click Validate. Select the stop reason from the dropdown, add a comment if required, then confirm. If the Validate button is not visible, you may not have the downtime:validate permission. Ask your administrator.

I cannot see my line on the operator screen: why?​

The operator screen only shows equipment assigned to your shift and your crew. Check that:

  1. Your crew is correctly assigned to the equipment for the current shift in Personnel → Schedules.
  2. The equipment is active (Administration → Equipment → the line must have status Active).
  3. You hold a business role granting perm:oee:read (every role does) and an equipment scope covering that line — check your profile under Roles and Permissions.

I cannot log in from the workshop tablet​

Tablets often lose their Keycloak session after inactivity. Try clearing the browser cache and cookies, then log in again. If the Keycloak login page itself does not load, the Keycloak service may be down. Contact your administrator. See also Login Issues.

How do I change shift mid-day?​

Shift changes in OpSee are automatic: the system switches to the next shift based on the schedule configured in Personnel → Shifts. You do not manually "select" a shift. If the current shift appears wrong, verify the shift schedule with your administrator.

How do I classify a micro-stop of less than 1 minute?​

Micro-stops below the minimum duration threshold configured in Administration may be aggregated or filtered out automatically. If you see a stop shorter than 1 minute that needs classification, validate it like any other stop: select the reason and confirm. If stops below a certain threshold are hidden entirely, ask your administrator to review the minimum stop duration setting.

Manager​

OEE is not calculating: what should I check?​

In order, verify:

  1. The equipment has OEE settings configured (Administration → Equipment → select the equipment → OEE tab). Without this, no OEE is calculated.
  2. The time range and equipment filters in the report are set correctly.
  3. Data is arriving: check Administration → Workers to confirm ingestion workers are running.
  4. At least one shift covers the period you are viewing — OEE is calculated per shift.

How do I compare performance between two shifts?​

Use Reports → OEE and group results by shift. You can filter by equipment and date range, then toggle the breakdown by shift in the chart or export the table to compare shift-by-shift availability, performance, and quality.

How do I export a downtime report?​

In Reports → Downtime, apply your filters (equipment, date range, stop reason), then click the Export button (CSV or Excel). For a Cockpit-based export, the oee-downtime-events widget has an export option in its toolbar.

Some stops are not categorized: what is the impact on OEE?​

Unvalidated stops with no reason assigned are counted as downtime in the Availability factor but are not broken down by loss type. They appear as "Unclassified" in loss-type charts and inflate unclassified time, making it harder to target improvements. The Validation Rate KPI widget shows what percentage of stops have been classified.

Performance looks wrong: how do I investigate?​

Start with the OEE Loss Types widget to see whether the deviation is in Availability, Performance, or Quality. Then:

  • Availability issue: check for long unvalidated stops or missing shift coverage.
  • Performance issue: verify the ideal cycle time (theoretical rate) is correctly configured for the equipment.
  • Quality issue: check whether reject counts are being ingested from the correct data tags.

Admin​

How do I create a new equipment and activate it for OEE?​

  1. Go to Administration → Equipment and click Add.
  2. Fill in the equipment name, hierarchy (site, area, process cell), and set status to Active.
  3. Open the equipment record and go to the OEE tab: configure the ideal cycle time, planned production time source, and any relevant loss categories.
  4. Assign data tags in the Tags tab so the system knows which tag feeds counter and downtime data.
  5. Save. OEE will start calculating from the next shift start.

CSV imports are failing: what should I check?​

  • Verify the file encoding is UTF-8 (not Latin-1 or Windows-1252).
  • Check that column headers exactly match the expected template — download a fresh template from the import dialog.
  • Look for extra whitespace, special characters in text fields, or numeric fields containing non-numeric values.
  • Check the error details in the import result dialog — it lists the row number and field that caused the failure.
  • If the file looks correct but still fails, check the backend logs for a more detailed error message.

How do I regenerate OEE after a configuration change?​

If you modify an equipment's ideal cycle time, shift schedule, or tag mapping after data has already been ingested, past OEE calculations will be stale. Navigate to Administration → Equipment → OEE → Recalculate and specify the date range to reprocess. This triggers a background job; processing time depends on the volume of data.

A new user sees no modules — why?​

In OpSee, access is controlled by Keycloak roles, not by user settings in the application. A new user with no roles sees a blank interface, because the sidebar only shows pages whose permission the user holds.

Assign access in Administration → Access Control → Users:

  1. Open the user record.
  2. Assign a business role — role:Operator, role:Supervisor, role:Technician, role:Quality, role:Planner or role:Admin. This grants the permissions for that job function.
  3. Assign an equipment scope — a site or line role, or tick All equipment. Without it the modules appear but every page stays empty.

Changes take effect on the user's next login.

Workers are not receiving data: how do I diagnose?​

  1. Go to Administration → Workers and check the status column: any worker with a red status is not running or has errors.
  2. Verify the data source configuration (MQTT broker, OPC-UA server, or Node-RED flows) is running and sending to the expected endpoints.
  3. Check the worker logs for connection errors or parsing failures.
  4. Confirm the data tags are correctly configured in Administration → Data Tags and map to the equipment.
  5. If all workers appear healthy but no data arrives, check the network path between the data source and the Docker network.