Secondary Containment Clause Samples

The Secondary Containment clause requires the installation and maintenance of additional barriers or systems designed to prevent the release of hazardous substances beyond a primary containment area. In practice, this may involve using dikes, double-walled tanks, or spill basins to capture leaks or spills from storage vessels or pipelines. The core function of this clause is to minimize environmental contamination and liability by ensuring that accidental releases are contained and do not spread beyond the immediate area, thereby protecting surrounding property and ecosystems.
Secondary Containment. Buyer will ascertain and perform any and all construction or retrofitting necessary to satisfy or comply with the secondary containment standards for underground storage tanks required by applicable laws, regulations or governmental authorities.
View SourceView Similar (6)
Secondary Containment. Oil storage containers greater than or equal to 55 gallons (e.g., 55-gallon drums, portable tanks) shall be stored within secondary containment such as a spill pallet or concrete berm capable of holding 110% of the largest container’s capacity or be double- walled.
View SourceView Similar (2)
Secondary Containment. As an operational control element, the contractor shall ensure, and the San Diego Water Board will verify, that all oil and fuel is housed in a secondary containment structure to ensure that spilled or leaked oil or fuel will be prevented from entering the water column.
View SourceView Similar (2)
Secondary Containment. Secondary containments are required for containers of liquid waste under the following circumstances: • When the waste is stored in 55-gallon drums. • When the waste is stored on the floor. • When the waste is stored in a hood which has a drain. • When the waste is stored within four (4) feet of a sink. • When necessary to separate incompatible or high hazard wastes. Plastic tubs can be used as secondary containments. EHSO should be consulted about secondary containments for 55-gallon drums.
View SourceView Similar (2)
Secondary Containment. 1.1.2.1 Approved by LMI and certified by appropriate regulatory agencies.
View Source
Secondary Containment. Within one hundred eighty (180) days of the Effective Date of this CA/FO, Respondent shall install secondary containment for Tanks T-1, 2, 5 and 6 in accordance with the plans and calculations attached hereto as Exhibit 1 in order to meet the capacity requirements provided in Exhibit 1 and comply with the requirements of 40 CFR § 265.193. Respondent also shall, to the extent necessary, be authorized to provide for alternative secondary containment for Tanks T-1, 2, 5 and 6 on a temporary basis during construction and inspection of the new secondary containment.
View Source
Secondary Containment. Not later than September 1, 2007, Tenant shall take such measures as necessary for the storage of diesel canisters for the on-site forklift to be stored within a roofed area with secondary containment at the following properties: Gelsenkirchen Premises, Essen-Altenessen Premises, and Dortmund-Kley Premises. Documentation of the completion of the actions shall include before and after photographs.
View Source
Secondary Containment. On or before November 1, 1997, Tenant shall install a containment curb around the storage area which shall be sufficient to contain any spills of chemicals or other materials from the largest storage container stored in the storage area.
View Source

Related to Secondary Containment

  • NETWORK MAINTENANCE AND MANAGEMENT 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Patch Management All workstations, laptops and other systems that process and/or store County PHI or PI must have critical security patches applied, with system reboot if necessary. There must be a documented patch management process which determines installation timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable patches must be installed within 30 days of vendor release.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.