June, 2005 1

Review Concept of Operations for an

Enterprise ArchitectureIntelligence Center

Haiping Luo

June, 2005 2

Settings You were members of an EA Steering Committee of

a fictional company, reviewing a Concept of Operations for an EA repository

You would critique the ConOps as roles such as: Enterprise managers Business function operators Enterprise architects Technical staff members External stakeholders (investor, customer, partner, auditor,

EA evaluator, …) Please hold your comments until the critique session.

During critiquing, please indicate your role and the slide number you are referring.

June, 2005 3

Overview EA Intelligence Center: an Introduction EAIC Architecture EAIC Construction EAIC Operations EAIC Performance Evaluation Summary Critique

EA’s Role in the Enterprise

EA provides an IT Enabled Holistic Approach to Enterprise Management.

0

2

4

6

8

10

1960's 1980's 2000's

Decade

IT’s Role in Enterprise Management

OverallEnterpriseManagement

IT enabledEnterpriseManagement

Degree of Complexity

Changes IT brought into the Enterprise

2000’s: + Enabling holistic approaches in managing enterprise.1990’s: + Conducting business online, IT utilization in all areas.1980’s: + Office productivity and computer networks.1970’s: + Data management and personal computer.1960’s: Electronic computing.

Inc

rea

se

d c

om

ple

xit

y

June, 2005 5

EA Intelligence Center: an Introduction The EA Intelligence Center:

Documents an enterprise’ structure, i.e., its elements, their relationships, and their interoperations;

Assembles and presents the abstract documentation and blueprints of an enterprise’ architecture;

Facilitates the processes of designing, aligning, improving, and managing the architecture of an enterprise.

June, 2005 6

EA Intelligence Center: an Introduction (cont.)The EAI Center is a core component in the EA Management Process, supporting all phases and all activities in the process.

EA Management Core & Infrastructure

EA DriverEA PrinciplesEA Strategy

EA Governance

EA DocumentationEA Intelligence

Existing EA StructureBusiness Architecture

Resource Arch.Information Arch.

Technology Arch.Application Arch.

Infrastructure Arch.Security Arch.

Planning Future EAEA PlanningEA DesignEA Policy

EA StandardsEA Process

Adding/Changing EABuild new components

Align existing componentsMonitor changesEvaluate output

Improve performance

Analyzing Existing EAEA Presentation

EA ReportsEA Analysis

June, 2005 7

The key characteristics of the EA Intelligence Center is that its information assembling activities focus on an ultimate goal:Providing EA Intelligence to support enterprise management decision making

EA Intelligence Center: an Introduction (cont.)

Concept: EA IntelligenceEnterprise Architecture Intelligence is the process of enhancing enterprise metadata into information and then into actionable knowledge to support enterprise management decision making.

Concept Comparison: EA Intelligence vs. Business Intelligence

Similarities: assemble scattered information; turn data into actionable knowledge; facilitate self-service reporting; support decision making.

Concept Comparison: EA Intelligence vs. Business Intelligence

Differences: focuses on metadata rather than data; processes mainly descriptive text rather than

numerical / categorical values; utilizes mainly qualitative / structural / reasoning

methods rather than quantitative methods; targets at improving structure more than amount; outputs mainly modeling diagrams & context

tables rather than statistical values & charts.

Possible Types of EA Intelligence Analyses• Change impact analysis (related, what if, quantitative, …)• Redundancy / reusability analysis• Process analysis (bottleneck, work flow, point of failure, …)• Vulnerability analysis (roles & responsibility, process, point of

failure,…) • Performance analysis (roles, responsibility, and accountability;

performance metrics,…)• Interoperation analysis (exchange of information,

standardization, …)• Structural analysis (degree of centralization, standardization,

capacity analysis, …)• Culture analysis (communication, philosophy, leadership

assumptions, methodology,…)• Semantic reasoning and inference

June, 2005 12

Who may benefit from the EA Intelligence Center?

Enterprise managers Business function operators Enterprise architects Technical staff members External stakeholders

EA Intelligence Center: an Introduction (cont.)

June, 2005 13

In short, the EA Intelligence Center’s mission is to assemble EA information to support a wide range of enterprise decision making.

With this mission in mind, the EA intelligence capacity needs to be:

built into EAIC’ design; implemented in its construction; carried out in its operations; embedded in its processes; evaluated in its performance evaluations.

EA Intelligence Center: an Introduction (cont.)

14 June, 2005

EAIC Architecture

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience

Construction

ChangeControl

Maintenance

TierManagement

Lifecycle*

*Note: The circle beside each tier represents the management lifecycle for that specific tier.

The Logical Structure

15 June, 2005

EAIC Architecture (cont.)

The Physical Structure

RepositoryServer

Application Server Web Server

