Enterprise Architecture and OneVA EA Overview (EA 101) October 2014 ARCHITECTURE, STRATEGY & DESIGN.

Enterprise Architecture and OneVA EA Overview (EA 101)

October 2014

ARCHITECTURE, STRATEGY & DESIGN

2

Objectives

ARCHITECTURE, STRATEGY AND DESIGN

• To increase knowledge regarding general EA concepts:– What Enterprise Architecture is and its value– Laws and regulations requiring Enterprise Architecture– Key elements that constitute an EA program

• Provide insight specific to the OneVA EA program:– Drivers (i.e., vision, mission, goals, and principles)– Questions-based approach to development– Use of the OneVA EA in Department decision process life cycles– OI&T’s Provider/Consumer Relationship with the OneVA EA– Your role in making the OneVA EA program a success

3

VA’s Business Challenges

ARCHITECTURE, STRATEGY AND DESIGN

General EA Concepts

4ARCHITECTURE, STRATEGY AND DESIGN

5

What is Enterprise Architecture?

ARCHITECTURE, STRATEGY AND DESIGN

Enterprise Architecture is a strategic planning and management tool consisting of an interrelated set of blueprints, plans, standards, and data reflecting different aspects of the enterprise (e.g., strategy, business, systems, data exchanges) at different levels (e.g., enterprise-wide, segment, solution). It provides authoritative information for planning, decision making and management.

• Business Functions Models• Business Process Models• System Interface Models

• Strategic Plans• Transition Plans• Modernization Plans

• Business Rules• Technical Standards• Performance Standards

Data• Resource Data• Demographic Data• Performance Data

Blueprint Examples Plan Examples Standard Examples

6

City Planning: A Good Analogy for Enterprise Architecture

ARCHITECTURE, STRATEGY AND DESIGN

• The City Plan

• The Zoning Plan

• The Building Code

• The Building Materials List

City Planning VA Enterprise Architecture

• Strategic Plan• Enterprise Roadmap

• VA Business Reference Model

• VA Enterprise Technical Architecture (ETA)

7

Federal Mandates and Directives

• Clinger Cohen Act and Title 40 USC 11312– Requires a Capital Planning and Control Process (CPIC) as prescribed by the Office

of Management and Budget (OMB)– CIOs must implement an integrated enterprise architecture

• OMB A-11, exhibit 300: – Building a business case in alignment with the EA

• OMB A-130 8.b(1)– Agencies must establish and maintain a capital planning and investment control

process that links mission needs, information, and information technology in an effective and efficient manner

• Common Approach to Federal Enterprise Architecture (May 2, 2012)– Only an enterprise-wide architecture can provide an integrated view of strategic,

business, and technology domains across all lines of business, services, and systems – which is key to optimizing mission capabilities and resource utilization. At present, there is no other management best practice, other than EA, that can serve as a context for enterprise-wide planning and decision making.ARCHITECTURE, STRATEGY AND DESIGN

8

Benefits of Enterprise Architecture

ARCHITECTURE, STRATEGY AND DESIGN

• Improve Service Delivery: Ensures that IT enables the business and mission functions to achieve optimum performance

• Functional Integration/ Interoperability: Provides context and the source of standards for all levels of interoperability

• Resource Optimization: Provides a harmonized set of views allowing more informed planning and investment decision-making

• Serve As Authoritative Reference: Establishes a trusted enterprise-wide authoritative source of information to enable better decision making at all levels

Ultimately, EA will enable VA to improve the quality and accessibility of health care, benefits, and memorial services while optimizing value

to Veterans

9

High Level Comparison:Product-Centric vs. Data-Centric Architecture

ARCHITECTURE, STRATEGY AND DESIGN

Product-Centric Architecture

Data-Centric Architecture

• Information resides as unstructured/ semi-structured data in document formats (e.g., doc, ppt, elsx)

• Data resides as structured data in a relational database in accordance with a meta-structure schema

• Architecture content developed in collaborative computing environment using an integrated set of modeling and management tools

• Architecture content developed in desktop environment using standard office automation and stand-alone modeling and management tools

• Architecture composed of loosely coupled products, stand-alone or connected via manual mapping (e.g., spreadsheets)

• Architecture composed of an integrated set of data bound by standard definitions, common methods, and unifying meta-structure

Value: Data-centric methodology allows for flexibility in large complex architecture efforts

10

Eight Basic Elements of EA

1. Governance 2. Principles 3. Method 4. Tools 5. Standards 6. Use 7. Reporting 8. Audit

There are eight basic elements that must be present and be designed to work together in each agency EA program. These elements ensure that agency EA programs are complete and can be effective in developing solutions that support planning and decision-making.

Source: CAFARCHITECTURE, STRATEGY AND DESIGN

OneVA EA Concept Introduction

11ARCHITECTURE, STRATEGY AND DESIGN

OneVA Enterprise Architecture Overview

12

Vision: To be the authoritative reference for the requisite strategic, business and technology information used to make informed decisions for the

Department of Veterans Affairs

OneVA EA MissionTo serve as a strategic planning and management tool that helps VA’s leadership chart the course for the Department’s transformation into a 21st century organization.

Strategic Goals include: Improve Service Delivery

Optimize Resources

Promote Functional Integration

Serve as an Authoritative Source

13

Question-Based Approach to OneVA EA Development

ARCHITECTURE, STRATEGY AND DESIGN

• Are we spending our money most effectively? How do we balance investments across our mission requirements?

• Are we supporting multiple systems / capabilities that provide the same service? What plans do we have to transition to more efficient solutions?

• Where do we have opportunities for consolidation / cost reduction? Service / capability reuse?

