Loading...

Please Wait...

PT Notes

What is the difference between RAGAGEP and Codes and Standards?

PT Notes is a series of topical technical notes on process safety provided periodically by Primatech for your benefit. Please feel free to provide feedback.

Recognized and Generally Accepted Good Engineering Practices (RAGAGEP) differ from Codes and Standards in several key ways. RAGAGEP and Codes, and Standards play crucial roles in ensuring the safety and reliability of industrial processes Understanding their differences is essential for regulatory compliance and operational excellence.

RAGAGEP refers to the collective wisdom and practices that are widely endorsed and utilized by professionals within an industry to achieve safe and efficient operations. RAGAGEP can include both formal published standards and the unwritten but broadly accepted practices that have been proven effective over time.

Codes and Standards are formal documents that establish technical specifications, procedures, and criteria designed to ensure materials, products, methods, and services are fit for purpose. Typically, they are developed by recognized standards organizations through a consensus process involving experts in the field.

Here are some key differences:

Authority and Formality

RAGAGEP can be less formal than Codes and Standards and may include industry best practices that are not codified in official documents but are recognized as effective through widespread use and consensus.

Codes and Standards are formal documents that have been through a rigorous development and review process by standards organizations They often have legal and regulatory recognition and must be adhered to in certain jurisdictions and contexts.

Scope and Application

RAGAGEP often provides guidance on best practices that cover a broad range of activities and operations within an industry, focusing on performance outcomes rather than prescriptive measures.

Codes and Standards provide specific requirements for particular aspects of design, construction, testing, and maintenance, etc., and are more prescriptive and detailed in their scope.

Legal and Regulatory Recognition

RAGAGEP may be referenced by regulators as a way to define industry best practices, but individually, practices under this umbrella might not have specific legal status.

Codes and Standards frequently are incorporated by reference into laws and regulations, making compliance with them a legal requirement for certain activities and industries.

Development and Evolution

RAGAGEP evolves as industry practices change and new technologies and methods are adopted. This evolution can be informal and decentralized.

Codes and Standards are updated through a formal revision process that involves formal review and input from various stakeholders. This process ensures that changes are carefully considered and consensus is reached before implementation.

Examples of RAGAGEP include industry best practices, manufacturer's recommendations, and consensus documents that may not have formal backing by standards organizations.

Examples of Codes and Standards include documents published by organizations such as the American Society of Mechanical Engineers (ASME), the National Fire Protection Association (NFPA), the International Society of Automation (ISA), the International Electrotechnical Commission (IEC), and the International Organization for Standardization (ISO).

Both RAGAGEP and Codes and Standards are critical for ensuring that process operations are conducted safely and effectively. Companies often must demonstrate compliance with both to satisfy regulatory requirements and minimize risks associated with their operations.

If you would like further information, please click here.

To comment on this PT Note, click here.

You may be interested in:

Process Safety Training

Process Safety Consulting

Process Safety Certification

Process Safety Software 

Back to PT Notes