-
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
To understand the difference between [Waiting] and [Minor Stop], read the definitions in the OEE Industry Standard first!
How can Stopps be identified
When (Minor) Stopps occur, such stopps can be assigned in three ways:
- When it is longer as a certain threshold; the stop can be identified by assigning an activity to it and take it into the availability losses.
- When it is shorter than this threshold; Treat the stopp as a performances loss by assigning it to the minor stopps. Classically this is the difference between the set speed and actual speed. This is described in the OEE Industry Standard
- OEE Coach has a third way to identify short stops as a group, not identifying them individually yet show them as a group in one availability ‘activity’.
How does OEE Coach does this
In the [Master] [Sensors] settings, you may define two intervals (thresholds):
- The threshold for for ‘short stops’
- The threshold for ‘Waiting’ time
Real Waiting Time
When no pulses are detected for longer than the ‘Waiting’ threshold (here 3 min), the machine is considered to be down and the operator needs to identify the reason by choosing a waiting-activity. Since the operator will not do this immediately, this time will be stored in a ‘dummy activity’ as you define under ‘Dummy Waiting’
Short Stopps (in availability)
When no pulses are detected between the ‘short stop’and ‘waiting’ threshold (here between 1 and 3 min), this sop is added to the Short Idle activity, as defined in the top left of the Sensor screen.
Minor Stopps (in Performance)
When no pulses are detected for a period shorter then the ‘Short Idle’ threshold, such stopps are considered to be a performance loss and will not show up in the availability. However, since they decrease the output, we can see them in the difference what would be expected to be produced at set speed and what was actually being produced. This is the way OEE Coach determines (calculates) minor stopps!
How to set thresholds for Minor-, Short and Normal stopps
The above mentioned thresholds and automatically assigned activities can be configured in [Master Data] [Sensors]
See also: How to calculate ‘Performance’