• What are the low-value investments that should be sunset or placed in minimal sustainment?

Facilitate Resource Optimization

Improve Service Delivery Promote Functional Integration

Serve as Authoritative Reference

• How well are we currently serving the veteran and what process changes need to be made to improve our services?

• To what degree do the VA’s programs align to and fulfill the VA’s priorities?

• What are the gaps in our capabilities to serve the Veteran (e.g., Eliminate Veteran’s Homelessness)?

• How can we enhance and streamline processes that collect and update beneficiary and family information and better apply these processes in the Administrations?

• Can VA provide consistent, authoritative answers to congressional queries / reporting requirements?

• What should be the VA authoritative sources for basic information about Veterans we serve?

• What is the common, consistent view of internal capabilities, services, systems and assets?

• What is the line of sight traceability of all VA goals, objectives, and priorities to VA capabilities, programs, and initiatives?

• What information is exchanged by systems and people between VA organizations and DoD?

• Which VA organizations are responsible for executing mission capabilities and how can we ensure they seamlessly integrate their services / capabilities / information flows across VA solutions and Veteran services?

• What dependencies exist between VA’s capabilities, initiatives, and investments?

• What information is required by a given capability or process?

• What is the IT landscape by business area? What systems/services do we have currently supporting a given capability or process?

OneVA EA Meta-Model

Strat Planning (OPP, OIT, Admins)

OPP Process Models

Data Asset Repository

Systems Inventory Initiative

Underway

IT Budget

Functional Organization

ModelTRM Under

Development

OPP Capability

Model used as baseline

15

OneVA EA Use Within VA Decision Processes

ARCHITECTURE, STRATEGY AND DESIGN

Strategic MeasuresBusiness Functions and Capabilities

Strategic Drivers

Bus. Proc. MeasuresLRPs & Bus. RulesTechnical Requirements

LRPs & Bus. RulesTechnicalRequirements

Data Exchanges

Data Requirements

B.P. & S.P. Measures

Necessary Decision Support

Information

16

OneVA EA Conceptual Vision

ARCHITECTURE, STRATEGY AND DESIGN

Engaging with OneVA EA Team to Evolve Content

17ARCHITECTURE, STRATEGY AND DESIGN

Current OneVA EA Focus Areas

• VA Systems Inventory (VASI)– VASI is the authoritative source describing VA’s business-oriented IT systems and supporting databases (

http://vaww.ea.oit.va.gov/enterprise-architecture/va-systems-inventory/)– Initial prototype has been established and user interface development and testing has begun

• Enterprise Technical Architecture (ETA)– Updating the ETA Compliance Criteria and providing ASD support for IPTs– Assessing options to fulfill ETA Compliance Criteria Automation requirements

• Enterprise Logical Data Model (ELDM)– Conducted ELDM Working Sessions to review draft ELDM and planning for Data Summit

• Strategy and Performance Architecture– Building out the strategy and performance meta-structure and populating with existing content– Researching authoritative performance measure data sources and processes– Identifying key POCs and developing linkages and views

• Enterprise Strategic Integration Team– Establish WG members, goals, deliverables, schedule

• OneVA EA Intranet Website– New look and feel: WordPress– Redesign: Enterprise Transformation theme; Integration of content from the Information Resources

Management (IRM) Strategic Plan and Enterprise Roadmap (ERM) (http://vaww.ea.oit.va.gov)• EA Training offerings– Enterprise Architecture 101 (EA 101)– IBM Rational System Architect (SA) Training

18

Notional OI&T Producer/Consumer Relationship with the OneVA EA

Architecture, Strategy & Design

(ASD)

OI&T Organization

Representative Services/ContentProduced

Representative Services/Content Consumed

Product Development

(PD)

Service Delivery & Engineering

(SDE)

Information Security

(OIS)

• Architecture Content Requirements• “As Is” and “To Be” Application Architecture• Interface Design Specifications• Compliance Assessment Reports• Other

• Governing VA-wide/Segment Architecture • Architecture Compliance Criteria• Architecture Implementation Guidance• Enterprise Service Specifications• Other

• EA Content/Tech Requirements• EA Source Content (e.g., VA-wide/ Solution

Architectures)• EA Methods, Standards, and Training• EA Repository/Tools Access• Other

Same as what gets produced

• Architecture Content Requirements• “As Is” and “To Be” Infrastructure

Architecture• Compliance Assessment Reports• Other

• Governing VA-wide/Segment Architecture • Architecture Compliance Criteria• Architecture Implementation Guidance• Enterprise Infra. Service Specifications• Other

• Architecture Content Requirements• “As Is” and “To Be” Security Architecture• Security Assessment Reports• Other

• Architecture Implementation Guidance• Enterprise Security Service Specifications• Other

OI&T’s Support for ETA Compliance Criteria

.

Collaboration

21ARCHITECTURE, STRATEGY AND DESIGN

How You Can Help Us How We Can Help You • Participation in definition of

requirements• Identification, definition, visibility

and accessibility of content• Ongoing participation within the

OneVA EA development lifecycle• Availability of the right resources at

the right time• Feedback relative to all phases of

the OneVA EA Development

• Implement the requisite Governance process to enable development of the right content

• Implement the requisite processes and rules to manage the development of the content

• Implement, deploy and manage the environment to support the aforementioned processes

• Provide access to the requisite training to enable customers to successfully use the environment

OneVA EA Website

22ARCHITECTURE, STRATEGY AND DESIGN

Learn more about the OneVA EA via our Intranet website:

http://vaww.ea.oit.va.gov

If you would like to request a tour and demonstration of the website, please contact us at [email protected].