Capacity Planning Clause Samples

Capacity Planning. A. Seller agrees to review forecasts provided by Buyer and advise Buyer if Seller anticipates that he will be unable to achieve the requested volumes. Buyer volume forecasts will be provided to Seller in accordance with Exhibit A. Seller may from time to time request Buyer to review Buyer's forecast and advise of any changes.

Capacity Planning. In order to facilitate future capacity planning with respect to the hardware infrastructure required to provide the Demandware Services and to avoid disruptions to the Services, the parties agree to discuss on an ongoing quarterly basis the history and projections of neckermann’s business and operations.

Capacity Planning. A. Seller agrees to review forecasts provided by Buyer and advise Buyer if Seller anticipates that it will be unable to achieve the requested volumes. Buyer's volume forecasts will be provided to Seller according to Section 5. Seller may from time to time request Buyer to review Buyer's forecast and advise of any changes and Buyer will do so. Seller agrees to provide Buyer with either 1) confirmation of feasibility of the forecast received, or 2) notice of specific feasibility issues with the forecast received within five (5) Days of receiving said forecast. B. If Buyer's rolling forecast exceeds Seller's available maximum capacity for Buyer, Seller shall advise Buyer of the limitations in the capacity and provide a response in writing as described in the Purchase Order and rolling forecast articles.

Capacity Planning. Service Provider’s responsibilities include: 1. Implement on-going activities with DIR and DIR Customers for Capacity Planning based on the documented Capacity Plan and coordinate with other Service Component Provider(s) and designated Third Party Vendors. 2. Incorporate appropriate capacity modeling to develop and deliver forecasts of growth and other changes in response to the projected DIR and DIR Customer business and operational needs disclosed by DIR to Service Provider. 2.1. Use appropriate types of modeling (e.g. Pilots, Benchmarks, Prototypes, Baseline, Trends) along with current and historical resource utilization experience in support of business planning, IT planning, and capacity and utilization studies. 2.2. Measure the effectiveness of the capacity planning models. 2.3. On an agreed schedule, or as requested by DIR, revise the capacity planning model based on actual performance. 3. Forecast DIR’s capacity requirements through trending and monitoring and validate the capacity forecast, for DIR designated resources, against DIR’s actual utilization, by DIR Customer and Application. 4. Collect and establish with DIR and DIR Customers appropriate thresholds for supporting the demand and capacity monitoring. 5. Develop forecasts of growth and other changes in demand in cooperation with other Service Component Provider(s), DIR and DIR Customers, taking into account: 5.1. Projected DIR and DIR Customers business and operational needs disclosed by DIR to Service Provider. 5.2. DIR and DIR Customers’ business strategies, business plans, and financial plans. 6. Maintain a knowledge-base of future demand for the Services, and predict the effects of demand on Service Levels. 7. Validate that Capacity Planning appropriately supports the forecasts of growth or other changes in demand. 8. Conduct at least quarterly meetings with DIR Customers on Capacity Planning, and coordinate participation from other Service Component Provider(s) as necessary. 9. Coordinate and provide meaningful Capacity Planning input to the Technology Plan in support of requirements for Long-Range Planning. 10. Coordinate and provide meaningful Capacity Planning input to the Refresh Plan in support of Refresh and Technical Currency.

