Monitoring Components Sample Clauses

Monitoring Components. The 2018 IM 15 monitoring activities include public health and baseline monitoring components.
AutoNDA by SimpleDocs
Monitoring Components. Five secured manhole monitoring stations, with leak detection probes, are located along the transfer line from the EWs. Should a leak occur, an alarm signal is displayed at the main system control panel and the corresponding EW pump(s) will shut down automatically. Local control panels for system monitoring are located at each EW, the sand filter skid, and the air stripper skid. Each EW pump has a flowmeter/totalizer, pressure gauge, and HIGH and LOW pressure sensor that will initiate a shutdown of the pumps at pre-set pressure levels. Additionally, the PLC will shut down the pump(s) when manually prompted by the operator, when the EQ tank level is high, or when a leak is detected in the pipeline. After shutdown, the pump(s) are manually restarted at the main system control panel only after all alarm conditions have been cleared. The main system control panel is located inside the NWPGS facility and has a graphic display of the system, an operator interface unit, and the PLC. A TCE online analyzer is used to monitor effluent TCE concentrations and has a high-level alarm linked to the PLC.
Monitoring Components. A mechanical flow rate/totalizer is installed in each NEPCS TU for recording flow rates and total volume pumped. Trailer effluent concentrations are measured at CERCLA Outfall 001 and for the liquid effluent of each trailer per the requirements of Section 4.
Monitoring Components. ‌ The monitoring module is responsible of implementing and centralizing the function- alities and algorithms to actually perform end-to-end measurements. It is build of three main components: The Passive Measurements Components (XxX) XxX implements the set of mea- surement functionalities needed to monitor exchanges between peers. This func- tion is basically passive as it relies on peers’ communications and never run active measurement probes to reduce as much as possible any overhead. The feasible passive measurements are explained in Chapters 2 and 3. Results of each measurement are then fed to the Monitoring Controller, which possibly elaborate them before pushing the result in the P-REP and N-Rep (via the Rep- Controller). XxX is implemented in every peer, and it is optionally used by peers when sending chunks (i.e., the chunk trading logic can pass the chunk to the XxX). The Active Measurement Component - AcM The AcM performs active measurements, i.e., it can inject pure measurement messages and data that do not carry any video information. This function possibly runs a number of different measurement probes, either periodically or on request. For example, it may be invoked to esti- mate the end-to-end status between the local peer and a remote peer to which no chunks are being sent. Therefore, AcM may be also seen as a bootstrap function when limited knowledge of the peers and the network is stored in the P-REP and N-REP. The Monitoring Controller - MON-Controller The Monitoring Controller is in charge of managing all the measurements performed by the XxX and the AcM. It imple- ments the algorithms to decide when to trigger a particular measurements, and to process the results of end-to-end measurements. For example, considering the XxX results, the MON-Controller can evaluate average, standard deviation and confidence intervals of a given index, it can identify and possibly discard wrong samples, etc. Considering the global network knowledge, it is supposed to implement the algorithms to infer the network status, e.g., by implementing some network tomography or virtual coordinate systems. It potentially collects statistics on all peers and on the state of the network.
Monitoring Components. The AIP 2009 Monitoring Plan includes the following two components.

Related to Monitoring Components

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • Monitoring Compliance Upon the request of the Lender, but without incurring any liability beyond the Guaranteed Obligations, from time to time, Guarantor shall promptly provide to the Lender such documents, certificates and other information as may be deemed reasonably necessary to enable the Lender to perform its functions under the Servicing Agreement as the same relates to the Guarantor.

  • Monitoring Services IDT staff shall, using methods that include face-to-face and other contacts with the member, monitor the services a member receives. This monitoring shall ensure that:

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components licensed under terms and conditions that mandate availability of such source code is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

Time is Money Join Law Insider Premium to draft better contracts faster.