PID Designer

User Guide
AVEVA Solutions Ltd

Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective licence agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries 2007

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
 PID Designer User Guide
Contents

PID Designer User Guide

Contents Page

PID Designer
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Starting P&ID Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Project Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Drawing Elements not supported by
the ISO15926 (Version 3.2.0) Schema. . . . . . . . . . . . . . . . . . 7
5 The Export Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6 Appendix: The ISO15926 (Version 3.2.0)
Schema Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
6.2 XML Model Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
6.2.1 XML File Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2.2 XML Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2.3 Geometries (Axis and Reference) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.2.4 Character encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.5 Tag Referencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.2.6 PersistentId referencing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.3 Shared Attribute Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
6.3.1 ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.2 Tag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.3 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.4 StockNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

© 2007 AVEVA Solutions Ltd 1 12.0

 PID Designer User Guide
Contents

6.3.5 ComponentName. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.6 ComponentClass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3.7 ComponentType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.8 Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.9 Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.3.10 Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6.4 Element Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
6.4.1 PlantModel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.4.2 Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.4.3 Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.4.4 BsplineCurve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.4.5 CenterLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.4.6 Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.4.7 Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.4.8 CompositeCurve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.4.9 Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.4.10 ConnectionPoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.4.11 ConnectionType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.4.12 ControlPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.4.13 ControlPointWeight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.4.14 Coordinate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.4.15 CrossPageConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4.16 Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4.17 Discipline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4.18 Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.4.19 DrawingBorder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4.20 Ellipse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.4.21 EndDiameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4.22 Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4.23 Extent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.24 FabricationCategory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.4.25 GenericAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.26 GeometricPrimitives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4.27 Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.4.28 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.29 Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.4.30 IdentifierElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.4.31 InsideDiameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.4.32 InstrumentLoop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.4.33 KnotMultiplicities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

© 2007 AVEVA Solutions Ltd 2 12.0

 PID Designer User Guide
Contents

6.4.34 Knot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.4.35 Knots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.4.36 Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.4.37 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.38 Manufacturer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.39 Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.4.40 MaterialDescription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4.41 Max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4.42 MaximumDesignPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4.43 MaximumDesignTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.44 MaximumOperatingPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.45 MaximumOperatingTemperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.4.46 Min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.4.47 MinimumDesignPressure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.4.48 MinimumDesignTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.4.49 MinimumOperatingPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.4.50 MinimumOperatingTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.4.51 ModelNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.4.52 Multiplicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.4.53 NominalDiameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.4.54 NormalDesignPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.4.55 NormalDesignTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.4.56 NormalOperatingPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.4.57 NormalOperatingTemperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.4.58 Nozzle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.4.59 NozzleType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.4.60 OperatorType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.4.61 OutsideDiameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.4.62 PConnectionPoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.4.63 PersistentID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.4.64 PipeConnector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.4.65 PipeFlowArrow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.4.66 PipingNetworkSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.4.67 PipingComponent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.4.68 PipingNetworkSegment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.4.69 PlantArea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.4.70 PlantInformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.4.71 PlantItem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.4.72 Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.4.73 PolyLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

© 2007 AVEVA Solutions Ltd 3 12.0

 PID Designer User Guide
Contents

6.4.74 Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.4.75 Presentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.4.76 ProcessInstrument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.4.77 Rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.4.78 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.4.79 Remark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.4.80 Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.4.81 Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.4.82 ShapeCatalogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.4.83 SignalConnectorSymbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.4.84 SignalLine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.4.85 SpecificationBreak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.4.86 StartDiameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.4.87 String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.4.88 Supplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.4.89 Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.4.90 TestPressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.4.91 Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.4.92 Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.4.93 TrimmedCurve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.4.94 UnitsOfMeasure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.4.95 WallThickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4.96 Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4.97 WeightsData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

© 2007 AVEVA Solutions Ltd 4 12.0

 PID Designer User Guide
Introduction

1 Introduction

P&ID Designer is a utility which exports data from AutoCAD P&IDs into XML files in
ISO15926 (Version 3.2.0) format.
These files contain both engineering item data and graphical data for use by the P&ID
Manager application. Refer to P&ID Manager documentation for further information.
P&ID Designer is an add-on for AutoCAD P&ID 2008.

© 2007 AVEVA Solutions Ltd 1:1 12.0

 PID Designer User Guide
Introduction

© 2007 AVEVA Solutions Ltd 1:2 Issue 1.0

 PID Designer User Guide
Starting P&ID Designer

2 Starting P&ID Designer

Start P&ID Designer either by selecting the P&ID Designer desktop icon or the shortcut on
the Programs menu:

AutoCAD P&ID 008 with the P&ID Designer add-on is then started.

© 2007 AVEVA Solutions Ltd 2:3 12.0

 PID Designer User Guide
Starting P&ID Designer

The add-on adds the AVEVA P&ID Designer toolbar and menu, and two project setup
options to AutoCAD P&ID 2008.

In all other respects AutoCAD P&ID 2008 is unchanged.

© 2007 AVEVA Solutions Ltd 2:4 Issue 1.0

 PID Designer User Guide
Project Setup

3 Project Setup

The two project setup options added for P&ID Designer are P&ID Designer_Output and
P&ID Designer_Tolerance. They are located in the Custom section of the Project Details
page of the Project Setup dialog.

The P&ID Designer_Output option specifies the location to which the XML files generated
by P&ID Designer are exported. The default location is the root directory of the project.
The P&ID Designer_Tolerance option specifies the distance within which elements on the
drawing are assumed to be connected by P&ID Designer. Items at or within the specified
distance of each other are assumed to be connected. Items further apart are assumed not to
be connected.
The default setting for Metric projects is 0.5mm.
The default setting for Imperial projects is 0.02 inches.

© 2007 AVEVA Solutions Ltd 3:5 12.0

 PID Designer User Guide
Project Setup

© 2007 AVEVA Solutions Ltd 3:6 Issue 1.0

 PID Designer User Guide
Drawing Elements not supported by the ISO15926 (Version 3.2.0) Schema

4 Drawing Elements not supported by

the ISO15926 (Version 3.2.0) Schema

The ISO15926 (Version 3.2.0) schema does not support all the drawing elements that
AutoCAD is capable of producing. These limitations should be considered when creating
and exporting from drawings.
The following elements are not supported:
• Splines: are not exported.
• Complex line styles: basic line styles consisting of lines, dashes, dots etc are exported
correctly. More complex lines styles that include more complicated shapes are not
supported. They will be replaced by simple lines.
• Complex hatching: basic hatching consisting of lines, dashes, dots etc is exported
correctly. More complex hatching that includes more complicated shapes is not
supported, and is not exported.
• Trimmed ellipses: ellipses that have been trimmed, i.e. that have had a part of them
removed, are not fully supported. The schema does not include sufficient tags to define
them properly. As a result, exported trimmed ellipses will be converted into other
shapes, typically arcs.
• Polylines with variable widths: the schema does not include sufficient tags to represent
more than one width for a single line. Only the first width specified for such a line is
exported.
• AutoCAD Fonts: are not supported and are automatically replaced by the Romans font
on export.
The specification of the ISO15926 (Version 3.2.0) schema is included at the end of this
document.

© 2007 AVEVA Solutions Ltd 4:7 12.0

 PID Designer User Guide
Drawing Elements not supported by the ISO15926 (Version 3.2.0) Schema

© 2007 AVEVA Solutions Ltd 4:8 Issue 1.0

 PID Designer User Guide
The Export Procedure

5 The Export Procedure

To export data from a drawing, open the drawing and select the Export option on the AVEVA
P&ID Designer menu, or the Export button on the AVEVA P&ID Designer toolbar:
The Export to ISO15926 dialog is then displayed:

The dialog displays the progress of the export.

To view more details, press the Details >> button.
The Tasks tab displays the progress of each task in the export procedure:

© 2007 AVEVA Solutions Ltd 5:9 12.0

 PID Designer User Guide
The Export Procedure

The Details tab displays details of the drawing elements exported:

A text file is generated by the export procedure, which lists the messages displayed in the
Details tab. Select the View button to open this file in Notepad.
The export procedure creates an XML file with the same name as the drawing file. The
exported file is placed in the location specified by the P&ID Designer_Output project setup
option (see above), and is now ready for use by P&ID Manager.
Example of an exported XML file displayed in XML Notepad.

© 2007 AVEVA Solutions Ltd 5:10 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6 Appendix: The ISO15926 (Version 3.2.0)

Schema Specification

6.1 Notation
Where the notation ‘…’ is used in examples it implies content that has been omitted due to it
not being relevant for the example.
Elements in examples have been abbreviated to <Tag … /> to show structure but limit
content.

© 2007 AVEVA Solutions Ltd 6:11 12.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.2 XML Model Details

6.2.1 XML File Document Structure

The document structure is defined in the XML schema for the P&ID profile (See below). An
output file that conforms to this document must validate against the profile schema.
The first line of the file must be an XML declaration, for example:

<?xml version="1.0" encoding="UTF-8" ?>

The document is to be encoded using UTF-8.

The root node of an XML file is a PlantModel element. See below for the definitions of its
attribute and element contents.
XML elements are not defined within an XML namespace and so are not namespace
qualified.
The following class model provides an overview of the significant structural elements
contained within an AVEVA P&ID XML profile file. The bi-directional arrows indicate and
parent/child element relationship in the XML file. The elements and their attributes are
defined in the Element Definitions section below.

Each structural element may contain geometric and text elements to represent the drawing
contents.

6.2.2 XML Topology

A PipingNetworkSegment, as its upstream reference (PipingNetworkSegment/Connection/
@FromID), will reference a Nozzle, splitting component (such as a Tee, Wye or Cross),
Reducer or SpecificationBreak that it doesn't contain or it will reference a PipeConnector
that it contains.

© 2007 AVEVA Solutions Ltd 6:12 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

A PipingNetworkSegment, as its downstream reference (PipingNetworkSegment/

Connection/@ToID), will reference a Nozzle, merging component (such as a Tee, Wye or
Cross) or SpecificationBreak that it doesn't contain or it will reference a splitting component
(such as a Tee, Wye or Cross), Reducer or PipeConnector that it contains. Nb All
PipingNetworkSegment elements are split where there is splitting component ( such as a
Tee, Wye or Cross) or a Reducer.
Contained components, with the exception of PipeConnectors require a ToNode attribute
which references the downstream ConnectionPoint of the component (i.e. the main flow out
of the segment).
Components contained by other segments must be referenced using a ToNode or
FromNode attribute as appropriate.
References to Nozzle, PipeConnector and SpecificationBreak elements do not require
ToNode/FromNode attributes..

6.2.3 Geometries (Axis and Reference)

