-
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 are the 3 Modes of registration
In [Master] [Machines] you select (per machine) the level of automated behavior while collecting data for a certain machine:
Manual, Semi-Automatic and Automated
1 – Manual Mode
Use this mode when manually entering all activities retrospective e.g. when using paper registration forms
- You will have to tell the system in sequence of occurrence what happened (which activities) and what came out (which good or rejected products).
- You will need to enter durations and quantities manually: No timer will be started.
- The system will take care the activities will for a closed time-line. In other words: it will try to prevent time to be forgotten.
2 – Semi-Automatic (Default mode)
This mode is used to automatically register elapsed time, allowing the operator to modify the actual start time or duration, since he may not always be able to select the activity at the moment it actually started (i.e. he was still busy operating the machine, causing a delay in the moment of registration.)
After adding a new activity in a shift where the date and time are at the current moment:
- After 60 seconds, the timer will calculate the elapsed time since the last entered activity unless the duration is entered manually.
- An indicator blinks to identify the timer is counting.
- The system will keep counting time until you enter a new activity.
- Output has to be entered manually.
3 – Automatic mode
This mode applies when a sensor in automatic and/or unmanned mode is automatically triggering the activity. Automatically collected data can be modified retrospective whenever needed
During a shift with date- and time in the current moment, activities will automatically be added, based on the settings in [Default M-A-P], (see menu [Master]) depending on the signal received from a sensor.
- Activities are started by sensors
- The timer starts immediately after an activity has been added. This assumes the start time of the new activity, and thus the duration of the previous one, was correct and needs no manual correction.
- output is counted based on sensor pulses
generated activities may need to be corrected by operator.