DEP SPECIFICATION

INSTRUMENTATION SYMBOLS AND IDENTIFICATION ON

PROCESS ENGINEERING FLOW SCHEMES

DEP 32.10.03.10-Gen.

February 2011

DESIGN AND ENGINEERING PRACTICE

DEM1

© 2011 Shell Group of companies

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, published or transmitted, in any form or by any means, without the prior
written permission of the copyright owner or Shell Global Solutions International BV.
 DEP 32.10.03.10-Gen.
February 2011
Page 2

PREFACE

DEP (Design and Engineering Practice) publications reflect the views, at the time of publication, of Shell Global
Solutions International B.V. (Shell GSI) and, in some cases, of other Shell Companies.
These views are based on the experience acquired during involvement with the design, construction, operation and
maintenance of processing units and facilities. Where deemed appropriate DEPs are based on, or reference
international, regional, national and industry standards.
The objective is to set the recommended standard for good design and engineering practice to be applied by Shell
companies in oil and gas production, oil refining, gas handling, gasification, chemical processing, or any other such
facility, and thereby to help achieve maximum technical and economic benefit from standardization.
The information set forth in these publications is provided to Shell companies for their consideration and decision to
implement. This is of particular importance where DEPs may not cover every requirement or diversity of condition at
each locality. The system of DEPs is expected to be sufficiently flexible to allow individual Operating Units to adapt the
information set forth in DEPs to their own environment and requirements.
When Contractors or Manufacturers/Suppliers use DEPs, they shall be solely responsible for such use, including the
quality of their work and the attainment of the required design and engineering standards. In particular, for those
requirements not specifically covered, the Principal will typically expect them to follow those design and engineering
practices that will achieve at least the same level of integrity as reflected in the DEPs. If in doubt, the Contractor or
Manufacturer/Supplier shall, without detracting from his own responsibility, consult the Principal.
The right to obtain and to use DEPs is restricted, and is granted by Shell GSI (and in some cases by other Shell
Companies) under a Service Agreement or a License Agreement. This right is granted primarily to Shell companies and
other companies receiving technical advice and services from Shell GSI or another Shell Company. Consequently, three
categories of users of DEPs can be distinguished:
1) Operating Units having a Service Agreement with Shell GSI or another Shell Company. The use of DEPs by
these Operating Units is subject in all respects to the terms and conditions of the relevant Service Agreement.
2) Other parties who are authorised to use DEPs subject to appropriate contractual arrangements (whether as part
of a Service Agreement or otherwise).
3) Contractors/subcontractors and Manufacturers/Suppliers under a contract with users referred to under 1) or 2)
which requires that tenders for projects, materials supplied or - generally - work performed on behalf of the said
users comply with the relevant standards.
Subject to any particular terms and conditions as may be set forth in specific agreements with users, Shell GSI
disclaims any liability of whatsoever nature for any damage (including injury or death) suffered by any company or
person whomsoever as a result of or in connection with the use, application or implementation of any DEP, combination
of DEPs or any part thereof, even if it is wholly or partly caused by negligence on the part of Shell GSI or other Shell
Company. The benefit of this disclaimer shall inure in all respects to Shell GSI and/or any Shell Company, or companies
affiliated to these companies, that may issue DEPs or advise or require the use of DEPs.
Without prejudice to any specific terms in respect of confidentiality under relevant contractual arrangements, DEPs shall
not, without the prior written consent of Shell GSI, be disclosed by users to any company or person whomsoever and
the DEPs shall be used exclusively for the purpose for which they have been provided to the user. They shall be
returned after use, including any copies which shall only be made by users with the express prior written consent of
Shell GSI. The copyright of DEPs vests in Shell Group of companies. Users shall arrange for DEPs to be held in safe
custody and Shell GSI may at any time require information satisfactory to them in order to ascertain how users
implement this requirement.
All administrative queries should be directed to the DEP Administrator in Shell GSI.
 DEP 32.10.03.10-Gen.
February 2011
Page 3

TABLE OF CONTENTS

1. INTRODUCTION ........................................................................................................4
1.1 SCOPE........................................................................................................................4
1.2 DISTRIBUTION, INTENDED USE AND REGULATORY CONSIDERATIONS .........4
1.3 DEFINITIONS .............................................................................................................4
1.4 CROSS-REFERENCES .............................................................................................5
1.5 SUMMARY OF MAIN CHANGES...............................................................................5
1.6 COMMENTS ON THIS DEP .......................................................................................6
2 SYMBOLS ..................................................................................................................7
3 SYMBOLS INDICATING FUNCTIONALITY OF LOOP BASED ON ISO3511 .........9
3.1 IDENTIFICATION .......................................................................................................9
4 SYMBOLS INDICATING FUNCTIONALITY OF COMPONENT DERIVED
FROM ISA S5.1 AND ISA S5.3................................................................................13
4.1 IDENTIFICATION .....................................................................................................13
5 TAG NUMBERING FOR DCS, ENGINEERING TOOLS AND MMS.......................17
5.1 TAG NUMBER CONVENTIONS...............................................................................17
5.2 ANALYSER TAG NUMBER......................................................................................17
5.3 DCS TAG NUMBER REDUCTION...........................................................................17
5.4 DCS TAG NUMBER SPLITTING AND MERGING...................................................18
5.5 TAG NUMBERING FOR ENGINEERING TOOLS ...................................................21
5.6 TAG NUMBERING FOR COMPUTER-BASED MAINTENANCE
MANAGEMENT SYSTEMS. .....................................................................................21
6 QUALIFICATION OF FUNCTIONS..........................................................................22
7 REFERENCES .........................................................................................................23

