February 2022

Environment and Safety

Are hot pipes and equipment surfaces ignition sources in the HPI?

Most international and national standards used in the hydrocarbon processing industry (HPI) for conducting hazardous area classification do not provide any guidance or recommendation for non-electrical equipment, such as hot pipe and equipment surfaces, that can act as ignition sources.

Biradar, B., Agarwal, A., Bechtel India Pvt Ltd.

Most international and national standards used in the hydrocarbon processing industry (HPI) for conducting hazardous area classification do not provide any guidance or recommendation for non-electrical equipment, such as hot pipe and equipment surfaces, that can act as ignition sources. These standards are written specifically for electrical equipment as the source of ignition for hazardous area classification purposes. Accordingly, HPI engineers are also conducting this exercise for the selection of electrical equipment in hazardous areas and other non-electrical ignition sources that are not reported in the classification process. Approach Some of the international and national standards

Log in to view this article.

Not Yet A Subscriber? Here are Your Options.

1) Start a FREE TRIAL SUBSCRIPTION and gain access to all articles in the current issue of Hydrocarbon Processing magazine.

2) SUBSCRIBE to Hydrocarbon Processing magazine in print or digital format and gain ACCESS to the current issue as well as to 3 articles from the HP archives per month. $409 for an annual subscription*.

3) Start a FULL ACCESS PLAN SUBSCRIPTION and regain ACCESS to this article, the current issue, all past issues in the HP Archive, the HP Process Handbooks, HP Market Data, and more. $1,995 for an annual subscription.  For information about group rates or multi-year terms, contact email Peter Ramsay or call +44 20 3409 2240*.

*Access will be granted the next business day.

Related Articles

From the Archive

Comments

Comments

{{ error }}
{{ comment.comment.Name }} • {{ comment.timeAgo }}
{{ comment.comment.Text }}