Difference between revisions of "Coordinated Governance Model"
Line 1: | Line 1: | ||
+ | [[Image:Gov banner.jpg|Gov banner.jpg]] | ||
− | |||
__NOTOC__ | __NOTOC__ | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
− | <b>On April 9th, 2020, the GC Coordinated model & GC Digital Core template strategy was endorsed by GCEARB which included the following components:</b> | + | <b><big>On April 9th, 2020, the GC Coordinated model & GC Digital Core template strategy was endorsed by GCEARB which included the following components:</big></b> |
− | + | * Implementation of a “GC Coordinated Model” to enable the GC-wide transition to S/4 HANA and to deliver financial management transformation, utilizing a new operating and governance model. | |
− | + | * Implementation of a “GC Digital Core” to support the transformation, which would have functionality built once, and used everywhere. This will accelerate implementations, avoid duplicative costs, and reduce the risk in transition to S/4 HANA. | |
− | + | * Maximize technical architecture. | |
− | + | * Maximize deployment options / clustering by reducing the number of SAP instances within the GC. This approach should significantly reduce the investments and the on-going operating costs, moving forwar | |
− | + | <b><big>In summary and in practical terms, the proposed strategy suggests that we:</big> </b> | |
− | + | * In partnership with OGDs, standardize approximately 70% of our financial processes (paying a bill is paying a bill…) across the GC and let Departments “customize” 30% to meet their specific needs. | |
− | + | * Encourage / enable the “clustering” concept across GC; preliminary assessments suggest going from 18 instances to 11. | |
− | |||
− | |||
− | |||
− | <b> In summary and in practical terms, the proposed strategy suggests that we: </b> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | '''<big>Coordinated model & GC Digital Core template strategy: ''High level release strategy''</big>''' '' '' | ||
+ | * DCP GC Digital Core Release 2: Planning underway, and Information to be shared with departments in December | ||
+ | * Business Authority, Setting the stage for Release Management: December 2, 2020 | ||
+ | * Business Process Owner Board: December 9,2020 | ||
+ | * Launch of Digital Comptrollership Program Website: •December 2020 | ||
<multilang> | <multilang> | ||
@en|__NOTOC__ | @en|__NOTOC__ |
Revision as of 10:09, 16 December 2020
On April 9th, 2020, the GC Coordinated model & GC Digital Core template strategy was endorsed by GCEARB which included the following components:
- Implementation of a “GC Coordinated Model” to enable the GC-wide transition to S/4 HANA and to deliver financial management transformation, utilizing a new operating and governance model.
- Implementation of a “GC Digital Core” to support the transformation, which would have functionality built once, and used everywhere. This will accelerate implementations, avoid duplicative costs, and reduce the risk in transition to S/4 HANA.
- Maximize technical architecture.
- Maximize deployment options / clustering by reducing the number of SAP instances within the GC. This approach should significantly reduce the investments and the on-going operating costs, moving forwar
In summary and in practical terms, the proposed strategy suggests that we:
- In partnership with OGDs, standardize approximately 70% of our financial processes (paying a bill is paying a bill…) across the GC and let Departments “customize” 30% to meet their specific needs.
- Encourage / enable the “clustering” concept across GC; preliminary assessments suggest going from 18 instances to 11.
Coordinated model & GC Digital Core template strategy: High level release strategy
- DCP GC Digital Core Release 2: Planning underway, and Information to be shared with departments in December
- Business Authority, Setting the stage for Release Management: December 2, 2020
- Business Process Owner Board: December 9,2020
- Launch of Digital Comptrollership Program Website: •December 2020
Reference Materials[edit | edit source]
Link to the TBS policy that describes the mandate for GC EARB and outlines the related responsibilities for Departmental CIOs.
|
Business Capability Model (BCM) (right) The Government of Canada's Digital Standards form the foundation of the government's shift to becoming more agile, open, and user-focused. They will guide teams in designing digital services in a way that best serves Canadians. |
Application Lifecycle Management (right) Link to the criteria of when to come to EARB as well as the mandatory procedures to be incorporated.
|
GC Enterprise Architecture and the Architecture Standard including the GC view of B-I-A-T-S+P. |
“Presenter” intake presentation to be completed by departments.
|
Departmental Checklist (Right) Link to TBS directive with detailed requirements for APIs. |
Need help? Contact us.
|