Difference between revisions of "Coordinated Governance Model"

From wiki
Jump to navigation Jump to search
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
[[Image:Gov banner.jpg|1000x10000px] "height=10"]
+
[[Image:Gov banner.jpg|Gov banner.jpg]]
 +
 
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__
  
  
 +
<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 forward
  
 +
<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.
  
 +
'''<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
 +
* Business Process Owner Board: December 2020
 +
* Launch of Digital Comptrollership Program Website: December 2020
 
<multilang>  
 
<multilang>  
 
@en|__NOTOC__
 
@en|__NOTOC__
Line 19: Line 33:
  
 
<!-- COLUMN 1 STARTS: -->  
 
<!-- COLUMN 1 STARTS: -->  
[[Image:Corporate-governance.jpeg |100px| left] ]]
+
[[Image:Education (1).png |100px| left] ]]
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 Heading 1 (left)]</b></span>
+
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 ARCHITECTURE REVIEW BOARD (left)]</b></span>
 +
 
 +
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
 +
 
  
Link to the TBS policy that describes the mandate for GC EARB and outlines the related responsibilities for Departmental CIOs.
 
 
<!-- COLUMN 1 ENDS: -->  
 
<!-- COLUMN 1 ENDS: -->  
  
Line 29: Line 47:
  
 
<!-- COLUMN 2 STARTS: -->  
 
<!-- COLUMN 2 STARTS: -->  
[[Image:thumb_digitalstandards.jpg |100px| left]]
+
[[Image:BPA.jpg|150px| left]]
<span style="font-size: 1.5em;"><b>[https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html Heading 2 (right)]</b></span>
+
<span style="font-size: 1.5em;"><b>[https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html BUSINESS PROCESS AUTHORITY BOARD (right)]</b></span>
 +
 
 +
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
  
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.
 
 
<!-- COLUMN 2 ENDS: -->  
 
<!-- COLUMN 2 ENDS: -->  
 
|}
 
|}
Line 45: Line 66:
 
<!-- COLUMN 1 STARTS: -->  
 
<!-- COLUMN 1 STARTS: -->  
 
[[Image:directive.png |100px| left]]
 
[[Image:directive.png |100px| left]]
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Heading 3 (right) ]</b></span>
+
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Application Lifecycle Management (right) ]</b></span>
  
 
Link to the criteria of when to come to EARB as well as the mandatory procedures to be incorporated.
 
Link to the criteria of when to come to EARB as well as the mandatory procedures to be incorporated.
Line 55: Line 76:
 
<!-- COLUMN 2 STARTS: -->  
 
<!-- COLUMN 2 STARTS: -->  
 
[[Image:thumb_archstandards.jpg |100px| left]]
 
[[Image:thumb_archstandards.jpg |100px| left]]
<span style="font-size: 1.5em;"><b>[[GC_Enterprise_Architecture | Heading 4 (right)]]</b></span>
+
<span style="font-size: 1.5em;"><b>[[GC_Enterprise_Architecture | Release Management (right)]]</b></span>
  
 
GC Enterprise Architecture and the Architecture Standard including the GC view of B-I-A-T-S+P.
 
GC Enterprise Architecture and the Architecture Standard including the GC view of B-I-A-T-S+P.
Line 70: 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:GC_EARB_Presenter_Template-2020-11-26.pptx | Heading 5 (left)]]</b></span>
+
<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:GC_EARB_Presenter_GENERAL_2019-09-13_FR.PPTX | French Presenter Template]]
+
[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_FR.pptx | French Presenter Template]]
 
<!-- COLUMN 1 ENDS: -->  
 
<!-- COLUMN 1 ENDS: -->  
  
Line 81: Line 102:
 
<!-- COLUMN 2 STARTS: -->  
 
<!-- COLUMN 2 STARTS: -->  
 
[[Image:API.png |100px| left]]
 
[[Image:API.png |100px| left]]
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32604 Heading 6 (Right)]</b></span>
+
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32604 Departmental Checklist (Right)]</b></span>
  
 
Link to TBS directive with detailed requirements for APIs.
 
Link to TBS directive with detailed requirements for APIs.
Line 87: Line 108:
 
|}
 
|}
  
 
 
<!-- FOOTER -->
 
 
 
{| width="100%" cellpadding="10"
 
 
|-valign="top"
 
|style="color:#008080;"|
 
<!-- COLUMN STARTS: -->
 
<div style="font-size: 1.8em; text-align:center;">Need help? Contact us.</div>
 
 
 
 
<!-- COLUMN 1 STARTS: -->
 
{| width="100%" cellpadding="5"
 
 
|-valign="top"
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: Envelope_icon.png  |100px | center]]
 
<div style="font-size:1.5em; text-align:center; color:white;">{{em|ZZCIOBDP@tbs-sct.gc.ca}}</div>
 
<!-- COLUMN 1 ENDS: -->
 
 
<!-- COLUMN 2 STARTS: -->
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: Cop_icon.png |100px | center]]
 
<div style="font-size:1.5em; text-align:center;">[https://gccollab.ca/groups/profile/1896301/enenterprise-architecture-community-of-practicefrcommunitu00e9-de-pratique-de-architecture-integru00e9e Enterprise Architecture Community of Practice]</div>
 
<!-- COLUMN 2 ENDS: -->
 
 
<!-- COLUMN 3 STARTS: -->
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: gcconnex_icon.png  |100px | center]]
 
<div style="font-size:1.5em; text-align:center;">[https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en GCconnex]</div>
 
<!-- COLUMN 3 ENDS: -->
 
<!-- TABLE ENDS --> |}
 
 
<!-- COLUMN ENDS: -->
 
 
<!-- TABLE ENDS --> |}
 
  
 
<!-- end -->
 
<!-- end -->
 
 
 
 
 
  
 
<!-- FRENCH -->
 
<!-- FRENCH -->
Line 203: 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:GC_EARB_Presenter_GENERAL_2019-09-13_FR.PPTX | Modèle du présentateur du GC CEAI]]</b></span>
+
<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:GC_EARB_Presenter_GENERAL_2019-09-13.PPTX | Modèle du présentateur anglais]]
+
[[Media:2022-11-30_GC_EARB_Presenter_GENERAL_EN.pptx | Modèle du présentateur anglais]]
 
<!-- COLUMN 1 ENDS: -->  
 
<!-- COLUMN 1 ENDS: -->  
  
Line 212: Line 189:
 
|width="50%" style="color: black;" |
 
|width="50%" style="color: black;" |
  
<!-- COLUMN 2 STARTS: -->
 
[[Image:API.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=32604 Procédures obligatoires sur les interfaces de programmation d’applications]</b></span>
 
 
Lien vers la directive du SCT avec les exigences détaillées pour les API.
 
<!-- COLUMN 2 ENDS: -->
 
|}
 
 
 
 
<!-- FOOTER -->
 
 
 
{| width="100%" cellpadding="10"
 
 
|-valign="top"
 
|style="color:#008080;"|
 
<!-- COLUMN STARTS: -->
 
<div style="font-size: 1.8em; text-align:center;">Besoin d’aide? Communiquez avec nous.</div>
 
 
 
 
<!-- COLUMN 1 STARTS: -->
 
{| width="100%" cellpadding="5"
 
 
|-valign="top"
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: Envelope_icon.png  |100px | center]]
 
<div style="font-size:1.5em; text-align:center; color:white;">{{em|ZZCIOBDP@tbs-sct.gc.ca}}</div>
 
<!-- COLUMN 1 ENDS: -->
 
 
<!-- COLUMN 2 STARTS: -->
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: Cop_icon.png |100px | center]]
 
<div style="font-size:1.5em; text-align:center;">[https://gccollab.ca/groups/profile/1896301/enenterprise-architecture-community-of-practicefrcommunitu00e9-de-pratique-de-architecture-integru00e9e Communité de pratique de architecture integrée]</div>
 
<!-- COLUMN 2 ENDS: -->
 
 
<!-- COLUMN 3 STARTS: -->
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#008080;"|
 
[[Image: gcconnex_icon.png  |100px | center]]
 
<div style="font-size:1.5em; text-align:center;">[https://gcconnex.gc.ca/groups/profile/29755185/gc-enterprise-architecture-review-board-comite-dexamen-de-larchitecture-dentreprise-du-gc?language=en GCconnex]</div>
 
<!-- COLUMN 3 ENDS: -->
 
<!-- TABLE ENDS --> |}
 
 
<!-- COLUMN ENDS: -->
 
 
<!-- TABLE ENDS --> |}
 
  
 
<!-- end -->
 
<!-- end -->
 
</multilang>
 
</multilang>
 +
{{OCIO_GCEARB_Footer}}

Latest revision as of 14:05, 14 December 2022

Gov banner.jpg



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]

left] 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



BPA.jpg

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


Directive.png

Application Lifecycle Management (right)

Link to the criteria of when to come to EARB as well as the mandatory procedures to be incorporated.


Thumb archstandards.jpg

Release Management (right)

GC Enterprise Architecture and the Architecture Standard including the GC view of B-I-A-T-S+P.


Thumb presentertemp.jpg

Operations Guide (left)

“Presenter” intake presentation to be completed by departments.

French Presenter Template


API.png

Departmental Checklist (Right)

Link to TBS directive with detailed requirements for APIs.