Difference between revisions of "GC Enterprise Architecture"

From wiki
Jump to navigation Jump to search
 
(56 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<!-- NAV -->
+
{{OCIO GCEA Header}}
 +
<multilang>
 +
@en|
 +
== Definition ==
 +
Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, and security domains to support strategic outcomes.  
  
{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center"
+
== Mandate ==
|-
+
The ''<u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 Policy on Service and Digital]</u>'' and supporting instruments serve as an integrated set of rules that articulate how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. Other requirements, including but not limited to, requirements for privacy, official languages and accessibility, also apply to the management of service delivery, information and data, information management and cyber security. Those policies, set out in Section 8, must be applied in conjunction with the Policy on Service and Digital. The Policy on Service and Digital focuses on the client, ensuring proactive consideration at the design stage of key requirements of these functions in the development of operations and services. It establishes an enterprise-wide, integrated approach to governance, planning and management. Overall, the Policy on Service and Digital advances the delivery of services and the effectiveness of government operations through the strategic management of government information and data and leveraging of information technology, supporting the mandate of the Minister for Digital Government in leading the Government of Canada’s digital transition. The management of these functions is guided by a commitment to the guiding principles and best practices of the Government of Canada Digital Standards: design with users; iterate and improve frequently; work in the open by default; use open standards and solutions; address security and privacy risks; build in accessible from the start; empower staff to deliver better services; be good data stewards; design ethical services; collaborate widely.
|-
 
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="6%" | '''[[GC_Enterprise_Architecture|<span style="color: snow">'''Home'''</span>]]'''
 
  
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Government_of_Canada_Architectural_Standards|<span style="color: Snow">'''EA standards'''</span>]]'''  
+
Section 4.1.2.3 of the ''Policy on Service and Digital''. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to '''enterprise architecture'''.
  
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="13%" | '''[[Past_Endorsed_Architectural_Decisions|<span style="color: Snow">'''EARB Endorsements'''</span>]] '''
+
Section 4.1.2.4 of the ''Policy on Service and Digital''. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an '''enterprise architecture''' review board that is mandated to '''define current and target architecture standards''' for the Government of Canada and review departmental proposals for '''alignment'''.
  
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Enterprise_Architecture_Artifacts|<span style="color: Snow">'''EA Artifacts'''</span>]] '''
+
The Directive on Service and Digital articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.
  
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="12%" | '''[[Architecture_Discussions|<span style="color: Snow">'''Working Groups'''</span>]] '''
+
Section 4.1.1.1 of the ''<u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]</u>''. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental '''architecture''' review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with '''enterprise architectures.'''
 
