 |
| |
Facility At-A-Glance Report
|
|
| |
[VIEW PRINTER FRIENDLY VERSION]
[EXPORT THIS REPORT TO EXCEL]
|
|
| |
[REFINE SEARCH]
[NEW SEARCH]
[GLOSSARY]
Place ID 856335
|
|
| |
|
|
| |
|
General Information
|
| Region |
Place ID |
Place Name |
Place Type |
Place Address |
Place County |
| 2 |
856335 |
3655 Kifer Road |
Domestic Site NEC |
3655 Kifer Santa Clara, CA, 95051 |
Santa Clara |
|
|
Related Parties
|
|
|
Total Related Parties: 2
|
|
|
|
Regulatory Measures
|
|
|
Total Reg Measures: 1
|
|
|
|
Violations
|
| Violation ID |
Occurred Date |
Violation Type |
(-) Violation Description |
Corrective Action |
Status |
Classification |
Source |
| 1077954 |
06/23/2019 |
DMON |
The Discharger conducted first-day startup sampling on April 18, 2019, and after receiving an exceedance of Chrysene effluent limits it put the Treatment System on recirculation mode on the same day. After an extended period while in recirculation mode, it began discharging on June 18, 2019. The discharger did not confirm Chrysene exceedance nor conduct on 5-day sampling which would have happened on June 23, 2019. The Discharger did not conduct 5-day startup sampling as required by Attachment E section VIII.A.2. |
On July 18 and 19, 2019, the Discharger held conference calls with team members to improve communication. The Discharger implemented a Lock-Out/Tag-Out program for the treatment system. This added security requires that 2 individuals must be in agreement to either open or close the discharge valve. Each individual has a set of keys to the double-locking system. |
Violation |
B |
Report |
| 1077955 |
06/23/2019 |
Failure to Notify |
The Discharger conducted first-day startup sampling on April 18, 2019, and after receiving an exceedance of Chrysene effluent limits it put the Treatment System on recirculation mode on the same day. After an extended period while in recirculation mode, it began discharging on June 18, 2019. The discharger did not confirm Chrysene exceedance nor conduct on 5-day sampling which would have happened on June 23, 2019. The Discharger did not conduct 5-day startup sampling as required by Attachment E section VIII.A.2. |
On July 18 and 19, 2019, the Discharger held conference calls with team members to improve communication. The Discharger implemented a Lock-Out/Tag-Out program for the treatment system. This added security requires that 2 individuals must be in agreement to either open or close the discharge valve. Each individual has a set of keys to the double-locking system. |
Violation |
B |
Report |
| 1077956 |
06/18/2019 |
Failure to Notify |
The Discharger conducted first-day startup sampling on April 18, 2019, and after receiving an exceedance of Chrysene effluent limits it put the Treatment System on recirculation mode on the same day. After an extended period while in recirculation mode, it began discharging on June 18, 2019. The discharger did not confirm Chrysene exceedance nor conduct on 5-day sampling which would have happened on June 23, 2019. |
On July 18 and 19, 2019, the Discharger held conference calls with team members to improve communication. The Discharger implemented a Lock-Out/Tag-Out program for the treatment system. This added security requires that 2 individuals must be in agreement to either open or close the discharge valve. Each individual has a set of keys to the double-locking system. |
Violation |
B |
Report |
|
Report displays most recent five years of violations. Refer to the Interactive Violation Report for more data.
|
|
|
Total Violations: 3
|
Priority Violations: 0
|
*Click the "(+/-) Violation Description" link to expand and contract the violation description.
*As of 5/20/2010, the Water Board's Enforcement Policy requires that all violations be classified as 1, 2 or 3, with class 1 being the highest. Prior to this, violations were simply classified as Yes or No. If a 123 classification has been assigned to a violation that occurred before this date, that classification data will be displayed instead of the Yes/No data.
|
| Violation Types |
|
DMON = Deficient Monitoring
|
Failure to Notify = Failure to Notify
|
|
|
|
|
Enforcement Actions
|
|
|
Total Enf Actions: 0
|
|
|
|
Inspections
|
|
| Total Inspections: 0 |
Last Inspection: None |
|
|
|
|
|
The current report was generated with data as of: 06/06/2024
Regional Boards are in the process of entering backlogged data.
As a result, data may be incomplete.
|
|
|
Back to Main Page
|
Back to Top of Page
|
|
|
|
|
|
