Section 1 — Index and Use

Deviations to IPE Engineering Practices

IPE Engineering Practice IPE-EP-1-1-3

Document number: IPE-EP-1-1-3 · Section: 1 — Index and Use

SCOPE

This Practice covers the mandatory requirements and procedures for deviating from an existing

IPE Engineering Practice.

Any Deviation from this Practice must be approved by the procedure provided in this Practice.
A revision bar indicates changes to the latest revision of this Practice. If the latest revision has undergone a major rewrite, then revision bars will not be used and a statement shall be made in the Scope to that regard.
An asterisk (*) indicates that a decision, approval, or additional information may be required by the Owner, Owner’s Engineer, Inspection Authority, or Purchaser (per EP 1–1–1).

2.0 REFERENCES

The latest edition of the following standards and publications are referred to herein.

STANDARDS AND PUBLICATIONS

DEFINITIONS

Deviation – Any site specific change, modification, addition or deletion to specific requirements or the application and use of a IPE Practice is deemed a deviation.
ES (Engineering Services) – IPE engineering group or third party Contractor responsible for overall coordination of the EPs.
ES EP Coordinator – Person within Engineering Services (ES) who is responsible for the overall development and revision of Practices. Also responsible for coordinating the review and implementation of revision requests.
Inspection Authority – An individual appointed or approved by the Owner who is responsible for the Owner’s quality assurance program and has the knowledge and training to resolve issues relating to inspection and quality.
Modification(s) – Revision(s), addition(s), deletion(s), or reaffirmation(s) to IPE Engineering Practices that are balloted by the EP Technical Committee.
Owner – IPE .
Owner’s Engineer – A IPE appointed engineer.
Project Manager – Assigned person having the ultimate responsibility for a specific project. This will usually be a major project having its own unique organization autonomous from the established company's organization.

Project EP Coordinator – Assigned person from the major project organization who coordinates project EP Deviations.
Purchaser – The party placing a direct purchase order. The Purchaser is the Owner’s designated representative.
Revisions – Modifications to an existing IPE Engineering Practice.
Section 1.0 Committee Member – A management level Technical Committee member appointed by management whose duties are outlined in Section 4.0 of EP 1–1–2.
Plant EP Coordinator – Assigned person that coordinates the EP’s for the IPE Plant

whose duties are outlined in Section 4.0 of EP 1–1–2.

EP Technical Committee – Committee consisting of 15 designated IPE representatives, one responsible for each specific EP section, whose duties are outlined in Section 4.0 of this Practice.
EP’s –IPE Engineering Practices.
EP Website – An internet website managed by Engineering Services, where current and archived revisions of the EPs and Deviations can be found. The URL of the website is TBD

DEVIATIONS

Deviations may apply only to the specific piece of equipment or the specific project for which they are approved and may have limited applicability within the IPE Plant.
There are three different types of Deviations:
Site wide; the Deviation is approved for site–wide application.
Project specific; the Deviation is only approved for use in connection with a specific project.
Equipment specific; the Deviation is only approved on a one–time basis for a particular equipment item or group of equipment.
There are two Deviation approval procedures:
The basic Deviation procedure shall be followed according to paragraph 4.4.
The Project Manager may elect to follow the alternate procedure in paragraph 4.5.
Basic Deviation Procedure (Plant):
The originator of a Deviation request shall fill in Form A and attach all relevant documentation. The Deviation request shall then be forwarded to the Plant EP Coordinator, who will in turn forward the Deviation request to the applicable Technical Committee Member at the site.
The Technical Committee member shall review the Deviation request and approve the type of Deviation being requested per paragraph 4.2. They should also consult with Engineering Services or other knowledgeable resources, such as Inspection Authorities, on an as needed basis. The Technical Committee Member shall approve or reject the Deviation request. Once the request is approved by the Technical Committee Member, they shall forward the request to the MOC Committee for approval.
Upon MOC Committee approval, the Technical Committee member shall for the Deviation request to the Section 1.0 Committee member for final approval.

The approved Deviation shall be returned to the Plant EP Coordinator, who shall provide copies of the Deviation to the originator and the Technical Committee member. The Plant EP Coordinator shall forward a copy of all site–wide or project specific Deviations to the ES EP Coordinator and the project file.
The Section 1.0 Committee member can appoint designees to be responsible for final Deviation approval by providing written notification to the Plant EP Coordinator.
The ES EP Coordinator shall post all site–wide and project specific Deviations on the EP website.
Alternative Deviation Procedure (Major Projects):
The originator of a Deviation request shall fill in Form A and attach all relevant documentation. The Deviation request shall then be forwarded to the Project EP Coordinator, who will in turn forward the Deviation request to the applicable Technical Committee member.
The Technical Committee member shall review the Deviation request and approve the type of Deviation being requested per paragraph 4.2. They should also consult with Engineering Services or knowledgeable resources, on an as needed basis. The Technical Committee Chairman shall approve or reject the Deviation request. Once the request is approved by the Technical Committee member, they shall forward the request to the MOC Committee for approval.
Upon MOC Committee approval, the Technical Committee member shall forward the Deviation request to the Section 1.0 Committee member for final approval.
The approved Deviation shall be returned to the Project EP Coordinator, who shall provide copies of the Deviation to the originator, Technical Committee member, the Project Manager, the Plant EP Coordinator, the project files and the ES EP Coordinator.
The Project Manager can appoint designees to be responsible for final Deviation approval by providing written notification to the Section 1.0 Committee Member.
The ES EP Coordinator shall post all site–wide and project specific Deviations on the EP website.
Once the Deviation is approved, it can be used immediately. The ES EP Coordinator shall update the Deviation electronic collection on the EP website.
The ES EP Coordinator shall void Deviations from the Deviation Collection on the EP website once they become void.
All site–wide and project specific Deviations should be reviewed to determine if a revision/modification to the applicable EP should be made. Anyone can initiate a revision/modification to a EP in accordance with the procedures provided in EP1–1–2.