APPENDICES
APPENDIX A: EXAMPLE OF SYMBOLS INDICATING FUNCTIONALITY OF LOOP
BASED ON ISO3511 .......................................................................................24
APPENDIX B: EXAMPLES OF SYMBOLS INDICATING FUNCTIONALITY OF
COMPONENT DERIVED FROM ISA S5.1 AND ISA S5.3 .............................40
 DEP 32.10.03.10-Gen.
February 2011
Page 4

1. INTRODUCTION

1.1 SCOPE
This DEP, in conjunction with Standard Drawings S 37.000, specifies requirements and
gives requirements for:
• symbols for the graphical presentation of instrument functions used on Process
Engineering Flow Schemes (PEFS); and,
• identification codes of the above instrument functions on PEFS.
This DEP contains mandatory requirements to mitigate process safety risks in accordance
with Design Engineering Manual DEM 1 – Application of Technical Standards
This DEP is a revision of the DEP of the same number dated January 2010; see (1.5)
regarding the changes.

1.2 DISTRIBUTION, INTENDED USE AND REGULATORY CONSIDERATIONS

Unless otherwise authorised by Shell GSI, the distribution of this DEP is confined to Shell
companies and, where necessary, to Contractors and Manufacturers/Suppliers nominated
by them. Any authorised access to DEPs does not for that reason constitute an
authorization to any documents, data or information to which the DEPs may refer.
This DEP is intended for use in facilities related to oil and gas production, gas handling, oil
refining, chemical processing, gasification, distribution and supply/marketing. This DEP
may also be applied in other similar facilities.
When DEPs are applied, a Management of Change (MOC) process should be
implemented; this is of particular importance when existing facilities are to be modified.
If national and/or local regulations exist in which some of the requirements could be more
stringent than in this DEP, the Contractor shall determine by careful scrutiny which of the
requirements are the more stringent and which combination of requirements will be
acceptable with regards to the safety, environmental, economic and legal aspects. In all
cases the Contractor shall inform the Principal of any deviation from the requirements of
this DEP which is considered to be necessary in order to comply with national and/or local
regulations. The Principal may then negotiate with the Authorities concerned, the objective
being to obtain agreement to follow this DEP as closely as possible.

1.3 DEFINITIONS
1.3.1 General definitions
The Contractor is the party that carries out all or part of the design, engineering,
procurement, construction, commissioning or management of a project or operation of a
facility. The Principal may undertake all or part of the duties of the Contractor.
The Manufacturer/Supplier is the party that manufactures or supplies equipment and
services to perform the duties specified by the Contractor.
The Principal is the party that initiates the project and ultimately pays for it. The Principal
may also include an agent or consultant authorised to act for, and on behalf of, the
Principal.
The word shall indicates a requirement.
The capitalised term SHALL [PS] indicates a Process Safety requirement.
The word should indicates a recommendation.
1.3.2 Abbreviations
BPCS Basic Process Control Systems (e.g. DCS)
CMMS Computer Maintenance Management System
 DEP 32.10.03.10-Gen.
February 2011
Page 5

DCS Distributed control system (in this document this terminology covers all
types of BPCS)
EPC Engineering Procurement Contractor
ESD Emergency Shutdown
HMI Human machine interface
IPF Instrumented protective function
IPS Instrumented protective system
MFD Mechanical Flow Diagram, similar to a PEFS
MMS Maintenance Management System(s)
MW Molecular weight
PEFS Process engineering flow scheme(s)
P&IDs Piping & Instrument Diagrams
PFS Process flow scheme(s)
PSFS Process safeguarding flow scheme(s)
SIL Safety Integrity Level, see DEP 32.80.10.10-Gen.
TSO Tight shut off to Class V or Class VI, in accordance with IEC 60534-4
UFS Utility Flow Scheme(s)

1.4 CROSS-REFERENCES
Where cross-references to other parts of this DEP are made, the referenced section
number is shown in brackets. Other documents referenced by this DEP are listed in (7).

1.5 SUMMARY OF MAIN CHANGES

This DEP is a revision of the DEP of the same number dated January 2010. The following
are the main, non-editorial changes.

Old New section Change

section
1.1 Updated
1.2 Updated
1.3.1 Updated
1.3.2 Updated
1.4 Updated
1.5 Added
1.6 Updated
1.7 Deleted
2.0 Updated to cover both ISO and ISA standards
3.0 Whole section changed for ISO3511
4.0 Whole section changed for ISA S5.1 and S5.3
5.0 Was section 3.6, moved and updated
6.0 Was section 4, moved and updated
7.0 Was section 5, moved and updated
 DEP 32.10.03.10-Gen.
February 2011
Page 6

Appendix A Was appendix 1, and updated

Appendix B New Appendix for ISA standards

1.6 COMMENTS ON THIS DEP

Comments on this DEP may be sent to the Administrator at standards@shell.com, using
the DEP Feedback Form. The DEP Feedback Form can be found on the main page of
“DEPs on the Web”, available through the Global Technical Standards web portal
http://sww.shell.com/standards and on the main page of the DEPs DVD-ROM.
 DEP 32.10.03.10-Gen.
February 2011
Page 7

2 SYMBOLS

