Difference between revisions of "GC Enterprise Architecture"
Jump to navigation
Jump to search
m (Update GC EARB link to remove redirect) |
|||
| (30 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | {{OCIO_GCEA_Header}} |
| + | <multilang> | ||
| + | @en|__NOTOC__ | ||
| + | ==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, security, and privacy domains to support strategic outcomes. | ||
| − | + | ==Mandate== | |
| − | + | 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. | |
| − | + | ==B-I-A-T-S+P (GC EA Layers)== | |
| + | 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. | ||
| − | + | ==Working Groups== | |
| + | 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> | ||
| + | |||
| + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Framework|EA Framework]]</b></span> | ||
| + | : Creates GC Architectural Standards as per the Directive for Management of IT | ||
| + | |||
| + | |||
| + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Enterprise Solutions|Enterprise Solutions]]</b></span> | ||
| + | : Publishes Past EA Endorsements as tied into the BIATS layers | ||
| + | |||
| + | |||
| + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Artifacts|EA Artifacts]]</b></span> | ||
| + | : Produces Artifacts supporting the Architectural Standards | ||
| − | |||
| − | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Working Groups|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_Enterprise_Architecture/Board |GC EARB]]</b></span> |
| + | : Refers to the GC EARB for Governance | ||
| − | |||
| − | < | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Other References|Other References]]</b></span> |
| + | : Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors | ||
| + | <!-- FRENCH --> | ||
| + | @fr|__NOTOC__ | ||
| + | ==Definition== | ||
| + | <br>En tant que membre du Conseil d’examen de l’architecture intégrée (CEAI) du GC, l’architecture intégrée (AI) du GC a le mandat de perfectionner les normes d’architecture actuelles et d’établir les normes d’architecture visées. | ||
| − | = | + | ==Mandat== |
| − | + | '''L’AI est une plan conceptuel qui définit la structure et le fonctionnement d’un organisme en tenant compte et en harmonisant les activités opérationnelles, l’information, les données, les applications, la technologie, la sécurité et la protection des renseignements personnels afin d’appuyer les résultats stratégiques. ''' | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Pour y parvenir, l’AI établit le lien entre les activités opérationnelles et la stratégie en matière de TI, permet la collaboration entre les activités opérationnelles et la stratégie en matière de TI et dirige l’intervention ministérielle en cas de perturbation. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==B-I-A-T-S+P (l'AI GC couches)== | |
| − | + | L’utilisation du cadre de normes industrielles appelée le TOGAF (The Open Group Architecture Framework) permet d’offrir une approche structurée relativement à ces normes. Le cadre a question a été élaborée au moyen des mêmes éléments constitutifs, c’est-à-dire le '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). Le « P » (pour protection de la vie privée) a été ajouté à titre de composante de sécurité importante pour la population canadienne. | |
| − | |||
| − | + | L’architecture d’entreprise est la discipline qui établit les '''capacités d’affaires''' et s’assure que la conception est axée sur les '''résultats pour les utilisateurs'''. Elle veille également à ce que les systèmes soient '''quantifiables et imputables''' et à ce que leur mise en œuvre soit réalisée par des '''équipes multidisciplinaires'''. | |
| − | |||
| + | L’architecture de l’information établit la structure en vue de la '''collect'''e, de la '''gestion''', de '''l’entreposage''' et du '''partage''' des données (en mettant l’accent sur le libre partage, conformément à la '''Directive sur le gouvernement ouvert)'''. | ||
| − | + | L’architecture d’application privilégie l’utilisation de '''normes et de solution ouvertes''', veille à l’'''optimisation de la réutilisation''' et met l’accent sur la '''facilitation de l’interopérabilité'''. | |
| − | |||
| + | L’architecture technologique est la discipline qui établit les normes d’utilisation du service d’hébergement du '''nuage public''' (et des modèles connexes comme logiciel en tant que service (SaaS)), de même que les normes de conception pour favoriser le '''rendement''', l’'''accessibilité''' et la '''flexibilité'''. | ||
| − | + | L’architecture de sécurité vise à garantir '''la mise en œuvre des procédures de sécurité dans tous les niveaux de l’architecture''' et la '''catégorisation des données''' en vue de déterminer les '''mesures de protection''' appropriées. | |
| − | |||
| + | L’architecture de protection de la vie privée met en évidence la nécessité de réaliser une '''évaluation des facteurs relatifs à la vie privée''' (EFVP) lorsqu’il est question de renseignements personnels et d’assurer l'''’équilibre entre, d’une part, les besoins des utilisateurs et de l’organisation et, d’autre part, l’utilisation de mesures de sécurité appropriées.''' | ||
| − | + | L’utilisation de la BIATS+P est établi comme ensemble de normes architecturales du GC dans la Directive sur la gestion des technologies de l'information (Annexe C - Procédures obligatoires pour l'évaluation de l'architecture intégrée). Ces normes sont utilisées pour évaluer les initiatives du GC et garantir l’harmonisation. | |
| − | |||
| + | ==Groupe de travail== | ||
| + | Un certain nombre de groupes de travail du GC soutiennent l’amélioration de ces normes et incitent les ministères à s’harmoniser à l’orientation établie dans le Plan stratégique des opérations numériques. | ||
| − | + | · Pour soutenir l’architecture d'''’entreprise''', un groupe de travail a été créé en fonction du mandat du comité des sous-ministres sur les priorités et la planification de l’entreprise (CSMEPC) de perfectionner le modèle de capacité opérationnelle du GC (MCO GC), lequel établit la terminologie partagée d’un bout à l’autre du gouvernement pour aborder les capacités commerciales. | |
| − | |||
| + | · Pour soutenir l’architecture de l’'''information,''' un autre groupe de travail, appelé la communauté de pratique des données d’entreprise du GC, a été mis sur pied afin de discuter de la façon de recueillir, d’entreposer, de partager et de gérer les données. Le groupe de travail sur la politique de l’intelligence artificielle soutient la composante importante de l’« information ». | ||
| − | + | · Pour soutenir l’architecture de l’'''application,''' le groupe de travail du programme d’échange numérique a été créé pour discuter de l’utilisation des interfaces pour la programmation d'applications (API) au GC et de la publication de ces dernières dans le magasin d’API du GC. | |
| − | |||
| + | · Le groupe de travail en nuage a été créé pour soutenir l’architecture de '''technologies''' associée à l’infrastructure du nuage public pour les charges de travail de niveau Protégé B ou inférieur. | ||
| + | · Pour l’architecture de '''sécurité''', le groupe de travail de « Ouverture de session Canada » et du cadre de confiance pancanadien axe ses activités sur l’identité numérique de l’entreprise. | ||
| − | + | · L’architecture de la '''vie privée''' est soutenue par des membres de l’équipe de protection de la vie privée du SCT, lesquels travaillent en étroite collaboration avec le Commissariat à la protection de la vie privée du Canada à l’élaboration de la définition des normes de protection de la vie privée. | |
| + | · La communauté de pratique de l’architecture d’entreprise travaille avec les ministères du GC pour continuer à perfectionner le BIATS+P et aider à assurer l’harmonisation. | ||
| − | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Framework | le cadriciel d'AE]]</b></span> | |
| + | : Crée des normes architectural du GC conformément à la Directive sur la gestion de la TI | ||
| − | |||
| − | |||
| − | |||
| − | |||
| + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Enterprise Solutions|l'Approbation de CEAI GC]]</b></span> | ||
| + | : Publie les approbations de l'AI antérieurs liés aux couches BIATS | ||
| − | < | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Artifacts|l'Artefacts de l'AI]]</b></span> |
| − | + | : Produit des artefacts soutenant les normes architecturales | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | < | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Working Groups|Groups de travail]]</b></span> |
| − | + | : Crée des groups de travail de l'AI - pour identifier et développer des artefacts afin de combler les lacunes | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | < | + | <span style="font-size:1.5em;"><b>[[GC_Enterprise_Architecture/Board |CEAI GC]]</b></span> |
| + | : Fait reference au CEAI GC pour gouvernance | ||
| − | |||
| − | < | + | <span style="font-size:1.5em;"><b>[[GC Enterprise Architecture/Other References |Autres références]]</b></span> |
| + | : Fournit des références rapids, telles que: Liste des fournisseurs de Infonuagique approvés et des fournisseurs de IA approuvés | ||
| + | stand | ||
| + | </multilang> | ||
| + | {{OCIO_GCEA_Footer}} | ||
Revision as of 16:03, 6 August 2020
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, security, and privacy domains to support strategic outcomes.
Mandate[edit | edit source]
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.
B-I-A-T-S+P (GC EA Layers)[edit | edit source]
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.
Working Groups[edit | edit source]
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
