Applications
JavaFX Applications
Designer Application
The Designer configures all aspects of equipment in order to enable OEE calculations. It has editors for defining the plant model, reasons, materials, units of measure and work schedule.
Design-time data can also be backed up and restored or imported from a file. The Designer can also display a dashboard for the selected equipment.
The Designer and Monitor have a trending capability to observe the input and output values of a configured data source. In this example, OPC DA.
Collector Application
The Collector application runs as a Windows service or Unix daemon on the configured host computer. A Collector executes equipment event resolver scripts upon receipt of an input value and stores the availability, production, material or job change event data in the database. This data is used for OEE, MTBF and MTTR calculations.
Monitor Application
The Monitor application has three main functions, to observe:
- Equipment performance via metrics available in the dashboard.
- Notifications from the data collectors for abnormal conditions
- Data collector status
An example of dashboard tiles is:
Production and availability events can be shown in chronological order, for example:
Production and availability events can also be shown in a trend chart, for example:
The time-losses tab shows a bar chart of the OEE loss categories:
A first-level Pareto chart show the time losses in percentage terms, for example:
A second-level Pareto displays the reasons for an availability category, for example for Minor Stoppages:
Operator Desktop Application
The Operator application is a desktop application that allows a user to enter availability, performance, production, material change and job events. The events can be recorded in chronological order as they happened or in summary form over a period of time by duration of the event.
Flutter Applications
The Flutter/Dart applications allow a user to enter availability, performance, production, material change and job events. The events can be recorded in chronological order as they happened or in summary form over a period of time by duration of event. A demonstration HTTP server is running a Collector at IP address 52.37.56.187 on port 8182 hosted on AWS Lightsail.
iOS Mobile Application
Below are screen shots of the home page showing the plant entity tree, availability page for entering equipment events, production page for entering produced material quantities and the equipment setup page:
Android Mobile Application
The Android screens are similar to the iOS screens. For example, the home entity and availability pages are:
macOS Application
The screen capture below is from the macOS application home page:
Windows Application
The screen capture below is from the Windows application home page:
Linux Application
The screen capture below is from the Linux application home page:
Chrome/Edge Application
The screen capture below is from the Chrome/Edge application home page:
Vaadin Application
The Operator web application is browser-based and allows a user to enter availability, performance, production, material change and job events. The events can be recorded in chronological order as they happened or in summary form over a period of time by duration of event.
Below is the screen for entering summarized availability data.
