10.B.5 TEMPLATE LOADING PROCEDURE
1. CSV FILE LIST The Starterkit CD file “CSV_File_List_7.00.01.00.xls” lists all Device and other graphic csv files. It also lists the files by Template type (_A0, _B0, or _C0)
Make sure to DBLoad the Base csv files listed in this document to your project application before converting any Device Shapes, Device Scripts, or Device Control Windows.
2. LOADING CSV FILES ? ? ? ?
3. IMPORTING AND CONVERTING SCRIPTS ? ? ? ?
Import and convert the Quick Function “DeviceRESET”.
Import and convert all Quick Functions that apply to the devices you will be using.
Import and convert all Active X Event Scripts that apply to the devices you will be using.
Import and convert all Data Change Scripts that apply to the devices you will be using.
Based on the requirements of your system, you will need to modify and load additional CSV files that correspond to the Devices you will be using. To determine which CSV files you must modify, examine the following Device Cross-Reference Excel Workbook:
4. IMPORTING AND CONVERTING WINDOWS ?
?
Import any “SKGS” windows that contain device graphics that you will be using. Copy the device graphics to your process window, and configure the graphic using the following method:
Import and convert all Device Bottom windows that apply to the devices you will be using.
D:\\Starter_Kits\\WonderWare\\Documentation\\Device_Xref.xls Dbload the file “Device.csv” to your Intouch application. Dbload the file “Device_MLS.csv” to your Intouch application. For Devices with PID Loops, Dbload the file “PID.csv” to your Intouch application.
For Devices with PID Loops, Dbload the file “PID_MLS.csv” to your Intouch application.
1. Click on the Device graphic cell that you placed on your process window.
Select the “Substitute Tags” from the Intouch “Special” menu.
2. Use the “Replace” function to replace all base tags (“FVxx”, “Mxx”, etc.)
with the base tags you have configured for the device.
3. Convert all tags and click OK. Your device should be ready for use.
10.D. Graphic Standards
This contains the Graphic and InTouch standards and conventions that were used to build the Wonderware StarterKit and that are recommended for project use.
Standards are: ? ? ? ? ? ?
Graphic Standards Tag Naming Conventions Window Naming Conventions Window Navigation Methodology Window_Version_Management Script Version Management.doc
10.C.1 INTRODUCTION TO GRAPHIC STANDARDS
1. Introduction
This document describes the basic philosophy and recommended standards to be used within Procter and Gamble for Custom Graphic displays created on Wonderware Intouch Human-Machine Interface (HMI) applications.
2. Use of this Document
Instructions on graphics, which are detailed in the project documents, take priority over standards contained in this document. Any details about graphics, which are not covered in the project documents, are to follow the standards in this document.
This document also describes how to use the standards in the P&G Starter Kit. The best way to gain an understanding of the Starter Kit Shapes and Popups is to read this document and then examine the \in the P&G Starter Kit Intouch Application portion of the Starter Kit. Examine the application in both the Runtime and the Development mode.
3. Philosophy
The objective is to produce screens, which are consistent throughout the process or machine and the company. The screens should also be cost effective to build, easy to use, and intelligent.
4. Consistency
Screen layout should be similar. ?
Colors - The colors should be neutral when the process or machine is in a
normal state. They should also be standard for the different parts of the process.
?
Shapes - A standard P&G shape library is part of this practice.
? Alarms - The same type of alarm should have the same effect from
screen to screen, and the noticeable colors (i.e., Red Flashing, etc.) should be reserved for alarms.
? ? ? ?
Buttons - Screen keys should be the same size, same color, and in the
same location.
Messages and Prompts - Should be displayed at the same location on
the screen.
Movement between screens - Movement from screen to screen should
require the same steps, or keystrokes. Data - Data displays should have the same form.
color and shape. They should come from the P&G shape library when possible.
? Process or Machine Equipment - all equipment should be consistent in
5. Ease of Use
All screens should be easy to use. This will be accomplished in part by making the screen consistent.
6. Simple versus Complex
Screens and symbols should be drawn as simply as possible. This allows the space on the screens to contain as much meaningful data as possible.
Complex, 3-dimensional figures are NOT recommended because they are unproductive, expensive, and occupy too much screen space. They do not add value! All shapes and text require space and if they are drawn with unnecessary details, each graphic will contain a lower amount of useful data.
All shapes and popup screens in the Starter Kit were created with standard Intouch graphic and animation commands. The only Wizards that were used are the simple push-buttons. This makes it possible for any project engineer or technician to dissect and modify the graphics if needed. A working knowledge of programming languages such as \order to modify graphics.
7. Intelligence
The screens should take full advantage of the Intouch capabilities.
Whenever possible, use of items which make Intouch utilize more memory or processor time should be avoided!
8. Fonts
The recommended font for all screen text is \languages). These reasons for this recommendation are:
?
Courier New is an Equal Spaced font, which means that a text object built for a specific number of characters of a given size will occupy the same screen space for any mix of Numeric, Upper Case, Lower Case, and Special Characters. ? ?
It is a True Type font, which means screen printouts will look just like the screen image.
Courier New is a very common font that is provided with most basic operating systems.
9. Conclusion
The main philosophy is to produce screens which are consistent throughout the application and company, cost effective to build, easy to use, and intelligent. This philosophy will reduce training costs by allowing
reapplication throughout P&G, produce a system which is easier to document and maintain, make the operating process or machine safer, and reduce the number of mistakes in the process or machine. These improvements can only be acheived if every line organization, technology support group, contractor, and manufacturing plant that install Intouch systems follow the guidelines.