For process plants there are two options applicable for instrument symbols used on PEFS,
namely:
• Option 1; Indicating functionality of the loop based on ISO 3511
- In this case sections 3, 5 and 6 apply.
• Option 2; Indicating functionality of components derived from ISA S5.1 and
ISA S5.3
- In this case sections 4, 5 and 6 apply
In conjunction with option 2, symbols and identification for protection devices identified in
API-RP-14C shall be used for all US based offshore facilities.
In conjunction with option 2, symbols and identification for protection devices identified in
ISO-10418 shall be used for all non US based offshore facilities.
There are other symbol schemes that may be used where authorized and defined by the
Principal, such as in power station applications.
For projects on existing sites the existing symbol schemes may be used.
When an alternate symbols scheme is to be used, it shall address all aspects of symbols
described in this document.
For most IPF and control functions, it is not possible to cover all functionality in sufficient
detail on PEFS. In such cases, further details shall be provided on separate documents,
such as narratives, block diagrams, functional logic diagrams, flow charts or a combination
of these documents.
On PEFS, the optional # sign is reserved to draw attention to the fact that further detailing
of functionality is available on other documents. Either the # sign or the full drawing number
shall be referenced (e.g. ‘refer to document R-123 456’).
A command to increase the output shall produce an increase on the process, such as
increase in capacity of control valve, a larger opening of louvres, increased motor speeds,
increased cooling capacity of variable-pitch fans etc. Where this is not the case (e.g. for
fail-open control valves) the signal shall be reversed upon exiting the DCS, and the reversal
function is shown on PEFS.
The following information shall not be shown on PEFS but shall be shown in other relevant
documents.
• Maintenance override switches and related status lamps, lamp test push buttons.
• Signals between the IPS and DCS for the purpose of synchronisation and controller
mode/output switching and ramping.
• Facilities for testing IPF initiators and IPF final elements, unless additional valves
(bypass and isolation valves) and hardwired instruments are required.
• Signals that provide information on failure of measuring instruments and instrument
systems, such as crippled mode alarms, system alarms and communication
alarms.
• Signals for initialisation, external feedback, etc.
• Signals for remote calibration (e.g. analysers).
• Serial communications between the DCS and IPS. This is an overview drawing or
serial communication drawing shall be provided to show all the signals that flow
between the two systems with tags specified on both sides of this communications
link.
The information flow direction shall be shown by arrows on signal line symbols.
 DEP 32.10.03.10-Gen.
February 2011
Page 8

When a loop is split across multiple PEFS drawing sheets cross-referencing between the
sheets shall be used. Service descriptions are optional and may be added for convenience.
 DEP 32.10.03.10-Gen.
February 2011
Page 9

3 SYMBOLS INDICATING FUNCTIONALITY OF LOOP BASED ON ISO3511

3.1 IDENTIFICATION
3.1.1 General
This Section covers option 1 (as per Section 2) for the identification of instrument functions
on PEFS.
The instrument symbols used on PEFS shall indicate the functionality of the loop. For DCS
and general instrumentation the symbols shall indicate which process condition or property
is being measured and controlled and what information is displayed. For safety related
function (e.g. IPFs) the symbols shall indicate which process condition or property is being
measured and what information is displayed.
NOTE: The same applies to PFS, PSFS and P&IDs. Note presentation of instrument functions on PFS and
PSFS will be less extensive.

All components and functions of the loop shall carry the same tag number. The numbering
shall be unique at loop level.
To clarify the functionality of the loop on PEFS the components shall be presented with
unique identifications, with the “process unit” and “serial number” left unchanged (e.g. in
loop 110FICA-101, a transmitter may be shown as 110FT-101, a local receiving indicator
as 110FI-101 and the two valves as 110FCV-101A and 110FCV-101B).
An instrument function is identified by its symbol (see Section 2 and Standard Drawing
S 37.000) and its tag number (see below).
3.1.2 Tag numbering for instrument functions on PEFS
3.1.2.1 General
Each instrument shall have a tag number of the format:
abc-yz
in which:

'a' is a three digit number used to identify the process unit.

'b' is a measured variable code: one capital letter code identifies the
process condition, property measured or initiating variable. Where
required, an additional modifier letter is added.
‘c’ is a function code: one or more capital letter codes identify the function
of the instrument or loop.
- is a separation dash, used for clarity
‘y’ is a three digit serial number (i.e. from 001 through 999)
‘z’ is an optional suffix which may be used to make a loop component
uniquely identifiable; only to be used if required.

3.1.2.2 Process unit identification 'A'

This is first two or three digits of the process unit number, and shall be used to reflect the
process unit identification in the instrument tag number.
For all new process units the three digit method shall be used. The two digit method may
be used when interfacing with existing plant; to provide uniformity.
 DEP 32.10.03.10-Gen.
February 2011
Page 10

Table-1: Examples of the relation between process unit and process unit
identification ‘a’

Identification ‘a’
Process unit
Two-digit method Three-digit method

0100 01 010

1100 11 110

1150 11 115
(see note below) (see note below)

7400 74 740

7420 74 742
(see note below) (see note below)

NOTE: In the two-digit method, no tag number distinction is made between instruments in the main unit
(e.g. 1100) and those in sub-units (e.g. 1150). If such a distinction is required, the three-digit method
shall be applied.

3.1.2.3 Measured variable code 'B'

This code shall indicate the process condition, property measured or initiating variable in
accordance with Table 5 of Standard Drawing S 37.000-005. Note a modifier may be
required to fully define the measured variable.
3.1.2.4 Function code 'C'
This code shall indicate the loop function in accordance with Table 5 of Standard Drawing
S 37.000-005 for option 1. Where two or more letters are required to capture the full
functionality, they shall be placed in the sequence ITBRQCSZA: ‘IBRQ’ for displays, ‘T’ for
transmitting, ‘CSZ’ for control/switch functions and ‘A’ for alarm.
For computing functions that cannot be manipulated by the operator, the letter ‘Y’ shall be
used (e.g. FY, PY, LY, PDY, XY, UY). For computing functions that can be manipulated by
the operator, the letter combination ‘HY’ shall be used.
For safety functions, the second letter in the function code SHALL [PS] be 'Z'.
3.1.2.5 Serial number 'Y'
Serial numbers shall be unique in each group of instruments having the same combination
of process unit identification (‘a’) and measured variable code (‘b’). Serial numbers shall
start at 001. Future expansions may be accommodated through allocation of unused
numbers.
Example: Flow instruments in unit 1100 are tagged 110FICA-001, 110FG-002, 110FP-003,
110FIZA-005. In this example, 110F-004 is intentionally left unused to allow for unforeseen
future expansions.
The practice of allocating separate number series for quality test points (QPs), restriction
orifices/flow test points (RO/FPs), flow glasses (FGs), pressure gauges/test points
(PGs/PPs) and temperature gauges/elements/test points (TGs/TEs/TPs) shall not be
applied for new installations. For modifications to existing sites the practice may however
still be applied for a specific project for the purpose of maintaining consistency with existing
installations.
Where a process unit contains identical process trains or identical pieces of equipment, the
assignment of serial number ‘y’ shall be selected to provide a recognisable numbering
 DEP 32.10.03.10-Gen.
February 2011
Page 11

relationship. For example: Process unit 1100 consists of two identical compressor sets, and
a future 3rd compressor is projected. Blocks of instrument serial numbers may be assigned
as follows: 001-099 for the common upstream and downstream process, 100-199 for
compressor one, 200 and 299 for compressor two, 300-399 reserved for compressor three.
The pressure controllers for compressors 1, 2 and 3 tagged as 110PICA-101/201/301
respectively, with the delineating being on the first digit of the serial number.
3.1.2.6 Optional suffix ‘Z’
When a loop consists of more than one similar component, a suffix letter may be used on
PEFS to make the identification of a component unique for reference purposes.
Examples:
• If two (redundant) transmitters are installed in loop 110PIC-056 for maintenance
purposes and a manual selector is provided to select one of them, the transmitters
may be shown on the PEFS as 110PT-056A and 110PT-056B.
• If loop 742FIC-001 is provided with a high and low range transmitter, the
transmitters may be shown on the PEFS as 742FT-001A for the low range
transmitter and 742FT-001B for the high range transmitter.
For multiple transmitters 'A' shall be assigned for the low range transmitter, with 'B' for the
mid range and 'C' for the high range. As the range increases the suffix letter increases.
The suffix ‘Z’ applies only to tag numbers used on PEFS. The tag number structures for
DCS, Engineering Tools and MMS require unique tagging at component/function level, see
(0).
3.1.3 Tag numbering for final elements on pefs
A final element shall be shown on the PEFS with the same tag number as the controller,
with the exception of the function code (‘c’) that shall be “CV”, e.g. if 110FICA-001 is the tag
number of a controller, the control valve is tagged 110FCV-001.
For the tag numbering of final elements associated with (binary) logic functions, see (0).
If a control loop consists of more than one final element, letters A/B/C etc. shall be used as
tag number suffix ‘z’ to make the numbering of the final elements unique.
Examples:
• If loop 110PIC-101 is provided with two valves in a split-range arrangement, the
valves shall be shown on the PEFS as 110PCV-101A and 110PCV-101B.
• If loop 742TIC-005 throttles the position of three louvres, the louvres shall be
tagged 742TCV-005A, 742TCV-005B and 742TCV-005C.
3.1.4 Tag numbering for (binary) logic functions on pefs
Binary logic functions shall be identified by either KS or UZ depending on their functionality:
aKS y for binary logic functions that are safety functions, e.g. sequential control
functions, switching functions, automatic start up functions. These functions
are not SIL assessed.
aUZ y for binary logic functions that are safety functions. These functions are Safety
Integrity Level (SIL) assessed and documented in Cause and Effect diagrams.
The serial number ‘y’ of the tag number for the binary logic function shall end with zero, e.g.
110KS-100, 110KS-110, 110KS-120, 742UZ-030, 742UZ-110, 742UZ-230.
The last digit shall be used for identification of the outputs from the binary logic functions,
and the solenoid valves/final elements driven by that logic. Final elements shall be tagged
KSV and UZV respectively.
Examples:
• Logic function 110KS-110 controls on-off valves 110KSV-111, 110KSV-112, and
110KSV-113.
 DEP 32.10.03.10-Gen.
February 2011
Page 12

• 110UZ-180 controls the position of valve 110FCV-001 via solenoid operated valve
110UZV-181 and controls on-off valves 110UZV-182 and 110UZV-183 via solenoid
operated valves with the same tag number.
3.1.5 Tag numbering for advanced control functions on pefs
Functions for advanced control shall be identified as:
aUC-y
Identification of outputs and associated final elements is the same as for binary logic
functions, see (0).
 DEP 32.10.03.10-Gen.
February 2011
Page 13

4 SYMBOLS INDICATING FUNCTIONALITY OF COMPONENT DERIVED FROM ISA S5.1

AND ISA S5.3

4.1 IDENTIFICATION
4.1.1 General
The instrument symbols used on PEFS shall indicate the functionality of the component.
For DCS and general instrumentation the symbols shall indicate which process condition or
property is being measured and controlled and what information is displayed. For safety
related function (e.g. IPFs) the symbols shall indicate which process condition or property is
being measured and what information is displayed.
NOTE: The same applies to PFS and PSFS but the presentation of instrument functions on these documents
will be less extensive.

Frequently used standardised symbols are shown on Standard Drawing S 37.000. Where
a symbol is not available on Standard Drawing S 37.000, ISA 5.1 shall be used as a guide
with the suggested symbol presented to the Principal for approval.
Typical examples of symbols used for instrument functions are shown in Appendix B of this
DEP. The use of this DEP and Standard Drawing S 37.000 allows most of the current
process control functions to be indicated on PEFS, including those for process computers,
shared display/control systems and interfaces.
The symbols used have been derived from ISA S5.1 and ISA S5.3.
To clarify the functionality of the control loop, it is required to show loop components on
PEFS. In such cases, the components may be presented on PEFS with unique
identifications, providing that the process unit and serial number are left unchanged (e.g. in
loop 110FIC-101, a transmitter may be shown as 110FT-101, a local receiving indicator as
110FI-101 and the two valves as 110FCV-101A and 110FCV-101B).
An instrument function is identified by its symbol (see Section 2 and Standard Drawing
S 37.000) and its tag number (see below).
4.1.2 Tag numbering for instrument functions on PEFS
4.1.2.1 General
Each instrument shall have a tag number of the format:
abc-yz
in which:

