Status Identifier Variables

When data is received from an external source such as a barcode scanner, there must be a method of identifying valid data and determining what the data is supposed to represent.  Status Identifiers are used to specify the type of status and whether or not the status has started or ended.  Equipment Status Identifiers can be specified on the Manage Equipment Status form of the application.

For each status type there is a Start and End General Status Identifier.  For example, the Cycle Status Identifiers default to CS and CE for cycle start and cycle end.  Planned downtime is PDTS and PDTE for planned downtime start and end, and the default for unplanned downtime is UPDTS and UPDTE for unplanned downtime start and end.

When using expression there are variables to reference these start and stop identifiers.

PCSDB.SI_Cycle_Start{}

PCSDB.SI_Cycle_End{}

PCSDB.SI_Planned_DT_Start{}

PCSDB.SI_Planned_DT_End{}

PCSDB.SI_Unplanned_DT_Start{}

PCSDB.SI_Unplanned_DT_End{}

Program Number Identifier Variables

There are identifier variables for making a program number active or inactive. 

PCSDB.send_program_number_start{PROGRAM NUMBER}

PCSDB.send_program_number_end{PROGRAM NUMBER}

Part Identifier Variables

There are identifier variables for making a part number active or inactive. 

PCSDB.PI_Part_Start{}

PCSDB.PI_Part_End{}

There are identifier variables for adding and subtracting good parts.

PCSDB.PCI_Add_Good_Part{}{}

PCSDB.PCI_Subtract_Good_Part{}{}

The brackets indicate that additional information can be referenced which would be a specific status identifier.  Specific Status Identifiers can be used to specify specific statuses such as no material, broken tool, or breaks. 

For example, if a specific planned downtime identifier of 200 has been created and defined as No Material then the start of the planned downtime can be referenced in the following ways.

PDTS{200}

or

PCSDB.SI_Planned_DT_Start{200}

---