Meeting the requirements of API 618, ASME B31.3, or any other applicable standard is necessary but not sufficient for a reliable compressor installation. Understanding the difference between code compliance and engineering adequacy is important for owners who want to specify the right level of analysis and for engineers who want to deliver results that actually work.
What Codes Are Designed to Do
Engineering codes are consensus documents that establish minimum requirements for acceptable practice. They are written to be broadly applicable across a wide range of applications and to be achievable by a competent engineering team without excessive cost. By design, they represent a minimum floor, not an optimal solution.
API 618 Design Approach 2, for example, requires that acoustic and mechanical natural frequencies be separated by a margin. It does not require that the system be dynamically optimized for minimum vibration levels. A system that barely meets the frequency separation requirement is compliant; it may still vibrate more than one that was designed with larger margins.
Where Code Minimum Falls Short
There are specific situations where code-minimum compliance reliably produces results that fall short of the owner’s reliability expectations. Installations with unusual operating profiles, variable speed drives, or complex multi-unit configurations may require analysis that goes beyond what the code requires.
Similarly, high-consequence installations — offshore platforms, FPSO systems, or units where downtime cost is very high — justify analysis margins and documentation rigor beyond the code minimum.
The Engineering Adequacy Standard
Engineering adequacy means that the analysis has been performed with sufficient depth and rigor to give confidence that the system will behave as predicted in actual service, not just that it satisfies the checklist items in the applicable standard. The analyst’s experience and judgment in selecting analysis methods, verifying assumptions, and interpreting results is what separates adequate engineering from code compliance paperwork.
At Tech Transfer, our goal is engineering adequacy. Code compliance is a byproduct of doing the analysis correctly.
