Ep Instructions

Design Guide
FactoryTalk eProcedure Instruction File

Important User Information
Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application,
Installation, and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at
http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired
electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid-state equipment, all persons responsible for
applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated
with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and
diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this
manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in
a hazardous environment, which may lead to personal injury or death, property damage, or
economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal
injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a
hazard, and recognize the consequence
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to
alert people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert
people that surfaces may reach dangerous temperatures.
Important: Identifies information that is critical for successful application and understanding of the product.
Allen-Bradley, Rockwell Software, and Rockwell Automation ControlLogix, eProcedure, FactoryTalk, RSBizWare, RSBizWare BatchHistorian, RSBizWare Historian, RSBizWare MaterialTrack, and RSLinx are
trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Table of contents
Chapter 1
Introduction to Document organization .......................................................................................................5

instruction files Work with instruction files .................................................................................................5
Instruction file components ................................................................................................5
Operator instructions ...................................................................................................6
Batch-specific data.........................................................................................................6
Step verification signature ...........................................................................................7
Report data entry fields ................................................................................................7
Valid web content .........................................................................................................9
Chapter 2
Instruction files Use Microsoft FrontPage to build instruction files..................................................... 11

Create a blank instruction file ................................................................................. 12
Add operator instructions ........................................................................................ 12
Include batch-specific data ....................................................................................... 13
Include a step verification signature template ...................................................... 14
Include report entry fields ........................................................................................ 15
Include report value confirmation .......................................................................... 16
Appendix A
Sample HTML code Control step with operator instructions........................................................................ 19

Control step with report data .......................................................................................... 20
Control step with step verification ................................................................................. 21
Control step with confirmation ...................................................................................... 22
Control step with other web content............................................................................. 22
Insert a calendar control............................................................................................ 22
Insert an avi file ........................................................................................................... 24
Use VBScript in instruction files .................................................................................... 25
Appendix B
Archive dynamic Archive dynamic HTML elements................................................................................. 27

HTML elements
Legal Notices Legal Notices ....................................................................................................................... 31
Index Index ..................................................................................................................................... 33
Rockwell Automation Publication FactoryTalk eProcedure Instruction File Design Guide - February 2017 3
Table of contents
4 Rockwell Automation Publication FactoryTalk eProcedure Instruction File Design Guide - February 2017
Chapter 1
Introduction to instruction files
This guide covers the building of instruction files for use in equipment database
creation and recipe development. This guide is intended for use as a reference by
the instruction file author.
Document The following subjects are addressed:
organization • Introducing instruction files

• Using instruction files with FactoryTalk® eProcedure®
• Building instruction files
• HTML requirements for instruction file development
Work with An instruction file is an HTML file that contains the control step(s) required to
instruction files manually execute a phase within FactoryTalk Batch. The instructions are
displayed within eProcedure’s web-based client during recipe execution.
Instruction files can include information such as operator instructions,
batch-specific information, data entry fields for report values, and standard
HTML components.
You need to create instruction files for each eProcedure or manual phase within
your equipment database. Each time you create an instance of the phase, you must
associate the instruction file with the new equipment module. Instruction files can
be created using any text editor or HTML editor. In this guide, Microsoft Word is
used to create the instruction file examples.
Instruction file The fundamental element of an instruction file is the control step. Each
instruction file can contain multiple control steps. A control step must be
components contained within an HTML form and the form must include a submit button.
The submit button is used to inform eProcedure when the control step is
complete. The control steps are executed sequentially in the order they are
encountered in the instruction file.
The following components can be used in a control step:
• Operator instructions
• Batch-specific data
• Step verification signature
Chapter 1 Introduction to instruction files
• Report data entry fields