'a' is a three digit number used to identify the process unit.

'b' is a measured variable code: one capital letter code identifies the
process condition, property measured or initiating variable. Where
required, an additional modifier letter is added.
‘c’ is a function code: one or more capital letter codes identify the function
of the instrument or loop.
- is a separation dash, used for clarity
‘y’ is a three digit serial number (i.e. from 001 through 999)
‘z’ is an optional suffix which may be used to make a loop component
uniquely identifiable; only to be used if required.

4.1.2.2 Process unit identification 'A'

This is first two or three digits of the process unit number, and shall be used to reflect the
process unit identification in the instrument tag number.
For all new process units the three digit method shall be used. The two digit method may
be used when interfacing with existing plant; to provide uniformity.
 DEP 32.10.03.10-Gen.
February 2011
Page 14

For sites that are considered as a single unit this identification number may be omitted. E.g.
an offshore platform could be considered a single unit. The platform name is added to the
tag and consists of 3 characters for the platform name, e.g. MRS for Mars.
Table-2: Examples of the relation between process unit and process unit
identification ‘a’

Identification ‘a’
Process unit
Two-digit method Three-digit method

0100 01 010

1100 11 110

1150 11 115
(see note below) (see note below)

7400 74 740

7420 74 742
(see note below) (see note below)

NOTE: In the two-digit method, no tag number distinction is made between instruments in the main unit
(e.g. 1100) and those in sub-units (e.g. 1150). If such a distinction is required, the three-digit method
shall be applied.

4.1.2.3 Measured variable code 'B'

This code shall indicate the process condition, property measured or initiating variable in
accordance with Table 6 of Standard Drawing S 37.000-010. Note a modifier may be
required to fully define the measured variable. Abbreviation examples and exceptions from
ISA 5.1 are provided in Table 7 of Standard Drawing S 37.000-010.
4.1.2.4 Function code 'C'
This code shall indicate the loop function in accordance with Table 6 of Standard Drawing
S 37.000-010. Where two or more letters are required to capture the full functionality, they
shall be placed in the sequence Measured or Initiating Variable, Variable Modifier, followed
by either Readout/Passive Function or Output/Active Function, then followed by the
Function Modifier. The use of suffixes will uniquely identify multiple inputs/outputs if they
are part of the same loop.
For computing functions that cannot be manipulated by the operator, the letter ‘Y’ shall be
used (e.g. FY, PY, LY, PDY, XY, and UY). For computing functions that can be
manipulated by the operator, the letter combination ‘HY’ shall be used (regardless of the
process function).
For safety functions, the second letter in the function code SHALL [PS] be 'Z'. Where
API-RP-14C is mandatory, the tagging convention of API-RP-14C shall be used and
second letter SHALL [PS] be “S”.
Transmitters shall not have an 'I' in the field device tag number to reflect a local indicator as
part of the transmitter. Where a local indicator is provided out in the field and is not part of a
transmitter, then the local indicator shall have a designator letter “I” (e.g. FI).
4.1.2.5 Serial number 'Y'
Serial numbers shall be unique in each group of instruments having the same combination
of process unit identification (‘a’) and measured variable code (‘b’). Serial numbers shall
start at 001. Future expansions may be accommodated through allocation of unused
numbers.
 DEP 32.10.03.10-Gen.
February 2011
Page 15

Example: Flow instruments in unit 1100 are tagged 110FIC-001, 110FG-002, 110FP-003,
110FI-005. In this example, 110F-004 is intentionally left unused to allow for unforeseen
future expansions.
The practice of allocating separate number series for quality test points (QPs), flow test
points (FPs), pressure test points (PPs) and temperature test points (TPs) shall not be
used. This practice may however for existing facilities still be desired for the purpose of
maintaining consistency with existing installations, or in cases where the available number
series cannot accommodate all instrument functions.
Where a process unit contains identical process trains or identical pieces of equipment, the
assignment of serial number ‘y’ shall be selected to provide a logical and recognisable
numbering relation between trains. Example: Process unit 1100 consists of two identical
compressor sets and a future 3rd compressor is projected. Blocks of instrument serial
numbers may be assigned as follows: 001-099 for the common upstream and downstream
process, 100-199 for compressor one, 200 and 299 for compressor two, 300-399 reserved
for compressor three. The pressure controllers for compressors 1, 2 and 3 tagged as
110PIC-101/201/301 respectively, with the delineating being on the first digit of the serial
number.
4.1.2.6 Optional suffix ‘Z’
When a loop consists of more than one similar component, a suffix letter may be used on
PEFS to make the identification of a component unique for reference purposes.
Examples:
• If two (redundant) transmitters are installed in loop 110PIC-056 for maintenance
purposes and a manual selector is provided to select one of them, the transmitters
may be shown on the PEFS as 110PT-056A and 110PT-056B.
• If loop 742FIC-001 is provided with a high and low range transmitter, the
transmitters shall be shown on the PEFS as 742FT-001A for the low range
transmitter and 742FT-001B for the high range transmitter.
For multiple transmitters 'A' shall be assigned for the low range transmitter, with 'B' for the
mid range and 'C' for the high range. As the range increases the suffix letter increases.
The suffix ‘Z’ applies only to tag numbers used on PEFS. The tag number structures for
DCS, Engineering Tools and MMS require unique tagging at component/function level,
see (0).
4.1.3 Tag numbering for final elements (e.g. valves) on PEFS
A control valve shall be shown on the PEFS with the same tag number as the controller,
with the exception of the function code (‘c’) that shall be “CV” or "V", e.g. if 110FIC-001 is
the tag number of a controller, the control valve is tagged 110FCV-001 or 110FV-001.
For the tag numbering of final elements associated with (binary) logic functions, see (0).
If a control loop consists of more than one final element, letters A/B/C etc. shall be used as
tag number suffix ‘z’ to make the numbering of the final elements unique.
Examples:
• If loop 110PIC-101 is provided with two valves in a split-range arrangement, the
valves shall be shown on the PEFS as 110PCV-101A and 110PCV-101B.
• If loop 742TIC-005 throttles the position of three louvres, the louvres shall be
tagged 742TCV-005A, 742TCV-005B and 742TCV-005C.
The DEP appendices use the following convention for control valve air failure mode: an
arrow pointing toward the line indicates that the valve fails closed, and an arrow pointing
away from the line indicates that the valve fails open. The US uses a convention in which
“FC” = fail closed, “FO” = fail open, and “FL” = fail last. The convention used in the US will
be allowed.
 DEP 32.10.03.10-Gen.
February 2011
Page 16

4.1.4 Tag numbering for (binary) logic functions on PEFS

Binary logic functions shall be identified by either KS or UZ depending on their functionality:
aKS y for binary logic functions that are safety functions, e.g. sequential control
functions, switching functions, automatic start up functions. These functions
are not SIL assessed.
aUZ y for binary logic functions that are safety functions. These functions are Safety
Integrity Level (SIL) assessed and documented in Cause and Effect diagrams.
The serial number ‘y’ of the tag number for the binary logic function shall end with zero, e.g.
110KS-100, 110KS-110, 110KS-120, 742UZ-030, 742UZ-110, 742UZ-230.
The last digit shall be used for identification of the outputs from the binary logic functions,
and the solenoid valves/final elements driven by that logic. Final elements shall be tagged
KSV and UZV respectively.
Examples:
• Logic function 110KS-110 controls on-off valves 110KSV-111, 110KSV-112, and
110KSV-113.
• 110UZ-180 controls the position of valve 110FCV-001 via solenoid operated valve
110UZV-181 and controls on-off valves 110UZV-182 and 110UZV-183 via solenoid
operated valves with the same tag number.
4.1.5 Tag numbering for advanced control functions on PEFS
Functions for advanced control shall be identified as:
aUC-y
Identification of outputs and associated final elements is the same as for binary logic
functions, see (0).
 DEP 32.10.03.10-Gen.
February 2011
Page 17

5 TAG NUMBERING FOR DCS, ENGINEERING TOOLS AND MMS

5.1 TAG NUMBER CONVENTIONS

For DCS, Engineering Tools and MMS unique numbering at component/function level may
be applied.

5.2 ANALYSER TAG NUMBER

Tag numbers associated with analysers may be tagged as follows:

TAG DESCRIPTION
aAW-y Analyzer Sample Probe
aAE-y Field Element
aAT-y Analyzer Transmitter
aAI-y Analyzer Indicator
aAC-y Analyzer Controller
aAS-y Analyzer Come Read (Used on Cyclic analyzers only)
aAA-y Analyzer Health Status (Alarms)
aAX-y Auxiliary Devices Associated with an analyzer
aAY-y Analyser calculated points in the DCS
Where analysers are multi-stream, the following is an example of convention that may be
used:

TAG DESCRIPTION
aAI-ypq Analyzer Indicator
in which:
'p' Is the Stream number
'q' Is the component suffix
The letters 'I' and 'O' shall not be used for component suffixes.

5.3 DCS TAG NUMBER REDUCTION

The DCS may pose restrictions on the number of characters for a tag name. Apart from this
system limitation there is a strong need for a uniform and clear operator access to tag
numbers. If, for example, access to DCS function 110PIC-004 is required, this shall not be
hampered by the omission of an 'A' for alarming or an ‘I’ for indication in the tag name. The
following tag number reduction rules may be applied:
• there needs to be available room for a suffix in the DCS naming convention;
• the process unit identification ‘a’ and the measured variable code ‘b’ (including its
modifier) shall remain unchanged. The serial number ‘y’ shall remain unchanged
also.
• if there is a requirement to shorten tag numbers on the DCS, then reduction may
be achieved by deleting characters from the function code ‘c’: the dash (-),
A(alarming), I(indicating) and B(status display) characters of the tag name may be
omitted in this order. The C(control), Z and S (switching) shall not be omitted. For
example, PDAHH (pressure differential alarm high-high) could be shortened to
PDHH.
• the tagging rules need to be consistent between the DCS and the IPS (and
integration of third party systems).
 DEP 32.10.03.10-Gen.
February 2011
Page 18

Examples of tag number reduction:

Option 1: Based on ISO3511

Full tag name, as shown on DCS tag name

PEFS
110PI-001 110PI001
110FIA-005 110FI005
110PICA-104 110PC104
110PDIC-202 110PDC202
110PDICA-305 110PDC305
110GBS-401 110GS401
110LSA-501 110LS501
110LISA-502 110LS502
110LZA-505 110LZ505

Option 2: Based on ISA S5.1 AND ISA S5.3

Full field device tag name, as DCS tag name

shown on PEFS
110PT-001 110PI001
110FT-005 110FI005
110PT-104 110PIC104
110PT-202 110PDIC202
110PTH-305 110PDIC305
110ZSC-401 110ZAC401
110ZSO-401 110ZAO401
110LSLL-501 110LALL501
110LT-502 110LI502
110LZT-505 110LZI505 in the IPS

5.4 DCS TAG NUMBER SPLITTING AND MERGING

When a single PEFS ‘balloon’ has multiple inputs or outputs in the DCS, each input and
output shall have a unique tag name in the DCS. Conversely, multiple PEFS ‘balloons’ are
sometimes combined into one DCS function, carrying only one DCS tag name.
Examples of this tag name splitting and merging are given below for a situation where tag
number reduction (see 0) is not a requirement.
 DEP 32.10.03.10-Gen.
