Electric Storage Resources Developer interconnecting an electric storage resource shall establish an operating range in Appendix C of its LGIA that specifies a minimum state of charge and a maximum state of charge between which the electric storage resource will be required to provide primary frequency response consistent with the conditions set forth in Articles 9.5.5, 9.5.5.1, 9.5.5.2, and 9.5.5.3 of this Agreement. Appendix C shall specify whether the operating range is static or dynamic, and shall consider (1) the expected magnitude of frequency deviations in the interconnection; (2) the expected duration that system frequency will remain outside of the deadband parameter in the interconnection; (3) the expected incidence of frequency deviations outside of the deadband parameter in the interconnection; (4) the physical capabilities of the electric storage resource; (5) operational limitations of the electric storage resources due to manufacturer specification; and (6) any other relevant factors agreed to by the NYISO, Connecting Transmission Owner, and Developer. If the operating range is dynamic, then Appendix C must establish how frequently the operating range will be reevaluated and the factors that may be considered during its reevaluation. Developer’s electric storage resource is required to provide timely and sustained primary frequency response consistent with Article 9.5.5.2 of this Agreement when it is online and dispatched to inject electricity to the New York State Transmission System and/or receive electricity from the New York State Transmission System. This excludes circumstances when the electric storage resource is not dispatched to inject electricity to the New York State Transmission System and/or dispatched to receive electricity from the New York State Transmission System. If Developer’s electric storage resource is charging at the time of a frequency deviation outside of its deadband parameter, it is to increase (for over-frequency deviations) or decrease (for under-frequency deviations) the rate at which it is charging in accordance with its droop parameter. Developer’s electric storage resource is not required to change from charging to discharging, or vice versa, unless the response necessitated by the droop and deadband settings requires it to do so and it is technically capable of making such a transition.
Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
Storage Tanks If storage tanks storing Hazardous Materials located on the Premises or the Project are used by Tenant or are hereafter placed on the Premises or the Project by Tenant, Tenant shall install, use, monitor, operate, maintain, upgrade and manage such storage tanks, maintain appropriate records, obtain and maintain appropriate insurance, implement reporting procedures, properly close any storage tanks, and take or cause to be taken all other actions necessary or required under applicable state and federal Legal Requirements, as such now exists or may hereafter be adopted or amended in connection with the installation, use, maintenance, management, operation, upgrading and closure of such storage tanks. Notwithstanding anything to the contrary contained herein, Tenant shall have no right to use or install any underground storage tanks at the Project.
Underground Storage Tanks In accordance with the requirements of Section 3(g) of the D.C. Underground Storage Tank Management Act of 1990, as amended by the District of Columbia Underground Storage Tank Management Act of 1990 Amendment Act of 1992 (D.C. Code § 8-113.01, et seq.) (collectively, the “UST Act”) and the applicable D.C. Underground Storage Tank Regulations, 20 DCMR Chapter 56 (the “UST Regulations”), District hereby informs the Developer that it has no knowledge of the existence or removal during its ownership of the Property of any “underground storage tanks” (as defined in the UST Act). Information pertaining to underground storage tanks and underground storage tank removals of which the D.C. Government has received notification is on file with the District Department of the Environment, Underground Storage Tank Branch, 00 X Xxxxxx, X.X., Xxxxx Xxxxx, Xxxxxxxxxx, X.X., 00000, telephone (000) 000-0000. District’s knowledge for purposes of this Section shall mean and be limited to the actual knowledge of Xxxxxx Xxxxx, Property Acquisition and Disposition Division of the Department of Housing and Community Development, telephone no. (000) 000-0000. The foregoing is set forth pursuant to requirements contained in the UST Act and UST Regulations and does not constitute a representation or warranty by District.
Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.
TOOL STORAGE 1. A company shall provide on all construction jobs in towns and cities, and elsewhere where reasonably necessary and practicable (or if requested buy the employee), a suitable and secure waterproof lock-up solely for the purpose of storing employees’ tools, and on multi-storey and major projects the company shall provide, where possible, a suitable lock-up for employees’ tools within a reasonable distance of the work area of large groups of employees. 2. Where an employee is absent from work because of illness or accident and has advised the company in accordance with Clause 33 – Personal Leave of the award, the company shall ensure that the employee’s tools are securely stored during his/her absence.
Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.
One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.
