Work Instructions Features
•
|
Work Instructions are HTML based. Editing work instructions is done using our built-in HTML WYSIWYG editor which allows for customizing the formatting, adding bullets, attaching pictures and also including text colors and fonts.
|
•
|
This version of the software allows the Work instructions to be displayed alongside the selected Operation / Activity / Location / Resource.
|
•
|
Work Instructions can be defined for:
|
•
|
Work Instructions can have documents attached, e.g. Images, Video, Audio, and other files (text, spreadsheet, etc.).
|
•
|
Work instructions can be assigned globally (same instruction, for each time the node is referenced) or overwritten locally (specific to the instance of the node).
|
•
|
Templates can be user-defined in order to determine the layout format for the aggregated work instructions (saved in HTML). Special formatting codes are available for automatically creating header and footer information.
|
•
|
Work instructions can be generated (aggregated) by process or location
|
•
|
Process based instructions in the mBOM view aggregate all of the Operation, Activity, Location and Resource instructions necessary to create an end-item or sub assembly.
|
•
|
Workstation based instructions in the Plant view aggregate all of the Activity, Location, and Resource instructions necessary to document everything the operator needs to know on the shop floor.
|
•
|
Distribute the work instruction to the Shop Floor. Instructions can be delivered to the shop floor over the company intranet. The instructions may also be printed bound via traditional methods.
|
Global / Local Overview
Local Work Instructions has priority over Global Work Instructions.
Global Work Instructions are common for every instance of operation / activity / component / resource / location. Local Work Instructions are different for every instance of operation / activity / component.
User Interface Overview
Work Instructions Module
 Figure 1: Process Work Instructions Editor |
1. The Operation is the top most node, underneath are the sub operations and the activities
2. The Designer is the editing area, the user can open the corresponding instructions in there and make changes.
3. The preview gives the final view of the instructions; the user can publish from here or print it out as well.
Tree Structure
 Figure 2: Tree structure |
The root of the Work Instruction Object Tree is the Operations Node, which contains all the selected operations. Each operation contains Activity Nodes and each activity node has Activity Locations nodes, and Resources nodes.
Tool Bar

The work instructions tool bar provides you with a variety of formatting options. New to 2.7 is the ability to add a page break in your work instructions. To do so, click on the location in your work instruction you want a page break and then click on the page break button
Data Model
All Operations and Activities can have Global and Local Work Instructions. Resources and Locations (Activity Location) can only have global Work Instructions.
 Figure 3: Data model |
Work Instruction Template
Proplanner allows the user to define templates for work instructions. The user could define header and the footer information, specify tables, and specify logos etc. There a few special codes that the user has to follow in order to create a template.
Note: The user can upload only one template at a time and the template has to be named as “default.htm”.
Special Codes
There are two types of special code, “[@keyword]”, and “[#keyword]”. The difference being that @ codes represent child objects e.g. Resources, Components, etc. and # codes represents attributes of the child objects e.g. Name, Description, ID, etc.
[@keyword]
Inserts all the child activities under an operation
Inserts all the child resources under an activity
Inserts all the child activities under an operation
Inserts all the components being consumed by that activity
Inserts all of the information contained in the control plan
[#keyword]
ID
Inserts the ID for the selected node
Nodes:
Operations, Activity, Resources, Locations, Components (C), Components (p)
Name
Inserts the Name for the selected node
Nodes:
Operations, Activity, Resources, Locations, Components (C), Components (p)
Description
Inserts the Description for the selected node
Nodes:
Operations, Activity, Resources, Locations, Components (C), Components (p)
Custom field name
Inserts the custom field value for the selected node.
Nodes:
Operations, Activity, Resources, Locations, Components (C), Components (p)
For e.g., if an Activity A1 has a custom field “RPM” defined and the value for the same is 1600, then in the corresponding work instruction the user needs to put in the key word [#RPM], and in the work instruction the value 1600 will show up.
Freq
Inserts the Frequency for the selected node
Nodes:
Operations, Activity
BaseFreq
Inserts the Base Frequency for the selected node
Nodes:
Operations, Activity
TreeOrder
Inserts the Tree Order for the selected node
Nodes:
Operations, Activity
Version
Inserts the Version for the selected node
Nodes:
Operations, Activity, locations, Components (C), Components (p)
EstTime
Inserts the Estimated Time for the selected node
Nodes:
Operations, Activity
CalcTime
Inserts the Calculated Time for the selected node
Nodes:
Operations, Activity
ObsTime
Inserts the Observed Time for the selected node
Nodes:
Operations, Activity
SetupTime
Inserts the Setup Time for the selected node
Nodes:
Operations, Activity
LastModifiedOn
Inserts the Last Date the node was modified for the selected node
Nodes:
Operations, Activity, Components (C), Components (p)
LastModifiedBy
Inserts the Name of the Last person to modify for the selected node
Nodes:
Operations, Activity, Components (C), Components (p)
Quantity
Inserts the Quantity for the selected node
Nodes:
Resources, Components (C), Components (p)
Category
Inserts the Category for the selected node
Nodes:
Resources
Notes
Inserts all notes for the selected node
Nodes:
Resources
Example of Work Instruction View
Designer View
 Figure 4: WI designer view |
Preview
 Figure 5: WI preview tab |
Templates in Work Instructions
Proplanner allows the user to create customizable Templates for Work Instructions.
Changing the Style of a Template
In the HTML file there are <STYLE> <\STYLE> tags in where the user could modify the style of the template. The user could change the page margins, the indents, the font, the background color, the heading style and so on, for more information visit the World Wide Web consortium (http://www.w3.org/MarkUp/Guide/Style).
•
|
In the style section find, H1 {font: 15pt/17pt "Times New Roman"; font-weight: bold; color: black} this is the heading for the work instruction.
|
•
|
The user could change the font attributes of size, type, color etc. A change made here would be reflected at every node this template is attached to.
|
Changing the Layout of the template
The user could change the layout of the template, including the default images and logos that he wants to have in each instruction
•
|
In the <PP_ACTIVITY_GLOBAL> tag there is the following section.
|
<TD width="50 %">< STRONG>Activity Overview: [#ID] ([#Name]) </STRONG></TD>
<TD width="50 %">
<P align=right><IMG src="76fa1c09-ec2c-493b-a064-35b075373c4d.GIF"></P></TD></TR></TBODY></TABLE>
•
|
The user should go and change the image, by changing the IMG src.
|
Changing the Contents of the Template
The default.html file defines the contents of the template. The <PP_ACTIVITY_GLOBAL> tag is defined for all activities. Changing the contents of this tag would change the fields that are visible for each activity.
The tags here denote the frequency, tree order, and version, modified by and modified on information for an activity.
<TD>Freq: [#Freq]</TD>
<TD>Tree Order: [#TreeOrder]</TD>
<TD></TD></TR>
<TR>
<TD>Version: [#Version]</TD>
<TD>Last Modified: [#LastModifiedOn]</TD>
<TD>Last Modified By: [#LastModifiedBy] </TD>
</TR></TBODY></TABLE>
The user remove some of these tags like, frequency and tree order and they would not show up in the work instruction.
Note: Changes made to the default file would be reflected for all activities and operations.
Importing\Exporting Templates
 Figure 6: Refer the Template Manager section in tools to learn about Import and Export of templates |
Creating Work Instructions
The work instructions module allows the user to create work instructions for operations, activities, resources and locations.
Creating Work Instructions in MBOM
1. Click on an operation/activity.
2. The tree structure lists the different sub-operations, activities, activity locations and resources related to that operation.
3. Click on Edit and that will bring up the corresponding template. The user can now start editing the instruction.
 Figure 7: Attaching images |
4. Attaching Images - The images specified in the list are brought in through the Documents module or through the Project Documents option.
· Click on the Insert Image icon.
· This brings the Select File form. The user can either select an image from the list or browse to the system to pick up the image.
Note: The work instruction created will be for the operation selected and will include the work instructions for all the activities, locations and resources under it.
5. Once the work instructions for all nodes are created, close the form and click on the “Preview” tab, this should show a print preview of the work instructions created.
The user can also publish the work instruction to a server on the network, for detailed instructions refer to the publishing section of the help manual.
Creating Work Instructions in Plants/Resources
 Figure 8: Creating WI for plants and resources |
1. Click on an activity location in the Plants tree and select the “Work Instructions” tab page.
2. Click edit and this will bring up the default template, the user can now edit the same and insert images, hyperlinks etc.
1. Click on a Resource in the Resource tree and select the “Work Instructions” tab page.
2. Click edit and this will bring up the default template, the user can now edit the same and insert images, hyperlinks etc.
|