• Valid web content
Operator instructions With each control step, you can include as many lines of text as necessary to
describe the control step to the operator. You may find it easier to put your text in
tables, allowing you to see where the text is in relation to the submit button.
Batch-specific data Each control step contains information specific to the batch currently running.
The eProcedure Server obtains batch-specific data at run-time by using the custom
tag <sop>, for example <sop>data{.attribute}</sop>. This tag tells the
eProcedure Server to replace the text between the tags with the appropriate
batch-specific data.
The following is a list of the batch-specific information you can include in your
control steps, including the required syntax:
Batch Data
<sop>BatchID</sop> <sop>Cell</sop>
<sop>Unit</sop> <sop>Phase</sop>
Parameter Data
<sop>parameter.Name</sop> <sop>parameter.LowLowLowLimit</sop>
<sop>parameter.EU</sop> <sop>parameter.LowLowLimit</sop>
<sop>parameter.High</sop> <sop>parameter.LowLimit</sop>
<sop>parameter.Low</sop> <sop>parameter.HighLimit</sop>
<sop>parameter.Type</sop> <sop>parameter.HighHighLimit</sop>
<sop>parameter.Value</sop> <sop>parameter.HighHighHighLimit</sop>
<sop>parameter.Default</sop>
(where parameter is the name of a phase parameter in the equipment database)
Report Data
<sop>report.Name</sop> <sop>report.LowLowLowLimit</sop>
<sop>report.EU</sop> <sop>report.HighLimit</sop>
<sop>report.Value</sop> sop>report.HighHighLimit</sop>
<sop>report.LowLimit</sop> <sop>report.HighHighHighLimit</sop>
<sop>report.LowLowLimit</sop> <sop>report.Default</sop>
<sop>report.Type</sop>
(where report is the name of a phase report in the equipment database)
Introduction to instruction files Chapter 1
Step verification If a control step requires a verification signature before the operator is allowed to
signature continue processing, you can add step verification to the control step. You have
the option of requiring one to three sign-offs per verification signature. The
verification signature template is defined in the FactoryTalk Batch Equipment
Editor (see the FactoryTalk Batch Equipment Editor User Guide for more
information).
Important: In earlier versions of eProcedure this feature used

<sop>VERIFY=GROUP1,GROUP2</sop>. In eProcedure version 7.00,
this changed to <sop>VERIFICATIONSIG=SignatureTemplate
</sop> as discussed in the following paragraph.
To specify a verification signature to be used for control step verification, enter:
<sop>VERIFICATIONSIG=SignatureTemplate</sop>
(where SignatureTemplate is the template name used for the verification

signature)
Report data entry Control steps can contain data entry fields that collect report data from the
fields operator. Data entry fields used to collect report data do not require the use of the
<sop> tag. Data entry fields are represented by a text box, text area, or list,
depending on the report data type. Text box controls and text area controls use
REAL, INT or STRING data types for reports, while drop-down box controls use
ENUMERATION data types for reports. You must set the HTML Name
property to match the report name so eProcedure knows which phase report to
associate with each data entry field.
REAL, INT or STRING Data Types
<INPUT TYPE="text" SIZE="20" NAME="report">
CONFIRM Data Types
You can configure a report parameter in an eProcedure instruction step to require

