System wide Monitoring Sample Clauses

System wide Monitoring. The Quality Assurance/Quality Management (QA/QM) System includes a systemic approach for measuring the effectiveness of PCP and identifying barriers to successful use of the PCP process. The best practices for supporting individuals through PCP are identified and implemented (what is working and what is not working in supporting individuals). Organizational expectations and standards are in place to assure that the person directs the PCP process and ensures that PCP is consistently followed.
AutoNDA by SimpleDocs
System wide Monitoring 

Related to System wide Monitoring

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

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

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

  • Infrastructure (a) The Borrower has and will maintain a sufficient infrastructure to conduct its business as presently conducted and as contemplated to be conducted following its execution of this Agreement.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Hosting 46.7.4.1 At CLEC’s request, SBC-SWBT and SBC-AMERITECH shall perform hosting responsibilities for the provision of billable message data and/or access usage data received from CLEC for distribution to the appropriate billing and/or processing location or for delivery to CLEC of such data via SBC-SWBT’s and SBC-AMERITECH’s internal network or the nationwide CMDS network pursuant to the applicable Appendix HOST, which is/are attached hereto and incorporated herein by reference.

  • Supply Chain Monitoring A copy of the supply chain monitoring process, which should include details of the process for monitoring the financial viability of the supply chain (including timing), together with any known risks to supply chain stability and material changes to the supply chain. This should include extracts from Board level meetings, risk registers etc where any of the above items have been discussed. Annex 1 1 Information from Contractors who are not required to submit form AR01 to Companies House

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

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