In Enterprise Asset Management, you can calculate costs to get an overview of actual costs compared to budget costs on objects, functional locations, or work orders. Actual costs are based on posted transactions. You can also make a date calculation if you want to compare scheduled start and end dates to actual start and end dates on work orders.
The calculations made for objects, functional locations, and work orders are almost identical. Only difference is that for objects and functional locations, you can also include sub objects and sub locations in your calculation. The date is the transaction date when the registration was recorded.
Another way of making a cost calculation is to multi-select objects in All objects or Active objects grid view. Then, you click the Cost control button > Cost control > Calculate cost, and you will see that the selected objects are automatically inserted in the Object field on the Records to include FastTab. Click OK in the Object cost control drop-down, and a cost calculation for the selected objects is shown. The same procedure can be done for functional locations in All functional locations or Active functional locations, and for work orders in All work orders or Active work orders.
Note
The Original budget field shows budget costs from the work order forecast. The Committed cost field shows the total amount of expenses that a legal entity has committed itself to pay. The Open committed cost field shows commitments to pay for items, hours, and services you have ordered or received but not yet paid for. When all consumption registrations have been posted, the related costs are included in the Actual cost field.
In the Cost Control section, you can read more about the cost control workspace, in which cost registrations can be displayed graphically in various views and detail levels.
Use this form to get an overview of expected start and end dates compared to actual start and end dates on work orders. Select a period for the calculation, then select the information you want to display by selecting the check boxes in the Group by section, and click Calculate.
Note
The Avg. start delay field shows the difference in days between scheduled start date for a work order compared to actual start date. If, for example, the actual start date was two days before the scheduled start date, "-2" will be displayed in this field.
The Avg. end delay field shows the difference in days between scheduled end date for a work order compared to actual end date. If, for example, the actual end date was three days after the scheduled end date, "3" will be displayed in this field.
The Occurrences fields show the number of times deviations occur in relation to scheduled and actual start date, and scheduled and actual end date on the work order.
In Enterprise Asset Management, you can calculate hours to get an overview of actual hours compared to budget hours on objects, functional locations, or work orders. Actual hours are based on posted transactions.
The calculations made for objects, functional locations, and work orders are almost identical. Only difference is that for objects and functional locations, you can also include sub objects and sub locations in your calculation. The date is the transaction date when the registration was recorded.
Another way of making a cost calculation is to multi-select objects in All objects or Active objects grid view. Then, you click the Hour control button > Hour control > Calculate hours, and you will see that the selected objects are automatically inserted in the Object field on the Records to include FastTab. Click OK in the Object hour control drop-down, and an hour calculation for the selected objects is shown. The same procedure can be done for functional locations in All functional locations or Active functional locations, and for work orders in the All work orders or Active work orders.
Note
The Original budget field shows budget hours from the work order forecast. The Actual hours field shows posted hours on work orders. The Committed hours field shows total amount of hours that your company is committed to in relation to work orders.
In Enterprise Asset Management, you can calculate costs on object fault registrations to get an overview of actual costs compared to budget costs on faults. Actual costs are based on posted transactions. The date is the fault date on which the symptom was recorded.
Refer to the Fault Management section for information on how to set up faults.
Note
The Original budget field shows budget costs from the work order forecast. The Actual cost field shows posted costs on work orders. The Committed cost field shows total costs that your company is committed to in relation to work orders.
In Enterprise Asset Management, you can analyze object fault registrations to get an overview of the total number of faults registered during a specific period. Fault registrations can be analyzed from different perspectives, for example with focus on objects, object types, functional locations, fault symptoms, or fault types.
Note
Every time you activate or deactivate buttons in the Group by... action pane groups, remember to click the Update button after you have changed the selections. This is required because a large amount of data is processed as you are recalculating fault probability.
There are many ways to analyze fault registrations. Below you will see examples in five screenshots of how different data selections provide different pieces of information. You will see how different selections provide more insight and detail when analyzing object fault registrations.
In the figure 1 below, the Symptom button is selected.
In the figure 2 below, Year and Month are added to show how you can view fault registrations during a selected period.
Note
The combination objects and an object type is used as a basis for the calculations shown in the three screenshots below, which will increase in detail level.
Generally, the buttons in the Group by date, Group by object, Group by functional location action pane groups, as well as the Fault button (Fault ID), contain periods or object relations. The Fault symptom, Fault area, Fault type, Fault cause, and Fault remedy buttons are categorizations used in Enterprise Asset Management fault management to analyze object fault registrations and pinpoint problem areas.
In the figure 3 below, Object and Object type were added to provide more detail regarding fault registrations.
In the figure 4 below, Area was added to Symptom, Object, and Object type to provide more detail regarding fault registrations.
In the figure 5 below, Type has been added, and the most detailed calculation in this example is shown.
In Enterprise Asset Management, you can calculate various Key Performance Indicators (KPIs) for objects and object types. KPIs are used to get an overview of performance on objects in relation to, for example, uptime, downtime, repair time, and Mean Time Between Failure (MTBF).
In the table below, you will find a short explanation of the fields in Object KPIs.
Field | Description |
Object | Object ID |
Total time | Total time set up in the calendar used in the calculation. If the object is related to a resource, the related resource calendar is used. If the object is not related to a resource, the calendar selected in the Standard calendar field in Enterprise asset management parameters is used. |
Uptime | Total time minus downtime. |
Downtime | Production stop registrations made on the object in the selected period. |
Repair time | Total number of work hours consumed on repair work orders. |
Availability % | Uptime divided by total time and multiplied by 100. |
Number of faults | Number of fault causes registered on fault symptoms on the object in the selected period. |
MTBF | Mean Time Between Failure, which is total time divided by number of faults registered on the object in the selected period. If number of faults is zero, MTBF is set to total time. |
Fail rate | 1 divided by MTBF. |
MRT | Mean Repair Time, which is repair time divided by number of faults registered on the object in the selected period. If number of faults is zero, MRT is set to repair time. |
Number of stops | Number of production stops registered on the object. |
MTBS | Mean Time Between Stops, which is total time divided by number of production stop registrations. If number of production stop registrations is zero in the selected period, the MTBS value is set to total time. |
MTPS | Mean Time Production Stops, which is production stop time divided by number of production stop registrations. If number of production stop registrations is zero in the selected period, the MTPS value is set to zero. |
Preventive cost | Costs posted on the object related to cost type "Preventive" in the selected period. Cost types are set up on work order types. |
Corrective cost | Costs posted on the object related to cost type "Corrective" in the selected period. Cost types are set up on work order types. |
Replacement value | Value defined on the object as the replacement cost. |
Object type | Identification of the object type selected on the object. |
Product | Identification of the product selected on the object. |
Model | Identification of the product model selected on the object. |
From date | Start date of the KPI calculation. If the object was created after the start date selected for the calculation, the start date of the object is shown in this field. |
To date | End date of the KPI calculation. If the object was registered as inactive before the end date selected for the calculation, the date from which the object was no longer active is shown in this field. |
Time scale | During calculation of the KPIs, you select a time scale to be used: Hours, Days, or Weeks. |
Availability | Uptime divided by total time. |
Work orders | Total number of work orders included in the KPI calculation. |
Work order time | Total number of work hours consumed on the work orders. |
Primary work orders | Number of primary work orders included in the KPI calculation. |
Secondary work orders | Number of secondary work orders included in the KPI calculation. |
Maintenance work orders | Number of maintenance work orders included in the KPI calculation. A maintenance work order is a work order with no related fault causes. |
Maintenance time | Total number of work hours consumed on maintenance work orders. |
Repair work orders | Number of repair work orders included in the KPI calculation. A repair work order is a work order with a related fault causes. |
Reliability % | Calculation based on the expected exponential development in fault registrations on an object meaning that, over time, the object becomes less reliable due to wear and tear. The calculation of this KPI is based on MTBF and total time. |
Total cost | Total costs posted on the object in the selected period. |
Investment cost | Costs posted on the object related to cost type "Investment" in the selected period. Cost types are set up on work order types. |
Note
You can multi-select several objects in All objects and click the Object KPIs button on the General tab. Then, click Calculate in Object KPIs to calculate KPIs for the selected objects.
Results from a KPI calculation may or may not include production stop registrations, depending on the setup and use of production stop types. Read more about production stops in the Production Stop section.
You can make a calculation for a specific item to get an overview of where in Enterprise Asset Management the item has been used. The results show the context in which the item has been used during its lifetime. The Item where used form can be opened from the main Enterprise asset management menu, and it can also be accessed from the following grid views and detail views:
In Enterprise Asset Management, you can make a calculation to see an overview of new, active, and completed requests, work orders, and production stops for a specific period. You can also see the number of completed condition assessments for the same period. You can use these calculations to get an overview of workload regarding incoming and completed requests and work orders.
Note
You can use the Level field to indicate how detailed you want the maintenance lines to be regarding functional locations. For example, if you insert the number "1" in the field, and you have a multi-level functional location hierarchy, all maintenance lines for a functional location will be shown on the top level, and therefore the status on a line may be added up from functional locations located at a lower level. If you insert the number "0" in the Level field, you will see a detailed result showing all maintenance lines on all the functional location levels to which they are related.
Note
The results shown in Maintenance status only include requests and work orders that have an actual start and date and time. End date and time may be blank.
Example 1:
In the first figure below, only the Year and Month fields have been activated. Here you can get a general overview on a monthly basis of workload and throughput related to requests and work orders.
Example 2:
In the second figure below, information about functional locations has been added. Now, it is possible to compare workload and throughput across functional locations, which may represent, for example, geographical locations, factories, or different work areas.