Capacity Management Analytics Modernization Guide

Capacity Management Analytics provided historical reporting, trend analysis, and forecasting of z/OS systems. It leveraged data from SMF records to identify resource bottlenecks and optimize system performance. Reports could be generated on CPU utilization, storage consumption, and network activity.

The product used Tivoli Decision Support as its base reporting engine. It also incorporated Cognos 8 Business Intelligence for advanced analytics and visualization. IBM SPSS Modeler was used for predictive modeling and forecasting.

Capacity Management Analytics supported data extraction from SMF records. It used predefined data models and ETL processes to transform the raw data into a usable format for reporting. Users could customize reports and dashboards to meet their specific needs.

Capacity Management Analytics relied on the underlying capabilities of Tivoli Decision Support, Cognos, and SPSS. Specific commands would vary depending on the component being used. For example, in Tivoli Decision Support, users might use commands to define reports, schedule data extracts, and manage users.

The architecture included components such as the data warehouse, ETL processes, reporting engine (Cognos), and modeling engine (SPSS). These components communicated through standard protocols and APIs. The data warehouse typically used a relational database such as DB2.

Capacity Management Analytics did not expose a public-facing API in the modern sense (REST, etc.). Integration was typically achieved through data exchange with the underlying components (Tivoli Decision Support, Cognos, SPSS).

By providing insights into resource utilization and performance bottlenecks, Capacity Management Analytics helped organizations optimize their z/OS environments. This could lead to reduced hardware costs, improved application performance, and better service levels.

The product helped organizations make data-driven decisions about capacity planning and resource allocation. By identifying trends and predicting future resource needs, it enabled proactive management of the z/OS environment.

Security was primarily handled by the underlying components (Tivoli Decision Support, Cognos, SPSS). These products supported various authentication methods, including LDAP and integration with z/OS security systems such as RACF, ACF2, and Top Secret.

Access control was typically role-based (RBAC), with users assigned to roles that defined their permissions within the system. Audit logging was available to track user activity and system events.

Administration involved configuring the various components (Tivoli Decision Support, Cognos, SPSS), managing users and permissions, and scheduling data extracts and reports. Monitoring capabilities were provided by the underlying platforms.

The product relied on the logging capabilities of the underlying components. Logs could be used to troubleshoot issues, monitor system performance, and track user activity.