Comprehensive import of work order data

The document describes the mechanism for importing comprehensive information specifying work orders in the system into the AMAGE system. This data includes basic information about orders, but also attachments/documentation facilitating the implementation of work, material lists necessary for their execution and the history of work performed.

The document describes import mechanisms and their use in order to fully import data into the system from various sources, but in total constituting complete information necessary to achieve a specific business goal. The tutorial does not describe in detail the functions of the importer mechanisms and individual windows. Please refer to the user manual for the basic user interface.

Our goal is to import data from various areas of the company’s business systems into the AMAGE system. Let’s call them collectively the ERP system, but it is not necessary to have this data in one system.

Usually, for proper operation we need:

The entire set of data mentioned above allows you to enter a significant amount of information into the system and use this data in individual field modules, e.g. supervision, service requests or inspections.

Let’s go through all the import mechanisms in the order described above.

We import users↓users. The XLS/CSV sheet contains user data, login, email, phone number and other data.

We select the import mechanism from the list of available importers.

We select the file to be imported and, if we have already gone through these steps, the mapping template we have. If we don’t have it, we create it in the next steps.

We define the import parameters. Each importer has its own specific parameters and behaviors. Here we have available:

Then we define the fields and their meaning in the imported file. Here we can also save all previously defined data in the template under a specific name. We will be able to use it in subsequent imports or to automate the process.

We import. Employees/users are in the system.

We move on to importing the assortment - element types. We usually have this data from the ERP system, from the warehouse or ordering module. We can also import data provided by our subcontractors.

We select the importer from the list.

Let’s define field mapping and their meaning

We import data. An example result of imported data with the division of the product range into categories is presented below.

Let’s move on to importing resources.

We select the resource importer from the list.

We define additional information and parameters. ATTENTION. The importer has an extensive parameter panel and please refer to the user manual for additional information about the meaning of individual parameters.

We define field mapping and their meaning.

We import data. In the import progress view, we receive a visual report of the activities performed and any errors.

The end result is imported resources in the system along with their association in trees and appropriate categorization with element types.

We have a ready data structure on which we can work. Now let’s import the to-do list.

We select the work order importer from the list.

We define general importer options.

We map the fields in the file and determine their meaning.

We import into the system.

As a result, we receive a list of tasks to be performed along with subtasks. The scope of fields to be imported is wide (import of schedule, task assignment, etc.).

To associate tasks with previously imported element types and resources, we need to perform two additional imports.

One file contains a link between the assortment (types of elements) and work orders, along with specifying the amount of a given material necessary to complete/order.

We select the importer from the list.

We choose the field mapping in the imported sheet and their meaning. The main task here is to indicate the relationship between types and work orders.

We import data into the system.

As a result, we receive a list of materials in the work order and a material plan. From here we will be able to order them or generate an order to the warehouse for delivery.

The second link is to link resources to work orders. We carry out similar activities.

As a result of these operations, we receive information about the resources associated with the work order. Based on this data, it will be possible to conduct further automation or quickly navigate between the task to be performed and the data of the resource (parameters, documentation) that needs to be performed.

In the process we describe, additional documentation is often created, which is very useful during the work performed. The attachment importer allows this. Unlike previous importers, it works on a ZIP archive containing files and an XLS sheet that contains information about which resources/work orders a given document should be attached to.

To create such an importer, we create:

We load such an archive into the system.

We define the mapping between the file and the resource or other object handled by this importer.

We import.

As a result, attachments appear in specific resources and can be viewed and downloaded.

The final step in this tutorial is to import order/delivery data. We use an order import mechanism.

We select the order importer.

We define the mapping of individual fields and perform the import.

The end result is imported delivery orders with material details.

We import supplies. Identical to other operations. We choose a supply importer.

We define the fields and their meaning and perform the import.

Deliveries appear in the system. Using the delivery module, we can verify their completeness, create complaints or transfer the material to warehouses.

In this way, we imported a significant range of data from the areas of orders, deliveries, data structure and work orders. We divided the imports into individual stages and used the available importer functions to adapt to the existing XLS/CSV data files. We can now use this data in the system.

Further automation may also be the next steps. While defining these imports, we saved individual templates. Now we can enable integration, e.g. via email, and set the system so that when an XLS file arrives with delivery, it will be automatically downloaded to the system and imported in relation to the template for a given supplier. The possibilities are endless :)