Capacity Management

According to ITIL, Capacity can be defined as "The maximum throughput that a configuration item or IT service can deliver. For some types of CIs, the capacity may be the size or the volume - for example, a disk drive".

Capacity Management can be defined as "The process responsible for ensuring that IT service capabilities and IT infrastructure are able to meet agreed capacity and performance requirements in a timely and cost-effective manner".

Capacity Management considers all the resources needed to deliver an IT service and addresses the attendance of current and future capacity and performance needs of the business.

Distinguishes between capacity and performance targets and measures (per the following definitions):

Vendor response: Yes, the platform can distinguishes between capacity and performance targets and customer can check both information on dashboard in realtime.

Capacity:



Performance:



Manages the capacity aspects of individual components that must include, at a minimum:

Manages the performance of services that must include, at a minimum:  

Vendor response: Yes, the platform allow customer manage individual capacity and end-to-end capacity/performance.



End-to-End





Supports the identification and use of the following non-technical elements as these may affect capacity, service performance, and capacity planning. This  must include, at a minimum: 

Vendor response: Yes, using capacity types can define financial, integrated with Financial Process and workforce linked with project process or via API with HR ERP.











Service models can be defined by the client, against which end-to-end service performance and related component capacity can be monitored, measured, and reported.

Vendor response: Yes, the platform allow aggregate components and check capacity and performance for each one





Capacity and performance modeling, optimization, and forecasting for planned service updates and new services can be managed.

Vendor response: 

Forecast



Mapa 4Biz forecast test

Capacity plans for the current and future capacity and performance requirements can be managed. 

Vendor response: Yes use capacity map or capacity forecast





Capacity and performance targets for all elements can be recorded and can be linked or related to appropriate records in the service and component repository.

Vendor response: Yes on platform customer can define the capacity target



Capacity and performance targets for all elements can be recorded and can be linked to or related to appropriate service and internal support agreements.

Vendor response:



Capacity and performance aspects can be recorded and managed, supporting the calculation and reporting of capacity and performance metrics. 

Capacity and performance data from multiple sources can be aggregated. 

While capacity or performance aspects can be entered manually, at a minimum, this information should be able to be captured through system monitoring. 

Vendor response: Yes, the platform support individual and total capacity from each service component and total service capacity/performance. If some threshold broke the platform can trigger an event, incident, problem or change





Capacity and performance issues can be related to or linked to incident and problem records for investigation and support.

Vendor response: Platform can create incident, problem and change based on capacity alerts





Performance and capacity issues can be applied to the component record in the service and component repository, which can then be accessed by and visible to incident and problem investigations. 

Vendor response: Platform can create incident, problem and change based on capacity alerts.

Incident



Problem



Capacity and performance metrics can be presented in dashboards for real-time, actionable support. 

Vendor response: Yes, all capacity individual or performance can be presented in real time dashbords.





Alert thresholds can be defined, against which notification of pending or breached capacity and performance issues can be triggered. This can be done at the service (performance) and component (capacity) levels and defined by the client.

Vendor response: Yes, the alert system allows trigger notification based on thresholds and pre-defined scope



Initiates related continuity or disaster recovery plans and notifications through predefined continuity thresholds related to capacity or performance.

Vendor response: Critical incidents can trigger continuity plans after approved



Calculates and reports capacity and performance metrics for all elements and links or provides these metrics to the appropriate service or component record in the repository. 

Vendor response: Platform Dashboards calculate on real time capacity and performance metrics for all elements and links or provides these metrics to the appropriate service or component record in the repository



Calculates and reports capacity and performance metrics for all elements and links or provides these metrics for the appropriate agreements and performance reporting.

Vendor response: Platform Dashboards calculate on real time performance metrics for all elements and links or provides these metrics to the appropriate service or component record in the repository



Manages and reports capacity utilization trends for an analysis of capacity planning, for all elements.

Vendor response: Yes, use service map and dashboard for check trend analysis for all elements. Including performance trends using machine leraning.



Automated scaling and load balancing can be supported or managed. 

Vendor response: Yes, use pipeline for trigger infrastructure needs like as create new component, auto scaling or HA.



Supports measuring a synthetic transaction of the availability and reliability of a service that defines the expected outcome, criteria, and scope of the measurement.

Vendor response: Yes, the platform give an APM for check all transaction metrics