Академический Документы
Профессиональный Документы
Культура Документы
User’s Guide
All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or
implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties.
The information and the software discussed in this document are subject to change without notice and should not be considered
commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this
license.
No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its
affiliated companies.
Trademarks
CLIX and Intergraph are registered trademarks of Intergraph Corporation. DesignReview, DIALOG, and SEE are trademarks of Intergraph
Corporation. All other brands and product names are trademarks of their respective owners.
Copyright
1984-2002 Intergraph Corporation
All Rights Reserved
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright and trade secret law and may not
be provided or otherwise made available without proper authorization.
Unpublished — rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
________________ If You Need Assistance
Intergraph Online
Our web site brings you fast, convenient, up-to-the-minute information about Intergraph’s
products, services, and direction. Our web address is: http://www.intergraph.com.
Support
For the lasest Support Services information, use a World Wide Web browser to connect to
http://www.intergraph.com/ppo/services/support.asp.
If you are outside of the United States, please call your local Intergraph office. The most up-
to-date list of international offices and distributors is available on the web at
http://www.intergraph.com.
Intergraph Directory
The following numbers are only valid in the United States unless otherwise indicated. If you
are outside the United States, please call your local Intergraph office.
Training Registration
1-800-766-7701 (U.S. Only)
Mailing Address
Intergraph Process, Power & Offshore
300 Intergraph Way
Madison, Alabama 35758
U.S.A.
3
________________
Documentation Contacts
We are constantly working on updates and improvements to the documents and other
educational media. If you have any suggestions on where we can improve the documentation
or where you think more information is needed, let us know. You can reach us by:
4
________________ Table of Contents
Table of Contents
If You Need Assistance ........................................................................................................ 3
Intergraph Directory ............................................................................................................. 3
5
________________
Report Manager User’s Guide - April 2002
6
________________ Table of Contents
4.3.1 Ownership (Piping Material Class and Line Name) ............................................... 146
4.3.2 Special Attributes .................................................................................................... 146
7
________________
Report Manager User’s Guide - April 2002
8
________________ Table of Contents
9
________________
Report Manager User’s Guide - April 2002
10
________________ Table of Contents
11
________________
Report Manager User’s Guide - April 2002
12
________________ Table of Contents
General Conventions
This document contains many visual cues to help you understand the meaning of certain
words or phrases. The use of different fonts for different types of information allows you to
scan the document for key concepts or commands. Symbols help abbreviate and identify
commonly used words, phrases, or groups of related information.
Typefaces
Italic Indicates a system response, which is an explanation of what the software is
doing. For example,
Bold Indicates a command name, parameter name, or dialog box title. Command
paths are shown using an arrow between command names. For example,
Sans serif Indicates a system prompt or message, which requires an action be taken by
the user. For example,
Bold Typewriter
Indicates what you should literally type in. For example,
Normal Typewriter
Indicates an actual file or directory name. For example,
13
________________
Report Manager User’s Guide - April 2002
Symbols
This document uses the following symbols to represent mouse buttons and to identify special
information:
Warning — Critical information that could cause the loss of data if not followed.
Need a hint — used with activities and labs, provides a tip or hint for doing the
exercises.
Keyboard Conventions
The following list outlines the abbreviations this document uses for keyboard keys and
describes how to use them in combination. You can make some menu selections through the
use of keyboard accelerators, which map menu selections to key combinations.
14
________________ Table of Contents
Terminology
Click To use a mouse or key combination to pick an item that begins an
action. For example,
Select the file original.dat from the list box, then click Delete to
remove it from the directory.
Drag To press and hold the data button (<D>) while moving the mouse or
hand-held cursor.
Key in To type in data and press ENTER to enter the data and execute the
default action.
15
________________
Report Manager User’s Guide - April 2002
16
________________ Welcome to Report Manager (PD_Report)
1.Overview
Material take-off reports (MTOs) can be generated on piping and equipment models through
PD_Report. The MTO process generates reports by using the graphical data in the specified
models to refer to the Design Database, Reference Database, Project Database, and Material
Description Libraries for the data on which to report. This data includes implied materials,
such as bolts, gaskets, and welds, that are not represented in the model but are necessary for
the specified connectivity.
17
________________
Report Manager User’s Guide - April 2002
In addition to the engineering data in the design database, PDS 3D uses the Material
Description Library and the material data in the Material Reference Database to provide
material descriptions for commodity items and specialty items.
18
________________ Reporting Overview
Reporting Process
These are the basic steps in the Material Take-Off process.
1.Overview
1. The system reads the user-defined report data, determines the discrimination data (such
as which models to process) and the format (content and layout) of the report.
2. For the specified models (and using any additional discrimination data, such as line
size), the system scans the physical elements in the model.
3. The system determines the number of items present in the model by unique commodity
code. In addition to the physical elements, it determines any implied items based on
configuration of mating components or designations in the Piping Commodity
Specification Data (PCD).
4. The system looks up the material descriptions for the located components and implied
items in the Material Description Library.
5. The system writes a report of the located and calculated items based on pre-defined
report format.
The two most important files that must be maintained in a report creation process are the
discrimination data file and the format file. The discrimination data file, which defines the
search criteria for a report, is maintained interactively with the Report Manager. The format
file is generated outside of the interface using an ASCII text editor. There are several sample
format files that are sent with the PDS product suite. You can use these files as examples for
creating format files to meet your specific needs.
The following section explains all of the files and records in the reporting process.
19
________________
Report Manager User’s Guide - April 2002
The format record is a record in the Project Control Database used to name and locate a
specific format file. Unlike the format file, the format record is created interactively. It is
called a record to classify it as a block of data that is used for report processing but is not an
actual file.
The discrimination data record is a record in the Project Control Database used to name and
locate a specific discrimination data file. There is a uniquely-numbered record for each
discrimination data file, so that it can be accessed for report processing. This is the same way
that the format record is used to access a format file.
The search criteria data record is a record in the Project Control Database used to name and
locate a specific search criteria data file. There is a uniquely-numbered record for each search
criteria data file, so that it can be accessed for report processing. This is the same way that the
format record is used to access a format file.
At the end of each report, Report Manager provides a parameters page which contains the
following information used by the system to generate the report:
20
________________ Reporting Overview
Report Output
Report number
1.Overview
Report title
Format
Discrimination Data
— Volume, if applicable
— Sorting sequence
Search Criteria
— Volume, if applicable
21
________________
Report Manager User’s Guide - April 2002
— Sorting sequence
22
________________ Processing Reports
1.Overview
Since there are reporting capabilities in various PDS modules, the format file, the
discrimination data file, and the module where the report process is activated determine what
type of report is created.
For instance, you can create MTO reports with Report Manager and Drawing reports with
the report manager module of Drawing Manager. Depending on the definition data used and
the module that executes the process, you can create MTO reports, Drawing reports, Spec
reports, Table Checker reports, Project reports, or Interference Reports.
For detailed steps in creating a report using the Report Manager interface, see
Chapter 2. Also, the report module is covered in each document that has
reporting capabilities.
The following section describes the various report types, how they are generated, and their
corresponding sample format files.
23
________________
Report Manager User’s Guide - April 2002
Sample Format – The sample format files for creating MTO reports are:
segment.fmt, piping_a.fmt through piping_g.fmt, weight.fmt, equip_a.fmt, and
weldno.fmt and are delivered in the win32app\ingr\pdreport\sample\ directory.
Drawing Report
Generates reports on PDS Piping and Equipment drawing views and drawing files.
This report is the same type of report as the MTO report generated by the Report
Manager. Format files used in this type of report primarily use A and B prefixed
indices. This report is generated using the Drawing Manager.
Sample Format – The sample format file for creating drawing reports are generally
the same as for MTO reports.
Spec Report
Generates reports on the Reference Database and Material Description Libraries.
This type of report is used with format file indices. The Spec report is used to report
on data in the reference database. Format files used to create this type of report
primarily use C prefixed indices. This report is generated by the Reference Data
Manager.
Sample Format – The sample format files for Spec reporting is piping_rdb.fmt and is
delivered in the win32app\ingr\pddata\sample\format\ directory.
Sample Format – The sample format files for Table Checker reporting are
tbl_chk_1.fmt through tbl_chk_6.fmt and are delivered in the
win32app\ingr\pddata\sample\format\ directory.
24
________________ Report Types
Project Report
Generates reports on the Project Control Database. Format files used in this type of
report primarily use D prefixed indices. This report is generated using the Project
Administrator.
1.Overview
Sample Format – The sample format files for Project reporting are: model_mgt.fmt,
iso_mgt.fmt, iso_rev.fmt and are delivered in the win32app\ingr\pdprojec\sample\
directory.
Interference Report
Generates reports on the Project Control Database. Clash Area, Clash Type, and
Clash Approval along with the search criteria specified in the discrimination data
define what interference data is reported. Format files used in this type of report
primarily use D prefixed indices. This report is generated using the Interference
Manager/Checker.
Sample Format – The sample format files for Interference reporting is clash_mgt.fmt
and is delivered in the win32app\ingr\pdclash\sample\ directory.
25
________________
Report Manager User’s Guide - April 2002
Refer to the Project Setup Technical Reference for detailed information about the pconfig
command and setting up a print node.
26
________________ The Report Manager Interface
Manager
2.Report
records for each discrimination data file and format file are stored in the project control
database. These numbered records are used to locate ASCII files on their specified nodes.
Options
Report Format — Displays the Report Format form, which you can use to create,
revise, copy, or delete the record of a format file (not the format file). For more
information, see Report Format Form, page 29.
Report Discrimination Data — Displays the Discrimination Data form, which you
can use to create, revise, copy, or delete the record of a discrimination data file as well
as the file itself. For more information, see Discrimination Data Form, page 35.
Report Search Criteria — Displays the Search Criteria Data form, which enables
you to create, revise, copy, or delete the record of the search criteria data file. The
Create, Copy, and Revise options also affect the actual search criteria data file. The
27
________________
Report Manager User’s Guide - April 2002
Delete option deletes only the record of the search criteria data file, since the data file
itself may be used by other projects. For more information, see Search Criteria Data
Form, page 47.
Copy Format/Search Data from Another Project — Enables you to copy the format
and search data (found in pdtable_142, Report Format Data, and pdtable_145, Report
Search Criteria Data) from other projects into the project control database for the active
project. By copying this data, you can have several different projects share format and
search information. When you choose this option, a list of available projects is
displayed. Select the project from which you want to copy report data, and then choose
Accept.
Report — Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form, page
65.
28
________________ Report Format Form
Manager
2.Report
This form enables you to create, copy, revise, or delete a record of the location of the format
file in the project control database. An option is also provided that enables you to copy a
record and its corresponding ASCII format files.
The format file defines the data that will be reported and the way in which that data will be
displayed. Reports cannot be generated unless a format file exists and a record of the file’s
location has been entered into the project control database.
Options
Create — Displays the Format Creation/Revision form, which enables you to add a
new record of a format file in the project control database. For more information, see
Format Creation/Revision Form, page 31.
Copy — Displays the Format Creation/Revision form, which copies the record of an
existing format file from the project control database along with the corresponding
ASCII format file. For more information, see Format Creation/Revision Form, page
31.
29
________________
Report Manager User’s Guide - April 2002
Delete — Displays the Deletion form, which deletes an existing record of a format file
from the project control database. If the record of the format file is deleted, reporting
cannot be performed. For more information, see Format Deletion Form, page 33.
30
________________ Format Creation/Revision Form
Manager
2.Report
This form creates or revises a record in the project control database; this record defines the
location of a format file. The format file itself defines the contents and format of the report.
Both the location specification and the format file must exist to report on PDS data.
Field Descriptions
Number — A unique number of up to 24 characters. Specifies the short name in the
project control database used to identify the record of the format file.
Path — The disk location of the format file. This field retains the active setting.
Node — The nodename of the system on which the format file is located. This field
retains the active setting.
31
________________
Report Manager User’s Guide - April 2002
Operating Sequence
1. Select Create, Copy, or Revise.
A list of available records displays for copy or revision. To create a database record,
go to Step 3.
From the displayed list, select the record to be copied or revised. Then click Accept.
Key-in fields are displayed for you to specify the required database information.
Type information in each of the displayed fields, taking care to press return in each
field. Then click Accept.
32
________________ Format Deletion Form
Manager
2.Report
This form deletes a report record from the project control database and can optionally delete
the associated file. This form is used with format files and their database records,
discrimination data files and their database records, and search criteria files and their database
records.
Delete File/Do Not Delete File — Determines whether the associated file is deleted.
When set to Delete File, the database record is deleted along with the associated file.
When set to Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
33
________________
Report Manager User’s Guide - April 2002
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
34
________________ Discrimination Data Form
Manager
2.Report
This form creates, copies, revises, and deletes a discrimination data file from the specified
directory. The associated record in the project control database is also copied, revised, or
deleted as needed.
A discrimination data file is an ASCII file that designates which models will be included in a
report. That is, discrimination data specifies the scope of the report. The project control
database record specifies the name and location of the discrimination data file that is to be
associated with a specific report.
Options
Create — Displays the Discrimination Data Creation form, which creates a new
discrimination data file. The associated project control database record is also created.
Copy — Displays the Discrimination Data Revision form, which copies an existing
data file. The associated project control database record is also copied.
35
________________
Report Manager User’s Guide - April 2002
Delete — Displays the Deletion form, which deletes a discrimination data file as well
as its associated record in the project control database. For more information, see
Discrimination Data Deletion Form, page 45.
36
________________ Discrimination Data Creation Form
Manager
2.Report
This form creates a discrimination data file in a specified directory. It also creates a
corresponding record in the project control database. In addition, you can use this form to
specify segment and component search criteria.
If you use this form to specify search criteria data and you specify search
criteria data using the Report Search Criteria option, the data specified using
the Report Search Criteria option takes precedence.
File Specification — The file name of the discrimination data record to be created.
File Path — The disk location of the discrimination data file. This field retains the
active settings.
37
________________
Report Manager User’s Guide - April 2002
File Node — The nodename of the system on which the discrimination data file is
located. This field retains the active settings.
All Piping Models — Specifies in the discrimination data file that all piping models
will be included in the report. Selecting this option disables the Select Piping Area(s)
and Select Piping Model(s) options.
Select Piping Area(s) — Specifies in the discrimination data file the specific piping
areas to be included in the report. Selecting this option displays the Piping Area
Selection form. On this form, select the area and then click Accept to specify a piping
area. When you have specified all piping areas to be included, click Cancel.
Select Piping Models — Specifies in the discrimination data file that specific piping
models will be included in the report. Selecting this option displays a series of forms to
select the models to be included. To select a model, first specify the piping area that
contains the model and click Accept. On the Model Selection form, select a model and
click Accept. When you have specified all piping areas to be included, click Cancel.
All Equipment Models — Specifies in the discrimination data file that all equipment
models will be included in the report. Selecting this option disables the Select
Equipment Area(s) and Select Equipment Model(s) options.
Select Equipment Area(s) — Specifies in the discrimination data file the specific
equipment areas to be included in the report. Selecting this option displays the
Equipment Area Selection form. On this form, select the area and then click Accept
to specify a piping area. When you have specified all piping areas to be included, click
Cancel.
Select Equipment Models — Specifies in the discrimination data file that specific
equipment models will be included in the report. Selecting this option displays a series
of forms to select the models to be included. To select a model, first specify the
equipment area that contains the model and click Accept. On the Model Selection
form, select a model and click Accept. When you have specified all piping areas to be
included, click Cancel.
Segment Search Criteria — Displays the Search Criteria form, which defines the
segment search criteria for the report. For more information, see Search Criteria -
Piping Segment Form, page 52.
Define Volume — Displays the Volume Definition form, which specifies the
coordinates of a design volume cube for reporting. For more information, see
Define Volume Form.
38
________________ Discrimination Data Creation Form
Use this list to change the And/Or relationships between piping segment search criteria
(table 12, piping segment data) and the search criteria for the component data in table
34, piping component data; table 50, piping/tubing data; table 67, instrument
component data; and table 80, pipe support data.
Each category of component search criteria data is related to the piping segment search
criteria by a logical AND or a logical OR. By default, the logical relationship between
the piping segment search criteria and the four categories of component search criteria
Manager
2.Report
is AND. This means that only components that meet the criteria defined for both sets of
criteria are reported.
Setting this relationship to OR increases the amount of data reported in that all
components that match either set of criteria are reported.
Operating Sequence
1. From the Report Discrimination Data form, select Create
In the fields provided, key in the number, description, and file specification, path, and
node.
3. Select additional options as needed to define the report discrimination data. Then click
Accept.
After including any models or search criteria for the discrimination data file,
be sure to click the final Accept. Because you must accept many forms while
specifying the discrimination data, it is easy to forget this step.
Even though you may have accepted many of the specifications, however,
the discrimination data file is not actually created until you click Accept on
the Report Discrimination Data form.
39
________________
Report Manager User’s Guide - April 2002
Use this form to specify the coordinates of a design volume (cube) within the primary model.
Fields
Easting - Low — Specifies the easting coordinates (X’X") for the lower left corner
point of the cube. Use a negative value to indicate a westing coordinate.
Easting - High — Specifies the easting coordinates (X’X") for the upper right corner
point of the cube. Use a negative value to indicate a westing coordinate.
Northing - Low — Specifies the northing coordinates (X’X") for the lower left corner
point of the cube. Use a negative value to indicate a southing coordinate.
Northing - High — Specifies the northing coordinates (X’X") for the upper right
corner point of the cube. Use a negative value to indicate a southing coordinate.
Elevation - Low — Specifies the elevation coordinates (X’X") for the lower left corner
point of the cube. Use a negative value to indicate a negative elevation.
Elevation - High — Specifies the elevation coordinates (X’X") for the upper left corner
point of the cube. Use a negative value to indicate a negative elevation.
40
________________ Define Volume Form
Operating Sequence
1. Click Define Volume.
Key in the absolute easting, northing, and elevation coordinates for the lower left and
upper right corners of the cube. Then click Accept.
Manager
2.Report
41
________________
Report Manager User’s Guide - April 2002
This form revises an existing discrimination data file. It also copies an existing discrimination
data file; you can then use the revision options to modify the copy as needed. The
corresponding records in the project control database are copied and/or modified as needed.
In addition, options are provided for you to modify segment and component search criteria
data.
If you use this form to specify search criteria data and you specify search
criteria data using the Report Search Criteria option, the data specified using
the Report Search Criteria option takes precedence.
File Specification — The file name of the discrimination data record to be created.
File Path — The disk location of the discrimination data file. This field retains the
active settings.
42
________________ Discrimination Data Revision Form
File Node — The nodename of the system on which the discrimination data file is
located. This field retains the active settings.
All Piping Models — Specifies in the discrimination data file that all piping models
will be included in the report. Selecting this option disables the Select Piping Area(s)
and Select Piping Model(s) options.
Select Piping Area(s) — Specifies in the discrimination data file the specific piping
areas to be included in the report. Selecting this option displays the Piping Area
Selection form. On this form, select the area and then click Accept to specify a piping
area. When you have specified all piping areas to be included, click Cancel.
Select Piping Models — Specifies in the discrimination data file that specific piping
Manager
2.Report
models will be included in the report. Selecting this option displays a series of forms to
select the models to be included. To select a model, first specify the piping area that
contains the model and click Accept. On the Model Selection form, select a model and
click Accept. When you have specified all piping areas to be included, click Cancel.
All Equipment Models — Specifies in the discrimination data file that all equipment
models will be included in the report. Selecting this option disables the Select
Equipment Area(s) and Select Equipment Model(s) options.
Select Equipment Area(s) — Specifies in the discrimination data file the specific
equipment areas to be included in the report. Selecting this option displays the
Equipment Area Selection form. On this form, select the area and then click Accept
to specify a piping area. When you have specified all piping areas to be included, click
Cancel.
Select Equipment Models — Specifies in the discrimination data file that specific
equipment models will be included in the report. Selecting this option displays a series
of forms to select the models to be included. To select a model, first specify the
equipment area that contains the model and click Accept. On the Model Selection
form, select a model and click Accept. When you have specified all piping areas to be
included, click Cancel.
Delete Models — Displays the Model Selection form, on which you specify a model to
be deleted from the discrimination data file.
Delete Areas — Displays the Area Selection form, on which you specify an area to be
deleted from the discrimination data file.
Segment Search Criteria — Displays the Search Criteria form, which defines the
segment search criteria for the report. For more information, see Search Criteria -
Piping Segment Form, page 52.
Define Volume — Displays the Volume Definition form, which specifies the
coordinates of a design volume cube for reporting. For more information, see
Define Volume Form.
43
________________
Report Manager User’s Guide - April 2002
Use this list to change the And/Or relationships between piping segment search criteria
(table 12, piping segment data) and the search criteria for the component data in table
34, piping component data; table 50, piping/tubing data; table 67, instrument
component data; and table 80, pipe support data.
Each category of component search criteria data is related to the piping segment search
criteria by a logical AND or a logical OR. By default, the logical relationship between
the piping segment search criteria and the four categories of component search criteria
is AND. This means that only components that meet the criteria defined for both sets of
criteria are reported.
Setting this relationship to OR increases the amount of data reported in that all
components that match either set of criteria are reported.
Operating Sequence
1. From the Report Discrimination Data form, select Copy or Revise.
In the fields provided, key in the number, description, and file specification, path, and
node.
3. Select additional options as needed to define the report discrimination data. Then click
Accept.
After updating any models or search criteria for the discrimination data file,
be sure to click the final Accept. Because you must accept many forms while
specifying the discrimination data, it is easy to forget this step. Even though
you may have accepted many of the specifications, however, the
discrimination data file is not actually updated until you click Accept on the
Report Discrimination Data form.
44
________________ Discrimination Data Deletion Form
Manager
2.Report
This form deletes a report record from the project control database and can optionally delete
the associated file. This form is used with format files and their database records,
discrimination data files and their database records, and search criteria files and their database
records.
Delete File/Do Not Delete File — Determines whether the associated file is deleted.
When set to Delete File, the database record is deleted along with the associated file.
When set to Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
45
________________
Report Manager User’s Guide - April 2002
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
46
________________ Search Criteria Data Form
Manager
2.Report
Use this form to create, copy, revise, or delete report search criteria. Search criteria data
determines reduces the amount of data reported by restricting the reporting of certain
attributes. Rather than report all data in a model, search criteria specifications narrow the
report to return only data that matches certain criteria.
You can specify search criteria as you create the discrimination data file; the options on the
Search Criteria Data form create the same data as a separate step. If you specify search
criteria data as you create the discrimination data file and by means of the Report Search
Criteria form, the specifications defined using the Report Search Criteria take precedence
when the report is generated.
Options
Create — Displays the Search Criteria Data Creation form, which adds a new record
of a report search criteria file in the project control database. For more information, see
Search Criteria Data Creation Form, page 49.
Copy — Displays the Search Criteria Data File Revision form, which copies the
record of an existing report search criteria file from the project control database and
copies the corresponding data file. For more information, see Search Criteria Data
Revision Form, page 61.
47
________________
Report Manager User’s Guide - April 2002
Delete — Displays the Deletion form, which deletes an existing report search criteria
data file as well as its associated record in the project control database. For more
information, see Search Criteria Deletion Form, page 63.
48
________________ Search Criteria Data Creation Form
Manager
2.Report
This form creates a report search criteria data file in a specified directory. It also creates a
corresponding record in the project control database.
If you specify search criteria using both this form and the search criteria
options when you create the discrimination data, the search criteria specified
on this form (Search Criteria Data Creation) takes precendence.
File Specification — The file name (up to 14 characters) of the search criteria data file
to be created.
File Path — The disk location of the search criteria data file. This field retains the
active settings.
49
________________
Report Manager User’s Guide - April 2002
File Node — The nodename of the system on which the search criteria data file is
located. This field retains the active settings.
Segment Search Criteria — Displays the Search Criteria form, which defines the
segment search criteria for the report. For more information, see Search Criteria -
Piping Segment Form, page 52.
Use this list to change the And/Or relationships between piping segment search criteria
(table 12, piping segment data) and the search criteria for the component data in table
34, piping component data; table 50, piping/tubing data; table 67, instrument
component data; and table 80, pipe support data.
Each category of component search criteria data is related to the piping segment search
criteria by a logical AND or a logical OR. By default, the logical relationship between
the piping segment search criteria and the four categories of component search criteria
is AND. This means that only components that meet the criteria defined for both sets of
criteria are reported.
Setting this relationship to OR increases the amount of data reported in that all
components that match either set of criteria are reported.
Operating Sequence
1. From the Search Criteria Data form, click Create
In the fields provided, key in the number, description, and file specification, path, and
node.
3. Select additional options as needed to define the report discrimination data. Then click
Accept.
50
________________ Search Criteria Data Creation Form
After including any models or search criteria for the search criteria data file,
be sure to click the final Accept. Because you must accept many forms while
specifying the discrimination data, it is easy to forget this step. Even though
you may have accepted many of the specifications, however, the search
criteria data file is not actually created until you click Accept on the Search
Criteria Data Creation form.
Manager
2.Report
51
________________
Report Manager User’s Guide - April 2002
This form specifies which segment attributes are to be reported on. The most commonly
reported attributes are available as form options, but you are not restricted to those options.
To display all available attributes, click Other.
52
________________ Search Criteria - Piping Segment Form
Manager
2.Report
When you select an attribute, applicable operator options are displayed along the bottom of
the form.
The combination of these operators with either attribute values or (where applicable) code list
values enables you to fully specify an attribute restriction (for example, fluid code = AC).
You can combine these specifications as needed using the And and Or options, which are
displayed in place of the operator options after you have defined a segment attribute
restriction.
When you select a code-listed attribute, the Review Standard Notes form is
displayed. This form provides a list of valid codes for the specified attribute.
Simply select a code from the list and click Accept to continue with the
specification.
When you are using this form to copy and/or revise an existing discrimination data file,
additional options are provided for you to insert, remove, or clear search criteria
specifications.
53
________________
Report Manager User’s Guide - April 2002
Unit Number — Restricts the reported segments by means of the unit number attribute.
Select an operator and key in an attribute value to complete the specification.
Fluid Code — Restricts the reported segments by means of the fluid code attribute.
Select an operator and a code list value to complete the specification.
Unit Code — Restricts the reported segments by means of the unit code attribute.
Select an operator and key in an attribute value to complete the specification.
Line Sequence Number — Restricts the reported segments by means of the line
sequence number attribute. Select an operator and key in an attribute value to complete
the specification.
Nominal Piping Diameter — Restricts the reported segments by means of the nominal
piping diameter attribute. Select an operator and key in an attribute value to complete
the specification.
Piping Materials Class — Restricts the reported segments by means of the piping
materials class attribute. Select an operator and key in an attribute value to complete
the specification.
Line ID — Restricts the reported segments by means of the line ID attribute. Select an
operator and key in an attribute value to complete the specification.
Heat Tracing Requirement — Restricts the reported segments by means of the heat
tracing requirement attribute. Select an operator and a code list value to complete the
specification.
Train Number — Restricts the reported segments by means of the train number
attribute. Select an operator and key in an attribute value to complete the specification.
Approval Status — Restricts the reported segments by means of the approval status
attribute. Select an operator and a code list value to complete the specification.
54
________________ Search Criteria - Piping Segment Form
Insert Search Definition — Displays the And and Or options to add search criteria to
the specification.
Remove Search Definition — Removes a selected line from the defined search criteria.
To remove a line, click Remove Search Definition, select the line to be removed, and
click Accept.
Clear Search Criteria — Removes the complete search criteria specification. Select
this option and click Accept to remove the defined set of search criteria.
Operating Sequence
Manager
2.Report
1. Select Segment Search Criteria.
2. Select Attribute
3. Select Operator
4. For code-listed attributes, select a value from the displayed list and click Accept. For
all other attributes, type an attribute value in the available field.
5. Use the And and Or options to specify additional restrictions as needed. Then click
Accept.
55
________________
Report Manager User’s Guide - April 2002
This form specifies which component attributes are restricted for the report. The default is no
search criteria (that is, no restrictions — all component attributes are reported). The most
commonly reported component attributes are available as form options, but you are not
restricted to those options. To display additional attributes, grouped by entity, click Other.
56
________________ Search Criteria - Component Form
Manager
2.Report
Define all the common search criteria such as Commodity Code and
Fabrication Category before selecting the Other option. Once the Other
option is selected, the search criteria should be defined separately for each
category, such as Piping Component, Instrument Component,
Piping/Tubing and Pipe Support.
When you select an attribute, applicable operator options are displayed along the bottom of
the form.
The combination of these operators with either attribute values or (where applicable) code list
values enables you to fully specify an attribute restriction (for example, fluid code = AC).
You can combine these specifications as needed using the And and Or options, which are
displayed in place of the operator options after you have defined a segment attribute
restriction.
When you select an entity grouping that includes the attribute you want to restrict, a list of
associated attributes is displayed.
57
________________
Report Manager User’s Guide - April 2002
When you select a code-listed attribute, the Review Standard Notes form is
displayed. This form provides a list of valid codes for the specified attribute.
Simply select a code from the list and click Accept to continue with the
specification.
When you are using this form to copy and/or revise an existing discrimination data file,
additional options are provided for you to insert, remove, or clear search criteria
specifications.
58
________________ Search Criteria - Component Form
Manager
2.Report
that are associated with piping or tubing components. From the displayed list, select an
attribute. Then select an operator and either key in an attribute value or select a code
list value to complete the specification.
Pipe Support — Restricts the reported components by means of any of the attributes
that are associated with pipe support attributes. From the displayed list, select an
attribute. Then select an operator and either key in an attribute value or select a code
list value to complete the specification.
Insert Search Definition — Displays the And and Or options to add search criteria to
the specification.
Remove Search Definition — Removes a selected line from the defined search criteria.
To remove a line, click Remove Search Definition, select the line to be removed, and
click Accept.
Clear Search Criteria — Removes the complete search criteria specification. Select
this option and click Accept to remove the defined set of search criteria.
Operating Sequence
1. Select Component Search Criteria.
2. Select Attribute
3. Select Operator
59
________________
Report Manager User’s Guide - April 2002
4. For code-listed attributes, select a value from the displayed list and click Accept. For
all other attributes, type an attribute value in the available field.
5. Use the And and Or options to specify additional restrictions as needed. Then click
Accept.
60
________________ Search Criteria Data Revision Form
Manager
2.Report
This form revises an existing search criteria data file. It also copies an existing search criteria
data file; you can then use the revision options to modify the copy as needed. The
corresponding records in the project control database are copied and/or modified as needed.
File Specification — The file name, up to 14 characters, of the search criteria file to be
created.
File Path — The disk location of the search criteria data file. This field retains the
active settings.
Segment Search Criteria — Displays the Search Criteria form, which defines the
segment search criteria for the report. For more information, see Search Criteria -
Piping Segment Form, page 52.
61
________________
Report Manager User’s Guide - April 2002
Define Volume — Displays the Volume Definition form, which specifies the
coordinates of a design volume cube for reporting. For more information, see Define
Volume Form.
Use this list to change the And/Or relationships between piping segment search criteria
(table 12, piping segment data) and the search criteria for the component data in table
34, piping component data; table 50, piping/tubing data; table 67, instrument
component data; and table 80, pipe support data.
Each category of component search criteria data is related to the piping segment search
criteria by a logical AND or a logical OR. By default, the logical relationship between
the piping segment search criteria and the four categories of component search criteria
is AND. This means that only components that meet the criteria defined for both sets of
criteria are reported.
Setting this relationship to OR increases the amount of data reported in that all
components that match either set of criteria are reported.
Operating Sequence
1. From the Report Search Criteria form, select Copy or Revise.
The Search Criteria Data File Revision form is displayed, with a list of available data
files.
2. From the displayed list, select a data file to be copied or revised. Then click Accept.
In the fields provided, key in the number, description, and file specification, path, and
node.
4. Select additional options as needed to define the report search criteria data. Then click
Accept.
62
________________ Search Criteria Deletion Form
Manager
2.Report
This form deletes a report record from the project control database and can optionally delete
the associated file. This form is used with format files and their database records,
discrimination data files and their database records, and search criteria files and their database
records.
Delete File/Do Not Delete File — Determines whether the associated file is deleted.
When set to Delete File, the database record is deleted along with the associated file.
When set to Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
63
________________
Report Manager User’s Guide - April 2002
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
64
________________ Report Form
Manager
2.Report
This form creates, revises, and deletes report records and report files. A report record holds
specifications for a report; these specifications include the report name, the report description,
and which format file, discrimination data file, and search criteria data file to use to generate a
report.
The report name is not the title that is printed on the report; the title is included
in the format file.
At the end of each report, a parameters page is included that contains the following
information:
Report Output — The report number, report title, report creation/revision date, and
report node, path, and file name.
Format — The report format number, description, and node, path, and file name.
Discrimination Data — The report discrimination data number, description, and file
location (network address, path, and file name). The following discrimination data is
also included: list of model numbers (with discipline), volume (if applicable), search
criteria (if applicable), and sorting sequence.
Search Criteria — The report search criteria number, description, and file location
(node, path, and file name. The following search criteria data is also included: list of
model numbers (with discipline), volume (if applicable), search criteria (if applicable),
and sorting sequence.
65
________________
Report Manager User’s Guide - April 2002
Options
Create — Displays the Report Creation form, which creates a report record and
generates a report. For more information, see Report Creation Form, page 67.
Revise — Displays the Revise Report form, which regenerates a report from an
existing or revised report record. For more information, see Revise Report Form, page
70.
Delete — Displays the Deletion form, which deletes an existing report record and the
corresponding report. For more information, see Report Deletion Form, page 73.
Approve — Displays the Report Approval form, which approves an existing report.
For more information, see Report Approval Form, page 75.
Multi-Create — Displays the Report Multiple Submit form, which submits multiple
reports to the printer. For more information, see Report Multiple Submit Form, page
78.
66
________________ Report Creation Form
Manager
2.Report
Use this form to create a report record and to generate a report. Because report records are
stored in the project control database, you can use them over and over again as needed.
Report Title — The 40-character descriptive name of the report file. This is not the
title in the actual report, but is rather the title of the report record. The title of the report
is contained in the format file.
Report File Spec — The name of the report output file (up to 14 characters).
Report File Path — The disk location for the report output file. This field retains the
active settings, and it is automatically populated if you have specified this data on the
Report Management Dataform. For more information, see Report Management
Defaults Form, page 80.
Report Node — The name of the system on which the report output file will be
located. This field retains the active settings, and it is automatically populated if you
have specified this data on the Report Management Data form. For more information,
see Report Management Defaults Form, page 80.
67
________________
Report Manager User’s Guide - April 2002
Report Format File — The name of the format file to be used to generate the active
report. When you select this field, a list of available format files is displayed. Select
the appropriate format file, and click Accept.
Report Discrimination File — The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination
data files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria — The name of the search criteria data file to be used to
generate the active report. When you select this field, a list of available search criteria
files is displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search
criteria data defined within it, and you specify a search criteria in this
field, the search criteria specified in the Report Search Criteria field
takes precedence over the search criteria contained in the discrimination
data.
Revision Number – The revision number (up to three characters) for the report.
Last Revision Number — The revision number of the last report generated. This is a
read-only field; you cannot edit it.
Revised By — The user (up to five characters) who checked the report. This field is
optional.
Print/Delete — Submits the report output file to the specified print queue and then
deletes the report output file. When you select this option, a list of available print
queues is displayed. Click on a queue to select it.
Print/Save — Submits the report output file to the specified print queue and saves the
report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Save — Saves the report output file without printing the report.
68
________________ Report Creation Form
Operating Sequence
1. From the Report form, select Create.
Key in the report record information. Then select the appropriate report format file,
discrimination data file, and search criteria data file.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
Manager
2.Report
printed.
69
________________
Report Manager User’s Guide - April 2002
This form revises an existing report record and generates a report from the project control
database. An option is also provided to update (in some cases) the report record without
generating a report output file. Similarly, you can choose to generate an updated report output
file without updating the report record.
Report Title — The 40-character descriptive name of the report file. This is not the
title in the actual report, but is rather the title of the report record. The title of the report
is contained in the format file.
Report File Spec — The name of the report output file (up to 14 characters).
Report File Path — The disk location for the report output file. This field retains the
active settings.
Report Node — The name of the system on which the report output file will be
located. This field retains the active settings.
70
________________ Revise Report Form
Report Format File — The name of the format file to be used to generate the active
report. When you select this field, a list of available format files is displayed. Select
the appropriate format file, and click Accept.
Report Discrimination File — The name of the discrimination data file to be used to
generate the active report. When you select this field, a list of available discrimination
data files is displayed. Select the appropriate discrimination data file, and click Accept.
Report Search Criteria — The name of the search criteria data file to be used to
generate the active report. When you select this field, a list of available search criteria
files is displayed. Select a search criteria file, and click Accept.
Select this field a second time to specify a different search criteria file. To clear a
Manager
2.Report
specification, click Accept without selecting a file.
If the report discrimination data selected for the active report has search
criteria data defined within it, and you specify a search criteria in this
field, the search criteria specified in the Report Search Criteria field
takes precedence over the search criteria contained in the discrimination
data.
Revision Number – The revision number (up to three characters) for the report.
Last Revision Number — The revision number of the last report generated. This is a
read-only field; you cannot edit it.
Revised By — The user (up to five characters) who checked the report. This field is
optional.
Print/Delete — Submits the report output file to the specified print queue and then
deletes the report output file. When you select this option, a list of available print
queues is displayed. Click on a queue to select it.
Print/Save — Submits the report output file to the specified print queue and saves the
report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Save — Saves the report output file without printing the report.
Revise Data Only/Revise Report and Data — Specifies revision of the report data
only (Revise Data Only) or revision of the report data and the report output file (Revise
Report and Data). To revise the report specification without updating the report
output file, make the necessary changes, set this toggle to Revise Data Only, and click
Accept. To revise the report output file only, set this toggle to Revise Report and
Data without modifying any of the fields, and click Accept. To modify both the report
71
________________
Report Manager User’s Guide - April 2002
file and the report output file, make the necessary changes, set this toggle to Revise
Data Only, and click Accept.
If you update any field other than Report Number and Report Title,
this toggle is automatically set to Revise Report and Data, and the
report output file is generated.
Operating Sequence
1. From the Report form, select Revise.
The Report Creation form is displayed with a list of available report files.
2. Select Report
From the displayed list, select the report to be revised. Then click Accept.
4. Select the appropriate print/save/delete option, and select a queue if the report is to be
printed.
72
________________ Report Deletion Form
Manager
2.Report
This form deletes a report record from the project control database and can optionally delete
the associated file. This form is used with format files and their database records,
discrimination data files and their database records, and search criteria files and their database
records.
Delete File/Do Not Delete File — Determines whether the associated file is deleted.
When set to Delete File, the database record is deleted along with the associated file.
When set to Do Not Delete File, only the database record is deleted.
Operating Sequence
1. Select Report Format
73
________________
Report Manager User’s Guide - April 2002
2. Set the Delete File/Do Not Delete File toggle as needed. Then click Accept.
The specified record is deleted. If specified, the associated file is also deleted.
74
________________ Report Approval Form
Manager
2.Report
Use this form to select a report to approve. Approving a report means that a database attribute
is set from not approved (the default) to approved. This approval status provides a way for
you to flag reports that you have run and verified that the output data is valid. When a report
is revised, the approval status is automatically reset to not approved.
Options
Number — The 24-character unique name (as called short name) of the report record.
Operating Sequence
1. From the Report form, select Approve.
2. From the displayed list, select a report to approve. Then click Accept. The Approval
form is displayed. For more information, see Approval/Revision Interface Form, page
76.
75
________________
Report Manager User’s Guide - April 2002
The first time a report is approved, only the Approved By field is active. All other fields are
purely informational. The data displayed in these fields is read from the Revise Report form.
Approved By — The initials (up to five characters) of the person who approved the
report.
Revision Number – The revision number (up to three characters) for the report. This
field is read-only; you cannot edit it.
Revised By — The initials (up to five characters) of the person who last revised the
report. This field is read-only; you cannot edit it.
76
________________ Approval/Revision Interface Form
Checked By — The initials (up to five characters) of the person who ran the report with
the revised information. This field is read-only; you cannot edit it.
Operating Sequence
1. On the Report Approval form, click Accept.
Manager
2.Report
2. Specify Approval/Revision Data
77
________________
Report Manager User’s Guide - April 2002
Print/Delete — Submits the report output file to the specified print queue and then
deletes the report output file. When you select this option, a list of available print
queues is displayed. Click on a queue to select it.
Print/Save — Submits the report output file to the specified print queue and saves the
report output file. When you select this option, a list of available print queues is
displayed. Click on a queue to select it.
Save — Saves the report output file without printing the report.
78
________________ Report Multiple Submit Form
Operating Sequence
1. From the Report form, select Multi-Create.
From the displayed list, select the reports to submit. Highlighed reports are selected;
select a highlighted report to remove the highlight and to not submit the report.
3. Select the appropriate print/save/delete option, and select a queue if the report is to be
Manager
2.Report
printed.
79
________________
Report Manager User’s Guide - April 2002
This form creates a record in the project control database of the node name and path of the
report definition files. This option is used primarily for setup.
Fields
Report Path — Specifies the default path of the report output files.
Report Node — Specifies the default node name of the system on which report output
files are located.
Report Format Path — Specifies the default path of the format files.
Report Format Node — Specifies the default node name of the system on which
format files are located.
Report Discrimination Data Path — Specifies the default path of the discrimination
data files.
80
________________ Report Management Defaults Form
Report Discrimination Data Node — Specifies the default node name of the system
on which discrimination data files are located.
Report Search Criteria Data Path — Specifies the default path of the report search
criteria data files.
Report Search Criteria Data Node — Specifies the default node name of the system
on which report search criteria data files are located.
Operating Sequence
1. From the Report Manager form, select Report Management Data.
Manager
2.Report
The Report Management Defaults form is displayed.
2. Accept or Exit
In the fields provided, key in the default paths and node names for the report output
files, format files, discrimination data files, and search criteria data files. Then click
Accept.
81
________________
Report Manager User’s Guide - April 2002
82
________________ Report Format File
The format file is a standard ASCII file that contains all of the needed criteria for creating the
actual report, such as text position, special indices for input into the report, and sorting
instructions for the indices. In short, the format file specifies what the final report output will
look like.
Formats
3. Report
83
________________
Report Manager User’s Guide - April 2002
Each line of the format file contains the entire description of one field. All fields are
independent of each other; if they have a common order in the report, you are responsible for
placing these fields in such a way that the orders match in the report. In other words, you are
responsible for defining your format file in such a way that your columns and headings will
fall under one another.
Each line in the format file can contain the following data. (Brackets [ ] indicate data that is
only used for certain field types; all other data is required in every field type.)
Field_Function,Row,Col,Field_Len,Data_Type,Field_Type,[Buffer],[Rows/Page],[Spacing]
Syntax Example
It is not possible to return an attribute twice in a report by repeating the line that returns the
attribute. For example, the following syntax in a format file will print the fluid code only
once.
4,2,3,3,1,2,AH9
4,2,8,3,1,2,AH9
84
________________ Format File Syntax - Definitions
Field_Function
0 — Null Field. Used to send a data field (index) to sort on an unreported item.
1 — Page Field - All Pages. Places the specified field once on every page of the report.
2 — Page Field - First Page Only. Places the specified field once on the first page of
the report.
3 — Page Field - Last Page Only. Places the specified field once on the last page of
the report.
4 — Output Field. Places the specified field a variable number of times on every page
of the report based on rows/page and spacing.
5 — New Page Marker. Forces a new page (form feed) after all the previous
statements have been processed. All the lines in the format file after this marker are
placed on a new (repeated) page. In other words, this enables you to append a complete
Formats
3. Report
format file to the previous format file and use the same data sources and sorting as the
previous lines of the format file.
6 — Continuous Page Marker. Forces everything after this marker in the format file up
to a New Page Marker or the end of file to be continuously output as one page. The
specified fields are continuously output without any page divisions. (This code
overrides the value for Rows/Page)
This function can be used to generate an intermediate data file in a fixed form that
contains only raw data (without headings and other annotation). This output can then
be used as input to your own report generation software.
7 — Turn On Output Field Appending Control. Forces all output fields after this
marker in the format file to begin after the previous output field (above 7) is completed.
That is, all output fields will initially begin at the last output field’s finishing row.
8 — Turn Off Output Field Appending Control. If 7 is in effect for an output field, this
code will turn the effect off, making output fields normal.
10 — End of output field loop. Repeats all output fields defined between codes 9 and
10 until out of data or the maximum number of lines per output field has been exceeded
by the number of lines of data between the 9 and 10 codes. These options are used to
prevent control sorts from breaking to a new page by using the remaining space on the
page before proceeding to a new page.
85
________________
Report Manager User’s Guide - April 2002
Row
Starting line number to be used in placing the field in the report. The maximum number of
rows in a report is 66.
Col
Starting column number to be used in placing the field within the specified row. The
maximum number of columns in a report is 132.
Field_Len
The maximum number of characters that a field can occupy for the active row. The starting
column plus the field length must not exceed 132. A negative value will truncate a field
rather than wrap around a field (default). If the text being placed in the field exceeds the field
length, the text is continued on the next row indented one space (col + 1) until it is completed
or the page ends.
Data_Type
Code used to determine the type of translation required to convert the data to text. (Refer to
the index listings to determine the applicable data type for a particular attribute.)
3 — Double precision integer or ’[Im]’, where m is the number of characters for the
integer field
Optional text can precede and/or follow the formatted data type within the quotation marks.
[Format] can be any legal FORTRAN format statement that matches an expected output.
86
________________ Format File Syntax - Definitions
Field_Type
1 Text Field. Sets the buffer for hard-coded text.
2 Data Field. Sets the buffer for an index number or code used to generate the data to
be placed in the field.
3 Generate Date/Time. No buffer required. When the report is generated, the system
date and time is placed at the designated row/col position.
4 Generate Page Number. No buffer required. When the report is generated, the
system calculates the page number and places the number at the designated row/col
position.
5 Generate Date. No buffer required. When the report is generated, the system date is
placed at the designated row/col position.
A negative value will underline the generated output for the field. (This causes the report to
be in a stream line feed file, rather than a stream carriage return file. This may impact an
existing interface to a material control system.)
Formats
3. Report
[Buffer] = Field Definition
The form of the buffer is dependent on the value for Field_Type.
For MTO reporting, the first character of the index is always A or B. For a description
of the indices, see Indices for MTO Reporting (With Implied Items), page 91.
For spec reporting, the first character of the index is always C. For a description of the
indices, see Indices for Spec Reporting, page 113. These indices are also used for the
Table Checker.
For project and interference reporting, the first character of the index is always D. For a
description of the indices, see Indices for Project and Interference Reporting, page 122.
[Rows/Page]
This setting is only required for output fields. It indicates the number of vertical spaces
(lines) in which to repeat the field contents on a given page. For example, a setting of 20
reserves 20 lines starting from a given row for use in placing the field contents (dependent on
spacing).
This does not take into account the extended fields due to exceeded field length.
87
________________
Report Manager User’s Guide - April 2002
This is not the total number of times that the field is repeated (that value is based on number
of occurrences for the specified attribute); it is only the vertical space allotted for repeating the
field on a page.
[Spacing]
This setting is only required for output fields. It indicates how much space (in rows) is
allowable between repeated fields. This is useful for reserving space for extended fields due
to exceeded field length.
(Rows/Page)/Spacing = the number of times an output field can appear on a page. For
example, if Rows/Page=40 and Spacing = 2, 20 occurrences of the specified attribute are
placed on a page (until the number of occurrences is reached).
1,8,1,-25,1,-1,!’Commodity Code’
1,8,27,-16,1,-1,!’Qty/Length’
or
2,3,10,-40,1,1,’!!Corporate Headquarters!!’
88
________________ Optional Report Type Line
report_type=689
Formats
3. Report
89
________________
Report Manager User’s Guide - April 2002
Each field is processed independently of the other fields on the report; there are no safeguards
to assure that information in different fields corresponds to the same item. Therefore, you are
responsible for placing these fields in such a way that the orders match in the report. To
ensure that items match, make sure that the same number of common items are reported on
each page. The Rows/Page divided by the Spacing determines the number of times an output
field can appear on a page. Therefore, all the common fields should use identical settings for
Rows/Page and Spacing.
The Spacing enables you to reserve space for extended fields due to exceeded field length.
For example, if you use a Field length of 20 for a field which may be up to 50 characters long,
you should set the spacing at 3 to leave adequate space for any extended fields.
If there is no data for the specified output field(s) on a page, that page will not
be printed.
90
________________ Indices for MTO Reporting (With Implied Items)
For MTO reporting, the first character of the index is either A,B, or E. This character is
followed by one or more characters that specify the type of data to be reported. The following
listing identifies the index structure. The following conventions are used in this listing:
The indices are divided into groups for reporting such as piping, components, and
segments.
A one-, two-, or three-character code (A, B, C, ... *A, *B, *C, ... **A, **B, ... )
indicates the specific group.
Formats
3. Report
n indicates an option number (such as 0)
For codes that designate a database table, refer to the list of Database Table/Column
values in Database Table/Column Information for Reporting, page 184.
The attribute type indicates the form of the information: Character indicates
character data, integer and short indicate integer values, and double
indicates a floating point value.
Codes integer, double, and short are reported as blank if their values are less than
-32767.
Any code list value = 0 is reported as a dash and not logged as an error; any undefined
code list value is reported as blank and logged as an error.
(SN499) indicates a standard note. Only the index number of the note (within standard
note 499) is reported unless option Z1 is used.
91
________________
Report Manager User’s Guide - April 2002
92
________________ MTO Indices for Piping Segments
Formats
3. Report
8 translate specific standard note type,
followed by standard note type - cancels option AZ7 ........ N/A
9 cancel options AZ7 and AZ8 .................................. N/A
10 report insulation thickness without units ....................N/A
12 store the insulation units for the segment used in forming....N/A
and interpreting the insulation thickness value
93
________________
Report Manager User’s Guide - April 2002
94
________________ MTO Indices for Piping Components
Formats
3. Report
8 x coordinate - Center of gravity (dry) .......................1
9 y coordinate - Center of gravity (dry) .......................1
10 z coordinate - Center of gravity (dry) .......................1
11 x coordinate - Center of gravity (wet) .......................1
12 y coordinate - Center of gravity (wet) .......................1
13 z coordinate - Center of gravity (wet) .......................1
14 P&ID Number (after P&I data transfer) character(24) ..........1
15 Model Number from Table 113 character(10) ..........1
1150- MTO labels from Label Description Library ...................1
2149
95
________________
Report Manager User’s Guide - April 2002
96
________________ MTO Indices for Implied Material
Formats
3. Report
2149
BX# = Bolts
1 line number label ...........................................1
2 piping material class .......................................1
3 number of bolts .............................................2
4 bolt diameter ................................................1
5 bolt length .................................................1
6 number of nuts ..............................................1
7 commodity name ..............................................1
8 bolt option .................................................1
9 material grade ..............................................1
12 commodity code ..............................................1
17 fabrication category ........................................1
18 standard note ’A’ ...........................................2 or 1
19 standard note ’B’ ...........................................2 or 1
20 short material description ..................................1
21 long material description ...................................1
22 total bolt weight (bolts, nuts, washers, etc.) ...............5
23 x coordinate - center of gravity location of set of bolts ...1
24 y coordinate - center of gravity location of set of bolts ...1
25 z coordinate - center of gravity location of set of bolts ...1
26 Line ID .....................................................1
27 P&ID Number (after P&I data transfer) character(24) ..........1
28 Model Number from Table 113 character(10) ..........1
1150- MTO labels from Label Description Library ...................1
2149
97
________________
Report Manager User’s Guide - April 2002
98
________________ MTO Indices for Instrument Components
Formats
3. Report
12 z coordinate - ’wet’ center of gravity location ............1
14 P&ID Number (after P&I data transfer) character(24) .........1
15 Model Number from Table 113 character(10) .........1
1150- MTO labels from Label Description Library ..................1
2149
99
________________
Report Manager User’s Guide - April 2002
100
________________ MTO Indices for Special Options
Formats
3. Report
101
________________
Report Manager User’s Guide - April 2002
102
________________ MTO Indices for Equipment
Formats
3. Report
8 oper_weight_1 double .................................5
9 oper_weight_2 double .................................5
10 insulation_thk double .................................5
11 construction_stat short (SN130) ...............1
12 equipment_division short (SN69) ...............1
13 approval_status short (SN35) ...............1
103
________________
Report Manager User’s Guide - April 2002
104
________________ Global Data
Formats
3. Report
15 x coordinate - ’wet b’ center of gravity location ..........1
16 y coordinate - ’wet b’ center of gravity location ..........1
17 z coordinate - ’wet b’ center of gravity location ..........1
18 x coordinate - ’wet c’ center of gravity location ..........1
19 y coordinate - ’wet c’ center of gravity location ..........1
20 z coordinate - ’wet c’ center of gravity location ..........1
21 total surface area of reported system ......................5
22 total line segment length of reported system ...............1
105
________________
Report Manager User’s Guide - April 2002
106
________________ Induction Bends
Formats
3. Report
B**Wx = Quantity for Induction Bends .................................2
(P = page total; T = grand total)
107
________________
Report Manager User’s Guide - April 2002
Special consideration must be made at the end of a pipeline to check if nozzles exist and generate
mating implied material.
If commodity codes and material descriptions are not reported and chain wheels are present, the
reported quantity of implied components will not be correct.
When reporting on pipe length, for sorting to be effective, you must sort all the items reported in
pipes with length as the last sort criteria. If length is sorted first, no summation or partial
summation may occur.
MTO Labels never wrap around; they are always based on field length. MTO Labels with
multiple lines translate into one line.
For more information on format files, see Sample Format Files and Output, page 257
108
________________ Report Management Data
1,8,1,-25,1,-1,’Commodity Code’
1,8,27,-16,1,-1,’Qty/Length’
1,8,45,-10,1,-1,’1st Size’
1,8,57,-10,1,-1,’2nd Size’
1,8,69,-63,1,-1,’Material Description’
9
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BI2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BB2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BT1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BX1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B**K2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*S2G1,45,2
8
4,12,1,-25,1,2,BG8S2,45,2
4,12,27,-16,2,2,BS,45,2
4,12,45,-10,1,2,BN49S3,45,2
4,12,57,-10,1,2,BN-49S4,45,2
4,12,69,63,1,2,BM1S5,45,2
7
Formats
3. Report
4,12,1,-25,1,2,BA12S2,45,2
4,12,27,-16,1,2,BA22,45,2
4,12,45,-10,1,2,BA7S3,45,2
4,12,69,63,1,2,BF1S4,45,2
7
4,12,1,-25,1,2,B*G2S2,45,2
4,12,27,-16,2,2,B*O,45,2
4,12,45,-10,1,2,B*L55S3,45,2
4,12,57,-10,1,2,B*L-55S4,45,2
4,12,69,63,1,2,B*K1S5,45,2
7
4,12,1,-25,1,2,BT13S2,45,2
4,12,27,-16,2,2,BV,45,2
4,12,45,-10,1,2,BT2S3,45,2
4,12,57,-10,1,2,BT23,45,2
4,12,69,63,1,2,BT21S4,45,2
7
4,12,1,-25,1,2,BX12S2,45,2
4,12,27,-16,2,2,BZ,45,2
4,12,45,-10,1,2,BX4S3,45,2
4,12,57,-10,1,2,BX5S4,45,2
4,12,69,63,1,2,BX20S5,45,2
7
4,12,1,-25,1,2,B**J7S2,45,2
4,12,27,-16,1,2,B**O,45,2
4,12,69,63,1,2,B**M1S3,45,2
7
4,12,1,-25,1,2,B*P12S2,45,2
4,12,27,-16,2,2,B*R,45,2
4,12,45,-10,1,2,B*S11S3,45,2
4,12,69,63,1,2,B*U1S4,45,2
10
109
________________
Report Manager User’s Guide - April 2002
5
1,3,1,-13,1,1,’Date/Time :’
1,3,14,-23,1,5
1,3,50,-40,1,1,’PDS MTO REPORT’
1,3,120,-6,1,1,’Page: ’
1,3,127,-3,2,4
1,11,1,-34,1,-1,’GRAND TOTALS’
1,13,1,-15,1,-1,’Components’
1,13,20,-15,1,-1,’Pipes’
1,13,40,-15,1,-1,’Instruments’
1,13,60,-15,1,-1,’Gaskets’
1,13,80,-15,1,-1,’Bolts’
1,13,100,-15,1,-1,’Pipe Supports’
1,14,1,-15,2,2,BST
1,14,20,-15,2,2,BRT
1,14,40,-15,2,2,B*OT
1,14,60,-15,2,2,BVT
1,14,80,-15,2,2,BZT
1,14,100,-15,2,2,B*RT
110
________________ Sample MTO Report Format Files
For more information on format files, see Sample Format Files and Output, page 257
segment.fmt — This report format will include piping segment data. It demonstrates ’control’ sorting and
output field ’looping’ (field functions 9 and 10).
This report format will report a list of piping segments grouped by the Model Builder’s alphanumeric
description id. The report will include all piping lines that are associated with a specific Model Builder
alphanumeric input file.
piping_a.fmt — This report format will include data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the use of standard output fields.
This report will include each category of data in a fixed area of a repeated report page using normal
Formats
3. Report
sorting and standard output fields (field function 4).
piping_b.fmt — This report format will include data for piping components, pipes, instrument
components, gaskets, bolts, nuts, and welds. It demonstrates the technique for grouping blocks of output
fields on the same page of the report.
This report format will report data similar to piping_a.fmt. It differs only in that it demonstrates another
method to format the data on the repeated page of the report.
piping_c.fmt — This report format will include data for piping components, pipes, instrument
components, gaskets, bolts, nuts, welds, pipe supports, implied piping components, equipment, and
nozzles. It demonstrates the use of different pages of output within one report.
This report format will report data similar to piping_b.fmt with the addition of pipe_supports, implied
piping components, equipment, and nozzles. It will use page break markers (field function 5) to break
each category of data onto a different repeated page of the report.
piping_d.fmt — This report format will report the material descriptions for piping components, pipes,
instrument components, pipe supports, gaskets, and bolts.
This report format will use identical report indices to create two columns to continue data on the same
report page. It will also use page breaks to separate the different categories of data onto different repeated
pages of the report.
111
________________
Report Manager User’s Guide - April 2002
piping_e.fmt — This report format will report data similar to piping_c.fmt, but without any equipment
and nozzle data.
This report format will use a continuous page marker (field function 6) to create a report with no page
boundaries and continuous output (typically used for creating a neutral file format). It also demonstrates
the use of report indices to create a summary of standard notes used in the report.
piping_f.fmt — This report format will include data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to piping_e.fmt.
Each category of data will be grouped (using global control sorting) under a common line number label
for each page of output. It uses ’output field appending’ (field functions 7 and 8) to have the different
categories of data reported on the same page and column of output.
piping_g.fmt — This report format will include data for piping components, pipes, instrument
components, gaskets, bolts, and pipe supports similar to piping_f.fmt with the same line number
grouping.
This report format uses output field looping (field functions 9 and 10) to utilize all of the report page
space available. The report will include a line number followed by all components that are associated with
that line number label with one or more line number labels being reported per page, depending upon the
amount of data and the space available.
weight.fmt — This report format will include weight and center of gravity data for piping components,
pipes, instrument components, gaskets, bolts, pipe supports, implied piping components, and equipment.
The output is similar in format to piping_e.fmt and demonstrates the weight and cog calculation
reporting indices.
equip_a.fmt — This report format will report equipment data (including location data) and nozzle data
(including location and orientation data).
Additional format files and search criteria data files are included as examples for different types of reports.
These files are provided in the ˜/pdreport/rpt directory.
112
________________ Indices for Spec Reporting
Refer to reporting for the Piping Job Specification Manager in the PDS Reference Data (PD_Data) Manager
Reference Guide for more information on Spec Reporting. For spec reporting, the first character of the index is
always C. This character is followed by one or more characters which specify the type of data to be reported.
The following listing identifies the index structure. The following conventions are used in this listing.
A one- or two-character code (A, B, C, ... YB, YC, ... ) indicates the specific group.
Formats
3. Report
No. description attribute type Data_Type
code
2 line_number_label character(40) ..................... 1
Character indicates character data, integer and short indicate integer values, and double
indicates a floating point value.
Codes integer, double, and short are reported as blank if their values are less than -32767.
Any codelist value = 0 is reported as a dash and not logged as an error; any undefined codelist value is
reported as blank and logged as an error.
(SN499) indicates a standard note. Only the index number of the note (within standard note 499) is
reported unless option Z1 is used.
113
________________
Report Manager User’s Guide - April 2002
The CFE index must immediately follow the CE index. All values
will pertain to the last reported component by the CE index. The
CFE index will report multiple Eden modules used by the last CE
index output.
114
________________ Indices for Spec Reporting
The CFT index must immediately follow the CE (or CF) index. All
values pertain to the last data reported bt the CE index. For
example, the CE index in the report format should be set to report
one row of data par page, where the CFT index should be set to
report the maximum amount of table data that any one component can
have. The CFT index reports multiple tables used by the last CE
index output.
1 Green Npd(s)
2 Red Npd(s)
3 Green Schedule Thickness(s)
4 Red Schedule Thickness(s)
5 Size Dependent Commodity Code(s)
6 "Unknown" Table Outputs
7 "Generic" Table Outputs
8 "Specific" Table Outputs
9 "Weight" Table Outputs
10 "Spec" Table Outputs
11 "Sub-Component" Table Outputs
12 "Unknown" Table Name(s)
13 "Generic" Table Name(s)
14 "Specific" Table Name(s)
Formats
3. Report
15 "Weight" Table Name(s)
16 "Spec" Table Name(s)
17 "Sub-Component" Table Name(s)
Instrument Data
CG# = Instrument Data Table 204
(followed by column number)
115
________________
Report Manager User’s Guide - April 2002
The CHE report index must immediately follow the CG report index.
All values will pertain to the last component reported by the CG
report index. The CGE report index reports multiple Eden modules
used by the last CG report index output.
The CHT index must immediately follow the CG (or CH) index. All
values pertain to the last data reported by the Cg index. For
example, the CG index in the report format should be set to report
one row of data per page, where the CHT index should be set to
report the maximum amount of table data that any one component can
have. The CHT index reports multiple tables used by the last CE
index output.
1 Green Npd(s)
2 Red Npd(s)
3 Green Schedule Thickness(s)
4 Red Schedule Thickness(s)
5 Size Dependent Commodity Code(s)
6 "Unknown" Table Outputs
7 "Generic" Table Outputs
8 "Specific" Table Outputs
9 "Weight" Table Outputs
10 "Spec" Table Outputs
11 "Sub-Component" Table Outputs
12 "Unknown" Table Name(s)
13 "Generic" Table Name(s)
14 "Specific" Table Name(s)
15 "Weight" Table Name(s)
16 "Spec" Table Name(s)
17 "Sub-Component" Table Name(s)
116
________________ Indices for Spec Reporting
Reporting Options
CZn = Options for reporting Piping Segments
1 translate all standard notes to text
(default = no translation to text)
2 list of standard notes used ........................ 2
3 list of translated standard notes used ............. 1
4 report nominal piping diameter without units
5 cancel option CZ1
6 Site Coordinate System (Default Plant Coordinate System
using coordinate labels)
7 do not translate standard note type - cancels option CZ8
Formats
3. Report
8 translate specific standard note type,
followed by standard note type - cancels option CZ7
9 cancel options CZ7 and CZ8
Table Checker
No Sorting affects these indices; they each use a hard-coded sort.
Options 1-17 are related; they contain data that will line up with each
other in a report, just like all the data in CC (commodity data) is
designed to line up (multiple information on the same item).
1 Green Npd(s)
2 Red Npd(s)
3 Green Schedule Thickness(s)
4 Red Schedule Thickness(s)
5 Size Dependent Commodity Code(s)
6 "Unknown" Table Outputs
117
________________
Report Manager User’s Guide - April 2002
Unlike other MTO indices, options 18-24 do not match up with 1-17, they are
two different sets of data about the same item. The following can be reported
in 3 groups of data (not found data, found data, found calculation data)
For more information on format files, see Sample Format Files and Output, page 257.
118
________________ Indices for Spec Reporting
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Material Class Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
2,3,10,-40,1,1,’Corporate Headquarters’
2,4,10,-40,1,1,’Intergraph Corporation’
2,5,10,-40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,-40,1,1,’(205)730-2000’
2,3,90,-20,1,2,B**Q5
2,3,110,-20,1,2,B**Q9
2,4,90,-20,1,2,B**Q6
2,5,90,-20,1,2,B**Q7
2,6,90,-20,1,2,B**Q8
1,9,1,-10,1,-1,’#’
1,9,15,-10,1,-1,’Class’
1,9,30,-80,1,-1,’Materials Description’
1,8,115,-14,1,-1,’Standard Notes’
1,9,115,-3,1,-1,’A’
1,9,125,-3,1,-1,’B’
4,11,1,-10,2,2,CYB,45,1
4,11,15,-10,1,2,CB2,45,1
4,11,30,-80,1,2,CB9,45,1
4,11,115,-3,2,2,CB19,45,1
4,11,125,-3,2,2,CB20,45,1
Formats
3. Report
1,58,10,-60,1,1,’Piping Material Class Page Total: ’
1,58,71,-4,2,-2,CYBP
3,60,10,-60,1,1,’Piping Material Class Grand Total: ’
3,60,71,-4,2,-2,CYBT
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Commodity Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
1,9,1,-10,1,-1,’Item’
1,9,15,-15,1,-1,’1st Size Low’
1,9,30,-15,1,-1,’1st Size High’
1,9,50,-60,1,-1,’Material Description’
1,8,115,-14,1,-1,’Standard Notes’
1,9,115,-3,1,-1,’A’
1,9,125,-3,1,-1,’B’
4,11,1,-10,1,2,CC3,45,2
4,11,15,-15,1,2,CC6,45,2
4,11,30,-15,1,2,CC7,45,2
4,11,45,-65,1,2,CD1,45,2
4,11,115,-3,2,2,CC26,45,2
4,11,125,-3,2,2,CC27,45,2
119
________________
Report Manager User’s Guide - April 2002
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Tap Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
1,9,1,-16,1,-1,’Tap Diameter’
1,9,20,-100,1,-1,’Tap Description’
4,16,1,-16,1,2,CI3,40,1
4,16,20,100,1,2,CJ1,40,1
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Standard Notes Used in Report’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
4,9,1,-10,1,-1,’Note #’
4,9,20,-110,1,-1,’Standard Note’
4,11,1,-10,2,2,CZ2,40,3
4,11,20,-110,1,2,CZ3,40,3
For more information on format files, see Sample Format Files and Output, page 257.
piping_rdb.fmt — This report format will include piping material class data and piping commodity data
from the Material Reference Database. It will report the partial (without embedded commodity code
labels) material descriptions.
tbl_chk_1.fmt — This report format will include Table Checker data for one piping material class. It will
report the piping commodities with the dimension tables and Piping Eden modules used, including a list
of all entries read in the dimension tables.
This report will also include a list of all dimension tables and Piping Eden modules that were required for
those piping commodities, but not available in the Reference Database.
120
________________ Indices for Spec Reporting
This report format is a combination of the following report formats tbl_chk_2.fmt, tblk_chk_3.fmt, and
tbl_chk_4.fmt. It provides full Table Checker output for a specific piping materials class.
tbl_chk_2.fmt — This report format will include Table Checker data for one piping material class. It will
report the dimension tables and Piping Eden modules used by each piping commodity in that piping
materials class.
tbl_chk_3.fmt — This report format will include Table Checker data for one piping material class. It will
list all entries read in dimension tables.
tbl_chk_4.fmt — This report format will include Table Checker data for one piping material class. It will
include a list of all dimension tables and Piping Eden modules used by the piping commodities in that
piping materials class.
This report will also include a list of all dimension tables and Piping Eden modules that were required for
those piping commodities, but not available in the Reference Database.
Formats
3. Report
(report type = 601)
121
________________
Report Manager User’s Guide - April 2002
Refer to reporting for the Project Control Manager in the PD_Project Administrator Reference
Guide for more information on Project Reporting. Refer to reporting for the Interference
Checker/Manager in the Interference Checker/Manager Reference Guide for more information
on Interference Reporting. Specifically, see Appendix C: Interference Tables to see the tables
that affect Interference Reporting.
For project and interference reporting, the first character of the index is always D. This character is followed by
one or more characters which specify the type of data to be reported. The following listing identifies the index
structure. The following conventions are used in this listing.
A one or two character code (A, B, C, ... YB, YC, ... ) indicates the specific group.
Character indicates character data, integer and short indicate integer values, and double
indicates a floating point value.
Codes integer, double, and short are reported as blank if their values are less than -32767.
Any codelist value = 0 is reported as a dash and not logged as an error; any undefined codelist value is
reported as blank and logged as an error.
(SN499) indicates a standard note. Only the index number of the note (within standard note 499) is
reported unless option Z1 is used.
122
________________ Indices for Project and Interference Reporting
Reporting Options
DZn = Options for Reporting Documents
1 translate all standard notes to text
(default = no translation to text)
Formats
3. Report
2 list of standard notes used ................................ 2
3 list of translated standard notes used ..................... 1
4 report nominal piping diameter without units
5 cancel option DZ1
6 report coordinates in the Site Coordinate System (the default is
the Plant Coordinate System)
7 do not translate specific standard note type - cancels option DZ8
8 translate specific standard note type, followed by standard note
type - cancels option DZ7
9 cancel options DZ7 and DZ8
10 plots clashes as they are being reported during
interference checking or interference reporting. This index
is not used for data reporting.
For example, in the Clash Management Data Table (PDtable_131) column 4 is the unique_sequence_no. A
corresponding column (column 12) exists in the Clash Data Per Project Table (PDtable_132), the
recent_sequence_no. There are typically many rows in the Clash Data Per Project Table that reference each row
of the Clash Management Data Table. Therefore, when formatting data to report from the Clash Data Per
Project Table, you can reference the Clash Management Data Table using column 12, which represents the
relationship. However, if you are formatting data to report from the Clash Management Data Table, you cannot
123
________________
Report Manager User’s Guide - April 2002
reference the Clash Data Per Project Table using column 4, since there would be many rows of the Clash Data
Per Project Table for which column 12 has the same value as column 4 of the Clash Management Data Table.
If you use the Clash Data Per Project reporting indices and reference the Clash Management Data, you can also
access data from tables referenced in the Clash Management Data such as Design Area Data (table 112) by the
area_index_no of the Clash Management Data. You can access table data within table data as far as the related
indices will take you. You are only limited by the supported indices for relational access and the uniqueness of
the index from the table on which you are reporting. All attributes in the project that support this one-way data
access are listed below. The following example describes the construct that is required to include relationships
within the report format.
For instance, DA132#12#5 would build a piece of data for the record concerning table 132 (Clash Data Per
Project). The data accessed would be attribute 12 (recent_sequence_no) which the software recognizes as a
special index attribute pointing to table 131 attribute 4. Since it is followed by another attribute it will scan for
the matching occurrence of table 131 attribute 4 using the value of table 132 attribute 12. If found then it will
access attribute 5 (completion date) of that data occurrence and store it as part of the table 132 data record. If the
attribute 5 has not been part of this index, as in DA132#12, then the index value itself would be reported as in
normal reporting.
DA132#12#3#3 would also build a piece of data for the record concerning table 132 (Clash Data Per Project). In
this case attribute 12 is used to locate the unique occurrence of table 131 attribute 3 which references table 112
attribute 3 which is the area_name used in the running of the interference clash.
124
________________
Indices for Project and Interference Reporting
Formats
3. Report
PDtable_185 (18) PDtable_184 (1)
PDtable_186 (2) PDtable_185 (1)
PDtable_186 (12) PDtable_182 (1)
Interference Data
125
________________
Report Manager User’s Guide - April 2002
For more information on format files, see Sample Format Files and Output, page 257
1,1,1,13,1,1,’Date/Time :’
1,1,14,23,1,3
1,1,50,40,1,1,’ISO REVISION HISTORY REPORT’
1,1,120,6,1,1,’Page: ’
1,1,127,3,2,4
2,3,10,40,1,1,’Corporate Headquarters’
2,4,10,40,1,1,’Intergraph Corporation’
2,5,10,40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,40,1,1,’(205)730-2000’
2,3,70,40,1,2,DA101#2
2,4,70,40,1,2,DA101#3
2,5,70,40,1,2,DA101#4
2,6,70,40,1,2,DA101#5
2,7,70,40,1,2,DA101#6
1,13,5,10,1,-1,’Rev. #’
1,13,15,13,1,-1,’Generated by’
1,13,30,13,1,-1,’Checked by’
1,13,45,13,1,-1,’Approved by’
1,13,60,25,1,-1,’Extraction Date’
1,13,90,40,1,-1,’Description’
9
4,15,25,-25,’[A16] (Line ID’,-2,DA186#2#3C1,45,1
4,15,50,-40,’ with [I2] sheets extracted)’,-2,DA186#10C2,45,1
4,17,5,-10,2,2,DA186#4,45,1
4,17,15,-3,1,2,DA186#5,45,1
4,17,30,-3,1,2,DA186#6,45,1
4,17,45,-3,1,2,DA186#7,45,1
4,17,60,-25,1,2,DA186#8,45,1
4,17,90,-40,1,2,DA186#11,45,1
10
For more information on format files, see Sample Format Files and Output, page 257.
126
________________ Indices for Project and Interference Reporting
If DZ10 is added to an interference format file, clashes will automatically be plotted along with
the report.
1,1,1,13,1,1,’Date/Time :’
1,1,14,23,1,3
1,1,50,40,1,1,’PDS INTERFERENCE CLASH REPORT’
1,1,120,6,1,1,’Page: ’
1,1,127,3,2,4
2,3,10,40,1,1,’Corporate Headquarters’
2,4,10,40,1,1,’Intergraph Corporation’
2,5,10,40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,40,1,1,’(205)730-2000’
2,3,70,40,1,2,DA101#2
2,4,70,40,1,2,DA101#3
2,5,70,40,1,2,DA101#4
2,6,70,40,1,2,DA101#5
2,7,70,40,1,2,DA101#6
1,13,2,20,1,-1,’Clash Type/Status/ID’
Formats
3. Report
4,15,2,-20,1,2,DA132#9S5,45,5
4,16,2,-20,1,2,DA132#2S6,45,5
4,17,2,-20,3,2,DA132#1,45,5
1,13,24,20,1,-1,’Item Name’
4,15,24,-20,1,2,DA132#3#5,45,5
4,16,24,-40,1,2,DA132#3#6,45,5
4,17,24,-20,1,2,DA132#4#5,45,5
4,18,24,-40,1,2,DA132#4#6,45,5
1,13,66,6,1,-1,’Entity’
4,15,66,-6,2,2,DA132#3#2,45,5
4,17,66,-6,2,2,DA132#4#2,45,5
1,13,74,10,1,-1,’Occurrence’
4,15,74,-10,3,2,DA132#3#3,45,5
4,17,74,-10,3,2,DA132#4#3,45,5
For more information on format files, see Sample Format Files and Output, page 257.
127
________________
Report Manager User’s Guide - April 2002
iso_rev.fmt — This format file reports isometric drawing revision management data.
ifc_1.fmt — This format file reports the XYZ volume of the clashing items. It should be used while
reporting on an area and is sorted by Approval Statusl, Clash Type, and Unique Clash ID.
ifc_2.fmt — This format file reports clashing items and should be used to easily compare interference
runs generated from different versions of software. It should be used while reporting on an area and is
sorted by Approval Status, Clash Type, and Unique Clash ID.
ifc_3.fmt This format file reports clashing items. It should be used while reporting on an area and is
sorted by Approval Status, Clash Type, and Unique Clash ID.
128
________________ Sorting
3.7 Sorting
The format file also contains information used to sort attribute data within the report. You can add a two
character suffix to the index to indicate the sorting requirements.
— C for a control sort (Maximum of 10 per item in the format file - counting each global sort in that
item as a control sort)
— G for a global sort (Maximum of 10 types and 10 per type allowed in the format file - total)
The second character indicates the order of the sort: 1 for primary, 2 for secondary, n for nth level sort.
A positive value indicates an ascending sort (smallest to largest). A negative value indicates a descending
sort (largest to smallest).
Formats
3. Report
The sorting suffix enables you to specify the order in which information is presented on the report. For
example, you can report components by decreasing line size (NPD Green), by component (Item Name), within
Piping Materials class. In this example, PMC is S1, Item Name is S2, and NPD Green is S-3.
If no sort suffix is assigned to an index item, the item will appear in the order of its appearance in the (unsorted
indices) format file.
Control Sorts
A control sort specifies a page break each time the value for a specified variable changes, with the exceptions of
field types 9 and 10. In the above example, you could use C1 for PMC to specify a control sort on the primary
attribute.
The control sort feature is useful for grouping material on separate pages by a common attribute (or attributes),
such as Line Number Label.
When using a control sort, you will usually display the control value only once per page. However, the number
of occurrences processed (items per page) must be the same as the other common variables.
Global Sorts
A global sort enables you to specify a group of attributes for use in sorting. A global sort is similar to a control
sort except that it causes a page break when any of the attributes that belong to the global sort group changes
value. For example, if two or more fields have G1 as the sorting suffix, the system breaks all the related fields
in relation to the group of G1 fields.
129
________________
Report Manager User’s Guide - April 2002
Sorting Example
The following extract from piping_f.fmt illustrates the use of a global sort for the attributes which make up the
line number label. All the attributes which make up the line number label belong to the same global sort group
(have the same sorting suffix).
1,8,40,15,1,1,’LINE NUMBER;’
4,8,55,30,1,2,BI2G1,45,2
7
4,8,55,30,1,2,BB2G1,45,2
7
4,8,55,30,1,2,B*I2G1,45,2
7
4,8,55,30,1,2,BT1G1,45,2
7
4,8,55,30,1,2,BX1G1,45,2
7
4,8,55,30,1,2,B**K2G1,45,2
7
4,8,55,30,1,2,B*S2G1,45,2
8
The 7s are used to print the output fields in relation to the previous output field.
130
________________ Reporting Weights and Center of Gravities
Wet Specific Gravity 1 Weight and Wet Specific Gravity 1 Center of Gravity
Wet Specific Gravity 2 Weight and Wet Specific Gravity 2 Center of Gravity
Wet Specific Gravity 3 Weight and Wet Specific Gravity 3 Center of Gravity
n
Total Weight = Σ Mi
Formats
3. Report
i =1
n
Σ Mi Xi (x)
i =1
Total COG (x) = ________
_
m
n
Σ Mi Xi (y)
i =1
Total COG (y) = _ ________
m
n
Σ Mi Xi (z)
i =1
_________
Total COG (z) =
m
where:
The reportable items affected by the weight and COG calculations are Pipes, Components, Engineered Items,
Instruments, Pipe Supports, Equipment, and Bolts.
131
________________
Report Manager User’s Guide - April 2002
Pipes
Dry Weight = Dry Weight Item (TDB) + Insulation Weight
Wet Water Weight = Dry Weight + Wet Water Weight Item (TDB)
Net SGi Weight = Dry Weight + Wet Water Weight Item (TDB) * SGi (TDB)
where i = 1, 2, or 3.
Dry Weight = Dry Weight Item (TDB) + Insulation Weight + Operator Weight (TDB)
132
________________ Reporting Weights and Center of Gravities
n
Volume= Σ π * CP Face To Center (TDB) * ((Radius OD + Insulation Thickness (TDB))2 − RadiusOD 2 )
i =1
All specific gravity (SG) Item COGs = Wet Water Item COGs
Net SGi Weight = Dry Weight+Wet Water Weight Item (TDB) * SGi (TDB)
where i = 1, 2, or 3.
Formats
3. Report
Pipe Supports
Dry Weight = Weight Item (TDB)
All specific gravity (SG) Item COGs = Wet Water Item COGs
where i = 1, 2, or 3.
Equipment
Equipment weights must include all weights of that entire piece of equipment. The wet weight is composed of
the dry weight plus the fluid weight without specific gravity being considered.
133
________________
Report Manager User’s Guide - April 2002
Bolts
B D E2
All SGs = Dry Weight = Wet Weight =π A __ A * L *δ*n
D2G
where:
For items with spec implied Spec materials, the weight should be entered in the weight table as 1⁄2 the total
weight of the combined item and spec implied spec item weight to create an exact weight. (This is strictly
user-controlled; the delivered specs do NOT reflect this method for spec implied items.) For items with spec
implied alphanumeric library materials, all combined weights must be entered in the weight table for that item
to produce an exact weight. For gaskets and nuts or any other weights, the bolt density is defined by the system
as 490 pounds per cubic foot.
The system automatically converts the units for reporting; the units need not be the same for the weight tables,
density values, and other physical data units. Weights are output in the RDB physical weight units and COGs
are output in plant coordinates.
A wet weight or dry weight that is 0 or undefined, generates a warning in the report error log and generates a *
by all effected weight and COG totals. This means that although the value was undefined the calculation was
still carried out using that value.
134
________________ Understanding Implied Items
The report resources and options are covered in the following order:
Bolts
The Bolts section includes sections on Retrieving and Reporting Bolt Data and Bolt
Type Definition.
Gaskets
The Gaskets section includes sections on Retrieving and Reporting Gasket Data,
Gasket Diameters, Gasket Priority Selection at Spec Break, and Gasket Separation.
4. Implied Items
Nuts
The Nuts section contains the spec data used to derive the number and size of nuts.
Weld Data
The Weld Data section includes an explanation of how the system retrieves weld
information.
Induction Bends
The Induction Bends section includes how to create induction bends for reporting.
MTO Notes
The MTO Notes section includes tips and hints for MTO reporting.
135
________________
Report Manager User’s Guide - April 2002
Bolts
Gaskets
Nuts
Welds
The Material Takeoff Options form is part of the Project Administrator module, and its
setting greatly affect the way mating implied items are reported.
For more information on mating implied item reporting, see Material Takeoff
Options, page 139.
The definition of the spec-implied item has the same search parameters as the primary
component, except in the following instances:
– The value for the option attribute of the spec-implied component is equal to 5000
plus the option value for the primary component.
136
________________ Understanding Implied Items
– The definition of the spec-implied component can be divided into several NPD
ranges.
The output parameters of the spec-implied component may differ from those of the
primary component in the following instances:
– Only the primary component is included in the model depiction; the spec-implied
component only appears in reports.
– Jacketed components when the outer jackets are obtained independently of the
internal components.
4. Implied Items
Commodity codes prefixed by a plus (+) in the Commodity Code field in the Piping Job
Specification indicate the primary component has one or more associated table-implied items.
The system searches for the definition of the implied item in the Piping Commodity Implied
Material Data (pdtable_212), which contains the commodity code of the primary component,
the applicable NPD range, and the commodity code of the table-implied components.
The output parameters of the table-implied item may differ from those of the primary
component in the following situations:
137
________________
Report Manager User’s Guide - April 2002
– If only the primary component is included in the model depiction, the table-implied
items appear only in the report.
The commodity codes prefixed by a ’+’ are used to define the following items:
Secondly, notice the table entries that are related to the primary component,
FAAABAWAAA, in pdtable_212. All of the related items, which include the first three items
in the table would be reported:
138
________________ Material Takeoff Options
This option activates the following form which specifies the source of commodity
information, units for bolt length and diameter, and specifies item names used to reference a
commodity item in the Graphic Commodity Library. Refer to the Reference Data Manager
Reference Guide for information on the stud table, bolt length calculations, and the bolt
commodity code table.
Steps
4. Implied Items
1. Specify the bolt information.
— Bolt Length Roundoff Select the option for the means to determine bolt length.
– Preferred Bolt Length Table The system uses the preferred bolt length table.
– Bolt Roundoff Factor The system rounds the calculated bolt length to the
nearest value specified by the roundoff factor.
— Length Calculation Select the method to be used in calculating bolt length. The
bolt length is read from the stud table. The table value can be determined using the
rating and table suffix (Almost Precise) or using termination type, rating, and table
suffix (Precise). This also affects bolt lengths for lap joint flanges.
139
________________
Report Manager User’s Guide - April 2002
— Bolt Commodity Code Select the method to be used in determining the commodity
code for bolts for use in material take-off. Piping Job Specification or Bolt
Commodity Code Table.
— Bolt Diameter Units Select the system of units for bolt diameter.
— Bolt Length Units Select the system of units for bolt length.
2. Gasket Search
Select this field to toggle the setting between Off or On. If this field is On, the system
displays a field to input the Field Fit Length Table name.
4. Commodity Code
Select this field to toggle the setting between Size Independent or Size Dependent.
— Source of Implied Data This option specifies the source of the commodity code for
reporting implied data from the Piping Commodity Implied Material Data Table.
The default option (System Commodity Code) tells the system to use the
commodity code defined in the Piping Commodity Specification Data Table
(pdtable_202 attribute 18).
The Size-Dependent Commodity Code option tells the system to use the
commodity code defined in the Piping Commodity Size-Dependent Material Data
Table (pdtable_211 attribute 7).
— Source of Material Description This option specifies the source of the commodity
code for reporting a component’s material description.
The default option (System Commodity Code) tells the system to use the
commodity code defined in the Piping Commodity Specification Data Table
(pdtable_202 attribute 18).
The Size-Dependent Commodity Code option tells the system to use the
140
________________ Material Takeoff Options
5. Key in the commodity item names to be used for reporting implied materials.
These fields indicate the default item names to be used in reporting implied
materials unless a specific override is set for the component being reported.
6. Key in the bolt length values. The display of these fields is dependent on the setting for
Bolt Roundoff Option.
— Bolt Length Table This table defines the low and high range for calculated bolt
lengths and corresponding preferred or purchased lengths of the bolt. This field is
only used if Preferred Bolt Length Table is the active Bolt Roundoff Option.
— Bolt Length Roundoff Factor This field defines the value for the bolt roundoff
factor in subunits. This value is only used if Bolt Roundoff Factor is the active
Bolt Roundoff Option.
7. Select Confirm (√) to accept any changes to the Material Takeoff options.
4. Implied Items
141
________________
Report Manager User’s Guide - April 2002
Preferred Bolt Length Table – The system uses the bolt length from the Preferred Bolt
Length Table.
Bolt Roundoff Factor – The system uses the Preferred Bolt Length Roundoff Factor.
For instance, if the factor is 0.25" and the bolt length is 3.95", the bolt length will be
rounded to the nearest factor of 0.25 which is 4.0".
If the Preferred Bolt Length Table option is selected, the system retrieves the bolt
length from Preferred Bolt Length Table in the Piping Spec Table Library.
If the Bolt Roundoff Factor option is selected, the Bolt Length Roundoff Factor field
is activated, and the factor that is keyed in is used to determine the bolt length.
Table_Data_Definition ’BOLT_LENGTH’
! Description= Preferred bolt lengths (maximum of 300 entries)
! By=GJH Ckd By=DCG Rev=1 Date=04-Aug-1987
No_Inputs 2 No_Outputs 1
Units= IN, IN, IN
142
________________ Bolt Length Roundoff
The system uses the Modifier attribute from the Commodity Item entity for the bolt to
determine whether it is a stud bolt (0 or positive), or machine bolt (negative). The absolute
value of the modifier, which ranges from 0 to 5, determines which of the bolt extension values
will be used. If the modifier points to a column in the table containing bolt extensions that
has a dash entry, no bolts are generated and an error is logged for that set of bolts.
4. Implied Items
143
________________
Report Manager User’s Guide - April 2002
If the toggle is set to Piping Job Spec, the Piping Component Data is used to generate
the commodity codes.
If it is set to Bolt Commodity Code Table, and if you have created a Bolt Commodity
Code Table as specified in the Reference Data Manger Reference Guide and compiled
it, the user-defined Bolt Commodity Code Table is used to generate 24-character
commodity codes.
Although this table uses only the bolt diameter and low bolt length data as
input, the correct look-up based on bolt diameter and calculated bolt length is
performed.
144
________________ Alternate Gasket Search
where end implies a combination of end preparation, table suffix, and pressure rating.
In order for the alternate gasket search to take place, the following steps must be done:
Set the Gasket Search toggle to Alternate on the Material Takeoff Options form in
Project Administrator.
The system performs the following actions to determine the gasket data to report.
MTO collects the end preparation, pressure rating, and table suffix for both mating
bolted ends.
4. Implied Items
— If both sets of data are the same, MTO searches the spec for the gasket in the
standard manner.
— If any of this data is different, MTO searchs the spec using both green and red data.
This method requires that the gasket data be created in the spec with some precedence for the
green and red data to eliminate any order dependencies. For example, the precedence could
be:
If ratings differ, green data would contain the higher rating (and the corresponding end
preparation and table suffix), or
If end preparations differ, green data would contain the lower end preparation value
(and the corresponding pressure rating and table suffix), or
If table suffix values differ, green data would contain the lower table suffix (and the
corresponding pressure rating and end preparation).
145
________________
Report Manager User’s Guide - April 2002
The Revise, Component, Data command sequence activates the Revise Component
Data form which displays a toggle line that defines how mating implied items are
generated. The toggle can be set to either:
Special Cases
If both (or neither) mating components have ownership, the system assigns ownership
randomly, as if no ownership was set.
When the mto requirement data on the Revise Component Data form is set to
Reportable by MTO (which is stored at 1) the system reports that data.
146
________________ Special Rules for Implied Items
When the mto requirement data on the Revise Component Data form is set to Not
Reported by MTO (which is stored as "2") the system does not report that data. If both
mating components are set to Not Reported by MTO, no mating implied items are
generated or reported.
4. Implied Items
147
________________
Report Manager User’s Guide - April 2002
4.4 Bolts
The data for bolts and gaskets is determined by the nominal diameter, end preparation, and
pressure rating for each mating flange.
Checks the end preparations of the components to see if the components are bolted.
Determines the following values for components A and B based on the TDB data.
(Component A is the first mating component found when scanning the model.)
— maximum temperature - this value is the largest of the four temperature values
(Operating and Design) defined in the segment entities.
148
________________ Bolts
— End preparation of connected component A (0 indicates that the spec has no end
prep defined)
Calls a Physical Dimension table which returns the number of bolts, the diameter, and
the bolt extension.
The table used for bolt reporting is determined by the Length Calculation option on
the Material Takeoff Options form in the Project Administrator.
If the Length Calculation field is set to Almost Precise, a table name using the
pressure rating and table suffix at the connect point is used, for example STUD_150_5.
If the Length Calculation field is set to Precise, a table name using the termination
type, pressure rating and table suffix at the connect point is used, for example
STUD_20_150_5.
Both tables return the bolt diameter, the number of bolts per mating for the nominal
diameter at the connect point, and a set of bolt extensions for the applicable bolt
diameter. This also causes lap joint flanges to calculate bolts specially.
Compares the returned values for components A and B. If the values for the number or
bolts, bolt diameter, or bolt circle diameter differ, the system writes an error to the
4. Implied Items
report error log and does not report on that set of bolts.
— For regular bolts, the system accumulates the bolt length as:
149
________________
Report Manager User’s Guide - April 2002
If more than one bolt-thru item is placed between components A and B, the system
calculates the thickness of the item and the gasket separation between each bolt-thru
item.
The bolt length varies with the entry for modifier attribute in the Piping Commodity
Specification Data Table (pdtable_202). If the attribute is 0 or positive, it is a stud bolt
which has two bolt extensions, and if the attribute is set to negative, it is a machine bolt
which has one bolt extensions. For machine bolts, the system uses the larger of the two
bolt extensions. This extension includes the thickness of the nut and the total length of
the visible threads.
The system retrieves one-half the gasket separation for each component from the
Design Database (dd_projname) and multiplies this value by 2 to get the full gasket
gap size. Then it compares the gasket gap at A and B and uses the larger of the two
values.
Uses the information obtained from the TDB defined by the Data, Revise, Revise Bolt
Option command sequence in Piping Design Graphics, which sets the bolt override in
graphics, to scan the Piping Job Specification for the first unique entry formed by the
search criteria.
The lap joint flange must be defined in the Piping Materials Class to include
the definition of wall thickness at its red connect point.
150
________________ Bolts
The following termination types are considered lap type ends and thus require the
addition of wall thickness from the TDB.
Since a lap type flange can be joined to a different termination type, the addition of wall
thickness is considered on a per end basis. For example, a lap flange end joined to a
raised face weld neck flange end only requires the addition of wall thickness at the lap
flange end.
When any of the lap type terminations are encountered, the system reads the TDB
schedule/thickness value of the red connect point of each non-thru bolted end involved
in the flanged joint. This thickness value is then added to the calculated stud length.
If the Length Calculation toggle on the Material Takeoff Options form is set to Almost
Precise, the following assumptions are used:
The entries for the lap type terminations in the BLT* generic tables provide for the
addition of wall thickness from the TDB.
The entries for the lap type terminations in the STUD_Term* generic tables provide for
the addition of wall thickness from the TDB in the calculation of nut extensions.
4. Implied Items
Commodity Specification Data Table (pdtable_202). If the attribute is 0 or positive, it is a stud
bolt which has two bolt extensions, and if the attribute is set to negative, it is a machine bolt
which has one bolt extensions. For machine bolts, the larger of the two bolt extensions is used
to calculate the length.
In the following example taken from Piping Commodity Specification Data, the first bolt is a
machine bolt and the second bolt is a stud bolt:
! AABBCC ————Green CP———– ————Red CP————- Commodity Model Geo Mat Wt FF
! Code Opt From To Prp Rating Sc/Th TS From To Prp Rating Sc/Th TS code TMx Code Std Mod Grd Cd FC Nte lng
6Q3C97 1 0.75 4 - 150 - - - - - - - - YZZZMZZAAA - - 81 -1 4031 - 7 - -
6Q3C97 1 6 36 - 150 - - - - - - - - YZZZHZZFFF - - 81 0 4031 - 7 - -
Also see the Gasket and Bolt Priority Selection at Spec Break in the following
section.
151
________________
Report Manager User’s Guide - April 2002
4.5 Gaskets
For piping, piping components and instrument components there are two attributes at each of
the component connect points which are used to generate data for gasket reporting:
cp_x_option_code - option code for the gasket type (x = connect point number).
Determines the following values for components A and B based on the TDB data.
(Component A is the first mating component found when scanning the model.)
— cp_x_option_code
— NPD
— end preparation
— pressure rating
— maximum temperature - this is the largest of the four temperature values (Operating
and Design) defined in the segment entities.
Uses these values (as search criteria) to scan the Piping Job Specification for the first
unique entry formed by these parameters. If there is more than one unique entry, the
system uses the first one it locates.
— If the information is the same for components A and B, the data for component A is
used.
152
________________ Bolts
— If the information differs for components A and B, the system retrieves the data for
both components and compares the commodity code and thickness for the gasket. If
the values are the same, the data for component B is used. If the values differ, the
system writes an error message.
If the pds_sort_code for the gasket spec entry is not "_GKT", the gasket outside
diameter is equivalent to the NPD of the rated component and the gasket inside
diameter is undefined.
Determines the following values for components A and B based on the TDB data.
(Component A is the first mating component found in scanning the model.)
You can prioritize gasket entries in each piping materials class by using the model code
attribute in the Commodity Item entity of the PJS. The priority value must be a numeric value
4. Implied Items
(integer or decimal) greater than zero; non-numeric values are ignored by MTO.
To implement the priority selection capability, you must assign a priority code
to all gaskets for all Piping Materials Classes in the PJS. If you assigned a
priority code entry for only one gasket at the bolted joint, MTO reports an
error.
Because the gasket selection is a function of the fluid being contained, and not
just the mechanical characteristics of the bolted joint, under some conditions,
an incorrect gasket may result from this priority selection approach. For
example, the priority could force the use of a spiral wound gasket on a flange
that is not strong enough to seat this gasket type.
153
________________
Report Manager User’s Guide - April 2002
To specify the gasket that has priority selection for reporting, modify the model code attribute
as seen in the following table with an attribute from 100, as the lowest, to 1, as the highest:
PIPING_MATERIALS_CLASS= 1CDZ31
! AABBCC ————Green CP———– ————Red CP————- Cmdty Model Geo Mat Wt
! Code Opt From To Prp Rating Sc/Th TS From To Prp Rating Sc/Th TS Code TMx Code Std Mod Grd Cd FC Nte
6Q3C95 1 0.75 24 21 150 - 5 - - - - - - gask1cdz31 - 2 161 .125 3653 - 7 - -
PIPING_MATERIALS_CLASS= 1C0031
6Q3C95 1 0.75 24 21 150 - 5 - - - - - - gask1c0031 - 1 161 .125 3653 - 7 - -
If you assign a priority code in the model code attribute for both gaskets corresponding
to the bolted ends that mate at a bolted joint, the system reports the gasket (and bolts)
corresponding to the bolted end with the higher priority (smaller number). This
capability supercedes the bolt ownership at that bolted joint. However, bolt length
calculations and bolt design checks are unaffected by this change.
If you do not assign priority code entries, the system determines the gasket for the two
connected components as described previously.
The priority selection of mating implied materials is determined by the following rules. The
Commodity Code column should be interpreted as the test for both commodity code and
gasket thickness.
— If the end preparation for the connect point is flanged, the gasket separation for the
connect point is set to one-half the Active Gasket Separation. However, some flanged
connections (lug, ring type joint, or wafer) have integral gaskets, which are determined by
end prep, and do not have a gasket separation. In this situation, the gasket separation at
each connect point is set to zero.
— If the end preparation for the connect point is not flanged, the gasket separation for the
connect point will be set to zero.
154
________________ Bolts
The Piping Material Class must specify gap table (DZG1) as shown below.
DZA131 4 521 - 0.063 31 L1001 D036 TA501 ML01 EL01 BA501 C001 V2 DZG1 - -
ˆˆˆˆ
The Project Control Database must set TMx for GASKETS as shown below.
! DEFINE PIPING COMMODITIES
PIPING_MATERIALS_CLASS= DZA131
Single_Spacing
! AABBCC ————Green CP———– ————Red CP————- Cmdty Model Geo Mat Wt
! Code Opt From To Prp Rating Sc/Th TS From To Prp Rating Sc/Th TS Code TMx Code Std Mod Grd Cd FC Nte
4. Implied Items
155
________________
Report Manager User’s Guide - April 2002
You must create the gasket tables in the following manner: DZG1_150 = 150#
connections, and DZG1_300 = 300# connections as shown below.
Table_Data_Definition ’DZG1_150’
! Description= Gasket GAP based on NPD + TEMP.
! By=dz Ckd By= Rev=0 Date=23-Jul-92
No_Inputs 2 No_Outputs 1
Units= NPD_IN, DF, IN
4.6 Nuts
Nuts are treated as part of bolts. The value for number and size of bolts is used to define the
number and size of the accompanying nuts. The spec data for nuts is derived from the search
criteria (if reported or present in the spec).
Maximum Temperature - this value is the largest of the four (operating and design)
temperature values defined in the segment entities.
156
________________ Bolts
Checks the end preparations of the components to see if the components are welded.
Reports (MTO) one weld in cases where two pipes with different line IDs are welded
together.
4. Implied Items
157
________________
Report Manager User’s Guide - April 2002
!DANZ - table created to check PIPE lng added to pipe based on Code
!list 1100
! Weld_Type
No_Inputs 1 No_Outputs 1
Units= INT, IN
11 0
12 1
13 13
21 0
22 0
23 10
24 30
weld_no.fmt
This report format is included in order to demonstrate the report formatting facilities
that are available for weld data. It will include the weld numbers and weld type for
as many as three ends of piping components and instrument components and both
ends of pipes.
158
________________ Induction Bends
Using the Bar Menu in Piping Design Graphics (PD_Design PD Model), set the
component group toggle to Component Group Locked on the Active Options form.
Using the Data, Revise, Component Group option, which is used to define a set of
components to be treated as a group to form an induction bend.
The indices that are used to report induction bends are: B**R#, B**S#, B**Un, B**V, and
B**Wx. See Indices for MTO Reporting (With Implied Items), page 91 for more information
on the table and indices for reporting induction bends.
For induction bends to work properly, all piping model files containing induction
bends must have the Component Group Lock set to ON, and File Design must be
executed before exiting the model files.
4. Implied Items
159
________________
Report Manager User’s Guide - April 2002
Developing a Format–Develop your own format files for specific reporting needs. The
format files in the product delivery are primarily examples of what can be done with
MTO output.
Testing a Format–Always test a new format file on a small test file which utilizes all of
the format file’s features and generates data that can be compared to known values.
Using Indices–In MTO reports, unless reporting on piping segment entities specifically,
format files should always use the long (B) prefixed indices due to their greater
flexibility.
Using MTO Reporting Indices–For weight and COG reporting, if dry or wet weights
are undefined, the system will always register warning messages for every component
that has one of the weights undefined. Any reports with item COG being reported will
have no items summed because each item has a unique COG location, thus making it a
unique item.
Reporting Weight and COG–Make sure that the system running MTO has sufficient
virtual memory available for the desired MTO process. The larger the report the more
virtual memory is required to create it.
Using (*)–Any piece of equipment with a star (*) as the first character of the equipment
group name will not be reported. The system assumes that that equipment item is used
to model something other than a reportable equipment item.
Reporting Skewed Nozzles–MTO will report the orientation of a skewed nozzle with a
semi-colon delimiter between the horizontal component and the vertical component of
the nozzle’s orientation. A nozzle that is skewed in both the horizontal and vertical
plane will be reported, for example, as ’W 30 N; 5 UP’.
Reporting Branch Reinforcement Welds–MTO will report only one weld for any branch
reinforcement (reinforcing weld or reinforcing pad). MTO will recognize these two
types of branch components on the basis of the applicable commodity names in the
Commodity Name Table of the Piping Job Specification Table Library, in the same
manner as for branch reinforcement calculations.
160
________________ Size Dependent and Independent Reporting
When the Commodity Code option is set to Size Dependent, the system provides two
additional options which specify the Source of Implied Data and the Source of
Material Description.
The default setting, Size Independent, uses the general commodity code from the
Piping Commodity Specification Data Table (pdtable_202) for reporting implied data
from the Piping Commodity Implied Material Data Table (pdtable_212).
For ISOGEN material takeoff reporting, the first model in the piping area,
from which the model you are doing the extractions from belongs, the
Commodity Code options need to be set as described under the Size
Dependent section in the System/System Commodity Code section. With any
other settings, the ISOGEN MTO for Size Dependent Implied items does not
work.
In order to determine which model is the first model in the area, do a batch
extraction with debug and verify On. A file is generated in the exported
ISOFILES directory which will be called isoname.dat. The first item in the
isoname.dat file is the first model file in the piping area.
4. Implied Items
161
________________
Report Manager User’s Guide - April 2002
162
________________ Size Dependent Setting
— If there is a ’+’ before the system commodity code in the Piping Component Data Table
(pdtable_202) and the Source of Implied Data option is set to System Commodity
Code, the system commodity code from pdtable_202 is used to retrieve implied items
from the Piping Commodity Implied Material Data Table (pdtable_212).
— The implied commodity codes, which are related to the system commodity code from
pdtable_202, are used to retrieve material descriptions from the Material Description
Library for the implied items. Both the implied commodity codes and their descriptions
are reported.
4. Implied Items
— When the Source of Material Description option is set to System Commodity Code, the
system commodity code from Piping Commodity Specification Data Table (pdtable_202)
is used to retrieve the material description from the Material Description Library for the
component being reported.
163
________________
Report Manager User’s Guide - April 2002
System/System Example
The following example displays the series of steps the system takes to report a 6 inch valve
with the previously explained settings:
164
________________ Size-Dependent/System Commodity Code Settings
— If there is a ’+’ before the system commodity code in the Piping Component Data Table
(pdtable_202) and the Source of Implied Data option is set to Size-Dependent
Commodity Code, the size-dependent commodity code from the Piping Commodity
Size-Dependent Material Data Table (pdtable_211) is used to retrieve implied items from
the Piping Commodity Implied Material Data Table (pdtable_212).
— The implied commodity codes related to the size-dependent commodity code from
pdtable_212 are used to retrieve material descriptions from the Material Description
Library for the implied items. Both the implied commodity codes and their descriptions
are reported.
— When the Source of Material Description option is set to System Commodity Code, the
system commodity code from the Piping Commodity Specification Data Table
(pdtable_202) is used to retrieve the material description from the Material Description
Library for the component being reported.
4. Implied Items
165
________________
Report Manager User’s Guide - April 2002
166
________________ System/Size-Dependent Commodity Code Settings
— If there is a ’+’ before the system commodity code in the Piping Component Data Table
(pdtable_202) and the Source of Implied Data option is set to System Commodity
Code, the system commodity code from pdtable_202 is used to retrieve implied items
from the Piping Commodity Implied Material Data Table (pdtable_212).
— The implied commodity codes related to the system commodity code from pdtable_202
are used to retrieve material descriptions from the Material Description Library for the
implied items. Both the implied commodity codes and their descriptions are reported.
4. Implied Items
167
________________
Report Manager User’s Guide - April 2002
System/Size-Dependent Example
The following example displays the series of steps the system takes to report a 6 inch valve
with the previously explained settings:
168
________________
Size-Dependent/Size-Dependent Commodity Code Settings
— If there is a ’+’ before the system commodity code in the Piping Component Data Table
(pdtable_202) and the Source of Implied Data option is set to Size-Dependent
Commodity Code, the size-dependent commodity code from the Piping Commodity
Size-Dependent Material Data Table (pdtable_211) is used to retrieve implied items from
the Piping Commodity Implied Material Data Table (pdtable_212).
— The implied commodity codes related to the size-dependent commodity code from
pdtable_212 are used to retrieve material descriptions from the Material Description
Library for the implied items. Both the implied commodity codes and their descriptions
are reported.
4. Implied Items
169
________________
Report Manager User’s Guide - April 2002
170
________________ Libraries and Database Table/Column Information
The following list briefly describes the different types of material description libraries used
for reporting.
171
________________
Report Manager User’s Guide - April 2002
172
________________ Short Material Description Library
The Short Material Description Library is created from two neutral files. (These can be
created with a text editor such as EMACS or vi.)
A neutral file containing the short material descriptions for commodity items. The
neutral file contains unique Commodity Codes followed by at least one space and a
description enclosed in single quotes. It also contains the chain wheel descriptions and
implied material descriptions associated with a commodity item.
The commodity code identifies the Piping Commodity Library code or customer’s
commodity code. The character length for this code is determined from the character
length of the commodity code in the Size Dependent Data table of the database, or from
the character length of the commodity library code in the Piping Commodity Data table
of the database, depending on which is being used to access the material descriptions.
For chain wheels the commodity code has the format CHAIN_xx, where xx represents
the chain wheel number (for example, CHAIN_12). The chain wheel number is defined
in the component and instrument analysis entities of the TDB.
A neutral file containing the material description addenda for taps. This file contains
the tap code and the text for the tap description. The tap code identifies the unique
Database Info
5. Library and
identification of a tap.
The following conventions are used to identify different types of information in the material
descriptions:
ˆ All information to the left of the carat (ˆ) is used in MTO reporting and isometric
extraction, but is excluded from Spec reporting.
173
________________
Report Manager User’s Guide - April 2002
[] Information appearing in [brackets] indicates a label type from the Label Description
Library. The system uses the label format to determine the information to be
included in the material description for MTO reporting and isometric extraction. The
label information is never used in Spec reporting.
Data Retrieval
The system uses the commodity code to retrieve the short material descriptions from the
Material Description Library.
174
________________ Material Descriptions from commodity.acd
175
________________
Report Manager User’s Guide - April 2002
176
________________
Material Descriptions from commodity.acd
Database Info
5. Library and
177
________________
Report Manager User’s Guide - April 2002
This data is used strictly for MTO reporting and material control.
You can use neutral files to insert data into the Long Material Description Library or replace
existing data.
The commodity code identifies the Piping Commodity Library code or customer’s commodity
code. The character length for this code is determined from the character length of the
commodity code in the Size Dependent Data database table, or from the character length of
the commodity library code in the Piping Commodity Data table of the PJS database,
depending on which is being used to access the material descriptions.
The long description can be up to 500 characters. Because this description may include label
numbers which are translated to text strings, the reported (compiled) length of the description
can be up to 600 characters.
Data Retrieval
The system uses the Piping Commodity Library code or commodity code to access the text for
the long description in the Long Material Description Library.
178
________________ Listing from longdescr.acd
Database Info
5. Library and
179
________________
Report Manager User’s Guide - April 2002
This data is used strictly for MTO reporting and material control. The specialty material
descriptions can be up to 240 characters in length.
These files contain the specialty tag number and the text for the material description. The
specialty tag number is appended by a specialty type which is used to distinguish between
engineered items, in-line instruments, and pipe supports.
180
________________ Specialty Material Description Library
You must create three neutral files to insert data into or replace data for the specialty material
descriptions.
For engineered items (Specialties), PD_Report searches the Specialty Material Description
Library based on the piping_comp_no attribute. If this attribute is not found, the library is
searched for the commodity_name attribute.
For instruments, PD_Report searches the Specialty Material Description Library based on the
instrument_comp_no attribute. If this attribute is not found, the library is searched for the
model_code attribute.
For pipe supports, PD_Report searches the Specialty Material Description Library based on
the commodity_code attribute. If this attribute is not found, the library is searched first for the
model_code_phy attribute (indicating that this is a Physical Pipe Support) and finally for the
model_code_log attribute (indicating that this is a Logical Pipe Support).
Data Retrieval
The system uses the specialty tag number and specialty type to access the text for the material
descriptions in the Specialty Material Description Library.
Database Info
5. Library and
181
________________
Report Manager User’s Guide - April 2002
Although data for bolts and gaskets is not recorded in the Piping Component Data Table
(pdtable_34_x) in the Piping Design Database (dd_projname), bolt and gasket labels are
classified as Piping Component Data labels. The system retrieves the bolt and gasket
information for reporting using related attributes in the Piping Component Data Table
(pdtable_202).
Although all of the attributes for piping components are available when you define a bolt or
gasket label using the Piping Component Data labels option, only the following attributes
contain data that is pertinent to bolt and gasket reporting. The following list displays the
form-attribute/table-attribute relationship which define what data is actually reported from the
Piping Component Data Table (pdtable_202):
182
________________ Labels in Material Descriptions
Database Info
5. Library and
183
________________
Report Manager User’s Guide - April 2002
All data in the Piping Design Database is a direct representation of the design.ddl file. Any
additional attributes added to any ddl may still be reported. The following rules should be
used to determine the data type for any additional attributes.
All data_types translate into the following numbers based on the following ddl file definitions
which can be used to determine data_type for user-defined attributes:
character–1
short (SN#)–1
short (NPD)–1
double (Dist. Model)–1
double (Dist. NPD)–1
double (ins thick units)–1
short–2
integer–3
float–4
double–5
Units for density, surface area, weight, and temperature are reported through
the Project Data index, B**Qn.
The insulation thickness units are set through file design of active line data
with PD_Design Place Component command. They will be either NPD units
or Model units depending on the toggle setting. See the Piping Design
Graphics Reference Guide for more information.
184
________________ Piping Design Database (dd_projname)
185
________________
Report Manager User’s Guide - April 2002
186
________________ Piping Design Database (dd_projname)
187
________________
Report Manager User’s Guide - April 2002
188
________________ Piping Design Database (dd_projname)
189
________________
Report Manager User’s Guide - April 2002
190
________________ Piping Design Database (dd_projname)
191
________________
Report Manager User’s Guide - April 2002
192
________________ Piping Design Database (dd_projname)
193
________________
Report Manager User’s Guide - April 2002
194
________________ Piping Design Database (dd_projname)
195
________________
Report Manager User’s Guide - April 2002
196
________________ Piping Design Database (dd_projname)
197
________________
Report Manager User’s Guide - April 2002
198
________________ Project Control Database
199
________________
Report Manager User’s Guide - April 2002
200
________________ Project Control Database
201
________________
Report Manager User’s Guide - April 2002
202
________________ Project Control Database
203
________________
Report Manager User’s Guide - April 2002
204
________________ Project Control Database
205
________________
Report Manager User’s Guide - April 2002
206
________________ Project Control Database
207
________________
Report Manager User’s Guide - April 2002
208
________________ Project Control Database
209
________________
Report Manager User’s Guide - April 2002
210
________________ Project Control Database
211
________________
Report Manager User’s Guide - April 2002
212
________________ Specification/Material Reference Database
213
________________
Report Manager User’s Guide - April 2002
214
________________ Specification/Material Reference Database
Data
1 specialty_rev_date integer ................................. 3
2 instr_rev_date integer ................................. 3
3 tap_data_rev_date integer ................................. 3
4 size_data_rev_date integer ................................. 3
5 implied_rev_date integer ................................. 3
6 cmp_insul_rev_date integer ................................. 3
7 flg_insul_rev_data integer ................................. 3
8 con_tol_excl_data integer ................................. 3
215
________________
Report Manager User’s Guide - April 2002
216
________________ Specification/Material Reference Database
Database Info
5. Library and
217
________________
Report Manager User’s Guide - April 2002
All model_index_no attribute names, if modified, must have the same name as is used in the
pdtable_900.
All table_no attribute names, if modified, must have the same name as is used in the
pdtable_910.
218
________________ FrameWorks Plus Data
219
________________
Report Manager User’s Guide - April 2002
220
________________ Material Takeoff Database
1. Each partition_no attribute should have the same name as it is named in Table
900.
2. Each table_no attribute should have the same name as it is named in Table 920.
MDP tables are not partitioned per model. The partition_no attribute is in all the
MDP Tables containing model specific data.
All attributes named partition_no (or ending with partition_no) are links to
the partition_no attribute in Table 900. The partition_no attributes in
Tables 21 and 22 refer to equipment models, and the partition_no attributes in
other tables refer to piping models. Also, in Table 170, if the table_no attribute is
21 or 22 then the table refers to the equipment model with that partition_no.
Otherwise it refers to a piping model with that partition_no.
nozzle names to which the segments are connected, and are in the format EQP-Name
/ NOZ-Name, for example AIRPUMP-1/NOZ-1.
The table_no attribute (or any attribute ending with table_no) in Tables 110,
120, 130, 170 and 180 is linked to the table_no attribute in Table 910 for getting the
table_name.
221
________________
Report Manager User’s Guide - April 2002
Tables 910 and 920 are linked by the table_no attribute for getting the attribute
information in that table.
1. Take the table_name to which the attribute belongs and look up the table name in
Table 910 to get its corresponding table_no.
— NULL, which means that this attribute is a normal attribute, and its
value needs no further processing being in its final form.
— NPD, which means that this attribute is a NPD attribute, with the
nominal piping diameter in coded form. All these attributes have
mirrored attributes in the same tables with name npd, which
contains the real NPD value in NPD units.
222
________________ Material Takeoff Database
223
________________
Report Manager User’s Guide - April 2002
Table 21 - Equipment
1 equip_indx_no integer index 1
2 equip_no character(30) .......................... 1
3 equip_descr_1 character(40) .......................... 1
4 equip_descr_2 character(40) .......................... 1
5 tutorial_no character(6) ........................... 1
6 equip_class character(2) ........................... 1
7 dry_weight double ................................. 5
8 oper_weight_1 double ................................. 5
9 oper_weight_2 double ................................. 5
10 insulation_thk double ................................. 5
11 construction_stat short (SN130) ................ 1
12 equipment_division short (SN69) ................ 1
13 approval_status short (SN35) ................ 1
Table 22 - Nozzles
1 nozzle_indx_no integer
2 nozzle_no character(10) .......................... 1
3 equip_index integer ................................ 3
4 nominal_piping_dia short ............................(NPD). 1
5 rating character(8) ........................... 1
6 preparation short (SN3300) ............... 1
7 piping_mater_class character(16) .......................... 1
8 unit_no character(12) .......................... 1
9 fluid_code short (SN125) ................ 1
224
________________ Material Takeoff Database
225
________________
Report Manager User’s Guide - April 2002
226
________________ Material Takeoff Database
227
________________
Report Manager User’s Guide - April 2002
Table 50 - Pipes
1 system_unique_no integer index 1
2 piping_comp_no character(20) .......................... 1
3 commodity_name character(6) ........................... 1
4 model_code character(6) ........................... 1
5 option_code short (SN400) ............... 1
6 maximum_temp double ................................. 5
7 nominal_piping_dia short ............................(NPD). 1
8 outside_diameter double .....................(Dist. NPD). 1
9 schedule_thickness character(8) (SN332) ............... 1
10 sched_thick_basis character(8) (SN332) ............... 1
11 rating character(8) ........................... 1
12 commodity_code character(16) .......................... 1
13 MTO_requirements short (SN365) ............... 1
14 fabrication_cat short (SN180) ............... 1
15 source_of_data short (SN425) ............... 1
16 PDS_sort_code character(6) ........................... 1
17 geometric_standard short (SN575) ............... 1
18 weight_code short (SN578) ............... 1
19 table_suffix_green short (SN576) ............... 1
20 table_suffix_red short (SN577) ............... 1
21 materials_grade short (SN145) ............... 1
22 pipe_length double ...................(Dist. Model). 1
23 surface_area double (SN1010 units) ........ 5
24 empty_weight double (SN1028 units) ........ 5
25 water_weight double (SN1028 units) ........ 5
26 cold_spring_length double ...................(Dist. Model). 1
27 construction_stat short (SN130) ............... 1
28 hold_status short (SN50) ................ 1
29 heat_tracing_reqmt short (SN200) ............... 1
30 heat_tracing_media short (SN210) ............... 1
31 heat_tracing_temp double ................................. 5
32 iso_dwg_index_no integer ................................ 3
33 isometric_sheet_no character(2) ........................... 1
34 piece_mark_no character(60) .......................... 1
35 color_code character(8) ........................... 1
36 piping_assembly character(12) .......................... 1
37 component_group_no short .................................. 2
38 remarks character(50) .......................... 1
39 standard_note_no_a short (SN499) ............... 2 or 1
40 standard_note_no_b short (SN499) ............... 2 or 1
228
________________ Material Takeoff Database
229
________________
Report Manager User’s Guide - April 2002
230
________________ Material Takeoff Database
231
________________
Report Manager User’s Guide - April 2002
232
________________ Material Takeoff Database
233
________________
Report Manager User’s Guide - April 2002
234
________________ Material Takeoff Database
235
________________
Report Manager User’s Guide - April 2002
The attribute_qual attribute specifies whether the attribute is a normal attribute, an NPD attribute, or a
codelisted attribute.
236
________________ Material Takeoff Database
Database Info
5. Library and
237
________________
Report Manager User’s Guide - April 2002
238
________________ Material Data Publisher
Publisher
6. Material Data
The Material Data Publisher utility (MDP) allows PDS users to generate relational database tables containing
all the material data associated with a PDS model and publish these tables to a new database schema
(MTO_PROJNAME). These tables make the model data available for easier reporting outside of PD_Report.
The Material Data Publisher uses selection set files to determine what data to publish. The MDP interface
allows you to select specific disciplines, model areas, and models within the project to publish, and to save
different sets of models in separate selection set files.
When the data is published, it can be accessed through ORACLE, INFORMIX, SQL, ODBC clients such as
Microsoft Access, and other database utilities for reporting, tracking, and ordering.
239
________________
Report Manager User’s Guide - April 2002
Beside each component of the tree view appears a box which changes depending upon the selections made in
the List View:
If all the subcomponents for a particular component are selected, the component’s box in the Tree View
contains an X.
If some but not all of the subcomponents for a particlar component are selected, the component’s box will
be shaded grey and contain an X.
If none of the subcomponents for a particular component are selected, the component’s box will be blank.
You can also use the boxes to select items in the tree view.
240
________________ List View
Publisher
6. Material Data
The List View, on the right side of the main MDP window, contains a listing of the various components
comprising the selected item in the Tree View. Initially the List View contains a list of available projects, with
projects using PDS Access Control represented by a lock icon.
When you select a project, discipline, or model area in the Tree View, the components that make up the project,
discipline, or model appear in the List View. Beside each component in the List View is a check box that
allows you to select the component for inclusion in the current selection set file.
241
________________
Report Manager User’s Guide - April 2002
6.2 Workflow
This section describes the general workflow for Material Data Publisher.
2. Select a project by double-clicking a project icon in the List View or by selecting a project from the
Project pulldown list.
If the MDP database tables have not been created for the project, or if they exist and need to be updated,
you will be prompted to create or update them.
3. Use the Tree View to navigate the project hierarchy, and use the List View check boxes to select various
components in the hierarchy.
4. Click File > Save or the Save button on the toolbar to save the project selection set file.
242
________________ Workflow
Publisher
6. Material Data
1. Create a selection set file.
— OR —
Click File > Open or the Open button on the toolbar to open an existing selection set file.
If a node is already performing a publishing operation on this project, a message box prompts you that
the project is locked by that node for MDP.
— OR —
Click Publish > Setup Scheduled Jobs to schedule publishing jobs for later.
4. Click the Submit button to process the job immediately or to schedule the batch jobs.
Clicking OK releases the lock, but this should only be done if the process has stopped
abnormally. This should not be done with an active process running.
243
________________
Report Manager User’s Guide - April 2002
Create the ODBC data source using the Windows NT Control Panel.
2. Click File > Get External Data > Import to import the published data into Access.
When the import process completes, you can manipulate the data contained in the imported tables as
necessary.
See Material Takeoff Database for a listing of the published tables and their attributes. Also see the
Material Data Publisher Data Model Diagram (DEA514810) for listings of the table attributes and their
relationships.
244
________________ Command Reference
Publisher
6. Material Data
This section details the Material Data Publisher commands, which are available from the toolbar and from
menus.
6.3.1.1 New
This command creates a new selection set (*.sel) file. If you are already working in a selection set file, or have
made selections in a new file, the system will prompt you to save the file.
6.3.1.2 Open
This command opens an existing selection set file for modification.
6.3.1.3 Save
This command saves the current selection set file. If you are working in a new file, the system will prompt you
for a file name.
6.3.1.4 Save As
This command saves the open selection set file to a new file name.
6.3.1.5 Exit
Exits the Material Data Publisher.
245
________________
Report Manager User’s Guide - April 2002
246
________________ Publish Menu
Publisher
6. Material Data
6.3.3.1 Start Publishing
This command displays the Schedule Setup dialog box, which starts the publishing processes that write the
material data to the database. If you are using a new selection set file, you will be prompted to save the file
before you can start the processes.
Operating Sequence
1. Click Publish > Start Publishing.
If you have not saved the current selection set file, you will be prompted to do so.
3. If necessary, select the Forced Publishing of Models check box to bypass revision date checking for an
incremental update. This bypass may be useful for such cases as spec changes.
— OR —
Click the Later radio button to display the job scheduling options of the Schedule Setup dialog box.
247
________________
Report Manager User’s Guide - April 2002
Options
Select Libraries to (Re)Publish – Allows you to include Short Material Description, Specialty
Material Description, and Standard Note attributes in the published data.
Forced Publishing of Models – Allows you to bypass revision date checking for an incremental update.
This bypass may be useful for such cases as spec changes.
Schedule Job Information – Allows you to schedule multiple jobs for batch processing.
— On – Allows you to select Every day selected in the Day list, the Next occurrence of the day selected
in the list, or None. When set to None, the job runs at the next occurrence of the specified time, either
the same day or the next day.
— Day – Allows you to select particular days of the week, as well as particular days in each month.
— Data File – Specifies the selection set file with which this job will be run.
— Data File Browse Button – Allows you to browse for the selection set file with which the scheduled
job will be run.
248
________________ Setup Scheduled Jobs
— Existing Scheduled Jobs – Displays the currently scheduled jobs and their various options. When
you select a job in this list, its options display in the other fields on the dialog box.
— Add – Adds the current job to the Existing Scheduled Jobs list.
Publisher
6. Material Data
— Remove – Deletes the currently selected job from the Existing Scheduled Jobs list.
The Remove button deletes jobs immediately. Clicking the Cancel button will not restore
deleted jobs.
— Modify – Saves the changes made to the currently selected job in the Existing Scheduled Jobs list.
Changes are submitted by clicking the Submit button.
The Scheduler service in Control Panel > Services must be started and running for jobs to be scheduled.
Operating Sequence
1. Click Publish > Setup Scheduled Jobs.
The system creates an mdpatjob.cmd file in the pdreport\bin directory which is used to start
the at job, and also submits an at job with the correct options specified.
You can modify the environmental variables set in the mdpatjob.cmd file after it is
created. The system will not overwrite this file if it already exists.
— OR —
Click Cancel to close the dialog box without making any changes or scheduling any jobs.
The Cancel button will not restore jobs deleted using the Remove button.
249
________________
Report Manager User’s Guide - April 2002
— OR —
250
________________ Unlock MDP Lock
Publisher
6. Material Data
displays a message box.
If the active project has been locked for MDP, the system displays another prompt.
Clicking OK displays a confirmation dialog box asking whether you want to remove the MDP lock for the
project.
251
________________
Report Manager User’s Guide - April 2002
Options
System Info – Displays the System Information dialog box.
252
________________ MDP Error Messages
Publisher
6. Material Data
If any errors occur while you are running the Material Data Publisher, the error code and its description are
written to pdtable_180. Below is a table that lists all the errors and the code that is written to pdtable_180 for
each.
Error Code
_________ Description
__________
253
________________
Report Manager User’s Guide - April 2002
840 ERROR - failed to translate red schedule thickness of lap joint flange at
mating.
@#, 840, <ent_no1>, <occ_no1>, <partition_no1>, <ent_no2>,
<occ_no2>, <partition_no2>
850 ERROR - failed to find Pipe Support spec data in reference database.
Searched with: material index - '<matl_index>'
254
________________ MDP Error Messages
Publisher
6. Material Data
database.
Searched with (ALTERNATE):
piping material class - '<pmc>'
gasket item name - '<name>'
option code - '<op_code>'
nominal diameter - '<npd>'
green end preparation - '<green_end_prep>'
green pressure rating - '<green_pr_rating>'
green table suffix - '<green_TS>'
red end preparation - '<red_end_prep>'
red pressure rating - '<red_pr_rating>'
red table suffix - '<red_TS>'
max temperature - '<max_temp>'
255
________________
Report Manager User’s Guide - April 2002
256
________________ Appendix A: Sample Format Files and Output
The format files and report output in this chapter have been provided to display format rather
than content, therefore many of the examples are only partial files and do not represent the entire
and Output
A. Format Files
format file or report output.
segment.fmt
This report format will include piping segment data. It demonstrates ’control’ sorting and output field ’looping’
(field functions 9 and 10).
This report format will report a list of piping segments grouped by the Model Builder’s alphanumeric
description id. The report will include all piping lines that are associated with a specific Model Builder
alphanumeric input file.
piping_a.fmt
This report format will include data for piping components, pipes, instrument components, gaskets, bolts, nuts,
and welds. It demonstrates the use of ’standard’ output fields.
This report will include each category of data in a fixed area of a repeated report page using ’normal sorting’
and ’standard output fields’ (field function 4).
piping_b.fmt
This report format will include data for piping components, pipes, instrument components, gaskets, bolts, nuts,
and welds. It demonstrates the technique for grouping blocks of output fields on the same page of the report.
This report format will report data similar to ’piping_a.fmt’. It differs only in that it demonstrates another
method to format the data on the repeated page of the report.
piping_c.fmt
This report format will include data for piping components, pipes, instrument components, gaskets, bolts, nuts,
welds, pipe supports, implied piping components, equipment, and nozzles. It demonstrates the use of different
pages of output within one report.
257
________________
Report Manager User’s Guide - April 2002
This report format will report data similar to ’piping_b.fmt’ with the addition of pipe_supports, implied piping
components, equipment, and nozzles. It will use ’page break markers’ (field function 5) to break each category
of data onto a different repeated page of the report.
piping_d.fmt
This report format will report the material descriptions for piping components, pipes, instrument components,
pipe supports, gaskets, and bolts.
This report format will use identical report indices to create two columns to continue data on the same report
page. It will also use page breaks to separate the different categories of data onto different repeated pages of the
report.
piping_e.fmt
This report format will report data similar to ’piping_c.fmt’, but without any equipment and nozzle data.
This report format will use a ’continuous page marker’ (field function 6) to create a report with no page
boundaries and continuous output (typically used for creating a neutral file format). It also demonstrates the use
of report indices to create a summary of standard notes used in the report.
piping_f.fmt
This report format will include data for piping components, pipes, instrument components, gaskets, bolts, and
pipe supports similar to ’piping_e.fmt’.
Each category of data will be grouped (using ’global control sorting’) under a common line number label for
each page of output. It uses ’output field appending’ (field functions 7 and 8) to have the different categories of
data reported on the same page and column of output.
piping_g.fmt
This report format will include data for piping components, pipes, instrument components, gaskets, bolts, and
pipe supports similar to ’piping_f.fmt’ with the same line number grouping.
This report format uses ’output field looping’ (field functions 9 and 10) to utilize all of the report page space
available. The report will include a line number followed by all components that are associated with that line
number label with one or more line number labels being reported per page, depending upon the amount of data
and the space available.
weight.fmt
This report format will include weight and center of gravity data for piping components, pipes, instrument
components, gaskets, bolts, pipe supports, implied piping components, and equipment.
258
________________ Appendix A: Sample Format Files and Output
The output is similar in format to ’piping_e.fmt’ and demonstrates the weight and cog calculation reporting
indices.
equip_a.fmt
This report format will report equipment data (including location data) and nozzle data (including location and
orientation data).
and Output
A. Format Files
weldno.fmt
This format reports weld information, such as the weld number, type and the first and second connect point
NPD.
The following files are provided in the product delivery in win32app\ingr\pdreport\rpt\ directory.
14_equip.fmt
This format report contains two sections. The first section contains an equipment section and the second section
contains nozzle data including data about the nozzles associated with each equipment item.
The default discrimination for this report is included in the 14_equip.dcr file.
16_classes.fmt
This format report provides piping class data including data from Piping Segment Data (table 12).
The default discrimination for this report is included in the 16_classes.dcr file.
17_seglist.fmt
This format report provides piping segment data including data from Piping Segment Data (table 12) and can be
modified to include report revision date, report title by user, P&ID number, and model number.
The default discrimination for this report is included in the 17_seglist.dcr file.
18_linelst.fmt
This format report provides piping line lists data including data from Piping Segment Data (table 12).
The default discrimination for this report is included in the 18_linelst.dcr file.
21_dwg_id.fmt
This format report provides line IDs per drawing data including data from Piping Segment Data (table 12).
259
________________
Report Manager User’s Guide - April 2002
Since drawing reports can only be run on one drawing at a time, there is no default discrimination file.
22_line_id.fmt
This format report provides line ID lists using data extracted from the t12c3 attribute. Data is extracted from all
piping model files including all piping design areas.
The default discrimination for this report is included in the 22_line_id.dcr file.
23_comp.fmt
This format report provides piping components data including data from Piping Segment Data (table 12) and
Piping Component Data (table 34).
The default discrimination for this report is included in the 23_comp.dcr file.
27_comp_ld.fmt
This format report provides piping components long description MTO summary data including data from Piping
Component Data (table 34).
The default discrimination for this report is included in the 27_comp_ld.dcr file.
28_pipe_ld.fmt
This format report provides piping components long description MTO summary data including data from
Piping/Tubing Data (table 50).
The default discrimination for this report is included in the 28_pipe_ld.dcr file.
29_pipspt1.fmt
This format report provides piping support data (report 1) including data from Pipe Segment Data (table 12).
To include report revision date, report title user, and model number in the report, the report format must be
modified.
The default discrimination for this report is included in the 29_pipspt1.dcr file.
30_pipspt2.fmt
This format report provides piping support data (report 2) including data from Pipe Segment Data (table 12) and
Pipe Support Data (table 80). To include report revision date, report title user, and model number in the report,
the report format must be modified.
The default discrimination for this report is included in the 30_pipspt2.dcr file.
40_instr.fmt
This format report provides instrument data including data from Pipe Segment Data (table 12) and Instrument
Component Data (table 67).
The default discrimination for this report is included in the 40_instr.dcr file.
260
________________ Appendix A: Sample Format Files and Output
60_pid_pip.fmt
This format report provides data for a P&ID and piping comparison including data from Pipe Segment Data
(table 12).
The default discrimination for this report is included in the 60_pidpip.dcr file.
65_pcalc.fmt
This format report provides piping calculation results including data from Pipe Segment Data (table 12) and
Piping/Tubing Data (table 50).
To include report revision date and report title by user, the report format file must be modified.
and Output
A. Format Files
The default discrimination for this report is included in the 65_pcalc.dcr file.
66_bcalc.fmt
This format report provides branch calculation results including data from Pipe Segment Data (table 12) and
Piping Component Data (table 34).
To include report revision date and report title by user, the report format file must be modified.
The default discrimination for this report is included in the 66_bcalc.dcr file.
The default search criteria for this report format is included in the 66_bcalc.srh file.
68_chkmdl.fmt
This format report provides an integrity check of a model including data from Pipe Segment Data (table 12),
Piping Component Data (table 34), Piping/Tubing Data (table 50), Instrument Component Data (table 67), and
Pipe Support Data (table 80).
piping_rdb.fmt
This report format will include piping material class data and piping commodity data from the Material
Reference Database. It will report the ’partial’ (without embedded commodity code labels) material
descriptions.
tbl_chk_1.fmt
This report format will include Table Checker data for one piping material class. It will report the piping
commodities with the dimension tables and Piping Eden modules used, including a list of all entries read in the
dimension tables.
261
________________
Report Manager User’s Guide - April 2002
This report will also include a list of all dimension tables and Piping Eden modules that were required for those
piping commodities, but not available in the Reference Database.
This report format is a combination of the following report formats tbl_chk_2.fmt, tblk_chk_3.fmt, and
tbl_chk_4.fmt. It provides full Table Checker output for a specific piping materials class.
tbl_chk_2.fmt
This report format will include Table Checker data for one piping material class. It will report the dimension
tables and Piping Eden modules used by each piping commodity in that piping materials class.
tbl_chk_3.fmt
This report format will include Table Checker data for one piping material class. It will list all entries read in
dimension tables.
tbl_chk_4.fmt
This report format will include Table Checker data for one piping material class. It will include a list of all
dimension tables and Piping Eden modules used by the piping commodities in that piping materials class.
This report will also include a list of all dimension tables and Piping Eden modules that were required for those
piping commodities, but not available in the Reference Database.
model_mgt.fmt
This format file reports model management data.
draw_mgt.fmt
This format file reports orthographic drawing management data.
iso_mgt.fmt
This format file reports isometric drawing management data.
iso_rev.fmt
This format file reports isometric drawing revision management data.
project_a.fmt
This format reports project information such as the client and project location and uses information from the
Drawing Management Data table and the Drawing Revision Data table for reporting.
262
________________ Appendix A: Sample Format Files and Output
clash_mgt.fmt
This format file reports interference checker data.
and Output
A. Format Files
pid_cmprpt.fmt
This format file specifies the format of the title page and heading for each page of the P&ID Consistency Check
reports. The remainder of the report is predefined by the product.
263
________________
Report Manager User’s Guide - April 2002
Sample Format – The sample format files for creating MTO reports are: segment.fmt, piping_a.fmt through
piping_g.fmt, weight.fmt, equip_a.fmt, and weldno.fmt and are delivered in the ˜\pdreport\sample\ directory.
9
4,11,50,-50,’Model Builder ID: [A12]’,-2,AH71C1,45,2
4,13,10,-5,2,2,AL,45,2
4,13,20,-40,1,2,AH2,45,2
4,13,80,-5,1,2,AH22,45,2
4,13,92,-5,1,2,AH20,45,2
4,13,102,-5,1,2,AH21,45,2
10
264
________________
Appendix A: Material Takeoff Reporting (Report Manager)
Line Status
Line Number Label Approval Construction Hold _________________
1 MMA0104-4"-1C0031-N NA - -
2 MMA0104-6"-1C0031-N NA - -
and Output
A. Format Files
Sample MTO Format (piping_a.fmt)
report_type=689 ! Piping Components MTO Report
1,1,1,23,1,3
1,1,117,4,1,1,’PAGE’
1,1,122,3,2,4
1,1,42,45,1,1,’INTERGRAPHS TEST MATERIAL TAKE-OFF EXAMPLE 1’
1,3,1,76,1,1,’—————————————————————————-’
1,3,77,55,1,1,’——————————————————-’
1,4,1,9,1,1,’LINE NAME’
1,4,30,3,1,1,’PMC’
1,4,38,14,1,1,’Material Grade’
1,4,85,13,1,1,’New Item Name’
1,4,100,25,1,1,’Commodity Code/Ins. Name’
1,4,65,15,1,1,’Quantity/Length’
1,5,5,9,1,1,’GREEN NPD’
1,5,24,8,1,1,’GREEN EP’
1,5,37,8,1,1,’GREEN ST’
1,5,49,8,1,1,’GREEN PR’
1,5,62,7,1,1,’RED NPD’
1,5,82,6,1,1,’RED EP’
1,5,98,6,1,1,’RED ST’
1,5,114,6,1,1,’RED PR’
1,6,5,26,1,1,’Short Material Description’
1,7,1,76,1,1,’—————————————————————————-’
1,7,77,55,1,1,’——————————————————-’
1,8,44,46,1,1,’Piping Components’
1,9,1,76,1,1,’............................................................................’
1,9,77,55,1,1,’.......................................................’
4,10,1,30,1,2,BI2S1,20,3
4,10,30,6,1,2,BI12,20,3
4,10,38,30,1,2,BG18,20,3
4,10,68,4,2,2,BS,20,3
4,10,85,16,1,2,BG4S3,20,3
4,10,101,16,1,2,BG8,20,3
4,11,5,16,1,2,BN49S4,20,3
4,11,24,16,1,2,BN51,20,3
4,11,37,8,1,2,BN52,20,3
4,11,49,8,1,2,BN53,20,3
4,11,62,16,1,2,BN-49S5,20,3
4,11,82,16,1,2,BN-51,20,3
4,11,98,8,1,2,BN-52,20,3
4,11,114,8,1,2,BN-53,20,3
4,12,5,125,1,2,BM1,20,3
1,31,1,76,1,1,’............................................................................’
1,31,77,55,1,1,’.......................................................’
1,32,57,17,1,1,’Pipes/Tubes/Hoses’
1,33,1,76,1,1,’............................................................................’
1,33,77,55,1,1,’.......................................................’
4,34,1,30,1,2,BB2S1,6,3
4,34,30,6,1,2,BB12S2,6,3
265
________________
Report Manager User’s Guide - April 2002
4,34,38,30,1,2,BA21,6,3
4,34,85,6,1,2,BA4,6,3
4,34,100,16,1,2,BA12,6,3
4,35,5,16,1,2,BA7S3,6,3
4,35,24,16,1,2,BA41,6,3
4,35,37,8,1,2,BA9,6,3
4,35,49,8,1,2,BA11,6,3
4,36,5,125,1,2,BF1,6,3
4,34,64,16,1,2,BA22,6,3
1,42,1,76,1,1,’............................................................................’
1,42,77,55,1,1,’.......................................................’
1,43,57,46,1,1,’Instrument Components’
1,44,1,76,1,1,’............................................................................’
1,44,77,55,1,1,’.......................................................’
4,45,1,30,1,2,B*I2S1,1,1
4,45,30,6,1,2,B*I12,1,1
4,45,38,30,1,2,B*G15,1,1
4,45,68,4,2,2,B*O,1,1
4,45,85,16,1,2,B*G2S2,1,1
4,45,101,16,1,2,B*G3,1,1
4,46,5,16,1,2,B*L55S3,1,1
4,46,24,16,1,2,B*L57,1,1
4,46,37,8,1,2,B*L58,1,1
4,46,49,8,1,2,B*L59,1,1
4,46,62,16,1,2,B*L-55S4,1,1
4,46,82,16,1,2,B*L-57,1,1
4,46,98,8,1,2,B*L-58,1,1
4,46,114,8,1,2,B*L-59,1,1
4,47,5,125,1,2,B*K1,1,1
1,48,1,76,1,1,’—————————————————————————-’
1,48,77,55,1,1,’——————————————————-’
1,49,46,70,1,1,’Gaskets (PMC,Quantity,New Item Name,Diameter,Commodity Code)’
4,50,5,6,1,2,BT3S1,2,1
4,50,15,4,2,2,BV,2,1
4,50,25,16,1,2,BT11S2,2,1
4,50,45,16,1,2,BT2S3,2,1
4,50,65,16,1,2,BT13S4,2,1
1,52,46,70,1,1,’Bolts (PMC,Quantity,New Item Name,Diameter,Bolt Length,Commodity Code)’
4,53,5,6,1,2,BX2S1,2,1
4,53,15,4,2,2,BZ,2,1
4,53,25,16,1,2,BX10S2,2,1
4,53,45,16,1,2,BX4S3,2,1
4,53,65,16,1,2,BX5S4,2,1
4,53,85,16,1,2,BX12S5,2,1
1,55,46,70,1,1,’Nuts (PMC,Quantity,Nut Diameter)’
4,56,5,6,1,2,B*A2S1,1,1
4,56,15,4,2,2,B*C,1,1
4,56,25,16,1,2,B*A3S2,1,1
1,57,46,70,1,1,’Welds (PMC,Quantity,Weld Diameter,Weld Type)’
4,58,5,6,1,2,B*D2S1,3,1
4,58,15,4,2,2,B*F,3,1
4,58,25,16,1,2,B*D3S2,3,1
4,58,45,30,1,2,B*D4S3,3,1
1,61,1,76,1,1,’............................................................................’
1,61,77,55,1,1,’.......................................................’
1,62,57,20,1,1,’PAGE TOTALS’
1,63,1,15,1,1,’Piping Comps’
1,63,17,15,1,1,’Piping’
1,63,33,15,1,1,’Instruments’
1,63,49,15,1,1,’Gaskets’
1,63,65,15,1,1,’Bolts’
1,63,81,15,1,1,’Nuts’
1,63,97,15,2,1,’Welds’
1,64,1,15,2,2,BSP
1,64,17,15,2,2,BRP
1,64,33,15,2,2,B*OP
1,64,49,15,2,2,BVP
1,64,65,15,2,2,BZP
1,64,81,15,2,2,B*CP
1,64,97,15,2,2,B*FP
3,65,115,13,1,1,’GRAND TOTALS’
3,65,1,15,2,2,BST
3,65,17,15,2,2,BRT
3,65,33,15,2,2,B*OT
3,65,49,15,2,2,BVT
3,65,65,15,2,2,BZT
3,65,81,15,2,2,B*CT
3,65,97,15,2,2,B*FT
266
________________
Appendix A: Material Takeoff Reporting (Report Manager)
and Output
A. Format Files
267
________________
Report Manager User’s Guide - April 2002
———————————————————————————————————————————–
LINE NAME PMC Material Grade Quantity/Length New Item Name Commodity Code/Ins. Name
GREEN NPD GREEN EP GREEN ST GREEN PR RED NPD RED EP RED ST RED PR
Short Material Description
———————————————————————————————————————————–
Piping Components
MMA0104-4"-1C0031-N 1C0031 A105 2 FWN FAAABAWAAA
4" RFFE NREQD CL150 4" BE S-STD CL150
Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore
MMA0104-6"-1C0031-N 1C0031 - 1
6" RFFE NREQD CL150 6" RFFE NREQD CL150
*
MMA0104-6"-1C0031-N 1C0031 A234-WPB 6 E90LR WAAAAAWAAA
6" BE S-STD 6" BE S-STD
90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
MMA0104-6"-1C0031-N 1C0031 A105 9 FWN FAAABAWAAA
6" RFFE NREQD CL150 6" BE S-STD CL150
Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore
MMA0104-6"-1C0031-N 1C0031 A216-WCB 3 GAT VAABAHCCAA
6" RFFE NREQD CL150 6" RFFE NREQD CL150
Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane 47
MMA0104-6"-1C0031-N 1C0031 A234-WPB 2 REDE WRBAAAWAAA
6" BE S-STD 4" BE S-STD
Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB, ANSI-B16.9
MMA0104-6"-1C0031-N 1C0031 A234-WPB 1 T WTAAAAWAAA
6" BE S-STD 6" BE S-STD
Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
Pipes/Tubes/Hoses
MMA0104-6"-1C0031-N 1C0031 A53-B 21’-10" PIPE PAAAAAWAAA
6" BE S-STD
Pipe, S-STD, BE, ASTM-A53-B Type S
Instrument Components
———————————————————————————————————————————–
Gaskets (PMC,Quantity,New Item Name,Diameter,Commodity Code)
1C0031 2 4" XDAABZZQSG
1C0031 9 6" XDAABZZQSG
Bolts (PMC,Quantity,New Item Name,Diameter,Bolt Length,Commodity Code)
1C0031 16 5/8" 3 1/2" YZZZHZZFFF
1C0031 72 3/4" 4" YZZZHZZFFF
Nuts (PMC,Quantity,Nut Diameter)
1C0031 32 5/8"
Welds (PMC,Quantity,Weld Diameter,Weld Type)
1C0031 2 4 1/2" Shop Weld
1C0031 21 6 5/8" Shop Weld
PAGE TOTALS
Piping Comps Piping Instruments Gaskets Bolts Nuts Welds
24 8 0 11 88 32 23
268
________________ Appendix A: Sample MTO Format (piping_b.fmt)
and Output
A. Format Files
1,12,8,13,1,1,’New Item Name’
1,12,25,10,1,1,’Spec’
1,11,38,10,1,1,’GREEN’
1,12,38,10,1,1,’Size’
1,11,51,10,1,1,’RED’
1,12,51,10,1,1,’Size’
1,11,64,10,1,1,’GREEN’
1,12,64,10,1,1,’End’
1,11,77,10,1,1,’RED’
1,12,77,10,1,1,’End’
1,11,90,10,1,1,’GREEN’
1,12,90,10,1,1,’S-W-W’
1,11,103,10,1,1,’RED’
1,12,103,10,1,1,’S-W-W’
1,12,116,16,1,1,’Commodity Code’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
1,33,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,33,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,1,1,1,1,’/’,19,1
4,14,132,1,1,1,’/’,19,1
4,14,4,3,2,2,BS,19,1
4,14,8,10,1,2,BG4S2,19,1
4,14,25,10,1,2,BI12S1,19,1
4,14,38,10,1,2,BN49S3,19,1
4,14,51,10,1,2,BN-49S4,19,1
4,14,64,10,1,2,BN51S5,19,1
4,14,77,10,1,2,BN-51S6,19,1
4,14,90,10,1,2,BN52S7,19,1
4,14,103,10,1,2,BN-52S8,19,1
4,14,116,16,1,2,BG8S9,19,1
1,35,1,34,1,1,’INSTRUMENTS’
1,36,2,3,1,1,’Qty’
1,36,8,16,1,1,’Tag Number’
1,36,30,16,1,1,’Instr Name’
1,35,50,10,1,1,’GREEN’
1,36,50,10,1,1,’Size’
1,35,65,10,1,1,’RED’
1,36,65,10,1,1,’Size’
1,35,80,10,1,1,’GREEN’
1,36,80,10,1,1,’End’
1,35,95,10,1,1,’RED’
1,36,95,10,1,1,’End’
1,37,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,37,67,66,1,1,’//////////////////////////////////////////////////////////////////’
1,40,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,40,67,66,1,1,’/////////////////////////////////////////////////////////////////’
4,38,1,1,1,1,’/’,2,1
4,38,100,1,1,1,’/’,2,1
4,38,4,3,2,2,B*O,2,1
4,38,8,16,1,2,B*G2S1,2,1
4,38,30,16,1,2,B*G3S2,2,1
4,38,50,10,1,2,B*L55S3,2,1
4,38,65,10,1,2,B*L-55S4,2,1
4,38,80,10,1,2,B*L57S5,2,1
4,38,95,10,1,2,B*L-57S6,2,1
1,42,1,34,1,1,’PIPES/TUBES/HOSES’
1,43,2,15,1,1,’Length’
269
________________
Report Manager User’s Guide - April 2002
270
________________ Appendix A: Sample MTO Output (piping_b.rpt)
and Output
A. Format Files
/ 9 FWN 1C0031 6" 6" RFFE BE NREQD S-STD FAAABAWAAA /
/ 3 GAT 1C0031 6" 6" RFFE RFFE NREQD NREQD VAABAHCCAA /
/ 2 REDE 1C0031 6" 4" BE BE S-STD S-STD WRBAAAWAAA /
/ 1 T 1C0031 6" 6" BE BE S-STD S-STD WTAAAAWAAA /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
PIPES/TUBES/HOSES
Length New Item Name Size S-W-W Commodity Code
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
/ 21’-10" PIPE 6" S-STD PAAAAAWAAA /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
/ /
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
/GASKETS (Qty Diameter) / BOLTS (Qty Diameter Length) / NUTS (Qty Diameter) / WELDS (Qty Diameter) /
————————————————————————————————————————————
/ 2 4" / 16 5/8" 3 1/2" / 32 5/8" / 2 4 1/2" /
/ 9 6" / 72 3/4" 4" / 144 3/4" / 21 6 5/8" /
/ / / / /
/ / / / /
271
________________
Report Manager User’s Guide - April 2002
272
________________ Appendix A: Sample MTO Format (piping_c.fmt)
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,3,4,2,2,B*O,40,1
4,14,8,20,1,2,B*G2S1,40,1
4,14,30,16,1,2,B*G3S2,40,1
4,14,50,10,1,2,B*L55S3,40,1
4,14,65,10,1,2,B*L-55S4,40,1
4,14,80,10,1,2,B*L57S5,40,1
4,14,95,10,1,2,B*L-57S6,40,1
!
! 1,57,3,4,2,2,B*OP
! 1,57,8,40,1,1,’:Page Total -Instruments’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’PIPES/TUBES/HOSES’
and Output
A. Format Files
1,12,2,15,1,1,’Length’
1,12,20,16,1,1,’New Item Name’
1,12,40,16,1,1,’Size’
1,12,60,10,1,1,’S-W-W’
1,12,80,16,1,1,’Commodity Code’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,20,16,1,2,BA4S1,40,1
4,14,40,16,1,2,BA7S2,40,1
4,14,60,10,1,2,BA9S3,40,1
4,14,80,16,1,2,BA12S4,40,1
4,14,4,15,1,2,BA22,40,1
!
! 1,57,3,4,2,2,BRP
! 1,57,8,40,1,1,’:Page Total -Individual Sections of Pipe’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’PIPE SUPPORTS’
1,12,2,15,1,1,’Quantity’
1,12,20,16,1,1,’Pipe Support Number’
1,12,40,16,1,1,’Size’
1,12,60,16,1,1,’Commodity Code’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,15,2,2,B*R,40,1
4,14,20,16,1,2,B*P2,40,1
4,14,40,16,1,2,B*S11,40,1
4,14,60,16,1,2,B*P12,40,1
!
! 1,57,3,4,2,2,B*RP
! 1,57,8,40,1,1,’:Page Total - Pipe Supports’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’IMPLIED MATERIALS’
1,12,7,15,1,1,’GASKETS’
1,13,4,3,1,1,’Qty’
1,13,10,10,1,1,’Diam.’
1,13,25,16,1,1,’Comm. Code’
1,12,52,10,1,1,’BOLTS’
1,13,45,3,1,1,’Qty’
1,13,50,10,1,1,’Diam.’
1,13,63,10,1,1,’Length’
1,12,78,10,1,1,’NUTS’
1,13,76,3,1,1,’Qty’
1,13,81,10,1,1,’Diam.’
1,12,109,10,1,1,’WELDS’
1,13,106,3,1,1,’Qty’
1,13,111,16,1,1,’Diam.’
273
________________
Report Manager User’s Guide - April 2002
1,14,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,14,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,15,3,4,2,2,BV,40,1
4,15,10,10,1,2,BT2S1,40,1
4,15,25,16,1,2,BT13S2,40,1
4,15,45,3,2,2,BZ,40,1
4,15,50,10,1,2,BX4S1,40,1
4,15,63,10,1,2,BX5S2,40,1
4,15,76,3,2,2,B*C,40,1
4,15,81,10,1,2,B*A3S1,40,1
4,15,106,3,2,2,B*F,40,1
4,15,111,16,1,2,B*D3S1,40,1
!
! 1,57,3,4,2,2,BVP
! 1,57,8,25,1,1,’:Page Total -Gaskets’
! 1,57,44,4,2,2,BZP
! 1,57,50,25,1,1,’:Page Total -Bolts’
! 1,57,75,4,2,2,B*CP
! 1,57,80,25,1,1,’:Page Total -Nuts’
! 1,57,105,4,2,2,B*FP
! 1,57,110,21,1,1,’:Page Total -Welds’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,10,50,34,1,1,’IMPILIED ALPHANUMERIC MATERIALS’
1,12,1,16,1,1,’Qty’
1,12,20,16,1,1,’Commodity’
1,12,40,80,1,1,’Fabrication Category’
1,12,125,4,1,1,’Note’
1,13,20,110,1,1,’Short Material Description’
1,14,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,14,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,16,1,16,1,2,B**O,36,3
4,16,20,16,1,2,B**J7,36,3
4,16,40,80,1,2,B**J9,36,3
4,16,125,4,2,2,B**J10,36,3
4,17,20,110,1,2,B**M1,36,3
!
! 1,57,105,4,5,2,B**OP
! 1,57,110,21,1,1,’:Page Total -Implied’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’EQUIPMENT’
1,12,2,15,1,1,’Quantity’
1,12,20,30,1,1,’Equipment Name’
1,12,55,40,1,1,’Equipment Description 1/2’
1,12,100,6,1,1,’Class’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,15,2,2,B**D,40,2
4,14,22,30,1,2,B**A2,40,2
4,14,57,40,1,2,B**A3,40,2
4,15,57,40,1,2,B**A4,40,2
4,14,102,2,1,2,B**A6,40,2
!
! 1,57,3,4,2,2,B**DP
! 1,57,8,40,1,1,’:Page Total - Equipment’
!
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’NOZZLES’
!
! 1,12,2,15,1,1,’Quantity’
!
1,12,20,30,1,1,’Equipment Name’
274
________________ Appendix A: Sample MTO Format (piping_c.fmt)
1,12,55,10,1,1,’Nozz Tag’
1,12,70,16,1,1,’Size’
1,12,90,8,1,1,’Rating’
1,12,100,16,1,1,’End Prep’
1,12,120,6,1,1,’PMC’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
!
! 4,14,4,15,2,2,B**I,40,1
!
4,14,22,30,1,2,B**F2C1,40,1
4,14,57,10,1,2,B**E2,40,1
4,14,72,16,1,2,B**E4,40,1
4,14,92,8,1,2,B**E5,40,1
4,14,102,16,1,2,B**E6,40,1
4,14,122,6,1,2,B**E7,40,1
!
! 1,57,3,4,2,2,B**IP
! 1,57,8,40,1,1,’:Page Total - Nozzles’
!
and Output
A. Format Files
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’GRAND TOTALS’
1,13,1,20,1,1,’Piping Components’
1,13,25,15,1,1,’Instruments’
1,18,1,20,1,1,’Equipment’
1,18,25,15,1,1,’Nozzles’
1,18,45,15,1,1,’Implied’
1,13,45,10,1,1,’Pipes’
1,13,60,15,1,1,’Pipe Supports’
1,13,80,10,1,1,’Gaskets’
1,13,95,10,1,1,’Bolts’
1,13,105,10,1,1,’Nuts’
1,13,120,10,1,1,’Welds’
1,14,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,14,67,66,1,1,’//////////////////////////////////////////////////////////////////’
1,19,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,15,8,4,2,2,BST
1,15,30,4,2,2,B*OT
1,20,8,4,2,2,B**DT
1,20,30,4,2,2,B**IT
1,20,47,4,5,2,B**OT
1,15,47,4,2,2,BRT
1,15,65,4,2,2,B*RT
1,15,83,4,2,2,BVT
1,15,96,4,2,2,BZT
1,15,106,4,2,2,B*CT
1,15,121,4,2,2,B*FT
275
________________
Report Manager User’s Guide - April 2002
PIPES/TUBES/HOSES
Length New Item Name Size S-W-W Commodity Code
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
21’-10" PIPE 6" S-STD PAAAAAWAAA
IMPLIED MATERIALS
GASKETS BOLTS NUTS WELDS
Qty Diam. Comm. Code Qty Diam. Length Qty Diam. Qty Diam.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
2 4" XDAABZZQSG 16 5/8" 3 1/2" 32 5/8" 2 4 1/2"
9 6" XDAABZZQSG 72 3/4" 4" 144 3/4" 21 6 5/8"
GRAND TOTALS
Piping Components Instruments Pipes Pipe Supports Gaskets Bolts Nuts Welds
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
24 0 8 0 11 88 176 23
276
________________ Appendix A: Sample MTO Format (piping_d.fmt)
and Output
A. Format Files
1,12,70,3,1,1,’Qty’
1,12,75,10,1,1,’New Item Name’
1,12,87,10,1,1,’Commodity Code’
1,12,100,30,1,1,’Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,67,1,1,1,’*’,43,1
4,14,4,3,2,2,BS,43,4
4,14,8,10,1,2,BG4S1,43,4
4,14,20,15,1,2,BG8S2,43,4
4,14,35,30,1,2,BM1,43,4
4,14,72,3,2,2,BS,43,4
4,14,75,10,1,2,BG4S1,43,4
4,14,87,15,1,2,BG8S2,43,4
4,14,102,30,1,2,BM1,43,4
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS PIPING MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’INSTRUMENTS’
1,12,2,3,1,1,’Qty’
1,12,8,16,1,1,’Tag Number’
1,12,30,16,1,1,’Instr Name’
1,12,50,80,1,1,’Specialty Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,3,2,2,B*O,43,4
4,14,8,16,1,2,B*G2S1,43,4
4,14,30,16,1,2,B*G3S2,43,4
4,14,50,80,1,2,B*K1,43,4
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS PIPING MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’PIPES/TUBES/HOSES’
1,12,2,15,1,1,’Length’
1,12,20,16,1,1,’New Item Name’
1,12,40,16,1,1,’Commodity Code’
1,12,60,70,1,1,’Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,20,16,1,2,BA4S1,43,4
4,14,40,16,1,2,BA12S2,43,4
4,14,60,70,1,2,BF1,43,4
4,14,4,15,1,2,BA22,43,4
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS PIPING MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’PIPE SUPPORTS’
1,12,2,15,1,1,’Qty’
1,12,20,16,1,1,’Support Number’
277
________________
Report Manager User’s Guide - April 2002
1,12,40,16,1,1,’Commodity Code’
1,12,60,70,1,1,’Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,15,2,2,B*R,43,4
4,14,20,16,1,2,B*P2S1,43,4
4,14,40,16,1,2,B*P12S2,43,4
4,14,60,70,1,2,B*U1,43,4
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS PIPING MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’GASKETS’
1,12,2,15,1,1,’Qty’
1,12,40,16,1,1,’Commodity Code’
1,12,60,70,1,1,’Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,15,2,2,BV,43,4
4,14,40,16,1,2,BT13,43,4
4,14,60,70,1,2,BT21,43,4
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS PIPING MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’BOLTS’
1,12,2,15,1,1,’Qty’
1,12,40,16,1,1,’Commodity Code’
1,12,60,70,1,1,’Material Description’
1,13,1,66,1,1,’//////////////////////////////////////////////////////////////////’
1,13,67,66,1,1,’//////////////////////////////////////////////////////////////////’
4,14,4,15,2,2,BZ,43,4
4,14,40,16,1,2,BX12,43,4
4,14,60,70,1,2,BX20,43,4
278
________________ Appendix A: Sample MTO Output (piping_d.rpt)
Corporation Headquarters
Intergraph Corporation
Huntsville, Alabama 35894-0001
(205)730-2000
PIPING COMPONENTS
Qty New Item Commodity Material Description Qty New Item Commodity Material Description
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
1 * *
*
*
and Output
A. Format Files
*
6 E90LR WAAAAAWAAA 90 deg LR elbow, S-STD, BE, *
ASTM-A234-WPB, ANSI-B16.9 *
*
*
11 FWN FAAABAWAAA Flange, CL150, RFFE/BE, *
ASTM-A105, ANSI-B16.5, WN, *
S-STD bore *
*
3 GAT VAABAHCCAA Gate valve, CL150, RFFE, BB, *
OS&Y, ASTM-A216-WCB, trim 8, *
Crane 47 *
*
2 REDE WRBAAAWAAA Eccentric reducer, S-STD x *
S-STD bore, BE, *
ASTM-A234-WPB, ANSI-B16.9 *
*
1 T WTAAAAWAAA Tee, S-STD, BE, ASTM-A234-WPB, *
ANSI-B16.9 *
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
279
________________
Report Manager User’s Guide - April 2002
280
________________
Appendix A: Sample MTO Format (piping_e.fmt)
4,9,2,20,1,2,B*G2,1,3
4,9,25,6,1,2,B*G3,1,3
4,9,36,8,1,2,B*L55,1,3
4,9,47,8,1,2,B*L59,1,3
4,9,58,8,1,2,B*L57,1,3
4,9,71,8,1,2,B*L-55,1,3
4,9,82,8,1,2,B*L-59,1,3
4,9,93,8,1,2,B*L-57,1,3
4,9,106,5,2,2,B*G53,1,3
4,10,19,113,1,2,B*K1,1,3
4,11,1,1,1,1,’ ’,1,3
5
6
1,3,50,34,1,1,’PIPE SUPPORTS’
1,5,2,3,1,1,’Qty’
1,5,8,16,1,1,’Support Number’
1,5,27,8,1,1,’Size’
1,5,38,16,1,1,’Commodity Code’
1,4,57,5,1,1,’Std. Note’
1,5,65,67,1,1,’Material Description’
and Output
A. Format Files
1,6,1,66,1,1,’——————————————————————’
1,6,67,66,1,1,’——————————————————————’
4,7,2,3,2,2,B*R,1,2
4,7,8,16,1,2,B*P2,1,2
4,7,27,8,1,2,B*S11,1,2
4,7,38,16,1,2,B*P12,1,2
4,7,57,5,2,2,B*P18,1,2
4,7,65,67,1,2,B*U1,1,2
4,8,1,1,1,2,’ ’,1,2
5
6
1,3,50,34,1,1,’IMPLIED MATERIAL - GASKETS’
1,5,2,3,1,1,’Qty’
1,5,8,8,1,1,’Size’
1,5,19,8,1,1,’End’
1,5,27,5,1,1,’Std. Note’
1,5,35,16,1,1,’Commodity Code’
1,5,54,68,1,1,’Material Description’
1,6,1,66,1,1,’——————————————————————’
1,6,67,66,1,1,’——————————————————————’
4,7,2,3,2,2,BV,1,2
4,7,8,8,1,2,BT2,1,2
4,7,19,8,1,2,BT8,1,2
4,7,27,5,2,2,BT19,1,2
4,7,35,16,1,2,BT13,1,2
4,7,54,68,1,2,BT21,1,2
4,8,1,1,1,1,’ ’,1,2
5
6
1,3,50,34,1,1,’IMPLIED MATERIAL - BOLTS’
1,5,2,3,1,1,’Qty’
1,5,8,8,1,1,’Size’
1,5,19,16,1,1,’Length’
1,5,38,5,1,1,’Std. Note’
1,5,46,16,1,1,’Commodity Code’
1,5,65,67,1,1,’Material Description’
1,6,1,66,1,1,’——————————————————————’
1,6,67,66,1,1,’——————————————————————’
4,7,2,3,2,2,BZ,1,2
4,7,8,8,1,2,BX4,1,2
4,7,19,8,1,2,BX5,1,2
4,7,38,5,2,2,BX18,1,2
4,7,46,16,1,2,BX12,1,2
4,7,65,67,1,2,BX20,1,2
4,8,1,1,1,1,’ ’,1,2
5
6
1,3,50,34,1,1,’IMPILIED MATERIALS’
1,4,29,10,1,1,’NUTS’
1,6,25,3,1,1,’Qty’
1,6,31,8,1,1,’Size’
1,4,84,10,1,1,’WELDS’
1,6,80,3,1,1,’Qty’
1,6,86,8,1,1,’Diam.’
1,7,1,66,1,1,’——————————————————————’
1,7,67,66,1,1,’——————————————————————’
4,8,25,3,2,2,B*C,1,1
4,8,31,8,1,2,B*A3,1,1
281
________________
Report Manager User’s Guide - April 2002
4,8,80,3,2,2,B*F,1,1
4,8,86,8,1,2,B*D3,1,1
5
6
1,3,50,34,1,1,’IMPILIED ALPHANUMERIC MATERIALS’
1,5,1,16,1,1,’Qty’
1,5,20,16,1,1,’Commodity’
1,5,40,80,1,1,’Fabrication Category’
1,5,125,4,1,1,’Note’
1,6,20,110,1,1,’Short Material Description’
1,7,1,66,1,1,’——————————————————————’
1,7,67,66,1,1,’——————————————————————’
4,8,1,16,1,2,B**O,1,3
4,8,20,16,1,2,B**J7,1,3
4,8,40,80,1,2,B**J9,1,3
4,8,125,4,2,2,B**J10,1,3
4,9,20,110,1,2,B**M1,1,3
4,10,1,1,1,1,’ ’,1,3
5
6
1,3,50,34,1,1,’STANDARD NOTES’
1,4,2,5,1,1,’Note’
1,5,2,5,1,1,’ #’
1,5,10,122,1,1,’Standard Note’
1,6,1,66,1,1,’——————————————————————’
1,6,67,66,1,1,’——————————————————————’
4,7,2,5,2,2,B*Z2,1,2
4,7,10,122,1,2,B*Z3,1,2
4,8,1,1,1,1,’ ’,1,2
5
6
1,3,1,34,1,1,’GRAND TOTALS’
1,6,1,20,1,1,’Piping Components’
1,6,25,15,1,1,’Instruments’
1,6,45,10,1,1,’Pipes’
1,6,60,15,1,1,’Pipe Supports’
1,6,80,10,1,1,’Gaskets’
1,6,95,10,1,1,’Bolts’
1,6,105,10,1,1,’Nuts’
1,6,120,10,1,1,’Welds’
1,7,1,66,1,1,’——————————————————————’
1,7,67,66,1,1,’——————————————————————’
1,8,8,4,2,2,BST
1,8,30,4,2,2,B*OT
1,8,47,4,2,2,BRT
1,8,65,4,2,2,B*RT
1,8,83,4,2,2,BVT
1,8,96,4,2,2,BZT
1,8,106,4,2,2,B*CT
1,8,121,4,2,2,B*FT
282
________________ Appendix A: Sample MTO Output (piping_e.rpt)
PIPING COMPONENTS
Qty New Item Name 1st Size 1st Rat 1st End
Tag Number 2nd Size 2nd Rat 2nd End Std. Note
Commodity Code Material Description
————————————————————————————————————————————
and Output
A. Format Files
1 6" CL150 RFFE 0
CAT-101 6" CL150 RFFE
*
6 E90LR 6" BE 0
6" BE
WAAAAAWAAA 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
2 REDE 6" BE 0
4" BE
WRBAAAWAAA Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB, ANSI-B16.9
1 T 6" BE 0
6" BE
WTAAAAWAAA Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
PIPES-TUBES-HOSES
283
________________
Report Manager User’s Guide - April 2002
1,10,1,25,1,1,’Commodity Code’
1,10,27,16,1,1,’Qty/Length’
1,10,45,10,1,1,’1st Size’
1,10,57,10,1,1,’2nd Size’
1,10,69,63,1,1,’Material Description’
1,11,1,66,1,1,’——————————————————————’
1,11,67,66,1,1,’——————————————————————’
4,12,1,25,1,2,BG8S2,45,2
4,12,27,16,2,2,BS,45,2
4,12,45,10,1,2,BN49S3,45,2
4,12,57,10,1,2,BN-49S4,45,2
4,12,69,63,1,2,BM1S5,45,2
7
4,12,1,25,1,2,BA12S2,45,2
4,12,27,16,1,2,BA39,45,2
4,12,45,10,1,2,BA7S3,45,2
4,12,69,63,1,2,BF1S4,45,2
7
4,12,1,25,1,2,B*G2S2,45,2
4,12,27,16,2,2,B*O,45,2
4,12,45,10,1,2,B*L55S3,45,2
4,12,57,10,1,2,B*L-55S4,45,2
4,12,69,63,1,2,B*K1S5,45,2
7
4,12,1,25,1,2,BT13S2,45,2
4,12,27,16,2,2,BV,45,2
4,12,45,10,1,2,BT2S3,45,2
4,12,57,10,1,2,BT23,45,2
4,12,69,63,1,2,BT21S4,45,2
7
4,12,1,25,1,2,BX12S2,45,2
4,12,27,16,2,2,BZ,45,2
4,12,45,10,1,2,BX4S3,45,2
4,12,57,10,1,2,BX5S4,45,2
4,12,69,63,1,2,BX20S5,45,2
7
4,12,1,25,1,2,B**J7S2,45,2
4,12,27,16,1,2,B**O,45,2
4,12,69,63,1,2,B**M1S3,45,2
7
4,12,1,25,1,2,B*P12S2,45,2
284
________________
Appendix A: Sample MTO Format (piping_f.fmt)
4,12,27,16,2,2,B*R,45,2
4,12,45,10,1,2,B*S11S3,45,2
4,12,69,63,1,2,B*U1S4,45,2
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’GRAND TOTALS’
1,13,1,15,1,1,’Components’
1,13,20,15,1,1,’Pipes’
1,13,40,15,1,1,’Instruments’
1,13,60,15,1,1,’Gaskets’
1,13,80,15,1,1,’Bolts’
1,13,100,15,1,1,’Pipe Supports’
1,14,1,15,2,2,BST
1,14,20,15,2,2,BRT
and Output
A. Format Files
1,14,40,15,2,2,B*OT
1,14,60,15,2,2,BVT
1,14,80,15,2,2,BZT
1,14,100,15,2,2,B*RT
285
________________
Report Manager User’s Guide - April 2002
XDAABZZQSG 2 4" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled,
CS center ring, API-601
YZZZHZZFFF 16 5/8" 3 1/2" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts
FAAABAWAAA 9 6" 6" Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore
VAABAHCCAA 3 6" 6" Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane
47
WAAAAAWAAA 6 6" 6" 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
WRBAAAWAAA 2 6" 4" Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,
ANSI-B16.9
WTAAAAWAAA 1 6" 6" Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
XDAABZZQSG 9 6" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled,
CS center ring, API-601
YZZZHZZFFF 72 3/4" 4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts
GRAND TOTALS
1 - ERROR - key ’CAT-101’ was not found in SPECIALTY material description library.
2 - ERROR - key ’FA1’ was not found in SPECIALTY material description library.
286
________________
Appendix A: Sample MTO Format (piping_g.fmt)
and Output
A. Format Files
1,8,1,-25,1,-1,’Commodity Code’
1,8,27,-16,1,-1,’Qty/Length’
1,8,45,-10,1,-1,’1st Size’
1,8,57,-10,1,-1,’2nd Size’
1,8,69,-63,1,-1,’Material Description’
9
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BI2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BB2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BT1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,BX1G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B**K2G1,45,2
7
4,10,55,-50,’LINE NUMBER: [A30]’,-2,B*S2G1,45,2
8
4,12,1,-25,1,2,BG8S2,45,2
4,12,27,-16,2,2,BS,45,2
4,12,45,-10,1,2,BN49S3,45,2
4,12,57,-10,1,2,BN-49S4,45,2
4,12,69,63,1,2,BM1S5,45,2
7
4,12,1,-25,1,2,BA12S2,45,2
4,12,27,-16,1,2,BA22,45,2
4,12,45,-10,1,2,BA7S3,45,2
4,12,69,63,1,2,BF1S4,45,2
7
4,12,1,-25,1,2,B*G2S2,45,2
4,12,27,-16,2,2,B*O,45,2
4,12,45,-10,1,2,B*L55S3,45,2
4,12,57,-10,1,2,B*L-55S4,45,2
4,12,69,63,1,2,B*K1S5,45,2
7
4,12,1,-25,1,2,BT13S2,45,2
4,12,27,-16,2,2,BV,45,2
4,12,45,-10,1,2,BT2S3,45,2
4,12,57,-10,1,2,BT23,45,2
4,12,69,63,1,2,BT21S4,45,2
7
4,12,1,-25,1,2,BX12S2,45,2
4,12,27,-16,2,2,BZ,45,2
4,12,45,-10,1,2,BX4S3,45,2
4,12,57,-10,1,2,BX5S4,45,2
4,12,69,63,1,2,BX20S5,45,2
7
4,12,1,-25,1,2,B**J7S2,45,2
4,12,27,-16,1,2,B**O,45,2
4,12,69,63,1,2,B**M1S3,45,2
7
4,12,1,-25,1,2,B*P12S2,45,2
4,12,27,-16,2,2,B*R,45,2
4,12,45,-10,1,2,B*S11S3,45,2
4,12,69,63,1,2,B*U1S4,45,2
10
287
________________
Report Manager User’s Guide - April 2002
5
1,3,1,-13,1,1,’Date/Time :’
1,3,14,-23,1,5
1,3,50,-40,1,1,’PDS MTO REPORT’
1,3,120,-6,1,1,’Page: ’
1,3,127,-3,2,4
1,11,1,-34,1,-1,’GRAND TOTALS’
1,13,1,-15,1,-1,’Components’
1,13,20,-15,1,-1,’Pipes’
1,13,40,-15,1,-1,’Instruments’
1,13,60,-15,1,-1,’Gaskets’
1,13,80,-15,1,-1,’Bolts’
1,13,100,-15,1,-1,’Pipe Supports’
1,14,1,-15,2,2,BST
1,14,20,-15,2,2,BRT
1,14,40,-15,2,2,B*OT
1,14,60,-15,2,2,BVT
1,14,80,-15,2,2,BZT
1,14,100,-15,2,2,B*RT
288
________________ Appendix A: Sample MTO Output (piping_g.rpt)
Commodity Code Qty/Length 1st Size 2nd Size Material Description______________ __________ ________ ______
FAAABAWAAA 2 4" 4" Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore
XDAABZZQSG 2 4" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled,
CS center ring, API-601
and Output
A. Format Files
YZZZHZZFFF 16 5/8" 3 1/2" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts
1 6" 6" *
FAAABAWAAA 9 6" 6" Flange, CL150, RFFE/BE, ASTM-A105, ANSI-B16.5, WN, S-STD bore
VAABAHCCAA 3 6" 6" Gate valve, CL150, RFFE, BB, OS&Y, ASTM-A216-WCB, trim 8, Crane
47
WAAAAAWAAA 6 6" 6" 90 deg LR elbow, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
WRBAAAWAAA 2 6" 4" Eccentric reducer, S-STD x S-STD bore, BE, ASTM-A234-WPB,
ANSI-B16.9
WTAAAAWAAA 1 6" 6" Tee, S-STD, BE, ASTM-A234-WPB, ANSI-B16.9
XDAABZZQSG 9 6" - Gasket, CL150, G653, 0.125" thk, 304 spiral wnd, graph filled,
CS center ring, API-601
YZZZHZZFFF 72 3/4" 4" B31, ASTM-A193-B7 studs w/ASTM-A194-2H hvy hex nuts
GRAND TOTALS____________
289
________________
Report Manager User’s Guide - April 2002
1,10,1,25,1,1,’Commodity Code’
1,10,27,16,1,1,’Qty/Length’
1,10,45,10,1,1,’1st Size’
1,10,57,10,1,1,’2nd Size’
1,10,69,45,1,1,’Material Description’
1,9,114,10,1,1,’Weight’
1,10,113,10,1,1,’Multiple’
1,9,121,12,1,1,’Dry/Wet Wt.’
1,10,123,8,1,2,B**Q3
1,11,1,66,1,1,’——————————————————————’
1,11,67,66,1,1,’——————————————————————’
4,12,1,25,1,2,BG8S2,45,3
4,12,27,16,2,2,BS,45,3
4,12,45,10,1,2,BN49S3,45,3
4,12,57,10,1,2,BN-49S4,45,3
4,12,69,45,1,2,BM1S5,45,3
4,12,116,5,2,2,BSS6,45,3
4,13,121,11,5,2,BM5,45,3
4,12,121,11,5,2,BM3,45,3
7
4,12,1,25,1,2,BA12S2,45,3
4,12,27,16,1,2,BA22,45,3
4,12,45,10,1,2,BA7S3,45,3
4,12,69,45,1,2,BF1S4,45,3
4,12,116,5,2,2,BRS5,45,3
4,13,121,11,5,2,BF5,45,3
4,12,121,11,5,2,BF3,45,3
7
4,12,1,25,1,2,B*G2S2,45,3
4,12,27,16,2,2,B*O,45,3
4,12,45,10,1,2,B*L55S3,45,3
4,12,57,10,1,2,B*L-55S4,45,3
4,12,69,50,1,2,B*K1S5,45,3
4,12,116,5,2,2,B*OS6,45,3
4,13,121,11,5,2,B*K4,45,3
290
________________
Appendix A: Sample MTO Format (weight.fmt)
4,12,121,11,5,2,B*K2,45,3
7
4,12,1,25,1,2,BT13S2,45,3
4,12,27,16,2,2,BV,45,3
4,12,45,10,1,2,BT2S3,45,3
4,12,57,10,1,2,BT23,45,3
4,12,69,45,1,2,BT21S4,45,3
7
4,12,1,25,1,2,BX12S2,45,3
4,12,27,16,2,2,BZ,45,3
4,12,45,10,1,2,BX4S3,45,3
4,12,57,10,1,2,BX5S4,45,3
4,12,69,45,1,2,BX20S5,45,3
4,12,121,11,5,2,BX22,45,3
7
4,12,1,25,1,2,B**J7S2,45,3
4,12,27,16,1,2,B**O,45,3
4,12,69,45,1,2,B**M1S3,45,3
7
4,12,1,25,1,2,B*P12S2,45,3
and Output
A. Format Files
4,12,27,16,2,2,B*R,45,3
4,12,45,10,1,2,B*S11S3,45,3
4,12,69,45,1,2,B*U1S4,45,3
4,12,116,5,2,2,B*RS5,45,3
4,12,121,11,5,2,B*P15,45,3
8
5
1,1,1,13,1,1,’Date/Time :’
1,1,14,23,1,3
1,1,50,40,1,1,’PDS MTO REPORT’
1,1,120,6,1,1,’Page: ’
1,1,127,3,2,4
1,10,1,25,1,1,’Equipment Name’
1,10,40,16,1,1,’Class’
1,10,69,40,1,1,’Equipment Description’
1,9,121,11,1,1,’Dry/Wet Wt.’
1,11,1,66,1,1,’——————————————————————’
1,11,67,66,1,1,’——————————————————————’
4,12,1,25,1,2,B**A2,45,3
4,12,40,16,1,2,B**A6,45,3
4,12,69,40,1,2,B**A3,45,3
4,13,69,40,1,2,B**A4,45,3
4,12,121,11,5,2,B**A7,45,3
4,13,121,11,5,2,B**A8,45,3
5
1,3,1,13,1,1,’Date/Time :’
1,3,14,23,1,3
1,3,50,40,1,1,’PDS MTO REPORT’
1,3,120,6,1,1,’Page: ’
1,3,127,3,2,4
1,11,1,34,1,1,’GRAND TOTALS’
1,13,1,15,1,1,’Components’
1,13,20,15,1,1,’Pipes’
1,13,40,15,1,1,’Instruments’
1,13,60,15,1,1,’Gaskets’
1,13,80,15,1,1,’Bolts’
1,13,100,15,1,1,’Pipe Supports’
1,14,1,15,2,2,BST
1,14,20,15,2,2,BRT
1,14,40,15,2,2,B*OT
1,14,60,15,2,2,BVT
1,14,80,15,2,2,BZT
1,14,100,15,2,2,B*RT
291
________________
Report Manager User’s Guide - April 2002
1,30,10,50,1,2,B**P8
1,27,70,35,1,1,’ WET CENTER OF GRAVITY :’
1,28,80,50,1,2,B**P12
1,29,80,50,1,2,B**P13
1,30,80,50,1,2,B**P14
PAAAAAWAAA 1’-5 3/16" 6" Pipe, S-STD, BE, ASTM-A53-B Type S 1 2.47786
2.47786
PAAAAAWAAA 1’-8 9/16" 6" Pipe, S-STD, BE, ASTM-A53-B Type S 1 2.96443
2.96443
PAAAAAWAAA 5’-0 1/4" 6" Pipe, S-STD, BE, ASTM-A53-B Type S 1 8.68604
8.68604
PAAAAAWAAA 5’-3 3/8" 6" Pipe, S-STD, BE, ASTM-A53-B Type S 1 9.13656
9.13656
PAAAAAWAAA 5’-10 5/8" 6" Pipe, S-STD, BE, ASTM-A53-B Type S 1 10.1818
10.1818
292
________________
Appendix A: Sample MTO Format (weight.fmt)
and Output
A. Format Files
293
________________
Report Manager User’s Guide - April 2002
294
________________ Appendix A: Sample MTO Output (equip_a.rpt)
38E-101A ________
SHELL & TUBE EXCHANGER 0.00 *
*
*
and Output
A. Format Files
N1 6 300 RFFE Default UP East 1316’ 7" Site
North 450’ 3 5/8" Site
Elev 16’ 8" Site
38E-101B ______________________________
SHELL & TUBE EXCHANGER 0.00 *
*
*
38E-101C ______________________________
SHELL & TUBE EXCHANGER 0.00 *
*
*
295
________________
Report Manager User’s Guide - April 2002
38E-101D ______________________________
SHELL & TUBE EXCHANGER 0.00 *
*
*
38E-101E ______________________________
SHELL & TUBE EXCHANGER 0.00 *
*
*
38E-102 _______
Kettle Exchanger 0.00 *
*
*
296
________________ Appendix A: Sample MTO Output (equip_a.rpt)
38E-103 _______
FIN FAN COOLING TOWER 0.00 *
*
*
and Output
A. Format Files
Elev 24’ 11 9/16" Site
38E-104 _______
FIN FAN COOLING TOWER 0.00 *
*
*
38E-105 _______
FIN FAN COOLING TOWER 0.00 *
*
*
38P-101A ________
Horizontal Centrifugal Pump 0.00 *
*
*
297
________________
Report Manager User’s Guide - April 2002
38P-101B ________
Horizontal Centrifugal Pump 0.00 *
*
*
38P-101B ________
N2 3 300 RFFE Default UP East 1370’ 1 1/4" Site
North 420’ 3 5/8" Site
Elev 14’ 3 1/2" Site
38P-103A ______________________________
Horizontal Centrifugal Pump 0.00 *
*
*
38P-103B ______________________________
Horizontal Centrifugal Pump 0.00 *
*
*
38P-104A ______________________________
Horizontal Centrifugal Pump 0.00 *
*
*
38P-104A ______________________________
N2 3 300 RFFE Default UP East 1308’ 1 1/4" Site
North 420’ 3 5/8" Site
Elev 14’ 3 1/2" Site
38P-104B ______________________________
Horizontal Centrifugal Pump 0.00 *
*
*
298
________________ Appendix A: Sample MTO Output (equip_a.rpt)
38TW-102 ________
Sour Water Stripper 0.00 *
*
*
and Output
A. Format Files
N10 6 150 RFFE Default E 45 S East 1338’ 2 29/32" Site
North 433’ 7 23/32" Site
Elev 30’ 6" Site
38TW-102 ________
N14 6 300 RFFE Default W 15 S East 1331’ 11 13/32" Site
North 435’ 3 31/32" Site
Elev 145’ 3" Site
38V-101 _______
Horizontal Drum 0.00 *
*
*
299
________________
Report Manager User’s Guide - April 2002
GRAND TOTALS____________
300
________________
Appendix A: Sample MTO Format (weldno.fmt)
and Output
A. Format Files
1,10,3,10,1,-1,’Model Code’
1,10,15,7,1,-1,’CP1 NPD’
1,10,23,7,1,-1,’Weld No’
1,10,35,9,1,-1,’Weld Type’
1,10,48,7,1,-1,’CP2 NPD’
1,10,58,7,1,-1,’Weld No’
1,10,68,10,1,-1,’Weld Type’
1,10,80,7,1,-1,’CP3 NPD’
1,10,90,7,1,-1,’Weld No’
1,10,99,10,1,-1,’Weld Type’
1,10,112,8,1,-1,’Comp No.’
9
4,12,3,-50,’LINE NUMBER: [A30]’,-2,BI2G1,50,1
7
4,12,3,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,50,1
7
4,12,3,-50,’LINE NUMBER: [A30]’,-2,BB2G1,50,1
8
4,13,3,-6,1,2,BG4,50,1
4,13,15,-6,1,2,BG49,50,1
4,13,23,-8,1,2,BG55,50,1
4,13,35,-10,1,2,BG56,50,1
4,13,48,-6,1,2,BG62,50,1
4,13,58,-8,1,2,BG68,50,1
4,13,68,-10,1,2,BG69,50,1
4,13,80,-6,1,2,BG75,50,1
4,13,90,-8,1,2,BG81,50,1
4,13,99,-10,1,2,BG82,50,1
4,13,112,-19,1,2,BG2,50,1
7
4,13,3,-6,1,2,B*G3,50,1
4,13,15,-6,1,2,B*G55,50,1
4,13,23,-8,1,2,B*G61,50,1
4,13,35,-10,1,2,B*G62,50,1
4,13,48,-6,1,2,B*G68,50,1
4,13,58,-8,1,2,B*G74,50,1
4,13,68,-10,1,2,B*G75,50,1
4,13,80,-6,1,2,B*G81,50,1
4,13,90,-8,1,2,B*G87,50,1
4,13,99,-10,1,2,B*G88,50,1
4,13,112,-19,1,2,B*G2,50,1
7
4,13,3,-6,1,2,BA4,50,1
4,13,15,-6,1,2,BA7,50,1
4,13,23,-10,1,2,BA42,50,1
4,13,35,-10,1,2,BA43,50,1
4,13,48,-6,1,2,BA7,50,1
4,13,58,-10,1,2,BA50,50,1
4,13,68,-10,1,2,BA51,50,1
4,13,80,-19,1,2,BA2,50,1
8
10
301
________________
Report Manager User’s Guide - April 2002
Model Code CP1 NPD Weld No Weld Type CP2 NPD Weld No Weld Type CP3 NPD Weld No Weld Type Comp No. __________ _______ _______
Model Code CP1 NPD Weld No Weld Type CP2 NPD Weld No Weld Type CP3 NPD Weld No Weld Type Comp No. __________ _______ _______
302
________________ Appendix A: Sample MTO Format (14_equip.fmt)
and Output
A. Format Files
1,7,9,40,’[A40]’,2,B**Q5
1,7,67,16,1,1,’EQUIPMENT REPORT’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,12,1,1,’EQUIPMENT NO’
1,9,25,14,1,1,’EQUIPMENT NAME’
1,9,62,11,1,1,’DGN AREA NO’
1,9,74,10,1,1,’INSULATION’
1,9,85,19,1,1,’PP POSITION IN SITE’
1,10,9,15,1,-1,’FORM NO ’
1,10,25,36,1,-1,’LAST REV DATE ’
1,10,62,11,1,-1,’MODEL NO ’
1,10,74,10,1,-1,’ ’
1,10,85,27,1,-1,’ ’
4,11,9,-15,1,2,B**A2,51,4
4,11,25,-36,1,2,B**A3,51,4
! 4,11,62,-10,?,?,?,51,4 (DGN AREA NO)
4,11,74,4,’[F4.2]’,2,B**A10,51,4
4,11,85,-27,1,2,B**B1,51,4
4,12,9,9,1,2,B**A5,51,4
! 4,12,25,?,?,? (LAST REV DATE FOR FORM)
4,12,62,-9,1,2,B**B22,51,4
4,12,85,-27,1,2,B**B2,51,4
4,13,85,-27,1,2,B**B3,51,4
5
1,4,9,40,’[A40]’,2,B**Q7
1,4,68,15,1,1,’PDS PIPING TASK’
1,4,112,7,1,1,’PROJECT’
1,4,120,12,’[A12]’2,B**Q9
1,5,9,40,’[A40]’,2,B**Q8
1,5,112,4,1,1,’PAGE’
1,5,124,4,2,4
! 1,6,55,40,1,2,[USER REPORT TITLE]
1,6,112,3,1,1,’REV’
! 1,6,124,2,1,2,[REV NO]
1,7,9,40,’[A40]’,2,B**Q5
1,7,64,23,1,1,’EQUIPMENT NOZZLE REPORT’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,14,1,-1,’EQUIPMENT NO= ’
1,10,9,10,1,-1,’NOZZLE NO ’
1,10,20,8,1,-1,’DIAM ’
1,10,29,9,1,-1,’END PREP ’
1,10,39,10,1,-1,’RATING/THK’
1,10,50,24,1,-1,’TS ’
1,10,75,23,1,-1,’ORIENTATION/SERVICE ’
1,10,99,27,1,-1,’NOZZLE CP POSITION IN SITE ’
4,9,23,-12,1,-2,B**F2C1,51,4
4,11,9,-10,1,2,B**E2S2,51,4
4,11,20,-8,1,2,B**E4,51,4
4,11,29,-9,1,2,B**E6,51,4
4,11,39,-8,1,2,B**E5,51,4
4,11,50,-24,1,2,B**E16,51,4
4,11,75,-23,1,2,B**G1,51,4
4,12,39,-5,1,2,B**E18,51,4
4,12,75,-20,1,2,B**E17,51,4
4,11,99,-27,1,2,B**G2,51,4
4,12,99,-27,1,2,B**G3,51,4
4,13,99,-27,1,2,B**G4,51,4
303
________________
Report Manager User’s Guide - April 2002
304
________________ Appendix A: Sample MTO Format (16_classes.fmt)
and Output
A. Format Files
1,7,9,40,’[A40]’,2,B**Q5
1,7,65,21,1,1,’PIPING CLASSES REPORT’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,6,1,-1,’CLASS ’
1,9,16,25,1,-1,’LINE NO ’
1,9,42,25,1,-1,’LINE NO ’
1,9,68,25,1,-1,’LINE NO ’
1,9,94,25,1,-1,’LINE NO ’
9
4,10,9,-6,1,2,AH12C1,54,1
4,10,9,-6,1,2,AH12C1,54,1
4,10,9,-6,1,2,AH12C1,54,1
4,10,9,-6,1,2,AH12C1,54,1
4,10,16,-25,1,2,AH2,1,1
4,10,42,-25,1,2,AH2,1,1
4,10,68,-25,1,2,AH2,1,1
4,10,94,-25,1,2,AH2,1,1
4,11,16,-25,1,2,AH2,1,1
4,11,42,-25,1,2,AH2,1,1
4,11,68,-25,1,2,AH2,1,1
4,11,94,-25,1,2,AH2,1,1
4,12,16,-25,1,2,AH2,1,1
4,12,42,-25,1,2,AH2,1,1
4,12,68,-25,1,2,AH2,1,1
4,12,94,-25,1,2,AH2,1,1
4,13,16,-25,1,2,AH2,1,1
4,13,42,-25,1,2,AH2,1,1
4,13,68,-25,1,2,AH2,1,1
4,13,94,-25,1,2,AH2,1,1
4,14,16,-25,1,2,AH2,1,1
4,14,42,-25,1,2,AH2,1,1
4,14,68,-25,1,2,AH2,1,1
4,14,94,-25,1,2,AH2,1,1
4,15,16,-25,1,2,AH2,1,1
4,15,42,-25,1,2,AH2,1,1
4,15,68,-25,1,2,AH2,1,1
4,15,94,-25,1,2,AH2,1,1
4,16,16,-25,1,2,AH2,1,1
4,16,42,-25,1,2,AH2,1,1
4,16,68,-25,1,2,AH2,1,1
4,16,94,-25,1,2,AH2,1,1
4,17,16,-25,1,2,AH2,1,1
4,17,42,-25,1,2,AH2,1,1
4,17,68,-25,1,2,AH2,1,1
4,17,94,-25,1,2,AH2,1,1
4,18,16,-25,1,2,AH2,1,1
4,18,42,-25,1,2,AH2,1,1
4,18,68,-25,1,2,AH2,1,1
4,18,94,-25,1,2,AH2,1,1
4,19,16,-25,1,2,AH2,1,1
4,19,42,-25,1,2,AH2,1,1
4,19,68,-25,1,2,AH2,1,1
4,19,94,-25,1,2,AH2,1,1
4,20,16,-25,1,2,AH2,1,1
4,20,42,-25,1,2,AH2,1,1
4,20,68,-25,1,2,AH2,1,1
4,20,94,-25,1,2,AH2,1,1
305
________________
Report Manager User’s Guide - April 2002
4,21,16,-25,1,2,AH2,1,1
4,21,42,-25,1,2,AH2,1,1
4,21,68,-25,1,2,AH2,1,1
4,21,94,-25,1,2,AH2,1,1
4,22,16,-25,1,2,AH2,1,1
4,22,42,-25,1,2,AH2,1,1
4,22,68,-25,1,2,AH2,1,1
4,22,94,-25,1,2,AH2,1,1
4,23,16,-25,1,2,AH2,1,1
4,23,42,-25,1,2,AH2,1,1
4,23,68,-25,1,2,AH2,1,1
4,23,94,-25,1,2,AH2,1,1
4,24,16,-25,1,2,AH2,1,1
4,24,42,-25,1,2,AH2,1,1
4,24,68,-25,1,2,AH2,1,1
4,24,94,-25,1,2,AH2,1,1
4,25,16,-25,1,2,AH2,1,1
4,25,42,-25,1,2,AH2,1,1
4,25,68,-25,1,2,AH2,1,1
4,25,94,-25,1,2,AH2,1,1
4,26,16,-25,1,2,AH2,1,1
4,26,42,-25,1,2,AH2,1,1
4,26,68,-25,1,2,AH2,1,1
4,26,94,-25,1,2,AH2,1,1
4,27,16,-25,1,2,AH2,1,1
4,27,42,-25,1,2,AH2,1,1
4,27,68,-25,1,2,AH2,1,1
4,27,94,-25,1,2,AH2,1,1
4,28,16,-25,1,2,AH2,1,1
4,28,42,-25,1,2,AH2,1,1
4,28,68,-25,1,2,AH2,1,1
4,28,94,-25,1,2,AH2,1,1
4,29,16,-25,1,2,AH2,1,1
4,29,42,-25,1,2,AH2,1,1
4,29,68,-25,1,2,AH2,1,1
4,29,94,-25,1,2,AH2,1,1
4,30,16,-25,1,2,AH2,1,1
4,30,42,-25,1,2,AH2,1,1
4,30,68,-25,1,2,AH2,1,1
4,30,94,-25,1,2,AH2,1,1
4,31,16,-25,1,2,AH2,1,1
4,31,42,-25,1,2,AH2,1,1
4,31,68,-25,1,2,AH2,1,1
4,31,94,-25,1,2,AH2,1,1
4,32,16,-25,1,2,AH2,1,1
4,32,42,-25,1,2,AH2,1,1
4,32,68,-25,1,2,AH2,1,1
4,32,94,-25,1,2,AH2,1,1
4,33,16,-25,1,2,AH2,1,1
4,33,42,-25,1,2,AH2,1,1
4,33,68,-25,1,2,AH2,1,1
4,33,94,-25,1,2,AH2,1,1
4,34,16,-25,1,2,AH2,1,1
4,34,42,-25,1,2,AH2,1,1
4,34,68,-25,1,2,AH2,1,1
4,34,94,-25,1,2,AH2,1,1
4,35,16,-25,1,2,AH2,1,1
4,35,42,-25,1,2,AH2,1,1
4,35,68,-25,1,2,AH2,1,1
4,35,94,-25,1,2,AH2,1,1
4,36,16,-25,1,2,AH2,1,1
4,36,42,-25,1,2,AH2,1,1
4,36,68,-25,1,2,AH2,1,1
4,36,94,-25,1,2,AH2,1,1
4,37,16,-25,1,2,AH2,1,1
4,37,42,-25,1,2,AH2,1,1
4,37,68,-25,1,2,AH2,1,1
4,37,94,-25,1,2,AH2,1,1
4,38,16,-25,1,2,AH2,1,1
4,38,42,-25,1,2,AH2,1,1
4,38,68,-25,1,2,AH2,1,1
4,38,94,-25,1,2,AH2,1,1
4,39,16,-25,1,2,AH2,1,1
4,39,42,-25,1,2,AH2,1,1
4,39,68,-25,1,2,AH2,1,1
4,39,94,-25,1,2,AH2,1,1
4,40,16,-25,1,2,AH2,1,1
4,40,42,-25,1,2,AH2,1,1
306
________________
Appendix A: Sample MTO Format (16_classes.fmt)
4,40,68,-25,1,2,AH2,1,1
4,40,94,-25,1,2,AH2,1,1
4,41,16,-25,1,2,AH2,1,1
4,41,42,-25,1,2,AH2,1,1
4,41,68,-25,1,2,AH2,1,1
4,41,94,-25,1,2,AH2,1,1
4,42,16,-25,1,2,AH2,1,1
4,42,42,-25,1,2,AH2,1,1
4,42,68,-25,1,2,AH2,1,1
4,42,94,-25,1,2,AH2,1,1
4,43,16,-25,1,2,AH2,1,1
4,43,42,-25,1,2,AH2,1,1
4,43,68,-25,1,2,AH2,1,1
4,43,94,-25,1,2,AH2,1,1
4,44,16,-25,1,2,AH2,1,1
4,44,42,-25,1,2,AH2,1,1
4,44,68,-25,1,2,AH2,1,1
4,44,94,-25,1,2,AH2,1,1
4,45,42,-25,1,2,AH2,1,1
4,45,68,-25,1,2,AH2,1,1
and Output
A. Format Files
4,45,94,-25,1,2,AH2,1,1
4,46,16,-25,1,2,AH2,1,1
4,46,42,-25,1,2,AH2,1,1
4,46,68,-25,1,2,AH2,1,1
4,46,94,-25,1,2,AH2,1,1
4,47,16,-25,1,2,AH2,1,1
4,47,42,-25,1,2,AH2,1,1
4,47,68,-25,1,2,AH2,1,1
4,47,94,-25,1,2,AH2,1,1
4,48,16,-25,1,2,AH2,1,1
4,48,42,-25,1,2,AH2,1,1
4,48,68,-25,1,2,AH2,1,1
4,48,94,-25,1,2,AH2,1,1
4,49,16,-25,1,2,AH2,1,1
4,49,42,-25,1,2,AH2,1,1
4,49,68,-25,1,2,AH2,1,1
4,49,94,-25,1,2,AH2,1,1
4,50,16,-25,1,2,AH2,1,1
4,50,42,-25,1,2,AH2,1,1
4,50,68,-25,1,2,AH2,1,1
4,50,94,-25,1,2,AH2,1,1
4,51,16,-25,1,2,AH2,1,1
4,51,42,-25,1,2,AH2,1,1
4,51,68,-25,1,2,AH2,1,1
4,51,94,-25,1,2,AH2,1,1
4,52,16,-25,1,2,AH2,1,1
4,52,42,-25,1,2,AH2,1,1
4,52,68,-25,1,2,AH2,1,1
4,52,94,-25,1,2,AH2,1,1
4,53,16,-25,1,2,AH2,1,1
4,53,42,-25,1,2,AH2,1,1
4,53,68,-25,1,2,AH2,1,1
4,53,94,-25,1,2,AH2,1,1
4,54,16,-25,1,2,AH2,1,1
4,54,42,-25,1,2,AH2,1,1
4,54,68,-25,1,2,AH2,1,1
4,54,94,-25,1,2,AH2,1,1
4,55,16,-25,1,2,AH2,1,1
4,55,42,-25,1,2,AH2,1,1
4,55,68,-25,1,2,AH2,1,1
4,55,94,-25,1,2,AH2,1,1
4,56,16,-25,1,2,AH2,1,1
4,56,42,-25,1,2,AH2,1,1
4,56,68,-25,1,2,AH2,1,1
4,56,94,-25,1,2,AH2,1,1
4,57,16,-25,1,2,AH2,1,1
4,57,42,-25,1,2,AH2,1,1
4,57,68,-25,1,2,AH2,1,1
4,57,94,-25,1,2,AH2,1,1
4,58,16,-25,1,2,AH2,1,1
4,58,42,-25,1,2,AH2,1,1
4,58,68,-25,1,2,AH2,1,1
4,58,94,-25,1,2,AH2,1,1
4,59,16,-25,1,2,AH2,1,1
4,59,42,-25,1,2,AH2,1,1
4,59,68,-25,1,2,AH2,1,1
4,59,94,-25,1,2,AH2,1,1
4,60,16,-25,1,2,AH2,1,1
307
________________
Report Manager User’s Guide - April 2002
4,60,42,-25,1,2,AH2,1,1
4,60,68,-25,1,2,AH2,1,1
4,60,94,-25,1,2,AH2,1,1
4,61,16,-25,1,2,AH2,1,1
4,61,42,-25,1,2,AH2,1,1
4,61,68,-25,1,2,AH2,1,1
4,61,94,-25,1,2,AH2,1,1
4,62,16,-25,1,2,AH2,1,1
4,62,42,-25,1,2,AH2,1,1
4,62,68,-25,1,2,AH2,1,1
4,62,94,-25,1,2,AH2,1,1
4,63,16,-25,1,2,AH2,1,1
4,63,42,-25,1,2,AH2,1,1
4,63,68,-25,1,2,AH2,1,1
4,63,94,-25,1,2,AH2,1,1
10
308
________________ Appendix A: Sample MTO Format (16_classes.fmt)
and Output
A. Format Files
Model Number: model01
Ranges:
W 88069’ 4 1/2" Plant E 88069’ 4 1/2" Plant
S 88069’ 4 1/2" Plant N 88069’ 4 1/2" Plant
El -88069’ 4 1/2" Plant El 88069’ 4 1/2" Plant
309
________________
Report Manager User’s Guide - April 2002
310
________________ Appendix A: Sample MTO Format (17_seglist.fmt)
DIAM CLASS DGN AREA NO P&ID NO NOR OP P/T ALT OP P/T STM OUT HEAT TRACING COATING
LINE ID OVER THK MODEL NO P&ID NODES 1-2 NOR DN P/T ALT DN P/T CONSTR ST INSULATION CLEANING
UNIQUE NO AN FILE NO TESTING APPVL/HLD ST
and Output
A. Format Files
2097156 - 0 NA -
311
________________
Report Manager User’s Guide - April 2002
eporty
dextDiscrimination Number: model.dis
Path Name: f:roj60
Discrimination Data Description: single model file
Discrimination Data File Specification: model.dis
Discrimination Data File Location:
Network Address: hxiu eporty
dexis
Path Name: f:roj60
Model Number: cp_m02
Ranges:
W 88069’ 4 1/2" Plant E 88069’ 4 1/2" Plant
S 88069’ 4 1/2" Plant N 88069’ 4 1/2" Plant
El -88069’ 4 1/2" Plant El 88069’ 4 1/2" Plant
312
________________ Appendix A: Sample MTO Format (18_linelst.fmt)
and Output
A. Format Files
1,7,9,40,’[A40]’,2,B**Q5
1,7,67,16,1,1,’PIPING LINE LIST’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,7,1,1,’LINE ID’
1,9,31,34,1,1,’NOR OP P/T ALT OP P/T HEAT TRACING’
1,9,68,4,1,1,’AREA’
1,9,88,14,1,1,’SHT REV SPOOLS’
1,9,127,3,1,1,’REV’
1,10,9,8,1,-1,’DIAM ’
1,10,18,12,1,-1,’CLASS OR-TH’
1,10,31,10,1,-1,’NOR DN P/T’
1,10,42,10,1,-1,’ALT DN P/T’
1,10,53,14,1,-1,’INSULATION ’
1,10,68,4,1,-1,’NO ’
1,10,73,14,1,-1,’ISO NO ’
1,10,88,3,1,-1,’NO ’
1,10,92,3,1,-1,’NO ’
1,10,96,10,1,-1,’NOS ’
1,10,107,19,1,-1,’ORTHO NO ’
1,10,127,3,1,-1,’NO ’
6
4,11,1,21,’ˆˆˆ [A13]’,2,AH3S1,53,2
4,11,31,-5,’[F6.0]’,2,AH24,53,2
4,11,37,-4,’[F5.0]’,2,AH25,53,2
4,11,42,-5,’[F6.0]’,2,AH26,53,2
4,11,48,-4,’[F5.0]’,2,AH27,53,2
4,11,53,-3,1,2,AH17,53,2
4,11,57,-3,1,2,AH18,53,2
4,11,61,-4,’[F5.0]’,2,AH19,53,2
4,12,9,-8,1,2,AH11S2,53,2
4,12,18,-6,1,2,AH12S3,53,2
4,12,25,-5,1,2,AH23,53,2
4,12,31,-5,’[F6.0]’,2,AH28,53,2
4,12,37,-4,’[F5.0]’,2,AH29,53,2
4,12,42,-5,’[F6.0]’,2,AH30,53,2
4,12,48,-4,’[F5.0]’,2,AH31,53,2
4,12,53,-6,1,2,AH14S4,53,2
4,12,60,-7,1,2,AH15,53,2
LINE ID NOR OP P/T ALT OP P/T HEAT TRACING AREA SHT REV SPOOLS REV
DIAM CLASS OR-TH NOR DN P/T ALT DN P/T INSULATION NO ISO NO NO NO NOS ORTHO NO NO
313
________________
Report Manager User’s Guide - April 2002
314
________________ Appendix A: Sample MTO Format (18_linelst.fmt)
eportis
Path Name: f:roj60
Model Number: cp_m02
Ranges:
W 88069’ 4 1/2" Plant E 88069’ 4 1/2" Plant
S 88069’ 4 1/2" Plant N 88069’ 4 1/2" Plant
El -88069’ 4 1/2" Plant El 88069’ 4 1/2" Plant
and Output
A. Format Files
Ranges:
W 88069’ 4 1/2" Plant E 88069’ 4 1/2" Plant
S 88069’ 4 1/2" Plant N 88069’ 4 1/2" Plant
El -88069’ 4 1/2" Plant El 88069’ 4 1/2" Plant
315
________________
Report Manager User’s Guide - April 2002
316
________________
Appendix A: Sample MTO Format (21_dwg_id.fmt)
and Output
A. Format Files
317
________________
Report Manager User’s Guide - April 2002
LINE ID ____________
3900112-RF
0101-A
**390101-WC
180101-AC
180104-AC
**390105-WC
180105-AC
380105-WC
180111-AC
**390207-WC
180207-AC
390207-WC
180303-AC
180305-AC
180306-AC
400306-AC
**390307-W
180307-AC
**390308-WC
180308-AC
180310-AC
**390311-W
180311-AC
180311-W
180313-AC
180314-AC
180315-AC
180316-AC
180316-W
180318-AC
**390322-RF
**390401-WC
180401-AC
**390402-WC
**390403-WC
180404-W
180407-W
**390408-W
180408-AC
318
________________ Appendix A: Sample MTO Format (22_line_id.fmt)
390408-W
**390501-RF
183804-AC
and Output
A. Format Files
Network Address: hxiu eportis
Path Name: f:roj60
Model Number: cp_m02
Ranges:
W 88069’ 4 1/2" Plant E 88069’ 4 1/2" Plant
S 88069’ 4 1/2" Plant N 88069’ 4 1/2" Plant
El -88069’ 4 1/2" Plant El 88069’ 4 1/2" Plant
319
________________
Report Manager User’s Guide - April 2002
- 3/4 3/4 -
ENG-XX 180318-AC 2C0032
- 1 1 VAUSAHGAAA CSFF
**390105-WC 1C0031 GATR
- 1 1 VAUSAHGAAA CSFF
180104-AC 1C0031 GATR
- 1 1 VAUSAHGAAA CSFF
180105-AC 1C0031 GATR
320
________________ Appendix A: Sample MTO Format (23_comp.fmt)
- 1 1 VAUSAHGAAA CSFF
180318-AC 2C0032 GATR
- 1 1 VAUSAHGAAA CSFF
180401-AC 2C0032 GATR
- 3 3 VABBAHCAAA CSFF
180311-W 2C0032 GAT
- 3 3 VABBAHCAAA CSFF
183804-AC 2C0032 GAT
- 4 4 VAABAHCCAA CSFF
180105-AC 1C0031 GAT
- 4 4 VAABAHCCAA CSFF
180207-AC 1C0031 GAT
- 4 4 VAABAHCCAA CSFF
180306-AC 1C0031 GAT
and Output
A. Format Files
- 4 4 VAABAHCCAA CSFF
180308-AC 1C0031 GAT
- 4 4 VAABAHCCAA CSFF
400306-AC 1C0031 GAT
- 4 4 VABBAHCAAA CSFF
180311-AC 2C0032 GAT
- 4 4 VABBAHCAAA CSFF
180311-W 2C0032 GAT
- 4 4 VABBAHCAAA CSFF
180401-AC 2C0032 GAT
- 4 4 VABBAHCAAA CSFF
180408-AC 2C0032 GAT
- 4 4 VABBAHCAAA CSFF
183804-AC 2C0032 GAT
- 6 6 VAABAHCCAA CSFF
**390105-WC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
**390207-WC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
180104-AC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
180105-AC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
180207-AC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
180307-AC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
180401-AC 1C0031 GAT
- 6 6 VAABAHCCAA CSFF
400306-AC 1C0031 GAT
- 6 6 VABBAHCAAA CSFF
0101-A 2C0032 GAT
321
________________
Report Manager User’s Guide - April 2002
- 6 6 VABBAHCAAA CSFF
180401-AC 2C0032 GAT
- 8 8 VAABAHCCAA CSFF
180316-AC 1C0031 GAT
- 8 8 VABBAHCAAA CSFF
180318-AC 2C0032 GAT
- 4 4 VBABAHCFAA CSFF
**390101-WC 1C0031 GLO
- 4 4 VBABAHCFAA CSFF
180101-AC 1C0031 GLO
- 4 4 VBABAHCFAA CSFF
180105-AC 1C0031 GLO
- 4 4 VBABAHCFAA CSFF
180207-AC 1C0031 GLO
- 4 4 VBABAHCFAA CSFF
400306-AC 1C0031 GLO
322
________________ Appendix A: Sample MTO Format (27_comp_ld.fmt)
and Output
A. Format Files
! 1,6,124,2,1,1,[REV NO]
1,7,9,40,’[A40]’,2,B**Q5
1,7,52,46,1,1,’PIPING COMPONENTS LONG DESCRIPTION MTO SUMMARY’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,14,1,1,’CMDTY CODE NO=’
1,10,9,17,1,1,’LONG DESCRIPTION=’
1,17,28,14,1,-1,’LARGE END DIAM’
1,17,43,14,1,-1,’SMALL END DIAM’
1,17,58,13,1,-1,’LARGE END THK’
1,17,72,13,1,-1,’SMALL END THK’
1,17,86,4,1,-1,’FC ’
1,17,91,4,1,-1,’QTY ’
4,9,28,20,1,2,BG8C2,45,1
4,10,28,104,1,2,BM2C3,45,1
4,18,28,-8,1,2,BN49S5,45,1
4,18,43,-8,1,2,BN-49,45,1
4,18,58,-8,1,2,BN52,45,1
4,18,72,-8,1,2,BN-52,45,1
4,18,86,-4,1,2,BG10S6,45,1
4,18,91,-4,2,2,BS,45,1
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
323
________________
Report Manager User’s Guide - April 2002
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
LARGE END DIAM SMALL END DIAM LARGE END THK SMALL END THK FC QTY
324
________________ Appendix A: Sample MTO Format (28_pipe_ld.fmt)
and Output
A. Format Files
1,7,59,33,1,1,’PIPE LONG DESCRIPTION MTO SUMMARY’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,14,1,1,’CMDTY CODE NO=’
1,10,9,17,1,1,’LONG DESCRIPTION=’
1,17,28,8,1,-1,’NOM DIAM’
1,17,37,8,1,-1,’THK ’
1,17,46,4,1,-1,’FC ’
1,17,51,6,1,-1,’LENGTH’
4,9,28,20,1,2,BA12C2,45,1
4,10,28,104,1,2,BF2C3,45,1
4,18,28,-8,1,2,BA7S4,45,1
4,18,37,-8,1,2,BA9,45,1
4,18,46,-4,1,2,BA14S5,45,1
4,18,51,-30,1,2,BA22,45,1
325
________________
Report Manager User’s Guide - April 2002
326
________________ Appendix A: Sample MTO Format (29_pipspt1.fmt)
and Output
A. Format Files
1,7,9,40,’[A40]’,2,B**Q5
1,7,64,22,1,1,’PIPE SUPPORTS REPORT 1’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,10,1,1,’SUPPORT NO’
1,9,25,7,1,1,’LINE NO’
1,9,51,14,1,1,’NOR/ALT OP TMP’
1,9,66,21,1,1,’DETAILS FOR PIPE SHOP’
1,10,9,9,1,1,’UNIQUE NO’
1,10,25,11,1,1,’DGN AREA NO’
1,10,42,8,1,1,’MODEL NO’
1,10,51,10,1,1,’INSULATION’
1,10,66,24,1,1,’DETAILS FOR SUPPORT SHOP’
1,11,9,15,1,-1,’ ’
1,11,25,25,1,-1,’ISO NO SH NO’
1,11,51,14,1,-1,’CONSTR/HLD ST ’
1,11,66,50,1,-1,’ORIENTATION ’
4,12,9,-15,1,2,B*P2S1,51,4
4,12,25,-25,1,2,B*S2,51,4
4,12,51,-4,’[F5.0]’,2,B*S25,51,4
4,12,61,-4,’[F5.0]’,2,B*S27,51,4
4,12,66,50,1,2,B*P9,51,4
4,13,9,-11,3,2,B*P1S2,51,4
4,13,25,-10,1,2,B*S36,51,4
4,13,41,-9,1,2,B*U6,51,4
4,13,51,-4,1,2,B*S15,51,4
4,13,66,50,1,2,B*P10,51,4
4,14,25,-15,1,2,B*U1151,51,4
4,14,48,2,1,2,B*P20,51,4
4,14,51,-9,1,2,B*P16,51,4
4,14,64,-1,1,2,B*P17,51,4
4,14,66,20,1,2,B*P11,51,4
SUPP1 AC180207-6"-1C0031- 60 0
3145729 model_03 0
180207-AC - -
327
________________
Report Manager User’s Guide - April 2002
SUPP2 AC180207-6"-1C0031- 60 0
3145730 model_03 0
180207-AC - -
SUPP3 AC180207-6"-1C0031- 60 0
3145731 model_03 0
180207-AC - -
SUPP4 AC180207-6"-1C0031- 60 0
3145732 model_03 0
180207-AC - -
SUPP5 AC180207-6"-1C0031- 60 0
3145733 model_03 0
180207-AC - -
TEST1 AC400306-6"-1C0031- 60 0
524289 model01 0
400306-AC - -
TEST2 AC400306-4"-1C0031- 60 0
524290 model01 0
400306-AC - -
TEST3 AC400306-6"-1C0031- 60 0
524291 model01 0
400306-AC - -
328
________________ Appendix A: Sample MTO Format (29_pipspt1.fmt)
and Output
A. Format Files
329
________________
Report Manager User’s Guide - April 2002
180207-AC SUPP1 60 0
model_03 3145729 0
AC180207-6"-1C0031- - -
180207-AC SUPP2 60 0
model_03 3145730 0
AC180207-6"-1C0031- - -
330
________________ Appendix A: Sample MTO Format (30_pipspt2.fmt)
180207-AC SUPP3 60 0
model_03 3145731 0
AC180207-6"-1C0031- - -
180207-AC SUPP4 60 0
model_03 3145732 0
AC180207-6"-1C0031- - -
180207-AC SUPP5 60 0
model_03 3145733 0
AC180207-6"-1C0031- - -
400306-AC TEST1 60 0
model01 524289 0
AC400306-6"-1C0031- - -
and Output
A. Format Files
400306-AC TEST2 60 0
model01 524290 0
AC400306-4"-1C0031- - -
400306-AC TEST3 60 0
model01 524291 0
AC400306-6"-1C0031- - -
331
________________
Report Manager User’s Guide - April 2002
332
________________ Appendix A: Sample MTO Format (40_instr.fmt)
and Output
A. Format Files
1,6,112,3,1,1,’REV’
! 1,6,124,2,1,2,[REV NO]
1,7,9,40,’[A40]’,2,B**Q5
1,7,66,18,1,1,’INSTRUMENTS REPORT’
1,7,112,4,1,1,’DATE’
1,7,120,11,1,5
1,9,9,47,1,1,’TAG NO EQUIPMENT NO/LINE NO’
1,9,57,18,1,1,’CONSTR ST HOLD ST’
1,9,76,16,1,1,’END PREPARATIONS’
1,9,103,16,1,1,’POSITION IN SITE’
! 1,10,9,47,1,-1,’MODEL NO ’
1,10,9,47,1,-1,’ ’
1,10,57,18,1,-1,’DIAMETERS ’
1,10,76,26,1,-1,’END RATINGS ’
1,10,103,27,1,-1,’ ’
4,11,9,-20,1,2,B*G2S3,52,4
4,11,31,-25,1,2,B*I2,52,4
4,11,57,-9,1,2,B*G29,52,4
4,11,73,-2,1,2,B*G30,52,4
4,11,76,-8,1,2,B*G57,52,4
4,11,85,-8,1,2,B*G70,52,4
4,11,94,-8,1,2,B*G83,52,4
4,11,103,-27,1,2,B*K7,52,4
! 4,12,9,-9,1,2,B*K15,52,4
4,12,57,-6,1,2,B*G55,52,4
4,12,63,-6,1,2,B*G68,52,4
4,12,69,-6,1,2,B*G81,52,4
4,12,76,-8,1,2,B*G59,52,4
4,12,85,-8,1,2,B*G72,52,4
4,12,94,-8,1,2,B*G85,52,4
4,12,103,-27,1,2,B*K8,52,4
4,13,103,-27,1,2,B*K9,52,4
333
________________
Report Manager User’s Guide - April 2002
334
________________
Appendix A: Sample MTO Format (40_instr.fmt)
and Output
A. Format Files
335
________________
Report Manager User’s Guide - April 2002
336
________________ Appendix A: Sample MTO Format (60_pid_pip.fmt)
and Output
A. Format Files
1572955 0 None NH
337
________________
Report Manager User’s Guide - April 2002
338
________________ Appendix A: Sample MTO Format (65_pcalc.fmt)
and Output
A. Format Files
180314-AC 12 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180314-AC 10 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180315-AC 6 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180316-W 8 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180318-AC 8 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180318-AC 3/4 2C0032 100 60 0 0 0 0 0 0 A106-B S-XS S-XS _______
180401-AC 6 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180401-AC 6 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180401-AC 4 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180404-W 4 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180407-W 4 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
180408-AC 4 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
183804-AC 6 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
183804-AC 4 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
183804-AC 3 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
380105-WC 24 2C0032 100 60 0 0 0 0 0 0 A53-B *C100 S-STD _______
380105-WC 24 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
380105-WC 20 2C0032 100 60 0 0 0 0 0 0 A53-B *C100 S-STD _______
380105-WC 20 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
380105-WC 20 2C0032 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
380105-WC 16 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
380105-WC 12 1C0031 100 60 0 0 0 0 0 0 A53-B S-STD S-STD _______
339
________________
Report Manager User’s Guide - April 2002
340
________________ Appendix A: Sample MTO Format (68_chkmdl.fmt)
and Output
A. Format Files
1,7,120,11,1,5
1,9,9,-25,1,-1,’Commodity Code’
9
4,11,19,-50,’LINE NUMBER: [A30]’,-2,BI2G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,BB2G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,B*I2G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,BT1G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,BX1G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,B**K2G1,45,2
7
4,11,19,-50,’LINE NUMBER: [A30]’,-2,B*S2G1,45,2
8
4,13,9,-25,1,2,BG8S2,45,2
7
4,13,9,-25,1,2,BA12S2,45,2
7
4,13,9,-25,1,2,B*G2S2,45,2
7
4,13,9,-25,1,2,BT13S2,45,2
7
4,13,9,-25,1,2,BX12S2,45,2
7
4,13,9,-25,1,2,B**J2S2,45,2
7
4,13,9,-25,1,2,B*P12S2,45,2
10
WAAAAAWAAA
PAAAAAWAAA
WAAAAAWAAA
WOAAAAWAFA
341
________________
Report Manager User’s Guide - April 2002
PAAJVAWABT
WAAAAAWAAA
WTAAAAWAAA
PAAAAAWAAA
FAAABAWAAA
GJGABZZADA
WAAAAAWAAA
PAAAAAWAAA
XDAABZZQSG
POCAAAOAAE
PPCAAAOAAE
**IN-0311-1
**IN-0311-2
FGPBBAWAAA
WRBAAAWAAA
PAAAAAWAAA
**38FE-585
XDABBZZQSG
YZZZHZZFFF
WAAAAAWAAA
FAAABAWAAA
GJGABZZADA
VBABAHCFAA
XDAABZZQSG
YZZZHZZFFF
WRBAAAWAAA
POCAAAOAAE
342
________________
Appendix A: Sample MTO Format (68_chkmdl.fmt)
SCAQZZZAAA
VAUSAHGAAA
and Output
A. Format Files
343
________________
Report Manager User’s Guide - April 2002
Sample Format – The sample format file for creating drawing reports are generally the same as for MTO
reports.
344
________________
Appendix A: Spec Reporting (Reference Data Manager)
Sample Format – The sample format files for Spec reporting is piping_rdb.fmt and is delivered in the
˜\pddata\sample\format\ directory.
and Output
A. Format Files
report_type=601 ! Piping RDB Reports
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Material Class Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
2,3,10,-40,1,1,’Corporate Headquarters’
2,4,10,-40,1,1,’Intergraph Corporation’
2,5,10,-40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,-40,1,1,’(205)730-2000’
2,3,90,-20,1,2,B**Q5
2,3,110,-20,1,2,B**Q9
2,4,90,-20,1,2,B**Q6
2,5,90,-20,1,2,B**Q7
2,6,90,-20,1,2,B**Q8
1,9,1,-10,1,-1,’#’
1,9,15,-10,1,-1,’Class’
1,9,30,-80,1,-1,’Materials Description’
1,8,115,-14,1,-1,’Standard Notes’
1,9,115,-3,1,-1,’A’
1,9,125,-3,1,-1,’B’
4,11,1,-10,2,2,CYB,45,1
4,11,15,-10,1,2,CB2,45,1
4,11,30,-80,1,2,CB9,45,1
4,11,115,-3,2,2,CB19,45,1
4,11,125,-3,2,2,CB20,45,1
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Commodity Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
1,9,1,-10,1,-1,’Item’
1,9,15,-15,1,-1,’1st Size Low’
1,9,30,-15,1,-1,’1st Size High’
1,9,50,-60,1,-1,’Material Description’
1,8,115,-14,1,-1,’Standard Notes’
1,9,115,-3,1,-1,’A’
1,9,125,-3,1,-1,’B’
4,11,1,-10,1,2,CC3,45,2
4,11,15,-15,1,2,CC6,45,2
4,11,30,-15,1,2,CC7,45,2
4,11,45,-65,1,2,CD1,45,2
4,11,115,-3,2,2,CC26,45,2
4,11,125,-3,2,2,CC27,45,2
345
________________
Report Manager User’s Guide - April 2002
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Piping Tap Data’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
1,9,1,-16,1,-1,’Tap Diameter’
1,9,20,-100,1,-1,’Tap Description’
4,16,1,-16,1,2,CI3,40,1
4,16,20,100,1,2,CJ1,40,1
5
1,1,1,-13,1,1,’Date/Time :’
1,1,14,-23,1,5
1,2,30,-60,1,-1,’PDS SPEC REPORT- Standard Notes Used in Report’
1,1,120,-6,1,1,’Page: ’
1,1,127,-3,2,4
4,9,1,-10,1,-1,’Note #’
4,9,20,-110,1,-1,’Standard Note’
4,11,1,-10,2,2,CZ2,40,3
4,11,20,-110,1,2,CZ3,40,3
346
________________
Appendix A: Table Checker Reporting (Reference Data Manager)
Sample Format – The sample format files for Table Checker reporting are tbl_chk_1.fmt through tbl_chk_3.fmt
and are delivered in the ˜\pddata\sample\format\ directory.
and Output
A. Format Files
Sample Table Checker Format (tbl_chk_3.fmt)
report_type=601 ! Piping RDB Reports
1,1,5,-23,1,5
1,2,30,-30,1,-1,’SIZE-DEPENDENT SPEC DATA’
1,1,70,-6,1,1,’Page: ’
1,1,77,-3,2,4
1,3,5,-20,1,1,’Piping Class:’
4,3,30,12,1,2,CC2,1,1
1,4,5,-20,1,1,’AABBCC:’
4,4,30,40,1,2,CC3,1,1
1,6,5,-10,1,1,’1st Size’
1,7,5,-20,1,-1,’Weight ’
4,8,5,-10,1,2,CDT1S0,56,4
4,9,5,20,1,2,CDT9S0,56,4
1,6,17,-10,1,1,’2nd Size’
1,7,17,-20,1,-1,’ ’
4,8,17,-10,1,2,CDT2S0,56,4
1,6,50,-50,1,1,’Physical Data’
1,7,30,-32,1,-1,’Generic’
1,7,65,-32,1,-1,’Specific’
1,7,100,-32,1,-1,’Sub-Component’
4,9,30,32,1,2,CDT7S0,56,4
4,9,65,32,1,2,CDT8S0,56,4
4,9,100,32,1,2,CDT11S0,56,4
3/4" 3/4"
1.2975In, 0.375In
1" 1"
1.558In, 0.4375In
347
________________
Report Manager User’s Guide - April 2002
1-1/2" 1-1/2"
2.155In, 0.5625In
2" 2"
2.6563In, 0.625In
22-Feb-93 Page: 2
SIZE-DEPENDENT SPEC DATA ________________________
Piping Class: GD2
AABBCC: 6Q1C01
3/4" 3/4"
1.2975In, 0.375In
1" 1"
1.558In, 0.4375In
1-1/2" 1-1/2"
2.155In, 0.5625In
2" 2"
2.6563In, 0.625In
22-Feb-93 Page: 3
SIZE-DEPENDENT SPEC DATA ________________________
Piping Class: GD2
AABBCC: 6Q1C01
3" 3"
0.916SFF, 3.5In, 1.75In
3-1/2" 3-1/2"
1.047SFF, 4In, 2In
4" 4"
1.178SFF, 4.5In, 2.25In
6" 6"
1.73SFF, 6.625In, 3.3125In
8" 8"
2.26SFF, 8.625In, 4.3125In
348
________________
Appendix A: Project Reporting (Project Administrator)
Sample Format – The sample format files for Project reporting are: model_mgt.fmt, iso_mgt.fmt, iso_rev.fmt
and are delivered in the ˜\pdprojec\sample\ directory.
and Output
A. Format Files
1,1,1,13,1,1,’Date/Time :’
1,1,14,23,1,3
1,1,50,40,1,1,’MODEL REPORT’
1,1,120,6,1,1,’Page: ’
1,1,127,3,2,4
2,3,10,40,1,1,’Corporate Headquarters’
2,4,10,40,1,1,’Intergraph Corporation’
2,5,10,40,1,1,’Huntsville, Alabama 35894-0001’
2,6,10,40,1,1,’(205)730-2000’
2,3,70,40,1,2,DA101#2
2,4,70,40,1,2,DA101#3
2,5,70,40,1,2,DA101#4
2,6,70,40,1,2,DA101#5
2,7,70,40,1,2,DA101#6
4,9,5,10,1,-1,’Area’
4,9,20,10,1,-1,’Model No.’
4,9,35,40,1,-1,’Description’
4,9,80,45,1,-1,’General Info’
9
4,11,5,-10,1,-2,DA113#3#3C2,45,5
4,11,35,-40,1,2,DA113#3#4C3,45,5
4,11,80,-45,’Discipline: [A20]’,2,DA113#2#2C1,45,5
4,12,15,-40,1,2,DA113#3#5C4,45,5
4,12,60,-40,1,2,DA113#3#8C5,45,5
4,13,15,-40,1,2,DA113#3#6C6,45,5
4,13,60,-40,1,2,DA113#3#9C7,45,5
4,14,15,-40,1,2,DA113#3#7C8,45,5
4,14,60,-40,1,2,DA113#3#10C9,45,5
4,16,20,-10,1,2,DA113#5S4,45,5
4,16,35,-40,1,2,DA113#6,45,5
4,16,80,-45,’Revised on [A30]’,2,DA113#14,45,5
4,17,80,-45,’Verified on [A30]’,2,DA113#13,45,5
4,17,35,-32,’Node= [A26]’,2,DA113#9,45,5
4,18,35,-42,’Path= [A36]’,2,DA113#8,45,5
4,19,35,-20,’File= [A14]’,2,DA113#7,45,5
10
349
________________
Report Manager User’s Guide - April 2002
Sample Format – The sample format files for Interference reporting is clash_mgt.fmt and is delivered in the
˜\pdclash\sample\ directory.
1,13,2,20,1,-1,’Clash Type/Status/ID’
4,15,2,-20,1,2,DA132#9S5,45,5
4,16,2,-20,1,2,DA132#2S6,45,5
4,17,2,-20,3,2,DA132#1,45,5
1,13,24,20,1,-1,’Item Name’
4,15,24,-20,1,2,DA132#3#5,45,5
4,16,24,-40,1,2,DA132#3#6,45,5
4,17,24,-20,1,2,DA132#4#5,45,5
4,18,24,-40,1,2,DA132#4#6,45,5
1,13,66,6,1,-1,’Entity’
4,15,66,-6,2,2,DA132#3#2,45,5
4,17,66,-6,2,2,DA132#4#2,45,5
1,13,74,10,1,-1,’Occurrence’
4,15,74,-10,3,2,DA132#3#3,45,5
4,17,74,-10,3,2,DA132#4#3,45,5
350
________________ Appendix B: Revise AND/OR Relations Examples
In the window below, all of the logical relations are set to AND, as they are in the default
setting.
With the above settings, the only components that will be reported are those that meet the
defined segment criteria AND the criteria defined for all four of the component data
categories.
EXAMPLE 2
B. Examples
Assume that the search criteria has been defined with the following values:
pipe supports have been defined to have a fabrication category of Contractor Supplied,
Shop Fabricated.
In this example, the logical relation for Instrument Components has been set to OR as shown
below.
351
________________
Report Manager User’s Guide - April 2002
352
________________ Appendix B: Pipeline Discrimination Data Example
B. Examples
2. Select a project from the list.
3. Select the Report Manager option from the Plant Design System form.
353
________________
Report Manager User’s Guide - April 2002
4. Select the Report Discrimination Data option from the Report Manager form.
354
________________ Appendix B: Pipeline Discrimination Data Example
B. Examples
9. Select a piping model from the list and select Confirm.
355
________________
Report Manager User’s Guide - April 2002
356
________________ Appendix B: Pipeline Discrimination Data Example
B. Examples
14. Select a fluid code from the list and select Confirm.
357
________________
Report Manager User’s Guide - April 2002
358
________________ Appendix B: Pipeline Discrimination Data Example
17.
B. Examples
The system returns to the Discrimination Data Creation form.
The system updates the database and creates the discrimination data.
359
________________
Report Manager User’s Guide - April 2002
360
________________Appendix B: Gate Valve Discrimination Data Example
B. Examples
2. Key in the required information.
361
________________
Report Manager User’s Guide - April 2002
362
________________Appendix B: Gate Valve Discrimination Data Example
B. Examples
9. Select the commodity_name option.
363
________________
Report Manager User’s Guide - April 2002
364
________________
Appendix B: Gate Valve Discrimination Data Example
B. Examples
13. Select the Define Volume option.
365
________________
Report Manager User’s Guide - April 2002
366
________________ Appendix B: Gate Valve Discrimination Data Example
B. Examples
367
________________
Report Manager User’s Guide - April 2002
368
________________ Appendix B: Equipment Discrimination Data Example
B. Examples
5. Select an equipment model from the list and select Confirm.
369
________________
Report Manager User’s Guide - April 2002
370
________________ Index
Index
A E
almost precise bolt calculation 143 equipment discrimination data example 368
Approval form 76 example
approving reports 76 equipment discrimination data 368
attributes gate valve discrimination data 361
specifying 52 interference format file 126
MTO format file 108
B pipeline discrimination data 353
bends project control format file 126
induction 159 revise AND OR relations 351
bolts 148 spec
commodity code 139, 144 reporting
length 139, 141 format file 118
almost precise 143
precise 143 F
roundoff 142 field
priority selection 153 fit length 140
roundoff 139 format file 83
options 142 indices
spec break selection 153 MTO reporting (with implied items) 91
output fields 90
C syntax 84
center of gravity reporting 131 column 86
COG (center of gravity) 131 data_type 86
commodity codes 140 field_functions 85
bolts 144 field_len 86
size field_type 87
dependent 163 row 86
Index
independent 162 format files
control sort 129 sample 111
conventions
reporting 18 G
gasket search 145
D gaskets 140, 152
data commodity name 141
search criteria 20 priority selection 153
database spec break selection 153
table/column information 171 gate valve
reporting 184 discrimination data example 361
definition data 19 gate valve discrimination data example 361
description global sort 129
libraries 171 gravity reporting 131
discrimination data
example for gate valve 361 I
file 20 implied items 135
indices 91, 97
371
________________
Report Manager User’s Guide - April 2002
372
________________ Index
Index
independent reporting 161, 162
R sorting 129
relationships for table attributes 124 example 130
report sorts 129
definition data 19 control 129
files 19 global 129
format normal 129
file spec
indices implied
interference reporting 122 items 135
project reporting 122 materials
sorting 129 reporting weights and center of gravities
syntax 84 131
format file 83 reporting
output 20 format file
processing 23 example 118
records 19 indices 113
report type line 89 instrument data 115
types 24 piping
373
________________
Report Manager User’s Guide - April 2002
spec (continued) W
reporting (continued) weight reporting 131
indices (continued) weld
piping (continued) data 157
commodity data 114 length 157
materials class data 114 type field fit length 157
specialty data 114
reporting
options 117
tap properties data 117
special rules for mating implied items 146
specialty
material description library 180
specialty material description library 171
spec-implied items 136
syntax
format file 84
column 86
data_type 86
field_functions 85
field_len 86
field_type 87
row 86
system
commodity code 163
T
table
attributes relationships 124
interference data 125
project control data 124
bolt length 141
checker
indices 117
implied items 135
table-implied items 137
tables 171
column information 171
type
report line 89
typefaces 13
types
reports 24
U
understanding
report data 19
format
file 20
report
output 20
374
Report Manager
(PD_Report)
User’s Guide Addendum
February 2003
DPDS3-PB-200035B
For PDS version 07.02.00.**
Table of Contents
The Report Manager Interface (replaces 2.0) .......................................................... 377
Sample Interference Report Format Files (replaces 3.6 subsection) ....................... 379
Weld Data (replaces 4.7).......................................................................................... 380
Project Control Database (replaces 5.3.3)................................................................ 381
Model Management Data (replaces 5.3.4) ............................................................... 384
Drawing Management Data (replaces 5.3.6) ........................................................... 386
Interference Management Data (replaces 5.3.7) ...................................................... 389
FrameWorks Plus Data (replaces 5.3.13)................................................................. 391
Material Takeoff Database (replaces 5.3.14) ........................................................... 397
376
The Report Manager Interface (replaces 2.0)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (pp 27-28 in the PDS
7.1 version of the document).
The following information has been added:
• Clarification of Copy Format/Search Data from Another Project
command
See the following text for details.
To access the PDS Report Manager environment, choose Report Manager from the
Plant Design System Environment form.
Options
Report Format — Displays the Report Format form, which you can use to create,
revise, copy, or delete the record of a format file (not the format file). For more
information, see Report Format Form, page 29.
377
Report Manager User’s Guide Addendum – February 2003
Report Discrimination Data — Displays the Discrimination Data form, which you
can use to create, revise, copy, or delete the record of a discrimination data file as
well as the file itself. For more information, see Discrimination Data Form, page 35.
Report Search Criteria — Displays the Search Criteria Data form, which enables
you to create, revise, copy, or delete the record of the search criteria data file. The
Create, Copy, and Revise options also affect the actual search criteria data file. The
Delete option deletes only the record of the search criteria data file, since the data file
itself may be used by other projects. For more information, see Search Criteria Data
Form, page 47.
Copy Format/Search Data from Another Project — Enables you to copy the
format and search data (found in pdtable_142, Report Format Data, and pdtable_145,
Report Search Criteria Data) from other projects into the project control database for
the active project. By copying this data, you can have several different projects share
format and search information. When you choose this option, a list of available
projects is displayed. Select the project from which you want to copy report data, and
then choose Accept.
Note: This command does not copy report formats or search criteria whose format or
search numbers already exist in the destination project.
Report — Displays the Report form, which you can use to create, revise, delete, and
approve report records and report files. For more information, see Report Form, page
65.
Report Management Data — Displays the Report Management Defaults form,
which you can use to create a record in the project control database of the default
nodename and path for the report definition files. This option is primarily used for
setup. For more information, see Report Management Defaults Form, page 80.
378
Sample Interference Report Format Files
(replaces 3.6 subsection)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (p. 128 in the PDS 7.1
version of the document).
The following information has been added:
• Report format files ifc_4.fmt and ifc_5.fmt
See the following text for details.
The following examples are delivered in the pdclash\sample\ directory.
clash_mgt.fmt — This format file reports interference checker data.
ifc_1.fmt — This format file reports the XYZ volume of the clashing items. It should
be used while reporting on an area and is sorted by Approval Status, Clash Type, and
Unique Clash ID.
ifc_2.fmt — This format file reports clashing items and can be used to easily
compare interference runs generated from different versions of software. It should be
used while reporting on an area and is sorted by Approval Status, Clash Type, and
Unique Clash ID.
ifc_3.fmt — This format file reports clashing items. It should be used while reporting
on an area and is sorted by Approval Status, Clash Type, and Unique Clash ID.
ifc_4.fmt — This format file reports the XYZ volume of the clashing items. It should
be used while reporting on an area and is sorted by Approval Status, Clash Pair Type
(pdtable_133), Area Index Number, and Recent Sequence Number.
ifc_5.fmt — This format file reports the XYZ volume of the clashing items. It should
be used while reporting on an area and is sorted by Approval Status, Clash Type
(pdtable_132), Area Index Number, and Recent Sequence Number. This format file is
similar to ifc_1.fmt, but it reports env_pair_type for each clash in addition to the other
reported data.
379
Report Manager User’s Guide Addendum – February 2003
380
Project Control Database (replaces 5.3.3)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (pp 199-200 in the PDS
7.1 version of the document).
The following information has been added:
• Pdtable_105 – Site Description Data
• Site_ID attribute in pdtable_101
• Note regarding pdtable_101 in PDS 2D
See the following text for details.
Table 101 – Project Description Data
Note: Both PDS 3D and PDS 2D use pdtable_101. For PDS 7.2, a new attribute,
site_id, has been added to the table. To use the updated table with PDS 2D, the
following line must be added at the appropriate location in the project attribute
file:
1200 site_id A10 ‘ ‘ 0 1 ‘Site ID’ ‘a10’
To see or use the attribute in PDS 2D, you must also add the attribute number,
630, to any list in a pertinent formlist and modify or add formats where necessary
to use in reports.
1 system_unique_no integer ................................. 3
2 project_no character(15) ........................... 1
3 project_name character(40) ........................... 1
4 job_no character(40) ........................... 1
5 company_name character(40) ........................... 1
6 plant_name character(40) ........................... 1
7 site_id character(10) ........................... 1
381
Report Manager User’s Guide Addendum – February 2003
382
9 min_pip_partition integer ................................. 3
10 max_pip_partition integer ................................. 3
11 min_eqp_partition integer ................................. 3
12 max_eqp_partition integer ................................. 3
13 master_flag short ................................... 2
383
Report Manager User’s Guide Addendum – February 2003
384
Table 114 - Piping Model Data
1 partition_no short ................................... 2
2 max_segment_number integer ................................. 3
3 max_piping_number integer ................................. 3
4 max_pipe_number integer ................................. 3
5 max_instr_number integer ................................. 3
6 max_support_number integer ................................. 3
385
Report Manager User’s Guide Addendum – February 2003
386
6 saved_view_name character(6) ............................ 1
7 viewing_direction short (SN1620 optional) ..... 1
8 composition_status short (SN1630) .............. 1
9 dwg_view_x_low double .................................. 1
10 dwg_view_y_low double .................................. 1
11 dwg_view_z_low double .................................. 1
12 dwg_view_x_high double .................................. 1
13 dwg_view_y_high double .................................. 1
14 dwg_view_z_high double .................................. 1
15 vhl_category_index short ................................... 2
16 drawing_view_type short ................................... 2
387
Report Manager User’s Guide Addendum – February 2003
388
Interference Management Data (replaces
5.3.7)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (pp 205-206 in the PDS
7.1 version of the document).
The following information has been added:
• Env_pair_type attribute in pdtable_133
See the following text for details.
Table 131 – Clash Management Data
1 system_unique_no integer index 1 ............... 3
2 discipline_indx_no short ................................... 2
3 area_index_no short ................................... 2
4 unique_sequence_no integer ................................. 3
5 completion_date integer ................................. 3
6 control_user_no short ................................... 2
7 env_creation_date integer ................................. 3
8 clash_check_option short (SN1208) ............ 1
9 volume_filter_opt short (SN1209) .............. 1
10 volume_low_x integer ................................. 3
11 volume_low_y integer ................................. 3
12 volume_low_z integer ................................. 3
13 volume_high_x integer ................................. 3
14 volume_high_y integer ................................. 3
15 volume_high_z integer ................................. 3
389
Report Manager User’s Guide Addendum – February 2003
390
FrameWorks Plus Data (replaces 5.3.13)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (pp 218-220 in the PDS
7.1 version of the document).
The following information has been added or modified:
• New tables 510, 533, 546, 548, and 550
• Attributes 14-16 in table 500
• Attributes 37-77 in table 532
• Attributes 29 and 30 in table 534
• Attributes 20-39 in table 536
• Changed attribute 13 in table 532 from member_status to
design_status
• Changed data type for attribute 33 in table 532 from character(12)
to character(14)
• Removed rotation and radius attributes from table 536
See the following text for details.
Note: You can change the name of any attribute if necessary; however, you cannot
move the attribute to a different location. Additionally, the following restrictions
apply:
All model_index_no attribute names, if modified, must have the same name as is
used in the pdtable_900.
All table_no attribute names, if modified, must have the same name as is used in
the pdtable_910.
Weight calculations for members with cutbacks are based on the member
graphical representation, which does not include the section fillets. Weight
calculations for members without cutbacks are based on the section area from the
section table, which includes the section fillets.
391
Report Manager User’s Guide Addendum – February 2003
392
42 buoyancy_val double .................................. 5
43 assembly1 short ................................... 2
44 assembly2 short ................................... 2
45 assembly3 short ................................... 2
46 coatings short ................................... 2
47 end1_connections short ................................... 2
48 end2_connections short ................................... 2
49 fabr_member_id integer ................................. 3
50 fabr_name short ................................... 2
51 fabr_prebuymark character(25) ........................... 1
52 fabr_note short ................................... 2
53 member_subtype short ................................... 2
54 piecemark character(25) ........................... 1
55 user_Attrib1 short ................................... 2
56 user_Attrib2 short ................................... 2
57 user_Attrib3 short ................................... 2
58 user_Attrib4 short ................................... 2
59 user_Attrib5 short ................................... 2
60 end1_RBJcategory short ................................... 2
61 end2_RBJcategory short ................................... 2
62 end1_RBJtype short ................................... 2
63 end2_RBJtype short ................................... 2
64 end1_offshRBJmode short ................................... 2
65 end2_offshRBJmode short ................................... 2
66 end1_secondaryID integer ................................. 3
67 end2_secondaryID integer ................................. 3
68 end1_supportID integer ................................. 3
69 end2_supportID integer ................................. 3
70 end1_clearenceReqd double .................................. 5
71 end2_clearenceReqd double .................................. 5
72 end1_overlapReqd double .................................. 5
73 end2_overlapReqd double .................................. 5
74 buoyancy double .................................. 5
75 cob_x double .................................. 5
76 cob_y double .................................. 5
77 cob_z double .................................. 5
393
Report Manager User’s Guide Addendum – February 2003
394
31 fabr_note short ................................... 2
32 member_subtype short ................................... 2
33 piecemark character(25) ........................... 1
34 user_attrib1 short ................................... 2
35 user_attrib2 short ................................... 2
36 user_attrib3 short ................................... 2
37 user_attrib4 short ................................... 2
38 user_attrib5 short ................................... 2
39 top_surf_area double .................................. 5
395
Report Manager User’s Guide Addendum – February 2003
396
Material Takeoff Database (replaces 5.3.14)
Note: The information in this section supersedes the information in the corresponding
section of previous versions of the Report Manager User’s Guide (pp 221-237 in the PDS
7.1 version of the document).
The following information has been added or modified:
• cp[1-5]_type attributes in pdtable_34 and pdtable_67
• model_status attribute in pdtable_900
• Weld ownership note in pdtable_130 section
• Changed commodity code attributes to character(25)
See the following text for details.
In tables 12, 21, 22, 34, 50, 67 and 80, any user-defined attributes will appear after the
attributes defined in the design and equipment ddl files, and the material data attributes
defined in the mto.ddl file will appear after the delivered attributes and any user-defined
attributes.
Notes on the Material Data Publisher Data Model
If there are already user-defined attributes added to the project, and if these attributes
have names which clash with attribute names in the mto.ddl file, the attributes in
the mto.ddl file can be changed in accordance with the restrictions noted in the
mto.ddl file. Currently these restrictions are:
1. Each partition_no attribute should have the same name as it is named in
Table 900.
2. Each table_no attribute should have the same name as it is named in Table
920.
MDP tables are not partitioned per model. The partition_no attribute is in all
the MDP Tables containing model specific data.
Table Attribute Relationships
All attributes named idx_xx (or ending with idx_xx), where xx is a number, are
links to the system_unique_no attribute in Table xx. For example, idx_12,
cp1_idx_12, and end1_idx_12 are links to Table 12, while idx_80 is a link
to the system_unique_number in Table 80.
All attributes named partition_no (or ending with partition_no) are links
to the partition_no attribute in Table 900. The partition_no attributes in
Tables 21 and 22 refer to equipment models, and the partition_no attributes in
other tables refer to piping models. Also, in Table 170, if the table_no attribute is
21 or 22 then the table refers to the equipment model with that partition_no.
Otherwise it refers to a piping model with that partition_no.
397
Report Manager User’s Guide Addendum – February 2003
398
NPD, which means that this attribute is a NPD attribute, with the
nominal piping diameter in coded form. All these attributes have
mirrored attributes in the same tables with name npd, which contains
the real NPD value in NPD units.
In the following listings, the line USER-DEFINED ATTRIBUTES (if
applicable) specifies the location of the user-defined attributes in relation to the
delivered attributes and material data attributes.
Table 12 – Piping Segments
1 system_unique_no integer index 1 1
2 line_number_label character(40) 1
3 line_id character(24) .......................... 1
4 unit_number character(12) .......................... 1
5 unit_code character(3) .......................... 1
6 module_no character(16) .......................... 1
7 package_system_no character(12) .......................... 1
8 train_number character(2) .......................... 1
9 fluid_code short (SN125) ............... 1
10 line_sequence_no character(16) .......................... 1
11 nominal_piping_dia short ............................(NPD). 1
12 piping_mater_class character(16) .......................... 1
13 gasket_separation character(8) .......................... 1
14 insulation_purpose short (SN220) ............... 1
15 insulation_thick double (ins thick units)....... 1
16 insulation_density double (SN1074 units).......... 5
17 heat_tracing_reqmt short (SN200) ............... 1
18 heat_tracing_media short (SN210) ............... 1
19 heat_tracing_temp double ................................. 5
20 construction_stat short (SN130) ............... 1
21 hold_status short (SN50) ................ 1
22 approval_status short (SN35) ................ 1
23 schedule_override character(8) (SN332)................. 1
24 nor_oper_pres double ................................. 5
25 nor_oper_temp double ................................. 5
26 alt_oper_pres double ................................. 5
27 alt_oper_temp double ................................. 5
28 nor_dgn_pres double ................................. 5
29 nor_dgn_temp double ................................. 5
30 alt_dgn_pres double ................................. 5
31 alt_dgn_temp double ................................. 5
32 steam_outlet_temp double ................................. 5
33 mater_of_construct character(6) .......................... 1
34 safety_class short (SN340) ............... 1
35 design_standard short (SN570) ............... 1
36 design_area_number character(10) .......................... 1
37 design_resp short (SN160) ............... 1
38 construction_resp short (SN160) ............... 1
39 supply_resp short (SN160) ............... 1
40 coating_reqmts short (SN190) ............... 1
41 cleaning_reqmts short (SN230) ............... 1
42 fluid_category character(4) ........................... 1
43 nor_op_pres_units short (SN1064) .............. 1
44 nor_op_temp_units short (SN1056) .............. 1
45 alt_op_pres_units short (SN1064) .............. 1
399
Report Manager User’s Guide Addendum – February 2003
Table 21 – Equipment
1 equip_indx_no integer index 1
2 equip_no character(30) .......................... 1
3 equip_descr_1 character(40) .......................... 1
4 equip_descr_2 character(40) .......................... 1
5 tutorial_no character(6) ........................... 1
6 equip_class character(2) ........................... 1
7 dry_weight double ................................. 5
8 oper_weight_1 double ................................. 5
9 oper_weight_2 double ................................. 5
10 insulation_thk double ................................. 5
11 construction_stat short (SN130) ................ 1
12 equipment_division short (SN69) ................ 1
13 approval_status short (SN35) ................ 1
400
1 partition_no short .................................. 2
Table 22 – Nozzles
1 nozzle_indx_no integer
2 nozzle_no character(10) .......................... 1
3 equip_index integer ................................ 3
4 nominal_piping_dia short ............................(NPD). 1
5 rating character(8) ........................... 1
6 preparation short (SN3300) ............... 1
7 piping_mater_class character(16) .......................... 1
8 unit_no character(12) .......................... 1
9 fluid_code short (SN125) ................ 1
10 unit_code character(3) ........................... 1
11 line_sequence_no character(16) .......................... 1
12 heat_tracing_reqmt short (SN200) ................ 1
13 heat_tracing_media short (SN210) ................ 1
14 insulation_purpose short (SN220) ................ 1
15 insulation_thk double ................................. 5
16 table_suffix short (SN576) ................ 1
17 service character(20) .......................... 1
18 schedule_thickness character(8) ........................... 1
19 nor_therm_growth_X double ................................. 5
20 nor_therm_growth_Y double ................................. 5
21 nor_therm_growth_Z double ................................. 5
22 alt_therm_growth_X double ................................. 5
23 alt_therm_growth_Y double ................................. 5
24 alt_therm_growth_Z double ................................. 5
25 construction_stat short (SN130) ................ 1
401
Report Manager User’s Guide Addendum – February 2003
402
52 cp_1_sch_thk character(8) (SN332) ............... 1
53 cp_1_rating character(8) ........................... 1
54 cp_1_face_to_ctr double ................................. 5
55 cp_1_weld_no character(8) ........................... 1
56 cp_1_weld_type short (SN1100)/400 (bolt option) 1
57 cp_1_gasket_gap double ................................. 5
58 cp_1_gasket_option short (SN400) ............... 1
59 cp_1_stress_node short .................................. 2
60 cp_1_stress_factor double ................................. 5
61 cp_1_head_loss double ................................. 5
403
Report Manager User’s Guide Addendum – February 2003
Table 50 -- Pipes
1 system_unique_no integer index 1
2 piping_comp_no character(20) .......................... 1
3 commodity_name character(6) ........................... 1
4 model_code character(6) ........................... 1
5 option_code short (SN400) ............... 1
404
6 maximum_temp double ................................. 5
7 nominal_piping_dia short ............................(NPD). 1
8 outside_diameter double .....................(Dist. NPD). 1
9 schedule_thickness character(8) (SN332) ............... 1
10 sched_thick_basis character(8) (SN332) ............... 1
11 rating character(8) ........................... 1
12 commodity_code character(16) .......................... 1
13 MTO_requirements short (SN365) ............... 1
14 fabrication_cat short (SN180) ............... 1
15 source_of_data short (SN425) ............... 1
16 PDS_sort_code character(6) ........................... 1
17 geometric_standard short (SN575) ............... 1
18 weight_code short (SN578) ............... 1
19 table_suffix_green short (SN576) ............... 1
20 table_suffix_red short (SN577) ............... 1
21 materials_grade short (SN145) ............... 1
22 pipe_length double ...................(Dist. Model). 1
23 surface_area double (SN1010 units) ........ 5
24 empty_weight double (SN1028 units) ........ 5
25 water_weight double (SN1028 units) ........ 5
26 cold_spring_length double ...................(Dist. Model). 1
27 construction_stat short (SN130) ............... 1
28 hold_status short (SN50) ................ 1
29 heat_tracing_reqmt short (SN200) ............... 1
30 heat_tracing_media short (SN210) ............... 1
31 heat_tracing_temp double ................................. 5
32 iso_dwg_index_no integer ................................ 3
33 isometric_sheet_no character(2) ........................... 1
34 piece_mark_no character(60) .......................... 1
35 color_code character(8) ........................... 1
36 piping_assembly character(12) .......................... 1
37 component_group_no short .................................. 2
38 remarks character(50) .......................... 1
39 standard_note_no_a short (SN499) ............. 2 or 1
40 standard_note_no_b short (SN499) ............. 2 or 1
41 end_1_end_prep short (SN330) ............... 1
42 end_1_weld_no character(8) ........................... 1
43 end_1_weld_type short (SN1100)/400 (bolt option) 1
44 end_1_gasket_gap double ...................(Dist. Model). 1
45 end_1_gasket_opt short (SN400) ............... 1
46 end_1_stress_node short .................................. 2
47 end_1_stres_int double ................................. 5
48 end_1_head_loss double ................................. 5
49 end_2_end_prep short (SN330) ............... 1
50 end_2_weld_no character(8) ........................... 1
51 end_2_weld_type short (SN1100)/400 (bolt option) 1
52 end_2_gasket_gap double ...................(Dist. Model). 1
53 end_2_gasket_opt short (SN400) ............... 1
54 end_2_stress_node short .................................. 2
55 end_2_stres_int double ................................. 5
56 end_2_head_loss double ................................. 5
57 unique_name character(12) .......................... 1
58 last_placed_date integer ................................ 3
59 inspection_key short .................................. 2
60 end_1_inspect_key short .................................. 2
61 end_2_inspect_key short .................................. 2
405
Report Manager User’s Guide Addendum – February 2003
406
47 stress_node_no short .................................. 2
48 stress_intens_fact double ................................. 5
49 head_loss_factor double ................................. 5
50 piping_assembly character(12) .......................... 1
51 component_group_no short .................................. 2
52 remarks character(50) .......................... 1
53 standard_note_no_a short (SN499) ............. 2 or 1
54 standard_note_no_b short (SN499) ............. 2 or 1
55 cp_1_nom_pipe_diam short ............................(NPD). 1
56 cp_1_outside_diam double .....................(Dist. NPD). 1
57 cp_1_end_prep short (SN330) ............... 1
58 cp_1_sch_thk character(8) (SN332) ............... 1
59 cp_1_rating character(8) ........................... 1
60 cp_1_face_to_ctr double ...................(Dist. Model). 1
61 cp_1_weld_no character(8) ........................... 1
62 cp_1_weld_type short (SN1100)/400 (bolt option) 1
63 cp_1_gasket_gap double ...................(Dist. Model). 1
64 cp_1_gasket_option short (SN400) ............... 1
65 cp_1_stress_node short .................................. 2
66 cp_1_stress_factor double ................................. 5
67 cp_1_head_loss double ................................. 5
68 cp_2_nom_pipe_diam short ............................(NPD). 1
69 cp_2_outside_diam double .....................(Dist. NPD). 1
70 cp_2_end_prep short (SN330) ............... 1
71 cp_2_sch_thk character(8) (SN332) ............... 1
72 cp_2_rating character(8) ........................... 1
73 cp_2_face_to_ctr double ...................(Dist. Model). 1
74 cp_2_weld_no character(8) ........................... 1
75 cp_2_weld_type short (SN1100)/400 (bolt option) 1
76 cp_2_gasket_gap double ...................(Dist. Model). 1
77 cp_2_gasket_option short (SN400) ............... 1
78 cp_2_stress_node short .................................. 2
79 cp_2_stress_factor double ................................. 5
80 cp_2_head_loss double ................................. 5
81 cp_3_nom_pipe_diam short ............................(NPD). 1
82 cp_3_outside_diam double .....................(Dist. NPD). 1
83 cp_3_end_prep short (SN330) ............... 1
84 cp_3_sch_thk character(8) (SN332) ............... 1
85 cp_3_rating character(8) ........................... 1
86 cp_3_face_to_ctr double ...................(Dist. Model). 1
87 cp_3_weld_no character(8) ........................... 1
88 cp_3_weld_type short (SN1100)/400 (bolt option) 1
89 cp_3_gasket_gap double ...................(Dist. Model). 1
90 cp_3_gasket_option short (SN400) ............... 1
91 cp_3_stress_node short .................................. 2
92 cp_3_stress_factor double ................................. 5
93 cp_3_head_loss double ................................. 5
94 cp_4_nom_pipe_diam short ............................(NPD). 1
95 cp_4_outside_diam double .....................(Dist. NPD). 1
96 cp_4_end_prep short (SN330) ............... 1
97 cp_4_sch_thk character(8) (SN332) ............... 1
98 cp_4_rating character(8) ........................... 1
99 cp_4_face_to_ctr double ...................(Dist. Model). 1
100 cp_4_weld_no character(8) ........................... 1
101 cp_4_weld_type short (SN1100)/400 (bolt option) 1
102 cp_4_gasket_gap double ...................(Dist. Model). 1
103 cp_4_gasket_option short (SN400) ............... 1
407
Report Manager User’s Guide Addendum – February 2003
408
6 iso_support_type_b short (SN380) ............... 1
7 iso_support_type_c short (SN380) ............... 1
8 iso_support_type_d short (SN380) ............... 1
9 details_for_shop character(50) .......................... 1
10 details_for_field character(50) .......................... 1
11 fabrication_orient character(20) .......................... 1
12 commodity_code character(16) .......................... 1
13 MTO_requirements short (SN365) ............... 1
14 fabrication_cat short (SN180) ............... 1
15 weight double (SN1028 units) ......... 5
16 construction_stat short (SN130) ............... 1
17 hold_status short (SN50) ................ 1
18 standard_note_no short (SN499) ............. 2 or 1
19 iso_dwg_index_no integer ................................ 3
20 isometric_sheet_no character(2) ........................... 1
21 piece_mark_no character(60) .......................... 1
22 color_code character(8) ........................... 1
23 isometric_dim_a double ................................. 5
24 isometric_dim_b double ................................. 5
25 isometric_dim_c double ................................. 5
26 isometric_dim_d double ................................. 5
27 isometric_dim_e double ................................. 5
28 trans_rigidity_x double ................................. 5
29 trans_rigidity_y double ................................. 5
30 trans_rigidity_z double ................................. 5
31 rot_rigidity_x double ................................. 5
32 rot_rigidity_y double ................................. 5
33 rot_rigidity_z double ................................. 5
34 spring_gap_length double ................................. 5
35 sping_gap_direct short .................................. 2
36 number_of_springs short .................................. 2
37 last_placed_date integer ................................. 3
38 inspection_key short .................................. 2
39 mark_number character(80) .......................... 1
40 group_id integer ................................. 3
41 gang_id integer ................................. 3
42 material_grade short (SN145) ................. 1
43 weld_code short .................................. 1
44 material_index character(16) .......................... 1
45 operating_load double ................................. 5
46 installed_load double ................................. 5
47 hydrostatic_load double ................................. 5
48 total_movement_1 double in subunits (dist. att.) ....... 1
49 total_movement_2 double in subunits (dist. att.) ....... 1
50 rod_diameter double in subunits .................... 1
409
Report Manager User’s Guide Addendum – February 2003
410
21 std_note_a short .................................. 2
22 std_note_b short .................................. 2
23 unique_name character(16) .......................... 1
24 idx_205 integer ................................ 3
25 idx_215 integer ................................ 3
411
Report Manager User’s Guide Addendum – February 2003
412
Table 250 - Standard Notes Table
This table is published when you select the Standard Notes option on the Schedule Setup
dialog box. This table should be published after any changes are made to the standard
notes.
Note: Only the Approved libraries are published.
1 system_unique_no integer ................................ 3
2 std_note_no short .................................. 2
3 std_note_code short .................................. 2
4 descr character(240) ......................... 1
413
Report Manager User’s Guide Addendum – February 2003
414
Index
data MTO
weld, 380 database listing, 397
drawing project
management data listing, 386 control database listing, 381
FrameWorks Plus report manager
data listing, 391 form, 377
interference interface, 377
management data listing, 389 sample
report format files, 379 report format files
material takeoff database listing, 397 interference, 379
model weld
management data listing, 384 data, 380
415