Execution Campaign Principle
Preparing Execution Campaigns
To be able to create an execution campaign, preparatory work is required at the level of controls. You must:
• connect processes to controls
• define questions on controls
For this you must define control steps (questionnaire templates).• define control execution calenders
You must specify a steering calendar on each control to execute. See Defining Control Execution Calendars.• define check-list respondents, who are control owners for a specific entity.
See Defining Respondents.Control Execution Periodicity
An execution campaign groups several execution sessions.
Each campaign session groups a set of controls to be executed on the same date.
Several assessment sessions are created in parallel for each steering calendar type identified.
For example:
a session is created each week if a weekly steering calendar has been specified on certain controls
a session is started each day if a daily steering calendar has been specified on certain controls
Controls are therefore grouped in each session according to the steering calendar to which they have been connected.
See also: Examples of Session Automatic Launch.
Assessment Template Specific to Control Execution
Execution campaigns are automatic assessment campaigns with a specific assessment template.
The "Control Execution" assessment template is selected by default at execution campaign creation. This assessment template:
• prompts you to specify an entity.
• is used to identify controls used by processes attached to this entity and its sub-entities.
Check-list respondents are control owners in an entity or in sub-entities.