MES Functions

Configuring a Request Flow

Details
Category: Notifications and Automated Actions

Description

This example configuration is designed to implement a 'Request' for action.  A operator will submit a Request, and then a supervisor will review this request and either approve or deny it.  It can also include Events that montor and notify specific User Groups of the submitted Request.

 

  • The outline of configuration is as follows:
  • Create First Step Definition
  • Create required Name-Values within Step Definition
  • Create Second Step Definition
  • Create required Name-Values within Step Definition
  • Create Flow Definition
  • Attach Step Definitions to Flow Definition
  • Create a Request Part Definition
  • [Optional] Configure Event for notification

 

Step Definition Creation

This Flow will be a simple two step process in which a Request is submitted in one step, and the following step the request is accepted or rejected.

Create Step 1: Request

Basic Step Configuration

To configure a the first Step Definition for 'Request Flow' you should first create a new Step Definition with the following settings:

  • Name: Request 
  • Step Number: SD13-000000001 (your number may vary)
  • Revision: A

RequestFlow-03

 

Name-Value Configuration

After the basic Step Definition configuration is completed you should now add Name-Value entry fields that you would like populated during operator interaction.  You can add as many entries that you would like for your particular Step / Operation.  However, the first Name-Value should be a Unique ID Type.  You can find help on all of the Name-Value Configurations here.

The one extra step we performed for all Name-Values used in this Flow is that use of the 'Write to NVR Value to PR by NV Name'.  This write the entry value to the Part Record and allows us to recall the information via Part Record.  This is located in the Name-Value 'General Parameters'.  It will be highlighted in the sample NV Configuration.

Here is a list of all Name-Values used for this step:

 

Sample Configuration for Calc NV Type

RequestFlow-05

 

 

 

Create Step 2: Request Approval

The second Step / Operation is unique in that its Name-Values 'defaults' to the values entered from the previous Step / Operation.  This is done with a Name-Value attribute called 'Copy Custom PR Attribute to NVR'.  It will be highlighted in the sample NV Configuration.

To configure a the second Step Definition for 'Request Flow' you should first create a new Step Definition with the following settings:

  • Name: Request Approval
  • Step Number: SD13-000000002 (your number may vary)
  • Revision: A

 

RequestFlow-04

 

 

Name Value Configuration

After the basic Step Definition configuration is completed you should now add Name-Value entry fields that you would like populated during operator interaction.  You can add as many entries that you would like for your particular Step / Operation.  As mentioned previously, this Step does require the use of the attributes 'Write to NVR Value to PR by NV Name' and 'Copy Custom PR Attribute to NVR'.

Here is a list of all Name-Values used for second step:

  • Name: Request Approved, Type: Pulldown
  • Name: Mask Name, Type: Pulldown
  • Name: Substrate Type, Type: Pulldown
  • Name: Quantity, Type: Number
  • Name: Purpose, Type: Text
  • Name: Comments, Type: Text

 

Sample Configuration for Calc NV Type

RequestFlow-06

 

Flow Definition Creation

Main Configuration

To configure a the Flow Definition for 'Request Flow' you should first create a new Flow Definition with the following settings:

  • Name: Request Flow
  • Flow Definition Number: FD13-000000001 (your number may vary)
  • Revision: A
  • Flow Definition Type: Use Part
  • Part State When Active: WIP
  • Part State When Done: RMI

RequestFlow-02

 

Adding Step Definitions

You must now add the Step Definitions you created for this Flow.  

 

 

Part Definition Creation

To configure a simple 'Request Flow' you should first create a new Part Definition with the following settings:

  • Part Name: Request

  • Part Number: PD13-000000002 (your number may vary)

  • Part Revision: A

  • Discrete: True

RequestFlow-01

 

 This concludes the configuration aspect of a 'Request Flow'.