Capacity Planning. UHC is responsible for providing the ActaMed's ProviderLink Help Desk with as much information as possible to assist ActaMed in planning for the appropriate levels of staffing to meet the service level objectives. Forecasts of site sales, installation scheduling and specific events that will impact ActaMed's ProviderLink volume of calls will be communicated to the best of UHC's ability. Major support requirements will be communicated with a 90 day lead time, whenever possible. TECHNICAL MAINTENANCE/ENHANCEMENT SCHEDULING OBJECTIVES PDR (PROVIDERLINK DEVELOPMENT REQUEST) PROCESS ActaMed will have an established process for documenting all ProviderLink user requests for correction of problems or the development of new functionality. All requests are recorded into a computerized defect control system software product including a detailed description of the requirements. All regular open requests are reviewed by the ActaMed ProviderLink development team on a routine basis, however, UHC will be responsible for establishing the development priorities. ActaMed assumes the responsibility to make the development and maintenance modifications based on UHC priorities. DURING THE TRANSITION, ACTAMED PROVIDERLINK PRODUCT MARKETING WILL AID AND CONTRIBUTE TO THE PRIORITIZATION OF UHC REQUESTS IF NEEDED. FOLLOWING THE TRANSITION PERIOD, ACTAMED WILL CONSIDER THIS ASSISTANCE A LONG TERM BILLABLE SERVICE. NETWORK MAINTENANCE RELEASES Regular ProviderLink network maintenance enhancements and fixes will be completed and certified on a regular basis. They will be released into production on Thursday evenings, AS AVAILABLE. Major software and hardware releases will be scheduled to go into production on weekends. ActaMed will communicate these changes to UHC on a regular, weekly basis. EMERGENCY MAINTENANCE RELEASES Emergency maintenance is defined as the correction of a technical bug or omission in the existing functionality of ActaMed's ProviderLink presentation software or network. The technical problem renders the ProviderLink feature or user inoperable. ActaMed will be responsible for ongoing monitoring and quality control of the network and application. UHC will expect ActaMed to have a well defined problem identification procedure to document and fix inoperable functionality before recognized by UHC or its users. However, when this has not been accomplished, UHC will in cooperation with an ActaMed staff resource, complete a PDR with as much information as is available, d...

Capacity Planning. Subscriber will provide commercially reasonable prior written notice to Travelport of any event that may have an impact on the number of Messages accessing the Travelport System, including, but not limited to, new code or changes to existing code launched by Subscriber, Subscriber’s entrance into new markets, or Subscriber’s advertising/marketing campaigns. Both Parties agree to work together to help ensure that Subscriber’s code operates with the Travelport System in the most efficient way possible. The Parties acknowledge and agree that this Section is not intended to materially modify the manner in which Subscriber connects to and receives the Products and Services as of the Agreement Date. Travelport shall maintain sufficient capacity to accommodate reasonable fluctuations in demand and traffic.

Capacity Planning. 23 34. GRATUITIES............................................................. 23

Capacity Planning. Promptly following the Effective Date, the Parties shall establish and implement a capacity planning team ("CPT") that shall act as a unified body responsible for closely monitoring, anticipating, determining and communicating SPSS' AOL Sample needs to AOL, so as to enable both Parties to plan prospectively for the provision of adequate quantities of AOL Sample to SPSS as reasonably needed for SPSS projects from time to time during the Term. Without limiting the generality of the foregoing, AOL shall allocate not less than forty-five percent (45%) of the annual number of Level 1 Screened OP Users for distribution to SPSS for Level 2 Screening and project assignment in accordance with the agreements made by the CPT ("Capacity Allocation"). The Parties acknowledge and agree that AOL shall use commercially reasonable best efforts to provide a volume of AOL Sample necessary to fully satisfy SPSS' project execution needs on a project by project basis; provided, that AOL shall not be in breach of this Agreement if it (i) is unable to provide SPSS with a volume of AOL Sample in excess of the Capacity Allocation, (ii) does not provide the full Capacity Allocation to SPSS during any Agreement Year in which SPSS' project needs fall below the Capacity Allocation, or (iii) is unable to satisfy any request for AOL Sample by SPSS that does not meet the Reasonable Project Guidelines (as defined below). The Parties understand that (a) the exact number of OP Users will fluctuate by day, week and month, thereby making the role of the CPT essential to AOL's ability to satisfy SPSS' AOL Sample needs, (b) AOL shall be entitled to retain the volume of AOL Sample not allocated to SPSS (the 55% of Level 1 Screened OP Users not allocated for use by SPSS), for use in connection with internal projects and AOLTW Partner project needs; and (c) AOL may, as determined in its sole discretion, make use of any unused portion of the Capacity Allocation without paying SPSS for such use, unless AOL makes use of SPSS' market research services in connection with the use of such unused portion of the Capacity Allocation.

Capacity Planning. Conduct capacity analysis weekly (or more frequently if reasonably required) to plan for sufficient system capacity to handle anticipated peak loads. Work with the business units to develop business forecasts and track actuals against forecasts.