Utah Admin. Code R315-264-1052 - Standards: Pumps in Light Liquid Service
(a)
(1)
Each pump in light liquid service shall be monitored monthly to detect leaks by
the methods specified in Subsection
R315-264-1063(b),
except as provided in Subsections R315-264-1052(d), (e), and (f).
(2) Each pump in light liquid service shall
be checked by visual inspection each calendar week for indications of liquids
dripping from the pump seal.
(b)
(1) If
an instrument reading of 10,000 ppm or greater is measured, a leak is detected.
(2) If there are indications of
liquids dripping from the pump seal, a leak is detected.
(c)
(1)
When a leak is detected, it shall be repaired as soon as practicable, but not
later than 15 calendar days after it is detected, except as provided in Section
R315-264-1059.
(2) A first attempt at repair,
e.g., tightening the packing gland, shall be made no later than 5 calendar days
after each leak is detected.
(d) Each pump equipped with a dual mechanical
seal system that includes a barrier fluid system is exempt from the
requirements of Subsection R315-264-1052(a), provided the following
requirements are met:
(1) Each dual
mechanical seal system shall be:
(i) Operated
with the barrier fluid at a pressure that is at all times greater than the pump
stuffing box pressure, or
(ii)
Equipped with a barrier fluid degassing reservoir that is connected by a
closed-vent system to a control device that complies with the requirements of
Section
R315-264-1060,
or
(iii) Equipped with a system
that purges the barrier fluid into a hazardous waste stream with no detectable
emissions to the atmosphere.
(2) The barrier fluid system shall not be a
hazardous waste with organic concentrations 10 percent or greater by weight.
(3) Each barrier fluid system
shall be equipped with a sensor that will detect failure of the seal system,
the barrier fluid system, or both.
(4) Each pump shall be checked by visual
inspection, each calendar week, for indications of liquids dripping from the
pump seals.
(5)
(i) Each sensor as described in Subsection
R315-264-1052(d)(3) shall be checked daily or be equipped with an audible alarm
that shall be checked monthly to ensure that it is functioning properly.
(ii) The owner or operator shall
determine, based on design considerations and operating experience, a criterion
that indicates failure of the seal system, the barrier fluid system, or both.
(6)
(i) If there are indications of liquids
dripping from the pump seal or the sensor indicates failure of the seal system,
the barrier fluid system, or both based on the criterion determined in
Subsection R315-264-1052(d)(5)(ii), a leak is detected.
(ii) When a leak is detected, it shall be
repaired as soon as practicable, but not later than 15 calendar days after it
is detected, except as provided in Section
R315-264-1059.
(iii) A first attempt at repair,
e.g., relapping the seal, shall be made no later than 5 calendar days after
each leak is detected.
(e) Any pump that is designated, as described
in Subsection
R315-264-1064(g)(2),
for no detectable emissions, as indicated by an instrument reading of less than
500 ppm above background, is exempt from the requirements of Subsections
R315-264-1052(a), (c), and (d) if the pump meets the following requirements:
(1) Shall have no externally actuated shaft
penetrating the pump housing.
(2)
Shall operate with no detectable emissions as indicated by an instrument
reading of less than 500 ppm above background as measured by the methods
specified in Subsection
R315-264-1063(c).
(3) Shall be tested for compliance
with Subsection R315-264-1052(e)(2) initially upon designation, annually, and
at other times as requested by the Director.
(f) If any pump is equipped with a
closed-vent system capable of capturing and transporting any leakage from the
seal or seals to a control device that complies with the requirements of
Section
R315-264-1060,
it is exempt from the requirements of Subsections R315-264-1052(a) through (e).
Notes
State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.
No prior version found.