9.1.1.2 Operation/Production Planning

The following figure illustrates the operation flow used during production programming. In this flow, the production coordinator generates programming files (STAPL and PDB), with or without serialization and security settings, depending on production requirements. The production the coordinator loads the programming file into the FlashPro® software to configure production‑programming settings, such as serialization options, action selections, and procedure selections.

Depending on production logistics and serialization requirements, the production coordinator may generate separate configuration files for each programming station. For example, if a programming file contains 10,000 serialization values and the production coordinator allocates 1,000 values to each programming station, ten configuration files are generated—one for each station. If serialization is not used, only a single configuration file is required.

The production coordinator can test the configuration files with one or more FlashPro4/3/3X programmers before sending it to the production programming floor. If PDB files are used in the production flow, warning icons may appear on the FlashPro/FlashPoint GUI because the automatic audit cannot find the source file on the production environment; the PDB file contains the valid programming data. If STAPL files are used, loaded STAPL files will be audited on execution of an action to determine if the original STAPL file has been modified. If it has not been modified, the action will continue to run. If it has been modified you will be prompted to reload the modified STAPL file, or to continue running the current action. If you select to reload the modified STAPL file, all previous programming settings will be refreshed and will need to be performed again.