-
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
What is the purpose of the ERP Feeder
This module sends live OEE data to business systems such as ERP, CMMS, MES and others.
This allows other systems to make live use of OEE data such as machine status, production volumes, etc.
This module is the antagonist of the ERP/OPC Reader, where OEE data are sent from an external OPC or MES/SCADA/ERP system to OEE Coach.
Why send data from the OEE system to ERP and not the other way around?
Because of the built-in plausibility rules in OEE Coach and the correction of any erroneous data directly at the source, the OEE data usually turns out to have a much higher correctness than data that would otherwise – without plausibility rules – have been obtained.
To avoid duplicate data entry, data can be transferred from OEE Coach directly to other systems.
How it works.
With every status change of the machine, a status update is sent to the external system.
As long as the machine is in a particular status (for example, [P]roduction or [F]ailure, ongoing data (such as time, volume, comments) can also be updated to the external system.
The user can specify which statuses are forwarded and which are not.
For example, you could forward only status changes for [F]ailure to be used subsequently In the (CMMS) maintenance system.
Whether the data is processed live in the external system or retroactively you choose, as well as how.
The ERP feeder fills each new activity during a running shift with relevant data in an SQL table.
Example
When the machine breaks down, the following line is added to the status table:
- Start date and time
- End date and time
- Machine Name
- Shift Name
- Team Name
- Category (P/W/F/L/U)
- Activity Name
- Order Number
- Scheduled operators
- Actual operators
In case the operator makes a change on his screen during this activity, the change will also be applied in the status line.
End time
As long as this status is current (so there is no new status yet), the end time is equal to the current time. Only when a new activity is registered, the end time of the activity will be recorded.