Viewing reports

The BMC Release Process Management product provides reports about your application deployments. The reports help you analyze how your application components are moving across the stages of deployment. The reports give you historical information, such as the total number of requests in the completed or problem state, time taken to complete the requests, a comparative view of the application versions deployed in various environments, and so on.

You can generate reports by filtering data in a variety of ways. You can also export this data to a .csv file and save it.

The following table describes the reports available in this release:

Report	Description
Process reports
Volume	Provides information about the total number of requests in the completed, problem, hold, or canceled state for each application for a specified period and matching the filter criteria. You can also set in-depth data filters to view this information for different applications, environments and processes. For more information about generating this report, see Volume Report.
Time to Complete	Provides information about the time required to complete the requests for each application during a specified period and matching the filter criteria. This report also provides statistical information, such as the minimum, maximum, median, and average time for requests to be completed. You can also set in-depth data filters to view this information for different applications, environments and processes. For more information about generating this report, see Time to Complete Report.
Problem Trend	Provides information about the number of requests in the problem state (that could not be completed successfully) for a specified period. This report also provides information about the users who created these requests. You can also set in-depth data filters to view this information for different applications, components, environments, request status, processes, work tasks, and so on. For more information about generating this report, see Problem Trend Report.
Time of Problem	Provides information about the time for which a request remained in the problem state for each user who created the request. This report also provides statistical information, such as the minimum, maximum, median, and average time for request steps between reporting (entering the problem state) and actually getting fixed (entering the completed state). This helps you determine how quickly a request in a problem state got fixed. You can also set in-depth data filters to view this information for different applications, components, environments, request status, processes, work tasks, and so on. For more information about generating this report, see Time of Problem Report.
Map reports
Component Versions Map by Application	Provides a comparative tabular view of the component versions of an application deployed in different environments. This report helps you determine which component of the application and which version of that component is in which environment. Example: Version 3 of Application 1 is in the Production environment and version 5 of Application 2 is in the Development environment. It helps you answer such questions as: Which component versions of an application have been deployed? In which environments are the component versions deployed? When were the component versions last deployed (date and time)? For more information about generating this report, see Component Versions Map by Application.
Properties Map by Environment or Application	Provides a comparative tabular view of the versions of the specified components of an application that are deployed in the specified environments. This report also provides historical information about the changes made to the component versions. It gives you a list of the different properties defined for the components that are deployed in different environments and tells you what changed in the property values and when the change occurred (date and time). It helps you answer such questions as: Which components of an application are deployed in which environment? What are the property values for that component? What change occurred in the property values (user name, password, and server name) when the component moved from one environment to the other? When did the change occur (date and time)? Which components were used in which release and in which environments were these components deployed? For more information about generating this report, see Properties Map by Environment or Application.
Servers Map by Application	Provides a tree view of the servers assigned to the applications. It provides data about the servers (physical or virtual) that an application is using. This report provides data about all the applications and assigned servers which are present in the database. It helps you answer such questions as: Which servers are being used? Which applications are using which servers? For more information about generating this report, see Servers Map by Application.
Servers Map	Provides a tree view of the servers assigned to the environments. It provides data about the environments in which the servers are installed. It helps you answer such questions as: Which servers are being used? Which environments are using which servers? Which server level instances are assigned to which environments? For more information about generating this report, see Servers Map.
Application Component Summary	Provides a tree view of the applications and the associated components deployed in environments. It provides data about applications, their associated components, and the environments in which these components are deployed. It helps you answer such questions as: Which application components are being used? Which components are deployed in which environment? Which applications are using which environments? For more information about generating this report, see Application Component Summary.

Viewing reports

Comments