Benefits of
e
Procedure

FactoryTalk
eProcedure
 reduces the amount of effort required to create and maintain recipes, as well as minimizes the time required to collect and report Batch data.
The following describes a typical recipe execution process, with and without
eProcedure
:
Without
eProcedure
With
eProcedure
A master recipe (a collection of SOPs) is maintained in written form. The master recipe includes instructions for the operator, places to enter data, and places for any required signatures.
A master recipe is created and maintained electronically with the
FactoryTalk Batch
 Recipe Editor. The master recipe includes operator instructions, report data, and prompts for required approvals.
When a batch needs to be run, the recipe is printed and given to the operator, who reads the instructions, manually sequences the process and enters the required information on the printout.
When a batch needs to be run, the operator adds a batch using
FactoryTalk Batch View
, steps through the instructions, and enters the required data into the system.
When the batch is complete, the completed recipe document is filed.
When the batch is complete, the electronic batch record contains a complete record of the entire batch process.
The data can be manually entered into a database for recording and reporting purposes.
The electronic batch record can be automatically transferred to any ODBC‑compliant database using the
FactoryTalk
 Event Archiver.
FactoryTalk
eProcedure
 can be implemented in a completely manual manufacturing facility or in a partially automated facility. With
eProcedure
, use all manual phases or a combination of manual and automated phases within a single recipe. Regardless of the state of automation, the implementation process is the same.
The
FactoryTalk Batch
 Equipment Editor is used to define the process equipment, both manual and automated. The modular approach in defining equipment is as appropriate with manual facilities as it is in automated facilities. As part of the configuration process, attach instruction files to each of the manual equipment modules.
Instruction files are HTML files that include all of the required control steps for a phase. Each control step can include textual instructions, embedded parameter values, report fields for operator input, and submit buttons. Control steps may also include any valid HTML component.
Once the equipment is defined, and the instruction files are created, create recipes in the same fashion as a completely automated facility.
FactoryTalk
eProcedure
 allows the operator to create and command batches from remote computers using Microsoft Internet Explorer. With
eProcedure
, the operator no longer needs to write processing information on a piece of paper for submission. The operator enters the data directly into the computer where the data is stored in an electronic batch record, which can later be downloaded into your ODBC-compliant database.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal