Professional Documents
Culture Documents
ERD-00-02
MAR-94
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 2
USER GUIDELINES
Engineering Reference documents (ERDs) contain information on PDO facilities and systems that are
either used repeatedly or that is retained for current or future reference.
ERDs shall be prepared and revised in accordance with ERD-00-10 'Content and Presentation of
Engineering Reference Documents'.
The specific objective of this document is to provide guidance on the rationale behind the Technical
Authority system used in PDO, to provide details of the Technical Authority level required to sign-off or
approve any of the documents used by PDO engineers during the lifecycle of the Company's facilities,
and to outline the procedure to be used when a deviation from Company Standards is required.
Not included in this ERD is the listing of authority levels held by individual engineers, as this listing
changes on a frequent basis as personnel are re-assigned. This listing will be issued separately at
appropriate intervals.
This ERD is intended for use by PDO and their nominated Consultants and Contractors.
It is the responsibility of the User of this Standard to ensure that he has the latest revision, by making
reference to ERD-00-01 'Index to PDO Facilities Standard and Procedures'.
Any User who identifies an inaccuracy or ambiguity is requested to notify the Functional Discipline
Head so that appropriate action can be taken. The User is requested to return the User Feedback
Page, situated at the end of the ERD, fully completed to indicate precisely the amendment(s)
recommended.
Listed below are details on any revision made to this ERD in the interim period between the issue of
the ERD (as currently recorded in ERD 00-01 (Wallchart)) and the next formal revision of the ERD.
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 3
TABLE OF CONTENTS
USER GUIDELINES.............................................................................................................2
1 SYSTEM DESCRIPTION...............................................................................................4
1.1 THE OBJECTIVE................................................................................................................... 4
1.2 THE SYSTEM........................................................................................................................ 4
1.3 INDIVIDUAL TECHNICAL AUTHORITIES............................................................................4
1.4 ALLOCATION OF AUTHORITY............................................................................................ 4
1.5 DELEGATION OF AUTHORITY............................................................................................ 5
1.6 UPDATING OF AUTHORITY LEVELS..................................................................................5
1.7 DEVIATIONS FROM COMPANY STANDARDS...................................................................5
1.8 SYSTEM CUSTODIAN.......................................................................................................... 5
2 LIST OF DISCIPLINE CODES AND T.A. LEVELS........................................................6
2.1 DISCIPLINE CODES............................................................................................................. 6
2.2 T.A. LEVELS.......................................................................................................................... 6
3 FACILITIES TECHNICAL DOCUMENT LISTING...........................................................7
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 4
1 SYSTEM DESCRIPTION
'to warrant the integrity of all PDO's facilities during the design, construction and operating phases of a
development, with individual engineers being clearly accountable'.
1.2 THE SYSTEM
The essence of the Technical Authorities System is to make maximum use of an individual's
competencies to make sound engineering judgements and decisions. An engineer is allocated a level
of technical authority through the Technical Authority (TA) System that enables him to take
responsibility for approving a range of engineering drawings/documents and also to deviate, where
appropriate, from Company standards. The required level of authority of the signatory is defined by
the TA system, but who (with the correct authority level) actually signs is determined by the engineer
in charge. The level of authority is discipline specific.
The system is suitable for use by all disciplines associated with facilities management (both surface
and subsurface), and covers all three discipline groups:
1) Hardware
2) Technical Advice
3) Work Co-ordination
1.3 INDIVIDUAL TECHNICAL AUTHORITIES
All engineers have a range of differing skills and experience profiles spread across the various
disciplines. In the Technical Authorities System, each individual has a 'base' discipline, that is the
discipline in which he is recognised as having his primary competency, and it will be in this discipline
that he will be allocated his primary technical authority. The consequence of this is that engineers who
are primarily responsible for managing projects will have predominantly 'Work Co-ordination'
authorities and the technical discipline based engineers will have largely 'Hardware' responsibilities.
There will also be engineers who have competencies in disciplines additional to their 'base' discipline,
and an individual can be allocated technical authority in additional disciplines, subject to the normal
approval process.
A typical example would be project engineers who, while working primarily in a project management
capacity and having 'Work Co-ordination' authorities, may well also have competencies in their
'original' technical discipline such as 'Pipelines' or 'Process'.
However, it is anticipated that the discipline competence of an engineer in this position will be
gradually eroded with time, and the Department Head, Senior Line Manager and in particular the
Corporate Functional Discipline Head (CFDH) need to be satisfied that the individual continues to be
suitably qualified. The status of engineers with any additional technical authorities will therefore be
reviewed each year by the relevant (CFDHs) as part of the annual review of technical authorities.
It will be noted that it is a feature of the Technical Authorities System that engineering decisions
and judgements should be made only by those individuals qualified to make them.
1.4 ALLOCATION OF AUTHORITY
The level of Technical Authority to be allocated to an engineer is determined by the individual's
competencies. The appropriate level of authority is proposed by the Department Head, supported by
the Corporate Functional Discipline Head, and endorsed by the Senior Line Manager (ADM, BDM,
AOM, BOM or TSD). In the event that the proposer and FDH fail to agree the appropriate level of
Technical Authority for an individual, the Senior Line Manager will rule.
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 5
A full listing of all drawings and documents used in typical projects has been developed for each
discipline, together with the TA level required to sign-off the document (listing attached). Not all of
these documents will be required in every project; the engineer will use those documents that he
needs for his purposes and the indicated TA levels will apply. All documents have only one Technical
Authority approval signatory.
1.5 DELEGATION OF AUTHORITY
When the Corporate Functional Discipline Head is to be absent from the Company for more than a
few days, he will delegate his level 1 authority to the next most senior discipline engineer for the
period of his absence. Notification will be given, as for the delegation of other authorities, through the
Weekly Notices.
1.6 UPDATING OF AUTHORITY LEVELS
A review of technical authority levels normally carried out annually on a company-wise basis following
the appraisal exercise, however ad-hoc updates and changes can be proposed at any time. The
Department Head forwards the T.A proposal, together with any supporting documentation, to the
CFDH. Supporting documentation should include CVs, relevant certificates and training records for
new and previously unregistered staff. After review, and if approved, the CFDH passes the proposal to
the Senior Line Manager for his endorsement. The form then goes to TTH/1 who registers the
individual in the database and issues him with his certificate of authority.
1.7 DEVIATIONS FROM COMPANY STANDARDS
The Technical Authorities system allows an engineer to deviate from Company Standards and
Procedures, where appropriate, using the variance procedure. If the engineer and the CFDH fail to
agree on the proposed variance, then the nominated Senior Line Manager (ADM, BDM, AOM, BOM,
TSD) in each Unit has the authority to make the final decision and over-rule the CFDH. Note this
procedure is only required in the context of variances from Standards or Procedures.
1.8 SYSTEM CUSTODIAN
BEZ/3 Information Co-ordinator is the System Custodian, responsible for the administration of the
system, database maintenance, and the issue of certificates.
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 6
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 7
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 8
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 10
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 11
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 12
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 13
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 14
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 15
Phase: 0=Gen., 1=Design, 2=Constr., 3=Handover, 4=Use, 5=Maint/Repair, 6=Change T.A =Technical Authority Level
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 16
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 17
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 18
▲ Revision 1/95
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 19
▲ Revision 1/95
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 20
From:
Any User who identifies an inaccuracy, error or ambiguity is requested to notify the custodian so that
appropriate action can be taken. The User is requested to return this page fully completed, indicating
precisely the amendment(s) recommended.
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
TECHNICAL AUTHORITIES SYSTEM ERD 00-02
March 1994
Page : 21
Name of proposed:
Company number:
Reference Indicator:
Discipline:
TA Level proposed:
Routing
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 22
NAME:
Company number:
Reference Indicator:
Discipli
ne :
Level of Technical
Authority :
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the
bottom of every page. You can find the latest issue date for this ERD on the wall-chart ERD-00-01. Check the
PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22
ERD 00-02 TECHNICAL AUTHORITIES SYSTEM
March 1994
Page 23
Is a variance to a No
Start Standard or End
Procedure
proposed ?
VARIANCE CONTROL
Applies to Standards and Procedures only
FDH = Functional Discipline Head
Yes
TA = Technical Authority
No
Yes Yes
FDH periodically reviews variances Variances to be reviewed by project team Variances to be reflected in Operations
and amends his standards during Design Reviews and Maintenance Manuals
accordingly
Do not use this copy of the ERD if the print-out date is before the latest issue date. The print-out date is on the bottom of every page. You can find the latest issue date for this ERD on the
wall-chart ERD-00-01. Check the PDO-Intranet (DCS page) for news about temporary amendments. Printout Date: 09/22/22