Review Concept of Operations for an Enterprise Architecture Intelligence Center

1. Review Concept of Operations for anEnterprise ArchitectureIntelligence Center Haiping Luo

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.

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

4. Degree of Complexity EA’s Role in the Enterprise EA provides an IT Enabled Holistic Approach to EnterpriseManagement. Increased 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.

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.

6. Existing EA Structure Business Architecture Resource Arch. Information Arch. Technology Arch. Application Arch. Infrastructure Arch. Security Arch. EA Management Core & Infrastructure EA Driver EA Principles EA Strategy EA Governance EA Documentation EA Intelligence Adding/Changing EA Build new components Align existing components Monitor changes Evaluate output Improve performance Analyzing Existing EA EA Presentation EA Reports EA Analysis Planning Future EA EA Planning EA Design EA Policy EA Standards EA Process 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.

7. EA Intelligence Center: an Introduction (cont.) • 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

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

9. Concept Comparison: EA Intelligence vs. Business Intelligence • Similarities: • assemble scattered information; • turn data into actionable knowledge; • facilitate self-service reporting; • support decision making.

10. 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.

11. 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

12. EA Intelligence Center: an Introduction (cont.) • Who may benefit from the EA Intelligence Center? • Enterprise managers • Business function operators • Enterprise architects • Technical staff members • External stakeholders

13. EA Intelligence Center: an Introduction (cont.) • 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.

14. Audience System Management Tier Presentation Tier Construction Analysis Tier Ontology Management Tier Change Control Maintenance Repository Tier Tier Management Lifecycle* Registry Tier Input information sources *Note: The circle beside each tier represents the management lifecycle for that specific tier. EAIC Architecture The Logical Structure

15. EAIC System Developers Client Application Server Web Server Repository Server Executives Managers EA Architects Planners Analysts Engineers IT Admins Security Officers EAIC Admins … Presentation Tier Registry Tier Analysis Tier Ontology Management Tier System Management Tier Repository Tier Feeding & Consuming Server EAIC Architecture (cont.) The Physical Structure

16. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. Audience System Management Tier Presentation Tier Analysis Tier Ontology Management Tier Repository Tier Registry Tier Input information sources EAIC Architecture (cont.) 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. EAIC Construction Development Phases: • Plan • Design and Prototype • Initial Inventory of EA contents • Full Construction • In depth baseline inventory (collect, decompose, connect) • Architectural analysis and construction • Intelligence insertion • Continuous Improvement in Supporting EA Management • Maintain and update information • Design target EA • Improve EA Intelligence Center User participation

24. EAIC Construction (cont.) Content and Capacity Building Scope • Simple Abstract Stage • Expansion Stage • Enrichment Stage

25. EAIC Operations • Content Management • System Management • Development Management

26. 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 as feasible.

27. EAIC Operations (cont.) System Management Requirements • Following system administration principles and industry best practice • Establishing Proper Security Policy • Documenting System Configuration

28. EAIC Operations (cont.) Development Management Ongoing Tasks • Automating content collection and update; • Providing web services to feed consuming systems; • Enhancing EA intelligence capacity through integrating more tools and creating own utilities; and • Upgrading EAIC system hardware and software.

29. EAIC Performance Evaluation Sample 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 making? - # 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

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

31. Critique • Usefulness • Feasibility • Enhancement

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