Blogs & Case Studies

When we start working in the oil and gas industry, one of the first things we are trained on is the importance of engineering codes and standards. Very early in our careers, we are told to “check the code,” “follow the standard,” or “ensure compliance.” This is correct advice, but it is incomplete. With some years of project exposure, site experience, and vendor interaction, most engineers realise that engineering codes are not the design itself—they are only the starting point in oil and gas engineering design.

This understanding does not usually come from books or classrooms. It comes from dealing with real engineering design problems, mismatches between drawings and site conditions, and equipment that technically met the code but still created operational headaches.

Engineering codes and standards are developed based on industry experience, past failures, and lessons learned over decades. They represent a collective agreement on minimum acceptable requirements for safety, performance, and reliability in industrial engineering design. In oil and gas facilities, where risks are high, these documents act as a common reference point for designers, owners, regulators, and inspectors.

However, it is important to understand the intent behind them. Codes define limits, boundaries, and minimum criteria. They do not define the full engineering design philosophy of a project. They assume that a competent engineer will apply judgment while using them.

On paper, a design may fully comply with the relevant engineering standards and code compliance requirements, but in reality, it may still face operational or maintenance challenges. This happens because engineering codes are written to be generic. They do not know your plant layout, your operating philosophy, or your future expansion plans.

For example, a pressure gauge selected strictly as per code requirements in oil and gas engineering may meet minimum standards, but without considering design pressure, operating range, or upset conditions, it may fail prematurely. The code did its job, but the engineering design intent was incomplete.

A design can be fully code-compliant in engineering terms and still be impractical. This is something many engineers realise only after commissioning or handover to operations. Engineering standards do not consider ease of maintenance, instrument accessibility, local operating practices, or plant-specific constraints.

For example, selecting an instrument exactly at the minimum rating allowed by industrial design standards may look acceptable on paper. But during plant operation, pressure fluctuations, temperature variations, or start-up conditions may push the equipment close to its limit repeatedly. Over time, this results in frequent failures, false alarms, or maintenance complaints.

Engineering codes usually refer to design conditions, but actual plants operate across a wide range of scenarios. Start-up, shutdown, regeneration, flushing, and upset conditions are part of daily plant life. Many of these conditions are not clearly defined in engineering code clauses.

A practical process engineering design approach considers normal, maximum, minimum, and abnormal operating cases. Engineers with experience learn to ask questions like: What happens if the valve downstream is closed suddenly? What happens during pump trip? Will this instrument still function if the process goes slightly outside normal limits?

Another real-world challenge in industrial engineering projects is vendor data. Vendors often design equipment to meet international engineering standards, but their interpretation may be very basic. Datasheets may show compliance, but details such as material compatibility, sealing philosophy, or long-term reliability may be weak.

An experienced engineer reviews vendor documents not only for code compliance, but also for practical suitability. This includes checking ranges, margins, material selections, and installation limitations. Engineering judgment fills the gaps where codes fall short.

Many engineering design lessons are learned during site execution and commissioning. Equipment that looked fine during design review may become difficult to access once piping, cable trays, and structures are installed. Engineering codes rarely address these integration challenges.

Engineers who have attended site work tend to design differently later in their careers. They think about clearance, isolation, draining, venting, and future maintenance. These considerations are not always explicitly stated in engineering standards, but they strongly influence good design.

Blindly following engineering codes and standards without understanding their intent can lead to poor decisions. Codes are periodically revised, but projects often use different editions based on contract requirements. What was acceptable in one edition may not fully address current engineering design best practices.

Also, codes cannot predict every failure mode. They provide guidance based on known risks, but new processes, materials, and operating philosophies continuously introduce scenarios that standard engineering codes may not yet capture.

Engineering judgment in design is not something that appears overnight. It develops gradually through exposure to design reviews, technical queries, construction feedback, and operational issues. After a few years, engineers begin to recognise patterns and common pitfalls.

This is when engineering codes stop being checklists and start becoming reference tools. The engineer understands when to strictly follow a clause and when to go beyond it for the sake of safety or reliability.