Line 138: |
Line 138: |
| The next layer projects the idea of a service‑oriented government, with a user‑centred approach to the business of government that puts citizens and their needs as the primary focus of our work, using “tell‑us‑once” service approaches, integrated services across the GC program and service landscape in a way that provides real‑time information to Canadians about their service applications. It is a perspective centred on users and service delivery when considering new IT solutions or modernizing older solutions. It builds on business architecture guidance to design for users first, focusing on the needs of users, using agile, iterative, and user‑centred methods in a whole-of-government context. | | The next layer projects the idea of a service‑oriented government, with a user‑centred approach to the business of government that puts citizens and their needs as the primary focus of our work, using “tell‑us‑once” service approaches, integrated services across the GC program and service landscape in a way that provides real‑time information to Canadians about their service applications. It is a perspective centred on users and service delivery when considering new IT solutions or modernizing older solutions. It builds on business architecture guidance to design for users first, focusing on the needs of users, using agile, iterative, and user‑centred methods in a whole-of-government context. |
| | | |
− | ADD image '''[[:File:External_Stakeholders.png]]''' | + | ADD '''[[:File:External_Stakeholders.png]]''' |
− | | |
− | Leveraging the concept of harmonization described for external users through Sign‑in Canada, GCPass will enable authentication and authorization to GC Systems for Internal stakeholders. The digital workplace will uniformly enable the work of public servants, building on a standard design.
| |
− | | |
− | '''ADD Image Internal Stakeholders'''
| |
− | | |
− | Information architecture is depicted in the following layer. Information architecture best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets.
| |
− | | |
− | Information architectures should also distinguish between personal and non‑personal data and information as the collection, use, sharing (disclosure), and management of personal information must respect the requirements of the ''Privacy Act'' and its related policies.
| |
− | | |
− | '''ADD Image''' Information architecture
| |
− | | |
− | The following layer depicts how services will interoperate through a standard fabric, supported by a set of common API standards specifying protocols and payloads. These services will be published in the API Store to facilitate reuse. APIs will be brokered through an API gateway to manage traffic, ensure version control, and monitor how services are exposed and consumed, either directly, or through a common event broker. Procurement of software as a service (SaaS) offerings will be facilitated through Shared Services Canada’s (SSC’s) Cloud Brokering Service and supported through their managed services. These are services that are available to steward infrastructure that are offered by SSC include database management services, cabling, facility management, transition planning and support, system integration services, and project management, among others. GC business programs and services and their enabling capabilities are built on resources within the application and information landscapes.
| |
− | | |
− | '''ADD Image''' Application architecture and technology architecture
| |
− | | |
− | Also highlighted in this layer are automation capabilities such as artificial intelligence and open source solutions listed on an open resource exchange. '''ADD Image''' Application architecture and technology architecture (duplicated?)
| |
− | | |
− | In the bottom‑most view of the Service and Digital Target Enterprise Architecture, the focus is on the technology infrastructure that acts as the glue to bring everything together: the network. The GC network consists of local area network (LAN), wide area network (WAN), satellite, and internet infrastructure that provides general connectivity for internal government users, as well as secure and networks that support collaboration between the government and scientific communities. These are all connected with network hubs that optimize the performance of the GC network. The core infrastructure includes SSC services that ensure IT continuity (disaster recovery), including performance monitoring and reliability planning.
| |
− | | |
− | '''ADD Image Enterprise Network Connectivity .....'''
| |
− | | |
− | Security is reflected in the Service and Digital Target Enterprise Architecture diagram as a cross‑cutting factor that spans all horizontal layers. The goal is to ensure security at all architectural levels, from design to implementation to operations; and to ensure authentication, authorization, auditing, monitoring, tokenization, and encryption of all data, whether at rest or in motion.
| |
− | | |
− | '''ADD Image''' Security architecture
| |
− | | |
− | === Improved outcomes ===
| |
− | {| class="wikitable"
| |
− | |'''Improved digital services that meet citizens’ expectations'''
| |
− | |Canadian citizens expect reliable digital services that deliver a cohesive user experience.
| |
− | | |
− | Their expectation for cohesive user experience is founded on their perception that digital services are being delivered by “one” government and not a collection of departments. By aligning digital service delivery to a common set of services defined within a GC Service Inventory and implemented using reusable components based on a common taxonomy of business capabilities, GC can improve the user experience.
| |
− | | |
− | Their expectations for reliability and availability are based on their experiences with modern private‑sector internet services. By transitioning to public cloud offerings and infrastructure, GC can leverage private sector investments to meet citizens’ expectations for reliability and availability.
| |
− | |-
| |
− | |'''Managed costs and improved agility'''
| |
− | |GC needs to achieve economies of scale realized by modernizing and standardizing IT and by reducing its reliance on costly and outdated technology.
| |
− | | |
− | By encouraging the sharing of reusable components based on business capabilities and by leveraging private sector cloud solutions and open source software, GC can both reduce redundancy and help manage costs.
| |
− | | |
− | By transitioning to an architecture that leverages public cloud offerings and infrastructure, GC can become more agile in responding to changes in business needs, thus delivering future‑ready IT systems that can support the GC digital transformation journey.
| |
− | |-
| |
− | |'''Engaged and effective workforce'''
| |
− | |Retention has been identified as a significant IT workforce and talent management issue. The ability to attract and retain new talent is challenging due to the perception that government IT is decades out‑of‑date. Besides the drain on workforce capacity, attrition has negatively impacted morale, the level of engagement and overall workforce effectiveness.
| |
− | | |
− | By adopting modern technology and practices, the government is in a better position to attract and retain new talent. Reducing attrition and boosting recent talent acquisition will have a positive impact on morale and foster an engaged and effective workforce.
| |
− | |}
| |
− | | |
− | === Realization practices and principles ===
| |
− | To realize the GC Enterprise Ecosystem Target Architecture, departments should align with the practices and principles as outlined below, when considering new IT solutions or modernizing older solutions. The architectural approach was developed to facilitate managed incremental transitions but requires more strategic planning on the part of departments to be implemented effectively.
| |
− | | |
− | The Government of Canada Enterprise Architecture Framework defined below presents the evaluation criteria being used by GC Enterprise Architecture Review Board to align solutions to the Service and Digital Target Enterprise Architecture. In the interest of effective communication to the architecture community of practice, the material has been organized based on the architectural domains business, information, application, technology, and security.
| |