February 2011
Page 19

Option 1: Based on ISO3511

Full tag name, as shown on PEFS DCS tag name

Split into:
110LIZA-001.
110LI001 (indication),
110LZ001 (trip alarm).

110LIZA-001 (2oo3). Split, for example, into:

110LI001A (indication from 110LT-001A),
110LI001B (indication from 110LT-001B),
110LI001C (indication from 110LT-001C),

110LZ001 (2oo3 trip alarm),

110LA001A (alarm from 110LT-001A),
110LA001B (alarm from 110LT-001B),
110LA001C (alarm from 110LT-001C).

110PCV-101A and 110PCV-101B Name the output to the valves after the
(split range valves, see item 8.2 of calculation blocks:
Appendix A8).
110HY001 (to valve 110PCV-101A),
110PY101 (to valve 110PCV-101B).

110HS-023 (pump start/stop command) Merge into:

and 110GB-045 (pump running signal).
110HS-023 (combining the start/stop
command and running/stopped status in
one display).

110HS-024 (open/close command) and Merge into:

110GB-046 (valve open/closed
110HS-024 (combining the open/closed
position).
command and open/close status in one
display function).

110FY-004 (calculation block) and Merge into:

110HY-005 (Auto/manual station). 110HY-005 (Calculation function in the
DCS with Auto/manual switching).
 DEP 32.10.03.10-Gen.
February 2011
Page 20

Option 2: Based on ISA S5.1 AND ISA S5.3

Full field device tag name, as shown DCS tag name
on PEFS

Split into:
110LZI-001.
110LZI001 (DCS indication),
110LZ001 (trip alarm).

110LZI-001A 110LI001A (indication from 110LT-001A),

110LI001B (indication from 110LT-001B),
110LZI-001B
110LI001C (indication from 110LT-001C),
110LZI-001C
110LZ001 (2oo3 trip alarm),
110LAHH001A (alarm from 110LT-001A),
110LAHH001B (alarm from 110LT-001B),
110LAHH001C (alarm from 110LT-001C).

Note: Assuming that the level trip is a high-

high level. If it were a low-low level trip,
then the above would be 110LALL001A;
110LALL001B; and 110LALL001C.

110PCV-101A and 110PCV-101B Name the output to the valves after the
(split range valves, see item 8.2 of calculation blocks:
Appendix B8).
110HY001 (to valve 110PCV-101A),
110PY101 (to valve 110PCV-101B).

110HS-023 (pump start/stop command) 110HS023 (the start/stop command)

and 110YS-045 (pump running signal). 110YI045 (running/stopped status).

110HS-024 (open/close command) 110HS-024 (open/closed command)

110ZSO-046 (valve open position) 110ZAO (valve open status)
110ZSC-046 (valve closed position) 110ZAC (valve closed status).
110FY-004 (calculation block) 110FY-004 (calculation block)
110HY-005 (Auto/manual station) 110HY-005 (Auto/manual station)
 DEP 32.10.03.10-Gen.
February 2011
Page 21

5.5 TAG NUMBERING FOR ENGINEERING TOOLS

Engineering Tools require loop components and functional elements to be uniquely
identified. A loop, presented on the PEFS with one tag number, requires a split into records
per component/function, each with a unique tag number.
Example - A single balloon for 110FIC(A)-001 on a PEFS may result in the following
database records:
Loop component Tag Option 1 Tag Option 2
Orifice assembly 110FICA-101-FE 110FE-101
Transmitter 110FICA-101-TX 110FT-101
DCS input function 110FICA-101-AI 110FX-101A
DCS control and alarm function 110FICA-101-C 110FIC-101
DCS output function 110FICA-101-AO 110FX-101B
Control valve 110FICA-101-CV 110FCV-101

The tagging structure between the PEFS, the DCS/IPS, and engineering tools (such as
SmartPlant Instrumentation or another instrument index, flow calculations, alarm enforcer/
other alarm management tools, or valve sizing) shall align.

5.6 TAG NUMBERING FOR COMPUTER-BASED MAINTENANCE MANAGEMENT

SYSTEMS.
Maintenance Management Systems (MMS) also require specific tag numbering structures.
It is important to define the tagging structures for MMS at the same time as those for the
DCS and Engineering tools to allow data conversion from the DCS/Engineering tools to the
MMS at the end of the engineering phase of a project.
 DEP 32.10.03.10-Gen.
February 2011
Page 22

6 QUALIFICATION OF FUNCTIONS

Where it is necessary to indicate process conditions at which action is required, such as

high high, high, low, low low, the qualifying letters HH, H, L, LL, shall be shown next to the
balloon. See Appendices A and B for examples.
When it is necessary to clarify the function, the letters Z, A, B or S, or combinations thereof,
shall be put in brackets after the above-mentioned qualifying letters.
 DEP 32.10.03.10-Gen.
February 2011
Page 23

7 REFERENCES

In this DEP reference is made to the following publications:

NOTES: 1. Unless specifically designated by date, the latest edition of each publication shall be used, together
with any amendments/supplements/revisions thereto.
2. Most referenced external standards are available for Shell users on the SWW (Shell Wide Web) at
address http://sww.shell.com/standards.

STANDARD DRAWINGS
Mechanical symbols for use on flow schemes S 02.002
PEFS legend for instrument symbols and identification S 37.000

AMERICAN STANDARDS
Recommended Practice for Analysis, Design, Installation, and API RP-14C
Testing of Basic Surface Safety Systems for Offshore
Production Platforms
Instrumentation symbols and identification ISA S5.1
Graphic symbols for distributed control/shared display ISA S5.3
instrumentation, logic and computer symbols.
Issued by:
Instrument Society of America,
400 Stanwix Street, Pittsburgh,
Pennsylvania 15222, USA.

