-
Install Hardware
-
Install Software
-
Access & Rights
- How to obtain a LICENSE
- How can I access OEE Coach the first time
- How to give Users Access on Screens & Computers
- How to configure USER-ROLES
- How to configure USERS
- How to configure VIEW PER COMPUTER
- How to set SYSTEM PREFERENCES
- How to set USER PREFERENCES
- Automatically adding activities
- How to use SEMI-AUTOMATED MODE
- How to CLOSE and LOCK a shift
-
Configure Masterdata
- Defining a 'MACHINE'
- How to add a new 'MACHINE'
- Methods to enter output data
- How to define GROUPS of machines
- How to use 'SHIFTS'
- How to use 'TEAMS'
- What are 'UNITS OF MEASUREMENT'
- What are ‘EQUIVALENT VALUES’
- How to define and use ACTIVITIES
- How to (re)use Activities in Mastertable
- What kind of ACTIVITIES can be defined
- What is the difference between [W]AIT and [U]NSCHEDULED
- How to define OUTPUT (='Products')
- How to calculate 'PERFORMANCE'
- What is the Maximum Speed of the Machine
- How to define Maximum Speed: NPC and ‘Standard’
- How to deal with short (‘Minor’) stoppages
- What is OEE Top?
- What is the 'Quality Rate'
- What categories of QUALITY are there
- How to link a Machine to Activities and Products (MAP)
- How to Change, add and remove parameters in MAP
- Why to visualize ALL losses
- Can OEE be used as a system for failure logging
- How to CHANGE SPEED in existing calculations RETROSPECTIVELY
- (How) can I change an existing Activity- or Producttype?
- How to allow Parallel Output
- How does the OEE Coach data collection mechanism work?
- How to CONFIGURE the SENSOR(s) in OEE Coach
- How to distinct Short Idle from Minor Stopps
- How to configure the Shift Planner module
- Show all articles ( 16 ) Collapse Articles
-
Enter Data
- How to register a shift
- What are ACTIVITIES during a shift
- What are the 3 Modes of registration
- How to add ACTIVITIES to a SHIFT
- How to MODIFY Activity Data
- The AVAILABILITY SUMMARY
- How to handle deviant shift lengths
- What if Shifts/Batches run >24 Hrs
- How to ADD OUTPUT to an activity
- How to handle multiple product runs in one shift
- How to handle a run where only scrap is produced
- The PERFORMANCE SUMMARY
- The Quality Summary
- The OEE Calculation
- The registration dashboard
- How to use ACTUAL vs PLANNED OPERATORS
- How to CLOSE and LOCK a shift
- What is the ANDON SYSTEM
- Error Detection & Validation System for Incorrect Input
- How to use the Calendar
- (How) can I change an existing Activity- or Producttype?
- How to use ORDER and BATCH numbers
- How to (re)use Activities in Mastertable
- AUTOMATIC MODE data collection
- Show all articles ( 9 ) Collapse Articles
-
Modify - Delete data
-
Validate Data
- Articles coming soon
-
Analyze-Report Data
- Printing a SHIFT-REPORT at end of shift
- What is the ANDON SYSTEM
- Error Detection & Validation System for Incorrect Input
- What are ANALYSES and what are REPORTS
- Features of the ANALYSES SCREENS
- How to PRINT or EXPORT charts
- How to use the Calendar
- What is the difference between STATIC and DYNAMIC analyses
- Analysis: EFFECTIVENESS
- Analysis: EFFECTIVENESS in Time
- Analysis: ANDON
- Analysis: AVAILABILITY
- Analysis: AVAILABILITY in Time
- Analysis: OUTPUT in Time
- Analysis: PRODUCT PERFORMANCE
- Analysis: BATCH PERFORMANCE
- Analysis: QUALITY
- Analysis: COMPARE CHARTS
- Show all articles ( 3 ) Collapse Articles
-
Support
-
Calculation Examples
- How are Calculations made; Examples
- 1. Registered time << Shift time
- 2. Actual Output = Max Output
- 3. Speed Loss
- 4. Minor Stops
- 5. Speed Loss and Minor Stops
- 6. Good product and Reject
- 7. More output than expected
- 8. Two sorts of Reject with one Product
- 9. Three sorts of Reject with one Product
- 10. Three Rejects; output > expected
- 11. Two runs with parallel output
- 12. Two runs, two products, two performances (speed loss)
- 13. Two runs, two products, two performances (minor stops)
- 14. Two runs, two products, two performances (minor stops+ speed loss)
- 15. Calculating Quality
- 16. Calculating Quality; extreme example
- 17. Multi batch, parallel output, incl. rejects
- 18. Multi batch, parallel output with rejects: entry errors
- 19. Multi batch, parallel output, extreme output
- 20. Multi batch, parallel output, multiple rejects
- 21. Multi batch, Slow and Fast, Multiple rejects
- 22. Multi batch, parallel output with rejects: entry errors
- 23.
- 15. Calculating Quality
- Show all articles ( 10 ) Collapse Articles
-
(Daily) Management
-
Setting Preferences
-
Integration
-
ERP Feeder Module
-
ERP/OPC Reader Module
-
Shiftplanner Module
-
Financial Module
-
Report Mailer Module
-
Energy Module
AUTOMATIC MODE data collection
OEE Coach has 3 modes to register data (read the ‘automatic mode’ section first, and make sure to configure the sensor settings and default activities/product first!)
Behavior in automatic mode
- Current time is used to register ‘what happens when’.
- The time window of the current shift needs to be around the current time (you can not register current events in a shift of yesterday or tomorrow).
- When pulses are received from the sensor, they need to be stored somewhere:
- A [P]roduction activity needs to be present or started.
- When the sensor initiates the start of a [P]roduction activity, the default (dummy) activity and product
- No [W]ait, [F]ailure or [U]nscheduled can be started while the machine is receiving pulses.
How are default activity and product used
When a sensor starts to give pulses, the count of these pulses needs to be stored with a [G]ood product during a [P]roduction activity. So what happens when the current activity is [Pause] (a [W]aiting activity?)
Default (dummy) product
OEE Coach automatically stops e.g. the [Pause] activity and starts the Production activity that goes along with the product you assigned in the sensor configuration masterdata screen.
When there is just one product running on the machine, put this one here as the default. In other cases, make a dummy product in the product master table, add it to the machine in the MAP end select it here.
By choosing a meaningful name, it is clear that this dummy product needs to be changed later to identify the actual product that was produced. (E.g. ‘give the correct productname’)
Default (Dummy) [W]aiting activity
When there is no more sensor signal detected, after the given ‘short Idle threshold’ (often 1 minute) an activity with the Short Idle label is added.
So in the example above, after 1 minute inactivity the short-idle activity is added.
When the machine remains idling, after 3 minutes (the ‘Waiting threshold’ is passed) the idle activity is replaced by the default waiting activity;
It is NOT possible to give any Idle activity when the machine is running.