All geometries in an XMpLant file are accompanied by Axis and Reference elements.
These define rotations around 3 dimensional axis that define how to map the coordinates
defined for the item into the target environment. For most 2D drawing work the following
values give the expected behaviour (i.e. the coordinates are defined in the 2D drawing
plane).
<Axis X="0" Y="0" Z="1"/>
<Reference X="1" Y="0" Z="0"/>
Some curve primitives such as ellipses in XMpLant require more complex use of Axis and
Reference in order to define the 2D forms.
The <Axis> value defines a unit vector in 3D space about which an object should rotate. For
2D diagrams nearly all geometries will define this element as <Axis X="0" Y="0" Z="1"/>
which denotes a vector aligned with the Z-axis.

© 2007 AVEVA Solutions Ltd 6:13 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

The <Reference> element defines what is effectively the rotation about the <Axis> element.
When you see the value written as <Reference X="1" Y="0" Z="0"/> it indicates that the X-
Axis with which the object's points are defined use the same X-Axis on the output surface/
window with which to orientate - in other words no rotation is required when you have the
following paired elements;
<Axis X="0" Y="0" Z="1"/>
<Reference X="1" Y="0" Z="0"/>

6.2.4 Character encoding

XML is encoded using UTF-8. This means that most characters used in western languages
are encoded using a single byte representation, more complex characters are encoded
using either a 2 byte encoding or a substitution mechanism. Where the export capabilities
are limited to a single byte representation or software is developed with limited knowledge of
UTF-8 it is common practice to output the 2 byte characters using a numerical substitution
syntax of &#nnn; where nnn denotes the character code.
P&ID Manager is very limited in the way that characters are supported because the base
storage has fixed length text types (120 characters) and limited character support. If two
byte characters are provided to P&ID Manager then they will be substituted numerically
when stored so that the database character constraints can be met. This substitution
compromises the amount of text stored as a single character will be converted to ~5
characters to complete the substitution. When exporting to XML bear in mind that the string
data contents loaded into P&ID Manager will be constrained to 120 characters in length
after two byte characters have been substituted numerically and XML substitutions have
been reversed (such as ‘?’ -> ‘&#FEA6;’, ‘&amp;’ ->’&’, ‘&lt;’ -> ‘<’ etc).

6.2.5 Tag Referencing

Tag attributes may be used to reference elements instead of referencing by the ID attribute.
The XML profile prefers the use of ID referencing as it gives a consistent referencing
mechanism that can be used regardless of the presence of a Tag attribute.
If Tags are used then there is a special case for referencing Nozzle elements. In this
instance the Tag is only unique within the scope of the containing Equipment element so the
Equipment Tag must also be included in the reference. The reference must have the form
<EquipmentTag>-<NozzleTag> and can only be used where the <NozzleTag> component
doesn’t contain a ‘-‘ character.
For Example:
Where:
Equipment/@Tag = ‘VP-1234-DNJ09’
Equipment/Nozzle/@Tag = ‘N1’
The reference would be:
VP-1234-DNJ09-N1

6.2.6 PersistentId referencing

As long as the context attribute used to scope PersistentID elements is at least equal in
scope to the file scope then PersistentId attributes may be used for cross referencing
elements. The PersistentID/@Identifier value is supported I any ItemId attribute.

© 2007 AVEVA Solutions Ltd 6:14 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.3 Shared Attribute Definitions

6.3.1 ID
The ID attributes of XML elements has the form ‘XMP_<n>’ where n is a sequential number
within the XML file. These id values may be used for cross referencing elements and are
transient. i.e. these ids are generated for each version of the file and cannot be used to
match file contents between two different exports of the same drawing.
For example :-

1. <PipingNetworkSegment ID=”XMP_23” … >

6.3.2 Tag
This should contain the full Tag for an item without additional text. This is an xsd:string
attribute with no specific validation (see Character encoding for character constraints)

6.3.3 Specification
This is a free text field that has no clearly defined semantics. Specification information may
be best represented in GenericAttributes.

6.3.4 StockNumber
This is defined as:
‘A code that will identify a purchasable plant item
‘The StockNumber attribute contains the unique name of this component that can be
used to relate to the complete set of information that is contained in the vendor
catalogue for the component. This attribute taken with the Specification and
NominalDiameter will identify a specific item, fully defining its parameters size and
optionally material and all other information available for it.’
This attribute is an xsd:string attribute and has no specific validation or constraints other
than those defined in the ‘Character encoding’ section of this document.

6.3.5 ComponentName
If present on a component that is inside a ShapeCatalogue element then this is the unique
id for the symbol within the XML file.
If present on a component that is not inside a ShapeCatalogue element then this is the
reference to the geometry of the components symbol. The component may have additional
annotation defined within it (See also Scale).

6.3.6 ComponentClass
The format of the ComponentClass attribute is documented in the XML Model Overview
section. The attribute is the RDL Designation field from the ISO 15926 RDL specification.
The value of this field is converted to Camel Case with all spaces removed. Notes : some
fields contain characters that must be substituted when written in XML (e.g. ‘&’ characters
must be substituted with &amp;). For example:

© 2007 AVEVA Solutions Ltd 6:15 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

GATE VALVE -> GateValve

CENTRIFUGAL PUMP -> CentrifugalPump

6.3.7 ComponentType
The precise semantics of this attribute are not documented so I would either omit it or
default it to ‘Normal’.
Permitted values :-
‘Normal’
‘Explicit’
‘Parametric’

6.3.8 Revision
If known this attribute should contain the revision or version of the item. This has the type of
xsd:string and therefore has no specific syntax or format constraints other than those
detailed in Character encoding.

6.3.9 Status
One of the following values :-
‘Current’ – This implies this is the latest version of an item
‘Deleted’ – This item has been superseded or removed from the drawing.
‘Modified’ – The last change to this item was a modification.
‘New’ – This is the first version of the item in the drawing.
If the item has a status of ‘Deleted’ then the item will be ignored by P&ID Manager.
Items will be deleted by Manager if they have a status of Deleted or if they do not appear in
the new version of a file and used to exist.

6.3.10 Units
The Units attribute is to be taken from the ISO15926 RDL catalogue using the name from
the catalogue converted to camel-case. All measurement values such as distances and
pressures are either accompanied by their units of measure or defaulted to the value
provided on the PlantInformation/UnitsOfMeasure element. The unit of measure for the
coordinate geometry is stipulated in the PlantInformation/@Units attribute. The permitted
values are as follows:
Angles:
Degree, Radian, deg, rad
Area :
SquareMillimetre, SquareCentimetre, SquareMetre, SquareKilometre, SquareInch,
SquareFoot, SquareYard, SquareMile, sq mm, sq cm, sq m, sq km
Distances:
Micron, Millimetre, Centimetre, Decimetre, Metre, Kilometre, Inch, Foot, Yard, Mile,
mm, cm, m, km, in, ft, yd

© 2007 AVEVA Solutions Ltd 6:16 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Pressures:
MillinewtonMetreSquared, NewtonMetreSquared, KilonewtonMetreSquared,
Picopascal, Micropascal, Millipascal, Pascal, Kilopascal, Megapascal, Gigapascal,
Bar, Bara, Barg
Temperatures:
DegreeKelvin, DegreeCelsius, DegreeRankine, DegreeFahrenheit, degC, degF, degK
Volume :
CubicMillimetre, CubicCentimetre, CubicMetre, CubicInch, CubicFeet, CubicYard, cc,
litres, gallons, USGallons, barrels
Weight:
Microgram, Milligram, Gram, Kilogram, Megagram, PoundMass, OunceMass, mg, Kg,
lb, oz

Note: All values are case sensitive.

6.4 Element Definitions

6.4.1 PlantModel
This is the root node of an XML document and only exists as the root node of an XML file.
Other than the first two child elements, PlantInformation and Extent, the ordering of child
elements within a PlantModel element is not significant.
There shouldn’t be any need to place graphical elements into a PlantModel element as all
drawing annotation such as borders and floating text should be child elements of the
drawing element.
While a Position element may be provided is has no attached semantics and is often
defaulted to 0,0,0.
Child Elements:

Element Name Cardinality Description

PlantInformation 1 The properties of a plant model
This includes properties like its name,
modification date, editing system etc.
The PlantInformation element must be the
first child element of a PlantModel element.
Extent 1 The minimum bounding rectangle that
encloses the full graphical contents of the
PlantModel instance.
The Extent element must be the second
child element of a PlantModel element
BsplineCurve 0..* A geometric primitive
Circle 0..* A geometric primitive
CompositeCurve 0..* A composite geometry

© 2007 AVEVA Solutions Ltd 6:17 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

Drawing 1 Metadata and graphical annotation related
to the P&ID drawing being represented
Ellipse 0..* A geometric primitive
Equipment 0..* The representation of a piece of plant
equipment.
GenericAttributes 0..* Source system properties that relate to the
XML file and plant model. These
properties may be grouped into many
GenericAttributes elements.
GeometricPrimitives 0..* A collection of geometric primitives.
InstrumentLoop 0..* A grouped set of instrument detail
Line 0..* A geometric primitive
PipingNetworkSystem 0..* An Engineering PipingNetworkSystem
element
PipeLine 0..* An Engineering PipeLine element
PlantArea 0..* A place holder for Area information
Point 0..* A geometric primitive
PolyLine 0..* A geometric Primitive
Position 0..1 Usually defaulted to 0,0,0 if output.
Presentation 0..* Style information for this object. In this
context it has no meaning and should be
omitted.
ProcessInstrument 0..* An Engineering Instrument object
Shape 0..* A geometric primitive
ShapeCatalogue 0..* A catalogue of Equipment and
PipingComponent symbols.
SignalLine 0..* A connection between instruments.
Text 0..* Label primitives
TrimmedCurve 0..* A geometric primitive

© 2007 AVEVA Solutions Ltd 6:18 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<?xml version="1.0" encoding="UTF-8" ?>
<PlantModel xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:noNamespaceSchemaLocation=".\XMLSchema.xsd">
<PlantInformation … />
<Extent … />
<Drawing … />
<ShapeCatalogue … />
<Equipment … />
…
</PlantModel>

6.4.2 Association
The Association element is used to relate engineering items to other resources.
One documented use of this is to relate in-line ProcessInstrument elements with
InstrumentLoop elements. In this case each in-line ProcessInstrument element has an
Association child element which details the relationship using the Type attribute with a value
of ‘is a part of’.
Child elements :
None
Attributes:

Attribute Name Required Description

Type Y The meaning/semantics of the
relationship.
ItemID N The ID or PersistentID/@Identifier attribute
value of the item being referenced.
Tag N The Tag attribute value of the item being
referenced. (See Tag Referencing)
Name N The Name attribute value of the item being
referenced.
URI N A URI identifying an associated resource
Context N If omitted then the resource is assumed to
be part of the model in the same file. If you
want to state the context as the current
model then use the value ‘XML’.

Example:
<ProcessInstrument ...>
<Association Type="is a part of" ItemID="XMP_235"/>
...
</ProcessInstrument>

6.4.3 Axis
See Geometries (Axis and Reference).

© 2007 AVEVA Solutions Ltd 6:19 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements :
None
Attributes :

Attribute Name Required Description

X Y
Y Y
Z Y

Example:
<Axis X="0" Y="0" Z="1" />

6.4.4 BsplineCurve
Geometric curve primitive detailing a Bspline.
Child elements:

Element Name Cardinality Description

Presentation 0..1 The style to use when drawing the Bspline.
The drawing behaviour is undefined if the
Presentation element is missing.
Extent 1 The minimum bounding geometry of this
element and its descendants
ControlPoints 1
KnotMultiplicities 0..1
Knots 0..1
WeightsData 0..1
GenericAttributes 0..1 Any application specific attributes relating
to the Bspline

Attributes:

Attribute Name Required Description

Degree Y
CurveType Y One of the following : 'BsplineCurve',
'BsplineCurveWithKnots' or
'RationalBsplineCurve'.
CurveForm N One of the following : 'PolyLine',
'CircularArc', 'EllipticArc', 'ParabolicArc' or
'HyperbolicArc'
NumControlPoints Y x

© 2007 AVEVA Solutions Ltd 6:20 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attribute Name Required Description

NumKnots N x
Closed N 'true' or 'false'
SelfIntersect N 'true' or 'false'

Example:

<BsplineCurve Degree="3" CurveType="BsplineCurveWithKnots"

NumControlPoints="4" NumKnots="8">
<Presentation Layer="" Color="-32363" LineType="0"
LineWeight="1" R="0.67" G="0.38" B="0"/>
<Extent>
<Min X="10241.64" Y="10283.399" Z="40.9999850090838"/>
<Max X="10241.64" Y="10283.399" Z="41.0000151701423"/>
</Extent>
<ControlPoints>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
</ControlPoints>
<Knots>
<Knot>0</Knot>
<Knot>1</Knot>
</Knots>
<KnotMultiplicities>
<Multiplicity>4</Multiplicity>
<Multiplicity>4</Multiplicity>
</KnotMultiplicities>
<WeightsData>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
</WeightsData>
</BsplineCurve>

6.4.5 CenterLine
Geometric curve primitive detailing the line geometry between the components of a
PipingNetworkSegment. A CenterLine element is used to imply the presence of tubing.
The interpolation between each coordinate is linear.
Child elements:

Element Name Cardinality Description

Presentation 0..1 The style to use when drawing the line.
The drawing behaviour is undefined if the
Presentation element is missing.
Extent 1 The minimum bounding geometry of the
CenterLine element and its descendants

© 2007 AVEVA Solutions Ltd 6:21 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

Coordinate 1..* The coordinates defining the line primitive
GenericAttributes 0..* Any application specific attributes relating
to the tube/CenterLine

Attributes:

Attribute Name Required Description

NumPoints Y The number of child Coordinate elements.

Example:
<CenterLine NumPoints="2">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="77" Y="463" Z="0" />
<Max X="646" Y="463" Z="0" />
</Extent>
<Coordinate X="77" Y="463" Z="0" />
<Coordinate X="646" Y="463" Z="0" />
</CenterLine>

6.4.6 Circle
A geometric primitive describing a circle.
Child elements:

Element Name Cardinality Description

Presentation 1 The style to use when drawing the circle
Extent 1 The minimum bounding geometry of the
circle
Position 1 The location of the circles centre
GenericAttributes 0..* Any application attributes relating to the
circle

Attributes:

Attribute Name Required Description

Radius Y The radius of the circle to draw
Filled N One of ‘Solid’ or ‘Hatch’. If not present the
circle is not filled.

© 2007 AVEVA Solutions Ltd 6:22 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Circle Radius="8">
<Presentation LineType="Solid" LineWeight="1" Color="22"
R="0.79" G="0.239" B="0.087" />
<Extent>
<Min X="710" Y="258" Z="0" />
<Max X="726" Y="274" Z="0" />
</Extent>
<Position>
<Location X="718" Y="266" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
</Circle>

6.4.7 Component
Used to group geometric and text primitives within a Drawing element. This inherits all
elements and attributes from the base type ‘PlantItem’. See ‘PlantItem’ for the definitions of
the inherited contents..
Child elements:
See ‘PlantItem’, no additional elements are defined.
Attiribute :
See ‘PlantItem’, no additional attributes are defined.
Example:
<Component ID="XMP_12" Tag>
<Extent>
<Min X="199.6153088" Y="155.02299606" Z="0" />
<Max X="236.78321894" Y="194.01149803" Z="0" />
</Extent>
<Position>
<Location X="221" Y="182" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
…
<Text … />
</Component>

6.4.8 CompositeCurve
A collection of geometric curve primitives

© 2007 AVEVA Solutions Ltd 6:23 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:

Element Name Cardinality Description

Presentation 0..1 The Presentation element has no purpose
in this context.
Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.
BsplineCurve 0..* A geometric primitive
Circle 0..* A geometric primitive
CompositeCurve 0..* A geometric primitive
Ellipse 0..* A geometric primitive
Line 0..* A geometric primitive
Polyline 0..* A geometric primitive
Shape 0..* A geometric primitive
TrimmedCurve 0..* A geometric primitive
GenericAttributes 0..* Any application specific properties relating
to the Drawing.

Attributes:
None
Example:
<CompositeCurve>
<Presentation LineType="Solid" LineWeight="1" Color="22"
R="0.79" G="0.239" B="0.087" />
<Extent>
<Min X="714.38797635" Y="260.50328515" Z="0" />
<Max X="720.62485791" Y="263.00328515" Z="0" />
</Extent>
<Circle ... />
<Circle ... />
<PolyLine ... />
</CompositeCurve>

6.4.9 Connection
This element is used to describe the flow connectivity between elements. The source of the
flow is defined using the attributes FromID and FromNode while the flow destination is
defined using ToID and ToNode. A connection element and its attributes are not mandatory
but must be present to represent the topology of a network. If the FromID/ToID attributes
reference a Nozzle, PipeConnector or SpecificationBreak element then the FromNode/
ToNode attributes are not required.
See ConnectionPoints for details on what is being referenced.
Child elements:

© 2007 AVEVA Solutions Ltd 6:24 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

None
Attributes:

Attribute Name Required Description

ToID N The ID, PersistentID/@Identifier or Tag of
the referenced item that is the flow
destination for the parent of the Connection
element.
ToNode N The index of the ConnectionPoints Node
element within the ConnectionPoints
element of the destination element. Nb
this is a 0 based index and is only required
if the destination is not a Nozzle,
PipeConnector or SpecificationBreak.
FromID N The ID, PersistentID/@Identifier or Tag of
the referenced item that is the flow source
for the parent of the Connection element.
See Tag Referencing
FromNode N The index of the ConnectionPoints Node
element within the ConnectionPoints
element of the source element. Nb this is a
0 based index and is only required if the
source is not a Nozzle, PipeConnector or
SpecificationBreak.

Example:
<PipingNetworkSegment … >
…
<Connection FromID="XMP_73" ToID="XMP_4" ToNode="2" />
…
</PipingNetworkSegment>

6.4.10 ConnectionPoints
This element is used to describe the potential flow connections from and to the parent of this
element. Each potential connection location is represented as a Node element. Nodes are
ordered and positioned on the drawing. Each Node element may be referenced by at most
one Connection element.
The first node (known as Node 0) represents the geometric origin of the parent of the
ConnectionPoints element.

© 2007 AVEVA Solutions Ltd 6:25 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:

Element Name Cardinality Description

Presentation 0..1 The Presentation element has no purpose
in this context.
Extent 0..1 The minimum bounding geometry of the
geometric contents of the
ConnectionPoints element and its
descendants.
Node 1..* The first node (Node 0) represents the
geometric location of the parent element.
Nodes 1..n represent the locations that
other elements may connect to.
GenericAttributes 0..* Any Application attributes related to
connectivity

Attributes:

Attribute Name Required Description

NumPoints Y The number of Node elements in this
ConnectionPoints element.
FlowIn N The index of the Node that is used for the
primary flow into the parent of the
ConnectionPoints element. This Defaults to
1 if not present.
FlowOut N The index of the Node that is used for the
primary flow from the parent of the
ConnectionPoints element. This defaults
to 2 if not present.

© 2007 AVEVA Solutions Ltd 6:26 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
nectionPoints NumPoints="4" FlowIn="1" FlowOut="2">
<!-- Node 0 : Geometric origin of the component -->
<Node>
<Position>
<Location X="337" Y="211" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
</Node>
<!-- Node 1 : FlowIn default -->
<Node>
<Position>
<Location X="337" Y="211" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<NominalDiameter Value="4" />
</Node>
<!-- Node 2 : FlowOut default -->
<Node>
<Position>
<Location X="337" Y="211" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<NominalDiameter Value="4" />
</Node>
<!-- Node 3 : Secondary flow, direction not stated -->
<Node>
<Position>
<Location X="337" Y="211" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<NominalDiameter Value="4" />
</Node>
</ConnectionPoints>

6.4.11 ConnectionType
This is a free form string element that may be unit qualified.
Child elements:
None
Attributes:

Attribute Name Required Description

Units N This may contain any of the permitted units
types See Units.

© 2007 AVEVA Solutions Ltd 6:27 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<ConnectionType>Welded</ConnectionType>

6.4.12 ControlPoints
Child elements :

Element Name Cardinality Description

Coordinate 1..*

Attributes:
None
Example:
<ControlPoints>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
<Coordinate X="10241.64" Y="10283.399" Z="41.0"/>
</ControlPoints>

6.4.13 ControlPointWeight
This is defined as an any but should be considered to be of type xsd:integer.
Child elements:
None
Attributes :
None
Example:
<ControlPointWeight>1</ControlPointWeight>

6.4.14 Coordinate
A Coordinate element is a Tuple of ordinates denoting a location in the drawing plane. For
2D drawings the Z ordinates should always be 0.
Child elements:
None
Attributes:

Attribute Name Required Description

X Y The X Axis ordinate as a double
Y Y The Y Axis ordinate as a double
Z N The Z Axis ordinate as a double, If not
present this defaults to 0.0

© 2007 AVEVA Solutions Ltd 6:28 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Coordinate X="112" Y="106" Z="0" />
<Coordinate X="112" Y="110" />

6.4.15 CrossPageConnection
An element describing how to match PipeConnector elements to represent cross page
connectivity on a P&ID.
Child elements:
None
Attributes:

Attribute Name Required Description

DrawingName N The Name attribute of the Drawing that the
matching PipeConnector is on. Depending
on whether the attribute for matching is
unique to a drawing or the entire project
this may be required.
AttributeName Y The attribute name on the PipeConnector
to use to match the connectors together.
This could be an ItemAttribute such as the
Tag or ID, or a member of a
GenericAttributes element.
AttributeValue Y The value of the attribute to match on.
Wildcards are not supported.
Set N If referencing an attribute inside a
GenericAttributes element then the Set of
the attribute should be provided.
If referencing a PersistentID attribute then
the Context attribute value of the
PersistentID should be provided here

Example:
<CrossPageConnection DrawingName="A1-51-2003-1"
AttributeName="PersistentID" AttributeValue="{SOME_ID_1}"
Context="http://www.aveva.com/example/P&amp;ID"/>

6.4.16 Description
A textual description of an item
Child elements:
None
Attributes:
None

© 2007 AVEVA Solutions Ltd 6:29 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Description>some piece of plant equipment</Description>

6.4.17 Discipline
This is a simple element with no attributes containing one of the following values to classify
an element:
Electrical
Mechanical
Process
HVAC
Telecomms
Example:
<Discipline>Mechanical</Discipline>

6.4.18 Drawing
This contains metadata about the drawing and graphical annotation for the drawing that the
XML file contains.
Child elements:

Element Name Cardinality Description

Presentation 1 The R, G and B values of this element
define the background colour for the
drawing. This is in contrast to the normal
use of the Presentation element that
defines foreground style information.
Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.
Component 0..* A PlantItem used to group annotation.
BsplineCurve 0..* A geometric primitive
Circle 0..* A geometric primitive
CompositeCurve 0..* A geometric primitive
Ellipse 0..* A geometric primitive
Line 0..* A geometric primitive
Polyline 0..* A geometric primitive
Shape 0..* A geometric primitive
TrimmedCurve 0..* A geometric primitive
Text 0..* Textual annotation on the drawing

© 2007 AVEVA Solutions Ltd 6:30 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

DrawingBorder 0..* This element may be used to store the
drawing border/outline but this is at the
discretion of the export tool.
GenericAttributes 0..* Any application specific properties relating
to the Drawing.

Attributes:

Attribute Name Required Description

Name Y Identity for the drawing, this must be
unique in the project.
Type Y Fixed value of ‘PID’
Revision N Free form string value. See Character
encoding
Title Y The drawing title
Size N This is a free text string and has no defined
syntax. See Character encoding.

Example:
<Drawing Name="A1-51-2003-1" Type="PID" Size="A0"
Title="Sample Project drawing" Revision="A">
<Presentation R="0" G="0" B="0" />
<Extent>
<Min X="0" Y="-2" Z="0" />
<Max X="850.0" Y="620.25" Z="0" />
</Extent>
<PolyLine NumPoints="4">…</PolyLine>
…
</Drawing>

6.4.19 DrawingBorder
This element may be used to separate the drawing frame and borders from the drawing
annotation.
Child elements:

Element Name Cardinality Description

Presentation 0..1 The Presentation element has no purpose
in this context.
Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.
BsplineCurve 0..* A geometric primitive
Circle 0..* A geometric primitive

© 2007 AVEVA Solutions Ltd 6:31 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

CompositeCurve 0..* A geometric primitive
Ellipse 0..* A geometric primitive
Line 0..* A geometric primitive
Polyline 0..* A geometric primitive
Shape 0..* A geometric primitive
TrimmedCurve 0..* A geometric primitive
Text 0..*
DrawingBorder 0..* This element may be used to store the
drawing border/outline but this is at the
discretion of the export tool.
GenericAttributes 0..* Any application specific properties relating
to the Drawing.

Attributes:

Attribute Name Required Description

Name N Identity for the drawing border
Size N This is a free text string and has no defined
syntax. See Character encoding.

Example:
<DrawingBorder Name="Top" Size="A0-Portrait">
<Presentation R="0" G="0" B="0" />
<Extent>
<Min X="0" Y="-2" Z="0" />
<Max X="850.0" Y="620.25" Z="0" />
</Extent>
<PolyLine NumPoints="4">…</PolyLine>
…
</DrawingBorder>

6.4.20 Ellipse
A geometric primitive used to describe an ellipse.
Child elements:

Element Name Cardinality Description

Presentation 1 This defines the drawing style to be used
for the ellipse.
Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.

© 2007 AVEVA Solutions Ltd 6:32 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

Position 1 The centre/origin of the ellipse to draw
GenericAttributes 0..* A geometric primitive

Attributes:

Attribute Name Required Description

PrimaryAxis Y Double describing the primary axis
SecondaryAxis Y double describing the secondary axis
Filled N A value of ‘Solid’ or ‘Hatch’. If not present
the ellipse is not filled.

Example:
<Ellipse PrimaryAxis="7.62" SecondaryAxis="3.83916">
<Presentation Layer="Default" LineType="Solid"
LineWeight="0.13 mm" Color="Red" R="1" G="0" B="0"/>
<Extent>
<Min X="184.52505999" Y="425.32167093" Z="0"/>
<Max X="199.76504821" Y="429.16757932" Z="0"/>
</Extent>
<Position>
<Location X="192.145059987" Y="425.328421759" Z="0"/>
<Axis X="0" Y="0" Z="1"/>
<Reference X="1" Y="0" Z="0"/>
</Position>
</Ellipse>

6.4.21 EndDiameter
This is the internal bore for a segment or a PipingNetworkSystem at its destination.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The bore size
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

Example:
<EndDiameter Value="4" />

<EndDiameter Value="200" Units="mm" />

© 2007 AVEVA Solutions Ltd 6:33 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.22 Equipment
An Equipment element inherits elements and attributes from the base type ‘PlantItem’. See
‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

Discipline 0..1 Functional domain of Equipment
NormalOperatingPressure 0..1
MinimumDesignPressure 0..1
MaximumDesignPressure 0..1
MinimumDesignTemperatu 0..1
re
MaximumDesignTemperat 0..1
ure
Equipment 0..* Equipment considered part of this
equipment
Nozzle 0..* Potential pipe connection to this equipment

Attributes:

Attribute Name Required Description

ProcessArea N A free form string identifying, if required,
the process area that this equipment
resides in (See Character encoding).
Purpose N A free form string describing the function of
this equipment in the process (see
Character encoding).

© 2007 AVEVA Solutions Ltd 6:34 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Equipment ID="XMP_12" Tag="P-1502B" ComponentClass="VerticalPump"
ComponentName="VPump" StockNumber="puv1">
<Extent>
<Min X="199.6153088" Y="155.02299606" Z="0" />
<Max X="236.78321894" Y="194.01149803" Z="0" />
</Extent>
<Position>
<Location X="221" Y="182" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<PersistentID Identifier="{A1-51-2003-1_Topology-EQUIPMENT-2}"
Context="http://www.aveva.com/example/P&amp;ID" />
…
<Nozzle ID="XMP_14" Tag="N2" ComponentClass="FlangedNozzle"
StockNumber="flnn1">
…
</Nozzle>
</Equipment>

6.4.23 Extent
A minimum bounding geometry describing the minimum and maximum coordinates of the
descendants of this elements parent.
Child elements:

Element Name Cardinality Description

Min 1 Minimum values for all geometric
descendants of the Extent elements
parent.
Max 1 Maximum values for all geometric
descendants of the Extent elements parent

Attributes:
None
Example:
<Extent>
<Min X="199.6153088" Y="155.02299606" Z="0" />
<Max X="236.78321894" Y="194.01149803" Z="0" />
</Extent>

6.4.24 FabricationCategory
This is a free form string element that may be unit qualified.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:35 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Units N This may contain any of the permitted units
types See Units.

Example:
None

6.4.25 GenericAttributes
This element permits application specific attributes/properties to be output into an XML file.
The properties themselves must adhere to the following complex type definition:
<complexType name="GenericAttributeType" mixed="true">
<attribute name="Format" type="xsd:string"/>
<attribute name="Value" type="xsd:string"/>
</complexType>

Child elements:

Element Name Cardinality Description

Xsd:any @Number The contents of a GenericAttributes
element are not validated and may be any
valid XML content. However the XML
applications will expect the contents to
conform to the schema fragment provided
above.

Attributes:

Attribute Name Required Description

Number Y The number of GenericAttributes inside
this set.
Set N A name for this grouping of attributes.

Example:
<GenericAttributes Number="6" Set="Instrument">
<TagSuffix Format="string" Value=" "/>
<LoopTagSuffix Format="string" Value=" "/>
<MeasuredVariableCode Format="string" Value="F"/>
<Description0 Format="string" Value="155"/>
<InstrumentTypeModifier Format="string" Value="CV"/>
<TagSequenceNo Format="string" Value="001"/>
</GenericAttributes>

6.4.26 GeometricPrimitives
A collection of geometric elements.

© 2007 AVEVA Solutions Ltd 6:36 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:

Element Name Cardinality Description

Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.
Surface 0..* A geometric primitive
BsplineCurve 0..* A geometric primitive
Circle 0..* A geometric primitive
CompositeCurve 0..* A geometric primitive
Ellipse 0..* A geometric primitive
Line 0..* A geometric primitive
Polyline 0..* A geometric primitive
Shape 0..* A geometric primitive
TrimmedCurve 0..* A geometric primitive

Attributes:

Attribute Name Required Description

NumPrimitives N The number of primitives inside this set. (=
number of child elements -1)

Example:
<GeometricPrimitives NumPrimitives="3">
<Extent>
<Min X="53" Y="125" Z="0"/>
<Max X="89" Y="130" Z="0"/>
</Extent>
<Circle ... />
<Circle ... />
<Surface ... />
</GeometricPrimitives>

6.4.27 Height
This is the height of the Nozzle origin on it’s parent Equipment, measured from the origin of
the Equipment.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:37 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value Y The height value
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

Example:
<Height Value="1.3" Units="m"/>

6.4.28 History
This is provided to contain an audit trail of the changes to an item.
Child elements:

Element Name Cardinality Description

Transaction 0..* An entry in the audit trail

Attributes:

Attribute Name Required Description

NumTransactions Y The number of Transaction child elements

Example:
<History NumTransaction="3">
<Transaction ... />
<Transaction ... />
<Transaction ... />
</History>

6.4.29 Identifier
This element is used to capture the structure of an identifier such as a Tag. Not usually
used.
Child elements:

Element Name Cardinality Description

IdentifierElement 0..* A structural component of an identifier.

Attributes:

Attribute Name Required Description

Purpose N A string describing the purpose of this
element.

© 2007 AVEVA Solutions Ltd 6:38 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Identifier Purpose="Tag breakdown">
<IdentifierElement Name="start" Value="AB-"/>
<IdentifierElement Name="middle" ItemID="XMP_24"
DependantAttribute="[Prefix]-[Number]"/>
</Identifier>

6.4.30 IdentifierElement
A structural element describing part of the structure of an identifier.
Child elements:
None
Attributes:

Attribute Name Required Description

Name Y The name of this part of the identifier
Value N Only required if dependantAttribute is not
provided.
ItemID N Only required if an attribute is referenced
on another item.
DependantAttribute N References an attribute from which this
part of the identifier is derived. See Textfor
a description of how this attribute is
defined.

Example:
<IdentifierElement Name="start" Value="AB-"/>

<IdentifierElement Name="middle" ItemID="XMP_24"

DependantAttribute="[Prefix]-[Number]"/>

6.4.31 InsideDiameter
This is the internal bore for an item at its source end.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The bore size
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

© 2007 AVEVA Solutions Ltd 6:39 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<InsideDiameter Value="4" />

<InsideDiameter Value="200" Units="mm" />

6.4.32 InstrumentLoop
A collection of related instruments. This element inherits elements and attributes from the
base type ‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents. Inline
instruments are associated to instrument loops by using the Association element.
Child elements:

Element Name Cardinality Description

ProcessInstrument 0..* An off-line instrument that is part of this set.
SignalLine 0..*
SignalConnectorSymbol 0..*
Connection 0..*

Attributes:
See ‘PlantItem’, no additional attributes are defined.
Example:
<InstrumentLoop ID="XMP_123">
<Extent>
<Min X="355" Y="339" Z="0" />
<Max X="481" Y="355" Z="0" />
</Extent>
<SignalLine ... />
<SignalLine ... />
<SignalLine ... />
<ProcessInstrument ... />
<ProcessInstrument ... />
</InstrumentLoop>

6.4.33 KnotMultiplicities
Child elements:

Element Name Cardinality Description

Multiplicity 1..*

Attributes:
None

© 2007 AVEVA Solutions Ltd 6:40 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<KnotMultiplicities>
<Multiplicity>4</Multiplicity>
<Multiplicity>4</Multiplicity>
</KnotMultiplicities>

6.4.34 Knot
This is defined as an any but should be considered to be of type xsd:integer.
Child elements :
None
Attributes:
None
Example:
<Knot>1</Knot>

6.4.35 Knots
Child elements:

Element Name Cardinality Description

Knot 1..*

6.4.36 Line
A linear geometry defined by two points.
Child elements:

Element Name Cardinality Description

Presentation 1 This defines the drawing style to be used
for the ellipse.
Extent 1 The minimum bounding geometry of the
geometric contents of the Drawing element
and its descendants.
Coordinate 2 The coordinates defining the start and end
of the line.
GenericAttributes 0..* A geometric primitive

Attributes:
None

© 2007 AVEVA Solutions Ltd 6:41 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Line>
<Presentation LineWeight="1" LineType="Solid" Color="red"
R="1" G="0" B="0" />
<Extent>
<Min X="831" Y="502.6" Z="0" />
<Max X="841" Y="502.6" Z="0" />
</Extent>
<Coordinate X="841" Y="502.6" Z="0" />
<Coordinate X="831" Y="502.6" Z="0" />
</Line>

6.4.37 Location
A Location element matches the definition of a Coordinated, it is a Tuple of ordinates
denoting a location in the drawing plane. For 2D drawings the Z ordinates should always be
0.
Child elements:
None
Attributes:

Attribute Name Required Description

X Y The X Axis ordinate as a double
Y Y The Y Axis ordinate as a double
Z N The Z Axis ordinate as a double, If not
present this defaults to 0.0

Example:
<Location X="112" Y="106" Z="0" />
<Location X="112" Y="110" />

6.4.38 Manufacturer
The manufacturer responsible for producing the item
Child elements:
None
Attributes:
None
Example:
<Manufacturer>My company</Manufacturer>

6.4.39 Material
The name of the Material used to construct the item
Child elements:

© 2007 AVEVA Solutions Ltd 6:42 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

None
Attributes:
None
Example:
<Material>Copper</Material>

6.4.40 MaterialDescription
A description of the material relating to an item
Child elements:
None
Attributes:
None
Example:
<MaterialDescription>Some descriptive text</MaterialDescription>

6.4.41 Max
Maximum coordinates for an Extent element
Child elements:
None
Attributes:

Attribute Name Required Description

X Y X axis value denoting the maximum X
value for all geometric descendants of ../..
Y Y Y axis value denoting the maximum Y
value for all geometric descendants of ../..
Z Y Z axis value denoting the maximum Z
value for all geometric descendants of ../..
For 2D drawings this should always be 0

Example:
<Max X="236.78321894" Y="194.01149803" Z="0" />

6.4.42 MaximumDesignPressure
The maximum design pressure for an item.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:43 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value Y The maximum design pressure
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MaximumDesignPressure Value="12" />

<MaximumDesignPressure Value="35" Units="bar" />

6.4.43 MaximumDesignTemperature
The maximum design temperature for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The maximum design temperature
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MaximumDesignTemperature Value="12" />

<MaximumDesignTemperature Value="35" Units="DegreeCelsius" />

6.4.44 MaximumOperatingPressure
The maximum operating pressure for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The maximum pressure
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

© 2007 AVEVA Solutions Ltd 6:44 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<MaximumOperatingPressure Value="12" />
<MaximumOperatingPressure Value="35" Units="bar" />

6.4.45 MaximumOperatingTemperature
The maximum operating temperature for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The maximum temperature
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MaximumOperatingTemperature Value="12" />
<MaximumOperatingTemperature Value="35" Units="DegreeCelsius" />

6.4.46 Min
Child elements:
None
Attributes:

Attribute Name Required Description

X Y X axis value denoting the minimum X value
for all geometric descendants of ../… This
is a double
Y Y Y axis value denoting the minimum Y value
for all geometric descendants of ../.. This
is a double
Z Y Z axis value denoting the minimum Z value
for all geometric descendants of ../.. This
is a double.
For 2D drawings this should always be 0.

Example:
<Min X="199.6153088" Y="155.02299606" Z="0" />

6.4.47 MinimumDesignPressure
This is the minimum design pressure for an item.

© 2007 AVEVA Solutions Ltd 6:45 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The minimum design pressure as a double.
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MinimumDesignPressure Value="12" />
<MinimumDesignPressure Value="35" Units="bar" />

6.4.48 MinimumDesignTemperature
This is the minimum design temperature for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The minimum design temperature as a
double.
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MinimumDesignTemperature Value="12" />
<MinimumDesignTemperature Value="35" Units="DegreeCelsius" />

6.4.49 MinimumOperatingPressure
This is the minimum operating pressure for an item.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:46 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value Y The minimum pressure as a double.
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MinimumOperatingPressure Value="12" />
<MinimumOperatingPressure Value="35" Units="bar" />

6.4.50 MinimumOperatingTemperature
This is the minimum operating temperature for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The minimum temperature as a double.
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

Example:
<MinimumOperatingTemperature Value="12" />

<MinimumOperatingTemperature Value="35" Units="DegreeCelsius" />

6.4.51 ModelNumber
String element detailing the model number for a component.
Child elements:
None
Attributes:
None
Example:
<ModelNumber>A485798347-BjiOM-9347</ModelNumber>

6.4.52 Multiplicity
This is defined as an any but should be considered to be of type xsd:integer.
Child elements:

© 2007 AVEVA Solutions Ltd 6:47 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

None
Attributes:
None
Example:
<Multiplicity>4</Multiplicity>

6.4.53 NominalDiameter
This is the internal bore for an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The bore size as a double
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

Example:
<NominalDiameter Value="4" />
<NominalDiameter Value="200" Units="mm" />

6.4.54 NormalDesignPressure
Design pressure of an item under normal conditions.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The pressure value as a double
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<NormalDesignPressure Value="4" />
<NormalDesignPressure Value="3" Units="barg" />

6.4.55 NormalDesignTemperature
Design temperature of an item under normal conditions.

© 2007 AVEVA Solutions Ltd 6:48 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The temperature value as a double
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

Example:
<NormalDesignTemperature Value="52" />
<NormalDesignTemperature Value="80" Units="DegreeCelsius" />

6.4.56 NormalOperatingPressure
Operating pressure of an item under normal conditions.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The pressure value as a double
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<NormalOperatingPressure Value="4" />
<NormalOperatingPressure Value="3" Units="barg" />

6.4.57 NormalOperatingTemperature
Operating temperature of an item under normal conditions
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The temperature value as a double
Units N This may be any of the temperature units
permitted. See Units for permitted values
and semantics if not present.

© 2007 AVEVA Solutions Ltd 6:49 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<NormalOperatingTemperature Value="52" />
<NormalOperatingTemperature Value="80" Units="DegreeCelsius" />

6.4.58 Nozzle
A Nozzle element inherits elements and attributes from the base type ‘PlantItem’. See
‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

NozzleType 0..1
NominalDiameter 0..1 Internal nominal bore of nozzle
Height 0..1 Height of Nozzle on the Equipment

Attributes:
See ‘PlantItem’, no additional attributes
Example:
<Nozzle ID="XMP_10" Tag="N1" ComponentClass="FlangedNozzle">
<Extent>
<Min X="205.47371879" Y="245.5" Z="0" />
<Max X="215" Y="263" Z="0" />
</Extent>
<Position>
<Location X="215" Y="255" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="-1" Y="0" Z="0" />
</Position>
<PersistentID Identifier="{A1-51-2003-1_Topology-NOZZLE-1}"
Context="http://www.aveva.com/example/P&amp;ID" />
<Line>
<Presentation LineType="Solid" LineWeight="1"
R="0.25" G="0.82" B="0.15" />
<Extent>
<Min X="211" Y="255" Z="0" />
<Max X="215" Y="255" Z="0" />
</Extent>
<Coordinate X="211" Y="255" Z="0" />
<Coordinate X="215" Y="255" Z="0" />
</Line>
…
<NominalDiameter Value="4" />
</Nozzle>

6.4.59 NozzleType
This is a simple element with one attribute and no contents
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:50 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value N One of ‘Welded’, ‘Flanged’ or ‘Elbow’.
This defaults to ‘Flanged’ if the Value
attribute isn’t present.

Example:
<NozzleType Value="Flanged"/>

6.4.60 OperatorType
This is a free form string element that may be unit qualified.
Child elements:
None
Attributes:

Attribute Name Required Description

Units N This may contain any of the permitted units
types See Units.

Example:
None

6.4.61 OutsideDiameter
This is the external diameter of an item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The external diameter measurement as a
double
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

Example:
<OutsideDiameter Value="4" />
<OutsideDiameter Value="200" Units="mm" />

6.4.62 PConnectionPoints
See Issues.

© 2007 AVEVA Solutions Ltd 6:51 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.63 PersistentID
The PersistentID element contains a source system identifier for an object that remains
consistent between exports of a drawing. A PersistentID is made up of two components the
identifier and its scope.
A PersistentID should be the same for an object that appears on multiple drawings where it
is practicable to do this. If this cannot be achieved the T, if present, will be used by P&ID
Manager for rationalising objects.
Child elements:
None
Attributes:

Attribute Name Required Description

Identifier Y The persistent identifier for an XML
element.
The Identifier must be unique within the set
of XML files that may interact directly or
indirectly with this drawing for the stated
context.
This a free form string type, see Character
encoding.
Context N This scopes a persistent identifier.
In this way an item may have different
Identifiers for different systems/contexts
and each identifier may be represented.
Ideally this would be encoded as a URI.
For example http://www.aveva.com/P&ID
Designer/ProjectName.

Example:
<PersistentID
Identifier="{A1-51-2003-1_Topology-NOZZLE-1}"
Context="http://www.aveva.com/example/P&amp;ID" />

6.4.64 PipeConnector
An on or off page connector that represents the connectivity of a PipingNetworkSegment
across a page boundary. These are contained by the PipingNetworkSegment elements and
reference as the segment source or destination.
A PipeConnector element inherits elements and attributes from the base type ‘PlantItem’.
See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

CrossPageConnection 0..1 Information describing the matching criteria
for the PipeConnector that is connected to
this one.

© 2007 AVEVA Solutions Ltd 6:52 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:
See ‘PlantItem’, no Additional attributes
Example:
<PipeConnector ID="XMP_92" Tag="A1-51-2003-3" StockNumber="flag1">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent … />
<Position … />
<PersistentID … />
<PolyLine … />
<Text … />
<CrossPageConnection … />
</PipeConnector>

6.4.65 PipeFlowArrow
This element is an annotation primitive to represent the direction of flow of a
PipingNetworkSegment.
A PipeFlowArrow element inherits elements and attributes from the base type ‘PlantItem’.
See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:
See ‘PlantItem’, no additional elements
Attributes:
See ‘PlantItem’, no additional attributes

© 2007 AVEVA Solutions Ltd 6:53 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<PipeFlowArrow ID="XMP_29" >
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="671" Y="148" Z="0" />
<Max X="673" Y="152" Z="0" />
</Extent>
<Position>
<Location X="672" Y="148" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="0" Y="1" Z="0" />
</Position>
<PolyLine NumPoints="42">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="671" Y="148" Z="0" />
<Max X="673" Y="152" Z="0" />
</Extent>
<Coordinate X="671" Y="152" Z="0" />
<Coordinate X="672" Y="148" Z="0" />
<Coordinate X="673" Y="152" Z="0" />
<Coordinate X="671" Y="152" Z="0" />
</PolyLine>
</PipeFlowArrow>

6.4.66 PipingNetworkSystem
A PipingNetworkSystem contains the information for a physical PipingNetworkSystem in the
plant or a section thereof as contained within a module. The PipingNetworkSystem contains
all of the PlantItems that belong to it. A PipingNetworkSystem may have multiple sources
and multiple destinations.'
A PipingNetworkSystem element inherits elements and attributes from the base type
‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

NominalDiameter 0..1
InsideDiameter 0..1
OutsideDiameter 0..1
StartDiameter 0..1
EndDiameter 0..1
NormalDesignPressure 0..1
MinimumDesignPressure 0..1
MaximumDesignPressure 0..1
NormalDesignTemperature 0..1

© 2007 AVEVA Solutions Ltd 6:54 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

MinimumDesignTemperatu 0..1
re
MaximumDesignTemperat 0..1
ure
NormalOperatingPressure 0..1
MinimumOperatingPressur 0..1
e
MaximumOperatingPressu 0..1
re
TestPressure 0..1
NormalOperatingTemperat 0..1
ure
MiniumumOperatingTemp 0..1
erature
MaximumOperatingTempe 0..1
rature
WallThickness 0..1
Connection 0..* Not used as connectivity should be
represented by each contained
PipingNetworkSegment.
PipingNetworkSegment 0..* The segments that make up the
PipingNetworkSystem
SpecificationBreak 0..* Points at which changes occur in the pipe
specification. This causes a break in the
segment.

Attributes:
See ‘PlantItem’, no additional attributes
Example:
<PipingNetworkSystem ID="PLINE_1">
<Extent ... />
<PersistentID ... />
<NominalDiameter ... />
<MinimumDesignPressure ... />
<MaximumDesignPressure ... />
<PipingNetworkSegment ... />
<PipingNetworkSegment ... />
<PipingNetworkSegment ... />
<SpecificationBreak ... />
</PipingNetworkSystem>

© 2007 AVEVA Solutions Ltd 6:55 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.67 PipingComponent
This represents a physical component that is common to piping systems.
A PipingComponent element inherits elements and attributes from the base type ‘PlantItem’.
See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

PipingComponent 0..* Contained PipingComponent.
ConnectionType 0..1
NominalDiameter 0..1
InsideDiameter 0..1
None 0..1
Outside Diameter
OperatorType 0..1
WallThickness 0..1
FabricationCategory 0..1

Attributes:

Attribute Name Required Description

ConnectionType N This is a free text string and has no defined
syntax. See Character encoding
Rating N This is a free text string and has no defined
syntax. See Character encoding
Standard N This is a free text string and has no defined
syntax. See Character encoding
ISOSymbol N This is a free text string and has no defined
syntax. See Character encoding

© 2007 AVEVA Solutions Ltd 6:56 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<PipingComponent ID="PipeTee_5" ComponentClass="PipeTee">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="112" Y="182" Z="0" />
<Max X="112" Y="182" Z="0" />
</Extent>
<Position>
<Location X="112" Y="182" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<PersistentID … />
<ConnectionPoints NumPoints="4" FlowIn="1" FlowOut="2" … />
</PipingComponent>

6.4.68 PipingNetworkSegment
A PipingNetworkSegment is a subsection of a PipingNetworkSystem where the engineering
parameters are common. A PipingNetworkSegment will start at a Nozzle,
SpecificationBreak or the downstream end of a Reducer or Tee and end at a Nozzle,
SpecificationBreak, Reducer, Tee or an open pipe. For a P&ID it can also start or end with a
PipeConnector. It will contain one or more CenterLine, PipingComponent, Equipment and
ProcessInstrument elements. For a P&ID it is the CenterLines that join the successive
components together and these should be considered in the same way as the other
symbols and all must occur in the order head to tail.
A PipingNetworkSegment element inherits elements and attributes from the base type
‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents.
PipeConnectors representing on and off page connectivity are contained by the
PipingNetworkSegment. See for details of PipingNetworkSegment connectivity.
Child Elements:

Element Name Cardinality Description

NominalDiameter 0..1
InsideDiameter 0..1
None 0..1
Outside Diameter
StartDiameter 0..1
EndDiameter 0..1
NormalDesignPressure 0..1
MinimumDesignPressure 0..1
MaximumDesignPressure 0..1
NormalDesignTemperature 0..1

© 2007 AVEVA Solutions Ltd 6:57 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Element Name Cardinality Description

MinimumDesignTemperatu 0..1
re
MaximumDesignTemperat 0..1
ure
NormalOperatingPressure 0..1
MinimumOperatingPressur 0..1
e
MaximumOperatingPressu 0..1
re
TestPressure 0..1
NormalOperatingTemperat 0..1
ure
MinimumOperating 0..1
Temperature
MaximumOperatingTempe 0..1
rature
WallThickness 0..1
Connection 0..* This states the head and tail connectivity of
this segment.
PipingNetworkSegment 0..* The segments that make up the
PipingNetworkSystem
SpecificationBreak 0..* Points at which changes occur in the pipe
specification. This causes a break in the
segment.
CenterLine 0..*
Equipment 0..*
PipingComponent 0..*
ProcessInstrument 0..*
PipeConnector 0..*
PipeFlowArrow 0..*

Attributes:
See ‘PlantItem’, no additional attributes

© 2007 AVEVA Solutions Ltd 6:58 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<PipingNetworkSegment ID="XMP_86" Tag="B-902" Specification="A3B">
<Extent>
<Min X="227" Y="118" Z="0" />
<Max X="337" Y="211" Z="0" />
</Extent>
<PersistentID Identifier="{A1-51-2003-1_Topology-SEGMENT-1}"
Context="http://www.aveva.com/example/P&amp;ID" />
<Connection FromID="XMP_73" ToID="XMP_87" ToNode="2" />
<NominalDiameter Value="4" />
<PipeFlowArrow ID="XMP_78" … />
<CenterLine NumPoints="3">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="227" Y="118" Z="0" />
<Max X="227" Y="132" Z="0" />
</Extent>
<Coordinate X="227" Y="118" Z="0" />
<Coordinate X="227" Y="132" Z="0" />
<Coordinate X="291" Y="132" Z="0" />
</CenterLine>
<PipingComponent ID="XMP_87" ComponentClass="PipeTee" … />
</PipingNetworkSegment>

6.4.69 PlantArea
In the P&ID content of an XML file this is just an object that may be used to represent the
name and attributes of named part(area) of a plant. A plant Area is not permitted to contain
model elements but may be referenced to associated segments, Equipment etc with a
named PlantArea.
A PlantArea element inherits elements and attributes from the base type ‘PlantItem’. See
‘PlantItem’ for the definitions of the inherited contents.
Child elements:
See ‘PlantItem’, no additional elements
Attributes:

Attribute Name Required Description

Name N A string representing the name of the area.
See Character encoding.

Example:
<PlantArea Name="Area-42">
<Extent .. />
<Association ../>
<Association ../>
<Association ../>
</PlantArea>

© 2007 AVEVA Solutions Ltd 6:59 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.70 PlantInformation
This element collects the metadata for a PlantModel. The Date and Time attributes should
be the Date and Time of the XML file creation.
Child elements:

Element Name Cardinality Description

UnitsOfMeasure 1 Defines the default units of measure for the
file.

Attributes:

Attribute Name Required Description

SchemaVersion Y Fixed value of ‘3.1.2’
OriginatingSystem Y Free form string. See Character encoding
ModelName N Free form string. See Character encoding
Date Y XML date of the format YYYY-MM-DD
ProjectName N Free form string. See Character encoding
ProjectCode N Free form string. See Character encoding
ProjectDescription N Free form string. See Character encoding
CompanyName N Free form string. See Character encoding
Time Y XML time type, assumed UTC unless zone
qualified
Is3D Y Fixed value of ‘no’
Units Y The distance units of measure for the
geometry in the file.
Discipline Y Fixed value of ‘PID’

Example:
<PlantInformation SchemaVersion="3.1.2"
OriginatingSystem="VPEPID"
ModelName="http://www.aveva.com/P&amp;ID/example"
Date="2006-12-12" Time="16:43:23"
Is3D="no" Units="Millimetre" Discipline="PID">
<UnitsOfMeasure Distance="Inch" />
</PlantInformation>

6.4.71 PlantItem
This element is a base abstract type of many elements within an XML file, it defines the
common elements and attributes for these items.

© 2007 AVEVA Solutions Ltd 6:60 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Child elements:

Element Name Cardinality Description

Presentation 0..1
Extent 1
PersistentID 0..*
Position 1
Scale 0..1
Surface 0..*
Circle 0..*
CompositeCurve 0..*
Ellipse 0..*
Line 0..*
Polyline 0..*
Shape 0..*
TrimmedCurve 0..*
BsplineCurve 0..*
GeometricPrimitives 0..*
ConnectionPoints 0..1
PConnectionPoints 0..1
Text 0..*
Identifier 0..*
Description 0..1
Weight 0..1
Material 0..1
MaterialDescription 0..1
ModelNumber 0..1
Supplier 0..1
Manufacturer 0..1
GenericAttributes 0..*
Association 0..*
History 0..1

© 2007 AVEVA Solutions Ltd 6:61 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

ID Y The sequential ID if the item in the file. Of
the form ‘XMP_nnn’ where n is the
sequential number as an integer. E.g.
XMP_22. See ID
Tag N See Tag
Specification N See Specification
StockNumber N See StockNumber
ComponentClass N See ComponentClass
ComponentName N See ComponentName
ComponentType N See ComponentType
Revision N See Revision
Status N See Status

Example:
N/A since the type is abstract

6.4.72 Point
A geometric primitive representing a one dimensional geometry.
Child elements:

Element Name Cardinality Description

Presentation 1 The style used to draw the point.
Location 1 The point coordinate
GenericAttributes 0..* Any application attributes for this point

Attributes:

Attribute Name Required Description

IsVisible N Valid values: ‘true’, ‘false’, ‘1’ or ‘0’.
Set to ‘false’ or ‘0’ if this point should not be
drawn.

Example:
<Point>
<Presentation LineType="Solid" LineWeight="1"
Color="22" R="0.79" G="0.239" B="0.087" />
<Location X="714.387976347" Y="261.753285151" Z="0" />
</Point>

© 2007 AVEVA Solutions Ltd 6:62 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.73 PolyLine
Geometric curve primitive detailing a polyline. The interpolation between each coordinate is
linear.
Child elements:

Element Name Cardinality Description

Presentation 0..1 The style to use when drawing the line.
The drawing behaviour is undefined if the
Presentation element is missing.
Extent 1 The minimum bounding geometry of the
element and its descendants
Coordinate 1..* The coordinates defining the line primitive

Attributes:

Attribute Name Required Description

NumPoints Y The number of child Coordinate elements.

Example:
<PolyLine NumPoints="2">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="77" Y="463" Z="0" />
<Max X="646" Y="463" Z="0" />
</Extent>
<Coordinate X="77" Y="463" Z="0" />
<Coordinate X="646" Y="463" Z="0" />
</PolyLine>

6.4.74 Position
This defines the place where an items origin is on a P&ID drawing. This is in effect the
location of the items symbol. The Axis and Reference attributes are used to define the
coordinate orientation in 3D space. The drawing is considered to be on the plane of Z=0.
Child elements:
Attributes:
None
Example:
<Position>
<Location X="716.06" Y="268.76" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>

© 2007 AVEVA Solutions Ltd 6:63 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.75 Presentation
The element defines a styles used to draw geometric and textual content. Whle all
attributes are defined as optional in the schema the R, G, B, LineWeight and LineType
attributes are expected for all geometric primitives, otherwise the behaviour is undefined.
Child elements:
None
Attributes:

Attribute Name Required Description

Layer N Name of the layer in which the graphical
elements resides. This has no functional
semantics associated with it.
Color N A lookup in a color index. This isn’t to be
used for P&ID Manager P&ID files.
LineType N One of the numbers or names from the
following (Object Model document v2.2):-
0 Solid
1 Dotted
2 Dashed
3 Long Dash
4 Long Dash + Short Dash,
CenterLine
5 Short Dash
6 Long Dash + Short Dash + Short
Dash
7 Dash + Short Dash
LineWeight N <real>
or
<real><units>
or
<real><space><units>
Where:-
<real> is an real value.
<space> is a space character (&#20;)
<units> is a distance units from Units
If the value isn’t qualified with units
then the behaviour is undefined.
R N 0 to 1 (double) 1 = maximum intensity of
Red component.
G N 0 to 1 (double) 1 = maximum intensity of
Green component.
B N 0 to 1 (double) 1 = maximum intensity of
blue component.

© 2007 AVEVA Solutions Ltd 6:64 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Presentation LineType="Solid" LineWeight="2mm"
Color="22" R="0.8" G="0.25" B="0.1" />

6.4.76 ProcessInstrument
This represents a physical instrument that is common to piping systems.
A ProcessInstrument element inherits elements and attributes from the base type
‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

PlantItem 0..* Contained PipingComponent.
NominalDiameter 0..1
InsideDiameter 0..1
None 0..1
Outside Diameter
OperatorType 0..1
WallThickness 0..1

Attributes:
See ‘PlantItem’, no additional attributes
Example:
<ProcessInstrument ID="XMP_33" Tag="LT-117"
ComponentClass="LevelTransmitter">
<Extent>
<Min X="710" Y="258" Z="0" />
<Max X="726" Y="274" Z="0" />
</Extent>
<Position>
<Location X="718" Y="266" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
<Circle Radius="8" … />
<Text … />
</ProcessInstrument>

6.4.77 Rating
This is a unit qualified string value to describe the rating of an item.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:65 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value Y Maximum safe load
Units N This may be any of the units permitted
since the type of measurement isn’t
specified. See Units for permitted values,
the semantics if Units are not present are
unclear.

Example:
<Rating Value="5" Units="bar"/>

6.4.78 Reference
See Geometries (Axis and Reference).
Child elements:
None
Attributes:

Attribute Name Required Description

X Y Double
Y Y Double
Z Y Double

Example:
<Reference X="1" Y="0" Z="0" />

6.4.79 Remark
A string comment element
Child elements:
None
Attributes:
None
Example:
<Remark>WP2134</Remark>

6.4.80 Scale
The scale element is used when symbols are drawn from a shape catalogue. The Scale
element enables symbols to be rescaled when positioned in a drawing.
Child elements:

© 2007 AVEVA Solutions Ltd 6:66 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

None
Attributes:

Attribute Name Required Description

X Y X scale factor
Y Y Y scale factor
Z N Z scale factor

Example:
<Scale X="2" Y="2" />

6.4.81 Shape
The Shape element defines a closed curve. The interpolation between each coordinate is
linear.
Child elements:

Element Name Cardinality Description

Presentation 0..1 The style to use when drawing the line.
The drawing behaviour is undefined if the
Presentation element is missing.
Extent 1 The minimum bounding geometry of the
element and its descendants
Coordinate 4..* The coordinates defining the primitive. The
first coordinate should match the last to
complete a closed form.
GenericAttributes 0..* Any application specific attributes

Attributes:

Attribute Name Required Description

NumPoints Y The number of child Coordinate elements.
Filled N One of ‘Solid’ or ‘Hatch’ used to specify a
fill technique

© 2007 AVEVA Solutions Ltd 6:67 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Shape NumPoints="4" Filled="Solid" >
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="77" Y="463" Z="0" />
<Max X="646" Y="534" Z="0" />
</Extent>
<Coordinate X="77" Y="463" Z="0" />
<Coordinate X="77" Y="534" Z="0" />
<Coordinate X="646" Y="463" Z="0" />
<Coordinate X="77" Y="463" Z="0" />
</Shape>

6.4.82 ShapeCatalogue
A Shape Catalogue defines a symbol library for a file. The elements for which the symbols
can be defined are currently limited to Equipment and PipingComponent elements only.
See ComponentName for how to reference and name a symbol in the catalogue.
See Scale for how to scale symbols when drawn.
Child elements:

Element Name Cardinality Description

Equipment 0..* Equipment symbols
PipingComponent 0..* PipingComponent symbols
Nozzle 0..* Nozzle symbols
ProcessInstrument 0..* ProcessInstrument symbols
Component 0..* Component symbols
PipeConnector 0..* PipeConnector symbols
SignalConnectorSymbol 0..* SignalConnector symbols

Attributes:

Attribute Name Required Description

Name Y The name of the symbol catalogue, this is a
string attribute.
Version N The version of the symbol set.

© 2007 AVEVA Solutions Ltd 6:68 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attribute Name Required Description

Units N The distance units that the symbols are
defined in. This affects the size of the
symbol with respect to the units defined by
the PlantInformation/UnitsOfMeasure/
@Distance attribute. i.e if Units is different
to the PlantInformation default then the
symbol is scaled.
See the distance section of Units for valid
values.
Date N The date the symbol library was created/
modified.

Example:
<ShapeCatalogue Name="Symbols">
<Equipment ID="XMP_22" ComponentClass="VerticalPump"
ComponentName="VPump">
<Extent … />
<Position … />
<PersistentID … />
<Circle … />
…
</Equipment>
<ShapeCatalogue>

6.4.83 SignalConnectorSymbol
An on or off page connector that represents the connectivity of a SignalLine across a page
boundary.
A SignalConnectorSymbol element inherits elements and attributes from the base type
‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

CrossPageConnection 0..1 Information describing the matching criteria
for the SignalConnector that is connected
to this one.

Attributes:
See ‘PlantItem’, no additional attributes

© 2007 AVEVA Solutions Ltd 6:69 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<SignalConnectorSymbol ID="XMP_92">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent … />
<Position … />
<PersistentID … />
<PolyLine … />
<Text … />
<CrossPageConnection … />
</SignalConnectorSymbol>

6.4.84 SignalLine
A connection between two instruments carrying instrumentation signals.
A SignalLine element inherits elements and attributes from the base type ‘PlantItem’. See
‘PlantItem’ for the definitions of the inherited contents.
Child elements:

Element Name Cardinality Description

CenterLine 0..* The graphical representation of the
connectivity.
ProcessInstrument 0..* Instruments contained in this signal line.
Connection 0..1 The connectivity details of this SignalLine
SignalConnectorSymbol 0..* An off/on page connector for signal lines.

Attributes:
See ‘PlantItem’, no additional attributes

© 2007 AVEVA Solutions Ltd 6:70 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<SignalLine ID="XMP_86" Tag="B-902" >
<Extent>
<Min X="227" Y="118" Z="0" />
<Max X="337" Y="211" Z="0" />
</Extent>
<PersistentID Identifier="{A1-51-2003-1_Topology-SIGNALLINE-1}"
Context="http://www.aveva.com/example/P&amp;ID" />
<Connection FromID="XMP_73" ToID="XMP_87" ToNode="2" />
<NominalDiameter Value="4" />
<CenterLine NumPoints="3">
<Presentation LineType="Solid" LineWeight="1"
Color="7" R="1" G="1" B="1" />
<Extent>
<Min X="227" Y="118" Z="0" />
<Max X="227" Y="132" Z="0" />
</Extent>
<Coordinate X="227" Y="118" Z="0" />
<Coordinate X="227" Y="132" Z="0" />
<Coordinate X="291" Y="132" Z="0" />
</CenterLine>
<ProcessInstrument ID="XMP_87" … />
</SignalLine>

6.4.85 SpecificationBreak
This represents the point at which there is a change in specification of the piping. See
Issues.
A SpecificationBreak element inherits elements and attributes from the base type
‘PlantItem’. See ‘PlantItem’ for the definitions of the inherited contents.
A SpecificationBreak may only be contained by a PipingNetworkSystem element.
Child elements :
(See ‘PlantItem’) No Additional elements
Attributes :
(See ‘PlantItem’) No Additional attributes
Example :
<SpecificationBreak ID="XMP_34">
<Description>Change in Insulation</Description>
</SpecificationBreak>

6.4.86 StartDiameter
This is the internal bore for a segment or a PipingNetworkSystem at its source.
Child elements:
None

© 2007 AVEVA Solutions Ltd 6:71 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Value Y The bore size
Units N This may be any of the distance units
permitted. See Units for permitted values
and semantics if not present.

Example:
<StartDiameter Value="4" />
<StartDiameter Value="200" Units="mm" />

6.4.87 String
A string value used to annotate a drawing. Each element represents a single line of text.
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The string value
Units N Any units associated with the string value, not
sure how to use this.

Example:
<String Value="1. my text annotation"/>
<String Value="2. a second line of text"/>

6.4.88 Supplier
This is the name of the supplier for an item.
Child elements:
None
Attributes:
None
Example:
<Supplier>My supplier</Supplier>

6.4.89 Surface
See Issues.

© 2007 AVEVA Solutions Ltd 6:72 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

6.4.90 TestPressure
The pressure that should be used to test an item
Child elements:
None
Attributes:

Attribute Name Required Description

Value Y The pressure
Units N This may be any of the pressure units
permitted. See Units for permitted values
and semantics if not present.

Example:
<TestPressure Value="60" Units="bar"/>

6.4.91 Text
This defines the textual annotation for a drawing. The text may be provided in an attribute,
referenced using attributes on this item, referenced on attributes of another item or provided
as a set of String elements.
Child elements:

Element Name Cardinality Description

Presentation 1 The style to use to draw the text.
Extent 1 The minimum bounding rectangle around
the text.
Position 1 The position of the text
String 0..* Used when the text contains a line break.
GenericAttributes 0..* Any application specific attributes, this
could include attributes that contain the text
content to write.

Attributes:

Attribute Name Required Description

NumLines N The number of text lines being
represented. If not present then a value of
1 is assumed.
String N If present this is the text to be drawn. If the
text contains a line break then it should be
split into the String child elements instead
of being in the attribute or the line break
character replaced with an appropriate
character reference.

© 2007 AVEVA Solutions Ltd 6:73 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attribute Name Required Description

Font Y The font family name to use.
Justification The location of Position within the Text to
be written. Where the text is on multiple
lines then Justification denotes the location
of Position for the first line of text.
One of the following:
LeftTop
LeftCenter
LeftBottom
CenterTop
CenterCenter
CenterBottom
RightTop
RightCenter
RightBottom
Defaults to LeftBottom if not provided.
Width Y The full width of the Text string once
rendered
Height Y The full height of the Text string once
rendered
TextAngle This is the angle that the base line of the
text string makes with the positive X axis
measured anticlockwise in degrees.
SlantAngle This is the angle, in degrees, of slant of the
text characters measured clockwise from
the positive Y axis. E.g. for the character I it
is the angle that the vertical stroke makes
with the positive Y axis.
ItemID If provided then the text string is to be
constructed from the attributes of another
element. The ID may be provided as the
ID of the element, the PersistentID/
@Identifier or the Tag of the element. See
Tag Referencing.

© 2007 AVEVA Solutions Ltd 6:74 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attribute Name Required Description

Set If the text is to be obtained from a child of a
GenericAttributes element then the set
name for the GenericAttributes element
may be provided to avoid ambiguity.
DependantAttribute The template for the textual contents if
obtaining the text from referenced
attributes.
The value of the DependantAttribute can
contain a single attribute or a list of
Attributes and explicit text. IF a single
attribute is referenced it may appear just as
the attribute name. Where multiple
attributes or explicit text is used the
attribute names are contained in square
brackets. E.g “[Tagprefix]-
[Tagnumber][Tagsuffix]”.
The search order will be the Attributes of
the PlantItem, ItemAttributes then
GenericAttributes of the Text followed by
the GenericAttributes of the parent or the
object explicitly identified by the ItemID.
The first occurrence of the named Attribute
will be used, there is no mechanism for
handling multiple attributes of the same
name.

© 2007 AVEVA Solutions Ltd 6:75 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Text String="4&quot;-B-902-A3B" Font="romans"
Justification="CenterCenter" Width="19.2"
Height="2.5" TextAngle="90" SlantAngle="0">
<Presentation LineType="Solid" LineWeight="1"
Color="160" R="0" G="0.4" B="1" />
<Extent>
<Min X="331.98850197" Y="154.37335742" Z="0" />
<Max X="334.48850197" Y="182.19944438" Z="0" />
</Extent>
<Position>
<Location X="333.238501971" Y="154.373357424" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
</Text>
<Text Font="Arial" Justification="LeftBottom" Width="17.2678"
Height="2.032" TextAngle="90"
DependantAttribute="[FluidSystem][OperFluidCode]">
<Presentation Layer="HiddenObjects" LineType="0" LineWeight="0"
Color="Black" R="0" G="0" B="0"/>
<Extent>
<Min X="262.83575736" Y="344.08495775" Z="0"/>
<Max X="264.86775736" Y="369.5594541" Z="0"/>
</Extent>
<Position>
<Location X="264.867757356" Y="344.08495775" Z="0"/>
<Axis X="0" Y="0" Z="1"/>
<Reference X="1" Y="0" Z="0"/>
</Position>
</Text>

6.4.92 Transaction
A record of a change to an item
Child elements:

Element Name Cardinality Description

Remark 0..* A comment describing the change.
GenericAttributes 0..* Any application specific attributes

© 2007 AVEVA Solutions Ltd 6:76 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

Type N One of the following;
to approve
to check
to copy
to create
to modify
to request
to release
Date N A date type (YYYY-MM-DD)
Time N A time type (HH:MM:SS) (See http://www/
w3.org for full details including time zones)
CompanyName N A free form string (see Character
encoding)
Person N A free form string (see Character
encoding)

Example:
<Transaction Type="to modify" Date="2007-06-10"
Time="10:30:32" CompanyName="My company" Person="Me">
<Remark>Amended Nozzle parameters for new
specification</Remark>
<Remark>WP2134</Remark>
</Transaction>

6.4.93 TrimmedCurve
An arc based on a circle or ellipse definition
Child elements:

Element Name Cardinality Description

Circle 0..1 Only present if Ellipse isn’t present. The
base Circle used to define the arc.
Ellipse 0..1 Only present if Circle isn’t present. The
base ellipse used to define the arc.
GenericAttributes 0..* Any application specific attributes

© 2007 AVEVA Solutions Ltd 6:77 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attributes:

Attribute Name Required Description

StartAngle Y The rotation around the circle/ellipse to
start the arc from. 0 = up.
The direction of the rotation is governed by
the Z axis specifier on the geometry.
Angle specified in degrees (0-360).
EndAngle Y The rotation around the circle/ellipse to end
the arc at. 0 = up.
The direction of the rotation is governed by
the Z axis specifier on the geometry.
Angle specified in degrees (0-360).

Example:
<TrimmedCurve StartAngle="0" EndAngle="56.251">
<Circle Radius="3.175">
<Presentation LineType="Solid" LineWeight="1"
R="0.25" G="0.82" B="0.15" />
<Extent>
<Min X="690.58888896" Y="480.00947926" Z="0" />
<Max X="692" Y="482.64942637" Z="0" />
</Extent>
<Position>
<Location X="688.825" Y="480.009479262" Z="0" />
<Axis X="0" Y="0" Z="1" />
<Reference X="1" Y="0" Z="0" />
</Position>
</Circle>
</TrimmedCurve>

6.4.94 UnitsOfMeasure
This element specifies the default units of measure for the file for each type of measured
value.
Child Elements:
None
Attributes:

Attribute Name Required Description

Distance N See Units for permitted distance values.
Default value is ‘Millimetre’.
Angle N See Units for permitted angle values.
Default value is ‘Degree’.
Temperature N See Units for permitted temperature
values. Default value is ‘DegreeCelsius’.

© 2007 AVEVA Solutions Ltd 6:78 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Attribute Name Required Description

Pressure N See Units for permitted pressure values.
Default value is ‘Bar’.
Weight N See Units for permitted weight values.
Default value is ‘Kilogram’.

Example:
<UnitsOfMeasure Distance="Inch" />

6.4.95 WallThickness
The thickness of the element construction.
Child elements:
None
Attributes:

Attribute Name Required Description

Value N The thickness value. Nb this is a string
type and so could be represented in many
ways.
Units N The units of measure (See Units for
permitted values). If not present then this
defaults to the units specified by
PlantInformation/UnitsOfMeasure.

Example:
<WallThickness Value="4" Units="mm"/>

6.4.96 Weight
The weight of the item.
Child elements:
None
Attributes:

Attribute Name Required Description

Value N The weight value.
Units N The units of measure (See Units for
permitted values). If not present then this
defaults to the units specified by
PlantInformation/UnitsOfMeasure.

© 2007 AVEVA Solutions Ltd 6:79 Issue 1.0

 PID Designer User Guide
Appendix: The ISO15926 (Version 3.2.0) Schema Specification

Example:
<Weight Value="6" Units="oz"/>

6.4.97 WeightsData
Child elements:

Element Name Cardinality Description

ControlPointWeight 0..*

Attributes:
None
Example:
<WeightsData>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
<ControlPointWeight>1</ControlPointWeight>
</WeightsData>

© 2007 AVEVA Solutions Ltd 6:80 Issue 1.0