confirmation. The confirmation can require a comment or not, and can be
configured to trigger on the High/Low, High-High/Low-Low, or
High-High-High/Low-Low-Low limits (configured in the FactoryTalk Batch.
Chapter 1 Introduction to instruction files
The available attributes are:
Attribute Value Description

Confirm True/False Determines if confirmation is required if a
report’s value is within the normal range.
Comment True/False Determines if a comment can be entered
with a confirmation if a report’s value is
within the normal range.
HLConfirm True/False Determines if confirmation is required if a
report’s value is outside the High or Low
limits but not outside the High High, High
High High, Low Low, or Low Low Low
limits.
HLComment True/False Determines if a comment can be entered
outside the High or Low limits but not
outside the High High, High High High,
Low Low, or Low Low Low limits.
HHLLConfirm True/False Determines if a confirmation is required if
a report’s value is outside the High High
or Low Low limits but not outside the High
High High or Low Low Low limits.
HHLLComment True/False Determines if a comment can be entered
outside the High High or Low Low limits
but not outside the High High High or Low
Low Low limits.
HHHLLLConfirm True/False Determines if a confirmation is required if
a report’s value is outside the High High
High or Low Low Low limits.
HHHLLLComment True/False Determines if a comment can be entered
outside the High High High or Low Low
Low limits.
Example:
The sample below contains an input for a report value; the report is configured to
require confirmation if the value is outside the High or Low limits, and allows the
operator to enter a comment.
<INPUT type=text NAME="report" HLConfirm=true HLComment=true>

(where report is the name of a phase report in the equipment database.)
ENUMERATION Data Types
<SELECT NAME="report" SIZE="1"></SELECT>

(where report is the name of a phase report in the equipment database.)
Tip: It is recommended that a single instruction form includes no more than two
reports.
Introduction to instruction files Chapter 1
Valid web content Controls steps can include any valid Web page components. The eProcedure
Server will ignore anything that does not meet the required naming conventions,
and your browser will interpret the component as it would in any other HTML
page. AVI files and calendar controls are two examples of valid Web page content.
(See the Control step with other web content topic for more information.)
See also
Control step with other web content on page 22
Chapter 2
Instruction files
Instruction files must be created for each phase within your equipment database
and associated with the appropriate equipment modules within the FactoryTalk
Batch Equipment Editor.
You can use any text or HTML Editor to create instruction files. The instruction
files and examples included in this document use FrontPage® 2003 as the HTML
editor.
Tip: See Customizing eProcedure in the FactoryTalk eProcedure

Administrator Guide for information on customizing the eProcedure
display.
Use Microsoft Microsoft FrontPage must be installed and set up correctly to enable the creation
of instruction files. Since you will be using forms for the eProcedure instruction
FrontPage to build files, you must select Page Options from the Tools menu, then in the General
instruction files tab select Automatically enclose form fields within a form.
Chapter 2 Instruction files
Create a blank The first step in building an instruction file is creating a blank instruction file.
instruction file 1. Open Microsoft FrontPage. FrontPage opens to a new blank page.
2. From the Insert menu, select Form > Form. A new form is inserted on the
page with Submit and Reset buttons.
3. Click the Submit button and press Delete. Repeat for the Reset button,
leaving an empty form. The buttons are not needed as eProcedure inserts an
OK (submit) button at run time.
4. From the File menu, select Save. The Save As dialog box opens.
5. Navigate to the desired location, enter a file name in the File name box, and
then click Save. This file can be used as a starting point for all new
instruction files.
Add operator You can add as many instruction lines as necessary in each form, and add as many
instructions forms as required. The examples in this document use tables, but they are not
required.
1. Open or create a blank instruction file. (See the Create a blank instruction
file topic for more information.)
2. Add as many forms as needed for the instruction file.
3. Return to the first form in the document.
4. With the cursor in the left-hand column, enter instructions in the order in
which you want them performed. Add as many lines as necessary. For
example, you might enter: Prepare <sop>ADD_AMOUNT</sop> KG of
Egg.
5. Press OK to proceed.
Instruction files Chapter 2
6. Move to the next form and enter the required instructions. Repeat until all
instructions are added. The finished file will resemble this:
7. Save the file.
See also
Create a blank instruction file on page 12
Include batch-specific You can add Batch data to your instructions. You must use the proper naming
data conventions to allow the eProcedure Server to replace the tagged string with the
correct recipe data.
2. Place the cursor within the instructions where you will display recipe data.
3. Using the correct naming conventions, enter the tagged data item.
Examples:
• To display the batch ID to the operator at run-time, enter

<sop>BatchID</sop>.
• To display the value of a parameter named AMOUNT, enter
<sop>AMOUNT.VALUE</sop>.
4. Save the file. The following example illustrates batch-specific data created in
FrontPage.
See also
Instruction File Components on page 5
Include a step You can require a step verification signature using a specific signature template for
verification signature a control step. You can add a step verification signature to any control step that
must be signed off before recipe execution continues. Signature templates are
template defined in the FactoryTalk Batch Equipment Editor. The signature must be
complete before recipe execution continues.
2. Place the cursor at the beginning of the first cell.
3. Using the correct naming conventions, enter the tagged data item.
Important: In earlier versions of eProcedure this feature used

<sop>VERIFY=GROUP1,GROUP2</sop>. In eProcedure version
7.00, this changed to
<sop>VERIFICATIONSIG=SignatureTemplate</sop> as discussed
in the following paragraph.
Example:
<sop>VERIFICATIONSIG=SignatureTemplate</sop>
where SignatureTemplate is the name of the desired template.
See also
Include report entry You can add report entry fields to your instructions. You must use the proper
fields naming conventions to allow the eProcedure Server to store the correct data in the
batch record.
2. Place the cursor within the instructions where you will display a report
entry field.
3. From the Insert menu, select Form > Textbox. A blank text box is added to
the instructions.
4. Double-click the text box. The Text Box Properties dialog box opens.
5. In the Name box, type the report parameter name defined in the
FactoryTalk Batch Equipment Editor. The following example uses the
<AMOUNT_ADDED> parameter.
6. Close the Text Box Properties dialog box. The following example
illustrates a text box in a form created in Microsoft FrontPage.
See also
Include report value While the verification method changed with RSBizWare eProcedure version 7.0,
confirmation you can still access a report value confirmation dialog box (Confirm Entry)
through the HTML code. By including the CONFIRM command in the HTML
code for the report entry control step, a Confirm Entry dialog box is generated
when the entered report value is outside the pre-determined limits. You can also
enable the optional comment field on the dialog box.
1. Place your cursor within an instruction file where you want the report entry
field (the Confirm and Comment data types must be associated with a
report parameter).
2. From the Insert menu, select Form >Textbox. A blank text box is added to
the instructions.
3. Double-click the text box. The Text Box Properties dialog box opens.
4. In the Name box, type the report parameter name used in the FactoryTalk
Batch Equipment Editor. The following example uses the
<AMOUNT_ADDED> parameter.
5. Click OK to close the Text Box Properties dialog box. The following
example illustrates a text box added to the form created in Microsoft
FrontPage.
6. Click the HTML tab at the bottom of the FrontPage window to display the
HTML code for the instructions.
7. Locate the line that corresponds with the text box just entered. Add the
code for the Confirm and/or Comment command at the end of the Report
name, before the closing bracket (>), as shown in the following example:
The example above uses the HLConfirm and HLComment parameters.

HLConfirm determines if confirmation is required when a report value is
outside the High or Low limits but not outside the High High, High High
High, Low Low, or Low Low Low limits. HLComment determines if a
comment can be entered with a confirmation when a report value is outside
the High or Low limits but not outside the High High, High High High,
Low Low, or Low Low Low limits.
Tip: For a complete list of parameters used with the Confirm and Comment
data types, see the Control step with confirmation topic.
8. Save the file.
See also
Control Step with confirmation on page 22
Appendix A
Sample HTML code
The following samples provide examples of the HTML code along with screen
shots of the code as it appears with the eProcedure Client.
The examples include controls steps with the following:
• Operator instructions (see Control step with operator instructions.)

• Operator instructions and Batch-specific data (see Control step with
report data.)
• Report data entry fields of all data types (see Control step with step
verification.)
• Non-eProcedure specific web content (see Control step with other web
content.)
See also
Control step with operator instructions on page 19
Control step with report data on page 20
Control step with step verification on page 21
Control step with other web content on page 22
Control step with

operator
instructions <HTML>
<HEAD>
</HEAD>
<BODY LANG="EN-US" STYLE="tab-interval:.5in">
<FORM METHOD="Post"
ENCTYPE="application/x-www-form-urlencoded">
Execute viscosity test number <sop>TEST_ID</sop> on the
sample for batch <sop>BATCHID</sop> from <sop>CELL</sop>.
It will be necessary to conduct three individual tests. Refer
to the testing documentation for instructions.
</FORM>
</BODY>
</HTML>
Appendix A Sample HTML code
Control step with Report Data of Type Integer, Real, or String

report data
<HTML>
<HEAD>
</HEAD>
<FORM METHOD="Post"
Enter the results from the three tests:
Player
Test1:
<INPUT TYPE=TEXT NAME="VISCOSITY1" SIZE="20"
MAXLENGTH="20"><sop>VISCOSITY1.EU</sop>
Player
Test2:
Player
Test3:
</FORM>
</BODY>
</HTML>
Report Data of Type Enumeration
<HTML>
<HEAD>
</HEAD>
<FORM METHOD="Post"
Enter the qualitative results of the tests: <SELECT
NAME="RESULTS" SIZE="1"></SELECT>
</FORM>
</BODY>
</HTML>
Sample HTML code Appendix A
Control step with The following example uses a signature template called StepSig, which requires
one signature.
step verification
<HTML>
<HEAD>
</HEAD>
<FORM METHOD="Post"
Record final amount of Sugar added to batch in SP_MIXER1:
<INPUT TYPE="text" SIZE="20" NAME="ACTUAL_AMOUNT">KG
Press <b>OK</b> to continue.
Player
<sop>VerificationSig=StepSig</sop>
</FORM>
</BODY>
</HTML>
Control step with The following example contains an input for a report value — the report is
configured to require confirmation if the value is outside the High or Low limits.
confirmation You can enter a comment, if desired.
<HTML>
<HEAD>
</HEAD>
<FORM METHOD="Post"
Enter a value for REPORT_1:
<INPUT TYPE="text" NAME="REPORT_1" HLConfirm="True"
HLComment="True">
</FORM>
</BODY>
</HTML>
Control step with The instructions in this section were created with Microsoft FrontPage.
other web content
Insert a calendar In the following example, a calendar is added to an instruction form. Tables
control within the forms allow for easier placement of the calendar. The instruction file
will look similar to the following example:
The HTML code for the previous example resembles the following:
(See the eProcedure Administrator Guide for information on using ActiveX

controls and scripting within your instruction files.)
Insert an avi file The following example shows a movie clip (.avi) file added to eProcedure
instruction forms.
The HTML code that inserts the .avi file into the instruction file resembles the
following:
Use VBScript in If you want to use VBScript with <SOP> elements, the SOP parameters must be
included in a hidden span (labeled parameter1) that contains the <SOP>
instruction files element. At runtime the eProcedure Server replaces the <SOP> element with its
value and the VBScript accesses the value by referencing parameter1.
In the VBScript, insert the element <SOP>parameter1</SOP> where

parameter1 is a legal parameter for this phase:
<FORM>
<SPAN id="Parameter1
style=display:none><SOP>PARAMETER1</SOP></SPAN>
<SCRIPT language=vbscript>
msgbox document.all("Parameter1").innertext
</SCRIPT>
</FORM>
Appendix B
Archive dynamic HTML elements
The following list defines HTML elements that can be contained in an instruction
step, can be dynamic and therefore must be disabled before archiving. (Source:
MSDN Library. See the MSDN library for documentation as to the types of
events that can be defined for each element.)
NAMES DESCRIPTION
a Designates the start or destination of a hypertext
link.
acronym Indicates an acronym abbreviation.
address Specifies information, such as address, signature,
and authorship, of the current document.
applet Places executable content on the page.
area Defines the shape, coordinates, and associated

URL of one hyperlink region within a client-side
image map.
b Specifies that the text should be rendered in bold.
Base Specifies an explicit URL used to resolve links and

references to external sources such as images and
style sheets.
baseFont Sets a base font value to be used as the default
font when rendering text.
bdo Allows authors to disable the bidirectional algorithm
for selected fragments of text.
bgSound Enables an author to create pages with

background sounds or sound tracks.
big Specifies that the enclosed text should be
displayed in a larger font than the current font.
blockQuote Sets apart a quotation in text.
Body Specifies the beginning and end of the document

body.
br Inserts a line break.
button Specifies a container for rich HTML that is
rendered as a button.
caption Specifies a brief description for a table.
center Centers subsequent text and images.
cite Indicates a citation by rendering text in italic.
Code Specifies a code sample.
Appendix B Archive dynamic HTML elements
NAMES DESCRIPTION
col Specifies column-based defaults for the table
properties.
colGroup Specifies property defaults for a column or group of
columns in a table.
comment Indicates a comment that is not displayed.
custom Represents a user-defined element.
dd Indicates the definition in a definition list. The
definition is usually indented in the definition list.
del Indicates text that has been deleted from the

document.
dfn Indicates the defining instance of a term.
dir Denotes a directory list.
div Specifies a container that renders HTML.
Dl Denotes a definition list.
Dt Indicates a definition term within a definition list.
em Emphasizes text, usually by rendering it in italic.
embed Allows documents of any type to be embedded.
fieldSet Draws a box around the text and other elements
that the field set contains.
font Specifies a new font, size, and color to be used for
rendering the enclosed text.
frame Specifies an individual frame within a FRAMESET

element.
frameSet Specifies a frameset, which is used to organize
multiple frames and nested framesets.
Head Provides an unordered collection of information

about the document.
hn Renders text in heading style.
hr Draws a horizontal rule.
html Identifies the document as containing HTML
elements.
i Specifies that the text should be rendered in italic,
where available.
iframe Creates inline floating frames.
img Embeds an image or a video clip in the document.
Input Creates a variety of form input controls.
Input Creates a button control.
type=button
Input Creates a check box control.
type=check box
Input type=file Creates a file upload object with a text box and
Browse button.
input Creates an image control that, when clicked,
type=image causes the form to be immediately submitted.
Archive dynamic HTML elements Appendix B
NAMES DESCRIPTION
input Creates a single-line text entry control similar to the
type=password INPUT type=text control, except that text is not
displayed as the user enters it.
input type=radio Creates a radio button control.
input type=reset Creates a button that, when clicked, resets the

form's controls to their initial values.
input Creates a button that, when clicked, submits the

type=submit form.
input type=text Creates a single-line text entry control.
ins Specifies text that has been inserted into the
document.
isIndex Causes the browser to display a dialog window that
prompts the user for a single line of input.
kbd Renders text in a fixed-width font.
label Specifies a label for another element on the page.

legend Inserts a caption into the box drawn by the fieldSet
object.
li Denotes one item in a list.
link Enables the current document to establish links to
external documents.
listing Renders text in a fixed-width font.
map Contains coordinate data for client-side image
maps.
marquee Creates a scrolling text marquee.
menu Creates an unordered list of items.
meta Conveys hidden information about the document to
the server and the client.
noBR Renders text without line breaks.
noFrames Contains HTML for browsers that do not support

FRAMESET elements.
noScript Specifies HTML to be displayed in browsers that do
not support scripting.
object Inserts an object into the HTML page.
ol Draws lines of text as a numbered list.
optGroup Allows authors to group choices logically in a select
element.
option Denotes one choice in a SELECT element.
p Denotes a paragraph.
plainText Renders text in a fixed-width font without
processing tags.
pre Renders text in a fixed-width font.
q Sets apart a quotation in text.
rt Designates the ruby text for the RUBY element.
Appendix B Archive dynamic HTML elements
NAMES DESCRIPTION
ruby Designates an annotation or pronunciation guide to
be placed above or inline with a string of text.
s Renders text in strike-through type.
samp Specifies a code sample.

script Specifies a script for the page that is interpreted by
a script engine.
select Denotes a list box or drop-down list.
small Specifies that the enclosed text should be
displayed in a smaller font.
span Specifies an inline text container.
strike Renders text in strike-through type.
strong Renders text in bold.
style Specifies a style sheet for the page.
sub Specifies that the enclosed text should be
displayed in subscript, using a smaller font than the
current font.
sup Specifies that the enclosed text should be
displayed in superscript, using a smaller font than
the current font.
table Specifies that the contained content is organized
into a table with rows and columns.
tBody Designates rows as the body of the table.
td Specifies a cell in a table.

textArea Specifies a multiline text input control.
tFoot Designates rows as the table's footer.
th Specifies a header column. Header columns are
centered within the cell and are bold.
tHead Designates rows as the table's header.
title Contains the title of the document.

tr Specifies a row in a table.
tt Renders text in a fixed-width font.
u Renders text that is underlined.
ul Draws lines of text as a bulleted list.
var Defines a programming variable. Typically renders
in an italic font style.
xmp Renders text used for examples in a fixed-width
font.
Legal Notices
Legal Notices Copyright notice
© 2017 Rockwell Automation Technologies, Inc. All rights reserved. Printed in

USA.
This document and any accompanying Rockwell Software products are

copyrighted by Rockwell Automation Technologies, Inc. Any reproduction
and/or distribution without prior written consent from Rockwell Automation
Technologies, Inc. is strictly prohibited. Please refer to the license agreement for
details.
End User License Agreement (EULA)
You can view the Rockwell Automation End-User License Agreement ("EULA")
by opening the License.rtf file located in your product's install folder on your hard
drive.
Trademark Notices
Allen-Bradley, CompactLogix, ControlLogix, Connected Components

Workbench, eProcedure, FactoryTalk, GuardLogix, GuardPLC, Micro800,
MicroLogix, MobileView, MobileView Guard, PanelBuilder, PanelView,
PhaseManager, PlantLink, PlantPAx, PLC-2, PLC-3, PLC-5, PowerMonitor,
RSBizWare, RSBizWare BatchHistorian, RSBizWare Historian, RSBizWare
MaterialTrack, RSLinx, Rockwell Automation, Rockwell Software, SLC,
SoftLogix, Studio 5000, and XMare trademarks of Rockwell Automation, Inc.
Any Rockwell Automation software or hardware not mentioned here is also a

trademark, registered or otherwise, of Rockwell Automation, Inc.
For a complete list of products and their respective trademarks, go to:

http://www.rockwellautomation.com/rockwellautomation/legal-notices/overvie
w.page?#tab4
Warranty
This product is warranted in accordance with the product license. The product’s
performance may be affected by system configuration, the application being
performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in
this document do not cover all the details or variations in the equipment,
Legal Notices
procedure, or process described, nor do they provide directions for meeting every
possible contingency during installation, operation, or maintenance. This
product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the
accompanying software may have changed since the release. Rockwell Automation,
Inc. reserves the right to change any information contained in this document or
the software at any time without prior notice. It is your responsibility to obtain the
most current information available from Rockwell when installing or using this
product.
Environmental compliance
Rockwell Automation maintains current product environmental information on

its website at
http://www.rockwellautomation.com/rockwellautomation/about-us/sustainabili
ty-ethics/product-environmental-compliance.page
Contact Rockwell Automation
Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support/
Index
control step with report data 20
A control step with verification 21
archiving
dynamic HTML 27
I
AVI file control in instruction files 23
instruction files
adding valid web content 22
B AVI file 23
batch calendar controls 22
data 6 components 5
batch-specific data 6, 13 batch-specific data 6
operator instructions 6
create in FrontPage 11
C definition of 5
calendar control in instruction files 22 electronic signature template 7
confirm report values 16 operator instructions 12, 19
control step 5 recipe data 13, 20
report entry fields 15, 20
step verification signature template 14
D
data type
confirm 7
M
enumeration 7 Microsoft FrontPage
INT 7 operator instructions 12
real 7 recipe data 13
string 7 report entry fields 15
document organization 5 step verification signature 14
dynamic HTML
archiving 27
N
naming conventions
E required syntax 6
electronic signatures
template 7
O
equipment database 5
operator instructions 6
F
P
FrontPage
create instruction files 11 parameter data 6
H R
HTML code examples report data 6
control step with confirmation 22 report data entry fields 7
control step with operator instructions 19 required syntax 6
control step with other web content 22
Index
S
signature template 14
submit button 5
V
valid web content 8, 22, 23
Rockwell Automation support
Rockwell Automation provides technical information on the web to assist you in using its products. At
http://www.rockwellautomation.com/support you can find technical and application notes, sample code, and links to software service packs. You
can also visit our Support Center at https://rockwellautomation.custhelp.com for software updates, support chats and forums, technical
information, FAQs, and to sign up for product notification updates.
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more information, contact your local
distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/services/online-phone.
Installation assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact
Customer Support for initial help in getting your product up and running.
United States or Canada 1.440.646.3434

Outside United States or Canada Use the Worldwide Locator available at http://www.rockwellautomation.com/locations,
or contact your local Rockwell Automation representative.
New product satisfaction return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if
your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the
phone number above to obtain one) to your distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
feedback form, publication RA-DU002.
Copyright © 2017 Rockwell Automation Technologies, Inc. All rights reserved. Printed in the U.S.A.

