Difference between revisions of "Coordinated Governance Model"
(One intermediate revision by one other user not shown) | |||
Line 91: | Line 91: | ||
<!-- COLUMN 1 STARTS: --> | <!-- COLUMN 1 STARTS: --> | ||
[[Image:thumb_presentertemp.jpg |100px| left]] | [[Image:thumb_presentertemp.jpg |100px| left]] | ||
− | <span style="font-size: 1.5em;"><b>[[Media: | + | <span style="font-size: 1.5em;"><b>[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx | Operations Guide (left)]]</b></span> |
“Presenter” intake presentation to be completed by departments. | “Presenter” intake presentation to be completed by departments. | ||
− | [[Media: | + | [[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx | French Presenter Template]] |
<!-- COLUMN 1 ENDS: --> | <!-- COLUMN 1 ENDS: --> | ||
Line 180: | Line 180: | ||
<!-- COLUMN 1 STARTS: --> | <!-- COLUMN 1 STARTS: --> | ||
[[Image:thumb_presentertemp.jpg |100px| left]] | [[Image:thumb_presentertemp.jpg |100px| left]] | ||
− | <span style="font-size: 1.5em;"><b>[[Media: | + | <span style="font-size: 1.5em;"><b>[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx | Modèle du présentateur du GC CEAI]]</b></span> |
La présentation des demandes du « présentateur » doit être remplie par les ministères. | La présentation des demandes du « présentateur » doit être remplie par les ministères. | ||
− | [[Media: | + | [[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx | Modèle du présentateur anglais]] |
<!-- COLUMN 1 ENDS: --> | <!-- COLUMN 1 ENDS: --> | ||
Latest revision as of 14:05, 14 December 2022
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 forward
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
- Business Process Owner Board: December 2020
- Launch of Digital Comptrollership Program Website: December 2020
Reference Materials[edit | edit source]
ARCHITECTURE REVIEW BOARD (left) Team of Architects who will define and maintain the target architecture and overall roadmap Review board with 2 representatives from each cluster to finalise all proposals from the arb and COE to the business authority
|
BUSINESS PROCESS AUTHORITY BOARD (right) Team of business and functional experts per line of business with Business Process Owners as Co-Leads, endorsing decisions DCFOs Business Process Owners’ role is to maintain process integrity, review and validate business requirements and master data per line of business |
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. |