OEE 2.0 offers many new features to help maximize manufacturing effectiveness.
These new features include:
Built on ISA-95
The OEE 2.0 module is built in compliance with the ISA-95 standard that provides a consistent terminology for supplier and manufacturer communications, information and operations models for clarifying application functionality and how information is to be used. It uses the same object model as the Track & Trace module to provide seamless integration between your lot tracking, production control and downtime tracking solution.
Refer to ISA-95 Overview for more information.
Enhanced Production Scheduling
Scheduler is now based on the same components as the Track and Trace module providing Work Order Drag and Drop capability, Auto-Delay feature, custom categories (hold schedule) and routes.
Refer to Production Scheduling & Dispatch for more information.
OEE 2.0 now provides support for using the Ignition Schedule Management component for creating complex and composite shift rotations. However if you need something different, you can simply provides us the shift information via a tag and we’ll associate that piece of information along with the production data we capture.
Refer to Shift Configuration for more information.
OEE 2.0 module now provides support for creating Equipment Modes. You can now track production line or area utilization by IDLE TIME, CHANGEOVER, PRODUCTION, MAINTENANCE, TRAINING, TESTING, even custom modes, and decide if they are to be considered in the OEE calculation.
Refer to Equipment Modes for more information.
Equipment States represent the status of the equipment that provides an indication of whether the equipment is offline, idle, running, faulted, blocked, starved, in CIP etc. It is entirely separate from the equipment mode, which provides a logistical view of intended purpose.
The equipment status will generally come from a PLC tag that provides real-time state information of the equipment, but can really come from any source that can populate an Ignition tag. This allows for manual entry screens of operator input equipment state or data parsed from a flat file entry.
Refer to Equipment States for more information.
Downtime Detection Modes
Key Reason Detection now supports primary cells anywhere within a line. Select a process cell in your line that you consider the bottleneck or primary cell and set that to Key Cell. As long as your primary cell is running, OEE will consider the production line to be running, but if your primary cell goes down, OEE will determine which piece of equipment is blocking or starving your primary cell and record that as the cause of the line down.
Refer to Downtime Detection Mode for more information.
Data Capture and Runtime Monitoring
Equipment Mode, State, counts, shift and standard rate tags are always monitored and recorded. Never miss another production run because a run wasn’t scheduled. You can now create multiple ‘live’ OEE values for user defined time periods. How often these values are updated is now user configurable and uses an optimized cache to provide real-time values that can be displayed for run-time monitoring. Users will now be able to see real-time OEE metrics and production counts updated as often as they want.
Refer to Live Analysis for more information.
Work-Center and Sub-Line OEE Operation
Share OEE Analysis with the Analysis Engine
New analysis engine is simplified and optimized to provide faster, more powerful analytics aggregating data from all MES sources as well as any custom value sources. OEE analysis now occurs on-the-fly and can be shared with other systems and web reporting tools using built-in system functions. Criteria can be changed to reflect the OEE based on your selection. Stored analysis now supports user security and ability to promote reports to the public domain.
The Impromptu Analysis components have been revamped to provide user security by stored analysis as well as the ability to promote user analysis reports to the Public Domain.
Built-in system functions will provide a scripting method for running a stored ad-hoc analysis and pushing that data out to a user configured database table. This can be done from a gateway timer, tag change event, etc. or through a web service call to allow the sharing of OEE analysis with other systems and Company Web Reporting tools.
Refer to Analysis and Reporting for more information.