...

Active batch average dwell time

Looks at the most recent x number of units processed at the specified operation alias for the batch (x is configurable, the default is 10). The next operation in the flow for the active batch is determined. For each unit, an attempt is made to locate a WIP record for the same serial number at the next operation. If found, the Time Completed at Operation 1 is subtracted from the Time Started at Operation 2 for that same unit and the difference is stored. If not found, that unit is skipped and the process is repeated using the second most recent unit to leave Operation 1. The process continues until x calculations are completed successfully or the algorithm runs out of Operation 1 WIP records. The average of all x differences is returned.

...

Active batch effective time per unit

Subtracts the Time Started of the very first WIP record at the operation for the active batch from the Time Completed of the most recent WIP record for the same operation, then divides that result by the total number of WIP records for the batch at the operation. The result is the average production rate across the whole job, including any down time related to breaks or other reasons.

...

Active job components per hour

Looks at all units processed and sums components placed and sums actual cycle time from the ItemSummary table to formulate components per hour. Components per hour = (total components placed / total cycle time) * 3600.

Average cycle time

Averages the cycle time of the most recent x number of units for the active batch for the point (x is configurable, default is 10). Cycle Time for a pair of units is defined as (Time Unit 2 Entered Point) – (Time Unit 3 Work Start at point). The calculation uses the Time Started field of the ItemSummary table.

Average working time

Averages the cycle time of the most recent x number of units for the active batch for the point (x is configurable, default is 10). Working Time for a single unit is defined (Time Work Complete at point) – (Time Work Start at point). For browser WIP records, TimeWorkStart is the same as TimeStarted and TimeWorkComplete is the same as TimeCompleted. For xLink machine data, this is not necessarily the case, it could be that a machine completes work on a unit, but because it is blocked by a downstream machine, it does not leave the machine for another minute or two.

...

An estimate of the time it will take to complete the job at the selected Operation and not to complete the entire route of the batch.

Determines the number of needed units for the Operation (job quantity – distinct WIP count) + scrap overage. This determines the production rate. If the Time Standard option (default) is set to Real-Time the production rate is calculated from the average cycle and will look at the last 10 units processed. If you select Estimated Time, the production rate is calculated from the estimated cycle times. The final calculation is the product of the production rate and the total units needed.

...

Job processing time detail

Displays the serial number, processing time and target time of x number of units processed or in process for all operations of the active batch (defaulted to the top 5 most critical units). Processing Time represents the actual cycle time and also includes the current processing time of any unit started and has not yet been completed. Target time is the estimated cycle time from the Time Standards. The most critical units are the ones with the least time remaining. The key idea behind this output is to show that the time processing is going beyond the time it should take to process. The gauge can be set to show only the active unit which displays only one unit which is the most critical.

Active job completion

Subtracts the number of units that have failed from the number of units processed through the operation to derive at the number of completed units. If the number of completed units is greater than the job quantity, the completed quantity is reduced to the job quantity.

Active Job DPMO (IPC 9261)

Calculates defects per million opportunities at the operation level. IPC 9261 DPMO is (the total defects collected / (the unit count * the operation opportunities) ) * 1,000,000.

...

Active Job DPMO (IPC 7912)

Calculates the defects per million opportunities, at the assembly level. IPC 7912 DPMO is (the total defects collected / (the unit count * the assembly opportunities)) * 1,000,000.

...

Active Batch Defects Per Unit (DPU)

The DPU is the total defect count / the total unit count (configurable to use x number of the most recent units).

Pass Yield

Configurable to use first pass, or second pass yield. Pass yield is calculated using pass unit failures. First pass failures are units that have ever failed and second pass failures are units that have ever been failed more than once. Pass yield is calculated as ((total units – total failed) / total units) * 100.

...

Overall Equipment Effectiveness (OEE)

The product of OEE Availability, OEE Performance and OEE Quality.

OEE Availability

This value reports the percentage of up-time achieved during planned production time during a specified time window. Planned production time is considered all time within the specified time window if zero planned production times have been defined. If one or more planned production times have been defined then the total planned production time is the time within the specified time window that has been explicitly identified as being production time.

...

OEE Performance

Performance is calculated as Ideal Cycle Time / (Operating Time / Total Pieces).

...

OEE Quality

Looks at first pass yield achieved during planned production time during a specified time window.

...