Overview

Enterprise Asset Management

Enterprise Asset Management is an advanced module for managing assets and maintenance jobs in Microsoft Dynamics® 365 for Finance and Operations. Enterprise Asset Management is developed by Dynaway A/S and integrates seamlessly with several modules in Microsoft Dynamics® 365 for Finance and Operations. In Figure 1 you will see a graphic illustration of the interfaces to other modules in Microsoft Dynamics® 365 for Finance and Operations.

Enterprise Asset Management allows you to efficiently manage and carry out all tasks related to managing and servicing many types of equipment in your company, for example, machines, production equipment, and vehicles. For Asset Service Management, the main focus is servicing customer equipment. Enterprise Asset Management as well as Asset Service Management supports solutions across numerous industries.

Figure 2 shows an overview of the key functionality covered by Enterprise Asset Management.

Functional locations and objects

Functional locations are used to manage objects on locations, including track object costs on functional locations. Functional locations are structured hierarchically, and locations can have sub locations. The functional location structure is static; locations cannot change place. Objects can be installed on functional locations and, if required, the objects can later be installed on another functional location.

Object costs always follow the location of the object meaning if you install an object on a new functional location, the object automatically use the financial dimensions related to the functional location. Therefore, object costs are always related to the functional location to which the object was related at any given time. This automatic handling of financial dimensions ensures complete tracking of costs when your company performs project controlling and reporting on functional locations.

How you build your functional location hierarchy is based on your company's requirements for maintaining internal equipment or servicing customer equipment. The two figures below show examples of functional locations - based on geographical locations and customers.

Objects and work orders

The central parts of Enterprise Asset Management are objects and work orders. An object is a machine or machine part that requires continuous maintenance and service. Objects can be created in a hierarchical structure, and they can be related to functional locations. Maintenance jobs can be planned at all levels in the object structure.

Various data such as product information and object specification and required maintenance sequences are set up on each object. The figure below provides an overview of object data and the object affiliation to job types. Red text are examples to show inheritance and dependencies.

A work order contains a work order type, for example, preventive maintenance, corrective maintenance, or inspection. The work order contains one or more work order lines. Each work order line defines a job to be carried out on an object and a related job type, for example, 10,000 km, 50,000 km, 1-year overhaul, or safety inspection. One work order can relate to several objects.

In the figure Work order overview you will find an overview of the key data in a work order.

A work order can be related to another work order, and job types can contain succeeding jobs, which create a work order. In general, there are no dependencies between work orders, meaning that they can change work order stage and be scheduled independently.

Work orders can be created in various ways relating to corrective, preventive, or reactive maintenance. It is also possible to create work orders manually. In the Process flow figure below, you see a graphic overview of the process flow regarding automatic or manual creation of work orders.

There are several steps to complete when you want to schedule and execute a maintenance job on a work order. In the last two figures below, an overview of the processing of a work order is displayed.