Configuration Concepts

The chapter provides information and guidance on the general steps and concepts when configuring master data in Infor MES.

Common Actions

These are the common action that are preformed when configuring master data:

  • Add: Allows you to create a new master data record. The application displays a screen that contains all mandatory fields marked with a red asterisk and optional fields. Some screens contain the Add Multi option to create multiple records at the same time.
  • Edit: Allows you to update a master data record. The application allows updates based on the status of the record. To update multiple records, press Ctrl and left‑click each record.
    Note: You cannot modify a record that is released to production, such as BOM variants or Inspection Versions. In this case, you must create a new revision to update the record.
  • Revise: Allows you to create a new revision of master data record. This ensures that updates are performed safely without altering the production version. For example, revision 1 of an inspection version remains active, revision 2 can be modified. When revising, you must specify a reason for the change. After modifying data, release the revision to activate the record.
  • Release: Allows you to approve master data record for production use. This action ensures data is reviewed and configured correctly before the record is operational. For example, Inspection Versions must be released before they can be used by end users.
    Note: You cannot release a record that is in a released state. The record must be revised and modified before the record is released.
  • Delete: Allows you to remove a master data record permanently. This option is used to correct mistakes or remove unnecessary entries. If deletion is not possible, you can retire the record.
    Note: Deletion is not possible if:
    • Production data is linked to a record. For example, Inspection Versions with quality checks.
    • Other master data depends on a record. For example, Machine Types assigned to Machines.
    • The record type does not support deletion.
  • Retire: Allows you to disable a record without deleting the record. The application prevents a retired record from being used on new master data and preserves historical data. For example, you cannot create new production orders for retired materials, however, existing orders remain valid and displayed. Retired records are excluded from reports, however, you can include retired records, using filters.
Dashboard Layouts
Dashboard layouts define how departments, lines, machines, and locations display on dashboards. A dashboard layout determines the following:
  • Spatial arrangement: Defines how items are positioned and organized on the dashboard.
  • Visibility: Defines which entities display or remain hidden when filters apply.
  • Interaction behaviour: Defines how a user interacts with dashboard elements, such as selecting items or drilling down to view more details.
To configure a layout, navigate to the relavant master data screen, select a record, and click Dashboard Layouts. See, Dashboard Layout.

On-Premise vs. Enterprise

Infor MES can be deployed as on‑premise or as an enterprise solution. Each deployment model impacts how master data is configured, governed, and maintained. Understanding these differences is essential to correctly setting up and managing master data.

In an on-premise deployment, each factory uses a dedicated installation of the Infor MES application. The installation runs on local hardware that customers own. A template application can be deployed for all factories; however, master data is not shared between factories. These are the key characteristics:

  • Each factory defines and maintains master data independently. This method provides flexibility; however, this can cause data divergence between factories. For example, deploying a new inspection to five factories means configuring the setup separately at each location, resulting in five individual configurations.
  • Global standards exist only as recommendations and cannot be centrally enforced.
  • On-premise deployments do not consolidate global reporting. Expansion to additional factories requires more time and resources because each factory manages data independently.

In Enterprise deployment, all factories share a single, centralized Infor MES deployment, which is hosted on the cloud or a centralized data center. This model is designed for scalability, consistency, and unified operations. These are the key characteristics:

  • Master data is created and maintained once at the central instance and shared across all factories. For example, an inspection needs to be created only once for all plants.
  • Centralized management ensures consistent global standards and improves operational visibility.
  • Certain master data, such as machines or locations, remain factory-specific and must be configured individually for each factory.
  • Centralized data enables global reporting capabilities and accelerates deployment of MES functionality to new sites.

Global master data covers materials, Bill of Materials (BOMs), variables, attributes, inspections, and maintenance procedures. Plant-specific master data includes lines, machines, locations, tools, and assets. For a complete list, see the Infor MES Table report in Application Configuration functionality.

Mandatory Fields

When you manage master data in Infor MES, some fields require values, and other fields remain optional. Mandatory fields display a red asterisk (*). You must specify values for these fields to maintain data integrity and data completeness. If any mandatory field remains blank, the system displays an error when you submit the form. Fields without a red asterisk are optional. You can save the record without specifying values for these fields. However, some optional fields support specific business processes. Review and complete all relevant optional fields to ensure that the master data supports operational requirements.

Entities Types Sets and Groups

Entities are the core master data records that represent real-world items or concepts in Infor MES. Each entity represents a single, unique instance and includes defined attributes. Entities form the primary building blocks of MES master data. Examples of entities include:
  • A specific machine, such as Machine #1234
  • A specific material, such as ABC123
  • A single production line, such as Line 5
Types classify entities into categories based on shared characteristics or usage. Types support standardization and organization for configuration and reporting. Types define shared characteristics and shared behaviors across related entities. Examples of types include:
  • Machine types, such as welder robot and conveyor, that group machines by function
  • Line types, such as assembly and packaging, that categorize production lines
  • Material types, such as steel plate and steel chassis, that classify materials
Sets are defined collections of related entities that simplify master data management. A set acts as a reusable collection that supports consistency across multiple master data records. Examples of sets include:
  • A production stop reason set that contains reasons such as maintenance, quality issue, and material shortage that apply to multiple lines
  • A scrap reason set that contains reasons such as damaged, severe dent, and incorrectly stamped that apply to multiple machines
Groups are logical aggregations of entities that support organization, navigation, and reporting. Groups can overlap across categories and support flexible reporting structures. Examples of groups include:
  • A machine group that combines multiple machines for production analysis
  • A material group that combines materials by business unit or class
  • A line group that combines production lines by product family or location

MES vs. ERP

Infor MES and ERP (Enterprise Resource Planning) systems maintain master data used in business and manufacturing operations. While certain master data elements overlap, each system is designed to manage information at a different level of detail and for distinct functional purposes.

ERP master data enables business enterprise‑level processes, such as finance, procurement, inventory management, order handling, and supply chain planning. ERP stores high-level, strategic information and is not intended for detailed shop floor execution or real-time monitoring. Examples include:

  • Customers and suppliers
  • Financial accounts and cost centers
  • Product catalogs with item numbers and descriptions
  • BOM structures and revisions
  • Inventory quantities tracked at a batch level
  • Purchase orders, sales orders, and contracts

Infor MES master data provides detailed, real-time management of production, quality, inventory traceability, and maintenance operations. This data is more granular than ERP data to meet specific requirements of shop floor operations. Examples include:

  • Production lines and machines
  • Tools and usage data
  • Inspection plans and specification limits
  • Maintenance procedures, work steps, and schedules
  • Inventory quantities tracked at the handling unit (serialized) level
  • Operators, labor skills, and shift schedules

Some master data, such as materials and BOMs overlaps between ERP and MES. ERP manages the master definitions and revisions, while MES uses the master data to run production orders. To prevent duplication and errors, assign clear data ownership and use integration to synchronize data between ERP and MES. ERP acts as the master for strategic data, such as materials, BOMs, and production orders. ERP exports this data to MES.

Infor MES provides configurable options, such as Code fields that map MES entities to ERP entities. Teams must understand which master data within Infor MES manages directly and which master data ERP provides. requires a clear understanding of which master data is managed by MES and which is imported from ERP. This clarity ensures proper data governance, consistent configurations, and seamless integration between MES and ERP.