====OEE Module==== The **OEE** [[analytic_modules|module]] is part of the [[start|ARDI Visual Analytics]] system, and is used to determine how a particular machine, subsystem or section has been utilised. As well as providing a breakdown of performance, it calculates a single number for //Overall Equipment Effectiveness// that can be used to gauge how well your equipment and your people are performing. ===OEE Accuracy=== If you're trying to calculate OEE, you might need to refer to a wide range of data sources. OEE can be a very misleading number if not calculated correctly, as it summarises a complex system with a number of different components into a single figure. The key is that OEE figures should filter out those times that are //beyond the control of the equipment and the team//. For example, for OEE to be a truly useful measurement, it shouldn't drop during... * Scheduled downtime, * Upstream/supply faults, or * Downstream blockages ===Starting Out=== When you first create a new OEE analytic, you'll see the graph below... {{oee_start.png}} This can look **very daunting**, but if for most users you only need to be concerned with the nodes on the far-left of the graph. {{oee_trinity.png}} These are the key inputs into the logic for OEE - is your asset **Available**, is it **Running** and is it **Required**. The rest of the logic on the graph breaks those three inputs down in to several distinct machine states... * Stopped * Running * Idle * Blocking Where **idle** indicates a machine that is running even though it's not required (this is often inefficient, but not always wrong), and where **blocking** indicates that the machine is needed, but is either unavailable or has failed to run. This logic and the categories themselves can be edited if needed. But in many cases, you can ignore everything other than those three nodes to the left. ===Outputs=== There are two different types of [[final output|output node]] on the graph - a **classification** (the coloured nodes) specifies what state your machine is in. You'll also see that classifications have outputs - these lead to a **runtime** node. This tells the system if that classification should be considered 'good' in terms of OEE (ie. if it should be counted as 'running' or counted as 'offline'). By default, all categories other than //blocking// count towards your OEE. ===Module-Specific Nodes=== [[oee_classify|Classification]] \\ [[oee_runtime|Runtime]] ===Examples=== [[example_oee_basic|Simple Production-Line OEE]]