+
@fr|
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[GC EARB|<span style="color: Snow">'''GC EARB'''</span>]] '''
+
To be translated
 
+
</multilang>
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="9%" | '''[[Monitoring_Architectural_Implementation|<span style="color: Snow">'''Other References'''</span>]] '''
 
 
 
|}
 
 
 
<!-- NAV end -->
 
 
 
<i>{{Translation to follow}}</i>
 
 
 
 
 
=GC Enterprise Architecture=
 
<br>
 
<p>GC Enterprise Architecture is created with the same idea, only with a scope of the whole government. The mandate of the GC Enterprise Architecture, as provided as part of GC EARB mandate, is to <i> refine </i> <b> current </b> architecture standard and to <i>define</i> <b> target </b> architecture standard.</p>
 
<p>Based on TOGAF (The Open Group Architecture Framework), the GC Enterprise Architecture is being developed using the same building block, ie. the <b>B-I-A-T-S+P</b> (<b>B</b>usiness - <b>I</b>nformation - <b>A</b>pplication - <b>T</b>echnology - <b>S</b>ecurity + <b>P</b>rivacy). The "<b>P</b>" (Privacy) is added here as an important component part of Security for Canadian public.</p>
 
<p>To understand more of what we are trying to accomplish through Enterprise Architecture, please find several definition of Enterprise Architecture below:</p>
 
<br>
 
 
 
===What is Enterprise Architecture===
 
There are many definitions for Enterprise Architecture out there. Here are 3 definitions that we really like:</br>
 
<i>“An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most <b>effectively achieve its current and future objectives</b>.” </i></br> Source: https://searchcio.techtarget.com/definition/enterprise-architecture </br>
 
<i>"Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes." </i></br> Source: https://www.techopedia.com/definition/24746/enterprise-architecture-ea </br>
 
<i>"…a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions." </i></br> Source: https://www.gartner.com/it-glossary/enterprise-architecture-ea/</br>
 
<br>
 
<br>
 
 
 
<p>Several work for each of the building blocks have started. In the "Business" building block, for example, a working group was created based on the mandate from the DMCEPP to create the GC Business Capability Model (GC BCM). The purpose of developing this model is to create common terminology across the government when talking about business capabilities.</p>
 
 
 
<p> Here are a few things that we do:</p><br>
 
 
 
<!-- Columns -->
 
 
 
{| width="100%" cellpadding="10"
 
|-valign="top"
 
 
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 1 STARTS: -->
 
[[Image:Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[Government_of_Canada_Architectural_Standards |EA Standards]]</b></span>
 
 
 
GC Architectural Standards as per the Directive for Management of IT
 
<!-- COLUMN 1 ENDS: -->
 
 
 
 
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 2 STARTS: -->
 
[[Image:Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[Past_Endorsed_Architectural_Decisions |EARB Endorsements]]</b></span>
 
 
 
Past EA Decisions tied into the BIATS
 
<!-- COLUMN 2 ENDS: -->
 
|}
 
 
 
 
 
 
 
 
 
<!-- Columns -->
 
 
 
{| width="100%" cellpadding="10"
 
 
 
|-valign="top"
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 1 STARTS: -->
 
[[Image: Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[Enterprise_Architecture_Artifacts |EA Artifacts]]</b></span>
 
 
 
Artifacts supporting the Architectural Standards
 
<!-- COLUMN 1 ENDS: -->
 
 
 
 
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 2 STARTS: -->
 
[[Image:Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[Architecture_Discussions |Working Groups]]</b></span>
 
 
 
EA Working groups - to identify and develop artifacts to bridge the gaps
 
 
 
<!-- COLUMN 2 ENDS: -->
 
|}
 
 
 
 
 
 
 
<!-- Columns -->
 
 
 
{| width="100%" cellpadding="10"
 
 
 
|-valign="top"
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 1 STARTS: -->
 
[[Image:Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[GC EARB |GC EARB]]</b></span>
 
 
 
GC EARB Home Page
 
<!-- COLUMN 1 ENDS: -->
 
 
 
 
 
|width="50%" style="color: black;" |
 
 
 
<!-- COLUMN 2 STARTS: -->
 
[[Image:Image_placeholder.png |100px| left]]
 
<span style="font-size: 1.5em;"><b>[[Monitoring_Architectural_Implementation |Other References]]</b></span>
 
 
 
List of approved Cloud Vendors & approved AI Vendors
 
<!-- COLUMN 2 ENDS: -->
 
|}
 
 
 
 
 
 
 
<!-- FOOTER -->
 
 
 
 
 
{| width="100%" cellpadding="10"
 
 
 
|-valign="top"
 
|style="color:#3C6D9E;"|
 
<!-- 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:#409DE2;"|
 
[[Image: Envelope_icon_blue.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:#409DE2;"|  
 
[[Image: gccollab_icon_blue.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 GC Collab]</div>
 
<!-- COLUMN 2 ENDS: -->
 
 
 
<!-- COLUMN 3 STARTS: -->
 
|width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;"|
 
[[Image: gcconnex_icon_blue.png  |100px | center]]
 
<div style="font-size:1.5em; text-align:center;">[https://gcconnex.gc.ca/groups/profile/7322003/gc-ea-working-group?language=en GCconnex]</div>
 
<!-- COLUMN 3 ENDS: -->
 
<!-- TABLE ENDS --> |}
 
 
 
<!-- COLUMN ENDS: -->
 
 
 
<!-- TABLE ENDS --> |}
 
 
 
<!-- end -->
 

Latest revision as of 13:45, 7 September 2021

Definition[edit | edit source]

Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, and security domains to support strategic outcomes.  

Mandate[edit | edit source]

The Policy on Service and Digital and supporting instruments serve as an integrated set of rules that articulate how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. Other requirements, including but not limited to, requirements for privacy, official languages and accessibility, also apply to the management of service delivery, information and data, information management and cyber security. Those policies, set out in Section 8, must be applied in conjunction with the Policy on Service and Digital. The Policy on Service and Digital focuses on the client, ensuring proactive consideration at the design stage of key requirements of these functions in the development of operations and services. It establishes an enterprise-wide, integrated approach to governance, planning and management. Overall, the Policy on Service and Digital advances the delivery of services and the effectiveness of government operations through the strategic management of government information and data and leveraging of information technology, supporting the mandate of the Minister for Digital Government in leading the Government of Canada’s digital transition. The management of these functions is guided by a commitment to the guiding principles and best practices of the Government of Canada Digital Standards: design with users; iterate and improve frequently; work in the open by default; use open standards and solutions; address security and privacy risks; build in accessible from the start; empower staff to deliver better services; be good data stewards; design ethical services; collaborate widely.

Section 4.1.2.3 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to enterprise architecture.

Section 4.1.2.4 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment.

The Directive on Service and Digital articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.

Section 4.1.1.1 of the Directive on Service and Digital. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.