Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.
Inputs 921 The following resources constitute a suitable, but neither exhaustive nor normative suite of the process inputs:
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.
Value Engineering The Supplier may prepare, at its own cost, a value engineering proposal at any time during the performance of the contract. The value engineering proposal shall, at a minimum, include the following;
Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.
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.
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.
Outputs 11. The objectives and outcomes of this Agreement will be achieved by:
Net Metering If you generate electricity from a renewable generating facility to offset your electricity consumption and/or use net metering at any time during the term of this Agreement, you must notify Starion.
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.