Milk Temperature Monitoring Sample Clauses

Milk Temperature Monitoring. Vat temperatures should be monitored during milking, at the completion of milking and at any stage during the day when the Supplier is in the vicinity of the milk vat. If at any point the milk is not cooling within specification, or cooling slower than usual, immediately contact a qualified technician to assess and if necessary repair / replace the cooling system.
AutoNDA by SimpleDocs

Related to Milk Temperature Monitoring

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • System Monitoring to ensure safe and continuous operation, the Customer must monitor key services and resource use as recommended by Deswik, and provide Deswik with details of monitoring and any relevant alerts as needed. Services to be monitors include, without limitation, disk space, CPU usage, memory usage, database connectivity, and network utilization.

  • Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Monitoring Equipment 2.2.1 24-hour TSP air quality monitoring was performed using High Volume Sampler (HVS) located at each designated monitoring station. The HVS meets all the requirements of the Project Specific EM&A Manual. Portable direct reading dust meters were used to carry out the 1-hour TSP monitoring. Brand and model of the equipment is given in Table 2.1.

  • 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:

  • 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:

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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