Entering Action Plan Information
Before proposing an action plan for approval, the action plan creator may supplement Action Plan information.
To update fields that characterize an action plan:
Open the Characteristics properties pages of the action plan that interests you.Several sections appear.
General characteristics
In the Characteristics section, you can specify the following:
• Name
• Owner: is the user responsible for submitting the action plan to the approver and for proposing the action plan closing when all the actions are closed.
For more details on the owner tasks, see Action Plan Execution.• Tags
• Owner Entity: enables restriction of the list of owners.
• Approver: is the user responsible for validating the action plan closing.
For more details on the approver tasks, see Action Plan Execution.• Means: text description of means required/desired for action plan execution.
• Priority: enables indication of a priority level of the action plan. Possible values are:
• “Low”,
• "Medium"
• “High” or
• "Critical".
• Origin: enables definition of the context of carrying out the action plan:
• "Audit",
• "Compliance",
• "Event",
• “Risk”, “RFC”
• “Other”.
• Category: enables specification of the action plan undertaken, for example: "Process Improvement".
• Nature: enables definition of the action plan nature “preventive” or “Corrective”.
• Description: enables to specify additional information on the action plan and its characteristics.
• Steering Calendar: enables to connect an existing steering calendar to the action plan.
A steering calendar enables performing recurring actions at predefined due dates. It can be used for example for sending recurrent reminders to the action plan responsibles so that they can indicate progress of this element. A steering Calendar can also be used to automatically trigger assessment Assessment Sessions at regular intervals. For more details on the use of the steering calendar, see Using Steering Calendars.• Action Plan Status: automatically updated depending on the action plan progress.
For more details on action plan statuses, see Action Plan Execution.Financial assertion
In the Financial assertion section, you can enter financial information that facilitate action plan cost monitoring.
• Forecast Cost: estimate of action plan cost expressed in current currency.
• Real Cost: action plan real cost expressed in currency current.
• Forecast Cost (Man-Days): estimate in man-days of action plan implementation workload.
• Real Cost (Man-Days): cost of action plan implementation expressed in man-days .
Action plan progress
In the Progression History section, you can enter progression status to facilitate the progression follow-up.
For more details on managing action plans progress, see Specifying Action Plan Progress Rate.Success factors
In the Success Factors and Outcome section, you can specify the success indicators enabling assessment of success of the action plan.
• Key Success Factor: text information on action plan success factors.
• Outcome: information on action plan result:
• Unknown
• Failed
• Succeeded
• Comments on Outcome: text information on action plan results.
Scope
You can associate objects with the action plan to position it in its environment.
Depending on the products you have, you can connect objects of the following types:
• risk
• organizational process
• business processes
• control
• entity
• application
• software technology
• touchpoint
• issue
• data asset
Milestones
Milestones are important dates of the action plan. You can specify these dates later.
• Planned Begin Date and Real Begin Date.
• Planned End Date and Real End Date.
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.