Capacity Management. The Client acknowledges that:
Capacity Management. Network capacity, utilisation, disk utilisation and load are proactively monitored, with automated alerting, to ensure that the SaaS Service has sufficient capacity of current and anticipated needs.
Capacity Management. Capacity Management will assess the business requirements (the required service delivery), the organization’s operation (the current service delivery), the IT infrastructure (the means of service delivery), and will ensure that capacity in all areas of IT service provision and support always exists and is matched to the current and future agreed needs of the business, within designated timeframes. Service Provider’s responsibilities include:
Capacity Management. Planet Payment will be responsible for monitoring Planet Payment application and system utilization in order to ensure service is provided in accordance with this Agreement.
Capacity Management. The Customer is responsible for ensuring that the Size of the additional Service matches the demand of the application. The Size of the additional Service needs to take into account overhead due to various data protection-related platform components, e.g., intrusion detection, log collection, and metrics collection. Load testing is recommended for Standard Plan Environments and is mandatory for Premium Plan Environments to ensure additional Services are properly sized. Load testing is described at: xxxxx://xxxxxxxxx.xx/compliantkubernetes/user- guide/go-live/
Capacity Management a) A documented policy and process exists to evaluate current capacity against projected requirements.
Capacity Management. DYONYX will monitor at a minimum the following items: • Storage utilization • CPU utilization (Physical and Virtual Servers) • Memory utilization (Physical and Virtual Servers) • Internet utilization DYONYX will notify the Customer when capacity thresholds are exceeded. DYONYX will not be held accountable for missed Service Levels due to the Customer’s delay in authorizing additional capacity once notified by DYONYX of potential outages. Capacity management Service Levels are defined in Table 6. Table 6 Capacity Management Service Levels Service Level Category Service Level Metric Comments Capacity Thresholds (Metric 13) Notify Customer of all thresholds exceeding 80% of utilization or other agreed upon thresholds Thresholds to be determined jointly by Customer and DYONYX. As a proactive measure, auto alerts will be set for utilization thresholds to notify DYONYX and Customer when thresholds are exceeded.
Capacity Management. The Contractor shall manage current IT resources and ensure resources are effectively used to meet current capacity requirements. The Contractor shall identify current application and infrastructure bottlenecks for corrective action, system utilization, growth patterns, and future demands that impact system capacity so proactive actions can be taken by the PMO to adjust system resources. The Contractor shall perform capacity planning to accommodate for usage growth through scaling of existing infrastructure (servers, licenses, storage, bandwidth, etc.) and emerging technologies. This growth can include new users, higher levels of usage (more concurrent users), hosting and integration of additional applications and web services, continued migration of capabilities to the GCSS-MC/LCM Increment 1 system, connection of additional interfaces or data feeds, creation of new dashboard/analytics applications and services, and federation with other systems. The Contractor shall provide a weekly GCSS-MC Enterprise NIPRNet Capacity Report that includes information related to service, resource use, and performance. The Contractor shall document current system use and forecast requirements, to maintain an annual Capacity Plan. The Contractor shall include recommended applicable machine modifications and/or additional equipment to increase the capacity of the system in the plan. The Contractor shall perform capacity and forecasting for Production based on current needs and future development plans.
Capacity Management. A business providing a service to a customer or customers needs to have sufficient resources to meet the customer requirements. More specifically, in the case of a business providing preservation services, sufficient hardware needs to be in place to meet the SLAs agreed with their customer(s). Knowledge of future trends is also necessary to correctly judge what additional hardware to purchase. This chapter looks at the relationship between the SLAs and the hardware requirement and various techniques for managing the capacity of the service. The sorts of questions that must be addressed to successfully manage a service are: o What resources do I need now and in the future to meet the terms of a proposed SLA? o How much will it cost me? o What effect will a change in software or hardware have on the system performance? o Will the existing SLAs still be sufficiently resourced? We can go through the example quality of service and constraint terms proposed in Chapter 5 to see how they have an impact on the underlying hardware requirements: ID Name Discussion Impact on QS-01 Availability A high availability for servers (e.g. for ingest or access) implies reliable hardware and/or redundant systems with automatic fallover. The servers must also have reliable access to the data so duplication of the data storage is also implied. + external servers + networking + storage QS-02 Integrity An integrity guarantee implies duplication of data storage in some way and processes in place to check the data integrity and repair where necessary which implies additional CPU and storage bandwidth to deal with these processes. + storage + CPU + networking QS-03 SIP ingestion time To rapidly process a SIP (extract, validate, index and transform) requires sufficient external bandwidth, fast servers and sufficient servers to ingest SIPs in parallel + external servers + CPU + external networking + internal networking + tier 1 storage QS-05 DIP delivery time Delivering a DIP requires retrieving the AIP and packaging it as a DIP. Sufficient bandwidth is also required to the customer. + external servers + CPU + external networking + internal networking + speed of storage QS-06 Search time The search time depends on the speed and capacity of the metadata database and the external search server(s) + external servers + database servers C-01 Authorised formats The constraint on which formats are authorised has no direct effect on the hardware. It is accounted for in the validation stage of...
Capacity Management. Using forecasted loads from Client for new projects and the evolution of existing services and projected growth volumes, this process defines what resources will be required to cover Client demands. FIS will provide capacity management services for CPU and web resources, DASD and tape. Client will participate in and provide drivers for the capacity planning process.
