In this report we can find a list of every single downtime and work event. User can choose to see data from any line or area accessible in a plant.
There are columns as:
Loss Detail - Problem name
Average target performance (if any) - defined as weighed average for the duration of each setting (e.g. for downtime 10:00-11:00, if I set 100 car/h for 10:00 - 10:50, and 120 car/h 10:50 - 11:00, the average will be (100*50 + 120 * 10)/60 = 103.33 car/h, assuming ‘car’ is the line production unit)
Actual performance (if any)
Site OEE Report
Site OEE Report contain a list of every single order as well as every single downtime registered in absence of running order. In case of a downtime recorded in absence of a running order, the Order ID field is filled with ‘NO PO’. An order or a downtime not related to an order going across shifts/calendar days splits in different rows (one per each shift/day) with its relative production/duration in such time intervals.
This report got possibility to use different classifications or levels of chosen classification. If standard classification chosen (OEE Loss Types) then it’s assigned to Effective Time, Utilization Loss, Availability Loss, Performance Loss, Quality Loss and Work.
Speed Loss Report
This report contains a list of every single order, with the aim to detail the speed losses on the line. There are collumns as:
Effective time: the ratio between the Good Production output for that order and the line validated speed for the running SKU
Average speed: the average throughput speed recorded for the line order during the Work states, expressed in the same units of the validated speed as recorded in the SKU data
Time lost [hours]: the time lost because of the difference between the Valudated speed and the Average speed of the order, calculated as the difference between the Work state total duration and Effective time
Labour Variance Report
This report contain a list of every single order and detailed collumns as:
Expected Working Hours: calculated by the system based on the information provided in the SKU master data and the actual Good Production
Actual Working Hours: based on the data inserted in the system when confirming the production order
Labour Variance: calculated as the ratio between the difference of Actual and Expected working hours expressed in %. The value is posivite if there is an excess of hours vs. expected and negative if the actual hours are lower than expected.
If an order goes across different days, the date is the order start, no splitting across days or shift.
Site weekly scorecard
This report contains data for whole week, starting from the Week start chosen day and at the local time indicated as Start of the day. It got one row for every line of the site, as well as one row summing up relative values as:
Scheduled Time: the sum of the total duration of all orders of the week, deducted by every downtime
Effective time: the sum of all ratios between the Good Production output of every order and the line validated speed for the respective SKU (converted in the units of the output production if different)
OEE1: the ratio between Effective Time and Scheduled Time (in PackOS it’s TEEP)
OEE1 Target: the OEE target set up for each line under “Production Targets” section (TEEP Target)
Achieved Target: it is populated either with “yes” or “no” if the target has been respectivately either achieved or missed.
On the final row of the report, the total scheduled time and the total effective time of every line is summed up, the OEE is calculated as the ratio between the sum of all effective times and the sum of all scheduled times, the achieved target column contain a total number of lines achieving the target.
In this report user can only choose which week data is coming from - all lines/areas are always included.
Site monthly scorecard
This report is based on a period of a calendar month, starting on the first day of the month at the local time indicated as the Start of the day.
There are 3 columns - line name, measure subject and measure values.
First column have the line name repeated on each row. Third column contain the numerical values expressed in minutes.