INTERNATIONAL STANDARDS
Process Measurement Control Functions And Instrumentation ISO 3511
- Symbolic Representation
Petroleum And Natural Gas Industries Offshore Production ISO 10418
Installations Basic Surface Process Safety Systems
Issued by:
International Organisation for Standardisation
1, Rue de Varembé
CH-1211 Geneva 20
Switzerland.

Copies can also be obtained from national standards organizations

 DEP 32.10.03.10-Gen.
February 2011
Page 24

APPENDIX A: EXAMPLE OF SYMBOLS INDICATING FUNCTIONALITY OF LOOP BASED

ON ISO3511

A1: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

ANALYSERS
 DEP 32.10.03.10-Gen.
February 2011
Page 25

A2: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS - FLOW

 DEP 32.10.03.10-Gen.
February 2011
Page 26

A3: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS - LEVEL

 DEP 32.10.03.10-Gen.
February 2011
Page 27

A4: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

PRESSURE
 DEP 32.10.03.10-Gen.
February 2011
Page 28

A5: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

TEMPERATURE
 DEP 32.10.03.10-Gen.
February 2011
Page 29

A6: EXAMPLES OF INSTRUMENT SYMBOLS FOR CALCULATIONS

 DEP 32.10.03.10-Gen.
February 2011
Page 30

A7: EXAMPLES OF INSTRUMENT SYMBOLS FOR SIGNAL SWITCHING AND SELECTION

 DEP 32.10.03.10-Gen.
February 2011
Page 31

A7: EXAMPLES OF INSTRUMENT SYMBOLS FOR SIGNAL SWITCHING AND SELECTION

(Continued)
 DEP 32.10.03.10-Gen.
February 2011
Page 32

A8: EXAMPLES OF INSTRUMENT SYMBOLS FOR SPECIAL CONTROL FUNCTIONS

 DEP 32.10.03.10-Gen.
February 2011
Page 33

A8: EXAMPLES OF INSTRUMENT SYMBOLS FOR SPECIAL CONTROL FUNCTIONS

(Continued)
 DEP 32.10.03.10-Gen.
February 2011
Page 34

A9: EXAMPLES OF INSTRUMENT SYMBOLS FOR COMBINED SPEED CONTROL AND IPF
 DEP 32.10.03.10-Gen.
February 2011
Page 35

A10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF

 DEP 32.10.03.10-Gen.
February 2011
Page 36

A10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF (Continued)

 DEP 32.10.03.10-Gen.
February 2011
Page 37

A10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF (Continued)

 DEP 32.10.03.10-Gen.
February 2011
Page 38

A11: EXAMPLES OF INSTRUMENT SYMBOLS FOR SEQUENCE CONTROL SYSTEM

 DEP 32.10.03.10-Gen.
February 2011
Page 39

A12: EXAMPLES OF INSTRUMENT SYMBOLS FOR ADVANCED CONTROL FUNCTIONS

 DEP 32.10.03.10-Gen.
February 2011
Page 40

APPENDIX B: EXAMPLES OF SYMBOLS INDICATING FUNCTIONALITY OF COMPONENT

DERIVED FROM ISA S5.1 AND ISA S5.3

B1: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

ANALYSERS
 DEP 32.10.03.10-Gen.
February 2011
Page 41

B2: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS - FLOW

 DEP 32.10.03.10-Gen.
February 2011
Page 42

B3: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS - LEVEL

 DEP 32.10.03.10-Gen.
February 2011
Page 43

B4: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

PRESSURE
 DEP 32.10.03.10-Gen.
February 2011
Page 44

B5: EXAMPLES OF INSTRUMENT SYMBOLS FOR MEASUREMENT FUNCTIONS -

TEMPERATURE
 DEP 32.10.03.10-Gen.
February 2011
Page 45

B6: EXAMPLES OF INSTRUMENT SYMBOLS FOR CALCULATIONS

 DEP 32.10.03.10-Gen.
February 2011
Page 46

B7: EXAMPLES OF INSTRUMENT SYMBOLS FOR SIGNAL SWITCHING AND SELECTION

 DEP 32.10.03.10-Gen.
February 2011
Page 47

B7: EXAMPLES OF INSTRUMENT SYMBOLS FOR SIGNAL SWITCHING AND SELECTION

(Continued)
 DEP 32.10.03.10-Gen.
February 2011
Page 48

B8: EXAMPLES OF INSTRUMENT SYMBOLS FOR SPECIAL CONTROL FUNCTIONS

 DEP 32.10.03.10-Gen.
February 2011
Page 49

B8: EXAMPLES OF INSTRUMENT SYMBOLS FOR SPECIAL CONTROL FUNCTIONS

(Continued)
 DEP 32.10.03.10-Gen.
February 2011
Page 50

B9: EXAMPLES OF INSTRUMENT SYMBOLS FOR COMBINED SPEED CONTROL AND IPF
 DEP 32.10.03.10-Gen.
February 2011
Page 51

B10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF

 DEP 32.10.03.10-Gen.
February 2011
Page 52

B10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF (Continued)

 DEP 32.10.03.10-Gen.
February 2011
Page 53

B10: EXAMPLES OF INSTRUMENT SYMBOLS FOR IPF (Continued)

For tags 115-ZZSC-212 and 115-ZZSO-212 in this example the position switches go into the IPS
(second letter is a “Z” to indicate safety function). If these were only connected to a BPCS, then ZSC
and ZSO is used.
.
 DEP 32.10.03.10-Gen.
February 2011
Page 54

B11: EXAMPLES OF INSTRUMENT SYMBOLS FOR SEQUENCE CONTROL SYSTEM

 DEP 32.10.03.10-Gen.
February 2011
Page 55

B12: EXAMPLES OF INSTRUMENT SYMBOLS FOR ADVANCED CONTROL FUNCTIONS