|
<< Click to Display Table of Contents >> Manual > Monitoring system construction guide > Construction of major functions > Operation monitoring > Function explanation > How various figures are calculated |
How various figures are calculated
The calculation methods for various values calculated by the operation monitoring function are as follows:
item |
explanation |
Formulas, notes, etc. |
Occupancy rate (%)
|
The production monitoring feature uses time-based availability rates and allows you to choose one of the following methods:
■ Calculate from time summary
With this method, you can freely select which of the four aggregation categories, "operating time," "stopped time," "abnormal time," and "other time," to include in the total time. The default setting is Total Time = Operating Time + Stopped Time + Abnormal Time + Other Time, which is the following calculation formula.
Availability rate = Uptime / (Uptime + Downtime + Abnormality time + Other time) * 100
■ Calculate from a fixed value
In this method, the operating rate is calculated by specifying a preset fixed value in minutes. For example, if you want to fix the total time in a day to 24 hours, specify 1440 minutes. |
Uptime = Uptime / Totaltime * 100
Or,
Availability = Operating time / Fixed value * 100
|
Progress rate (%)
|
It indicates the progress of production results against production targets. |
Progress rate = Production result / Production target * 100
|
Takt Time
|
This is the time (unit: seconds) obtained by dividing the operating time by the production result. It indicates the time required to produce one product. |
Takt time = Operating time / Production results |
Production variance
|
This is the difference between the production result and the production target. It shows the remaining quantity against the target number. |
Production variance = Production target - Production actual
|
Uptime
|
This is the ON time for the day in the operating state registered with the aggregation classification as "operating" (unit: minutes). This time is calculated according to priority. For example, if multiple operating states are registered for the same aggregation classification and multiple conditions are met at the same time, the ON time of the operating state with the highest priority will be added. For details about the priority of operating states, please refer to "About Priority of Operating States". |
- |
Abnormal Time
|
The ON time for the day when the operation status is "Abnormal" (unit: minutes). As with the operation time, the time is calculated according to the priority. |
Abnormality rate = Abnormal time / (Operating time + Downtime + Abnormal time + Other time) * 100 |
Downtime
|
The ON time for the day when the device is in the "operational stop" status (unit: minutes). As with operating time, the time is calculated according to priority. |
Outage rate = outage time / (operation time + outage time + abnormal time + other time) * 100 |
Other time
|
The ON time for the operating status of the "Other" tabulation category on the current day (unit: minutes). As with operating time, the time is calculated according to priority. |
Other rate = Other time / (Operating time + Stopping time + Abnormal time + Other time) * 100 |
Number of times of operation
|
This is the total number of times that an operation status registered with the count classification "operating" was ON on the day. Priority is not taken into account when calculating the number of times, and the ON counts of all operation statuses that belong to the same count classification are added together. |
- |
Abnormal count
|
This is the number of times that an operating status belonging to the counting classification "Abnormal" was ON on the day. As above, priority is not relevant. |
- |
Number of stops
|
This is the number of times that the operating status belonging to the counting classification "operation stopped" was ON on the day. As above, priority is not relevant. |
- |
Other times
|
This is the number of times that the operating status belonging to the "Other" classification was ON on the day. As above, priority is not relevant. |
- |
Longest continuous operating time
|
The longest continuous ON time during the operating hours of the day (unit: minutes). The concept of priority is the same as for operating hours. |
When selecting data on the operation status monitor screen, it is displayed as "Continuous operation time." |
Longest continuous abnormal time
|
The longest continuous ON time during abnormal hours on the day (unit: minutes). Priority is determined in the same way as for operating hours. |
In the data selection on the operation status monitor screen, this is displayed as "Continuous abnormal time." |
Longest continuous stop time
|
The longest continuous ON time during the downtime of the day (unit: minutes). The priority is the same as for the operating time. |
When selecting data on the operation status monitor screen, this is displayed as "Continuous stop time." |
Longest continuous other time
|
The longest continuous ON time during other times on the day (unit: minutes). Priority is the same as for operating hours. |
When selecting data on the operation status monitor screen, this is displayed as "Continuous other time." |
ON time 1 to 10
|
Displays the ON time for each operation status on the day (unit: minutes). The number at the end of the item name is the status ID for each operation status registered on the "Operation Status Collection Settings" screen. These times are also calculated according to priority, just like operation times. |
- |
ON count 1 to 10
|
This is the number of times each operating state was ON on the day. The number at the end of the item name is the status ID of each operating state registered on the "Operating Status Collection Settings" screen. Priority is not taken into account when calculating the number of times, and the number of times each operating state was ON is added. |
- |
|
The calculation of "Longest continuous operating time," "Longest continuous abnormal time," "Longest continuous stopped time," and "Longest continuous other time" may have an error of a few seconds depending on the timing of internal processing. |