Ep Instructions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ep Instructions

Uploaded by

Copyright:

Available Formats

Design Guide

FactoryTalk eProcedure Instruction File

Introduction to Document organization .......................................................................................................5

Instruction files Use Microsoft FrontPage to build instruction files..................................................... 11

Sample HTML code Control step with operator instructions........................................................................ 19

Archive dynamic Archive dynamic HTML elements................................................................................. 27

Legal Notices Legal Notices ....................................................................................................................... 31

Index Index ..................................................................................................................................... 33

Introduction to instruction files

Document The following subjects are addressed:

organization • Introducing instruction files

The following components can be used in a control step:

• Report data entry fields

(where parameter is the name of a phase parameter in the equipment database)

(where report is the name of a phase report in the equipment database)

Important: In earlier versions of eProcedure this feature used

To specify a verification signature to be used for control step verification, enter:

(where SignatureTemplate is the template name used for the verification

REAL, INT or STRING Data Types

<INPUT TYPE="text" SIZE="20" NAME="report">

CONFIRM Data Types

You can configure a report parameter in an eProcedure instruction step to require

The available attributes are:

Attribute Value Description

<INPUT type=text NAME="report" HLConfirm=true HLComment=true>

ENUMERATION Data Types

<SELECT NAME="report" SIZE="1"></SELECT>

Control step with other web content on page 22

Tip: See Customizing eProcedure in the FactoryTalk eProcedure

2. Add as many forms as needed for the instruction file.

3. Return to the first form in the document.

7. Save the file.

Create a blank instruction file on page 12

• To display the batch ID to the operator at run-time, enter

Instruction File Components on page 5

Create a blank instruction file on page 12

2. Place the cursor at the beginning of the first cell.

Important: In earlier versions of eProcedure this feature used

Create a blank instruction file on page 12

Create a blank instruction file on page 12

The example above uses the HLConfirm and HLComment parameters.

8. Save the file.

Control Step with confirmation on page 22

Sample HTML code

The examples include controls steps with the following:

• Operator instructions (see Control step with operator instructions.)

Control step with operator instructions on page 19

Control step with report data on page 20

Control step with step verification on page 21

Control step with other web content on page 22

Control step with

Control step with Report Data of Type Integer, Real, or String

Report Data of Type Enumeration

(See the eProcedure Administrator Guide for information on using ActiveX

In the VBScript, insert the element <SOP>parameter1</SOP> where

Archive dynamic HTML elements

applet Places executable content on the page.

area Defines the shape, coordinates, and associated

Base Specifies an explicit URL used to resolve links and

bgSound Enables an author to create pages with

blockQuote Sets apart a quotation in text.

Body Specifies the beginning and end of the document

del Indicates text that has been deleted from the