Practice 000.200.

0716
Date 03Nov2010
Page 1 of 3

GENERAL AUTHORITY ENGINEERING

DISCIPINE INTERFACE

PURPOSE

The purpose of this document is to establish in an early stage of a project, the

requirements of authorities in the design, engineering, procurement, fabrication and
construction phases of the project involved and to ensure proper definition of
responsibilities and implementation of these authority requirements in the execution of
the project Scope Of Work

SCOPE

This document starts with identification of potential authorities involved in the project,
continues with the definition of involved authorities and their requirements and concludes
with steps to ensure proper implementation of these requirements.

APPLICATION

This document applies to all projects.

TIMING

This procedure should preferably be applied at the proposal stage too as the involvement
or requirements from codes and jurisdictional authorities will impact capital cost,
schedule, labor, documentation, construction position, and many other project execution
considerations that need to be planned for.

DETAILED PROCEDURE

Responsible parties are:

 Project Manager
 All Project Discipline Leads
 Authority Coordinator
 Client

Note: Always observe the possible role of client/end user: In some cases their
involvement can be required, e.g. the user design specification required by
ASME VIII Division 2.

Authorities in the context of this procedure are all government, municipality and local
authorities, legal inspection, insurance and certification agencies, custom and import
agencies, etc.

A "single department authority" is defined in the context of this procedure as an authority

which may have impact on the activities of more than one department.

Copyright © 2010, Fluor Corporation. All Rights Reserved. Engineering

 Practice 000.200.0716
Date 03Nov2010
Page 2 of 3

GENERAL AUTHORITY ENGINEERING

DISCIPINE INTERFACE

REQUEST FOR POTENTIAL AUTHORITIES

The Project Manager requests all departments (i.e. technical disciplines, procurement and
construction) in an early phase of the project, their input regarding authorities who might
possibly be involved in the project. Prior to the request the Project Manager issues all
available and relevant client and/or proposal information.

AUTHORITY COORDINATOR

Depending on the size of the project and the office organization the Project Manager can
select to assign an Authority Coordinator.
This will provide a focal point in the Project to better coordinate this activity with the
involved Disciplines, Client and Authorities.

It is important for the success of a Project to clearly identify "What" is needed

(requirements), "When" needed (phase of the Project) and "Who" needs it (Authority). As
this varies from one Project to the other, based on the type of Project or local
requirements, the Authority Coordination will be able ensure that authority requirements
are implemented and executed and aviud missing requirements or delays in the Project
schedule.
Documentation to be issued normally involves more than a discipline, so the coordination
role is very important.

It is recommended the prepare a Project Authority Plan where the "what/when/who" and
the different roles and responsibilities are identified. Definition of roles and
responsibilities with Clients must be clear as they (when owners) play a key role in
relations with Authorities

IDENTIFICATION POTENTIAL AUTHORITIES

The discipline Project Leads provide list of all possible involved authorities with brief
description of the known scope of their involvement.

DEFINITION INVOLVED AUTHORITIES

The Project Manager discusses all potential authorities with parties involved, defines and
issues a job bulletin with for each authority involved in the project:

 Responsibility split between Fluor and Client.

 Brief scope of authority involvement (e.g. by type of equipment, material, design and
engineering activity, inspection and certification, etc.).
 Departments involved. (single or multiple).
 Prime responsible department and individual for liaison (a lead discipline engineer or
liaison engineer) with that authority.
 Major action items (e.g. investigation, initial contacts, etc.).
 Authority contact person(s).

Copyright © 2010, Fluor Corporation. All Rights Reserved. Engineering

 Practice 000.200.0716
Date 03Nov2010
Page 3 of 3

GENERAL AUTHORITY ENGINEERING

DISCIPINE INTERFACE

IMPLEMENTATION REQUIREMENTS (SINGLE DEPARTMENT INVOLVEMENT)

The Discipline Lead takes all initiatives and actions to establish in detail the mandatory
requirements (technical, codes, documentation, drawings, etc.) imposed by that authority
with respect to the project scope.

DEFINITION REQUIREMENTS (MULTIPLE DEPARTMENT INVOLVEMENT)

The Discipline Leads or Authority Coordinator discuss and undertake with the
departments involved the necessary initiatives and actions to establish in detail the
mandatory requirements (technical, codes, documentation, drawings, etc.) imposed by
that authority with respect to the activities of the department involved.

They prepare and issue project interface instructions, supplemented with internal
departmental instructions, if required, which defines the major activities, interfaces and
responsibilities of the responsible and involved department.

Note: Make maximum use of existing procedures (e.g. PED coordination procedure).

IMPLEMENTATION REQUIREMENTS (MULTIPLE DEPARTMENT INVOLVEMENT).

The Discipline Leads take all initiatives and actions to ensure that authority requirements
are implemented and/or executed along the guidelines defined.

They provide information and data as requested by responsible department or liaison

engineer to enable a smooth and timely execution of the project and proper liaison with
the authority.

VERIFICATION

The responsible Discipline Lead or Authority Coordinator reviews discipline activities,

documentation and drawings prepared, for compliance with the project execution plan.

REFERENCES

000.200.0718: PED Coordination procedure and Responsibilities,

ATTACHMENTS

Attachment 01: Template for Duties and Responsibilities of the Authority

Coordinator(s)

Copyright © 2010, Fluor Corporation. All Rights Reserved. Engineering

 Practice 000.200.XXXX
Date 03Nov2010
Attachment 01 - Page 1 of 2

GENERAL AUTHORITY ENGINEERING

DUTIES AND RESPONSIBILITIES OF THE AUTHORITY COORDINATOR(S)

PURPOSE

This document provides a list of the detailed responsibilities of the authority coordinator
for:

(list authorities)

SCOPE

This document relates to the requirements of the above-mentioned authorities.

APPLICATION

Project Manager and Lead Engineers to define authority coordination on a specific

project.

GENERAL ACTIVITIE AND RESPONSIBILITIES AUTHORITY COORDINATOR

Overall responsibility for all written and verbal contacts between Fluor and Authorities
during the engineering and design phase of the project.

Review and approve applicable documents generated by other disciplines on the project
for technical soundness and completeness.

Arranges meetings with Authorities as required.

Establishes project specific work instructions and procedures which apply to the
Authority coordination.

Ensures that Authority requirements are implemented and/or executed in a timely

manner.

Act as source of information for questions related to the Authorities.

Copyright © 2010, Fluor Corporation. All Rights Reserved. Engineering

 Practice 000.200.XXXX
Date 03Nov2010
Attachment 01 - Page 2 of 2

GENERAL AUTHORITY ENGINEERING

DUTIES AND RESPONSIBILITIES OF THE AUTHORITY COORDINATOR(S)

DETAILED ACTIVITIES AND RESPONSIBILITIES "AUTHORITY COORDINATOR 1"

(TO BE FILLED IN BE INDIVIDUAL DISCIPLINES)

DETAILED ACTIVITIES AND RESPONSIBILITIES "AUTHORITY COORDINATOR 2"

(TO BE FILLED IN BY INDIVIDUAL DISCIPLINES)

Copyright © 2010, Fluor Corporation. All Rights Reserved. Engineering