GC Enterprise Architecture

Home

EA standards

EARB Endorsements

EA Artifacts

Working Groups

GC EARB

Other References

GC Enterprise Architecture

GC Enterprise Architecture is created with the same idea as the industry standard of what an Enterprise Architecture suppose to be, only with a scope of the whole Government of Canada. The mandate of the GC Enterprise Architecture, as provided as part of GC EARB mandate, is to refine current architecture standard and to define target architecture standard.

Based on TOGAF (The Open Group Architecture Framework), the GC Enterprise Architecture is being developed using the same building blocks, ie. the B-I-A-T-S+P (Business - Information - Application - Technology - Security + Privacy). The "P" (Privacy) is added here as an important component part of Security for Canadian public.

To understand more of what we are trying to accomplish through Enterprise Architecture, please find a few good definitions of Enterprise Architecture below:

What is Enterprise Architecture

“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 effectively achieve its current and future objectives.” (Source: TechTarget)

"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." (Source: Techopedia)

"…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." (Source: Gartner)

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. In the "Information" building block, another working group called the GC Enterprise Data Community of Practice was created to figure out how to collect, store, share and manage data. An Artificial Intelligence Policy working group also support the "Information" building block by the use of emerging technology. In the "Application" building block, the Digital Exchange Program working group was created to talk about creating APIs that others can use and make it available in the API store. In the "Security & Privacy" building block, the ICAM & Pan Canadian Trust Framework working group focuses on the Enterprise Digital Identity. And we would still be creating more working group to close the gaps in the Enterprise Architecture framework.

Below are a few things that the GC Enterprise Architecture does:

EA Standards

GC Architectural Standards as per the Directive for Management of IT

EARB Endorsements

Past EA Decisions tied into the BIATS

EA Artifacts

Artifacts supporting the Architectural Standards

Working Groups

EA Working groups - to identify and develop artifacts to bridge the gaps

GC EARB

GC EARB Home Page

Other References

List of approved Cloud Vendors & approved AI Vendors

Need help? Contact us. ZZCIOBDP@tbs-sct.gc.ca GC Collab GCconnex