project

DEP SPECIFICATION
Copyright Shell Group of Companies. No reproduction or networking permitted without license from Shell. Not for resale
PROCEDURE FOR GLOBAL TECHNICAL STANDARDS
PUBLICATIONS
DEP 00.00.00.30-Gen.
February 2017
ECCN EAR99
DESIGN AND ENGINEERING PRACTICE
© 2017 Shell Group of companies
All rights reserved. No part of this document 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.
This document contains information that is classified as EAR99 and, as a consequence, can neither be exported nor re-exported to any country which is under an
embargo of the U.S. government pursuant to Part 746 of the Export Administration Regulations (15 C.F R. Part 746) nor can be made available to any national of such
country. In addition, the information in this document cannot be exported nor re-exported to an end-user or for an end-use that is prohibited by Part 744 of the Export
Administration Regulations (15 C.F.R. Part 744).
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
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 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 respons bility, consult the Principal.
The right to obtain and to use DEPs is restricted, and is typically 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.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 3
TABLE OF CONTENTS
1.
1.1
1.2
1.3
1.4
1.5
1.6
1.7
INTRODUCTION ........................................................................................................ 5
SCOPE........................................................................................................................ 5
DISTRIBUTION, INTENDED USE AND REGULATORY CONSIDERATIONS ......... 5
DEFINITIONS ............................................................................................................. 5
CROSS-REFERENCES ............................................................................................. 8
SUMMARY OF MAIN CHANGES ............................................................................... 8
COMMENTS ON THIS DEP ....................................................................................... 9
NON NORMATIVE TEXT (COMMENTARY) .............................................................. 9
2.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
POLICY, GOVERNANCE AND STANDARDS STRUCTURE ................................. 10
POLICY ..................................................................................................................... 10
USER INVOLVEMENT ............................................................................................. 10
PROJECT EXECUTION COMMUNITY .................................................................... 11
CONTRACTOR AND MANUFACTURER/SUPPLIER INVOLVEMENT ................... 11
STANDARDS STRUCTURE..................................................................................... 11
TYPES OF DEPS ..................................................................................................... 12
OTHER GLOBAL TECHNICAL STANDARDS ......................................................... 13
PHASES IN DEP PROCESSING ............................................................................. 14
CONTENT OF DEPS AND OTHER TECHNICAL STANDARDS............................. 14
3.
3.1
3.2
3.3
PLANNING CYCLE .................................................................................................. 14
GENERAL ................................................................................................................. 14
OPERATING PLANS ................................................................................................ 14
PROPOSAL FOR TECHNICAL STANDARDS WORK ............................................ 15
4.
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
WRITING NEW AND UPDATING STANDARDS..................................................... 15
GENERAL ................................................................................................................. 15
INITIAL DRAFT ......................................................................................................... 15
COMMENT ROUND ................................................................................................. 16
SECOND DRAFT ...................................................................................................... 16
APPROVAL ............................................................................................................... 17
DISTRIBUTION ......................................................................................................... 17
DEP FEEDBACK ...................................................................................................... 17
PROGRESS AND EXPENDITURE MONITORING .................................................. 18
FILE NAMING CONVENTIONS................................................................................ 18
5.
5.1
5.2
5.3
5.4
5.5
MAINTENANCE ....................................................................................................... 19
GENERAL ................................................................................................................. 19
APPLICATION OF PROJECT TECHNICAL SPECIFICATIONS.............................. 19
REVISION OF EXISTING DEPS .............................................................................. 20
PROCEDURE FOR WITHDRAWAL, DEACTIVATION OR REAFFIRMATION
OF DEPs ................................................................................................................... 21
DEP INDEX REVISION ............................................................................................ 21
6.
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
SPECIFIC RULES FOR STANDARDS CONTENTS ............................................... 22
CLARITY OF REQUIREMENTS ............................................................................... 22
MINIMUM REQUIREMENTS .................................................................................... 24
REFERENCED STANDARDS .................................................................................. 24
MIXING OF EXTERNAL STANDARDS .................................................................... 25
COMMERCIAL STATEMENTS ................................................................................ 25
COPYRIGHT ............................................................................................................. 25
TRADE-NAMES AND COMPANY NAMES .............................................................. 25
PROPRIETARY OR LICENSABLE INFORMATION ................................................ 26
CROSS-REFERENCES WITHIN A DEP.................................................................. 26
VALUES AND TOLERANCES .................................................................................. 26
UNITS ....................................................................................................................... 26
DEM1 STATEMENTS ............................................................................................... 26
7.
REQUISITIONS AND STANDARD FORMS ............................................................ 27
8.
REFERENCES ......................................................................................................... 28
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 4
9.
BIBLIOGRAPHY ...................................................................................................... 28
10.
FIGURES .................................................................................................................. 29
APPENDICES
APPENDIX A
STANDARD STRUCTURE OF DEP SPECIFICATION .................................. 37
APPENDIX B
STANDARD STRUCTURE OF DEP INFORMATIVES .................................. 42
APPENDIX C
EDITORIAL AND TYPOGRAPHICAL REQUIREMENTS .............................. 45
APPENDIX D
MANAGEMENT SYSTEM FOR PORTFOLIO REQUIREMENTS
SPECIFICATIONS........................................................................................... 48
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 5
1.
INTRODUCTION
1.1
SCOPE
This DEP provides policies, specifies requirements and gives recommendations for the
initiation, writing and maintenance of DEPs and other Global Technical Standards.
The target users of this DEP are Authors and Custodians of DEPs.
Requirements relating to the distribution of standards, and the authorisation to receive or
purchase DEPs or other technical standards are not covered in this DEP. The commercial
and licensing focal point in the Technical Standards Team may be contacted for information
on this topic. Packaged Equipment Solutions standards such as SPEPs and GFS that
support replication in projects are not covered in this DEP; see PES 00.00.00.31-Gen.
This DEP is a revision of the DEP of the same number dated February 2015; 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
authorisation to any documents, data or information to which the DEPs may refer.
This DEP is intended for use by those individuals responsible for maintaining the standards
(primarily the Administrator and the relevant Custodians and Authors).
When DEPs are applied, a Management of Change (MOC) process shall 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 word should indicates a recommendation.
The word may indicates a permitted option,
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
1.3.2
DEP 00.00.00.30-Gen.
February 2017
Page 6
Specific definitions
Term
Definition
Action Items
Indicated in the left margin of the standard. Identifies that a position has to
be clarified during the specification phase of a project or an order.
Administrator
Person responsible for the administration of the standards.
The Administrator can be contacted at standards@shell.com.
Auditable
(requirement)
Requirement that is observable and measurable, is neither vague nor
ambiguous, and has finite acceptance/rejection criteria.
Author
Person appointed by the Custodian to be responsible for writing or revising
a Global Technical Standard. The Author is typically an SME for the subject
concerned.
Champion
Person appointed by the GDH to be responsible for the day-to-day
coordination of Global Technical Standards planning, delivery and cost
control.
Custodian
Person within the discipline appointed by the GDH to be responsible for the
contents, upkeep and approval of a specific DEP or other standard. The
Custodian is normally the technical authority on the contents of the
document. The Custodian also acts as the focal point for questions relating
to the content, meaning and application of the Global Technical Standard.
The Custodian is typically the relevant senior discipline specialist.
DEP
Amendment
Historically issued as an interim update between DEP revisions. May
contain both editorial changes (corrections) as well as minor changes to the
content of the DEP. Amendments are identified by both the amendment
number and date on the cover page (e.g., Amendment A01 incorporated
September 2012). DEP Amendments are no longer used.
DEP Circular
A letter previously issued to inform DEP users about the issue, revision,
amendment or withdrawal of a DEP. Each letter was uniquely numbered.
DEP Circulars are no longer used.
DEP IM Tool
A web based database containing all items in the DEP system. The
database provides information pertaining to each DEP item, the annual
DEP plan and status of tracking revisions until publication.
DEP
Informative
A companion to the DEP Specification document of the same number.
Explains the background and reasons for certain requirements in the
DEP Specification.
DEP
Specification
Design and Engineering Practice Specification; for project use - provides a
basis for understanding between the Principal, Contractor and
Manufacturer/Supplier, specifying requirements for a product, process or
service.
DW Standard
Deepwater Standard; provides a basis for understanding between the
Principal, Contractor and Manufacturer/Supplier, specifying requirements
for a product, material or process specifically for deepwater installations.
External
standard
Standard (e.g., ISO, EN, ASME, BS, API, etc.) issued under the auspices of
a non-Shell standards body.
Global
Discipline
Head
Person accountable for the contents of the Global Technical Standards and
who is responsible for the assignment of Custodians.
Inactive DEP
A DEP that is not maintained and is not mandated but is kept on the DEPs
Online library for reference by the project. Use of the DEP content is
optional at the discretion of the discipline engineer.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 7
Term
Definition
OU Variation
Supplement to a DEP, generated by an Operating Unit (OU) to reflect the
regional/local requirements of that OU. OU Variations are no longer in use.
Project
Technical
Specification
The specification generated by a project to reflect the specific technical
requirements of that project.
PRS
Informative
A companion to the PRS Specification document of the same number.
Explains the background and reasons for content in the PRS Specification.
PRS
Specification
A Portfolio Requirements Specification (PRS) is a DEM1 compliant
technical specification developed for a specific business portfolio that
contains consolidated requirements from the individual DEPs applicable to
the portfolio.
Within the boundary conditions defined in the PRS Specification, the PRS
may be selected and applied by projects in lieu of the individual DEPs.
Selection of the PRS is determined by the project during selection of
standards. The management system for PRS is defined in (Appendix E).
PS Table
A table located in the DEP Informative for a DEM1 DEP listing the
associated process safety risks for each process safety mandatory
technical requirement, as well as its associated Risk Assessment Matrix
rating.
Requirements
Database
A structured repository of the technical requirements and supporting
information contained in the DEPs. It is used to generate collections of
requirements including DEPs and project technical specifications.
RM Practice
Run and Maintain Practice; defines a recommended practice that is
intended to meet a desired performance standard. Applies to the “operate,
inspect and maintain” phase of asset life..
Servco
Service Company of the Shell Group.
Standard
Document, established by consensus and approved by a recognised body,
that provides, for common and repeated use, rules, guidelines or
characteristics for activities or their results, aimed at the achievement of the
optimum degree of order in a given context.
NOTE:
WS Standard
1.3.3
From ISO/IEC Guide 2.
Wells Standard; provides a basis for understanding between the Principal,
Contractor and Manufacturer/Supplier, specifying requirements for a
product, material or process specifically for oil and gas wells.
Abbreviations
Term
Definition
CMT
Catalogue Management Tool, which includes the MESC data.
DEM1
Design and Engineering Manual – Number 1
DEP
Design and Engineering Practice
GDH
Global Discipline Head
GFS
General Functional Specification
MESC
Materials and Equipment Standards and Code
OU
Operating Unit of the Shell Group
PES
Packaged Equipment Solutions
PRS
Portfolio Requirements Specification
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
1.4
DEP 00.00.00.30-Gen.
February 2017
Page 8
Term
Definition
PS
Process Safety
PTE
Principal Technical Expert – acknowledged as the person with the
Technical Authority in their area.
P&T
Projects and Technology; the organisation in Shell with ownership of the
DEPs.
RAM
Risk Assessment Matrix as defined in the HSSE Control Framework
Shell GSI
Shell Global Solutions International
Shell P&T
Shell Projects & Technology
SIEP
Shell International Exploration and Production
SME
Subject Matter Expert – acknowledged expert in a very specific area of the
business. The SME actively supports and contributes to the DEPs.
SPEP
Shell Pre-Engineered Package
CROSS-REFERENCES
Where cross-references to other parts of this DEP are made, the referenced section or
clause number is shown in brackets ( ). Other documents referenced by this DEP are listed
in (8).
1.5
SUMMARY OF MAIN CHANGES
This DEP is a revision of the DEP of the same number dated February 2015. The following
are the main, non-editorial changes:
Section/Clause
Change
1.3
Updated definitions
2.2
Deleted ETSB section, sections renumbered
2.12
Deleted Specific Rules for Contents of Technical Standards
2.13
Deleted Controls Section
4
Section updated
5
Section updated, added Inactive DEPs
6.12
Added section on DEM1 statements
Appendix D
Deleted Word processor settings, Appendices renumbered.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
1.6
DEP 00.00.00.30-Gen.
February 2017
Page 9
COMMENTS ON THIS DEP
Comments on this DEP may be submitted to the Administrator using one of the following
options:
Shell DEPs Online
(Users with access to
Shell DEPs Online)
Enter the Shell DEPs Online system at
https://www.shelldeps.com
Select a DEP and then go to the details screen for
that DEP.
Click on the “Give feedback” link, fill in the online
form and submit.
DEP Feedback System
(Users with access to
Shell Wide Web)
Enter comments directly in the DEP Feedback
System which is accessible from the Technical
Standards Portal http://sww.shell.com/standards.
Select “Submit DEP Feedback”, fill in the online form
and submit.
DEP Standard Form
(Other users)
Use DEP Standard Form 00.00.05.80-Gen. to record
feedback and email the form to the Administrator at
standards@shell.com.
Feedback that has been registered in the DEP Feedback System by using one of the above
options will be reviewed by the DEP Custodian for potential improvements to the DEP.
1.7
NON NORMATIVE TEXT (COMMENTARY)
Text shown in italic style in this DEP indicates text that is non-normative and is provided as
explanation or background information only.
Non-normative text is normally indented slightly to the right of the relevant DEP clause.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 10
2.
POLICY, GOVERNANCE AND STANDARDS STRUCTURE
2.1
POLICY
Global Technical Standards are maintained with the specific aim of providing a means
to:
•
execute project work efficiently and cost effectively;
•
enhance asset integrity;
•
transfer knowledge and share best practice.
The policy aims to achieve the following:
1.
•
to maximise the use of external standards;
•
to maintain a single set of DEPs in which requirements additional to the relevant
external standards are minimised;
•
to discontinue local, regional and business-specific variations;
•
to develop and apply Project Technical Specifications during project execution,
using a selection of applicable requirements from the DEPs, supplemented by
the minimum number of project-specific requirements;
•
to constantly improve the quality of Technical Standards by creating and
maintaining feedback loops between users and Custodians (owners) of the
standards;
•
to influence external standards bodies through participation,
endeavouring to reduce the need for additional Shell standards.
thereby
DEPs shall make maximum use of external standards by referring to them wherever
appropriate.
a. A DEP should refer to an external standard and not duplicate its content.
2.
The order of preference for the selection of an external standard on which to base the
DEP, or to refer to in a DEP shall be:
a. International (e.g., IEC)
b. Regional;
c.
National;
d. Industry.
At the discretion of the Administrator and the Custodian, it is acceptable to select a
lower standard in the hierarchy when this lower standard is considered technically
more suitable. Under current circumstances, this could be relevant for cases
where the connection between an international (ISO) standard and the industry
standard (API) has been lost and maintenance of the API standard is more up to
date than the ISO one.
2.2
USER INVOLVEMENT
1.
The DEP work process shall facilitate the involvement of DEP users (including
Projects, Operating Units, Contractors and Suppliers) during DEP creation and DEP
revision (e.g., comment rounds).
User involvement is considered critical to driving continuous improvement in the
DEPs.
2.
DEPs that are issued on comment round shall be posted on the Technical Standards
web portal.
Interested individuals within Shell can participate in the comment round by
providing comments.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
2.3
DEP 00.00.00.30-Gen.
February 2017
Page 11
PROJECT EXECUTION COMMUNITY
DEPs are written for project discipline engineers (and Contractors) to apply and are not
written as purchase specifications. Projects are expected to select the applicable
requirements, adapt them as necessary and combine them to make a project-specific
technical specification for a Contract or Purchase Order. These project-specific technical
specifications can be replicated if appropriate for future projects.
2.4
1.
Project Technical Specifications should be subject to a technical and commercial
authorisation process to demonstrate that they contain the minimum requirements in
addition to applicable industry standards.
2.
Project Technical Specifications should be used as feedback (input) into subsequent
DEP revisions (5.3.3).
3.
Project lessons learned that relate to DEPs and technical standards should be inputted
into the DEP feedback system for consideration as opportunities for improvement.
CONTRACTOR AND MANUFACTURER/SUPPLIER INVOLVEMENT
1.
Selected Contractors and Manufacturers/Suppliers should be involved in commenting
on DEPs during the creation and revision process.
a. The DEP Author and Custodian shall identify the parties to be included in the
comment round when submitting a draft DEP to the Technical Standards
Team.
2.5
2.
A confidentiality agreement addressing DEPs shall be in place when including
rd
3 parties in the comment round.
3.
Feedback to a 3rd party at the end of the comment round shall only include the
comments raised by the 3rd party and responses to those comments from the Author
and Custodian.
STANDARDS STRUCTURE
The relationship of DEPs to Industry standards and project standards is illustrated in
Figure 1.
The objectives of the standards structure are to provide:
•
transparency (clear understanding) of the relationships;
•
cost efficiency through maximum focus on the external world;
•
a clear management structure to control variations and to obtain feedback of
knowledge;
•
a reduction in administrative effort by centralising information as much as
possible.
The main elements of the standards structure for a particular standard are:
1.
•
maximum use of the external standard (where available);
•
the DEP, which supplements the external standard reflects a minimum of
additional Shell Group requirements;
•
each project applies Project Technical Specifications, which select the
applicable DEP requirements and supplement them as necessary to reflect the
specific requirements of a project.
Each DEP shall have an external standards strategy identifying the following:
a. The applicable external standards;
b. How the DEP is maximising the use of these standards.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 12
c.
2.
Strategy for involvement in the external standard body, if practical, to minimise
the need for Shell variations.
DEPs that are based on an external standard shall be written either in the form of an
endorsement of, or amendments/supplements to the external standard (Appendix A).
Where endorsement is not practical, the preferred method is to base the DEP
directly on an external standard as an amendment/supplement. However, this will
not be possible if a suitable external standard does not exist, or if basing the DEP
on one would require extensive amendments. Typically, if more than 25 % of the
external standard’s paragraphs would require amendment, it is impractical to
structure the DEP as an amendment/supplement of the external standard.
2.6
TYPES OF DEPS
2.6.1
General
1.
The DEPs shall consist of the DEP Specification, and in most cases, a companion
DEP Informative document, which are defined in Table 1.
Table 1
DEP Documents
DEP Specification
These provide a basis for understanding between the
Principal, Contractor and Manufacturer/Supplier, specifying
requirements for a product, process or service and indicating
the criteria whereby compliance can be assessed.
DEP Informative
These are companion documents to each DEP Specification.
The DEP Informative documents the background and reason
for certain requirements, particularly where those
requirements have raised questions in the past.
The principal purpose of the DEP Informative is to assist the
discipline in retaining knowledge about certain requirements
in the DEPs and how they should be applied. In some cases,
the DEP Informative may also contain examples or addenda
to assist with project specific application of the DEP.
It is NOT intended for the DEP Informative to be a lengthy
tutorial on any particular subject.
DEP Excel
2.
A spreadsheet format of the Specification and Informative
content that allows the project to select and apply the
appropriate content when preparing a project specific
technical specification.
DEP Informatives should not be distributed to Contractors or Manufacturers/Suppliers.
By their nature, DEP Informatives can contain Shell intellectual property and are
directed towards Shell personnel rather than to Contractors and Manufacturers.
3.
2.6.2
DEP Excels shall be stripped of Informative content before sharing with Contractors or
Manufacturer/Suppliers.
DEP supporting documents
The document types in Table 2 are maintained in the DEP system as supporting
documents.
In addition to the DEP system, the CMT system includes technical specifications and
MESC details relating to catalogue components.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 13
Table 2
Requisition/Datasheet
Supporting Documents
Provides the engineering information required for the
procurement of equipment and materials.
Requisitions are indexed in DEP 30.10.01.10-Gen.
Standard Form
These are used to present information in a consistent
manner.
Standard Forms are indexed in DEP 00.00.10.05-Gen.
Standard Drawing
Drawings of equipment or configurations that are
considered to have wide applicability within Shell.
Standard Drawings are indexed in DEP 00.00.06.06-Gen.
Piping Classes
2.6.3
An assembly of piping components in a piping system,
suitable for a defined service within design limits.
DEM1 status
Selected DEP Specifications are listed in the HSSE & SP Control Framework under
DEM1 as containing at least one mandatory process safety related requirement.
The term “SHALL [PS]” is used within these DEPs to indicate DEM1 requirements.
DEM1 requirements are mandatory technical requirements intended to prevent or
mitigate a process safety incident with RAM Red or Yellow 5A or 5B rating on the Group
RAM.
1.
2.7
For each DEM1 DEP, the DEP Informative shall include a Process Safety (PS) Table
providing the justification for mandatory SHALL [PS] statements that are deemed
necessary to potentially mitigate process safety related incidents.
OTHER GLOBAL TECHNICAL STANDARDS
The technical standards listed in Table 3 are administered by the Technical Standards
Team and are included in the same management system as the DEPs (as described in
this DEP).
Table 3
Other Technical Documents
DW Standard
Restricted standards specifying requirements for a product,
material or process for deepwater installations. By their nature,
DW Standards contain information that is not routinely
distributed outside of Shell.
PRS
Portfolio Requirements Specifications (PRS) are technical
specifications developed for application within a specific
business portfolio. They are based on a selection of DEPs
applicable to the portfolio, maintained to an identified DEP
version and are assured to be DEM1 compliant. The DEM1
assurance process includes an annual review to incorporate
new learnings from the DEPs.
The management system for PRS is defined in (Appendix E).
RM Practice
Archive documents that specified requirements or provided
guidance for activities being performed during the operating
phase of a facility (as distinct from design, engineering,
procurement and construction). Now superseded by documents
maintained by the Technical Safety Discipline.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 14
The technical standards listed in Table 4 are administered by the Technical Standards
Team but are covered by a different management system (refer to
PES 00.00.00.31-Gen.).
Table 4
Packaged Equipment Solutions
PES
Packaged Equipment Solutions administrative documents.
SPEP
Shell Pre-Engineered Package. Refer to PES 00.00.00.31-Gen.
GFS
General Functional Specification. Refer to
PES 00.00.00.31-Gen.
The Wells Manuals are not administered by the Technical Standards Team and are
administered by the Wells organization.
2.8
PHASES IN DEP PROCESSING
The three phases in processing a DEP are:
•
initiating a DEP and DEP planning;
•
writing a new DEP;
•
maintenance of existing DEPs (revision, reaffirmation or withdrawal).
This sequence of events is shown in Figure 2. There is a feedback loop from
maintenance to initiation.
2.9
CONTENT OF DEPS AND OTHER TECHNICAL STANDARDS
1.
The internal structure and basic content of DEP Specifications shall be as shown in
(Appendix A).
2.
The structure of DEP Informatives shall be as shown in (Appendix B).
The basic requirements for the editorial and typographical requirements are given in
(Appendix C).
3.
PLANNING CYCLE
3.1
GENERAL
The flowchart describing the standards planning cycle is shown in Figure 3.
Factors leading to the need to revise an existing standard are described in (5).
The identification of the requirement for a new standard is facilitated through inclusion in
the annual operating plan.
1.
Standards work may be initiated when any of the following apply:
a. an existing standard needs revision;
b. a new standard is required.
3.2
OPERATING PLANS
1.
By the end of each year, the Administrator shall develop the annual DEP standards
plan detailing the following:
a. the agreed plan for DEPs and other technical standards to be revised, issued
new or withdrawn in the following year (the first year of the plan) along with the
budget provision;
b. a preliminary plan for standards work in subsequent years.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
3.3
DEP 00.00.00.30-Gen.
February 2017
Page 15
2.
The standards plan shall be maintained throughout the year in the DEP IM Tool,
accessible from the Technical Standards web portal http://sww.shell.com/standards.
3.
External and internal standards work plans shall be aligned.
PROPOSAL FOR TECHNICAL STANDARDS WORK
1.
The Custodian shall be responsible for proposing a new standard and for proposing a
revision to an existing standard.
2.
For a new standard, the Administrator shall assign a provisional standard number.
This number will become final upon issue of the standard.
3.
For revision of existing standards, the original standard number shall be used unless a
change in scope warrants the allocation of a different number.
4.
WRITING NEW AND UPDATING STANDARDS
4.1
GENERAL
The flowchart describing the generation of a new or revised DEP is shown in Figure 4a
and Figure 4b.
DEP indices, requisition/data sheets, standard drawings and standard forms need not
follow the requirements of (4). However, the processes described in (4) are generally
applicable to other types of standards.
1.
Where the DEP is an endorsement of an external standard without further
modification, the DEP should be a brief statement of endorsement.
This will depend on whether or not a suitable external standard(s) exists covering
the subject matter.
2.
If an external standard is available, but does not fully cover Shell Group requirements,
then the DEP should amend/supplement the external standard.
a. The DEP may be used to confirm requirements left optional in the external
standard and so reduce engineering effort in the projects.
3.
4.2
If an external standard is not available or is considered impractical as a base standard,
the DEP shall contain the compilation of the minimum common Shell Group
requirements.
INITIAL DRAFT
1.
If a DEP is being proposed for inclusion in the DEM1 Manual, the Author and
Custodian should first consult with the DEM1 Team as described in the DEM1 User’s
Guide.
2.
When drafting a DEM1 DEP, every SHALL [PS] clause shall have a supporting entry in
the DEP Informative with the supporting risk rating and supporting incident or credible
scenario.
3.
The Administrator shall be consulted when drafting a DEP to provide support and
access to the requirements database, and to advise on the structure of the standard
and relationship to external standards.
a. Initial drafts may be prepared directly in the requirements database or by
amending Word or Excel versions of the content.
4.
The Author shall convert any drawings for the DEP into their final form.
5.
For drawings produced electronically, the file format should be as specified by the
Administrator.
6.
The completed draft should be reviewed by the Custodian prior to submission to the
Administrator.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
7.
4.3
DEP 00.00.00.30-Gen.
February 2017
Page 16
Upon receipt by the Administrator, the draft DEP shall be edited and audited to ensure
it complies with this DEP and loaded into the requirements database.
COMMENT ROUND
1.
The Author/Custodian shall provide to the Administrator a suggested list of SMEs with
a major technical interest in the subject concerned, including the following as
applicable:
a. Representatives from each region for all relevant disciplines;
b. Representatives with recent experience of implementing projects involving the
subject;
c.
non-Shell parties such as Contractors and Manufacturers/Suppliers;
d. for DEM1 DEPs, representatives at TA-1 level.
2.
The Administrator may add extra names to the list to ensure appropriate coverage.
3.
If the DEP is an existing or proposed DEM1 listed DEP, the DEM1 Standards Engineer
shall be included in the list.
4.
At the discretion of the Administrator, the DEP may be excluded from a formal
comment round.
An example of this could be a non-technical revision or correction of a DEP.
a. A workshop forum may be used instead of document-based comment round to
engage a range of reviewers and deliver a technical review.
5.
All comments shall be submitted to the Administrator using the DEP Comment Round
Form.
6.
Comments of substance should be accompanied by clear reasoning and explanation
so that the Author can respond effectively.
7.
The comment round is not intended to lead to a period of extensive consensus building
throughout the user community. The Custodian is ultimately responsible for the
technical content of the DEP and shall make decisions with respect to incorporating
comments received.
8.
The Administrator shall compile all comments into the requirements database and
pass them on to the Author/Custodian for consideration.
9.
The Custodian (or the delegated Author) shall respond to all comments of substance
with a decision to accept or reject.
It is good practice to provide a brief explanation of the decision.
10. Should there be any reason for disregarding a substantial comment, this should be
discussed and resolved between the Author or Custodian and the commentator, and
recorded in the requirements database.
11. The Administrator shall circulate the compiled comments register, showing the
resolution of all comments received, by email to the individuals that provided
comments.
4.4
SECOND DRAFT
1.
The Author shall update the draft DEP to reflect changes agreed following the
comment round and submit to the Administrator.
2.
A second edit and audit shall be performed by the Administrator to assess compliance
with this DEP.
Gaps identified during edit/audit could require re-drafting and further update by
the Author.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
3.
4.5
DEP 00.00.00.30-Gen.
February 2017
Page 17
The classification of the DEP for Export controls shall be defined on completion of the
second audit and included in the DEP Specification, DEP Informative and DEP Excel.
APPROVAL
1.
Following the resolution of second audit results, the Administrator shall obtain approval
of the Custodian to publish.
The Custodian’s approval confirms that the requirements contained in the DEP
have been justified both technically and commercially, and that the DEP is written
in accordance with the requirements of this DEP.
a. At the discretion of the Administrator, the formal approval of the Custodian
may be waived.
For example, if the changes are purely editorial.
2.
4.6
Final approval for publication of each DEP shall be at the discretion of the Executive
Vice President PTE.
DISTRIBUTION
1.
After the DEP has been final approved, the Administrator shall arrange for distribution.
2.
If the DEP refers to other DEPs or external standards, the DEP should only be issued
if they either already exist or have been approved for issue (4.4).
3.
The release of new DEPs, revised DEPs and the withdrawal of DEP documents shall
be controlled in Shell DEPs Online by the Administrator.
4.
The Shell DEPs Online system shall maintain discrete collections of DEP documents
that can be selected for use on a specific project.
These collections are referred to as DEP versions (e.g., DEPs v39 was released
in February 2015).
4.7
5.
Each DEP (individual document) revision shall be associated with one or more DEP
versions that are maintained in Shell DEPs Online for use on projects.
6.
All active DEPs (including new DEPs, revised DEPs and all other DEPs that are
currently active but have not been revised) shall be made available under the latest
DEP version.
7.
The Administrator shall maintain a record of which DEPs are classified as EAR99 in
the DEP IM Tool.
8.
DEPs that are classified as EAR99 shall not be distributed to Generally Embargoed
Countries unless approved by an Export Controls officer.
DEP FEEDBACK
Comments on DEPs and other standards are welcomed and encouraged. Comments
can be offered at any time, not just during a formal update/review cycle.
Drafts of both new standards and revised standards are widely distributed for comment.
1.
A system for collecting and tracking unsolicited feedback on DEPs for the purpose of
continuous improvement shall be maintained by the Administrator.
Feedback obtained during comment rounds administered as part of the DEP
revision process (4.3) need not be entered in the DEP Feedback system.
Recommended changes arising from feedback will be used when determining the
timing of DEP revision.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
2.
DEP 00.00.00.30-Gen.
February 2017
Page 18
Feedback on standards may be submitted at any time by one of the following:
a. Entering comments directly into the DEP Feedback System on the Technical
Standards Portal http://sww.shell.com/standards (mandatory for users with
access to Shell Wide Web);
b. Downloading DEP Standard Form DEP 00.00.05.80-Gen. (DEP feedback
form).
c.
Requesting a DEP feedback form from the Administrator at
standards@shell.com (for users without access to Shell Wide Web).
For the last two cases, after feedback is entered into the DEP Feedback
Form, it is attached to an email and sent to the Administrator at
standards@shell.com.
3.
4.8
4.9
All comments and Custodian responses shall be visible in the DEP Feedback System
accessible from the Technical Standards website.
PROGRESS AND EXPENDITURE MONITORING
1.
The Administrator shall monitor progress against the annual operating plan.
2.
The Standards Champions shall ensure delivery of first draft and final draft documents
to the Standards Team for the DEPs listed in the annual operating plan and for
monitoring expenditures under the standards budget codes for their disciplines.
FILE NAMING CONVENTIONS
The Shell DEPs Online distribution system (4.5) requires a specific file naming
convention for the published DEP files. Since multiple revisions and/or amendments of
the same DEP documents are available in the system, each file requires a unique file
name.
1.
The DEP Specification, Informative and Excel Export file name shall consist of the
following components:
a. the DEP number string (8 digits),
b. the DEP type (Spec or Inf),
c.
the revision date (4 digit year, then 2 digit month, YYYY-MM),
d. amendment number
e. the file extension (.pdf,.docx, .xls).
2.
Amendment numbers shall be designated with the prefix A followed by 2 digits.
When a new revision is issued, the designation A00 is used to indicate that no
st
amendment exits. A01 denotes the 1 amendment and A02 denotes the
nd
2 amendment.
3.
Spacing between the number, type, date and amendment number shall be an
“underscore”.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 19
DEP number string (8 digits )
Amendment number to denominate subsequent
amendment revisions (prefix A with 2 digits )
revision date
WWXXYYZZ _Type_YYYY-MM_A00.file extension
DEP type (e.g. Spec , Inf, Export)
DEP 31.38.01.11-Gen.
Specification
Piping - General
requirements
February 2017
DEP 31.38.01.11-Gen.
Informative
Piping - General
requirements
February 2017
5.
MAINTENANCE
5.1
GENERAL
pdf & Doc, docx, xls or xlsx
31380111_Spec_2017-02_A00.pdf
31380111_Spec_2017-02_A00.doc
31380111_Inf_2017-02_A00.pdf
31380111_Inf_2017-02_A00.doc
The flowchart for maintenance of a DEP is shown in Figure 5. Separate detailed
flowcharts describe the:
• application and maintenance of Project Technical Specifications (Figure 5a);
• requirements for revising DEPs;
• procedure for withdrawal or reaffirmation of DEPs (Figure 5b).
The processes described in (5) are generally applicable to other types of standards.
5.2
1.
For DEM1 listed DEPs, revisions involving changes to SHALL [PS] statements shall be
permitted only in conjunction with a revision to the DEM1 Manual (one time per year).
2.
Revisions to the DEP Informative shall coincide with the companion DEP Specification,
such that the revision date of the Informative is maintained in alignment with the DEP.
APPLICATION OF PROJECT TECHNICAL SPECIFICATIONS
Project Technical Standards are prepared and maintained by the Project management
and are covered in the Project Guides and Standards.
1.
For a particular project, the requirements that are applicable to the project should be
selected using the DEP Excel.
DEPs are general documents and the requirements that are applicable to the
project as selected and blanket application of all requirements can lead to
excessive complexity when communicating with Contractors and Suppliers,
resulting in additional cost.
Approval of the requirements selection and any resulting Project Technical
Specification is managed through the Project controls.
2.
When DEPs are amended by a project, an entry should be made in the DEP Feedback
system to help drive the improvement process.
3.
Experience obtained from the application of the standards should be fed back to the
Custodians for consideration in the next revision of the DEP.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
4.
DEP 00.00.00.30-Gen.
February 2017
Page 20
Requirements that are commonly specified in Project Technical Specifications and
common project derogations from DEM1 requirements should be incorporated in the
DEP.
5.3
REVISION OF EXISTING DEPS
5.3.1
Change to regulations
1.
5.3.2
5.3.3
Changes to international regulations should be reflected in the external standard
(if applicable) and the DEP.
Change to external standard
1.
The Custodian of a DEP shall monitor changes to external standards referenced by
the DEP and determine if a corresponding DEP update is required.
2.
Shell members of external standard committees should seek to incorporate the
relevant additional requirements currently in the DEP into the external standard.
Review of Project Technical Specifications and DEM1 derogations
1.
5.3.4
Requirements that are commonly specified in Project Technical Specifications and
derogations to DEM1 should be routinely reviewed by the Custodian with the objective
of incorporating these in the DEP (5.2).
Findings of technical audits
1.
If a technical audit reveals that a requirement in a DEP is unclear or cannot be applied
locally, the Custodian shall review the DEP and implement a revision where needed.
a. An entry should be made in the DEP Feedback System to help drive this
process.
Technical audits are carried out on the design and operation of Shell Group
facilities. One of the objectives of these audits is to determine conformance to
standards.
5.3.5
Change in technology or best practice
1.
5.3.6
Changes in available technology, equipment or best practices should result in a review
of the DEP.
Commercial reasons
1.
If the commerciality of a DEP is questioned, this should trigger its review.
Examples of this are:
• significant cost increase when compared to an external standard or a
Manufacturer’s standard product;
• the need to improve variety control.
5.3.7
Scheduled Revisions
1.
Changing a DEP can have a significant administrative impact on users and DEP
revisions should be as infrequent as possible, preferably linked to the update cycle of
relevant external standards.
2.
Each DEP shall be formally reviewed by the Custodian every 5 years against the
criteria listed in (5.3) to determine if it is still current and fit-for-purpose.
The outcome of the Custodian review can result in:
•
Withdrawal of the DEP (5.5) if it is no longer adding significant value;
•
Reaffirmation of the DEP (5.5) and planning for the next review;
•
Scheduling of the next revision.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
3.
5.3.8
DEP 00.00.00.30-Gen.
February 2017
Page 21
The DEP Administrator shall assist the Custodian review by providing information on
DEP downloads and derogations.
DEP feedback
Feedback collected in the DEP Feedback System could trigger a revision of the DEP.
5.3.9
Process safety incidents
Process safety incidents that have occurred either within Shell Group companies or
external to Shell can justify a review. Technical requirements can be added or revised in
order to prevent or mitigate the risk.
5.4
PROCEDURE FOR WITHDRAWAL, DEACTIVATION OR REAFFIRMATION OF DEPs
The procedure for withdrawing or reaffirming DEPs whose last review is older than five
years is shown in the flowchart in Figure 5b.
1.
DEPs that require revision (5.3) shall follow the normal sequence of events; see (3)
and (4).
2.
For reaffirmation of DEPs that are more than five years old and are still required, the
following procedure shall apply:
a. the Custodian or Author reviews any changes to the referenced standards and
any feedback in the DEP Feedback System;
b. if the Custodian considers the DEP is still valid, it is reaffirmed by setting a
new review interval of up to 5 years in the DEP IM Tool and the DEP
Specification is not amended.
3.
DEPs that are no longer required shall be withdrawn as follows:.
a. The Custodian assesses that a DEP is no longer required;
Withdrawal of a DEM1 listed DEP constitutes a change to DEM1. Refer to the
DEM1 user manual.
b. The Custodian approves the reaffirmation or withdrawal.
The withdrawal of a DEM1 listed DEP also requires governance approval, and
only occurs in conjunction with an approved revision to DEM1. Refer to DEM1
user manual.
4.
The withdrawal of a DEP shall be indicated in the DEP Index (DEP 00.00.05.05-Gen.)
and in the “What’s New” feature of Shell DEPs Online.
5.
DEPs that are considered to be no longer suitable for the collection may be classified
as Inactive for a period.
Inactive DEPs are not mandated but are retained on the DEP Online register for
reference by projects. Their use is at the discretion of the project discipline
engineer.
6.
5.5
Inactive DEPs shall be reviewed by the Custodian at a maximum interval of 5 years to
determine if they will be formally withdrawn, retained as inactive or updated to be
added to the active DEP catalogue.
DEP INDEX REVISION
1.
The DEP Index (DEP 00.00.05.05-Gen.) shall be issued at least annually by the
Administrator.
2.
The DEP Index shall identify the latest revision of the indexed DEPs and whether a
DEP has been withdrawn.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 22
6.
SPECIFIC RULES FOR STANDARDS CONTENTS
6.1
CLARITY OF REQUIREMENTS
6.1.1
General
1.
Requirements shall be auditable and unambiguous.
This means avoiding terms such as “minimise”, “generally”, “typically”, “etc.”,
“shall consider”.
2.
Each requirement, recommendation or permissive statement should be identified as a
separate clause (to the extent practical) within the DEP with each clause identified by
a number as follows:
a. Allow one shall / should / may / refer / see verb per clause;
b. Use sub-items to structure related clauses;
c.
Keep SHALL [PS] clauses separate from shall / should / may statements;
d. Provide sufficient content so that the clause and its sub-items is stand-alone
and can be understood;
e. Check that the requirement is precise and verifiable.
Would a reader be clear on the deliverable for the requirement and how to
confirm that it has been achieved?
3.
Explanations should be clear, succinct and logical.
4.
The rationale and background for a requirement should be recorded in a DEP
Informative but not in the DEP Specification.
5.
Requirements shall be consistent with each other, with no contradictions.
6.
Requirements once specified shall not be made optional at a later stage, which would
then leave the reader uncertain as to the final requirement.
7.
Information that should already be known to the intended user should not be included.
8.
Similarly, diagrams should be used to illustrate principles when necessary.
a. Photographs and colour coding should not be used.
9.
Requirements shall be stated once in the DEP and cross-referenced if necessary (i.e.,
no duplication of requirements).
10. See (6.12) for additional DEM1 statement requirements.
6.1.2
Verbal forms
1.
In DEP Specifications and other technical standards, normative requirements,
recommendations and permissions shall be indicated using the verbal forms specified
in the first column of Table 5, Table 6 and Table 7.
Tables 5, 6 and 7 are based on the ISO Directives Part 2.
2.
The equivalent expressions given in the second column of these tables shall be used
only in exceptional cases when the form given in the first column cannot be used for
linguistic reasons.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 23
Table 5
Verbal forms to indicate normative requirements
Verbal form
Equivalent expressions
Shall
SHALL [PS]
is to
is required to
it is required that
has to
only … is permitted
it is necessary
shall not
SHALL [PS] not
is not allowed [permitted] [acceptable] [permissible]
is required to be not
is required that … be not
is not to be
Do not use “must” as an alternative for “shall”. (This will avoid any
confusion between the requirements of a document and external statutory
obligations.)
Do not use “may not” instead of “shall not” to express a prohibition.
To express a direct instruction, for example referring to steps to be taken
in a test method, the imperative mood may be used.
EXAMPLE “Switch on the recorder.”
Table 6
Verbal forms to indicate normative recommendations
Verbal form
Equivalent expressions
Should
it is recommended that
ought to
should not
it is not recommended that
ought not to
Table 7
Verbal forms to indicate normative permissions
Verbal form
Equivalent expressions
May
is permitted
is allowed
is permissible
Do not use “possible” or “impossible” in this context.
Do not use “can” instead of “may” in this context.
NOTE:
“May” signifies permission expressed by the document, whereas “can” refers to
the ability of a user of the document or to a possibility open to him/her.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
3.
DEP 00.00.00.30-Gen.
February 2017
Page 24
Normative references to other requirements and other standards shall use one of the
following forms:
a. “Refer to …”
b. “See …”
4.
Informative expressions should use the terms can, might, could, would, need to.
5.
Conditional statements that require the permission of the Principal shall use one of the
following forms:
a. “subject to the approval of the Principal”
b. “subject to approval by the Principal’s designated Technical Authority”
c.
6.2
“subject to approval by the Principals designated Technical Authority (TA-2)
for corrosion and metallurgy”
MINIMUM REQUIREMENTS
1.
DEP Specifications shall state Shell Group minimum requirements with the objective of
minimising the need for project amendments.
2.
If the scope for application of a requirement is limited, the context of this limited scope
shall be made clear in the standard.
3.
Requirements should not be stated that are subject to variation in different applications
unless the DEP identifies the circumstances under which the requirement is applicable
or under which a particular choice is suitable.
The DEP Requisition or Standard Form would normally be the vehicle for
selecting the valid option for a particular application.
4.
When a DEP presents technical requirements where choices are to be made, the DEP
may use the “Action Item” method defined in (1.3.2) and described in (Appendix A,
A.3.5) and (Appendix C, C.4.5) to identify the areas that require clarification or decision
by the Principal when applying the DEP.
5.
Requirements should not be stated which vary depending on the selected Supplier.
6.3
REFERENCED STANDARDS
6.3.1
General
1.
Sections from external standards shall not be duplicated.
2.
Sections or requirements from other DEPs shall not be duplicated.
Duplication leads to inconsistencies and conflicts.
3.
When references are made to other DEPs, the reference should identify the specific
clause(s) that apply, unless it is clear that the entire DEP is to be applied.
For example, “Refer DEP xx.xx.xx xx-Gen., Section 2.1 for requirements related to
…”
4.
When an external standard is selected as a reference, the order of preference is as
follows unless a standard lower in the hierarchy is considered technically more
suitable:
a. International standard (ISO or IEC);
b. Regional standard;
c.
National standard;
d. Industry standard.
5.
The title of the referenced standard should not be quoted in the text of a standard.
6.
The title shall be given in the list of referenced standards (6.3.4).
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
6.3.2
Standard invoked by “latest edition”
1.
6.3.3
Only the identifying number of the referenced standard (e.g., ASTM E709) should be
quoted in the text of a standard, without the date, title, clause, tables.
Standard invoked by “specific date”
1.
6.3.4
DEP 00.00.00.30-Gen.
February 2017
Page 25
Only the identifying number and, as appropriate, the date, clause, table of the
referenced standard should be quoted in the text of a standard.
List of referenced standards
1.
Included at the end of the main text of each standard shall be a list of referenced
standards that gives the standard number and the title.
a. The list shall display the title on the left followed by the standard number on
the right as shown in (8).
2.
The references should be listed and described in the following way: first the Shell
Global Technical Standards, e.g., DEPs and Standard Drawings, second external
standards.
3.
The list shall include only the standards that are actually referenced in the DEP and
are, by nature of the context, integral with the DEP.
a. Any other documents that the Author wishes to include, e.g., source
documents, shall be separately listed under a heading such as “Bibliography”
or “Literature”.
4.
6.4
Reference shall not be made to standards or documents that are unavailable to a Shell
user.
MIXING OF EXTERNAL STANDARDS
1.
External standards should not be mixed within a DEP.
For example, if specifying requirements or additions to an ASME code for
pressure vessels, do not require welding qualification and acceptance to be in
accordance with a British Standard.
For example, avoid referring to one external standard, e.g., an ASTM
specification, which only defines a test method and then referring to another
external standard, e.g., a British Standard, for the acceptance criteria.
6.5
COMMERCIAL STATEMENTS
1.
6.6
DEPs shall not stipulate commercial issues such as prices, warranties, guarantees,
competitiveness, freedom of access to premises, purchasing conditions.
COPYRIGHT
1.
Material known to infringe on another party’s copyright shall not be included in a DEP.
a. If it is the intention to include such material, written permission shall be
obtained from the copyright holder.
6.7
TRADE-NAMES AND COMPANY NAMES
1.
DEP Specification and Informative shall not include trade names or specific company
products or names.
This is to avoid commercial conflicts and to comply with legal requirements
pertaining to open competition in the marketplace.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
6.8
DEP 00.00.00.30-Gen.
February 2017
Page 26
PROPRIETARY OR LICENSABLE INFORMATION
1.
Information that is considered to be proprietary or licensable shall not be included
within a DEP Specification or Informative.
The DEP Specifications and Informatives are licensed to third parties and thus this
information would be disseminated.
6.9
CROSS-REFERENCES WITHIN A DEP
1.
Where cross-references to other parts of the same DEP are made, the referenced
section number should be shown in brackets “( )”.
External references are covered in (6.3).
6.10
VALUES AND TOLERANCES
1.
6.11
When values are specified, it should be made clear whether they are nominal,
maximum or minimum values or are subject to tolerances.
UNITS
1.
The International System of Units (SI) and DEP 00.00.20.10-Gen. shall be applied in
DEPs as a matter of policy.
2.
The SI units should be followed by US Customary units in brackets.
a. Each DEP that contains dual units should indicate that, when agreed by the
Principal, the indicated USC values/units can be used.
6.12
DEM1 STATEMENTS
1.
All SHALL [PS] statements shall be reviewed and meet the following:
a. Have a corresponding process safety risk described in the Informative and
requirement prevents or mitigates the described risk;
b. The process safety risk is clearly described and RAM rated
c.
For rating of 5B or RAM Red, there is a definitive incident identified associated
with the risk that is to be mitigated or prevented (incident example);
d. For 5A rating there is a credible scenario described;
e. The statement relates to the Design and Construction Project Phase (not
Operations or Maintenance);
f.
The requirement is clear and specific, not using of vague terms (such as
“inappropriate”, “sufficient” or “thorough”) that are open to interpretation;
g. The requirement is an action that is singular in purpose and verifiable
(auditable);
h. The requirement is unique and not repeated elsewhere in the DEP collection.
2.
The following shall not be used as SHALL[PS] requirements:
a. Requirements that mandate the use of a complete set of requirements such as
other DEPs, DEM1 requirements or full external standards
For example, can’t have “SHALL[PS] comply with DEP 00.00.00.30-Gen.”
or “SHALL[PS] comply with ASME B31.3”. The referenced document has
shall/should/may and informative content and it is then unclear what
precisely is the DEM1 requirement.
b. Wording that allows deviation (without a Derogation), making them not DEM1
by definition.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
7.
DEP 00.00.00.30-Gen.
February 2017
Page 27
REQUISITIONS AND STANDARD FORMS
1.
The extent to which Requisitions and Standard Forms follow this DEP shall be
determined on a case-by-case basis by the Administrator.
Requisitions and Standard Forms are available in electronic form.
2.
When a new or revised DEP Specification is issued, the corresponding DEP
Requisition(s) and/or Standard Form(s) should also be prepared, or revised, if
necessary.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
8.
DEP 00.00.00.30-Gen.
February 2017
Page 28
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. The DEPs and most referenced external standards are available to Shell staff on the SWW (Shell
Wide Web) at http://sww.shell.com/standards/.
SHELL STANDARDS
Global Technical Standards index
DEP 00.00.05.05-Gen.
Standard drawings index
DEP 00.00.06.06-Gen.
Standard forms index
DEP 00.00.10.05-Gen.
Requisitions index
DEP 30.10.01.10-Gen.
The use of SI quantities and units (endorsement of ISO 31, ISO 1000 and
ISO 80000)
DEP 00.00.20.10-Gen.
DEP feedback form (Standard Form)
DEP 00.00.05.80-Gen.
Procedure for packaged equipment solutions publications
PES 00.00.00.31-Gen.
Design and Engineering Manual (DEM 1) – Application of Technical
Standards
https://eu001sp.shell.com/sites/AAAAA8432/CF/Web/Design Engineering Manual 1 D
EM1.aspx
DEM1
DEM1 User Guide (Shell Wiki page)
https://eu001sp.shell.com/sites/AAAAA8432/CF/Web/Design Engineering Manual 1 D
EM1.aspx
Shell Wiki
Wells Manuals
http://sww.shell.com/pt/business units/wells/technical assurance standard
s/TA.html
INTERNATIONAL STANDARDS
Rules for the structure and drafting of International Standards –
Sixth Edition
9.
ISO/IEC DIRECTIVES
PART 2
BIBLIOGRAPHY
NOTE:
The following document is for information only and does not form an integral part of this DEP.
INTERNATIONAL STANDARDS
Standardization and related activities - General vocabulary
ISO/IEC Guide 2
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
10.
DEP 00.00.00.30-Gen.
February 2017
Page 29
FIGURES
Figure 1
Transparent standards structure .................................................................................... 30
Figure 2
Phases in standard processing ...................................................................................... 30
Figure 3
Standards planning cycle ............................................................................................... 31
Figure 4a
Writing new and updating standards ............................................................................. 32
Figure 4b
Writing new and updating standards - Audit/comment/approval/issue .......................... 33
Figure 5
Maintenance of a DEP ................................................................................................... 34
Figure 5a
Maintenance of a project technical specification ........................................................... 35
Figure 5b
Procedure for withdrawal or reaffirmation of DEPs ....................................................... 36
Figure D.1
Suggested decision flow for PRS content...................................................................... 52
Figure D.2
PRS application timeline ................................................................................................ 54
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 30
Figure 1
Figure 2
(Proposal to create
or revise a DEP)
Transparent standards structure
Phases in standard processing
DEP PLANNING CYCLE
Section 3
Figure 3
WRITING NEW AND
UPDATING STANDARDS
Section 4
(Requirement for
revision identified)
Figures 4a,4b
MAINTENANCE OF
A STANDARD
Section 5
Figure 5
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 31
Figure 3
Standards planning cycle
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 32
Figure 4a
Writing new and updating standards
DEP PLANNING CYCLE
Section 3
Figure 3
Go to A in Fig 4b for
records/monitoring
Map and Compare Servco and
OU Standards
4.1
External
standard(s)
available as
a basis
DEM1 DEP?
No
Follow guidelines in
DEM1 User’s Manual
Yes
Yes
No
Select External Standard
4.1
Ext. Standard(s)
fully satisfy Group
requirements?
No
DEM1 DEP?
Yes
Follow guidelines in
DEM1 User’s Manual
No
Yes
DEM1 DEP?
Follow guidelines in
DEM1 User’s Manual
No
Prepare as “Amendments/
Supplements to Ext Std
Prepare as “Endorsement”
of External Standard
4.1
Author captures common
minimum requirements in
draft DEP
4.1
4.1
Con inue on Fig. 4b for
Audit/Comment/Approval/
Issue
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 33
Figure 4b
Writing new and updating standards - Audit/comment/approval/issue
Continued from Figure 4a Author
Drafts DEP
4.2
From Fig. 4a
Figure 4a
A
Custodian reviews draft DEP as
being minimum requirements
4.2
Feedback
1st audit by Administrator. DEP
edited
4.7
4.2
List of commentors compiled by
Author and Administrator
4.3
DEP sent on comment round by
Administrator
4.3
Comments received by
Administrator and passed to Author
4.3
Comments resolved/incorporated
by Author and new draft submitted
to Administrator (including
completed drawings)
4.4
2nd audit by Administrator. DEP
edited
4.4
DEP sent on approval round
4.5
DEP issued
4.6
MAINTENANCE OF A DEP
Section 5
Figure 5
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
Progress/expenditure control
monitoring
4.8
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 34
Figure 5
Maintenance of a DEP
WRITING NEW AND
UPDATING DEP
Section 4
Figure 4b
Application and maintenance
of Project Technical Standards
5.2
Figure 5a
Requirements for revising
a DEP
5.3
Figure 5b
Procedure for withdrawal,
deactivation or reaffirmation of DEPs
5.4
Figure 5c
DEP PLANNING CYCLE
Section 3
Figure 3
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 35
Figure 5a
Maintenance of a project technical specification
WRITING NEW AND
UPDATING DEP
Section 4
Figure 4b
DEP received by OU
5.2
Project prepares
Project Techncial Specification
5.2
Project Technical Specification
approved by project
5.2
Project applies standards
5.2
Common project
variations or
derogations/deviations
identified?
No
Yes
Requirements for revising
DEP identified
Section 5.3
Figure 5
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 36
Figure 5b
Procedure for withdrawal or reaffirmation of DEPs
Periodic review
5.3.7
Requirement
for revising DEP
WRITING NEW AND
UPDATING DEP
Yes
identified?
Section 4
Figure 4b
No
More than
5 years since last
No
No action required
edition?
Yes
DEP still
required?
Yes
No
DEM1 DEP?
Yes
Follow guidelines in
DEM1 User’s Guide
No
Withdraw DEP
Reaffirm DEP or make Inactive
5.4
5.4
Update DEP Index
5.5
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 37
APPENDIX A
A.1
STANDARD STRUCTURE OF DEP SPECIFICATION
STRUCTURE
1.
DEP Specifications shall be structured as follows:
PRELIMINARY PAGES
Title Page
Preface
Table of Contents
INTRODUCTION
Scope
Distribution, intended use and regulatory considerations
Definitions
Abbreviations (if applicable)
Action items (if applicable)
Cross-references (if applicable)
Summary of main changes (if applicable)
Comments on this DEP
Dual units
MAIN TEXT
REFERENCES (if applicable)
BIBLIOGRAPHY (if applicable)
TABLES (if applicable, and if not included in the main text or appendices)
FIGURES (if applicable, and if not included in the main text or appendices)
APPENDICES (if applicable)
A.2
PRELIMINARY PAGES
A.2.1
Title Page
The Title Page indicates the DEP type (i.e., DEP Specification), DEP title, DEP number
and DEP draft date (which will later be changed to show the DEP date of issue).
The title page also includes a standard confidentiality and copyright statement and, if
applicable, the U.S. Export Classification ECCN EAR99.
1.
DEPs that are based on an external standard shall be so identified in the title by
including the appropriate text as follows:
a. Endorsement of [Standard XYZ], or;
b. Amendments/Supplements to [Standard XYZ].
A.2.2
Preface
1.
The Preface is standard for all DEP Specifications. It shall not be changed unless
agreed by the Administrator and, if necessary, endorsed by the Shell GSI Legal
Department.
It has been carefully worded and endorsed by the ShelI GSI Legal Department.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
A.2.3
DEP 00.00.00.30-Gen.
February 2017
Page 38
Table of Contents
1.
The Table of Contents shall list sections and subsections (Heading 0, Heading 1,
Heading 2 styles).
2.
Sub-subsections should not be included in the Table of Contents.
3.
Figures should not be listed in the table of contents.
4.
Appendices should be listed as a separate table of contents under the main Table of
Contents.
A.3
INTRODUCTION
A.3.1
Scope
1.
Every DEP Specification shall contain a scope that defines the function of the DEP and
the extent and limitations of the subject addressed.
It can, therefore, be significant in the event of a dispute.
A.3.2
2.
The scope statement shall not contain requirements.
3.
DEPs that are based on an external standard shall be so identified in the Scope.
4.
DEPs that are DEM1 status shall be so identified in the Scope.
Distribution, intended use and regulatory considerations
1.
The following four standard paragraphs shall be included.
c.
The first, third and fourth paragraphs should remain unaltered.
d. The second paragraph should be altered as necessary to describe the
intended use of the particular DEP.
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 shall 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 may 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.
A.3.3
Definitions
A.3.3.1
General definitions
1.
The definitions below shall be included if the words defined are used in the DEP:
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 or
maintenance of a facility. The Principal may undertake all or part of the duties of the
Contractor.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 39
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 word should indicates a recommendation.
The word may indicates a permitted option.
2.
For DEPs that are listed in DEM1, the following additional definition shall be added:
The capitalised term “SHALL [PS]” indicates a process safety requirement.
A.3.3.2
Specific definitions
1.
Definitions of words (normally technical terms) that are used in the DEP and need
defining shall be included here.
2.
Words that are only used in a limited part of the DEP should be defined at the first
place of use rather than here.
3.
The global abbreviations directory in the requirements database should be consulted
to align abbreviations and definitions across all DEPs and aid with consistent
application of terms.
A.3.3.3
A.3.4
Abbreviations
1.
A list of abbreviations used in the text of the DEP should be provided unless they are
in common use.
2.
If the abbreviations are only used in a limited part of the DEP, they should be defined
at the first place of use rather than here.
Action items
1.
If the DEP is constructed such that a list of Action Items is considered necessary, a
description of what these mean shall be provided.
A typical clause would be:
A1 In applying this DEP, items that require information to be provided or a decision to be made
are identified by the letter 'A' and a number in the left hand margin. A summary list of all
such 'action items' is given in (xx).......
A.3.5
Cross-references
1.
If the DEP contains cross-references to other parts of the DEP, a paragraph similar the
following shall be included.
Where cross-references to other parts of this DEP are made, the referenced section or
clause number is shown in brackets ( ). Other documents referenced in this DEP are listed
in (xx).
2.
A cross-reference to a section of an appendix should indicate the appendix number
and the section number. For example, this section would be cross-referenced as
(Appendix A, A.3.5).
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
A.3.6
DEP 00.00.00.30-Gen.
February 2017
Page 40
Summary of main changes
1.
If the DEP is a revision to a previously published DEP, a summary of the major
changes should be included, unless they are so extensive as to make this impractical.
A typical example is shown below.
The intention is to describe the changes that need to be brought to the attention of
the user. It is not the intention to describe every editorial or relatively minor change.
This DEP is a revision of the DEP of the same number dated mmmm yyyy. The following
are the main, non-editorial changes.
A.3.7
Section/Clause
Change
Title Page
Changed title to "Blast Resilient and Blast Resistant Control
Buildings/Field Auxiliary Rooms".
2
Location considerations are changed and are related to side on-overpressure and duration occurrence, instead of fixed distances. This
information will determine the design requirements.
3.4
In the old section, only one blast load was indicated. In the new section
more blast load values/combinations and related possible design
examples of buildings are given. This section will give a quick reference
to structural elements of buildings.
4
This section is completely revised. Instead of equivalent static loads and
related calculations for determining the structural elements/parts of
buildings, a dynamic loading/calculation approach is adopted. All
sections are revised or put into another sequence. Typical
parts/elements are not changed, e.g., window design details and related
requirements, etc.
Comments on this DEP
1.
The following text, or similar, shall appear in every DEP:
Comments on this DEP may be submitted to the Administrator using one of the following
options:
Shell DEPs Online
(Users with access to
Shell DEPs Online)
Enter the Shell DEPs Online system at
https://www.shelldeps.com
Select a DEP and then go to the details screen for
that DEP.
Click on the “Give feedback” link, fill in the online
form and submit.
DEP Feedback System
(Users with access to
Shell Wide Web)
Enter comments directly in the DEP Feedback
System which is accessible from the Technical
Standards Portal http://sww.shell.com/standards.
Select “Submit DEP Feedback”, fill in the online form
and submit.
DEP Standard Form
(Other users)
Use DEP Standard Form 00.00.05.80-Gen. to record
feedback and email the form to the Administrator at
standards@shell.com.
Feedback that has been registered in the DEP Feedback System by using one of the above
options will be reviewed by the DEP Custodian for potential improvements to the DEP.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
A.3.8
DEP 00.00.00.30-Gen.
February 2017
Page 41
Dual units
1.
The following text, or similar, shall appear in every DEP that has been updated with
dual units. See (6.11).
This DEP contains both the International System (SI) units, as well as the corresponding
US Customary (USC) units, which are given following the SI units in brackets. When
agreed by the Principal, the indicated USC values/units may be used.
A.3.9
Non-normative text (Commentary)
1.
The following text, or similar, shall appear in every DEP:
Text shown in italic style in this DEP indicates text that is non-normative and is provided as
explanation or background information only.
Non-normative text is normally indented slightly to the right of the relevant DEP clause.
A.4
MAIN TEXT
1.
See (Appendix C) for editorial and typographical requirements.
2.
If a DEP is an amendment/supplement of an external standard, it should be
constructed so that the section numbers of the external standard are retained.
a. The DEP should be written in terms of additions to, deletions from, or
replacements of those sections.
3.
All figures, tables and equations shall have a unique number and title.
a. For amendment/supplement DEPs, the numbering shall following the format of
the external standard without conflicting with the content of the external
standard.
If the external standard has Figures 2-1 through 2-7, then the first figure in
section 2 of the DEP would be Figure 2-8.
A.5
REFERENCES
1.
The following standard text should precede the list of referenced standards:
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. The DEPs and most referenced external standards are available to Shell
staff on the SWW (Shell Wide Web) at address:
http://sww.shell.com/standards/.
A.6
BIBLIOGRAPHY
1.
The following standard note should precede the list of bibliographic references:
NOTE:
A.7
The following documents are for information only and do not form an integral
part of this DEP.
APPENDICES
1.
Appendices should be used for material which, if included in the main text, would make
the DEP less easily understood.
2.
Appendices may also apply to drawings and to material (e.g., figures, tables) that are
referenced in different parts of the main text.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 42
APPENDIX B
B.1
STANDARD STRUCTURE OF DEP INFORMATIVES
STRUCTURE
1.
DEP Informatives shall be structured as follows:
PRELIMINARY PAGES
Title Page
Preface
Table of Contents
INTRODUCTION TO INFORMATIVE
INFORMATION PERTAINING TO COMPANION DEP
1.3 Definitions
REFERENCES (only if needed)
BIBLIOGRAPHY (only if needed)
APPENDICES (if needed)
2.
The numbering of the companion DEP Specification shall be followed.
3.
For DEM1 DEPs, the Process Safety Summary Table shall be included in 1.3
Definitions.
4.
If the Informative is making commentary on an Appendix that is in the
DEP Specification, then the placement in the structure should be under “Information
Pertaining to Companion DEP”.
B.2
PRELIMINARY PAGES
B.2.1
Title Page
B.2.2
1.
The Title Page indicates the DEP type (i.e., DEP Informative), DEP title, DEP number
and revision date.
2.
The title and number shall be the same as shown in the DEP Specification.
3.
The title page also includes a standard confidentiality and copyright statement and, if
applicable, the ECCN EAR99 classification but not the DEM1 label.
Preface
1.
The Preface is standard for all DEP Informatives. It shall not be changed unless
agreed by the Administrator and, if necessary, endorsed by the Shell GSI Legal
Department.
It has been carefully worded and endorsed by the Shell GSI Legal Department.
B.2.3
Table of Contents
1.
The Table of Contents shall list sections and subsections.
2.
Sub-subsections should not be included in the table of contents since this would cause
it to be too long.
3.
Figures should not be listed in the Table of Contents.
4.
Appendices should be listed in the Table of Contents.
5.
Annexes or Appendices that are additional to Annexes or Appendices in the
DEP Specification shall be listed in a separate table of contents under the main Table
of Contents.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
B.3
DEP 00.00.00.30-Gen.
February 2017
Page 43
INTRODUCTION TO INFORMATIVE
1.
The introduction section shall include the text shown below.
INTRODUCTION TO INFORMATIVE
This DEP Informative is the companion to DEP XX.XX.XX.XX-Gen., and provides the
rationale for certain requirements and recommendations in that document.
For clarity, the section and paragraph numbering of DEP XX.XX.XX.XX-Gen. is used in this
document. Where there are no comments regarding a particular paragraph or section,
these have been omitted.
The information in this document is maintained by the Custodian responsible for the DEP,
primarily for the following purposes:
• Documentation of the reason or background for certain requirements, particularly where
those requirements have raised questions in the past;
•
Inclusion of the PS Tables, where applicable, which explain the reasons for certain
requirements designated as process safety related;
This information can be used as guidance when considering deviation requests.
This is a revision of the DEP Informative of the same number dated mmmm yyyy.
2.
A statement summarizing the external standards strategy for the DEP should also be
included in the Introduction.
a. This should include the longer term strategy to influence an identified external
standard and make the DEP based on the external standard, when applicable.
B.4
INFORMATION PERTAINING TO COMPANION DEP
1.
In this part of the Informative, the section numbering of the companion DEP
Specification shall be followed.
2.
If the companion DEP Specification is listed as DEM1, then a process safety table
shall be inserted under 1.3 Definitions to indicate the reasons why certain
requirements have been identified as being process safety requirements.
3.
If the companion DEP Specification includes dual units, the Informative should include
the following text, when appropriate:
The conversion of values from the SI system to the corresponding USC values has been
made using an adaptive process (i.e., not an exact mathematical conversion). In some
cases, size substitutions have been made in order to align with available products or
methods customarily used in the US.
B.5
APPENDICES
1.
If it is desired to add extensive information that is not specifically covered in the
companion DEP Specification, this should be included in Appendices or Annexes that
are placed at the end.
a. If the DEP Specification has Appendices, then the DEP Informative should use
Annexes for information not covered in the Specification.
b. If the DEP Specification has Annexes, then the DEP Informative should use
Appendices for information not covered in the Specification.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
B.5
DEP 00.00.00.30-Gen.
February 2017
Page 44
FIGURES, TABLES AND EQUATIONS
1. All figures, tables and equations shall have a unique number and title using a numbering
format different from the DEP Specification.
To avoid there being a “Figure 1” in both Specification and Informative, one uses
the format Figure 1,2,3, the other uses the format Figure 2.1, Figure 2.2
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 45
APPENDIX C
C.1
EDITORIAL AND TYPOGRAPHICAL REQUIREMENTS
GENERAL
This Appendix describes the editorial and typographical requirements for a DEP.
1.
C.2
NUMBERING OF SECTIONS
1.
2.
C.3
All DEPs shall be written in the requirements database directly or using a word
processing or spreadsheet template provided by the Administrator.
Section numbering and further divisions of the section shall be as follows:
Sections
1., 2., 3., etc.
Subsections
1.1, 1.2, 1.3, etc.
Sub-subsections
1.1.1, 1.1.2, etc.
Sub-sub-subsections
1.1.1.1, 1.1.1.2, 1.1.1.3, etc.
If the DEP is an amendment/supplement of an external standard, it shall observe the
same numbering style of the external standard within the portion of the DEP that is
amending and supplementing the external standard.
TYPE STYLE FOR SECTION HEADINGS
1.
The type style for headings should be as follows:
Style
Sections
Font type
Heading 0,
Heading 1
Sections 1., 2., 3., etc.
IN CAPITALS AND IN BOLD TYPE
Heading 2
Subsections 1.1, 1.2, 1.3, etc.
IN CAPITALS AND NOT IN BOLD TYPE
Heading 3
Sub-subsections 1.1.1, 1.1.2, etc.
In lower case and in bold type
Heading 4
Sub-sub-subsections 1.1.1.1, etc.
In lower case and not in bold type
It might be necessary to deviate from the above formats to follow an external standard
that uses a different format.
C.4
TYPOGRAPHICAL LAYOUT
C.4.1
Margins
C.4.2
1.
For the purposes of this section, the left margin shall be considered as the datum point
(zero mm) and set to give a print position of 26 mm.
2.
The section number shall be placed on the left margin.
3.
The right margin shall be set at print position 26 mm and 158 mm from the left margin.
Paragraphs
1.
Starting with Section 2, within the above sections/sub-sections (C.2), each clause shall
be identified by a number.
This is intended to make all instructions (requirements, recommendations and
permissive statements) clearly identified and for ease of reference. This is not done
in the Introduction (Section 1) since the technical requirements are normally after
the Introduction section.
C.4.3
Comments
1.
Text that is not normative, but is providing explanation or background information that
is deemed necessary in the Specification should be shown in italicized text as
paragraphs separate from the numbered clauses.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
C.4.4
DEP 00.00.00.30-Gen.
February 2017
Page 46
Notes added to text
1.
If a note is required, it should immediately follow the relevant Figure or Table.
2.
Notes should be introduced by the word "NOTE(S):" in capital letters, point size 8, not
in bold type.
3.
If more than one note appertains to a subject, the notes should be numbered.
4.
Notes should not include shall/should/may instructions.
An example is shown below.
NOTES:
1. The font of the note should be point size 8.
2. Notes should be placed below the pertinent paragraph.
3. For numbered Notes, No. 1 note should use the style: “Note 1 of more”.
4. For subsequent numbered notes, the notes style should be: “Note 2 etc.”
C.4.5
Action item indication
1
If action items are to be included they shall be indicated at the beginning of the line.
2.
Bullets or different letters may be used to indicate the type of action, e.g., S = Specify,
A = Approve.
3.
Action items may be numbered sequentially if it is intended to make a summary list of
them in the DEP.
Use the style named “Action Item” for an Action Item paragraph.
C.4.6
Page numbering
1.
C.4.7
Headers
1.
C.4.8
Page numbering shall start on the page containing the Preface (page 2).
Headers shall contain the DEP number, date of issue, and page number and, if
applicable, the ECCN EAR99 classification.
Tables, figures and illustrations
1.
All tables, figures and illustrations shall be referenced in the text.
a. References should be made by use of the number without the description,
e.g., "… in accordance with Figure xx".
4.
The location should be decided by the requirement for ease of reference and
readability.
5.
The Author should formulate the numbering of the tables and figures to suit the
subject.
The methods of numbering can vary from a straight sequential number to a
number which takes its root from the section number, as is the case in some
external standards.
C.4.9
C.4.10
Drawings
1.
Standard Drawings should not be included in a DEP.
2.
If reference is made to Standard Drawings, their number and title shall be included in
the list of referenced standards.
3.
For other drawings to be included in a DEP, the electronic file format should be as
specified by the Administrator.
Formulae
1.
Formulae should use simple forms of notation and layout to achieve maximum clarity
to assist the reader in comprehension.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
C.4.11
DEP 00.00.00.30-Gen.
February 2017
Page 47
Revision marking
1.
Text or sections that have changed since the previous issue of a DEP should not be
marked (e.g., by a vertical line in the margin).
Most DEP revisions are comprehensive and revision marking would be so
extensive as to cause confusion. However, pdf versions of the DEP are available
for downloading from Shell DEPs Online with revision marking (comparing two
individual DEP versions).
2.
For the version of a DEP going on comment round (4.3.2) the DEP may include
revision marks if desired by the Author or Administrator.
C.5.
GRAMMATICAL STYLE
C.5.1
Capitalisation
C.5.2
C.5.3
1.
Other than for proper nouns, capitals should be avoided except where desired in the
titles, headings, tables and figures.
2.
A word or term which has been uniquely defined in the DEP may commence with a
capital letter if thought useful to the user and if by so doing the text remains readable.
Hyphenation
1.
All aspects of the DEP name shall always remain on one line, which means inserting a
“nonbreaking space” and “nonbreaking hyphen” where required, e.g.,
DEP 00.00.00.30-Gen.
2.
There are no fixed rules for hyphenation in English. Hyphens should be used only if
there is otherwise a danger of misinterpretation.
Word division
1.
C.5.4
Single words shall not be broken (hyphenated) at the end of a line.
Spelling
1.
For amendment/supplement DEPs, the spelling of the source external standard shall
be used.
2.
British (rather than American) spelling should be used.
3.
Where alternative spelling of words with the same meaning is possible, one spelling
should be used consistently within a DEP.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
APPENDIX D
D.1
DEP 00.00.00.30-Gen.
February 2017
Page 48
MANAGEMENT SYSTEM FOR PORTFOLIO REQUIREMENTS
SPECIFICATIONS
INTRODUCTION
The framework described in this appendix applies to a limited number of “stand alone”
technical standards that apply to a specific business portfolio. These standards, called
Portfolio Requirements Specifications (PRS), may be selected and applied by projects
within the defined boundary conditions of the PRS. The PRS is a streamlined set of
requirements that have been pre-selected and rationalized from the applicable DEPs.
PRS standards are administered by the Technical Standards Team and distributed in
the Shell DEPs Online system. They will be created only when there is sufficient
business justification and support to develop and maintain them compliant to DEM1 and
agreement by the Manager Technical Standards to be administered as part of the global
technical standards.
D.2
BACKGROUND
Experience has shown that the application of the DEPs in non-core businesses may
result in extensive re-engineering in order to translate DEP requirements (including
DEM1 mandatory process safety requirements) into a set of requirements that are fit for
purpose in the context of the business philosophy and project premises. In some case,
there are multiple projects to be executed within a business that each requires similar
re-engineering of technical requirements. For example, projects being executed within
the Upstream Unconventionals business portfolio.
In order to improve engineering efficiency, PRS standards may be developed (where
justified and approved) for use within a defined business portfolio in lieu of the DEPs.
Each PRS standard has clearly defined boundary conditions for application. Aspects of
the project that fall outside of the boundary conditions must establish the applicable
technical requirements based on the applicable industry standards and DEP
requirements.
A PRS may be viewed as a collection of technical requirements that have been preselected from the DEPs and fully rationalized for application within a defined business
portfolio. During the development of a PRS, mandatory process safety (DEM1)
requirements in the base DEPs are assessed and where applicable to the business
portfolio, are established in the PRS standard. Once created, each PRS will be
maintained on an annual basis, incorporating new learnings that are added to the Group
DEPs and assuring that projects applying the PRS remain DEM1 compliant.
PRS will be listed in the annual DEM1 update as having DEM1 status within the
boundaries of their applicability.
The maintenance requirements are significant in order to keep each PRS updated as
changes occur in the base DEPs and to assure that projects applying the PRS are
DEM1 compliant. Therefore, it is a basic requirement that the business justification must
be compelling and founded on the principal that the existing DEPs are not suitable for
application during project execution following the normal project work processes in the
ORS (selection and application of technical standards).
Projects applying the PRS are compliant to the version of DEM1 that the PRS is based
on. The project might, however, be required to apply additional DEM1 requirements
when a subsequent version of the DEPs is issued or when aspects of the project fall
outside of the defined boundary conditions of the PRS.
D.3
GENERAL PRINCIPLES
1.
A PRS shall be developed only when there is agreement at the EVP level between the
business and PTE that there is a compelling case of justification and support.
A PRS will not be created solely to minimize engineering effort required to apply
DEPs in projects.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 49
2.
For each PRS, it shall be clearly identified which DEP version it is based on and the
specific DEPs that have been selected as the technical basis.
3.
Each PRS shall have a scope that clearly defines the boundary conditions for
application of the PRS in projects.
a. When certain aspects of project work fall outside of the defined boundary
conditions, a management of change process shall be applied within the
project, in order to establish the necessary further requirements.
4.
During the development of a PRS, the mandatory process safety requirements in the
identified base DEPs shall be individually assessed for applicability.
a. When determined to be applicable within the scope of the PRS as barriers to
prevent RAM red or 5A/5B process safety incidents, they shall be established
as mandatory process safety requirements in the PRS document.
b. Documentation of this assessment shall be maintained in the Informative.
c.
5.
Evidence of the completed assessment shall be recorded by the business as
an approved derogation in the DEM1 derogation register.
For each PRS, the business shall enter an annual derogation additional to
st
(D.3, Item 4) in the DEM1 Derogation Register before July 1 as evidence that a
review has occurred and to assure that the PRS remains DEM1 compliant.
a. New learnings that have been introduced into the DEPs, including any
changes to DEM1 mandatory process safety requirements, shall be reviewed
and a determination made whether to incorporate changes into the PRS.
D.4
6.
Projects that have not yet passed DG-3 in the ORS on July 1st shall assure that they
are compliant to the latest version of DEM1.
7.
PRS documents shall be administered by the Technical Standards Team with the
same level of support as the DEPs and made available for project use through the
Shell DEPs Online system.
RESPONSIBILITIES
1.
The business shall provide justification and resources to develop a new PRS, including
the following aspects:
a. A sufficient business case made to the Manager Technical Standards.
b. Coordination of the development effort, including TA1 selection and
involvement.
c.
Defining the scope and integration with the business framework (e.g. business
philosophies and risk hazard registers).
d. Assuring the PRS is DEM1 compliant, identifying process safety mandatory
requirements that are barriers to prevent RAM red or 5A/5B risks and that
have been fully assessed against the existing DEM1 process safety
requirements.
2.
The business shall assure that the PRS is maintained compliant to DEM1 including the
following:
a. Assign a Custodian (typically TA1) to each PRS as the accountable person.
b. Annual gap assessment of changes to the base DEPs (including DEM1
changes) and annual filing of an approved derogation in the DEM1 Derogation
Register.
c.
3.
Updating of the PRS to incorporate changes that have occurred in the base
DEPs as well as other learnings.
Each project shall be responsible for applying the PRS within the boundary conditions
defined in the PRS and for assuring that the project is executed compliant to DEM1.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
4.
DEP 00.00.00.30-Gen.
February 2017
Page 50
The Standards Team shall administer the PRS, including the following:
a. Incorporate the PRS in the annual standards plan,
b. Define document structure and quality requirements.
c.
Provide document editing and audit functions.
d. Facilitate DEM1 Team approval.
e. Coordinate commenting and approval of the finalized document.
f.
Maintain documented evidence of the development phase and subsequent
maintenance revision work.
g. Publish in Shell DEPs Online.
h. Collect feedback via the DEP Feedback System (provide IT system).
i.
Maintain the DEM1 derogation register (provide IT system).
j.
Maintain the mapping to other relevant DEPs (in DEP IM Tool).
k.
Provide an annual notification of changes to the mapped base DEPs (will
notify Custodian).
l.
Support annual DEM1 derogation (lead by the Business).
m. Support maintenance/revision cycle (lead by the Business).
D.5
APPROVAL OF NEW PRS
1.
A business case for developing and maintaining a PRS shall be demonstrated.
a. The business case shall be based on the principle that the existing DEPs
cannot be efficiently applied to a defined portfolio of projects using the normal
work processes in the ORS.
Justification is typically based on the technical requirements in the DEPs having
been developed for application in a substantially different business context. In order
to apply the DEP requirements, extensive re-engineering is required for multiple
projects.
2.
The proposal to develop a new PRS should:
a. Identify which base DEPs are applicable.
b. Demonstrate why the DEPs as currently written are not fit for purpose to the
business portfolio.
c.
Demonstrate a business need to execute multiple projects within the defined
business portfolio.
d. Propose how the PRS will be developed, including resourcing.
e. Commit to maintain the PRS in the future.
3.
A proposal shall be made to the Manager Technical Standards Team with each
request to develop a new PRS.
a. The business case shall be supported by the Manager of Technical Standards
and agreed at the EVP level by the business and PTE.
D.6
DEVELOPING A NEW PRS
1.
The business shall identify a lead resource to coordinate the development activities
with the Technical Standards Team.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
2.
DEP 00.00.00.30-Gen.
February 2017
Page 51
A resourcing plan and implementation plan shall be established in coordination with
the Standards Team, including the following:
a. A workshop to align the TA1s with the business on the scope, business
philosophies and risks.
b. Workshop(s) dedicated for TA1 assessment of the base DEP requirements
and development of the technical content of the PRS.
It is recommended that workshops be held involving the affected discipline
TA1s in order to align the disciplines on the risks associated with the
business and to consolidate requirements that are in different base DEPs.
c.
Documentation requirements, including the PRS Informative content.
d. Version control.
e. Quality auditing requirements.
f.
A process for review and comment by stakeholders.
g. Approvals by the TA1s and by the business.
h. An approved derogation entered in the DEM1 Derogation System.
i.
Publication for use in Shell DEPs Online.
3.
Discipline TA1s shall be identified and engaged to establish the technical content of
the PRS.
4.
The base DEPs that are applicable to the scope of the PRS shall be identified
(documented in the PRS Informative).
a. A mapping to these base DEPs shall be maintained in the DEP IM Tool.
The mapping is based on a selection of the standards that apply to the scope of the
portfolio projects. This basis for selection of standards is used in each project when
the PRS is applied.
5.
The responsible TA1s shall assure that mandatory process safety requirements are
incorporated into the PRS that are equivalent to the DEM1 mandatory process safety
requirements in the base DEPs in terms of risk reduction.
a. Documentation of this analysis shall be maintained in the PRS Informative.
b. Mandatory process safety requirements that are SHALL [PS] statements in the
base DEPs may be:
i.
adopted as written;
ii.
retained as SHALL [PS] statements that are modified;
iii.
demoted to a “shall” requirement based on RAM rating;
iv.
eliminated due to consolidation of requirements, or;
v.
determined to be not applicable in the business.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 52
Figure D.1
6.
Suggested decision flow for PRS content
A draft of the PRS Specification and companion Informative shall be prepared for
review.
a. A comment round may be administered by the Standards Team.
b. The affected disciplines as well as business stakeholders shall review the draft
and provide input prior to preparation of a final draft.
c.
A comment register should be maintained to record the comments as well as
the decision on each comment (recorded by the TA1).
7.
During the comment period, the DEM1 Team shall review the mandatory process
safety requirements.
8.
After all comments have been addressed and incorporated, a final draft of the PRS
shall be prepared for edit/audit and subsequent approval.
9.
After final audit by the Administrator, the finalized PRS shall be approved by the
business Custodian before publication in the Shell DEPs Online system.
10. Assurance that the mandatory process safety requirements in the PRS are compliant
to DEM1 shall be provided by entering an approved derogation in the DEM1
derogation register prior to issuing the PRS.
It is recommended to file one derogation per discipline.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
D.7
DEP 00.00.00.30-Gen.
February 2017
Page 53
ANNUAL DEM1 ASSURANCE OF THE PRS
1.
On an annual basis, following the publication of the DEPs in February, the Standards
Team shall notify the Custodian of any base DEPs that have been revised.
The business is responsible (between February and July) for assessing the
changes in the base DEPs, including mandatory process safety requirements,
and determining if any changes or updates are required in the PRS.
2.
st
Prior to July 1 of each year, an approved derogation shall be entered in the DEM1
Derogation Register providing assurance that the PRS remains compliant to the
current version of DEM1.
Because of the time required to develop the Specification, it is expected that DEP
revisions will be issued in February each year that supersede the DEPs that have
been used as the technical basis for developing the Specification being issued at
the same time. These changes in base DEPs may include changes in mandatory
process safety requirements (DEM1). When a revision to the PRS is required, the
revision will not be issued until February of the following year. The purpose of the
annual assurance process is to assure that changes in the base DEPs are
evaluated and projects that are using the stand-alone Specification remain DEM1
compliant with respect to these changes.
3.
st
Projects that pass DG3 prior to July 1
consideration of changes in the base DEPs.
may apply the PRS without further
A gap assessment is recommended but is not mandatory.
4.
If there are any changes in DEM1 requirements in the base DEPs that are applicable
to the portfolio projects, these are covered by the annual derogation. If there are no
changes in DEM1 requirements applicable to the portfolio projects, the derogation is
still filed as evidence of the review process.
In the event that there are risks identified that require mitigation in projects as new
engineering requirements that are not in the PRS, these will need to be
implemented by the business using management of change procedures.
D.8
MAINTENANCE
As an outcome of the annual assurance process, a revision to the PRS could be
initiated. This is a judgement based on the extent of change.
A revision to the PRS is initiated by the businesses with a request made to the
Standards Team to include the PRS in the annual standards plan.
The resources required to work on a revision to the PRS (including commitment of the
discipline TA1s and budget) are the responsibility of the business.
The revision process will be administered by the Standards Team.
A resourcing plan and detailed implementation plan should be established, including key
elements listed in (D.3).
1.
The update of the PRS shall be included in the annual standards plan as reflected in
the IM Tool.
2.
A maximum interval of 3 years shall be applied between PRS updates.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11
ECCN EAR99
DEP 00.00.00.30-Gen.
February 2017
Page 54
Figure D.2
Feb 2015
DEPs
PRS
1st July 2015
v39
v1
Updates from DEM1
changes from v38 to v39
1st July 2015
v2
Derogation
to v39
Updates from DEM1
changes from v39 to v40
Derogation
per business
portfolio
to v39
Pre-DG3
D.9
Feb 2016
v40
Derogation
to v38
Portfolio
Project
PRS application timeline
PostDG3
Derogation
per business
portfolio
to v40
Gap Assessment
MINIMUM DOCUMENTATION REQUIREMENTS
1.
In the PRS (Specification) the boundary conditions of the PRS for application in
projects shall be clearly defined.
This could be accomplished by referencing business philosophies or other
documents that are version controlled.
2.
The Informative document shall include the following:
a. The selection of standards that the PRS is based on. This includes the list of
base DEPs that are mapped to the PRS.
b. Detailed assessment of each DEM1 mandatory process safety requirement in
the base DEPs and the outcome in terms of adoption into the PRS.
i.
c.
This assessment shall include the RAM rating of each DEM1
requirement in the base DEPs (as it relates to the business
environment) and the basis for the outcome.
A process safety table summarizing both the risk and the RAM rating for each
mandatory process safety requirement in the PRS.
d. Definition of business controls to support the assessment (e.g., Hazard
register, operational philosophies) and of the process for managing change to
those controls.
3.
The DEP IM Tool shall include the following:
a. The current status of each PRS document (reserved, active, withdrawn).
b. The base DEPs that mapped to the PRS (D.9, Item 2.a)
c.
Inclusion of the PRS in the standards operating plan.
d. The Custodian of the PRS who is accountable for the technical content and
annual maintenance.
This document has been supplied under license by Shell to:
UOP Honeywell ted.fuger@honeywell.com 19/01/2018 05:36:11