---
pdfexport: true
alias: master-data-create-a-model-tutorial
description: "Learn to build a maintenance model using Excel files and Master Data Packages within the MES system"
---

# Creating a Model

In this tutorial you will learn by example as we show you how to load different **Maintenance Plans** into Critical Manufacturing MES using **Master Data Packages**. Let's start by filling in the model in the Excel file and then load it into the system.

## Modeling Sequence

As discussed before, it is vital to maintain an appropriate modeling sequence to prevent precedence errors. Let's start by filling the properties for the entities, following the proper sequence. See [[master-data-excel-template-tutorial#modeling-sequence|Modeling Sequence]] for more information.

!!! note
    Whenever you are filling cells that have specific enumeration options, those options will be shown in the form of a dropdown selection box to prevent typing errors.

    ![Screenshot showing a UI with checkboxes labeled "Yes" and "No", alongside a filename input field displaying "masterdata 15".](../../../../images/masterdata_15.png)

    There are also comments in most of the columns (that, if you recall, represent the entity properties) to help you with information as well as an indication of whether the properties are mandatory.

    ![Screenshot showing a sequence modeling interface with fields labeled "EE EE ESS ee D [From Costtenter Lookup]", "po —— —", ": remeron", ": bisemeerent oer", and ": eri".](../../../../images/masterdata_16.png)

## Roles

First, let's create different **Roles** for the operators of the **Maintenance Plans**.

![Screenshot showing a list with two roles: "Maintenance Manager" and "Maintenance Technician".](../../../../images/masterdata_17.png)

!!! info
    For more information, see [[security-admin]].

## Users

Following the rules of precedence, you can then use these same **Roles** in the **Users** sheet.

![Screenshot showing a data entry form with fields for "PMI manera", "Tecniiny Bunda", and other related information.](../../../../images/masterdata_18.png)

## Documents and Folders

Let's add **Documents** (that you will later upload) to show on the **Maintenance Plans** as information files for the actual Maintenance process. First we need to create **Folders** where the **Documents** will be stored in the MES.

![Screenshot showing a list of folders with "Process Documents" and "Quality Documents" listed, along with a filename hint for "masterdata 19".](../../../../images/masterdata_19.png)

Moving to the **Document** tab, the filename must match the names of the documents in the `.zip` file that you are going to load into the system.

![Screenshot showing a folder structure with documents and folders, likely related to maintenance plans.](../../../../images/masterdata_20.png)

!!! info
    For more information, see [[user-guide-document-index]].

## Certifications

Now, let's create **Certifications** to ensure that employees with the proper knowledge are used for the Maintenance procedures. These **Certifications** are used in the Personnel Requirements of the Resource and are validated when executing the **Maintenance Plans**.

![Screenshot showing a section of master data related to certifications.](../../../../images/masterdata_21.png)

!!! info
    For more information on **Certifications**, see [[user-guide-certification-index]].

## Calendar

Let's continue focusing on the modeling sequence precedence, which dictates that you must create a **Calendar** before you can create the rest of the entities that depend on it.

![Screenshot showing a calendar with events listed for Dublin, Edinburgh, and Lisbon.](../../../../images/masterdata_22.png)

!!! info
    For more information, see [[user-guide-calendar-index]].

## Teams and Shift Definitions

In this case there are several entities that you need to create. Let's start with **Teams** and **Shift Definitions**.

![Screenshot showing a table with team and shift definitions, including team names (Team-A, Team-B, Team-C) and corresponding calendar codes.](../../../../images/masterdata_23.png)

![Screenshot showing a table with columns labeled "Name", "Description" and "StartTime" for Teams and Shift Definitions.](../../../../images/masterdata_24.png)

![Screenshot showing a table with team and shift definitions, including names such as "LT AS A" and "Sapien ftemoen".](../../../../images/masterdata_25.png)

!!! info
    For more information, see [[user-guide-shift-definition-index]].

## Facilities and Areas

And let's continue with **Facilities** and **Areas**. Remember that the creation of the **Facility** takes precedence over the creation of the **Areas** and the other entities.

