Common Functionality User Guide
Common Functionality User Guide
Common Functionality
User Guide
AVEVA Solutions Limited
Disclaimer
AVEVA Instrumentation provides instrument sizing calculations for estimation purposes only, end users of the
software should not rely on the calculations produced by the software for design purposes. End users should seek
the advice of certified equipment suppliers prior to specifying or purchasing equipment.
a) AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses;
b) AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the customer, including any loss suffered by the customer resulting from the inaccuracy or invalidity of
any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or
arise in contract, tort (including negligence) or otherwise;
c) AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the
customer's claim is brought.
In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
All intellectual property rights, including but not limited to, copyright in this manual and the associated software,
(including source code, object code, and any data) belongs to or is validly licensed by AVEVA Solutions Limited or
its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not reverse
engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in
this publication may be incorporated into any third-party software, product, machine, or system without the prior
written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms
and conditions of the respective licence agreements, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the product is strictly prohibited.
© Copyright 2000 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
The AVEVA Instrumentation user interface is based on the Microsoft® Office Fluent™ user interface.
Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Group plc or its subsidiaries. AVEVA product names are
trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
trademarks belonging to AVEVA Group plc or its subsidiaries is strictly forbidden.
Fluent is a trademark of Microsoft Corporation and the Fluent user interface is licensed from Microsoft Corporation.
The Microsoft Office User Interface is subject to protection under U.S. and international intellectual property laws
and is used by AVEVA Solutions Limited under license from Microsoft.
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Instrumentation Common Functionality User Guide
Revision Sheet
Contents Page
Common Functionality
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1
Area Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Area-Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:5
Claims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
Instrument Sizing Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1
Control Valve Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
Formulas Used For Liquids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:2
Formulas Used For Gases (Compressible Fluids) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:4
Typical Values for FL and XT and Fd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:6
Why Molecular Weight and Compressibility are Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . A:6
Relief Valve Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:7
Fundamental Equations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:7
Application to Relief Valves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:9
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:12
Flow Element Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:13
Calculation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:14
Pressure Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:15
Other Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:15
Thermowell Vibrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:16
Tapered Thermowells Natural Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:16
Analysis of a Cylindrical (Parallel) Thermowell (or Sample Quill) . . . . . . . . . . . . . . . . . . . A:18
Order of Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:20
Gas Compressibility Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:21
Compressibility Factor by Redlich-Kwong Equation of State . . . . . . . . . . . . . . . . . . . . . . . A:21
Equation of State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:21
Redlich-Kwong EoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:22
Expression of Z as a Function of Reduced Pressure and Reduced Temperature . . . . . . . A:23
Solving Equation 4.2.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:24
1 Introduction
Areas Describes the procedure for adding plant areas to the project
database. All objects in AVEVA Instrumentation are assigned to
one of these areas.
Import and Export Describes import and export procedures that are common to
Procedures multiple AVEVA Instrumentation modules.
Work Packs Describes the procedure for creating and editing work packs,
collections of items with shared project management
requirements or properties.
Change Reports Describes the Audit Manager, which enables users to view
database changes made to the project, and the Project
Revisions facility, used to track changes between key
milestones in the project.
AVEVA NET Export An appendix describing the configuration files used by the
Configuration Files AVEVA Schematic Gateway to process data exported from
AVEVA Instrumentation.
2 AVEVA Instrumentation
Projects using AVEVA Instrumentation are less error prone than conventional design
methods:
• Data is checked and validated by the database system.
• Data is electronically transferred, reducing errors and associated checking time.
• Use of a relational database means that data changed in one place is changed
throughout the database and reflected on all deliverables generated using that content.
• Construction and commissioning time is reduced due to improved design accuracy.
2.2 Intelli-Link
The use of Intelli-Link enables P&ID drawings drawn in AutoCAD (or AutoCAD LT) to be
scanned to check instrument data contained in drawings against data in the AVEVA
Instrumentation Instrument Index. Any differences are reported and can (optionally) be
imported into and changed in the index. Intelli-Link should work with most drawing symbols
and is user configurable. Intelli-Link can import tags directly from P&IDs into AVEVA
Instrumentation.
Intelli-Link does not require AutoCAD for auto tag checking/scanning. However, Intelli-Link
can use AutoCAD to create connectivity, including line lists (with sources and destinations)
and update AVEVA Instrumentation 'Plant Connection' data (i.e. the line numbers and
equipment numbers that instruments are connected to) from most existing AutoCAD P&ID
drawings. The user will not therefore need to redraw P&IDs in order to produce intelligent
drawings.
Note: Windows Region and Language settings support displaying decimal symbols as
commas. In AVEVA Instrumentation decimal symbols are currently displayed as
decimal points regardless of this setting.
3 User Interface
The User Interfaces of the Designer, Engineer, Process Engineer and Wiring Manager
modules share a number of common features:
• The procedure for selecting and opening projects. See Open an AVEVA
Instrumentation Project for details.
• Most commands, facilities and utilities of these modules are accessed from a number
of tabs. Refer to Tabs for details.
• Options on these tabs can be added to the Quick Access Toolbar for convenient
access. The default location of this toolbar is above the tabs, but it can be moved below
them if required. Refer to Quick Access Toolbar for details.
• Project data in AVEVA Instrumentation is viewed and edited using a number of data
grids. For details of the common features of the data grids, see Data Grids.
The Select an AVEVA Instrumentation Project window can also be opened by selecting
the Open Project option from the Project Tab of all modules.
Double-click on the project to be opened, or click on it then click Select.
The login procedure then depends on the authentication type of the project (see the Security
Manager User Guide for details).
• If Windows Authentication (the default option) is the authentication method being used
for the project, the project is then opened.
• If SQL Server Authentication is the authentication method being used for the project,
the SQL User Login window is displayed:
Enter valid SQL server login details and click OK. The project is then opened.
• If AVEVA Project Authentication is the authentication method being used for the
project, the Project User Login window is displayed:
Enter valid project user login details and click OK. The project is then opened.
If the project database is at an earlier version than that of the product, it will need to be
upgraded before it is opened. See Database Upgrade.
If the project is being opened for the first time, the following message is displayed:
Enter the password for Security Manager and click Login. Refer to the Security Manager
User Guide for more details of Security Manager and passwords.
The Database Upgrade window is then displayed:
Select the product version to upgrade to from the list and click Upgrade.
A message is then displayed. For example:
Click OK to proceed with the upgrade. The progress of the upgrade is displayed:
After the upgrade is finished, select the project from the Select an AVEVA Electrical
Project window to open it.
3.2 Tabs
On opening, the Designer, Engineer, Process Engineer and Wiring Manager modules each
display four tabs: Project, Home, Manage and View. Once a grid is opened, an optional "List
Tools" tab, named after that grid and containing commands specific to that grid, is displayed
if applicable.
When a module is opened, the Home tab is initially displayed.
If required, the tabs, apart from their titles, can be hidden to save space.
To hide the tabs, right-click on them and select the Minimize the Ribbon option from the
menu that is then displayed, double-click on any tab, or click the button the right-hand end of
the ribbon (next to the Help button).
Repeat the above procedure to “un-hide” the tabs.
Work Packs Accesses the Work Packs sub-menu, used to activate and
deactivate Work Pack mode for a selected Work Pack, create
new Work Packs and add and remove drawings to and from
them. See Work Packs for details.
Setup Sub-Menu
The following options are common to each module.
Add/Edit Plant Areas Used to create and edit plant areas for the project. Refer to
Areas for details.
Add/Edit Plant Area Used to create and edit plant areas for the project. Refer to
Types Areas for details.
Edit Pick Lists Displays the Pick List (All) window enabling users to add
and edit PickLists, including the adding of new items to
PickLists. Refer to Pick Lists for further information.
Publish to AVEVA NET Displays the AVEVA NET Export Configuration window.
Configuration Refer to module documentation for details.
Lists Section
Select Used to select and open a data grid. See Open a Grid for
details.
Manage Used to select, create and edit grid views. See Grid Manager
for details.
Clipboard Section
These options in this section are used to cut, copy and paste from and to a data grid. See
Copy, Cut and Paste Commands for details.
Records Section
These options are used to refresh data in a grid, and to create edit and delete records. For
details see Other Common Grid Commands.
The options in this section are also located on the List Tools tabs.
Reports Section
Report Manager Used to open the Report Manager, used to view, create and
modify user-created reports. See Report Manager for details.
Custom Reports Used to open the Custom Reports window. See View, Edit
and Create Custom Reports for details.
Fixed Reports Displays the list of “fixed” non-user generated reports supplied
with the AVEVA Instrumentation for the module. For details,
refer to the appropriate module documentation.
Changes Section
These options provide access to the Audit Manager, which enables users to view database
changes made to the project, and the Project Revisions facility, used to track changes
between key milestones in the project. See Change Reports for details.
Integration Section
The options in this section provide access to facilities for integrating module data with other
AVEVA products. For details refer to the appropriate module documentation.
Import Section
The options in this section provide access to facilities for importing data into AVEVA
Instrumentation from non-AVEVA products.
For details of the common procedure for importing from Excel, see Import from Excel.
For details of other import procedures, refer to the appropriate module documentation.
Export Section
The options in this section provide access to facilities for exporting data from AVEVA
Instrumentation to Excel, XPS and PDF files.
For details of the procedure for exporting from Excel, see Export to Excel.
For details of the procedure for exporting to XPS and PDF files, see Export to XPS and PDF
Files.
Window Section
The options in this section are used to change the arrangement of grid tabs. Refer to Grid
Window Options for details.
The List Tools tab contains options specific to the grid which is currently being viewed. If no
grid is open, the tab will not be displayed.
It also includes the options from the Records section of the Home tab (see Other Common
Grid Commands for details).
The name of the tab will be the name of the current grid.
For details of the options on this tab, refer to the appropriate module documentation.
To add a tab option to the toolbar, right-click on it and select the Add to Quick Access
Toolbar option from the menu that is then displayed.
By default, the toolbar is located above the tabs. If required it can be moved below the tabs
by selecting the Show Quick Access Toolbar Below the Ribbon option from the right-click
menu shown above, or the Show Below the Ribbon option from the Customize Quick
Access Toolbar menu displayed by clicking the arrow at the end of the toolbar.
Once the toolbar is below the ribbon, the menu options become Show Quick Access
Toolbar Above the Ribbon and Show Above the Ribbon, and are used to move the
toolbar back to its original position.
The Customize Quick Access Toolbar menu also includes options for removing and
returning the Undo and Redo buttons from and to the toolbar.
3.4.1 Windows XP
To enable Cleartype effects on Windows XP: right-click on the desktop and select
Properties from the pop-up menu.
From the Display Properties window that is then displayed, select the Appearance tab,
and click the Effects button.
On the Effects window, check the Use the following method to smooth edges of screen
fonts: checkbox, and from the list beneath the checkbox, select the ClearType option.
3.4.2 Windows 7
To enable Cleartype effects on Windows 7: open the Control Panel.
If Control Panel options are being displayed in the “Category” configuration, select
Appearance and Personalization and then Display.
If Control Panel options are being displayed in the “Small Icons” or “Large Icons”
configuration, select Display.
Select Adjust Clear Type Text from the list of options on the right-hand side of the window.
The ClearType Text Tuner window is then displayed.
Check the Turn on ClearType checkbox. Click Next and step through the tuning wizard.
Finally, click Finish to implement the changes.
4 Data Grids
Project data in AVEVA Instrumentation is viewed and edited using a number of data grids,
one for each category of data.
This section describes data grid functionality common to multiple AVEVA Instrumentation
modules.
The list may be divided into categories of grid, e.g. Lists and Catalogues, as in the example
above.
Click on a grid name to open it.
Each grid is displayed in its own tab. To switch from one open grid to another, click on the
appropriate tab title. Options for changing the arrangement of grid tabs are available. Refer
to Grid Window Options for details.
When a list is opened, an additional “List Tools” tab, named after that grid and containing
commands specific to that grid, is displayed (if there are any).
Pin Rows
When a row is pinned it remains at the top of the grid even when the grid is scrolled down,
so that it is always in view.
Pin icons are displayed to the left of the first column of a grid if the facility for pinning rows is
turned on for it. If not, to activate the facility for pinning rows for the current grid, check the
Pinned Rows checkbox in the Grid Options section of the View Tab.
To pin a row, click on its pin icon.
When a row is pinned, its pin icon changes orientation, so that its point is downwards.
To unpin a row, click its pin icon again.
Resize
To resize a column, click and hold on the line between columns and drag the line left or right
to make it wider or narrower. Double-clicking on the line will resize the column to fit the
longest string of characters within that column.
Sort a Grid
The user can sort the Data Grid on any combination of fields by clicking on a column (field)
name. To sort by multiple fields hold the <Shift> key while making selections. The grid will
be sorted in the order that the columns are selected.
Pin Columns
When a column is pinned, it automatically becomes the first (left-hand most) column of the
grid, and remains displayed at the left-hand side of the grid even when the grid is scrolled to
the right, so that it is always in view.
Pin icons are displayed in headings of a grid if the facility for pinning columns is turned on
for it. If not, to activate the facility for pinning columns for the current grid, check the Pinned
Column checkbox in the Grid Options section of the View Tab.
To pin a column, click on its pin icon.
When a column is pinned, its pin icon changes orientation, so that its point is downwards.
To unpin a column, click its pin icon again.
Column Summaries
The average, count (i.e. number of values), minimum, maximum and total values of a
column containing numbers only can be calculated and displayed beneath the column.
Sum icons are displayed in the headings of a grid if the summarise columns facility is turned
on for it.
If not, to activate the facility for the current grid, check the Column summaries checkbox in
the Grid Options section of the View Tab.
To specify which summaries are to be displayed, click on the icon. The Select Summaries
window is then displayed:
Check the checkboxes for the summaries which are to displayed, then click OK.
The selected summaries are then displayed beneath the column. For example:
To turn on this facility for a grid, check the Merged cells checkbox in the Grid Options
section of the View Tab.
Drag the line back to its original position to remove the split.
If not, to activate the facility, check the Grouping panel checkbox in the Grid Options
section of the View Tab.
To group data, drag and drop the column heading of the attribute in question into the
grouping panel.
The grid then changes to display the name of each group in the following format:
<Attribute Name>: <Attribute Value> <(Number of records in the group)>.
The name of the column that records are grouped by is displayed in the grouping panel.
To view the items within a group, click on the "+" button next to the group name. The items
are then listed under the name. Press the "-" button to close the list.
Note: The fields within a group can be fixed, sorted, moved and filtered in the normal way.
If the second heading is dropped to the left of the first heading, records will be grouped the
other way round.
To apply a basic column filter, select a filter criterion, for example, ‘Starts with’, ‘Contains’ or
‘Does not end with’ from the drop-down list displayed by clicking the left-hand button in the
filtering row of the column.
If a value is selected without a criterion being selected, the ‘Starts with’ criterion is applied
by default.
Then either enter a value in the field to the right of the criterion selection button, or click on
the button to the right of this field and select a value from the list that is then displayed.
The list contains every value in the column, plus ‘Custom’, ‘Blanks’ and ‘NonBlanks’. If
‘Custom’ is selected the window used to construct advanced grid filters is displayed. Refer
to Apply Advanced Grid Filters for details.
If ‘Blanks’ is selected rows without a value in the column are displayed when the filter is
applied. If ‘NonBlanks’ is selected rows with a value in the column are displayed.
The selected value is displayed in the field between the two buttons.
The filter is then applied to the grid.
The window lists all the values in the column, plus ‘All’ and ‘Blanks’.
Next to each item in the list there is a checkbox. To filter out a value from the column,
uncheck its checkbox. To uncheck all values, uncheck the ‘All’ checkbox. Check the ‘All’
checkbox again to check all the checkboxes again.
If the ‘Blanks’ checkbox is checked, rows without a value in the column are displayed when
the filter is applied.
When the required filter conditions have been selected, click OK to close the window and
apply the filter.
The filter is then applied. The value that the column is being filtered by is displayed in the
filtering row field for the column. If the column is being filtered by multiple values or by a text
filter (see below), ‘Custom’ is displayed.
To edit an Excel style filter, access the Excel style window filter again and change the filter
criteria as required. To clear the filter, click Clear Filter. See also Remove Filtering.
Text Filters
More advanced filters can be applied by clicking Text Filters. A list of text filtering criteria is
then display, plus ‘Custom Filter’.
Click on the required criterion. The advanced filtering window is then displayed with the
selected criterion selected in the Criteria field and the current column selected in the Field
field.
If the ‘Custom Filter’ option is selected, the advanced filtering window is displayed without
the Criteria field being completed.
See Apply Advanced Grid Filters for details of advanced filtering.
Note: Some filter criteria such as 'Begins With' use a wild card match to filter values. Do not
supply any wild card characters such as '*' or '%' as AVEVA Instrumentation handles
this for the user.
Exact Match Field = Value 1234 Shows all records where Field = 1234
Begins With - Field like XX* XX Shows all records where Field begins
Partial Match with two characters XX
Ends With - Field like *XX XX Shows all records where Field ends with
Partial Match two characters XX
Greater Than Field ≥ Value 1234 Shows all records where Field ≥ 1234
Or Equal To
Less Than Field < Value 1234 Shows all records where Field < 1234
Less Than Or Field ≤ Value 1234 Shows all records where Field ≤ 1234
Equal To
Greater Than Field > Value 1234 Shows all records where Field > 1234
Not Exact Not Field = 1234 Shows all records where Field does not
Match = 1234
Not Begins With Field like T T Shows all records not beginning with T
Partial_Match
Not Ends With Field like T T Shows all records not ending with T
Partial_Match
Not Empty Not Field = Shows all records where Field is not
(nothing) empty (no characters)
Not Null Not Field = Shows all records where Field is not Null
Null
Note: A database NULL means nothing has ever been entered in this field, whereas Empty
means that current value is empty (no characters).
Command Buttons
Apply Exits the Filter window and applies the filter to the current grid.
Cancel Exits the Filter window without changing any filters in the current grid.
Toolbar Commands
- Filter Removes the selected Filter row from the filter definition
Change Join Toggles the selected logical join between AND and OR
To remove all filtering from the current grid, in the Grid Actions section of the Home Tab
click Clear Filters.
To remove only column filtering from a grid, either click the clear filters button at the start of
the filtering row, or select the Clear Column Filters option from the Right-Click Context
Sensitive Menu.
To remove only advanced filtering from the grid, select the Clear Temporary Filters option
from the Right-Click Context Sensitive Menu.
Columns with a pale yellow coloured background cannot be edited directly in the grid (see
the Loop Service cells in the example above), and can only be edited, if they are editable at
all, using the appropriate Edit window for the type of record.
For further details of the facilities for editing grid data, refer to:
• Pick Lists and Buttons in Cells
• Copy, Cut and Paste Commands
• Undo and Redo Changes
Undo Undoes the last row edit. Any subsequent undo will undo each row's
edits on a row by row basis.
Redo Reverses the last undo (see above) made to data in the grid.
The last change made can be also be undone by selecting that cell it was made in and
pressing Ctrl+Z. Pressing Ctrl+Z again will redo the change.
Records Section:
Edit Displays a window used to edit an existing item selected from the grid.
Note: In most grids, the user can double-click on an item to open an editing window.
Refresh Updates the entire grid with the latest database information (useful in
multi-user project environments).
Note: These options are also available on the List Tools tabs.
Select All Rows Used to select every row in a grid. Refer to Row (Record)
Display Options.
Vertical View Displays selected rows in a vertical format (columns) for 'side
by side' editing. See below for an example.
Click on this option again to change the grid back to the default
display format.
Auto Size Columns Automatically sizes each column in the grid view to fit the
longest string of characters.
Filter Used to apply a filter to the data in a grid. Refer to Grid Filters.
Clear Filters Used to remove filtering from the data in a grid. Refer to Grid
Filters.
Quick Report Displays the grid in the Report Viewer window, a component
of the Report Manager. Refer to Report Manager for details of
this window and its facilities.
Commands common to most or all grids are described in this document. Grid-specific
commands are described in the appropriate module documentation.
Enter the string that is to be searched for in the Find What field. If the string has already
been searched for during this session, it can be selected from the drop down list accessible
from this field.
Click Options >> if a more refined search is required. Additional fields are then displayed in
the window:
From the Within drop down list, select which columns are to be searched. By default, all
columns are searched, but a single grid column can be selected if required.
From the Search drop down list, select the direction in which the search will take place: All
(i.e. up and down, the default setting), Up, or Down.
From the Match drop down list, select the matching criteria for the search: Partial Match -
Contains (default), Partial Match - Begins With, Partial Match - Ends With, or Complete
Match
Check Match Case if only text in the grid that matches the case of the text entered in the
Find What field is to be found. The checkbox is unchecked by default.
To proceed with the search, click Find Next.
The first row that contains a match is then highlighted and the cell that contains the match is
selected.
Click Find Next again to find the next match.
If no matches are found, a message is displayed to inform the user of this.
Click Close to exit the window.
data grids available in AVEVA Instrumentation modules. These sets of fields are called
'Views' and typically contain a subset of all available fields. These include the project-
specific properties that may be setup in the Engineer and Process Engineer modules.
Note: If the user is working in a project and the Security option has been activated in
Security Manager, the user may not have permissions to perform all grid
management tasks. Contact the System Administrator for further information.
The feature enables each user to restrict the grid to display only those fields that are
required for their current task. For example, in the Engineer Instrument List data grid the
user can select from any of the available database fields to define a customised set and
name that View. If the user was to select fields related to calibration data, they may select
fields TagNo, Service, P&ID, Range, CalibratedRange, Alarms etc and name this view
'Calibration'.
Users can easily change between Views by selecting from the list of Views created in the
project. New Views can be created by any user and can be set to Public, which allows any
other AVEVA Instrumentation user, to use the view, or set to Private, which restricts access
to only the user that created the View.
Note: All examples in this document refer to Engineer’s Instrument List. However, all
functionality described can be applied to Data Grids in general.
The name of the current View is displayed on the left-hand side of the bar at the bottom of
the AVEVA Instrumentation window.
Continue at:
• Change to another View
• Create a New Grid View
To change a view, click on View Name and then click Apply, or double-click on the View
Name.
Once selected, the data grid will refresh with the View fields, sort order, data filters, etc.
The Grid Name is the name of the current data grid and is non-editable (this View is based
on the Instrument List data grid).
Enter a View Name and optional Description.
Views can be marked Public, which allows any other users to use this View, or set to
Private, which restricts access to the user that created the View. If a view is to be Public,
tick the Public checkbox.
Field Definition
All views must contain at least one database field (column). To define the View fields, click
the Fields tab to display a list of fields available for the current data grid:
To select/de-select fields, click each fields checkbox in the Select column. The user can add
as many fields as required.
The user can rename the titles in the Caption column fields by clicking in the field and
changing the text. The new title will be used in the Grid View.
If required, select a pick-list from the PickList field. The associated list of values will then be
available from the field in question. Refer to Pick Lists for details of how pick-lists are
created and edited. If a field has “Not Applicable” in its PickList field then that field in a grid
is completed from a source other than a pick-list.
Note: If a locked pick-list is assigned to a field, only values from that list may be entered in
that field. This includes imported values. If an attempt is made to import a value into
such a field that is not in the assigned pick-list, the import of that value will fail.
Note: If a pick-list is assigned to a field, and that field is displayed in a window, the pick list
will not be available for that field in the window. However, if the pick-list is locked the
field will be read-only in the window.
When all the fields have been selected, click Save to save the fields for the new View.
Note: Edit any existing View by selecting the View in the Grid View window and clicking
Edit to open the List Manager for the selected view.
Note: Any View named 'AVEVADefault' cannot be edited. This is a system protected View.
However, the AVEVADefault View can be copied and modified.
Layout
All the fields selected in a View can be located in any order or sequence within the data grid
and have their default widths pre-set.
To define the Layout, click Layout to display the selected fields.
Note: The user must select fields prior to defining the Layout.
To change the order of the fields, click on the field Caption and drag the column to the
desired location.
Note: Two arrows are displayed to assist the user in positioning the field.
To change the default column width, click on the vertical dividing line and drag the dividing
line to the required width.
Note: Double-clicking on the dividing line will size the column to fit the largest string of text
within that column.
Sorting
Use the Sorting tab to define the fields by which the View will be sorted.
The View Fields list displays all fields for the View. Check the Show Used Only checkbox if
only those fields selected for the View (in the Fields tab) are to be displayed.
To select a field to sort the View by, double-click on it in the View Fields list. It is then moved
to the Sort By list. Repeat for as many fields as required.
The order of fields in the Sort By list will be the sort order of the View. In the example below,
data in the View will be sorted first by Area, and then by Tag Number.
To remove a field from the Sort By list, double-click on it. It is then returned to the View
Fields list.
Filtering
Use the Filtering tab to apply filtering to a View.
The Filtering tab is used in the same way as the Filter window. Refer to Apply Advanced
Grid Filters for details.
New Horizontal Tab To view more than one grid tab at a time, with the two tabs
displayed side-by-side, open the two grids and click this option.
Instead of the two grids being displayed as tabs, with one
“behind” the other, the grid view is then split vertically, with each
grid being displayed in one half of the grid view. The grid
currently selected is displayed in the right-hand half of the grid
view.
If three or more grids are open when the option is selected, these
additional grids are displayed as tabs in the left-hand side of the
grid view.
If an additional grid is opened once the option has been selected,
this grid is displayed as a tab in the same half of the grid view as
the currently selected grid.
New Vertical Tab This option works in the same way as the New Horizontal Tab
option except that grids are displayed one on top of the other, i.e.
the grid view is split horizontally.
Tabbed View This option will arrange all currently open document windows
such as loops and datasheets into a single tabbed window. The
user can click on a tab to display the content of that window.
If grids are to be displayed in tabs, check this checkbox (this is
the default setting).
If each grid is to be displayed in a separate window, uncheck this
checkbox.
Move to Previous If the grid view has been split into two parts using either the New
Tab Horizontal Tab or New Vertical Tab option, use this option to
move the current grid from the left-hand or top grid half to the
right-hand or bottom grid half.
If all grids are moved from a grid view half, the grid view half is
closed and the grid view reverts to the default tabbed view.
Move to Next Tab If the grid view has been split into two parts using either the New
Horizontal Tab or New Vertical Tab option, use this option to
move the current grid from the right-hand or bottom grid half to
the left-hand or top grid view half.
Note: Grids can also be moved from one grid view half to another by clicking on the grid
title and dragging and dropping it into the other grid view half.
The window displays a preview of the grid. Click the Print toolbar button to print it, or select
the Print option from the File menu. The File menu also includes a Page Setup option,
which accesses the standard Windows Page Setup window.
Thumbnail images of each page are displayed in the left-hand pane of the window. The
section of the page currently being viewed in the main viewing pane is blanked out in the
thumbnail (see the example above).
To close and open the thumbnail pane, select the Thumbnails option from the View menu.
Hand Tool Used to drag the page view in any direction. Click on the page
with this tool activated, drag the page until the required view is
visible, then release the mouse button.
Also available on the Tools menu.
Dynamic Zoom When this tool is active, the page will be zoomed into when the
Tool cursor is dragged up the page or the mouse wheel rolled up, and
zoomed out when it the cursor is dragged down or the mouse
wheel rolled down.
Also available on the Tools menu.
Zoom In Tool When this tool is active, left-clicking the mouse on a page will
zoom into that page to the next standard zoom level.
Also available on the Tools menu.
Zoom Out Tool When this tool is active, left-clicking the mouse on a page will
zoom out from that page to the next standard zoom level.
Also available on the Tools menu.
Page Width Sets the view to same width as the current page.
Also available on the View menu.
Margin Width Sets the view to the width of the margins of the grid image on the
current page.
Also available on the View menu.
Whole Page Sets the view to display the entire current page.
Also available on the View menu.
Zoom In Zooms into the page to the next standard zoom level.
Also available on the View menu.
Zoom Used to change the zoom level the value selected from the list
accessed from this field, or typed into this field.
Also available on the View menu.
Zoom Out Zooms out from the page to the next standard zoom level.
Also available on the View menu.
Continuous Removes the gaps between the different pages of the preview in
the main view. Click this button again to replace the gaps.
Page Layout Opens a drop-down list from where various page layout options
can be selected.
5 Areas
All Engineering items in AVEVA Instrumentation must be assigned to a Plant Area. The first
task once the project is setup (refer to the Installation User Guide for further information on
project setup), is to add areas to the project database.
Note: Access control restrictions to Plant Areas may be setup in the Security Manager
module, which may restrict the access of users to certain Plant Areas. Refer to Area-
Based Access Control for further details.
Select Setup > Add/Edit Plant Areas from the Project Tab to display the Areas window. If
Areas already exist in the project, these will be displayed in the Areas window grid view.
To add a new Plant Area, click New to display the Area Information window.
Note: The short description can be used in AVEVA Instrumentation documents such as
datasheets and loop lists if the full Area description is too long to be used in those
documents.
Click Save to create the new Area and return to the Areas window. The new Area will be
displayed in the Areas window grid view.
Click Cancel to return to the Areas window without creating a new Area.
To delete an Area, select it from the grid list and click Delete. A message will be displayed
asking the user to confirm the deletion.
Click Yes to confirm the deletion and return to the Areas window. The deleted Area will be
deleted and removed from the grid view.
Click No to cancel the deletion and return to the Areas window.
Clicking Close on the Areas window closes the window and returns the user back to their
original view.
In a grid view, the available Plant Areas can be viewed by clicking on any cell in the Area (or
AreaNo) column, and clicking the button that is displayed to the right of the column. A drop-
down list of the Plant Areas is displayed.
To add or edit an Area Type, select Setup > Add/Edit Plant Area Types from the Project
Tab to display the Area Types window.
The Area Types window displays a grid list all the currently available Area Types and the
criteria associated with each Area Type.
To add an Area Type, select New to display the Area Type window.
The Area Type window can also be displayed by clicking the arrow to the right of the Area
Type field on the Area Information window. Refer to Areas for more information.
The user must add a Name to the Area Type and select which criteria to associate to the
Area Type by checking one or more of the four checkboxes.
Note: If the checkbox Must be Root is selected, the checkbox Can be Root is
automatically checked by the system and becomes inactive.
Can be Root Allows the Area to be a Root (top level) Area or a Sub-Area
of another Area. If the Area is allocated a Parent Area it
cannot be selected as a Parent Area and vice versa.
Must be Root Specifies that the area must be a Root (top level) area and
cannot be a Sub Area.
The user can make the required changes and click Save.
Click OK to return to the Area Types window. The edited Area Type will be displayed in the
Area Types window.
Clicking Cancel on the Area Type window returns the user back to Area Types window
without editing the Area Type.
To delete an Area Type, select from the grid list and click Delete. A message will be
displayed asking the user to confirm the deletion.
Click Yes to confirm the deletion and return to the Area Types window. The Area Type will
be deleted and removed from the grid view.
Click No to cancel the deletion and return to the Area Types window.
Clicking Close on the Area Types window closes the window.
Full Access allows a user to add, edit and delete data in the area
Read-Only (Allow allows a user to view object data, create reports and
Connections) make connections to objects in the area (e.g. users may
assign a supply in the area to a load in a full access
area)
6 Pick Lists
Many grid cells, datasheet cells and window fields can be, or must be, completed by
selecting from lists of values.
For example:
These “Pick Lists” can be edited by the user if required. Users can define new pick lists, add,
edit and delete values in existing pick lists, and delete pick lists.
Select Setup > Edit Pick Lists from the Project tab to display the Pick List window.
The Pick List (All) window initially displays the name of every pick lists in the PickList
Name column. The data type of each pick lists is displayed in the Data Type column. Pick
lists are listed in alphabetical order.
Enter a unique name for the new pick list in the PickList Name field.
From the DataType list, select the data type for the new pick list:
The default type is “Text”. All values added to the pick list must be of the selected data type.
If a grid cell etc. with which the list is allocated to must be completed using one of the pick
list values, check the Locked checkbox. Otherwise leave it unchecked, meaning that other
values may be entered in addition to those in the list of values.
Note: If a pick list is assigned to a field in the Grid Manager (see Grid Manager), and that
field is displayed in a window, the pick list will not be available for that field in the
window. If the pick list is locked it will be a read-only field in the window, if it is not
locked, it will not be read-only.
Click Save to exit the window and save the new pick list.
Click Cancel to exit the window without saving the new pick list.
Note: The data type cannot be changed if the pick list has any values assigned to it. These
values must be deleted first.
Enter the name of the new pick list in the Merged Picklist Name field. The name must be
not have been used for any other pick list.
Enter a caption for the new pick list in the Merged Picklist Caption field.
The pick lists that form the new, merged pick lists may optionally, if user-created, be deleted
as part of the process. If this is required, check the Delete existing Picklists checkbox.
Pick lists supplied with the product cannot be deleted. If a supplied pick list has been
selected for merging, if the checkbox is checked a message will be displayed informing the
user of this and the checkbox will revert to being unchecked.
The pick lists selected for merging are listed in the lower part of the window. Select which of
the selected lists are to be merged into the new list by clicking on them, or click the All
option if all selected pick lists are to be merged.
Click Save to exit the window and save the new merged pick list, which is then added to the
list of pick lists and populated with the values from the selected lists.
Click Cancel to exit the window without saving the pick list.
The values in the list are then displayed. The name of the selected pick list is displayed in
the window title bar.
Continue at:
• Edit Pick List Values
• Add Values to a Pick List
• Delete Pick List Values
• Save Changes to Pick List Values
Note: If a deleted value has already been assigned to a grid cell, datasheet cell or window
field it will not be deleted from that cell or field. In the case of grid cells and window
fields, the deleted value will continue to be available for selection for items of that
type (for example, an instrument or a drawing) while any item of that type still has the
deleted value assigned to it.
A number of import and export facilities are common to the AVEVA Instrumentation
engineering modules. See:
• Import from Excel
• Export to Excel
• Export to XPS and PDF Files
mapping using this identity column, the identity column is ignored and records in the
database are searched and updated based on the foreign key field.
Once an Excel spreadsheet is selected for import, users must 'map' each Excel column
name (heading) to an AVEVA Instrumentation database field using the AVEVA
Instrumentation import utility. Data can then be imported into AVEVA Instrumentation. The
import utility will check if the identity column field exists in mappings.
While processing records to be imported, if a record already exists in the database AVEVA
Instrumentation will show the differences between the imported data and the AVEVA
Instrumentation data, allowing the user to accept/reject the proposed changes on a record
by record (and field by field) basis. If the record does not exist in AVEVA Instrumentation
and the user accepts the importation of the record, AVEVA Instrumentation will create a new
record for that drawing or catalogue item.
Browse for the spreadsheet that data is to be imported from and click Open. The Import
Fields window is then displayed:
The window shows all the columns in the Excel spreadsheet to be imported. Select an
existing Field Mapping (if one for this Import type exists) from saved mappings drop down
or use the automatic mappings created by AVEVA Instrumentation and make changes to
these mappings as required.
Excel Column Name fields display the names of the columns in the spreadsheet. The
AVEVA Instrumentation Field fields displays the Instrumentation fields they are mapped
to.
To map an Excel Column to an AVEVA Instrumentation database field click in the AVEVA
Instrumentation Field field adjacent to the relevant Excel Column Name field, and select
the required AVEVA Instrumentation field from a drop-down list. To exclude a field from the
import, click Clear button in the grid against the field that needs to be excluded or select the
blank entry from the mapping drop-down list.
Note: AVEVA Instrumentation automatically checks each Excel Column Name from the first
row in the Excel worksheet against fields names in AVEVA Instrumentation Database
(if not found then field Captions - as set in the Grid Manager). If a match is found
then AVEVA Instrumentation automatically adds the Field Name to the mapping list.
The user can select a different field from the mapping list if required.
Once the details for the mapping have been entered, click Save. The mappings will be
saved and Saved Mappings drop down will have the newly added mapping name
appended to it.
Note: It is not compulsory to save the mappings to import data, data can also be imported
by just clicking on the Import button at any time. However it is useful to save the
mappings if an import with those mappings is to be performed multiple times.
If import mapping are being tested, the Process each Tag and Show Differences one by
one option is recommended.
Once the required option has been selected, AVEVA Instrumentation will go ahead and
process the data. The Import Differences window is displayed either once for all
differences or multiple times for each record, as explained above.
The Import Differences window shows the differences between AVEVA Instrumentation
data and proposed (imported Excel) data.
To accept the changes either, select individual field data by clicking Accept checkbox for
each.
Alternatively, select the Accept All checkbox at the top of this window. All Accept
checkboxes will then be checked (individual records may then be unchecked if required).
To save the checked (accepted) data, click Save.
If the Batch Process all Tags and Show Differences at end option was selected, the
process is then complete.
If the Process each Tag and Show Differences one by one option was selected, AVEVA
Instrumentation will then proceed to the next tag record to be imported and display the
differences in the Import Differences window.
To cancel any import for the current tag record, click Close. AVEVA Instrumentation will then
proceed to the next record to be Imported.
Once the import procedure is complete, an Import Log window will be displayed, in which
details of the import are displayed (records successfully imported, errors, warning etc).
Select the location to which the Excel file is to be saved, enter the file name, and click Save.
The export then takes place.
The contents of a grid (except the Seed List in Designer) may be exported to a spreadsheet
with an extra column which is automatically populated with a unique identifying number for
each row of data.
To produce a spreadsheet in this format, proceed as described above, but select the Export
to Excel (With Id) option, accessible by clicking the arrow next to the Export to Excel
option.
To export to a spreadsheet from a grid in a window, click the Export to Excel button and
specify the file name and location as described above.
To export the contents of a grid to an Excel spreadsheet, open the appropriate grid. On the
Manage Tab, click Export to XPS or Export to PDF as appropriate in the Export section.
A Save file as window is then displayed. Select the location to which the file is to be saved,
enter the file name, and click Save. The export then takes place.
8 Work Packs
Work packs can be created which consist of collections of items with shared project
management requirements or properties. For example, all the items an individual user or
group of users is concerned with may be assigned to a single work pack. Time constraints
may be assigned to work packs, for example the required start and completion dates of
items in a work pack, so that work can be more easily prioritised.
When the user starts the application, if work packs have been created, the Select a
WorkPack window is displayed from which the user can select a work pack. The user can
choose not to select a work pack by clicking Operate without WorkPack.
The Select a WorkPack window can also be accessed by selecting Work Packs > Open
from the Project Tab.
To create a work pack, click New to display the Work Pack window.
To edit an existing work pack, select it from the list and click Edit to display the Work Pack
window with the current work pack properties displayed.
The user must give the work pack a WorkPack No but the description and four user fields
can be left blank.
Note: It is advisable to enter information in some of the fields for later reference.
The user can then assign a start and end date for the work pack by selecting dates in the
Date Started and Date Required fields.
Click Save to create the work pack or save changes and return to the Select a WorkPack
window where the new work pack will be displayed.
Click Cancel to exit the WorkPack window and return to the Select a WorkPack window.
Once a work pack has been created, items, for example drawings or instruments, can be
assigned to it. To assign items to a work pack, select the required items in the appropriate
grid view and select Work Packs > Assign to Work Pack from the Project Tab to display
the Select a WorkPack window. Select the required work pack from the list and click
Select. The WorkPack number selected will be displayed against the items in the
WorkPackNumber field in the grid view.
Note: When working in a work pack, any newly created objects will automatically be
assigned to the current work pack.
Note: The WorkPackNumber column is not selected for display in the AVEVADefault Grid
View. If it is required to be displayed, a new grid layout must be created with the field
visible.
To un-assign an item from a work pack, select the item in the grid view and select Work
Packs > Un-Assign from Work Pack from the Project Tab. The grid view is refreshed and
the selected item is removed from the work pack.
The user can view the items assigned to a work pack by selecting Work Packs > Open
from the Project Tab and selecting the work pack from the list displayed on the Select a
WorkPack window. The grid view will be refreshed to display only the items in the selected
work pack.
Work packs can be deleted by selecting Work Packs > Open from the Project Tab to
display the Select a WorkPack window. Select the work pack to be deleted from the list and
click Delete. If items have been assigned to the work pack, a Delete confirmation window
will be displayed informing the user that items are assigned to the Work Pack and asking if
the user wants to delete the work pack. The user can select Yes to delete the work pack or
No to cancel the deletion and return to the Select a WorkPack window. If Yes is selected all
items assigned to the work pack will be un-assigned.
Clicking Yes will assign all the imported records to the work pack. Clicking No will import all
the records without assigning them to the work pack.
9 Change Reports
By default the Audit Manager displays all database changes for the current AVEVA
Instrumentation module and grid. The grid shows the most recent change at the top.
The Audit log includes the user name and date/time of the change. The user name is the
Windows login name of the user that changed the data in AVEVA Instrumentation.
Data from other AVEVA Instrumentation objects can be selected from AVEVA
Instrumentation Object Type list (more than one can be selected).
The Apply Date/Time filter enables the list to be filtered between user defined dates/times.
The Apply Limit enables the list to be limited to a user defined maximum. The most current
changes are always included, effectively removing the early project changes from the list.
The Tools menu includes an Export to Excel command, used to export the data to Excel.
This window shows all previously saved Database Revisions (if any have been saved).
Toolbar Menus
Command Description
New Saves the state of the current project database as a revision for
change reporting in the future with the Save Database Revisions
window.
Refresh Refreshes (re-loads) the grid with data from the database.
Continue at:
• Save Database Revisions
• Compare Changes between Database Revisions
To save the current database state as a Database Revision, enter a unique Revision
Number and (optionally) descriptions and a user name, click Save to save the revision.
Note: If the current database is large (i.e. there are many entries) this action may take a
few minutes to complete.
Note: It is recommended that Database Revisions are saved only when all other engineers
and designers have exited AVEVA Instrumentation applications.
To compare the current database state to the Database Revision selected in the previous
Database Revision list, select the Change Report type from the list on the right-hand side of
the Compare Database Revisions window.
Note: Multiple Change Reports may be selected by clicking on any number of types in the
list.
Note: If the current database is large (i.e. there are many entries) this action may take a
few minutes to complete particularly if multiple detail reports are run.
When the comparison reports are completed, AVEVA Instrumentation will display any
differences in a grid. For example:
This grid shows all changes for the selected Change Report (in this example 'Instrument
Details’).
The changes can be printed or exported to Excel by using the appropriate toolbar
commands.
10 Report Manager
AVEVA Instrumentation has an in-built Report Manager that enables users to create and
modify reports.
The Report Manager is available from most Grid Views within each AVEVA Instrumentation
module by selecting Report Manager from the Reports section of the Home Tab.
The AVEVA Instrumentation Report Manager window is then displayed:
The Report Manager shows a list of all previously defined reports for the current AVEVA
Instrumentation Grid in the list on the left hand side. If there are multiple reports already
created, the user can run those reports by clicking on the report name.
The Report Manager supports printing to a printer and to PDF file format as well as to Excel
and other formats. Report data is formatted as defined by the applied report design, which
are created and modified by users using the Report Designer.
New Used to create new reports. Refer to Create a New Report (for
the current Grid).
Delete Used to delete the report selected in the left hand pane. A
message is displayed requesting that the deletion be
confirmed. Click Yes to proceed.
Open Issues Displays the Issues window listing all the current issues for the
For Selected selected report.
Highlight Issue Highlights the differences between the current report and a
Changes for report issue selected from a further sub-menu.
Revision Displays a list of all reports with revisions (and their revisions).
Sub-menu options are:
Publish to AVEVA Used to export reports and associated data to AVEVA NET.
NET Refer to Export to AVEVA NET.
Search Opens a Find window with standard facilities, used to search for
text within a report.
Quick Print Used to print the report using the default printer settings.
Page Setup Used to configure the report page. Opens a standard Windows
Page Setup window.
Hand Tool Changes the cursor to the hand tool, which can be used to pan
around the report.
Magnifier Changes the cursor to the magnifier tool, used to change the
report view by zooming in and out.
Zoom % Used to adjust the report view by the zoom percent value.
Multiple Pages Used to change the report view to display multiple pages.
Opens the following drop-down:
Watermark Used to add a text or picture watermark to the report. Opens the
Watermark window:
Export Document Used to export the report as a file. Displays the following menu,
from which the file format is selected:
Click OK.
Send via E-mail Used to save the report as a file and send the file via e-mail.
Displays the following menu, from which the file format is
selected:
Click OK.
A standard Save As window is then displayed which is used to
specify the location that the file is to be saved to. Click Save to
complete the save.
Edit Layout Opens the Report Designer, used to edit the layout of the report.
Refer to Edit Report Layouts
Continue:
• Create a New Report (for the current Grid)
• Report Preferences
• Report Revisions
• Report Issues
• Import Reports
• Edit Report Layouts
• View, Edit and Create Custom Reports
• Export to AVEVA NET
Note: New reports can also be created by copying an existing report. Select the report to
be copied, then click the down-arrow button next to New. From the menu that is then
displayed, select Copy Selected. The AVEVA Electrical Report window is then
displayed, populated with details of the copied report.
Create a unique name for the report by entering a name for the report in the Document No
field. Enter a description in the Description field.
Set the report to be “public” for the project by checking the Public checkbox. Access to the
report is restricted to the current user if the checkbox is left unchecked.
If required, enter a full title for the report in the Title 1 and Title 2 fields.
Click the Fields tab to show a list of fields available for use in the report.
To select/de-select fields, click each fields checkbox in the Select column. The user can add
as many fields as required.
Define a sort order by clicking Sorting to select the field(s) to sort by in the new report.
The View Fields list displays all fields for the report. Check the Show Used Only checkbox
if only those fields selected for the report (in the Fields tab) are to be displayed.
To select a field, double-click it in the View Fields list to move it to the Sort By list.
The order of fields in the Sort By list will be the sort order of the report. In the example
above, data in the report will be sorted first by Area, and then by Tag Number.
To remove a field from the Sort By list, double-click on it. It is then returned to the View
Fields list.
The Filtering tab is used in the same way as the Filter window. Refer to Apply Advanced
Grid Filters for details.
To add a revision to the report, click Revision to display the revision fields.
Note: Revisions can also be added, edited, deleted and viewed using facilities directly
accessible from the Report Manager window. Refer to Report Revisions.
Complete the fields with the required revision data (entry of a revision number is
mandatory).
Note: When creating a new revision, leaving the Revision No field blank will cause
Instrumentation to use the next revision number. e.g. if the current revision is "A",
then the next is "B" or if current revision is "2", then the next is "3" etc.
Note: The Description field contains a list of all previously created revision descriptions.
Add a new description by entering any required description. Any new descriptions
will be available for future revisions.
Click Save. The Revisions window is then displayed again with the new revision added to
the list of revision.
To edit a revision, select the revision from the list and click Edit to display the Revision
Entry window. Change the values as required and click Save. The amended values will be
displayed in the list.
To delete a revision, select the revision from the list and click Delete. A message is
displayed requesting the user to confirm the deletion.
Click Yes to confirm the deletion and return to the Revisions window. The selected revision
is then removed from the list. Click No to cancel the deletion.
The user can view the revision in a sub-report by clicking View Revisions Subreport to
display the Custom Report window.
Note: The report can also be viewed by selecting Custom Reports on the Reports section
of the Home Tab.
If the user has added revisions and wants to view them, these must be saved before clicking
View Revisions Subreport.
A message will be displayed requesting the user saves the changes. Click Yes to save the
changes to report view and proceed to view the report with all the changes displayed, or
click No to view the report without the changes.
Once the user has defined all the fields, sort order and any filters, click Save.
AVEVA Instrumentation will then build the report and display it in the Report Manger window.
Select the font, font size, boldness, background colour and row height for each report
section.
Select the colour in which changes between a selected issue and the current data in a
report are to be highlighted in the Issue Changes section.
Click Save to save changes to the preferences and exit the window.
Click Cancel to exit the window without saving.
Complete the fields with the required revision data (entry of a revision number is
mandatory).
Note: The Description field contains a list of all previously created revision descriptions.
Add a new description by entering any required description. Any new descriptions
will be available for future revisions.
Note: When creating a new revision, leaving the Revision No field blank will cause
Instrumentation to use the next revision number. e.g. if the current revision is "A",
then the next is "B" or if current revision is "2", then the next is "3" etc.
To view the revisions for a single report, click on the + icon next to its listing.
To view revisions for all reports, click Show All Revs.
To edit an existing revision click Edit. The Multi-Field Edit (Bulk Edit) window is displayed.
• To edit a revision field, check the appropriate checkbox and enter the new value.
• Click Select all to select all fields for editing.
• Click Copy first record's data to copy the values for the revision first selected in the
Revision window into the fields.
• Once the required changes have been made, click Save.
To add a new revision, click New. The Revision Entry window (see Create a Revision) is
then displayed. Enter the required details and click Save.
To delete a revision, select the revision and click Delete. A message will then be displayed
requesting that the deletion be confirmed. Click Yes to confirm the deletion or No to cancel.
If the report has already been issued at the current revision, or has had no revisions created
for it, a message window is displayed to inform that the user that a new revision must be
created before issuing.
Click Cancel to cancel the issue or OK to create a new revision. Refer to Report Revisions
for further information on creating a new revision. Once the revision has been created, the
issue procedure automatically resumes.
See also:
• View Previous Issues
• Highlight Changes Since a Selected Issue
If Open Issues For Selected was clicked, the window lists all the issues for the report
currently selected in the grid. If Open Issues For All was clicked, the window lists all the
issues for all the reports in the grid.
Note: If the revision associated with an issue has been deleted, the Cancelled checkbox
for the issue will be checked. The issue itself however will not be deleted, and the
issued report may still be opened and viewed.
Command Buttons:
Open Open the selected issues in the Preview window (see below).
Note: Before an issue of a report can be deleted, all later issues of that report must first
be deleted. A message is displayed if a user attempts to delete an issue of a
report for which later issues exist. For example:
Find Displays the Find window, used to search by any text string located
anywhere within the grid.
Filter Opens the Grid Manager window, used to define the current grid view
filter criteria.
Refresh Updates entire grid with latest database information (useful in multi-user
project environments).
Preview Window
The Preview window is opened by selecting an issue and clicking Open, as described
above. It is used to view, save, print, e-mail and export report issues.
The toolbar buttons are identical to those of the main Report Manager window, with the
addition of buttons for opening and saving reports, and with the exception of the Edit
Layout button. Many of the facilities accessible from the toolbar are also accessible from
the File, View and Background menus.
Changes are then highlighted in the colour selected in the Report Preferences window
(refer to Report Preferences).
The Report Import window is then displayed. This lists all the reports definitions in the
selected project for the current grid, e.g. the Instrument List.
To select a report definition for importing, check its Select checkbox. Check the Select all
checkbox to check all Select checkboxes.
When the required report definitions have been selected, click Import.
A progress window displays the progress of the import. The selected report definitions are
then added to the project and are listed in the left hand pane of the Report Manager.
If an imported report has the same name as a report in the current project, it's name will be
suffixed with "Copy of…".
Note: It is the report definitions that are imported, not the reports themselves. Imported
reports will therefore display data for the current project, as specified by the report
definition, not data from the project they were imported from.
The Report Import window is then displayed. This lists all the reports definitions in the
project for the current grid.
Select and import the required reports as described above.
For more information about editing report layouts please refer to the Report Designer User
Guide.
The Report Manager for custom reports provides the same facilities as that for non-custom
reports, as described previously, except that the Preferences, Issue and Revisions
buttons are not available.
Also, the New and Edit buttons display a window that is used to create and edit the SQL
queries that define custom reports:
When creating a new custom report, enter the name of the report in the Report Name field.
To add an SQL query, click Add Query. The SQL Query Maker is then displayed, in which
the query can be defined.
To edit an existing query, select it from the list beneath the button and click Edit Query. The
SQL Query maker is then displayed with definition of the selected query displayed for
editing.
For information on how to use the SQL Query maker, refer to the Active Query Builder User
Guide or visit www.activequerybuilder.com.
To delete a query, select it from the list beneath the button and click Delete Query. A
message is displayed requesting that the deletion be confirmed. Click Yes to proceed.
Click Save to save changes to the report definition and exit the window.
Click Cancel to exit the window without saving.
Once the export is completed, the Export Report window is displayed, listing the report for
which the data export was requested and whether or not that export was successful or not:
11 Claims
If a user attempts to edit an item which is currently being edited by another item, a message
is displayed to inform the user that the item is locked. For example:
To unlock an item click Claims in the Multi User section of the Manage Tab. The Claims
window is then displayed:
A.1.1 Units
ISA S75.01 has several standard conversion factors for unit conversion. The program
enforces two conventions:
1. The flow units are mass flows.
flow: kg/h
pressure: kPa
density: kg/m3
Valve/Pipe diameter: mm
Valve size: Cv factors
Viscosity: mPa.s (same as centipoise)
For this purpose ISA 75.01 has provided N factors in tables 1 and 2.
In the program we define the same factors with the same name except in lower case as
global variables, namely:
n2 = 0.00214
n4 = 76000
n5 = 0.00241
n6 = 2.73
Should it be desired to change the units to say, imperial units, then using the factors in
tables 1 and 2 of ISA 75.01 would be a convenient way to do it.
It is strongly recommend that units of flow remain in mass units rather than volumetric units.
Volumetric units, especially when gases are involved, lead to great confusion at times.
Basics
w
Cv =
N 6 FP ρ(P1 − P2 )
Where w is the mass flow rate, r is the density, P1 and P2 are the pressures respectively
upstream and downstream. N6 is a unit correction factor and FP is the piping factor (see
Effects of Fittings below).
1/ 4
N 4 Fd w ⎛ FL2 C 2V ⎞
RE = ⎜
1 / 2 1/ 2 ⎜ 4
+1⎟⎟
1000 μFL C V ⎝ N 2 d ⎠
Here we use w (kg/hr) instead of q (m3/hr) and the absolute viscosity, m, in mPa.s
(centipoise). The 1000 factor is the base density of water. N4 is the coefficient
corresponding to q in m3/hr i.e. N4 = 76000. Fd is a valve factor (for all practical purposes if
a valve internal has a single flow path, Fd = 1, if it has multiple flow paths, Fd = sqrt(n). In
general valves have either 1 or 2 paths and Fd is either 1 or 0.7).
Effects of Fittings
The effect of reducers and expanders before and after the valve is described in the standard
under section 4.3. The base piping factor FP is given by the following formula:
1
−
⎛ ΣKC ⎞ 2
2
FP = ⎜⎜ + 1⎟⎟V
4
⎝ N 2d ⎠ Eq. 3 Section 4.3
Choking
When P1 and P2 are defined, inside the valve there exists a section where the pressure is at
a minimum. This pressure is called PVC where VC stands for Vena Contracta.
The factor FL is obtained experimentally by the valve manufacturer. It is defined as:
P1 − P2
FL =
P1 − PVC
If the downstream pressure is lowered sufficiently, at a certain value the vena contracta
pressure reaches the vapour pressure of the liquid and the liquid starts to boil. At this stage
lowering the downstream pressure further does not produce an increase in flow rate, the
vena contracta pressure remaining at the boiling point of the liquid. The valve is said to be
choked.
There are 2 modes of choking depending on whether the downstream pressure is less or
greater than the vapour pressure. If the downstream pressure is less than the vapour
pressure, the flow remains two phase all the way to the valve exit, the valve is said to be
flashing. If the downstream pressure is greater than the vapour pressure of the liquid, the
valve is said to be cavitating. Both flashing and cavitation produce a lot of noise but of the
two, cavitation is far more severe as the vapour bubbles created at the vena contracta
implode nearer the exit and cause a lot of erosion on the metal parts. Valves left cavitating
can literally destroy themselves in minutes.
One thing to notice during choking is that the flow is solely determined by the pressure
difference between inlet and the vena contracta, and it follows that the outlet fittings no
longer have any significance on the flow rate.
The flow formula becomes:
w
Cv =
N 6 FLP ρ(P1 − FF PV )
1/ 2
⎛P ⎞
FF = 0.96 − 0.28⎜⎜ V ⎟⎟
Where ⎝ PC ⎠ Equation G1
and PV is the vapour pressure and PC is the critical pressure.
FLP is a factor which combines the recovery factor and the piping geometry and we use
Equation 16 to calculate it:
( −1 / 2 )
⎛ (K 1 + K B1 )FL2 C 2V ⎞
FLP = FL ⎜⎜ 4
+1⎟⎟
⎝ N 2d ⎠ Eq 16 section 5.3
The fittings() function returns the following values:
w = N 6 FP C V Y xP1ρ1
Where Y is a factor for the expansion of the gas and x is defined as:
x=
(P1 − P2 )
P1
Where FL was a valve characteristic determined by the manufacturer to characterise the
pressure recovery in the valve in liquid flow, the factor XT is used for gases in a similar
fashion. Again this factor is measured by the manufacturer.
CP / Cv
FK =
FK is defined as 1.4 where Cp/Cv is the isentropic exponent of the gas.
The expansion factor Y is given by equation
x
Y =1−
3FK X T but cannot be less than 2/3.
When fittings are used, XT should be replaced by XTP which is defined as:
−1
X ⎛ X T (K 1 + K B1 )C 2V ⎞
X TP = 2T ⎜ + 1⎟⎟
FP ⎜ N 5d 4
⎝ ⎠
Choked Flow
Similarly to liquids, gases flow can also choke. Simply speaking, given an upstream
pressure and a valve size, as the pressure downstream is lowered the flow increases. This
continues until the downstream pressure is such that the speed of the gas at the throat of
the valve (vena contracta) reaches the speed of sound. Lowering the downstream pressure
even more is of no avail as information about what is happening downstream cannot
propagate past the sound barrier. The flow is therefore choked.
The pressure at which choking occurs (for a given upstream pressure) is called the critical
pressure, P2CRIT.
P2CRIT = P1 (1 − FK X TP )
If P2 is less than P2CRIT, then simply use P2CRIT instead of P2 in the formulas.
Valve FL XT Fd
Type Trim Flow
Direction
P1M W
ρ1 =
Z R T1
With the density in kg/m3, the pressure in kPa (absolute) and the temperature in K.
The molecular weight is in kg/kmole.
R is the universal gas constant R = 8.314 kJ/kmole K.
Z can be estimated using the Redlich-Kwong Equation of state (only Pressure, Temperature
and the critical Pressure and critical temperature of the gas are required for estimating Z). If
unknown, assume Z = 1.0.
Another program, zrk, performs the calculation of Z and the conversion of pressure and
temperature to density for any gas when the gas critical properties are known.
Gas Law
The relation between pressure, temperature, density and molecular weight is expressed as
follows:
P MW
ρ=
Z R T Eq. 2.1.1
Here the variables are:
Z is a compressibility factor to correct for deviation from the ideal gas law.
⎡ ∂P ⎤
a= ⎢ ⎥
⎣ ∂ρ ⎦ S Eq. 2.2.1
P
k
= constant
If we assume that ρ then the formula becomes:
P
a= k
ρ Eq. 2.2.2
This is the formula which is often quoted but one needs to remember that it is only true if the
P
k
= constant
gas follows the ρ law. Also the isentropic exponent is often called the ratio of
CP
k=
specific heats because for most gases at low pressures
C V . This law is not always
true when the pressures get higher, and simply using the ratio of specific heat and applying
it as the isentropic exponent can lead to errors. The k which is required is that which
expresses the gas isentropic compression best.
g (Z 2 – Z1 ) +
(v 2
2 )
– v12 ⎛P P ⎞
+ (U 2 – U 1 ) + ⎜⎜ 2 – 1 ⎟⎟ = W + Q
2 ⎝ ρ 2 ρ1 ⎠ Eq. 2.3.1
V22 P V2 P
+ U 2 + 2 = 1 + U1 + 1
2 ρ2 2 ρ1 Eq. 2.4.1
U= CV T
The internal energy for an ideal gas is
P
H = U+
And the thermodynamic definition of Enthalpy is ρ
So equation 2.4.1 can also be written in term of Enthalpy:
V22 V2
+ H 2 = 1 + H1
2 2 Eq. 2.4.2
This equation is currently not used much for sizing relief valves but the improvement arising
from the various thermodynamic models show that in the future this equation will be able to
be used directly for solving relief valve sizing problems. This is especially true when the
problem is far away from conventional problems, for instance for compressible fluids close
to critical conditions or when two phase flow is involved, where current international
standards fall far short of offering sensible solutions.
Assumptions
P R
= T
The gas Equation of State is
ρ M W Eq. 3.1.1
V1 = 0
The state 1 conditions are those in the pressure vessel; in particular this implies as
the vessel is much larger than the nozzle of a relief valve.
The flow from the vessel to the throat of the relief valve is isentropic (i.e. no friction and no
heat exchange).
P
k
= constant
The law ρ applies to the gas to characterise the isentropic expansion.
Eq. 3.1.2
CP
k=
C V Eq. 3.1.3
R = M W (C P – C V ) Eq. 3.1.4
U = CV T
Eq. 3.1.5
These are the assumptions made by all relief valve sizing standards.
Combining Eq. 3.1.3, 3.1.4 and 3.1.5 we get:
1 R
U= T
(k – 1) M W Eq. 3.1.6
Subsonic Flow Equations
Since V1 = 0, we can express equation 2.4.1 as follows:
V22 ⎛P P ⎞
= (U1 – U 2 ) + ⎜⎜ 1 – 2 ⎟⎟
2 ⎝ ρ1 ρ2 ⎠ Eq. 3.2.1
From equation 3.1.6 we have:
1 R
U1 – U 2 = (T – T )
(k − 1) M W 1 2 Eq. 3.2.2
From equation 3.1.1 and equation 3.1.2 we derive:
k –1
T2 P2 ρ1 ⎛ P2 ⎞ k
= =⎜ ⎟⎟
T1 P1 ρ 2 ⎜⎝ P1 ⎠ Eq. 3.2.3
And replacing in equation 3.2.2 we finally derive the change in internal energy of the gas
during the isentropic expansion is:
⎛ k −1 ⎞
⎜ ⎞ k ⎟⎟
1 R T1 ⎜ ⎛ P2
U1 – U 2 = 1– ⎜ ⎟⎟
k – 1 M W ⎜ ⎜⎝ P1 ⎠ ⎟
⎜ ⎟
⎝ ⎠ Eq. 3.2.4
Similarly we have:
⎛ k –1 ⎞
⎛ ⎞ ⎜ ⎞ k ⎟⎟
P1 P2 P1 P2 ρ1 R T1 ⎜ ⎛ P2
– = ⎜ 1– . ⎟ ⎟ = 1– ⎜ ⎟⎟
ρ1 ρ 2 ρ1 ⎜⎝ P1 ρ2 ⎠ M W ⎜ ⎜⎝ P1 ⎠ ⎟
⎜ ⎟
⎝ ⎠ Eq. 3.2.5
Hence for the speed at the throat of the nozzle we get:
⎡ k −1⎤
2k R T1 ⎢ ⎛ P2 ⎞ k ⎥
V2 = . ⎢1 – ⎜⎜ ⎟⎟ ⎥
k − 1 M W ⎢ ⎝ P1 ⎠ ⎥
⎣⎢ ⎦⎥ Eq. 3.2.6
The theoretical mass flow rate through the nozzle is:
1
PM ⎛ P2 ⎞k
ρ2 = 1 W ⎜⎜ ⎟⎟
m = A ρ2 V2 and RT1 ⎝ P1 ⎠
So:
⎡ 2 k +1 ⎤
2k M W ⎢⎛ P2 ⎞ k ⎛ P2 ⎞ k ⎥
m = AP1 ⎢⎜ ⎟⎟ – ⎜⎜ ⎟⎟ ⎥
k − 1 R T1 ⎢⎜⎝ P1 ⎠ ⎝ P1 ⎠ ⎥
⎢⎣ ⎥⎦
Eq. 3.2.7
Where A is the area of the nozzle and m is the mass flow rate.
In practice, the flow is always less than the theoretical flow rate and we introduce Kd, the
coefficient of discharge. Many standards also add a safety factor asking that the flow be
further de-rated by 10% so the sizing formula becomes:
m
A=
⎡ 2 k +1 ⎤
2k M W ⎢⎛ P2 ⎞ k ⎛ P2 ⎞ k ⎥
0.9KdP1 ⎢⎜ ⎟⎟ – ⎜⎜ ⎟⎟ ⎥
k − 1 R T1 ⎢⎜⎝ P1 ⎠ ⎝ P1 ⎠ ⎥
⎣⎢ ⎦⎥ Eq. 3.2.8
This is the formula used by the program.
Sonic Flow
As the pressure downstream is lowered, the velocity through the nozzle increases until it
reaches the speed of sound. When this occurs, the flow becomes choked and lowering the
pressure further on the downstream side does not produce an increase in flow rate. The
pressure at which the flow becomes critical is called the critical pressure, Pcrit.
At this critical pressure, the speed through the nozzle is still given by equation 3.2.6 but it is
also given by equation 2.2.2:
⎡ k −1⎤
2k R T1 ⎢ ⎛ PCRIT ⎞ k ⎥
V2 = . ⎢1 – ⎜ ⎟⎟ ⎥
k − 1 M W ⎢ ⎜⎝ P1 ⎠ ⎥
⎢⎣ ⎥⎦
Eq. 3.3.1
and:
PCRIT
V2 = k
ρCRIT
Eq. 3.3.2
and:
1 1
⎛P ⎞k M ⎛ PCRIT ⎞k
ρCRIT = ρ1 ⎜⎜ CRIT ⎟⎟ = P1 W ⎜⎜ ⎟⎟
⎝ P1 ⎠ RT1 ⎝ P1 ⎠ Eq. 3.3.3
Eliminating V2 we get the relationship between the critical pressure and the upstream
pressure as a function of k.
k
PCRIT ⎛ 2 ⎞k −1
=⎜ ⎟
P1 ⎝ k +1 ⎠ Eq. 3.3.4
Because most of the time relief valves operate in choked mode (sonic flow), most standards
insert this critical pressure ratio in Equation 3.2.8 Then, to cater for the cases when the flow
is subsonic, they re-introduce formula 3.2.8. In the program we operate in a slightly different
manner. The formula always remains the same (Eq. 3.2.8) but we calculate the critical
pressure, PCRIT based on equation 3.3.4. If P2 is less than PCRIT we use PCRIT in the
formula otherwise we use P2 and we have the advantage of having a single formula
covering both cases.
Note: The various relief valve standards still require the calculation of the Critical Pressure
Ratio.
P R
=Z T
ρ M W Eq. 3.4.1
In practice nothing is changed except that T is replaced by ZT in all equations.
A.2.3 Units
Mass flow units are kg/h.
Pressures are in kPa gauge. Atmospheric pressure is assumed to be 101.3 kPa absolute.
Temperatures are in °C, they are changed to Kelvins internally.
C π
qm = ε d 2 2 ΔP ρ1
1− β4 4
Refer ISO5167 part 1 section 5.1
d
β=
However, since D and D is always known (Pipe ID) my own preference is to re-write
the ISO 5167 equation as:
1 π 2
qm = C ε D 2 ΔP ρ1
1 4
−1
β4
And in particular, when sizing a flow element, I find the expression of b as a function of the
other variables particularly useful:
1
β=
1
⎡
⎢1 +
(
C ε π D2 )
2
⎤4
ΔP ρ1 ⎥
⎢⎣ 8 q 2m ⎥⎦ Equation 1
This is the formula I use in preference to that suggested by ISO5167 for the iteration
procedure when calculating b. After each iteration, C is corrected (and for compressible
fluids e) and recalculate.
Continue at:
• Calculation Problems
• Pressure Loss
• Other Remarks
Sizing Problem
This is the normal design function given a flow rate and a differential pressure; calculate the
b factor of the flow element that will satisfy the conditions.
Because often the designer wants a full scale differential pressure corresponding to a round
figure, it pays to allow a full scale flow rate and full scale DP to specified as well as
specifying a normal flow. In this case the first step is to calculate the normal differential
pressure.
2
⎛ FLOWnormal ⎞
DPnormal = DPmax ⎜⎜ ⎟⎟
⎝ FLOWmax ⎠
If the designer enters a Full scale flow rate and full scale DP without specifying a normal
2
flow rate, then a normal flow rate of 2 the full scale flow rate is applied as a reasonable
estimate of what the expected normal flow will be.
Then using this value for the normal differential pressure and the normal flow, the design
proceeds by iteration until sufficient precision is achieved:
First assume C = 0.6, e= 1.0
Step 1 calculate b using Equation 1
Step 2 using the calculated b, calculate C
Step 3 using b calculate e (in the case of compressible fluid only)
Go back to step 1 and continue looping until convergence has been achieved.
Once b has been calculated, the actual maximum flow at the full scale differential pressure
is back calculated and displayed (this shows the difference between the nominal maximum
flow originally specified and the actual maximum flow). Similarly if a minimum flow had been
nominated, then the DP at the minimum flow is also calculated.
The b calculation is ALWAYS done for normal flow.
DP Calculation Problem
This calculation is required if an existing flow element is in service but an increase in
throughput is required. New full scale and normal flows are usually nominated and the
transmitter needs to be re-ranged. b is known.
2
If only the full scale flow rate is given, then the normal flow is assumed as 2 the
maximum flow rate.
The calculation proceeds as follows:
Since flow and b are known, the Reynolds number and C are calculated. We assume
e= 1.0
Step 1 The differential pressure is calculated with pdrop
Step 2 e is calculated (only necessary for compressible fluids)
Return to step 1 and iterate until convergence is achieved.
The calculation is carried out for all the flows nominated.
Continue at:
• Tapered Thermowells Natural Frequency
• Analysis of a Cylindrical (Parallel) Thermowell (or Sample Quill)
• Order of Accuracy
d = D0/D1.
E = Young’s Modulus (2. 1011 Pa for steel and stainless steel).
I (x ) =
(
π D (4x ) − D 04 )
64 Eq. 2.1
⎡ x ⎤
D ( x ) = D1 ⎢1 − (1 − k )⎥
⎣ L ⎦ Eq. 2.2
hence we get for I(x):
πD14 ⎡⎛ x ⎞
4
⎤
⎢⎜1 − (1 − k )⎟ − δ ⎥
4
I (x ) =
64 ⎣⎢⎝ L ⎠ ⎦⎥ Eq. 2.3
The simplest deflected shape which we can use is:
⎡x4 x3 x2 ⎤
y ( x,t ) = λ ⎢ 4 − 4 3 + 6 2 ⎥ sin (ωt )
⎣L L L ⎦
Eq. 2.4
as it is consistent with the cantilevered condition at x = 0 & x=L since it is the deflected
shape of a cantilever of uniform section subjected to a uniform load (l is an arbitrary
constant).
∂y ⎡x4 x3 x2 ⎤
= ωλ ⎢ 4 − 4 3 + 6 2 ⎥ cos(ωt )
∂t ⎣L L L ⎦
The instantaneous speed is: Eq. 2.5
the maximum kinetic energy occurs when cos(wt)=1 and is given by:
1 ⎡
L
U k = ∫ ⎢ ρπ
(
D (2x ) − D 02 )⎤⎛ ∂y ⎞ 2
⎥⎜ ⎟ dx
2 0 ⎢⎣ 4 ⎥⎦⎝ ∂t ⎠ MAX Eq.2.6
or:
πρλ 2 ω 2 ⎡ 2 x2 ⎞ ⎤
2
L
⎛ x4 x3
Uk =
8 ∫ (
⎢ D ( x ) − D 02 )
⎜⎜ 4 − 4 3 + 6 2 ⎟⎟ ⎥ dx
0⎢⎣ ⎝L L L ⎠ ⎥
⎦ Eq. 2.7
πω 2 λ 2ρL D12
Uk =
27720
[
5353 k 2 + 2142 k + 513 − 8008δ 2 ]
Eq. 2.8
The internal energy in the thermowell at maximum deflection is:
1 ⎡ M (x ) ⎤
L 2
2 ∫0 ⎢⎣ E I ( x ) ⎥⎦
Ui = ⎢ ⎥ dx
Eq. 2.9
where M(x) is the bending moment at x.
The bending moment, M(x), is a function of the stiffness and curvature of the deflected
thermowell:
∂2y
M (x ) = E I (x )
∂x 2 Eq. 2.10
Since we assumed the shape, we have:
⎡∂2y⎤ 12 λ ⎛ x 2 x ⎞
⎢ 2⎥ = ⎜
2 ⎜ 2
− 2 + 1⎟⎟
⎣ ∂x ⎦ MAX L ⎝L L ⎠
Eq. 2.11
We get for the internal energy:
144 λ 2 E ⎡ ⎛ x 2 ⎞ ⎤
L 2
x
2 L4 ∫0 ⎢ ⎜⎝ L2
Ui = ⎢I ( x ) ⎜ ⎟
− 2 + 1⎟ ⎥dx
L ⎠ ⎥
⎣ ⎦ Eq. 2.12
Replacing I(x) by its expression in equation 2.3 and integrating we finally obtain:
λ 2 Eππ 14 4
Ui =
560L 3
[
k + 5 k 3 +15 k 2 + 35 K + 70 − 126 δ 4 ]
Eq. 2.13
and finally we get by equating Ui and Uk since according to the principle of conservation of
energy, when the kinetic energy is maximum, the potential (internal) energy is zero and vice-
versa.
ω D E ⎡ k 4 + 5 k 3 +15 k 2 + 35 k + 70 − 126δ 4 ⎤
fn = = 1.1197 21 ⎢ ⎥
2π L ρ ⎣ 5353 k 2 + 2142k + 513 − 8008δ 2 ⎦
Eq. 2.15
I=
(
π D4 − d4 )
64 Eq. 3.1 where D is the outside diameter, and d the bore diameter.
The cross section is:
A=
(
π D2 − d 2 )
4 Eq. 3.2
The general motion of a beam of uniform cross section in free motion is:
∂4y ∂2y
EI + ρA =0
∂x 4 ∂t 2 Eq. 3.3
Where y is the deflection of the beam (as a function of x and t).
Because we are looking at a single harmonic function, y(x,t) can be written as:
y(x,t) = y(x) cos(wt) where w = 2 p fn (fn = natural frequency)
The equation to be solved is now:
d4y ω2
− ρ A y= 0
dx 4 EI Eq. 3.4
ρAω 2
z4 =
If we call
EI
The generalised solution of the y(x) equation is:
this implies
A1 = − A 3 Eq. 3.7
2
∂ y
2= 0
3. at x = L, the bending moment is always 0 hence ∂ x ,
this implies, taking into account the relations obtained at 1) and 2):
A 2 = − A1
[sinh (z L ) + sin (z L )]
[cosh(z L ) + cos(z L )] Eq. 3.8
∂3y
3
=0
4. at x = L, the shear force is also always 0 hence ∂x , taking into account all
previous relations we finally get:
A1
[1 + cos(z L )cosh(z L )] = 0
[cos(z L ) + cosh (z L )] Eq. 3.9
For this to be true regardless of A1 is we must have
3.516015 E I
ω=
L2 ρA
This corresponds to or in frequency:
0.55959 E I
fn =
L2 ρA Eq. 3.11
d
δ=
If we define D we can write I and A as functions of D and d:
πD 4
I=
64
(
1− δ4 )
πD 2
A=
4
(
1 − δ2 )
And the frequency formula becomes:
fn =
0.139898 D E 1+ δ 2 ( )
L2 ρ Eq. 3.12
This formula is exact for parallel thermowells:
d = 0.26
k = 1.0
d = 0.76
k = 1.0
Perfect Gases
P R
= T
ρ M W Eq. 2.1.1
Where:
P is the absolute pressure in kPa
Real Gases
Real gases follow the ideal gas law closely. A factor, Z, called compressibility factor, is often
introduced to show the deviation from ideal behaviour. Z = 1.0 means the gas is behaving
like an ideal gas.
P R
=Z T
ρ M W Eq. 2.2.1
R
T
MW aT
P= −
1 1⎛1 ⎞
−b ⎜⎜ + b ⎟⎟
ρ ρ⎝ρ ⎠ Perry’s Eq. 4-220
With for a single component gas:
2
⎛ R ⎞ 2.5
0.42748 ⎜⎜ ⎟⎟ TC
a= ⎝ MW ⎠
PC Perry’s Eq. 4-223
and:
R
0.08664 TC
MW
b=
PC Perry’s Eq. 4-224
Expressing it for Z, Perry’s give:
⎛ ⎞
⎜ ⎟
Z=
1
− ⎜ a ⎟⎛⎜ h ⎞⎟
1− h ⎜ R 1.5 ⎟⎝ 1+ h ⎠
⎜b T ⎟
⎝ MW ⎠ Perry’s Eq. 4-225
with:
bP
h=
R
Z T
M W Perry’s Eq. 4-227
In those equations, Pc is the critical pressure and TC is the critical temperature.
Reduced Variables
P
PR =
PC Reduced Pressure Eq. 4.1.1
T
TR =
TC Reduced temperature Eq. 4.1.2
⎛ ⎞
⎜ ⎟
1 ⎛ 0.42748 ⎞⎜ 1 ⎟
Z= − ⎜⎜ ⎟
1.5 ⎟⎜ ⎟
0.08664 ⎛ PR ⎞ ⎝ 0.08664 TR ⎠⎜ 1+ Z ⎛ TR ⎞⎟
1− ⎜ ⎟⎟ ⎜ ⎟⎟
Z ⎜⎝ TR ⎠
⎜ 0.08664 ⎜ P
⎝ ⎝ R
⎟
⎠ ⎠ Eq. 4.2.1
or:
⎡ ⎤ ⎡ ⎛ PR ⎞⎤
⎢ ⎥ ⎢ ⎜ ⎟⎥
Z= ⎢
Z ⎥ − ⎢⎛⎜ 0.42748 ⎞⎟⎜ TR ⎟⎥
⎢ ⎜ ⎟⎜ ⎟
⎢ ⎛P ⎞ ⎥ TR1.5
⎠⎜ Z + 0.08664⎛⎜ PR ⎞ ⎟⎥
⎢ Z − 0.08664⎜⎜ R ⎟⎟ ⎥ ⎢⎝ ⎜T ⎟⎟ ⎥
⎜ ⎟
⎣⎢ ⎝ TR ⎠ ⎦⎥ ⎢⎣ ⎝ ⎝ R ⎠ ⎠⎥⎦ Eq 4.2.2
Or, when placing the right hand side over a common denominator:
⎛ P ⎞ ⎛ PR ⎞⎛ P ⎞
Z⎜⎜ Z + 0.08664 R ⎟⎟ − ⎜⎜ 0.42748 2.5 ⎟⎟⎜⎜ Z − 0.08664 R ⎟⎟
TR TR ⎠⎝ TR
Z= ⎝ ⎠ ⎝
2
⎠
⎛ P ⎞
Z 2 − ⎜⎜ 0.08664 R ⎟⎟
⎝ TR ⎠
Eq. 4.2.3
And passing the denominator to the left hand side:
2
⎛ P ⎞ ⎛ P PR ⎞ 0.08664 × 0.42748PR2
Z − ⎜⎜ 0.08664 R
3
⎟⎟ Z = Z 2 + Z⎜⎜ 0.08664 R − 0.42748 2.5 ⎟+
⎝ TR ⎠ ⎝ TR TR ⎟⎠ TR3.5
Z 3 − Z 2 + R 1 Z − R 2 = 0 Eq. 4.2.4
with:
2
PR ⎛ P ⎞ P
R 1 = 0.42748 2.5 − ⎜⎜ 0.08664 R ⎟⎟ − 0.08664 R
TR ⎝ TR ⎠ TR
Eq 4.2.5
and:
Y = Z 3 − Z 2 + R 1 Z − R 2 Eq. 5.1
dY
= 3 Z2 − 2 Z + R1
dZ Eq 5.2
The iterative method consists of picking a first guess for Z (1.0 is a good start) then we
calculate Y using equation 5.1 and dY/dZ with equation 5.2. We then make a correction to Z
such as:
Y
Cor = −
dY
dZ Eq. 5.3
And the new Z is calculated as previous Z + Cor.
The iterations continue until Cor becomes small enough in absolute value.
Note that a 3rd degree equation can have three real roots. Perry’s states that for T >Tc only
one root exists but for T < Tc at certain pressures, up to 3 positive roots can exist and for the
vapour state the largest should be used.
My experience is that starting from Z = 1.0, for all reasonably realistic pressures/
temperatures the convergence is to the gas phase Z.
Following configuration files will be used by the AVEVA Schematic Gateway to process the
data exported from AVEVA Instrumentation:
• Project Configuration
• Object Mapping
• Classes Mapping
• Presentation Mapping
All these configuration files are of XML format and are best edited in XML editor, but
notepad or any text editor can also be used. It is recommended for the user to have one
configuration file of each type mentioned above per element to be exported to AVEVA NET.
All these configuration files are provided as input to the Gateway. Elements and attributes of
these configuration files are detailed out in subsequent sections below.
<Files>
<Extension> … </Extension>
<ExcelRanges> … </ExcelRanges>
<ExcelAddHotspotting> … </ExcelAddHotspotting>
<TagsNamedRange> … </TagsNamedRange>
</Files>
<RegularExpression>
<Search> … </Search>
</RegularExpression>
</InputFiles>
</ConfigurationSettings>
ConfigurationSettings
This is the root element for all Project Configurations and contains following sub-elements.
There would be only one ConfigurationSettings element allowed in the Project Configuration
XML.
TemplateID
Each EIWM output file should have a template Id that must be unique to that file for the
project. The "TemplateID" is typically based on the output file name. "TemplateID" is an
optional element.
The "TemplateID" can be specified in a number of ways:
• Fixed "TemplateID" specified:
All file(s) produced based on the configuration file will have the Template ID specified.
This should not be used if multiple files are being produced.
e.g <TemplateID>C:\Staging\Instruments_null.XML</TemplateID>
• Root "TemplateID" specified:
The Template ID in the output file will be the full output file name with the string
specified removed from its start.
e.g. <TemplateID Root="true">C:\</TemplateID>
In this example, if the full output file name is "c:\Staging\Instruments_null.xml", then the
output would be "Staging\Instruments_null.xml".
• No "TemplateID" specified.
If no "TemplateID" is specified then the full file name (incl. path) of the output file will be
used for the Template ID.
"TemplateID" supports following Attributes:
Root: As mentioned in the example above, this attribute is used to remove the specified
path from the start of the full output file path.
OutputFile
AVEVA Schematic Gateway will generate an XML output in EIWM format that can be
imported into AVEVA NET using AVEVA NET Import Controller. Although the output for the
entire DataSet can be generated into a single EIWM file, sometimes its desirable to split the
output into multiple EIWM files to facilitate easy import of data into AVEVA NET. This is
because AVEVA NET can handle small EIWM files more effectively as compared to large
EIWM files. "OutputFile" is a mandatory element.
"OutputFile" element supports following attributes:
File: This attribute allows user to specify the name of the Output File. It's a mandatory
attribute.
e.g. <OutputFile File="Instruments_null.XML"/>
DeleteExisting: "DeleteExisting" can have "true" and "false" as valid values. Setting
"DeleteExisting" to "true" deletes all the contents of the staging area before proceeding with
execution of the export functionality of the Gateway. This is an optional attribute and default
value of this attribute would be "false".
"OutputFile" can have following sub-elements:
Directory
In order to break the output into multiple EIWM files, an element "Directory" can be used.
This is an optional element, but if used, it can occur many times under "OutputFile" element.
e.g.<Directory>AreaNo</Directory>
In above example, a sub-directory for each AreaNo will be created under Staging Area
("AreaNo" would be the exact column name in the DataSet) and each sub-directory would
contain EIWM file/s corresponding to the specific AreaNo.
<Directory>AreaNo</Directory>
<Directory>TagNo</Directory>
Above example will result into sub-directory under Staging Area for each unique AreaNo
and then further sub-directories under each "AreaNo" specific directory per "TagNo" (again
"AreaNo" and "TagNo" should be the exact column names in the DataSet).
"Directory" element supports following attributes:
SearchExpression: This attribute allows user to provide an expression to generate the
name of the directory. This is an optional attribute.
e.g. <Directory SearchExpression="substring(TagNo, 1, 4)"/>
Above example will result into sub-directories with unique strings of first 4 characters of the
available "TagNo"s. ("TagNo" should be the exact column name in the DataSet).
KeepUnmappedAttributes
This element defines how to handle attributes of the entity not defined in Attributes Mapping
configuration. This element can have "true" and "false" as valid values. If it is set to "true",
then all unmapped attributes of the entity will be exported as characteristics. This is an
optional element and its default value will be "false" if not defined explicitly.
e.g. <KeepUnmappedAttributes>true</KeepUnmappedAttributes>
Mapping
The mapping section is where configuration gets down to mapping rows/nodes from the
DataSet to AVEVA NET objects. Each configuration file can have one or more mapping
sections but most of the cases, there would be need of at the most only one mapping
section. In case of multiple mapping sections each mapping section will be applied to each
entity (row or node) in the DataSet in turn.
Object mappings will create object instances for AVEVA NET. The format of the mapping for
the high level object data (identity, class…) will resemble:
<Mapping Type="Object" Condition="" UseIdForFileNames="false">
<ID ApplyBehaviour="concat(ID, TagNo, ' Instrument')"/>
<Context Value="PROJECTCONTEXT"/>
<ClassID From="Description"/>
<Name From="Description" Default="N/A" RegExPattern="[A-Z]{3}"
RegExRemovePattern="\s"/>
</Mapping>
Various AVEVA NET Properties that can be mapped here are:
• ID
• Context
• ClassID
• Name
All these properties can be specified under mapping section as separate sub-elements. As
mentioned above, these elements support following attributes:
Value: Hard coded string that will be used as the value of the property in the output.
ApplyBehaviour: Perform some processing on DataSet value(s) to determine the output.
The setting for the ApplyBehaviour can be any XPath 1.0 functions.
From: DataSet column (or node) name from which value should be read.
Default: A default value that will be used if no value is found in the DataSet. If no value is
found in the DataSet for a mapped property then that will not be included in the output file
unless a default for it is defined - if no value to be written, specify default="".
RegExPattern: Specified regular expression pattern will be applied to the property value
and the matched sub-string to the pattern will be the output value.
RegExRemovePattern: A regular expression pattern to identify part of the value to be
removed. E.g. This could be used to remove spaces or dashes from a value.
Note: Out of "From", "Value" or "ApplyBehaviour" which define how the value for the
property should be determined, one and only one of these three should be specified.
In case user specifies more than one attributes out of these three, then preference
will be given in following sequence > Value, ApplyBehaviour, From.
Association
An Association is a link between two Objects that can be followed from one Object to
another and there is no limit to the number of Associations an Object may have. This is an
optional element.
Association supports the following sub-elements:
TargetClassID: This element specifies the Class ID of the target object with which the
object has the association.
TargetContext: This element specifies the namespace of the target object.
TargetClassID: This element specifies the Class ID of the target object with which the
object has the association.
TargetContext: This element specifies the namespace of the target object.
TargetName: This element specifies the name assigned to the target object.
All these sub-elements support "From", "Value" and "ApplyBehaviour" attributes, but one at
a time one and only one out of these three should be specified. Usage of these attributes
will be exactly same as mentioned above in "Mapping" section.
"Association" supports following attribute:
Type: This attribute specifies the type of relationship between the object and the target
object. The relationship mentioned here should be supported by AVEVA NET for example:
<Association Type="is classified as">
<TargetID From="TagNo"/>
<TargetRevision Value="1.2"/>
<TargetClassID From="Description"/>
<TargetContext Value="NewNamespace"/>
<TargetName Value="Instrument"/>
</Association>
InputFiles
This element gives us information about how to process the input files of different types (e.g.
xls, xlsx, pdf). "InputFiles" is not mandatory and can be ignored if there are no input files to
be processed.
AVEVA Schematic Gateway accepts "input file location" as well as list of files to be
processed as an input. When no input file names are provided to the Gateway, it will
process all the files present in the Input location.
"InputFiles" support following attribute:
IncludeSubFolders: If IncludeSubFolder is set as "true", Gateway will search the
subfolders of the Input location too. This attribute will carry no meaning if list of files to be
processed is provided to the Gateway.
InputFiles supports following sub-elements:
Files
This Element provides the gateway, information about the different types of file extensions
that are processed by it, for example:
<Files>
<Extension>xlsx</Extension>
<ExcelAddHotspotting>true</ExcelAddHotspotting>
<ExcelRanges>true</ExcelRanges>
<TagsNamedRange>VNETTags,TagNo</TagsNamedRange>
</Files>
Files supports following sub-elements:
Extension: This specifies the extension of the files unique to the current "Files" element for
which rest of the elements in the "Files" block are applicable to. Valid values are: xls, xlsx,
pdf.
e.g., <Extension>xls</Extension>
ExcelRanges: This element has "true" and "false" as valid values. If this is set to "true", the
gateway will hotspot the output file with the specified ranges in the excel spreadsheet. This
element works in conjunction with "TagsNamedRange" and only the ranges specified in
"TagsNamedRange" will be hot-spotted.
If this element is "false", then the Gateway will hotspot the values which match the search
patterns mentioned in RegularExpression.
This element will be ignored if "ExcelAddHotspotting" is set to "false". Moreover this element
is applicable only if "Extension specified is either "xls" or "xlsx". For other extensions this
element will be ignored. Default value of this element, if not set, will be "false".
ExcelAddHotspotting: If this is set to "true", then hot-spotting would be performed on the
output MHTML file. This element is optional and is expected to be set only if "extension" is
"xls" or "xlsx". Default value of this element, if not set, will be "false".
TagsNamedRange: If "ExcelRanges" is set to "true", then the gateway will hot-spot the
Ranges mentioned in this element.
e.g., <TagsNamedRange>VNETTags,TagNo</TagsNamedRange>
This element is optional and is expected to be set only if "extension" is "xls" or "xlsx". Default
value of this element, if not set, will be "". Multiple ranges can be specified as a comma
separated string.
RegularExpression
If "ExcelRanges" element is set to "false", the Gateway would choose the Regular
expression search patterns for hot-spotting. This element is optional.
RegularExpression supports following sub-elements:
Search: The regular expressions specified in this element would be matched to the text in
the input file and the cell containing the matching text would be hot-spotted.
e.g., <Search>[A-Z]{3}</Search>
If the above search pattern is provided in the Project Configuration and if the datasheet has
a cell with value "ABCD123", then that cell would be hot-spotted.
RegularExpression can have as many "Search" expressions as want but there has to be at
least one "Search" element under it.
Attributes
This is the root element in the Attributes Mapping file. It contains multiple instances of the
sub-element "Attribute". There can be only one instance of the "Attributes" element.
Attribute:
"Attributes" element can contain multiple instances of this element. It specifies the attribute
in the input dataset which is to be mapped into another attribute in the output file. It can also
specify if an attribute should be present in the output file or not.
Following are the attributes supported by this element:
From: The value for the new attribute would be taken from the column specified in this
attribute from the DataSet. It is mandatory to have the attribute mentioned here be available
in the DataSet as a column.
e.g., <Attribute From="TagNo" To="Tag Number" Output="true"/>
In the above example, in the output file there would be a characteristic as follows:
<Characteristic>
<Name>Tag Number</Name>
<Value>00-AE-123ab</Value>
</Characteristic>
Value: Hard coded string that will be used as the value of the characteristic.
ApplyBehaviour: Perform some processing on DataSet value(s) to determine the value of
the characteristic.
Note: Out of "From", "Value" or "ApplyBehaviour" which define how the value for the
attribute should be determined, one and only one of these three should be specified.
In case user specifies more than one attributes out of these three, then preference
will be given in following sequence >Value, ApplyBehaviour, From.
To: This attribute provides the name of the new characteristic. This is mandatory attribute.
Default: A default value that will be used if no value is found in the DataSet.
RegExPattern: : Specified regular expression pattern will be applied to the attribute's value
and the matched sub-string to the pattern will be the output value for the characteristic.
RegExRemovePattern: A regular expression pattern to identify part of the value to be
removed. E.g. This could be used to remove spaces or dashes from a value.
Output: This attribute can have "true" and "false" as valid values. If it is "true", the output file
would contain the corresponding attribute. If it is "false", the attribute would not be present in
the output file.
If the value of attribute 'Output' is "true", then one of the following attributes must be present:
"Value", "From" or "ApplyBehaviour".
Classes
This is the root element in the Classes Mapping file. It contains multiple instances of the
sub-element "Class". There can be only one instance of the "Classes" element.
Class:
Every "Classes" element can contain multiple instances of this element. It specifies the
Class mappings between the ClassIDs in the input system and output file.
e.g., <Class From="PUMP" To="INSTRUMENT"/>
Following are the attributes of the element 'Class':
From: The ClassID of the current object which is to be mapped.
To: The ClassID of the object in the Target Namespace.
Presentation
This is the root element in the Presentation Mapping file. It contains a single instance of the
sub-element "Colours". There can be only one instance of the "Presentation" element.
Colours:
The “Colours” element contains multiple instances of the sub-element "Colour". There can
be only one instance of the "Colours" element.
Colour:
Every "Colours" element can contain multiple instances of this element. It specifies the
colour mappings between the colours in the input and output files.
For example:
<colours>
<colour>
<from index="6"/>
<to R="255" G="0" B="255"/>
</colour>
<colour>
<from index="5"/>
<to name="Blue"/>
</colour>
</colours>
From: Must be a valid AutoCAD colour index (0-256).
To: Either a a valid colour name or an RGB value (see below).
antiquewhite 250,235,215
aqua 0,255,255
aquamarine 127,255,212
azure 240,255,255
beige 245,245,220
bisque 255,228,196
black 0,0,0
blanchedalmond 255,235,205
blue 0,0,255
blueviolet 138,43,226
brown 165,42,42
burlywood 222,184,135
cadetblue 95,158,160
chartreuse 127,255,0
chocolate 210,105,30
coral 255,127,80
cornflowerblue 100,149,237
cornsilk 255,248,220
crimson 220,20,60
cyan 0,255,255
darkblue 0,0,139
darkcyan 0,139,139
darkgoldenrod 184,134,11
darkgray 169,169,169
darkgreen 0,100,0
darkgrey 169,169,169
darkkhaki 189,183,107
darkmagenta 139,0,139
darkolivegreen 85,107,47
darkorange 255,140,0
darkorchid 153,50,204
darkred 139,0,0
darksalmon 233,150,122
darkseagreen 143,188,143
darkslateblue 72,61,139
darkslategray 47,79,79
darkslategrey 47,79,79
darkturquoise 0,206,209
darkviolet 148,0,211
deeppink 255,20,147
deepskyblue 0,191,255
dimgray 105,105,105
dimgrey 105,105,105
dodgerblue 30,144,255
firebrick 178,34,34
floralwhite 255,250,240
forestgreen 34,139,34
fuchsia 255,0,255
gainsboro 220,220,220
ghostwhite 248,248,255
gold 255,215,0
goldenrod 218,165,32
gray 128,128,128
green 0,128,0
greenyellow 173,255,47
grey 128,128,128
honeydew 240,255,240
hotpink 255,105,180
indianred 205,92,92
indigo 75,0,130
ivory 255,255,240
khaki 240,230,140
lavender 230,230,250
lavenderblush 255,240,245
lawngreen 124,252,0
lemonchiffon 255,250,205
lightblue 173,216,230
lightcoral 240,128,128
lightcyan 224,255,255
lightgoldenrodyellow 250,250,210
lightgray 211,211,211
lightgreen 144,238,144
lightgrey 211,211,211
lightpink 255,182,193
lightsalmon 255,160,122
lightseagreen 32,178,170
lightskyblue 135,206,250
lightslategray 119,136,153
lightslategrey 119,136,153
lightsteelblue 176,196,222
lightyellow 255,255,224
lime 0,255,0
limegreen 50,205,50
linen 250,240,230
magenta 255,0,255
maroon 128,0,0
mediumaquamarine 102,205,170
mediumblue 0,0,205
mediumorchid 186,85,211
mediumpurple 147,112,219
mediumseagreen 60,179,113
mediumslateblue 123,104,238
mediumspringgreen 0,250,154
mediumturquoise 72,209,204
mediumvioletred 199,21,133
midnightblue 25,25,112
mintcream 245,255,250
mistyrose 255,228,225
moccasin 255,228,181
navajowhite 255,222,173
navy 0,0,128
oldlace 253,245,230
olive 128,128,0
olivedrab 107,142,35
orange 255,165,0
orangered 255,69,0
orchid 218,112,214
palegoldenrod 238,232,170
palegreen 152,251,152
paleturquoise 175,238,238
palevioletred 219,112,147
papayawhip 255,239,213
peachpuff 255,218,185
peru 205,133,63
pink 255,192,203
plum 221,160,221
powderblue 176,224,230
purple 128,0,128
red 255,0,0
rosybrown 188,143,143
royalblue 65,105,225
saddlebrown 139,69,19
salmon 250,128,114
sandybrown 244,164,96
seagreen 46,139,87
seashell 255,245,238
sienna 160,82,45
silver 192,192,192
skyblue 135,206,235
slateblue 106,90,205
slategray 112,128,144
slategrey 112,128,144
snow 255,250,250
springgreen 0,255,127
steelblue 70,130,180
tan 210,180,140
teal 0,128,128
thistle 216,191,216
tomato 255,99,71
turquoise 64,224,208
violet 238,130,238
wheat 245,222,179
white 255,255,255
whitesmoke 245,245,245
yellow 255,255,0
yellowgreen 154,205,50
Index
U
Undo and Redo . . . . . . . . . . . . . . . . . . . 4:17
W
Work Packs . . . . . . . . . . . . . . . . . . . . . . . 8:1