LPM Lifecycle Monitoring System. 45.8.1 Full lifecycle monitoring and information system is provided, and it continues to be provided to the Board and to the PLAs as the machine changes ownership within the industry.
LPM Lifecycle Monitoring System Sample Clauses
Related to LPM Lifecycle Monitoring System
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.
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:
Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.
Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.
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.
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.
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 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.
