OEE Coach Software Help
-
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
17. Multi batch, parallel output, incl. rejects
In this example
- Shift time: 500 min
- Production Run A: 100 min
- Output 1 45.000 Good (Set Speed 800 pcs/min)
- 5000 reject
- Output 2 38 (Set Speed 0,6 pcs/min)
- 2 reject
- Production Run B: 10 min
- Output 3 4.500 (Set Speed 700 pcs/min)
- 400 reject
- Output 4 5 (Set Speed 0,6 pcs/min)
- 1 reject
- Waiting: 390 min
Result
- Availability 22% (110min/500min)
- Performance: 45,9% (Weighted average!!)
- Quality: 91,7% (Weighted average!!)
- OEE = 22% x 45,9% x 91,7% = 9,3%
Calculation of Performance
- The quality of each product in a run is calculated:
- First run:
- 90%
- 95%
- Second run:
- 91,8%
- 83,3%
- First run:
- The average performance for each run is calculated
- First run: (90+95)/2= 92,5%
- Second run (91,8% + 83,3%)/2 = 87,55%
- A weighted average is calculated for the different runs = 92%
- 100 minutes at 45% and
- 10 minutes at 54,5%:
- ((100/110) * 45%) + ((10/110) * 54,5%) = 45,9%
Warning: Just adding all actual outputs and dividing this by all maximum outputs does not give a correct performance!
Calculation of Quality
- The quality of each product in a run is calculated:
First run:
- 45000 Good/ (45000 Good + 5000 Reject) = 90%
- 38 Good/(38 + 2 Reject) = 95%
Second run:
- 4500 Good /(4500 Good + 400 Reject) = 91,8%
- 5 Good/(5 Good + 1 Reject) = 83,3%
2. The average performance for each run is calculated
- First run: (90+95)/2= 92,5%
- Second run (91,8% + 83,3%)/2 = 87,55%
3. A weighted average is calculated for the different runs:
- 100 minutes at 92,5% and
- 10 minutes at 87,585%:
- ((100/110) * 92,5%) + ((10/110) * 87,585%) = 92,05%
Warning: Also the quality rate is a weighted average! Just adding all good outputs and dividing this by all actual outputs does not give a correct quality rate!