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.
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2
System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.
Customer Equipment Customer represents and warrants that it owns or has the legal right and authority, and will continue to own or maintain the legal right and authority during the term of this Agreement, to place and use the Customer Equipment as contemplated by this Agreement. Customer further represents and warrants that its placement, arrangement, and use of the Customer Equipment in the Internet Data Centers complies with the Customer Equipment Manufacturer's environmental and other specifications.
XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.
Connectivity User is solely responsible for providing and maintaining all necessary electronic communications with Exchange, including, wiring, computer hardware, software, communication line access, and networking devices.
End Users Customer will control access to and use of the Products by End Users and is responsible for any use of the Products that does not comply with this Agreement.
System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.
Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.
