System Tested Baseline Application Modifications Sample Clauses

System Tested Baseline Application Modifications. Contractor shall certify, in writing, that Contractor has successfully System Tested all components of the Baseline Application Modifications to the Application Software and has successfully corrected all identified Deficiencies and that the Baseline Application Modifications function as designed.
AutoNDA by SimpleDocs

Related to System Tested Baseline Application Modifications

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • OGS Centralized Contract Modifications OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Budget Modifications The total Approved Budget and the assignment of costs may be adjusted based on implementation of the Scope of Work, spending patterns, and unexpended funds, but only by an amendment to the Approved Budget. In no event shall an amendment to the Approved Budget result in payments in excess of the aggregate amount specified in Section 2.01 “Award of Monies” or in approved supplemental funding for the Project, if any. The RECIPIENT may make transfers between or among lines within budget categories without prior written approval provided that:

  • CENTRALIZED CONTRACT MODIFICATIONS A. OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • INTEGRATION/MODIFICATION This Agreement constitutes the entire understanding and agreement between the Company and the Executive regarding its subject matter and supersedes all prior negotiations and agreements, whether oral or written, between them with respect to its subject matter. This Agreement may not be modified except by a written agreement signed by the Executive and a duly authorized officer of the Company.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.

  • Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

Time is Money Join Law Insider Premium to draft better contracts faster.