FORMS

FORM A

DEVIATION REQUEST FORM	DEVIATION REQUEST FORM	DEVIATION REQUEST FORM	DEVIATION REQUEST FORM	DEVIATION REQUEST FORM
SITE:	SITE:	SITE:	SITE:	SITE:
FROM:	FROM:	FROM:	DATE:	DATE:
ORIGINATOR	ORIGINATOR	ORIGINATOR
TYPE OF DEVIATION	SITE WIDE	PROJECT SPECIFIC	PROJECT SPECIFIC	EQUIPMENT SPECIFIC
PROJECT/JOB TITLE:	PROJECT/JOB TITLE:	PROJECT/JOB TITLE:	PROJECT/JOB TITLE:	PROJECT/JOB TITLE:
EP NO.	EP NO.	EP NO.	REV.	REV.
EP TITLE:	EP TITLE:	EP TITLE:
TWO ATTACHMENTS ARE REQUIRED:	TWO ATTACHMENTS ARE REQUIRED:	TWO ATTACHMENTS ARE REQUIRED:	TWO ATTACHMENTS ARE REQUIRED:	TWO ATTACHMENTS ARE REQUIRED:
ATTACHMENT 1 SHALL LIST THE ORIGINAL PARAGRAPHS MODIFIED	ATTACHMENT 1 SHALL LIST THE ORIGINAL PARAGRAPHS MODIFIED	ATTACHMENT 1 SHALL LIST THE ORIGINAL PARAGRAPHS MODIFIED	ATTACHMENT 1 SHALL LIST THE ORIGINAL PARAGRAPHS MODIFIED	ATTACHMENT 1 SHALL LIST THE ORIGINAL PARAGRAPHS MODIFIED
ATTACHMENT 2 SHALL INCLUDE THE SUGGESTED ACTION AND JUSTIFICATION.	ATTACHMENT 2 SHALL INCLUDE THE SUGGESTED ACTION AND JUSTIFICATION.	ATTACHMENT 2 SHALL INCLUDE THE SUGGESTED ACTION AND JUSTIFICATION.	ATTACHMENT 2 SHALL INCLUDE THE SUGGESTED ACTION AND JUSTIFICATION.	ATTACHMENT 2 SHALL INCLUDE THE SUGGESTED ACTION AND JUSTIFICATION.

APPROVALS:	APPROVALS:	APPROVALS:	APPROVALS:	APPROVALS:
TECHNICAL COMMITTEE MEMBER	TECHNICAL COMMITTEE MEMBER	TECHNICAL COMMITTEE MEMBER	TECHNICAL COMMITTEE MEMBER	TECHNICAL COMMITTEE MEMBER

SECTION 1.0 COMMITTEE MEMBER	SECTION 1.0 COMMITTEE MEMBER	SECTION 1.0 COMMITTEE MEMBER	SECTION 1.0 COMMITTEE MEMBER	SECTION 1.0 COMMITTEE MEMBER
CC: TECHNICAL COMMITTEE MEMBER	CC: TECHNICAL COMMITTEE MEMBER	CC: TECHNICAL COMMITTEE MEMBER	CC: TECHNICAL COMMITTEE MEMBER	CC: TECHNICAL COMMITTEE MEMBER
CC: ORIGINATOR	CC: ORIGINATOR	CC: ORIGINATOR	CC: ORIGINATOR	CC: ORIGINATOR
ORIG: PROJECT FILE	ORIG: PROJECT FILE	ORIG: PROJECT FILE	ORIG: PROJECT FILE	ORIG: PROJECT FILE

© 2026 Inflection Point Engineering, LLC. All rights reserved. The content of this page — including calculation methods, reference data, written analysis, interactive tools, and source code — is the intellectual property of Inflection Point Engineering, LLC and is protected under applicable copyright, trademark, and trade secret laws. Unauthorized reproduction, redistribution, modification, or derivative use in whole or in part is prohibited without prior written consent.

Disclaimer. This material is provided for informational and educational purposes only and does not constitute professional engineering advice. Calculations, reference data, and methodologies are based on published standards and accepted engineering practice but are not a substitute for engineering judgment, site-specific analysis, or review by a licensed Professional Engineer. Inflection Point Engineering, LLC makes no warranties, express or implied, regarding the accuracy, completeness, or fitness for a particular purpose of any content presented here, and shall not be liable for any direct, indirect, incidental, or consequential damages arising from its use. Users assume all risk associated with applying this content to real-world design, operations, or decisions.