![Screenshot showing a table with facility and area data, including warehouse, production, and customer information.](../../../../images/masterdata_26.png)

![Diagram showing a screenshot of a data entry form with fields labeled "LTT", "EE", and "Paaing Posing Wiretone Aes rena".](../../../../images/masterdata_28.png)

!!! info
    For more information, see [[user-guide-facility-index]] and [[user-guide-area-index]].

## Employees

In the **Employee** sheet, define the **Calendar** and the **Area** for each **Employee**. Since the Employee Number is a mandatory field, you must use unique values for different employees, which should be a fairly typical situation in most production environments.

![Screenshot showing a list of employees.](../../../../images/masterdata_29.png)

!!! info
    For more information on **Employees**, see [[user-guide-employee-index]].

### Personnel Requirements

For Personnel Requirements, use the **Certification** entities created above and fill in the information for each **Certification** in the **EmployeeCertification** sheet.

![Screenshot showing a table with personnel requirements data, including columns for maintenance and technical information.](../../../../images/masterdata_30.png)

!!! info
    For more information, see [[user-guide-manage-personnel-resource]].

## Products

Now let's focus on the **Products**, a vital part of the model. For each **Product** you need a **FlowPath**. Considering the modeling sequence, for a **FlowPath** to be created you first need to create the **Steps**, followed by the **Flows**. After setting up both **Steps** and **Flows**, you can populate the **FlowItems** sheet to create (and subsequently load) the desired **Flow** structure. This process establishes the proper sequence necessary for the creation of **FlowPaths**.

### Steps and Flows

