System Impact Study An assessment by the Transmission Provider of (i) the adequacy of the Transmission System to accommodate a Completed Application, an Interconnection Request or an Upgrade Request, (ii) whether any additional costs may be incurred in order to provide such transmission service or to accommodate an Interconnection Request, and (iii) with respect to an Interconnection Request, an estimated date that an Interconnection Customer’s Customer Facility can be interconnected with the Transmission System and an estimate of the Interconnection Customer’s cost responsibility for the interconnection; and (iv) with respect to an Upgrade Request, the estimated cost of the requested system upgrades or expansion, or of the cost of the system upgrades or expansion, necessary to provide the requested incremental rights.
Standard Service Features Ethernet Access allows Customer to terminate single and/or multiple Ethernet Virtual Circuits (EVCs) from Customer equipment onto a single Ethernet Access UNI.
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.
Design Criteria and Standards All PROJECTS/SERVICES shall be performed in accordance with instructions, criteria and standards set forth by the DIRECTOR.
Design Criteria The Engineer shall develop the roadway design criteria based on the controlling factors specified by the State (i.e. 4R, 3R, 2R, or special facilities), by use of the funding categories, design speed, functional classification, roadway class and any other set criteria as set forth in PS&E Preparation Manual, Roadway Design Manual, Bridge Design Manual, Hydraulic Design Manual, and other deemed necessary State approved manuals. In addition, the Engineer shall prepare the Design Summary Report (DSR) and submit it electronically. The Engineer shall obtain written concurrence from the State prior to proceeding with a design if any questions arise during the design process regarding the applicability of State’s design criteria.
Construction Standards The Subrecipient and Developer shall ensure that all Approved Projects comply with the following requirements:
Design Standards Most recent edition of the “Owner’s Design Standards,” including any partial updates as may be directed by the Owner.
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.
Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
