Solve:Asset Modernization Guide

Solve:Asset was a mainframe-based system designed to manage and track IT assets within an organization. It provided a centralized view of hardware and software inventory, helping to optimize resource allocation and ensure compliance. The product was primarily used in z/OS environments.

Solve:Asset was an application that provided asset management capabilities. It offered features for tracking hardware and software assets, managing configurations, and generating reports. It was not a system in itself, but rather an application that ran on the z/OS operating system.

Solve:Asset was suitable for large enterprises that relied on mainframe systems for critical business operations. These organizations typically had complex IT infrastructures and needed a robust solution for managing their assets. Industries that commonly used Solve:Asset included banking, finance, insurance, and government.

An organization should have considered Solve:Asset when they needed a centralized solution for managing their IT assets on the mainframe. This included tracking hardware and software inventory, managing configurations, and ensuring compliance with regulatory requirements. It was particularly useful for organizations with complex IT infrastructures and a large number of assets to manage.

Alternatives to Solve:Asset include IBM Tivoli Asset Management for z/OS, BMC Helix Discovery, and ServiceNow IT Asset Management. These products offer similar capabilities for managing IT assets, but may have different features, pricing models, and deployment options. Organizations should evaluate their specific needs and requirements before choosing a replacement product.

Solve:Asset required a z/OS environment to run. It also required specific subsystems, such as CICS or IMS, to be installed and configured. The product relied on these subsystems for communication and data access. It also required a database, such as DB2, to store asset information.

Solve:Asset ran in an LPAR (Logical Partition) on the mainframe. It was dependent on the z/OS operating system and required specific subsystems, such as CICS or IMS, to be installed and configured. The product also required a database, such as DB2, to store asset information.

Solve:Asset was a standalone product, but it could integrate with other CA Technologies products, such as CA Solve:Central. This integration allowed for a more comprehensive view of the IT environment. However, it did not extend or enhance any specific product.

The main system components of Solve:Asset included the user interface, the data repository, and the reporting engine. The user interface allowed users to interact with the system and manage assets. The data repository stored asset information, and the reporting engine generated reports on asset usage and compliance.

Solve:Asset used a database, such as DB2, to store asset information. The product also used VSAM files for storing configuration data and other system information. These storage mechanisms were essential for the proper functioning of the product.

Solve:Asset provided several business benefits, including improved asset utilization, reduced costs, and enhanced compliance. By tracking hardware and software inventory, organizations could optimize resource allocation and avoid unnecessary purchases. The product also helped organizations comply with regulatory requirements by providing a centralized view of asset information.

If an organization did not use Solve:Asset, they would have faced challenges in managing their IT assets effectively. This could have led to inefficient resource allocation, increased costs, and compliance issues. The organization would have also lacked a centralized view of their IT environment, making it difficult to make informed decisions.

The typical licensing model for Solve:Asset was perpetual. This meant that organizations purchased a license to use the product indefinitely. The total cost of ownership included the initial license fee, as well as ongoing maintenance and support costs. There were also costs associated with implementation and training.

Solve:Asset integrated with enterprise ecosystems through its support for industry-standard protocols and APIs. This allowed the product to exchange data with other systems, such as service management platforms and configuration management databases. The integration capabilities of Solve:Asset enhanced its value and made it easier to manage IT assets across the enterprise.

Solve:Asset supported various authentication methods, including RACF, ACF2, and Top Secret. These methods allowed organizations to control access to the product and ensure that only authorized users could manage IT assets. The product also supported role-based access control (RBAC), which allowed administrators to assign specific permissions to users based on their roles.

Solve:Asset used a role-based access control (RBAC) model to control access to its features and data. This model allowed administrators to assign specific permissions to users based on their roles within the organization. For example, a system administrator might have full access to all features, while a help desk technician might only have access to view asset information.

Solve:Asset provided audit and logging capabilities to track user activity and system events. This information could be used to identify security breaches and ensure compliance with regulatory requirements. The product logged all user logins, logouts, and changes to asset information.

Solve:Asset controlled access to mainframe datasets by integrating with security systems such as RACF, ACF2, and Top Secret. These systems allowed administrators to define access rules and permissions for users and groups. The product also provided features for monitoring and auditing access to sensitive data.

Solve:Asset was typically deployed on-premise in a z/OS environment. The implementation required technical expertise in mainframe systems, including z/OS, CICS, and DB2. The implementation process involved installing the product, configuring the database, and integrating with security systems.

Implementing Solve:Asset required a high level of technical expertise in mainframe systems. This included knowledge of z/OS, CICS, DB2, and security systems. The implementation team needed to have experience in installing and configuring software on the mainframe, as well as integrating with existing systems.

Ongoing operational requirements for Solve:Asset included monitoring system performance, maintaining the database, and applying software updates. The product also required regular backups to ensure data integrity. The operational team needed to have expertise in mainframe systems and asset management.

Common implementation challenges for Solve:Asset included integrating with existing security systems, migrating data from legacy systems, and training users on the new system. The implementation team needed to have a clear understanding of the organization's IT environment and business requirements.