An object has an object type attached to it. The object type defines which job types, meaning which maintenance jobs, can be carried out on an object. When you create a work order, selecting a job type is mandatory. It is only possible to select the job types that are related to the object type setup used on the object.
Refer to the Overview chapter for a graphic outline of objects and job types, and their connection to a work order.
Job variants can be set up on a job type. Job variants define variations of a job type, for example, size (small, medium, large), periods (weekly, bi-weekly, 1 month, 3 months), and configurations (low standard, flexible, high performance).
Job trades are information regarding professional trade, for example, mechanical, electrical, and hydraulic. Competency requirements can be set up on a job trade. All job trades can be used in relation to all job types. Selecting job variant and/or job trade on work a order is optional.
For each job type, variations of job type setup can be created. Example: If you have a job type called "Service", you can create variations for that job type relating to "Trucks 30,000 km", "Cars 30,000 km", and "Vans 30,000 km".
Job groups are used to collect a group of job types for overview purposes. Examples could be "Calibration", "Inspection", "Overhaul", and "Instrumentation".
First, you set up the required job groups, job variants, and job trades. Next you create job types. Then, you create all the variations of job types that are required for your equipment in Job type setup. Forecasts, checklists, and tools can be set up for a combination of job type in Job type setup.
Note
A job type can only be related to one job group
Note
If you add more than one job type line, the sequence of the lines indicate the order in which they should be carried out, starting from the top of the list.
When you have related job groups to job types, you will see how many job types are related to the job group in the Job types field.
In the situation where you have multiple job type setup lines in the Job type setup' form and you want to handle a lot of data, you can change the layout to optimize the performance of the form. See the section Job type setup improvements below. Otherwise, you can follow the steps here from 1-32.
Note
If you want to copy a forecast setup from another job type, select the Copy forecast button and select the job type from which to copy the setup.
Note
If you want to copy checklist setup from another job type, click the Copy checklist button and select the job type from which to copy the setup.
You can easily create a template from an existing checklist, which can be reused across multiple checklists. The new template will be an exact copy of the active checklists. Click the Create template button and insert a Name for the template. You can set the Replace toggle button to "Yes" to replace the existing checklist with a single line referencing the new template. You can see the contents of the template in the Checklist templates detail view.
Note
If you want to copy a tool setup from another job type, select the Copy tools button and select the job type from which to copy the setup.
Note
If a description is added, that description overrules a description set up on the job type. If no description is added in this form, the description, if any, in Job types is used. Descriptions are automatically transferred to work orders using the job type or job type setup.
Note
Attachments on a job type setup line are only printed with a work order report if the document types of the attachments are selected in Enterprise asset management > Setup > Enterprise asset management parameters > Document types.
Examples of attachments could be a guideline explaining how to complete a specific job, or a predefined checklist (if you do not use the checklist functionality for job type setup lines).
When the system selects the available job type setup to be used on a work order line, the selection is based on the object and the related object type setup. Enterprise Asset Management goes through all job type setup records related to the job type, which is related to the object type, to check for a possible match, always checking the most specific combination first. This means that, first, a possible match regarding Trade is checked. If no match is found, Variant is checked. If no match is found, Job type is checked, and so on. As you can see in the layout of Job type setup, this means that Enterprise Asset Management checks each record from right to left for a match (Trade, then Variant, then Job type, Object, Model, Product, and Object type to find the most specific combination. If no match is found, the "default" record is used in which only the job type is selected.
Note
For each job type setup line you create, a project activity ID is automatically related to the line. The project activity is created on the forecast project selected in Enterprise asset management parameters > Objects link > Forecast project field. The purpose of the project activity is to manage forecasts on hours, items, and expenses in relation to work orders. Job type forecasts are automatically transferred to the work order line, and they are copied from the forecast project to the work order project created for the work order line. The purpose of the project activity is to manage forecasts in relation to work orders.
A batch job can be set up to update job type setup references to run manually or at regular intervals. Click Enterprise asset management > Periodic > Preventive maintenance > Update job type setup references to create a batch job or run a manual update.
In the situation where you have multiple job type setup lines in the 'Job type setup' form and you want to handle a lot of data, you can change the layout to optimize the performance of the form.
To enable the new feature improving performance for the 'Job type setup' form, go to the 'Feature management' workspace and then find and enable the feature called Dynaway - Performance improvements for job type setup form.
With this feature enabled, the layout of the 'Job type setup' form is changed so that fields using display methods are moved from the grid to the 'Statistics' form part on the right (This can be seen in the screenshot Improvements to the 'Job type setup form' below). This change significantly improves the performance of the 'Job type setup' form.
When you have created the required job type setup combinations, it is possible to get an overview of the current job type setup related to a specific object in All Objects. The overview shows a combination of all job type setup combinations that can be used on the object type selected on the object, including combinations with variations of job variants and job trades.
In Enterprise Asset Management, you can automatically update any changes in job type forecasts regarding hour costs, item costs, and expenses, which have been updated in other modules in Dynamics 365 for Finance and Operations. This is done to ensure that the latest cost prices are always used in your job type forecasts. It is also possible to make similar updates for work order forecasts.
Checklist templates and checklist variables are used for setup of checklists. Checklists are set up on job types and used on work orders.
When you create checklist lines in the job type setup, you must select a checklist type. "Variable" is a checklist type. It is used to define a possible result in a range on a checklist line, which is related to a work order line. A variable is a way to create a set of predefined outcomes without having to make an exact measurement.
Example 1: You can measure oil level by defining 'Level too high', 'Level too low', and 'Level within range'. For each of the three values, you define if the value result is "Pass", "Fail", or "None".
Example 2: Make a visual inspection or assessment of a piece of equipment regarding wear and tear.
Checklist templates can be used as a common set of tasks that a worker must perform in order to complete a work order correctly. The templates are referenced from checklist lines on the job type setup. Templates can be referenced across multiple job type setup lines, making it easy to reuse a set of common checklist tasks. Examples include general safety instructions, or a list of items and conditions to be checked on a specific pump or similar models of a conveyor belt.
Note
The "Measurement" type without a counter setup is treated as an independent measurement registration for which there is no automatic follow-up in Enterprise Asset Management. Likewise, if the selected counter type is not present on the object related to the work order, the checklist task is handled as an independent measurement. The counter value can be changed multiple times; it will not be posted until the work order stage is changed to a stage in which the Process checklist toggle button is set to "Yes".
Work order stages define the stages that a work order can go through, for example, Created, Scheduled, In progress, and Ended. Work order stages may be updated manually on a work order, or they may be updated automatically, for example during work order scheduling.
The work order stages required for your work orders must be attached to matching project stages in the Project management and accounting module > Project management and accounting parameters. First, you set up project stages in Project management and accounting, then you set up work order stages and stage groups in Enterprise Asset Management.
Here is a short description of the toggle buttons in Work order stages > General FastTab > Work order and Schedule sections:
Field name | Description |
---|---|
Active |
Select "Yes" if the work order should be active at this stage. |
Add line |
Select "Yes" if it should be possible to add work order lines to a work order at this stage. |
Delete |
Select "Yes" if it should be possible to delete a work order at this stage. |
Delete line |
Select "Yes" if it should be possible to delete work order lines on a work order at this stage. |
Allow scheduling |
Select "Yes" if it should be possible to schedule a work order at this stage. |
Set actual start |
Select "Yes" to ensure that when a work order is updated to this stage, the user is asked to select an actual start date and time for the work order. |
Set actual end |
Select "Yes" to ensure that when a work order is updated to this stage, the user is asked to select an actual end date and time for the work order. |
Post journals |
Select "Yes" if work order journals should be automatically posted at this stage. If journal posting results in an error, an Infolog message is shown, and the work order stage update is canceled. If you want to check the journal lines of a work order, click Enterprise asset management > Common > Work orders > All work orders or Active work orders or My active work orders > select work order in list > Journals. This automatic setup of work order journal posting at a certain stage is the same as when you click the Post journals button in Work order journals. Note: If you select "Yes" on this toggle button, journals are automatically posted if no approval workflow has been set up. If your company uses the journal approval setup in Project management and accounting > Setup > Journals > Journal approval, consumption registrations must be validated and posted by a manager or clerk. |
Process checklist |
If you select "Yes", it means that when a work order is updated to this stage, all attached checklists will be processed. Processing includes posting any counter registrations made on a checklist and evaluating the result of the checklist as a whole. Checklist lines with 'Pass/Fail' results are evaluated, and if at least one checklist line has failed, the entire checklist is marked as "failed" in Enterprise Asset Management. |
Ready |
If you select "Yes", it means that when a work order is updated to this stage, the work order line schedule status for all work order lines created on the work order is automatically updated to "Ready". |
Start |
If you select "Yes", it means that when a work order is updated to this stage, the work order line schedule status for all work order lines created on the work order is automatically updated to "Started". |
End |
If you select "Yes", it means that when a work order is updated to this stage, the work order line schedule status for all work order lines created on the work order is automatically updated to "Ended". |
Delete schedule lines |
If you select "Yes", when a work order is set to this stage, and it has already been scheduled, scheduling will be deleted on all work order lines created on that work order. This means capacity reservations on the object, the related worker, and related tools will be deleted. Example: Select this parameter on a work order stage called "Estimated", to allow scheduling to be deleted on a work order which is 'rolled back' to this stage, because rescheduling is required. |
Note
If the project stage for the project type is not selected, and that project stage is used on a work order stage, the work order projects will not be updated accordingly.
Note
The project activity number related to a work order line is shown in Enterprise asset management > Common > Work orders > All work orders or Active work orders or My active work orders > select work order > Edit button > select work order line > Line details FastTab > General tab > Project section > Activity number field.
Note
Schedule lines related to work order lines are shown in Enterprise asset management > Common > Work orders > All work orders or Active work orders or My active work orders > select work order > Edit button. In All Work orders Details view, select a work order line on the Work order lines FastTab > see related schedule lines on the Line details FastTabs. The status of a schedule line is shown on the Schedule tab in the Status field. The Status field may show one of the following statuses: Scheduled - Ready - Started - Stopped - Ended.
Note
You can read more about kanban functionality in the document "Mobile EAM Client Training Material", which describes the features and functions of the mobile client.
Note
The Production stop, Fault symptom, Fault cause, and Fault remedy toggle buttons on the Validate FastTab relate to the toggle buttons in the Mandatory section in Work order types (Enterprise asset management > Setup > Work orders > Work order types). In order to activate those validations, the related toggle buttons must also be set to "Yes" on the work order type used on the work order.
When a work order is updated to a work order stage for which the Checklist toggle button is set to "Yes" on the Validate FastTab, it means that the checklist lines marked "Mandatory" are validated as being either 'Checked' or 'Not applicable'. If none of those registrations have been made on the mandatory lines, an info message or error or warning will be shown when the work order stage is updated to this stage.
When a work order is updated to a work order stage for which the Committed cost toggle button is set to "Yes" on the Validate FastTab, it means that total committed costs (meaning total amount of expenses that the legal entity has committed to pay) are calculated for each work order line. An Infolog is shown if the committed cost amount is larger than zero. The types of cost commitment to be included are selected in Project management and accounting > Setup > Project management and accounting parameters > Cost control > Cost commitments section.
When a work order is updated to a work order stage for which the Production stop toggle button is set to "Yes", a production stop validation is made on the object related to a work order. If a production stop has been registered, and it does not have an 'ended' registration, a message is displayed when the work order is updated to this stage.
Note
In Project management and accounting parameters, you can set up user-defined project stages if you require special stages for your Enterprise Asset Management setup that are not included in the standard project setup.
See the Forecasts, Work Orders, and Projects section for more information on the relation between work order stages, project stages, and work order projects.
Note
When you change stage on a work order to a work order stage that is not active (meaning "No" is selected on the Active toggle button on the General FastTab for that stage in the Work order stages view), not yet posted journals related to the work order will automatically be deleted. This is done to ensure automatic cleanup of unused data.
However, if you manually set a work order to be inactive (Enterprise asset management > Common > Work orders > All work orders or Active work orders > select work order in list > Edit button > Header link > General FastTab > set the Active toggle button to "No"), related but not yet posted journals will not automatically be deleted.
Note
When you change stage on a work order to a work order stage that is not active (meaning "No" is selected on the Active toggle button on the General FastTab for that stage in the Work order stages view), not yet posted journals related to the work order will automatically be deleted. This is done to ensure automatic cleanup of unused data.
However, if you manually set a work order to be inactive (Enterprise asset management > Common > Work orders > All work orders or Active work orders > select work order in list > Edit button > Header link > General FastTab > set the Active toggle button to "No"), related but not yet posted journals will not automatically be deleted.
Stage groups refer to work flows, and stages are selected in a stage group in a sequential order. Stage groups are set up on types. Types determine the size or extent of work flows and work processes. For example, a standard work order type, "Maintenance", may be related to a work order stage group containing many stages. A "Corrective" work order type, which is used for work orders that have not been scheduled, or work orders for which the job was completed before the work order was made because of a need of urgency, may have a related work order stage group that only contains a few work order stages.
The idea behind using types is that when a type is defined on, for example, a work order or an object, the related work processes (stages) are automatically defined. Refer to the Work Order Types section for more information about how to set up work order types.
Note
Stages, stage groups, and types apply to: Functional locations - Objects - Requests - Work orders.
The figure below shows the relation between work order types, work order stage groups, and related work order stages.
When you have created the work order stages required for your work orders, stages can be divided into work order groups. As a minimum, one standard work order stage group should be created.
A work order type is used to categorize a work order, for example relating to preventive maintenance or corrective maintenance. A work order type defines the work order stage group affiliation. Work order stage group defines which stages can be set on a work order, for example, "Created", "In Process", and "Finished".
Refer to the Work Order Stages section for more information about work order and project stages.
Note
The toggle buttons in the Mandatory section relate to the toggle buttons on the Validate FastTab in Work order stages (Enterprise asset management > Setup > Work orders > Stage > Stages).
In the Enterprise asset management module, a project relation on a work order line is mandatory. The project associated with the work order line allows you to track costs on different projects related to Enterprise Asset Management, for example, internal maintenance projects, service management projects, and investment projects. Refer to the Integration to Project Management and Accounting chapter for more information about project relations to work orders and objects.
When you create a new work order line on a work order, the project setup in the Project management and accounting module, and the work order project setup in Enterprise asset management determine how projects can be used for cost control on the object selected on the work order line. This section describes different parts of the project setup used on a work order: Parent project (Project ID) - Project type - Project activities - Financial dimensions:
The section below explains how to set up parent projects and project groups, which are used for controlling and reporting regarding work orders.
Before you start creating work orders, you must set up work order projects. Work order project setup contains two links, Parent project and Project group. In the Parent project section, you can set up project relations to be used in case no project is set up on the object selected on the work order line. Parent project setup is not required if your company uses object projects. It is only relevant if you want to use work order projects instead of object projects - in that case you must set up at least one parent project.
In the Project group section, you can set up project groups to be associated with work order types, functional locations, object types, and objects.
Project groups can be used to create specific categories (groups) used for cost control. Example: Creating project groups for specific object types or work order types allow you to track maintenance costs by type on a detailed level.
Project groups are not mandatory. If you do not set up project groups, the parent project is used to determine the project group, and a child project is created from the parent project's project group.
The setup allows complete integration with the Project management and accounting module, allowing you to track costs related to work orders in the related projects. Read more about the relation between work order projects, project stages, and work order stages in the Forecasts, Work Orders, and Projects section. The following procedure describes the work order project setup.
Note
If you select a functional location, the related sub locations are automatically included. If you select an object, it is possible to create more work order project setup lines for the same object, but select different projects for the same object.
When you create a new work order, you may want to prioritize the work order and add a general description to it. You can create priorities and descriptions in the Priority and Work order description forms.
Work order priorities, which are described in the previous section, can be used to set up scheduled execution. You can use scheduled execution to provide flexibility in work planning for the maintenance worker by setting up more detailed or less detailed requirements as to the interval during which a work order should be completed. For example, if a maintenance worker has completed a job faster than expected in a production facility, the worker may be able to complete a job nearby, not necessarily planned for the current day, but for the current week. This approach provides the possibility of optimizing worker planning and job completion.
Scheduled execution can be set up for various levels related to a work order. You can set up generic lines - as shown in the figure "Scheduled execution" at the end of the present article- that are not limited to specific work order types, object types, and so on. Or you can create specific scheduled execution lines that apply to a work order type, object type, job type, and so on, or a combination.
In Enterprise Asset Management, you can manage faults detected on objects by describing symptoms, areas, and fault types. The fault designer allows you to set up symptoms, areas, and fault types on object types. Also, fault causes and suggestions to remedy faults can be registered on a work order.
The sequence of registration and management of faults is: First, you create a list of fault symptoms, fault areas, and fault types that may occur on your object types. Next step is setting up symptoms, fault areas, and fault types in the Fault designer. To understand the distinction between fault symptoms, fault areas, and fault types, here are a few examples:
Fault symptoms: |
Unbalanced voltages Short circuit Noise Leak Vibrations |
Fault areas: |
Electrical Mechanical Hydraulic Pneumatic |
Fault types: |
Faulty main stator winding Faulty diode Dirty windings Defective generator Defective sensor |
The relations between fault symptoms, fault areas, and fault types depend on the license configuration setup of the Enterprise Asset Management module. In License configuration (System administration > Setup > License configuration), you can select a Fault hierarchy check box. If that check box is selected, it means that when you select a symptom in Fault designer, the fault areas related to that symptom are shown on the Fault area FastTab. Likewise, when you select a fault area in Fault designer, the fault types related to that area are shown on the Fault type FastTab. Refer to the License Configuration chapter for more information about configuration of Enterprise Asset Management.
Note
If the Fault hierarchy check box is cleared in License configuration, it means that when you select a fault symptom in Fault designer, you will see all the fault areas and fault types that have been added in Fault designer. In that case, there is no hierarchical relationship between the selected fault symptom, fault areas, and fault types displayed.
Cause and remedy for a specific fault can be selected on a work order or a request.
Note
You can only create fault records on work orders and requests if they contain objects with object types that have faults connected to them in the Fault designe
Note
If required, you can change or update the names of your fault symptoms, areas, types, causes, and remedies. The name changes are automatically reflected in the related fault registrations.
Create a list of symptoms to be used in the fault designer.
Create a list of areas or locations to be used in the fault designer.
Create a list of fault types to be used in the fault designer.
In Fault designer, you set up fault data on object types.
Create a list of known fault causes, which can be added to a work order or a request.
Create a list of suggestions for remedy and repair, which can be added to a work order or a request.
In standard Dynamics 365 for Finance and Operations, it is possible to perform consistency check on your setup data for some modules, including Enterprise Asset Management. If you want to carry out a consistency check to validate your setup data, click System administration > Periodic > Database > Consistency check, and select the modules to be included in the validation.
When the validation is completed, a message box describing any inconsistencies is shown. Various inconsistencies in the setup data may be found in Enterprise Asset Management. For example, a request may be related to a work order that no longer exists, or a work order project ID requires a sub project ID format (Project management and accounting > Setup > Project management and accounting parameters > General link > Default subproject ID format field), which is not available.
Copyright Dynaway A/S