Difference between revisions of "GC Enterprise Architecture"

From wiki
Jump to navigation Jump to search
m (earb)
 
(37 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!-- NAV -->
+
{{OCIO GCEA Header}}
{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center"
+
<multilang>
|-
+
@en|
|-
+
== Definition ==
| 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>]]'''
+
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.  
  
| 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>]]'''  
+
== 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="13%" | '''[[EARB_Endorsements|<span style="color: Snow">'''EARB Endorsements'''</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="11%" | '''[[Enterprise_Architecture_Artifacts|<span style="color: Snow">'''EA Artifacts'''</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="12%" | '''[[Working_Groups|<span style="color: Snow">'''Working Groups'''</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="11%" | '''[[GC EARB|<span style="color: Snow">'''GC EARB'''</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="9%" | '''[[Other_References|<span style="color: Snow">'''Other References'''</span>]] '''
+
To be translated
 
+
</multilang>
|}
 
 
 
<!-- NAV end -->
 
<i>{{Translation to follow}}</i>
 
 
 
Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, security, and privacy domains to support strategic outcomes.  
 
 
 
The mandate of GC EA, as part of the GC Enterprise Architecture Review Board (EARB), is to refine current architecture standards and to define target architecture standards.
 
 
 
EA does this by linking business and IT strategy, enabling cooperation between business and IT, and leading the enterprise response to disruption.
 
 
 
The use of an industry standard framework called TOGAF (The Open Group Architecture Framework) is useful for providing a structured approach to these standards, and it has been adapted using the same building blocks, the '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). The "P" (Privacy) was  added as an important component part of Security for Canadian public.
 
* <u>Business Architecture</u> is the discipline that defines '''[https://gcconnex.gc.ca/file/download/50303099 business capabilities]''' and ensures that design is focused on '''outcomes for users'''. It also ensures systems are designed to be '''measurable and accountable''', and delivered by '''multidisciplinary teams'''.
 
* <u>Information Architecture</u> establishes a structure for data '''collection''', '''management''', '''storage''', and '''sharing''' (with a focus on open sharing as per the '''Directive on Open Government''').
 
* <u>Application Architecture</u> emphasises the use of '''open standards and solutions,''' ensures '''reuse is maximized''', and focuses on '''enabling interoperability.'''
 
* <u>Technology Architecture</u> is the discipline that defines standards for using '''Public Cloud''' hosting (and related models such as Software as a Service), and designing for '''performance''', '''availability''', and '''scalability'''.
 
* <u>Security Architecture</u> is concerned with ensuring '''security is implemented across all architectural layers''', and '''categorizing data''' to determine appropriate '''safeguards.'''
 
* <u>Privacy Architecture</u> emphasizes the need to perform a '''privacy impact assessment''' (PIA) when personal information is involved, and ensures a '''balance between user and business needs with proportionate security measures.'''
 
The use of the BIATS+P was codified as a set of GC Architectural Standards in the Directive on Management of Information Technology (Appendix C - Mandatory Procedures for Enterprise Architecture Assessment). These standards are used to evaluate GC initiatives and ensure alignment.
 
 
 
A number of GC Working Groups support the refinement of these standards and influence departments to align with the direction set in the Digital Operations Strategic Plan.
 
* Supporting '''Business''' architecture, a working group was created based on the mandate from the DMCEPP to refine the [https://gcconnex.gc.ca/file/download/50303099 GC Business Capability Model] (GC BCM), which defines common terminology across the government for discussing business capabilities.
 
* Supporting '''Information''' architecture, another working group called the GC Enterprise Data Community of Practice was created to discuss how to collect, store, share and manage data. An Artificial Intelligence Policy working group also supports the "Information" building block.
 
* Supporting '''Application''' architecture, the Digital Exchange Program working group was created to discuss using APIs (Application Programming Interfaces) for GC use, and publishing them in the GC API store.
 
* The Cloud Working group was created to support '''Technology''' architecture related to Public Cloud infrastructure for Protected B workloads and below.
 
* In '''Security''' architecture, the Sign in Canada & Pan Canadian Trust Framework working group focuses on the Enterprise Digital Identity.  
 
* '''Privacy''' architecture is supported by members of the TBS Privacy team, who worked closely with the Office of the Privacy Commissioner on the definition of the Privacy standards.
 
* The Enterprise Architecture Community of Practice works with departments across the GC to continue refine the BIATS+P and help ensure alignment.
 
<br>
 
<br>
 
 
 
<span style="font-size:1.5em;"><b>[[Government_of_Canada_Architectural_Standards |EA Standards]]</b></span>
 
: Creates GC Architectural Standards as per the Directive for Management of IT
 
 
 
 
 
<span style="font-size:1.5em;"><b>[[Past_Endorsed_Architectural_Decisions |EARB Endorsements]]</b></span>
 
: Publishes Past EA Endorsements as tied into the BIATS layers
 
 
 
 
 
<span style="font-size:1.5em;"><b>[[Enterprise_Architecture_Artifacts |EA Artifacts]]</b></span>
 
: Produces Artifacts supporting the Architectural Standards
 
 
 
 
 
<span style="font-size:1.5em;"><b>[[Architecture_Discussions |Working Groups]]</b></span>
 
: Creates EA Working groups - to identify and develop artifacts to bridge the gaps
 
 
 
 
 
<span style="font-size:1.5em;"><b>[[GC_EARB |GC EARB]]</b></span>
 
: Refers to the GC EARB for Governance
 
 
 
 
 
<span style="font-size:1.5em;"><b>[[Monitoring_Architectural_Implementation |Other References]]</b></span>
 
: Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors
 
 
 
 
 
 
 
<!-- 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 GCcollab]</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 12: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.