This guide can be used as a reference for configuring EZ-MES. For most of the configuration elements a step by step overview on configuration procedure is provided.

Configuring EZ-MES

The configuration of EZ-MES takes place on the Configuration Desktop, from here the following configuration objects can be managed:

1. Part Definitions
   
   

   Part Definitions can be seen as templates (blue print, hence the blue Icons and forms) for Part Records. Part Records are the EZ-MES representation of real world parts.

   • 
     
     

     Equipment Definitions can be seen as a template (blue print, hence the blue Icons and forms) for Equipment Instances. Equipment Definitions are the EZ-MES representation of real world Equipment.

2. Step Definitions
   
   

   Step Definitions are the actions you perform to make or change one or multiple part. Your Step Definition can be reused in different Flow Definitions.

3. Flow Definitions
   
   

   A Flow Definition is a template to create Travelers that will 'carry' the actual parts. The Flow Definition is created by sequencing a one or more of Step Definitions.

4.   Documents
   
   

   Documents can be attached to Step Definitions, Part Definitions and Flow Definitions. The documents attached to the Step Definitions are directly accessible for the Operator.

5. Spec Definitions
   
   

   It is possible to define Specifications for Part Definitions. Using these Spec Values the actual data entries on a step Definition can be cross checked with the specification of the Product Definition that is moving through the step.

6. Categories
    
   

   Categories can be used to group other objects e.g. Part Definitions, Documents etc..

7. Event Definitions
   
   

   Using the Event Definition Configuration Element, Actions that are dependent on certain situations can Trigger the moment that situation occurs.

8. Triggers
   
   

   Triggers are conditions that are evaluated on regular intervals and/or at specific user actions. A trigger that evaluates to true can be used to initiate single or multiple Actions. The Event Definition defines which Triggers belong to which Actions

9. Actions
    
   

   One or more Actions can be connected to Event Definitions, at the moment the Trigger of an Event evaluates as True the Actions of the Event are Executed.

10. Name Value/Data Entries
    
    

    To configure the Data Acquisition during the flow.

11. Input-Output Conversion
    
    Input Output Combinations can be used to create a part conversion during a Step, by changing the Part Records Part Definition. Input Output combinations can also be used to constrain a specific flow to specific Part Definitions

Note: screenshots can be different from your actual situation. The differences can be caused by differences in Access Rights, differences in purchased application, and new functionality that is not yet included in the manual. It is also possible that your browser settings change the appearance.

What would you like to do next?