Repository TierRegistry TierAnalysis TierOntology Management TierSystem Management Tier

Presentation Tier

Client

ExecutivesManagersEA ArchitectsPlannersAnalystsEngineersIT AdminsSecurity OfficersEAIC Admins…

EAIC System Developers

Feeding & Consuming Server

16 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At system design stage:-Identify decision support use cases.- Identify what tool or tool combination to use to build the decision support capacity

A decision support example:

- Need to provide IT security certification and accreditation (C&A) status report to the CIO quarterly.

17 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At Ontology Management Tier:- What information to collect- How to shape and organize the information.

C&A example:-Identify metadata for IT systems, processes being supported, criteria for importance, responsible org…-C&A status will be set as required fields for each system. The history of C&A needs to be kept.

18 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At Registry Tier:- How to collect information- Who is responsible to maintain the information- How frequent the update should be

C&A example:-Require owners to register and maintain metadata about IT systems, processes, criteria, organizations…-Stewardship assigned to maintain C & A status information.-C&A status update should be no less than quarterly.

19 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At Repository Tier:- What is the cutoff point of centralized vs. federated information storage- What kind of query performance the database should support

C&A example:- C&A status should be centrally stored in the Center while detail IT system configuration information may be pulled from the system documentation at runtime. - Metadata need to be indexed properly to speed up text query such as the C&A report.

20 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At Analysis Tier:- What report to produce- What is the process of identifying and building more useful decision support reports

C&A example:- C&A status reports should include statistics by category, organization, and location. - An automated workflow for the C&A process should be added into the EAI Center.

21 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At Presentation Tier:- How to present information captured in the Center- How to provide self-service reporting capacity

C&A example:- Due to the frequency of the reporting need, the C&A status report will be a predefined dynamic report for user to open.- User can drill down from the C&A report to get related information.- User can output the report to office document files or other databases.

22 June, 2005

EAIC Architecture (cont.)

Analysis Tier

Presentation Tier

Repository Tier

Input information sources

Registry Tier

OntologyManagement

Tier

SystemManagementTier

Audience At System Management Tier:- How to support a wide range of enterprise users - How to establish security control on information and reports- How to maintain system availability

C&A example:- Staff at the Office of CIO needs to be trained to generate the C&A report.- Only system owners and CIO staff members can view and print the portion of C&A reports they authorized to view.- EAIC needs to be up 24/7 allowing system owners to update their information any time.

23 June, 2005

EAIC Construction

Development Phases:I. PlanII. Design and PrototypeIII. Initial Inventory of EA contentsIV. Full Construction

i. In depth baseline inventory (collect, decompose, connect)ii. Architectural analysis and constructioniii. Intelligence insertion

V. Continuous Improvement in Supporting EA Managementi. Maintain and update informationii. Design target EAiii. Improve EA Intelligence Center

User

pa

rticip

atio

n

24 June, 2005

EAIC Construction (cont.)

Content and Capacity Building Scope1. Simple Abstract Stage

2. Expansion Stage

3. Enrichment Stage

25 June, 2005

EAIC Operations

Content Management System Management Development Management

26 June, 2005

EAIC Operations (cont.)

Content Management Principles Ensure wide participation and clear stewardship; Establish policy, ownership, content manager, and

content management process; Manage the entire content lifecycle, ad infinitum; Use the correct criteria for quality control; Be realistic in update requirement; and Enable automatically gathering contents as much a

s feasible.

27 June, 2005

EAIC Operations (cont.)

System Management Requirements Following system administration princi

ples and industry best practice Establishing Proper Security Policy Documenting System Configuration

28 June, 2005

EAIC Operations (cont.)

Development Management Ongoing Tasks Automating content collection and update; Providing web services to feed consuming s

ystems; Enhancing EA intelligence capacity through

integrating more tools and creating own utilities; and

Upgrading EAIC system hardware and software.

29 June, 2005

EAIC Performance EvaluationSample questions and metrics How well EAIC reaches EA documentation goals?

-% of planned elements documented.; How well EAIC is received by the enterprise?

-Ave. daily users and accesses. How well EAIC is supporting enterprise decision ma

king? - # of predefined reports- score of user satisfaction on DS capacity

How well EAIC is administrated?- % up time- ave. resolution time for help calls- security C&A score

June, 2005 30

Summary EAIC is a powerful tool to help

managing the enterprise with a holistic approach

Building EA intelligence capacity is a critical requirement for an EA repository

Stakeholders participation is the key to EAIC success

June, 2005 31

Critique Usefulness Feasibility Enhancement

June, 2005 32

Contact Information

Haiping Luo

haiping.luo@va.gov

This presentation will be at

http://www.aeajournal.org

http://www.aeajournal.org/Chapter_DC.asp