Shell Dep Standards -
Shell DEPs (Design and Engineering Practices) are a comprehensive set of technical standards used by Shell and its partners to ensure consistency, safety, and efficiency in the design, construction, and operation of oil, gas, and chemical facilities. These standards bridge the gap between broad international codes and the specific operational requirements of a global energy company, covering everything from materials and welding to instrumentation and safety systems. Key Components of Shell DEP Standards
Shell's technical framework is divided into several specialized categories to maintain high engineering rigor:
Design and Engineering Practices (DEPs): The core guidelines that specify technical requirements for projects and operations.
MESC (Material and Equipment Standards and Code): A proprietary system for material identification and coding, facilitating global procurement and inventory management.
Standard Drawings: Reusable, pre-engineered technical drawings for common components like flanges, piping supports, and vessel internals.
Technical Specifications: Detailed documents outlining requirements for specific equipment, such as analysers or sample conditioning systems. Core Disciplines Covered
The DEPs are exhaustive, spanning nearly every engineering discipline required for large-scale energy infrastructure:
Mechanical & Piping: Standards for welding, piping design, and metallic materials.
Instrumentation & Control: Requirements for control systems, analyzers, and electronic equipment.
Safety & Environment: Guidelines for fire protection, insulation, and onshore/offshore coatings.
Specialized Operations: Standards for diving operations, offshore structures, and subsea integrity. Access and Distribution Shell DEP Standards Overview - Underwater Diving - Scribd
Technical Overview: Shell Design and Engineering Practices (DEPs) shell dep standards
Shell Design and Engineering Practices (DEPs) are the definitive technical standards used by Shell Global Solutions and its partners to ensure safety, reliability, and efficiency across the lifecycle of oil, gas, and chemical assets. These standards consolidate decades of operational experience into a structured framework for design, construction, and maintenance. 1. Purpose and Core Objectives
The primary goal of Shell DEPs is to standardize "good design and engineering practice" globally to achieve technical and economic benefits.
Safety & Risk Mitigation: Establishing rigorous requirements for high-risk operations, such as lifting and hoisting in Deep Water environments (e.g., Gulf of Mexico).
Operational Excellence: Reflecting proven views on the design and maintenance of processing units based on Shell's global experience.
International Alignment: DEPs often reference or amend international standards (like API or ASME) to tailor them to Shell’s specific safety and quality thresholds. 2. Standard Taxonomy and Disciplines
Shell DEPs cover a wide range of engineering disciplines, categorized by functional areas:
Piping & Mechanical: Detailed classes for Refining and Chemicals, general piping requirements, and specific specifications for valves, flanges, and fittings.
Materials & Welding: Specifications for Positive Material Identification (PMI), oxidation of stainless steel, and prevention of brittle fracture.
Instrumentation & Control: Standards for automation, telecommunications, and safety-critical instrumentation.
Civil & Structural: Requirements for facilities, onshore/offshore coatings, and thermal insulation.
Process Engineering: Standards for specialized equipment like steam jet vacuum ejectors. 3. Key Components of the DEP Ecosystem Shell DEPs (Design and Engineering Practices) are a
Beyond the core DEP documents, the standard ecosystem includes several supplementary tools:
Standard Drawings: Blueprints for standardized components like compressor designs and piping fittings.
MESC (Material and Equipment Standards and Code): A coding system linked to DEPs that identifies specific pipes, valves, and equipment types.
Standard Requisitions & Forms: Templates used by contractors and manufacturers to ensure compliance during the procurement phase. 4. Implementation and Compliance
The use of DEPs is typically governed by a distribution system and specific licensing agreements.
Contractor Responsibility: Manufacturers and contractors are responsible for adhering to DEP requirements for fabrication, inspection, and performance testing.
Latest Versions: Engineering projects are required to use the latest versions (e.g., current version 39) along with all applicable amendments and attachments.
Local Flexibility: While DEPs set a global standard, they allow for flexibility where local regulations or specific site conditions require deviations. 5. Essential DEP References (Examples) Description DEP 31.38.01.11
Overview of deliverables across Process, Mechanical, and Piping DEP 31.40.20.37 Gen: Piping Class - Basis of Design DEP 33.64.10.10 Gen: Electrical Engineering Design DEP 30.10.02.11 Gen: Metallic materials - Selected standards
This guide outlines a comprehensive set of standards and best practices for shell scripting (specifically Bash/Sh) regarding dependencies. The goal is to produce scripts that are portable, robust, and easy to maintain.
3. Version Constraints (where possible)
- Document minimum versions:
awk --version,bash --version. - Avoid deprecated flags (e.g.,
egrep→grep -E).
Step 4: Manage Revisions During Long Projects
A project lasting 4 years might see two DEP revisions. The contract usually states "the DEP revision at the contract award date applies." However, Shell may mandate "roll-forward" to the latest rev if safety-critical changes exist. Establish a revision management protocol in your project quality plan. Document minimum versions: awk --version , bash --version
3. Inadequate Coating and Wrapping
A common DEP demand: "Three-layer polyethylene coating (3LPE) with a minimum thickness of 2.5 mm, tested for cathodic disbondment at 95°C." Using cheaper FBE (Fusion Bonded Epoxy) alone will fail.
The Anatomy of a Shell DEP Document
Understanding the numbering system is critical. A typical DEP document number looks like: DEP 31.22.00.10-Gen
Let's break it down:
- 31 : Discipline (e.g., 30-series = Mechanical; 40-series = Electrical; 70-series = Civil/Structural)
- 22 : Sub-discipline (e.g., Pressure Vessels)
- 00 : Document type (00 = Specification; 10 = Guideline; 20 = Data Sheet)
- 10 : Sequence number
- Gen : Applicability (Gen = General; HSS = High Sulfur Service; LowT = Low Temperature; Offshore)
The command -v Standard
Avoid using which for checking dependencies. which is an external binary and may not exist on all minimal systems (e.g., minimal Docker containers). Use the built-in command -v.
Standard Pattern:
declare -a required_commands=("jq" "curl" "docker")
for cmd in "$required_commands[@]"; do if ! command -v "$cmd" &> /dev/null; then echo "Error: Required dependency '$cmd' is not installed or not in PATH." exit 1 fi done
Rest of script...
curl "$API_BASE_URL/endpoint" | jq '.data'
Running on a system without jq:
ERROR: Missing required command 'jq'
ERROR: Dependency validation failed. Aborting.
4. Forgotten "Legacy DEP" Clauses
Shell periodically updates DEPs. A project approved in 2020 may use DEP 2017 edition. However, if a vendor uses the 2023 edition without checking, they may add costly unrequired features.
Part 6: The MESC Number – The DNA of Shell Procurement
To the uninitiated, a string like "MESC 27.40.60.10– 123" looks like gibberish. In reality, the MESC (Materials and Equipment Standards and Codification) is a classification system that ties a specific DEP to a commercial item.
- MESC Prefix (e.g., 27.40): Defines the equipment class (e.g., 27 = Valves, 40 = Ball Valves).
- MESC Suffix (e.g., .10): Specific design details (e.g., floating ball, soft seated).
- Numeric tail (e.g., 123): Size, pressure class, and material.
When a buyer issues a purchase order, the MESC number automatically invokes the related DEP requirements. Vendors who bid without understanding the MESC-to-DEP linkage invariably fail technical evaluation.
