Characterizing Action Plans
See also Creating Action Plans.To specify action plan properties:
1. In the HOPEX IRM desktop, select Test > Remediation > Remediating Action Plans > All Issue-Remediating Action Plans
2. Open the properties of the action plan.
General characteristics
You can specify the following information:
• Name: action plan name.
• Owner:by default the user who created the action plan.
• Owner Entity: entity responsible for action plan implementation.
• Approver: user responsible for validation of the action plan when all actions are completed.
• Means: text description of means required/desired for action plan execution.
• Priority: enables indication of a level. Priority can be:
• "Low"
• "Medium"
• "High"
• "Critical"
• Organizational Level: final objective of plan; this can be:
• "Global"
• "Local"
• Origin: enables definition of the context of carrying out the action plan:
• "Audit"
• "Compliance"
• "Event"
• "Risk"
• "RFC"
• "Other".
• Category: the action plan can for example be connected to:
• risk impact reduction
• project management
• process improvement
• control performance improvement
• etc.
• Other values are available.
• Nature: enables definition of whether the action plan is:
• Corrective
• Preventive
• Comment: supplements information on the action plan and its characteristics.
• Steering Calendar: used for sending reminders to the person responsible for an action plan so that they can indicate action plan progress.
A steering calendar for monthly reminder of progress is supplied by default.Financial assertion
• Forecast Cost: action plan cost estimate.
• Forecast Cost (Man-Days): estimate in man-days of action plan implementation workload.
RACI
The user defined as action plan Responsible is responsible for definition of actions to be carried out and their execution.
This field is specified with the name of the action plan creator or with the name of the action plan approver.
For more details on the use of RACI, see Responsibilities concerning Controls.Success factors
In the Success Factors section, you can specify in text the success indicators enabling assessment of success of the action plan.
Scope?
To position an action plan in its environment, you can associate objects with the action plan in the Scope section.
You can connect objects of the following types:
• controls
• applications
• risks
• entities
• processes
• incidents
Milestones
Milestones are key dates of the action plan.
The planned end date is mandatory.Attachments
You can attach business documents to an action plan:
For more details on the use of business documents, see the HOPEX Common Features guide.