Shell Dep Standards New! -

Shell Design and Engineering Practices (DEPs) are a comprehensive set of technical standards developed by Shell to ensure global consistency in the design, construction, and maintenance of its petrochemical plants and upstream facilities

  1. File Permissions: Set execute permissions on scripts using chmod +x script.sh.
  2. Script Location: Store scripts in a designated directory, such as /usr/local/bin or /opt/scripts.
  3. Script Naming: Use a consistent naming convention, such as $script_name.sh.
  4. Version Control: Store scripts in a version control system, such as Git.
  5. Change Management: Implement a change management process to track changes to scripts.

Authorized Access Routes:

  1. Direct Shell Contractors: If your company has a frame agreement or specific project contract with Shell, you will be granted access via Shell’s Global Technical Standards Portal (GTSP) .
  2. Vendors: Equipment suppliers must register with Shell’s TAMAP (Technical Assurance Management and Procurement) system. Often, a buyer will issue a "DEP requisition" as part of the RFQ package.
  3. Licensing via IHS Markit: For non-Shell entities (e.g., engineering consultancies bidding on a Shell job), DEPs can be purchased through IHS Markit (now part of S&P Global) under a limited-use license.
  4. Joint Ventures: In a JV operation, Shell usually requires adoption of DEPs as the governing standard.

Let's break it down:

Disclaimer: DEP numbers and titles evolve. Always confirm the latest revision with Shell’s official portal. shell dep standards

The Core Purpose

  • Global Consistency: A platform designed in Nigeria must be identical in specification to one in Brunei or the Gulf of Mexico.
  • Risk Reduction: DEPs embed decades of lessons learned from incidents and failures.
  • Lifecycle Cost Optimization: They prioritize total cost of ownership over upfront capital expenditure.
  • Interoperability: Ensure that equipment from different vendors works seamlessly within Shell’s ecosystem.