Difference between revisions of "GC Enterprise Architecture"
m |
John.currah (talk | contribs) (→GC Enterprise Architecture: updated text to align with DM one-pager) |
||
| Line 1: | Line 1: | ||
<!-- NAV --> | <!-- NAV --> | ||
| − | |||
{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center" | {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center" | ||
|- | |- | ||
| Line 21: | Line 20: | ||
<!-- NAV end --> | <!-- NAV end --> | ||
| − | |||
<i>{{Translation to follow}}</i> | <i>{{Translation to follow}}</i> | ||
=GC Enterprise Architecture= | =GC Enterprise Architecture= | ||
| − | <br> | + | <br>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 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. | ||
| + | |||
| + | Business Architecture is the discipline that defines '''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'''. | ||
| + | |||
| + | Information Architecture establishes a structure for data '''collection''', '''management''', '''storage''', and '''sharing''' (with a focus on open sharing as per the '''Directive on Open Government'''). | ||
| + | |||
| + | Application Architecture emphasises the use of '''open standards and solutions,''' ensures '''reuse is maximized''', and focuses on '''enabling interoperability.''' | ||
| + | |||
| + | Technology Architecture 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'''. | ||
| + | |||
| + | Security Architecture is concerned with ensuring '''security is implemented across all architectural layers''', and '''categorizing data''' to determine appropriate '''safeguards.''' | ||
| + | |||
| + | Privacy Architecture 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 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> | ||
<br> | <br> | ||
| Line 71: | Line 91: | ||
<!-- FOOTER --> | <!-- FOOTER --> | ||
| − | |||
| − | |||
{| width="100%" cellpadding="10" | {| width="100%" cellpadding="10" | ||
| − | |-valign="top" | + | |- valign="top" |
| − | |style="color:#3C6D9E;"| | + | | style="color:#3C6D9E;" | |
<!-- COLUMN STARTS: --> | <!-- COLUMN STARTS: --> | ||
<div style="font-size: 1.8em; text-align:center;">Need help? Contact us.</div> | <div style="font-size: 1.8em; text-align:center;">Need help? Contact us.</div> | ||
| Line 85: | Line 103: | ||
{| width="100%" cellpadding="5" | {| width="100%" cellpadding="5" | ||
| − | |-valign="top" | + | |- valign="top" |
| − | |width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;"| | + | | width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;" | |
[[Image: Envelope_icon_blue.png |100px | center]] | [[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> | <div style="font-size:1.5em; text-align:center; color:white;">{{em|ZZCIOBDP@tbs-sct.gc.ca}}</div> | ||
| Line 92: | Line 110: | ||
<!-- COLUMN 2 STARTS: --> | <!-- COLUMN 2 STARTS: --> | ||
| − | |width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;"| | + | | width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;" | |
[[Image: gccollab_icon_blue.png |100px | center]] | [[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> | <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> | ||
| Line 98: | Line 116: | ||
<!-- COLUMN 3 STARTS: --> | <!-- COLUMN 3 STARTS: --> | ||
| − | |width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;"| | + | | width="33.3%" style="border: 1px solid lightgray; background-color:#fff; color:#409DE2;" | |
[[Image: gcconnex_icon_blue.png |100px | center]] | [[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> | <div style="font-size:1.5em; text-align:center;">[https://gcconnex.gc.ca/groups/profile/7322003/gc-ea-working-group?language=en GCconnex]</div> | ||
| Line 105: | Line 123: | ||
<!-- COLUMN ENDS: --> | <!-- COLUMN ENDS: --> | ||
| − | |||
<!-- TABLE ENDS --> |} | <!-- TABLE ENDS --> |} | ||
| − | |||
<!-- end --> | <!-- end --> | ||
Revision as of 09:46, 19 September 2019
| Home | EA standards | EARB Endorsements | EA Artifacts | Working Groups | GC EARB | Other References |
 |
This page is a work in progress. We welcome your feedback. Please use the discussion page for suggestions and comments. When the page is approved and finalized, we will send it for translation. |
GC Enterprise Architecture
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 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.
Business Architecture is the discipline that defines 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.
Information Architecture establishes a structure for data collection, management, storage, and sharing (with a focus on open sharing as per the Directive on Open Government).
Application Architecture emphasises the use of open standards and solutions, ensures reuse is maximized, and focuses on enabling interoperability.
Technology Architecture 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.
Security Architecture is concerned with ensuring security is implemented across all architectural layers, and categorizing data to determine appropriate safeguards.
Privacy Architecture 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 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.
- Creates GC Architectural Standards as per the Directive for Management of IT
- Publishes Past EA Endorsements as tied into the BIATS layers
- Produces Artifacts supporting the Architectural Standards
- Creates EA Working groups - to identify and develop artifacts to bridge the gaps
- Refers to the GC EARB for Governance
- Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors
|
Need help? Contact us.
|
