Engineering guide

Designing to SABIC Specifications: A Practical Guide for Engineers

Designing to SABIC specifications means applying the owner's engineering standards on top of the international codes, and showing in every deliverable which requirement governed each decision. This guide explains how those documents are structured, what inputs a designer needs, how compliance is normally demonstrated and where projects tend to go wrong.

Last updated:

How SABIC engineering standards are structured

SABIC and its affiliates publish engineering standards and specifications that define how plants, equipment and materials must be designed, purchased and built. Like most operator standards, they rarely replace the international codes. Instead, they adopt a base code, such as ASME Section VIII for pressure vessels, API 650 for storage tanks or ASME B31.3 for process piping, and then add, modify or delete requirements.

Each affiliate and each project can also have its own specification layer. A project at one site may invoke a different revision, an affiliate-specific supplement or a licensor's requirements for a particular unit. The first task on any job is therefore to establish exactly which documents and revisions apply, not to assume that the set used on the last project is still valid.

  • International base code (ASME, API, ASCE, ACI, AISC and similar)
  • SABIC or affiliate engineering standards that supplement the base code
  • Project specifications and site data for the specific plant
  • Licensor requirements for proprietary process units
  • Purchase order or contract terms that set revision and order of precedence

Order of precedence and conflicts

When documents conflict, the contract normally defines the order of precedence. A common arrangement places statutory requirements first, then the purchase order and project specification, then the owner's standards, and finally the international codes. That order is not universal, so it must be read from the contract rather than assumed.

Where two requirements cannot both be met, the designer should not quietly choose one. The usual practice is to raise a technical query, record it in a clarification register and wait for a written answer. On a fixed schedule this feels slow, but an unrecorded choice is far more expensive when it is found at final review or during inspection.

Technical queries work best when they propose an answer. A query that states the conflict, the options and the designer's recommended option with its reasoning is usually closed faster than one that simply asks the owner what to do.

Typical inputs for a design package

Most review comments on specification-heavy projects come from inputs that were assumed rather than confirmed. Before calculations start, the designer should hold a complete set of the items below and list them in the design basis.

Any input that is still provisional should be marked as such in the design basis, with a hold on the affected calculations. Releasing a calculation with an unmarked assumption invites a comment, or worse, a design that passes review on the wrong basis.

Inputs to confirm before design starts
InputWhy it mattersTypical source
Applicable standards and revisionsDefines the rules every check must followContract, project specification
Design pressure, temperature and MDMTDrives thickness, material and impact testingProcess datasheet
Corrosion allowance and material selectionOwner standards often set minimums above codeMaterials selection report
Site data: wind, seismic, ambient temperatureSets environmental loads on equipment and structuresProject site data
Nozzle loads and external loadsGoverns local stress at nozzles and supportsPiping stress or owner tables
Datasheet and document formatsReviewers expect the owner's templatesProject procedures

Where SABIC specifications usually add requirements

Without quoting individual clauses, which vary between documents and revisions, the areas where operator standards commonly tighten the base code are well known. Designers should check each of these explicitly against the project set rather than relying on the base code alone.

Materials are the most frequent area. Owner standards often restrict certain grades, require additional impact testing at low temperature, set hardness limits for wet sour service or require positive material identification. Minimum corrosion allowances and minimum nozzle sizes are also common, as are requirements for full-penetration welds at specific joints, additional radiography and stricter tolerances.

Loads are the second area. Nozzle load tables, wind and seismic data and load combinations for equipment supports may be prescribed by the owner rather than left to the designer. Using the generic values from a code annex in place of the owner's tables is a frequent cause of rejected calculations.

Showing compliance in deliverables

Reviewers need to see compliance, not just be told about it. A good package lets the reviewer trace any value back to an input and any check back to a requirement, without asking the designer.

Calculations should name the governing standard and revision at the top and reference the relevant requirement next to each check. Datasheets should use the owner's format and match the calculations exactly. A compliance matrix, listing each applicable requirement as comply, exception or not applicable with a pointer to where it is addressed, is often requested and is worth preparing even when it is not. Exceptions belong in a deviation register with a technical justification so they can be approved formally.

Revision control is part of compliance. When a calculation is revised after comments, the datasheet, drawings and any dependent calculations, such as foundation loads taken from the equipment design, must be revised with it. A simple cross-reference list showing which documents use which outputs makes this manageable on packages with many interdependent documents.

Common mistakes

Most problems on these projects are procedural rather than technical. The engineering is usually sound; what fails is the link between the engineering and the documents that govern it.

  • Working to the latest revision of a standard when the contract names an earlier one, or the reverse
  • Copying a previous project's design basis without checking the affiliate or site-specific documents
  • Using base-code default nozzle loads or wind data instead of the owner's values
  • Missing supplementary material requirements such as extra impact testing or hardness limits
  • Leaving deviations in emails instead of a register, so they resurface at final review
  • Datasheets that drift out of step with revised calculations

When to bring in a specialist engineer

A fabrication workshop or contractor with strong code experience can handle many packages in-house. Outside support is worth considering when the package includes analysis beyond rule-based design, such as finite-element assessment of local loads or fatigue, when the workload exceeds in-house capacity, or when a first submission has come back with a large number of comments.

SLETEC prepares designs to SABIC specifications and the client's project specification as an engineering subcontractor, working under the contractor's document numbering and procedures. We do not claim any approval from SABIC; the contractor submits our deliverables through their own channels. For related work see our static equipment design service, our EPC engineering support and our page on Saudi Aramco standards engineering.

Frequently asked questions

Do SABIC standards replace ASME and API codes?

No. They normally adopt an international code as the base and then add, modify or delete requirements. The designer must apply the base code and the owner's supplements together, in the order of precedence set by the contract.

Which revision of a SABIC standard should be used?

Use the revision named in the contract, purchase order or project specification. If none is named, raise a technical query and record the agreed revision in the design basis before calculations start.

What is a compliance matrix?

A compliance matrix is a table that lists each applicable requirement and states whether the design complies, takes an exception or finds it not applicable. Each line points to the document and section where the requirement is addressed, which makes review faster.

Can SLETEC prepare designs for SABIC affiliate projects?

Yes, as an engineering subcontractor to the contractor or manufacturer. We prepare designs to the applicable SABIC specifications and the project specification, and the contractor submits them through their own approved route. We do not claim SABIC approval.

Discuss your project with an engineer

Send drawings, datasheets or a short scope – an engineer replies with scope, schedule and price, usually within 24 hours.