![Screenshot showing the Master Data screen with Wesley Neville's information.](../../../../images/masterdata_31.png)

![Steps and Flows (Screenshot shows: tae, revisor, exciton, Type, ostaGrovg, nonseqvenvalblonslterat)](../../../../images/masterdata_32.png)

![Screenshot showing a data entry form with fields for "Fi ope Taner Revers" and "Condtiotype".](../../../../images/masterdata_33.png)

!!! note
    As a fresh reminder, **Steps** must be created before **Flows**. For more information, please see [[tutorials-flowmodeling-index]].

### Product

We can now create the **Products**, using the entries created in the **FlowStructures** sheet and strictly following the **FlowPath** notation used throughout the system: `Flow:RevisionName:CorrelationId/Flow:RevisionName:CorrelationId/.../Step:CorrelationId`.

!!! info
    For more information, see [[user-guide-flow-index]].

![Screenshot showing a product entry form with fields for "Olumofite" and "Pow Warsow prssncnng Pat".](../../../../images/masterdata_34.png)

## Services and Resources

Continuing to follow the modeling sequence, let's create the **Services** followed by the **Resources**.

![Screenshot showing a table with two rows of data, labeled "WH_Storage" and "Production_Storage", displaying storage information.](../../../../images/masterdata_27.png)

![Screenshot showing a sequence of steps in creating services and resources, including setup and configuration options.](../../../../images/masterdata_36.png)

After these two entities are created, let's proceed in creating the link between **Resources** and **Services** in the **ResourceService** sheet.

![Screenshot showing a table with two rows of data, listing "Trolley_1" and "Trolley_2" as services with storage parts in different locations.](../../../../images/masterdata_37.png)

## Data Collection

We want to add a **Data Collection** to measure some parameters during the quality control phase of the process. Before adding any **Parameters** to a **Data Collection**, create the **Parameters** it will use when recording data.

!!! info
    For more information, see [[user-guide-data-collection-index]].

### Parameters

![Screenshot showing a UI with a filename "masterdata 35" and a title "EM I : Nene mene Nerrerenee toro hee pee 9 . =".](../../../../images/masterdata_35.png)

Let's create the **Data Collection**.

![Screenshot showing a table with parameters, including "Name", "Revision", and "Type".](../../../../images/masterdata_38.png)

And now we can use those **Parameters** and add them to the **Data Collection** using the **DataCollectionParameters** sheet.

![Screenshot showing a spreadsheet with parameters and data collection settings.](../../../../images/masterdata_39.png)

## BOM

The maintenance process typically requires a **BOM** (Bill-of-Materials) to replace faulty parts in the processing **Resources**. Let's start with creating the base **BOM**.

![Screenshot showing a blank or empty screen, possibly related to creating a Bill-of-Materials (BOM) for maintenance purposes.](../../../../images/masterdata_40.png)

### BOM Items

With the **BOM** created, we can add the **Products** that will be used as **BOM Items**.

![Screenshot showing a table with product information, including "TE" and "2 pOM".](../../../../images/masterdata_41.png)

!!! note
    For more information, see [[user-guide-bom-index]].

## Checklist

To list all the work that will be done during this maintenance process, we can add a **Checklist** to our model to help our maintenance technician. Let's start by creating the base **Checklist** object.

![Screenshot showing a checklist with numbered items, including "ine Te" and "PEE TE".](../../../../images/masterdata_42.png)

!!! note
    For more information, see [[user-guide-checklist-index]].

### Checklist Items

Similar to what we did earlier with the **BOM**, let's add **Checklist Items** to indicate what will be done during the execution of the **Checklist**.

![Screenshot showing a checklist with items for execution.](../../../../images/masterdata_43.png)

### Checklist Item BOM Items

Since the proper completion of some of the **Checklist Items** require the use of Parts to perform the maintenance activity, let's add those Parts (which are modeled as **BOM Items**) to the **ChecklistItemBOMItems** sheet.

![Screenshot showing a table with a list of BOM items.](../../../../images/masterdata_44.png)

### Checklist with Data Collection

To gather more data from the process, let's associate a **Data Collection** with the same **Checklist** under the same **Maintenance Plan** by filling the appropriate values in the **ChecklistItemDataColParameters** sheet.

![Screenshot showing a checklist with two items: "Maintenance Check tool Machine Pressure" and "Maintenance Check tool | iauid Qutout".](../../../../images/masterdata_45.png)

### Checklist Item Signatures

Adding some extra process security and bulking up the approval process, let's add a mandatory signature to one of the **Checklist Items** by using the **ChecklistItemSignatures** sheet.

![Screenshot showing a checklist item with two signature fields, labeled "Trenane Sito" and "EA signstuecetiiato siuturenlowselld".](../../../../images/masterdata_46.png)

## Maintenance Plan

Finally, after creating all these entities, it's time to create the actual **Maintenance Plan**.

![Screenshot showing a table with column headers "Name", "EZ Revision", "Description", and "Typda" for creating a Maintenance Plan.](../../../../images/masterdata_47.png)

!!! note
    For more information, see [[user-guide-maintenance-plan-index]].

### Maintenance Activities

A Maintenance Plan is composed of a number of Maintenance Activities, that you can define in the **MaintenancePlanActivities** sheet.

![Screenshot showing a maintenance activities list with entries labeled LS A eT - CF.](../../../../images/masterdata_48.png)

Associating the **Checklist**, **Data Collection** and **BOM** is done in this same **MaintenancePlanActivities** sheet, using the appropriate columns.

![Maintenance Activities — screenshot: masterdata 55](../../../../images/masterdata_55.png)

### Maintenance Activity Documents

To add a **Document** to a specific Maintenance Activity, use the **MaintenanceActivityDocument** sheet.

![Maintenance Activity Documents — To add a Document to a specific Maintenance Activity, use the MaintenanceActivityDocument sheet (Screenshot shows: Bal, _MaintenancePlan, Activityame, Orde, bocument, Machine)](../../../../images/masterdata_49.png)

Let's also specify the Personnel Requirements for the **Maintenance Activities**.

![Screenshot showing a spreadsheet with maintenance activity documents, including "Machine Maintenance" and "Annual Maintenance Certification".](../../../../images/masterdata_50.png)

## Loading the model

With the entire process completed, you just need to compress all the pertinent files, including the Excel template and other images, into a `.zip` file. This is the file you will use to load the data into the system.

![Screenshot showing a loading model in an example use case.](../../../../images/masterdata_12.png)

To complete the process, see [[master-data-loading-the-model-tutorial]] for information on how to load the model.