Download MES User Manual - Inductive Automation

Recipe / Changeover
444
To import recipe values in the client, right click on a line, cell, cell group or location underneath
the line and select the import menu item. A file chooser dialog will appear to select or enter a
file name to import to. The file format is a comma separated values (CSV) and must contain
the following columns:
Recipe_Name
Value_Name
Item_Path
Recipe_Value
All other columns will be ignored during the import. Also, all values must be surrounded with
quotes including the recipe value. During importing, the recipe value will be converted to the
appropriate data type that the recipe value is defined as, which is based on the tag it is
associated.
Recipe values can be imported for multiple recipes and production items combinations in one
import operation as defined with the Recipe_Name and Item_Path columns of the CSV file.
This supports bulk import operations instead of only being limited to one recipe at a time.
Recipe values can also be imported and exported using script either at the client or in the
gateway. See exportRecipe and importRecipe script functions for more information. The
following is an example statement that will import recipe values on the gateway. The project
name is required because recipe values are managed by project. The csvData parameter is a
string of csv data that can be read in from a file, web service, etc. And last, the note is what will
show in the recipe change log.
system.recipe.importRecipe("RecipeProject", csvData, note)
This functionality supports reading recipe values from ERP or other systems that are currently
being used to manage recipes. Once the recipe values are in Ignition they can be selected,
monitored for variances, analysis, etc.
Script
In addition to importing and exporting recipe values there are scripts to add recipes, rename
recipes, delete recipes and much more. See Client / Gateway Scripts for documentation of all
script functions. Because the built-in functionality will not fit the requirements in every situation,
the scripting functions provide the built-in functionality to be extended to accommodate the
requirements.
4.1.7
Recipe Change Log
Keeping an audit log of when recipes are changed, by who and why can be important.
Especially in some industries where regulatory compliance are in force. The Recipe /
Changeover Module records all changes to recipes wether the changes were made from the
recipe editor, importing or script. The only changes not automatically detected are changes
made directly to the database and proper database security should be implemented if this is a
risk.
Below are the methods that the change log history can be examined.
Recipe Change Log Viewer
There is a component that will easily show recipe change log history on screens. It has
© Inductive Automation