This section contains the following topics:
How to Set up for Incident Financial Defaults
Before a resource can enter financial data for incidents, do the following:
For more information, see the Financial Management User Guide.
Investments only support investment-level allocations and chargebacks.
Part of setting up Demand Management is to create logical groups of investments named incident categories. Incident categories let you classify incidents of a particular type. They allow you to configure logical groupings of incidents that reflect your organization structure. You can then create and associate investments with these incident categories.
In small organizations, where resources work with all incident categories, you can add all resources to a group. Then assign the group to an incident category. In a larger organization, where resources are specialists, you can create groups, and add resources to groups based upon their expertise. Then assign the groups to different incident categories.
Once you have created incident categories, resources can log incidents. Next, define the incident category properties, associate your investments with incident categories, and grant resources, groups, and OBS units access to the incident category.
Use the Create Incident Category page to create an incident category.
Follow these steps:
The setup page appears.
The create page appears.
Defines the short name for the incident category.
Defines the unique identifier for the incident category.
Defines a brief description.
Once you catalog your investments, you can associate investments-assets, applications, products, services, and other work-with incident categories individually or using a batch process. For example, you can associate the monitor, keyboard, and mouse assets with the Hardware: Peripherals incident category.
You can also associate investments with an incident category from the incident.
Before associating your investments with an incident category, select the affected investments within an incident category.
Follow these steps:
The setup page appears.
The properties page appears.
Use the Access to this Category pages to control resources, groups, and OBS units that have access to an incident category.
Follow these steps:
The setup page appears.
The properties page appears.
Displays a list of all resources, groups, and OBS units having access to the incident category. Also, the access rights of resources, groups, and OBS units have to this category.
Defines the resources to grant access to this incident category.
Defines the groups to grant access to this incident category.
Defines the OBS units to grant access to this incident category.
Note: The list of entities that appears depends upon your selection.
Use the incident priority matrix to escalate incidents based on impact and urgency. You can set the priority levels for the matrix. For example, low, medium, or high. The impact values are plotted against the urgency values. The intersection of every impact and urgency value becomes the incident priority.
When you save an existing incident, the incident priority is recalculated based on changes made to the incident priority matrix.
Follow these steps:
The setup page appears.
CA Clarity PPM is often not the primary data source for incidents. You can use the XML Open Gateway to capture incidents from other systems and bring them into CA Clarity PPM. Often incidents are imported with incomplete investment data. The incidents can have individual effort entries not associated with an investment. In this case, you can assign a single investment to all such effort entries.
For more information, see the XML Open Gateway Developer Guide.
Follow these steps:
The setup page appears.
The investment is assigned to the incident.
CA Clarity PPM provides the following jobs for incidents:
Follow these steps:
The setup page appears.
|
Copyright © 2013 CA.
All rights reserved.
|
|