ISODRAFT Reference Manual
Transfer Data to the COMPIPE Module : Format of COMPIPE MTO FIle
Format of COMPIPE MTO FIle
The MTO file contains a single batch header record, followed by a group of records for each pipeline or isometric sheet:
Batch Header
 
 
MTO Line Header
|
 
MTO Drawing Header
|
for each pipeline
Component records (one record for each material list entry)
 
isometric sheet
A maximum of 200 pipelines or isometric sheets may be included in each file. In the following record definitions, the : character is a field separator, and the * character is a record terminator.
The Batch Header record is defined thus:
BATCH888821JAN99MATOPROJNUMB
where:
BATCH
is a fixed record identifier
8888
is a fixed 4 digit batch sequence number
21JAN99
is the run date when the pipe was detailed
MATO
is a fixed identifier for an MTO file
PROJNUMB
is the project number (truncated to 8 characters)
The MTO Line Header record is defined thus:
$L:AREA:LINENUMBER:SHEET NO:RUNTYPE::U or C:S or L*
where:
$L
is a fixed record identifier
AREA
is from the pipe AREA attribute (max 4 characters)
LINENUMBER
is from the pipe CNUM or NAME (truncated to 14 characters)
SHEET NO
is the isometric sheet number, e.g. 01
RUNTYPE
is data type transferred, always set to A (Actual)
U or C
signifies reports will have User or Client Itemcodes
S or L
signifies reports will have Short or Long Descriptions
The Drawing Header record is defined thus:
$D:DRWGNUMBER::REVISION*
where:
$D
is a fixed record identifier
DRWGNUMBER
is from the pipe CDRG attribute (max 24 characters)
REVISION
is from the pipe REV attribute (max 2 characters)
If the CDRG attribute for a pipe is unset or blank, a drawing number will be automatically generated, based on the pipe nominal size and name. This will take the form:
1.1/2”PIPENAME
for pipes using imperial bores
40MM-PIPENAME
for pipes using metric bores (’MM-’ is the default Atext 453)
Each component entry on the material list has an equivalent entry in the MTO file. Components are classified as ’in-spec’ being in the specification set at pipe level, ’alternative-spec’ being in a different specification, and ’out-of-spec’ being in no pipe specification (a concept AVEVA E3D™ does not have).
The in-Spec Component record is defined thus:
n::SHORT CODE:TAG NUMBER:1st NS:2nd NS:3rd NS:QUANTITY:BOLTLENGTH:*
where:
n
= 1 for SHOP flag = TRUE, = 3 for SHOP flag
 
= FALSE
SHORT CODE
is from the detail text’s SCOD (max 3 characters)
TAG NUMBER
unique identifier (max 8 characters), refer to Notes
1st NS
is main size, of the form 1.1/2 (imperial) or 40 (metric)
2nd NS
is second size (format as for 1st NS)
3rd NS
is third size (format as for 1st NS)
QUANTITY
is quantity for component, tube or bolt sets (max 6 characters)
BOLTLENGTH
is length of bolts, refer to Notes
Notes:
1.
Short code is a reference to a component entry in the Compipe specification.
2.
Instruments and supports take a tag number from their AVEVA E3D™ name if the options INSTruments NAMe and ATTAname SPREf are used.
3.
Standard assemblies take a tag number of their itemcode, which is not unique, but is the same for all assemblies of the same content/configuration, i.e. standard assembly number.
4.
Quantity is an integer number for components, or a length for tube. For bolts it is the number of sets, not the number of bolts. Also for bolts, the size is the pipeline nominal size, not the bolt diameter.
5.
Boltlength is preceded by the character H to indicate an override to COMPIPE. Metric lengths take the form H120.0. Imperial lengths take the form H4.3/4.
Where a change of spec occurs in the pipeline, an Alternative Spec record is output, defined thus:
n::YY:ALTERNATESPEC:::::*
where:
n
= 1 for SHOP flag = TRUE, = 3 for SHOP flag = FALSE
YY
is a fixed identifier to indicate alternative spec
ALTERNATESPEC
is the alternative spec name (max 6 characters)
Components from the alternative spec then follow, with records to the same format as in-spec components, except that a Y character is output as a prefix to their short code. A return to the standard spec for the pipe is indicated by the additional Y character no longer being output.
Note:
The output of Alternative spec records may be suppressed if the SPECBreak BRANch option is used.
Out-of-specification components take two records, defined thus:
n:::ITEMCODE:QUANTITY*
where:
n
= 1 for SHOP flag = TRUE,
 
= 3 for SHOP flag = FALSE
ITEMCODE
is from the component’s itemcode (max 12 characters)
QUANTITY
is quantity for component, tube or bolt sets
N.S.:::::::*
where:
N.S.
is the nominal size of the component
Note:
Out-of-specification components can only be from ‘additional items on the material list' in ISODRAFT, i.e. not normal pipeline components.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo