wiki

GC Enterprise Architecture/Enterprise Solutions

< GC Enterprise Architecture
Revision as of 10:37, 11 March 2022 by Gita.nurlaila (talk | contribs)
GC Enterprise Architecture GC Enterprise Architecture Review Board, GC EARB
GC Service & Digital Target Enterprise Architecture When to come
Enterprise Architecture Framework Forward Agenda
Business Capability Model (BCM) Past Sessions
Exemplar and Reference Architectures 10 Things You Need to Know
Enterprise Solutions Governance for Digital Solutions
Working Groups EA and GC EARB Overview – Presentation
Other References


The following content is a synopsis of the December 15, 2020 DM CEPP presentation.

What is enterprise?

Enterprise is generally defined as “an organization” or “organizational unit”

In the GC, ‘enterprise’ refers to a whole-of-government holistic approach.

An enterprise approach can be applied various facets, like governance, solutions, standards and culture.

Enterprise solutions definition

Enterprise solutions are internal and external Government of Canada assets that can be re-used in and across multiple parts of the organization.

Why focus on enterprise solutions?

To “operate as one” and advance the CEPP mandate we propose to focus on enterprise solutions defined by to business capabilities.

Role of business capabilities

Business capabilities are an expression of what a business does and can do.

It is proposed that enterprise solutions are defined as business capabilities

How to get your solution declared as Enterprise Solution

To get your solution declared as an Enterprise Solution in GC EARB, you need to fill up a special GC EARB deck template specifically for Enterprise Solution. It is similar to the regular GC EARB deck template with additional pages added to provide supporting rationale of why your solution needs to be declared as an Enterprise Solution and that you have fulfilled all the necessary requirements to support an enterprise solution.

Then deck can be submitted to the EA team via the EA generic mailbox to be scheduled for GC EARB, and it will be reviewed by the extended EA team.

Once GC EARB approve it as an Enterprise Solution, then department needs to ready itself to provide service to other departments, which may include:

  • create a MOU / agreement with the subscribing department for funding model and service model

What is needed for Enterprise Solutions to work in the GC?

The Enterprise Solutions framework has 3 facets.

Framework image.jpg
Three facets
Governance Culture Solutions
  • What are the roles and responsibilities
    and who decides who fills them?
  • What is the financial and funding
    model for an enterprise solution?
  • Which business capabilities should be
    addressed first?
  • How will user expectations be addressed?
  • What is the path to enterprise-wide adoption?
  • Is everyone ready to buy-in to enterprise solutions?
  • How do we ensure participation?
  • How will open and transparent input be gathered?
  • What are the mind-set and skills
    needed to foster an enterprise solution culture?
  • Which business problem are we solving?
  • Who can access the Enterprise Solution?
  • What data and technology standards are required?
  • Is the implementation secure enough?
  • Will it always be reliably online?

The following content is research conducted by the EA team after December 15, 2020 DM CEPP presentation.

Enterprise Solutions Framework Assessment Key Findings

Governance

OK - Pilots have been able to describe their solutions using the BCM, identify the business problem, and value proposition to address user needs

Issue - Enterprise solution opportunities lack a defined path to advance and as a result tend to fizzle out

Issue - Operational enterprise solutions governance and support is at a low maturity level

Issue - Departments are not mandated and lack incentives to provide services to other departments, need a dedicated organization for enterprise solutions.

Issue - Cost recovery and appropriation models are adequate for operational costs, but up-front funding is required for initial development and evolution of enterprise solutions.

Culture

OK - Departments are ready to buy into Enterprise solutions once they exist, but lack of available ready to use solutions result in departments developing their own.

Issue - Need dedicated teams of “enterprise” business owners and service providers to develop, operate and evolve enterprise solutions, do we need a Shared Services organization to act as the service provider? Do expand SSC mandate to include applications?

Issue - Mandate use and appropriate departmental funds. Define a clear role and responsibility for users to determine needs and for the Business Owners and Service Provider to be accountable.

Solutions

OK - Identifying and developing enterprise solutions is not a problem, focus needs to be on governance and culture

OK - Pilots have been able to define the business problem and processes like the concept case and GCEARB are existing tools that can be used

OK - Cloud base solutions from public cloud service providers are enabling business owners to envision enterprise solutions but they need technical partnerships from dedicated solution providers to provision IT

Proposed Roles and Responsibilities for Enterprise solutions

Stakeholders, defines ”who”

Stakeholders in the form of a ‘product board’ determine and validate user needs, prioritize the delivery roadmap and manage the related expenditures.

•       business/program representatives from across departments

•       sponsors enterprise solution

•       identify users

•       determine user needs

•       consumes

•       contributes funds

Business Owner, defines ”what”

The Business Owner has overall accountability for delivering on the business outcomes and achieving the benefits that a solution is meant to enable or facilitate.

•       Defines the required capabilities and intended business outcomes and benefits

•       Serves as sponsor and is accountable for the achievement of the business outcomes and benefits following implementation

•       Establishes and maintains governance

•       Secures funding and resources and provides oversight

•       Consults with and engages stakeholders and other implicated parties to ensure alignment towards delivery

•       Reviews and signs-off on key strategic risks

•       Authorizes the IT service

•       Oversees data stewardship practices at the production solution-level

•       Creates roadmap for service or product improvements

Service Provider, defines ”how”

The Service Provider operates and manages IT solutions and/or services and provides them to end users.

•       Responsible on behalf of an organization for requirements definitions, service delivery, security and reliability

•       Implement the requirements

•       Signs off on platform scope

•       Collect data to measure service levels and key performance indicators

•       Ensure compliance with standards

•       Monitor, test and adjust as required

•       Support innovative products and services

•       Conduct security assessments

Proposed Governance for Enterprise solutions

Product management board per solution

•       Cross departmental stakeholder representation

DM CEPP

•       Enterprise Business Direction

GC EARB

•       Alignment with Enterprise Architecture Framework

Draft DM CEPP presentation still to be presented

The following initiatives endorsed by GC EARB have characteristics of Enterprise Solutions

This registry of GC Enterprise Solutions are classified in the layers of the EA framework

Business Architecture

Business Intelligence:


Policy/Standard/Framework/Tools:


Information Architecture

Collaboration Platform:

Data Analytics:

Information Management:

Policy/Standard/Framework/Strategies/Tools:


Application Architecture

ATIP:

Asset Management

Case Management:

Contact Centre:

Finance:

Grants & Contributions:

Geospatial:

Human Resources:

Interoperability:

Jobs / Talent Management:

Learning / Training:

Project & Portfolio Management:

Procurement:

Security Clearance:

Service Management:

Search:

Policy/Standard/Framework/Strategies/Tools:


Technology Architecture

Access:

Cloud:

Device:

Infrastructure:

Split Tunnel:

Policy/Standard/Framework/Strategies/Tools:


Security Architecture and Privacy

Electronic Security:

Email Security:

Identity & Access Management

Policy/Standard/Framework/Strategies/Tools:

Archived Enterprise Solutions material

List of Enterprise Solutions from 2017

PSPC

  • GCdocs
  • Shared Case Management
  • BuyandSell.ca
  • Termium
  • eProcurement Solution
  • National Service Call Centre
  • WebEx
  • Shared Travel Services
  • Phoenix
  • myGCHR
  • Compensation Web Apps

CSPS

  • Integrated Learning Management System / Gccampus

TBS

PSC

  • Jobs.gc.ca

ESDC Canada.ca SSC

  • Email
  • GCSRA
  • GCSI
  • GEDS
  • GCKey


Retrieved from "https://wiki.gccollab.ca/index.php?title=GC_Enterprise_Architecture/Enterprise_Solutions&oldid=67724"