Additional Quantities For a period not exceeding ninety (90) days from the date of solicitation award, the Customer reserves the right to acquire additional quantities up to the amount shown on the solicitation but not to exceed the threshold for Category Two at the prices submitted in the response to the solicitation.
Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.
Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.
Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.
Minimum Technical Requirements Participant will be responsible for installing (unless Vendor provides), maintaining and hosting the Vendor’s integration package (either “Full Express” or “Express Lite” software) on Participant’s own computer to enable connectivity to the Network for the Patient Look-Up and Delivery Services including installing and maintaining updates and upgrades. Participant’s machine must meet the following requirements for hosting the Vendor’s integration package: • A virtual machine environment running VMware Player (free open source product) that can run the Express VMware disk image (.ova format) • For Vendor’s “Express Lite” software (for Participants that already have an enterprise master patient index (MPI) and a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 4 CPU cores o 8GB of RAM o 100GB of available disk space • For Vendor’s “Full Express” software (for Participants that do not already have an MPI or a clinical data repository), the minimum system resources that should be allocated to the virtual machine are: o 8 CPU cores o 16GB of RAM o 500GB of available disk space • Network access between the Vendor’s Express software (either “Express Lite” or “Full Express”) and the Participant’s health information exchange system for the exchange of clinical system data for the Patient Look-Up and Delivery Services. The Participant shall maintain availability of its data for query on a 24 hour/7 day basis with the exception of routine and unexpected maintenance, at greater than 99% uptime monthly. The Participant shall make its data available for a minimum look-back period of 18 months up to and including current available data and update the available data daily.
Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.
Initial Trunk Forecast Requirements At least ninety (90) days before initiating interconnection in a LATA, Emergency 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.
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.
CAISO Monthly Billed Fuel Cost [for Geysers Main only] The CAISO Monthly Billed Fuel Cost is given by Equation C2-1. CAISO Monthly Billed Fuel Cost Equation C2-1 = Billable MWh ◆ Steam Price ($/MWh) Where: • Steam Price is $16.34/MWh. • For purposes of Equation C2-1, Billable MWh is all Billable MWh Delivered after cumulative Hourly Metered Total Net Generation during the Contract Year from all Units exceeds the Minimum Annual Generation given by Equation C2-2. Equation C2-2 Minimum Annual Generation = (Annual Average Field Capacity ◆ 8760 hours ◆ 0.4) - (A+B+C) Where: • Annual Average Field Capacity is the arithmetic average of the two Field Capacities in MW for each Contract Year, determined as described below. Field Capacity shall be determined for each six-month period from July 1 through December 31 of the preceding calendar year and January 1 through June 30 of the Contract Year. Field Capacity shall be the average of the five highest amounts of net generation (in MWh) simultaneously achieved by all Units during eight-hour periods within the six-month period. The capacity simultaneously achieved by all Units during each eight-hour period shall be the sum of Hourly Metered Total Net Generation for all Units during such eight-hour period, divided by eight hours. Such eight-hour periods shall not overlap or be counted more than once but may be consecutive. Within 30 days after the end of each six-month period, Owner shall provide CAISO and the Responsible Utility with its determination of Field Capacity, including all information necessary to validate that determination. • A is the amount of Energy that cannot be produced (as defined below) due to the curtailment of a Unit during a test of the Facility, a Unit or the steam field agreed to by CAISO and Owner. • B is the amount of Energy that cannot be produced (as defined below) due to the retirement of a Unit or due to a Unit’s Availability remaining at zero after a period of ten Months during which the Unit’s Availability has been zero. • C is the amount of Energy that cannot be produced (as defined below) because a Force Majeure Event reduces a Unit’s Availability to zero for at least thirty (30) days or because a Force Majeure Event reduces a Unit’s Availability for at least one hundred eighty (180) days to a level below the Unit Availability Limit immediately prior to the Force Majeure Event. • The amount of Energy that cannot be produced is the sum, for each Settlement Period during which the condition applicable to A, B or C above exists, of the difference between the Unit Availability Limit immediately prior to the condition and the Unit Availability Limit during the condition.
