586
edits
Changes
Jump to navigation
Jump to search
Line 216:
Line 216: − + − − == Digital Core Architecture Guiding Principles == − '''Build Once, Use Everywhere''' − − Build solutions, components and processes for the GC, and reuse across departments; select common over department-specific. − − '''Business before Technology''' − − Derive the solution definition from business requirements and user needs. Design and run the solutions based on overall end to end process. − − '''Standard over Custom''' − − Use standard to maximize integrity, sustainability and interoperability. Design for flexible adoption of enhancements and upgrades. − − '''User-Centricity''' − − Design with, build for, and deliver the best experience to internal and external users. Focus on the needs of users, using user-centred methods. − − '''Treat Data as an Asset''' − − Design to maximize data use and availability. Use the data you collect and implement analytical tools. Reuse existing data where possible. − − '''Design for Security and Privacy''' − − Balance user and business needs with proportionate security measures and adequate privacy protections. − − '''Cloud First''' − − Explore “… as a service” (XaaS) cloud services first. Cloud first but not cloud only… for On Premise, try to adhere to Cloud qualities (e.g. zero modification). − − '''Maximize Benefits''' − − Strive to maximize the benefits for the enterprise; optimize total cost of ownership and minimize risk. Design to be measurable and accountable. − − '''Integration''' − − Enable interoperability based on standard components and solutions. Minimize the number and complexity of the interfaces. Line 332:
Line 295: − + − In a '''shared services''' model, the customers of the shared services are part of the formal board of directors, governing the strategic intent of the shared services organization and determining what service levels will be provided. − − '''Centralization''' is most commonly successful in forms of government with a single, strong leader such as a governor, a strong mayor or county executive, or a president, where the role has significant power over the machinery of government. − − There are occasional exceptions to both of these situations, but creating a centralization model in the '''parliamentary form of government''' is extremely challenging because the parliamentary model usually doesn’t envision enterprise authority vested in any one person. − − == Health Canada classification model == − # Business Capability − # Solution, specific tool − # Component Line 356:
Line 309: − + Line 365:
Line 318: + Line 585:
Line 539: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GC Enterprise Architecture/Enterprise Solutions (view source)
Revision as of 14:26, 26 August 2020
, 14:26, 26 August 2020→Digital Core Architecture Guiding Principles
|Dashboard (per user category), status pages (<nowiki>https://status.status.io/</nowiki>), published road maps, published runbooks, automation libraries, user guides, embedded client execs, planned vs. unplanned outages feeds
|Dashboard (per user category), status pages (<nowiki>https://status.status.io/</nowiki>), published road maps, published runbooks, automation libraries, user guides, embedded client execs, planned vs. unplanned outages feeds
|Client feedback surveys, technical usage statistics
|Client feedback surveys, technical usage statistics
|}
|}
== Benefits of Enterprise Solutions ==
== Benefits of Enterprise Solutions ==
* '''Capacities:''' Is there an existing organization (e.g. a common service organization) that could provide the service? Is there a lead organization or cluster with the necessary resources, expertise and commitment to successfully execute?
* '''Capacities:''' Is there an existing organization (e.g. a common service organization) that could provide the service? Is there a lead organization or cluster with the necessary resources, expertise and commitment to successfully execute?
== Input from Gartner ==
== Operationalization of Enterprise Solutions ==
== Service & Digital Target Enterprise Architecture ==
== Service & Digital Target Enterprise Architecture ==
* This re-use is enabled through the use of published APIs shared across government. This approach allows GC to focus on improving its service delivery to Canadians while addressing the challenges with legacy systems.
* This re-use is enabled through the use of published APIs shared across government. This approach allows GC to focus on improving its service delivery to Canadians while addressing the challenges with legacy systems.
== Enterprise Solutions and the EA Framework ==
== GCEARB and the EA Framework ==
The Business Architecture layer of the the EA Framework has the following assessment criteria for GC EARB reviews:
The Business Architecture layer of the the EA Framework has the following assessment criteria for GC EARB reviews:
* Promote Horizontal Enablement of the Enterprise
* Promote Horizontal Enablement of the Enterprise
* Publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services.
* Publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services.
Decision Making Framework for Enterprise Solutions is included as part of the presenter template
== The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions/Shared Services. ==
== The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions/Shared Services. ==
|2018-12-13
|2018-12-13
|}
|}
== Archived Reference material ==
== Input from Gartner ==
In a '''shared services''' model, the customers of the shared services are part of the formal board of directors, governing the strategic intent of the shared services organization and determining what service levels will be provided.
'''Centralization''' is most commonly successful in forms of government with a single, strong leader such as a governor, a strong mayor or county executive, or a president, where the role has significant power over the machinery of government.
There are occasional exceptions to both of these situations, but creating a centralization model in the '''parliamentary form of government''' is extremely challenging because the parliamentary model usually doesn’t envision enterprise authority vested in any one person.
== Health Canada classification model ==
# Business Capability
# Solution, specific tool
# Component
== Digital Core Architecture Guiding Principles ==
'''Build Once, Use Everywhere'''
Build solutions, components and processes for the GC, and reuse across departments; select common over department-specific.
'''Business before Technology'''
Derive the solution definition from business requirements and user needs. Design and run the solutions based on overall end to end process.
'''Standard over Custom'''
Use standard to maximize integrity, sustainability and interoperability. Design for flexible adoption of enhancements and upgrades.
'''User-Centricity'''
Design with, build for, and deliver the best experience to internal and external users. Focus on the needs of users, using user-centred methods.
'''Treat Data as an Asset'''
Design to maximize data use and availability. Use the data you collect and implement analytical tools. Reuse existing data where possible.
'''Design for Security and Privacy'''
Balance user and business needs with proportionate security measures and adequate privacy protections.
'''Cloud First'''
Explore “… as a service” (XaaS) cloud services first. Cloud first but not cloud only… for On Premise, try to adhere to Cloud qualities (e.g. zero modification).
'''Maximize Benefits'''
Strive to maximize the benefits for the enterprise; optimize total cost of ownership and minimize risk. Design to be measurable and accountable.
'''Integration'''
Enable interoperability based on standard components and solutions. Minimize the number and complexity of the interfaces.
{{OCIO_GCEA_Footer}}
{{OCIO_GCEA_Footer}}
