7
Workflows supporting the Stratex Framework November 2016

Workflows supporting the Stratex Framework

Embed Size (px)

Citation preview

Page 1: Workflows supporting the Stratex Framework

Workflows supporting the Stratex FrameworkNovember 2016

Page 2: Workflows supporting the Stratex Framework

Purpose

Purpose

The purpose of this presentation is to outline the workflows that support the Stratex Framework and are designed to drive timely completion of key GRC Processes.

Topics covered Asses and Update

Page 3: Workflows supporting the Stratex Framework

3

Assess & Update workflows

Within the Stratex Framework, one of the central workflows is the one that drive the regular update and assessment of items.

This includes; Indicator (KPIs, KRIs & KCIs) update Risk Assessment Control Assessment Control Certification Initiative Update Actions Update Audit Update Issue Update Test Update

Page 4: Workflows supporting the Stratex Framework

4

Key fields that trigger the Assess & Update workflows

To trigger the Assess & Update workflow, the following three fields within the Stratex Framework must be completed;

Updater – this is the person who is the ‘data provider’ to complete the update or assessment

Update Frequency – this sets the frequency with which the item is updated or assessed. The options are; Annual, Bi-Annual, Quarterly, Monthly, Weekly, Daily and Ad hoc.

Update Method – this determines how the item is updated. By default it is set to ‘Manual’. Setting it to automatic will trigger a process whereby StratexPoint will import data from Line of Business systems.

Another field which relates to the Assess & Update workflow is the Update Due. This field can be manually set, particularly when an item is added to the framework, however this field is updated by the system.

Page 5: Workflows supporting the Stratex Framework

5

Update Due

The Update Due field can be set when an item is added to the Stratex Framework, however it is maintained/updated by the system.

The Update Due field is used to show when an item is ‘due’ however this means slightly different things for ‘updates’ and ‘assessments’.

Updates relate to items which are predominantly quantitative in nature i.e ‘data-driven’ such as indicators, initiatives, issues and actions % complete. These items will show as due after the update due date because only then will the data be available to input or import.

Assessments relate to items which are predominantly qualitative in nature. In StratexPoint this includes Risk Assessments and Control Assessments.These items will show as due, within the period before the update due.

Page 6: Workflows supporting the Stratex Framework

6

When the Update Due Date is 30 June and Update Frequency is set to Quarterly.

Data for the Period ending June 30 should be updated as shown. The entered data is held against the period end date i.e June 30. Once updated (or assessed), the Update Due Date is set to 30 Sept.

When is an item due i.e when does it appear in the Stratex Update webpart?

1 Jan 31 Mar. 30 June 30 Sept. 31 Dec.

Period Start Period EndControl AssessmentRisk Assessment

Initiative UpdatesIndicators UpdatesControl Certifications

Action UpdatesAudit UpdatesIssue UpdatesTest Updates

Page 7: Workflows supporting the Stratex Framework

Workflows supporting the Stratex FrameworkNovember 2016