Business Architectures, Federal Transition Framework and Semantic Interoperability

1. Business Architectures, Federal Transition Framework and Semantic Interoperability Presentation to Best Practices Committee September 13, 2006 Denise Bedford

2. Business Architecture in Enterprise Architecture • Descriptions of Enterprise Architecture present typically include 3 layers: • Technology architecture • Information architecture • Services architecture • A critical layer, though, is often overlooked - Business Architecture • Goals of Business Architecture • Designing our technologies to support the business – the way we work • Align and evaluate the use of all of our assets around business • Provide a perspective on the business without having to realign the administrative or organizational structure

3. Business Architecture in the FTF

4. Business Layer • Business Layer describes the common business processes and initiatives across the organization. These are aligned with a logical business architecture model which is described in greater detail below (Question 3). • Lines of Business are defined generally as a set of business processes that generate lines or families of products and services. • Business Processes are defined generally as sequential set of activities having a beginning and ending point, generating results (outputs and/or outcomes) of measurable value to the organization. • Business Subprocesses are defined generally as a set of activities which cannot stand on their own – but are leveraged by a business process (get a name and address) • Business Activities or Tasks are defined generally as individual steps that make up either a business process or a subprocess.: • Common Business Process is a process which has been rationalized across the organization. Common Business Processes may have variations in practice which are documented in the business architecture.

5. Information (Data) Layer • Information Layer describes the common information exchange packages, information repositories and standards which support the business architecture. • It includes entities and relationships pertaining to information exchanged as part of a common business process. The data layer foundation should be a fully elaborated corporate data model. The data layer includes: • Business Function Scheme is a critical component of this layer – represented as a controlled hierarchical structure. • Scheme is a representation of the Business Architecture -- a progressive decomposition of Business Areas, Lines of Business, Business Processes, Business Subprocesses and Tasks. This schema is used to categorize all kinds of information and assets to business perspectives. • Business Function Values the actual values which are used to describe the five layers of the business architecture and to categorize assets wherever they live and are managed.

7. Business Area – Level 1 • Business Areas represent the organization’s highest level strategy and performance goals. Business Areas are identified by the organization’s senior management and are published in the World Bank’s Strategy and Performance Contracts. There are currently two Business Areas defined through 2008 • Financial, Administrative and Corporate Business Area – which may be broken down into client or internal facing lines of business; • Operational Business Area – which may be broken down into network or regional operational lines of business.

8. Line of Business • A Line of business (LOB) is defined in terms of lines or groups of products or services. • Set of criteria for World Bank Lines of Business -- describe the line of business wholistically. • A Line of Business is identified only when all of these criteria are met.

9. Criteria for a Line of Business

10. Asset Management Services Auditing Services Business Continuity Services Capacity Building and Training Products and Services Conference Services Corporate Budget Services Corporate Legal Products and Services Corporate Management Services Corporate Procurement Services Corporate Risk Management Services Development Research Products and Services External Affairs Management Facilities Services Fiduciary Products and Services Food Services Graphics, Cartography and Photography Services Health Services Human Resource Management Services Information Services Examples of Lines of Business

11. Business Process • Business process is defined as a set of one or more linked procedures or activities which collectively realize a business objective or policy goal, normally within the context of an organizational structure defining functional roles and relationships • Business process generates a product or service • This is the first level in the business architecture which is ‘executable’ at the workflow level • Business processes should be represented as business process models • Business process modeling should identify all the assets, products and services associated with business subprocesses and activities

12. Example of a Business Process

13. Criteria for Business Process [i] Clarification per conversation with Das.

14. Business Subprocess & Activity • Business Subprocess is a sequence of activities which do not stand on their own – they are called by an initiating process. • A Business Activity is a description of a piece of work that forms one logical step within a process. An activity is the smallest unit of work which is scheduled in a process. • One activity may result in multiple work items being assigned to a participant or actor. • At the levels of Business Process, Business Subprocess and Activity – we want to see • Human resources • IT resources • Financial resources • Information assets • Facilities

15. Elements of Semantic Interoperability • Business Architecture is a very important component of semantic interoperability but it is very challenging to achieve • Organization has to agree to have or map to a single view • Governance and business stewardship are important aspects of ‘interoperability’ at this level • Business Function Scheme is important for achieving semantic interoperability – without this there is no ‘backbone’ • Programmatic categorization is key to semantic interoperability – without this, there is no practical application or implementation – it’s all just fancy shelfware

16. View of the Business Function Scheme

17. Programmatic Categorization to Business Perspective • Model the ‘decision making’ process of people – rules are not always straight forward • Person reads the first portion of a document – looking for key terms which signify a process • Use ‘concept extraction’ to identify the key phrases • Use ‘semantic conditions’ to review key portions of the document to find these phrases • Use categorization tools to model the semantic conditions

18. Enterprise Level Profile for Categorization to Business Perspective • Enterprise Metadata Profile Concept Extraction Technology • Country • Organization Name • People Name • Series Name/Collection Title • Author/Creator • Title • Publisher • Standard Statistical Variable • Version/Edition Categorization Technology • Topic Categorization • Business Function Categorization • Region Categorization • Sector Categorization • Theme Categorization Rule-Based Capture • Project ID • Trust Fund # • Loan # • Credit # • Series # • Publication Date • Language Summarization UCM Service Requests Update & Change Requests Data Governance Process for Topics, Business Function, Country, Region, Keywords, People, Organizations, Project ID e-CDS Reference Sources for Country, Region, Topics Business Function, Keywords, Project ID, People, Organization Enterprise Profile Development & Maintenance System 5 TK240 Client Teragram Team System 4 System 1 System 2 System 3

19. Content Owners Content Owners Dedicated Server – Teragram Semantic Engine – Concept Extraction, Categorization, Clustering, Rule Based Engine, Language Detection APIs & Integration APIs & Integration ISP Integration Functional Team IRIS Integration Business Analyst Enterprise Metadata Capture Strategy TK240 Client XML Output Content Capture Content Capture XML Wrapped Metadata XML Wrapped Metadata APIs & Integration APIs & Technical Integration Enterprise Profile Development & Maintenance Factiva Metadata Database ImageBank Integration Reference Sources Indexers Librarians Sustaining Interoperability for Business Function

20. How Do We Get There? • Model business processes working with business process managers • Identify business stewards and formalize a governance model • Formalize the scheme as a representation of the overall architecture • Align assets with business processes • Build profiles to represent the rules a human follows to discover a business process • Programmatically tag assets to business scheme