Download
1 / 63
731 likes | 1.19k Views
The EIM Reference Architecture A Journey to the Center of the Enterprise. Presented by Luminita Vollmer - MBA, CDMP, CBIP April 30, 2014 – Austin, TX. CONTENTS. Introduction Presentation Goals Enterprise Architecture EnterpriseInformationManagement Reference Architecture
E N D
The EIM Reference ArchitectureA Journey to the Center of the Enterprise Presented by Luminita Vollmer - MBA, CDMP, CBIP April 30, 2014 – Austin, TX
CONTENTS • Introduction • Presentation Goals • Enterprise Architecture • EnterpriseInformationManagement • Reference Architecture • Drivers for Ref Arch • References • Closure
INTRODUCTION Speaker Bio: IT professional for over 20 years Data Architecture /Enterprise Information Undergraduate studies in MIS/Business MBA – College of St. Thomas in St. Paul CDMP, CBIP certified Cyberfraud Analyst and AML – in training
INTRODUCTION Speaker Contact: luminita.vollmer@gmail.com lvollmer@moneygram.com Linkedin: Luminita Vollmer
The Presentation Goals Process Overview Introduce the Enterprise Architecture and Domains Standards that Influence IT Architectures Present the EIM Reference Architecture Introduce the templates The steps to the EIM RA Overview of how a RA is used in the enterprise Links to Resources available
Enterprise Architecture – What It Is • Enterprise Architecture is the process of turning business vision and strategy into a portfolio of capabilities, applications, information assets and technologies that enable the enterprise’s business vision and strategy through a clearly defined roadmap. • Ensures alignment of business and IT strategies by identifying and enabling common business capabilities, ensuring quality and timely information and making certain that proper technology investments are selected to meet MGI’s business objectives. • Helps to create a strategic roadmap with key programs/projects to attain the strategic business objectives and goals, and • Helps to create the enterprise’s IT strategies and technology direction by analyzing the industry trends, best practices, and technology direction in the marketplace
What are Principles Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission. Depending on the organization, principles may be established at any or all of three levels: Enterprise: These principles provide a basis for decision-making throughout an enterprise, and inform how the organization sets about fulfilling its mission. Such enterprise-level principles are commonly found in governmental and not-for-profit organizations, but are encountered in commercial organizations also, as a means of harmonizing decision-making across a distributed organization. In particular, they are a key element in a successful architecture governance strategy (see Architecture Governance). Information Technology (IT): These principles provide guidance on the use and deployment of all IT resources and assets across the enterprise. They are developed in order to make the information environment as productive and cost-effective as possible. Architecture: These principles are a subset of IT principles that relate to architecture work. They reflect a level of consensus across the enterprise, and embody the spirit and thinking of the enterprise architecture. Architecture principles can be further divided into: Principles that govern the architecture process, affecting the development, maintenance, and use of the enterprise architecture
Another view of Principles • Principles are statements of an Enterprise’s Values and Policies, and how they related to the IT Architecture. • They provide links between business, organizational resources, technology strategies; they represent the foundation for technical positions and templates. • A Position is “a stake in the ground”. • A template is a Blueprint. • Created in a vacuum – they will not serve the Enterprise.
What Affects EA Principles • Many kinds of Principles drive or affect the IT architecture • Information Security Association’s Generally Accepted Information Security Principles (GAISP) • GARP (Generally Accepted Recordkeeping Principles) is a framework for managing records in a way that supports an organization's immediate and future regulatory, legal, risk mitigation, environmental and operational requirements. • ITIL - is the most widely adopted approach for IT Service Management in the world. It provides a practical, no-nonsense framework for identifying, planning, delivering and supporting IT services to the business. • To develop an IT Architecture – there has to exist a position on such principles and the position has to be at the Enterprise, domain, or project levels – where the variance of opinions happens.
Enterprise Information Architecture Principles - Example Information is a corporate asset - Information is a shared asset that must be recognized and treated as a valuable asset to the enterprise and managed efficiently, consistently and securely to ensure its reliability and availability. Information must be defined - Information assets will be defined within models aligned to an organizing enterprise conceptual information framework. Information Redundancy must be carefully Managed - Information redundancy creates expense and risk and must be avoided where possible, minimized where necessary and properly architected using specific implementation patterns to ensure sound design is achieved. Information owners are accountable for information quality and appropriate usage Ensuring information quality and appropriate usage is the accountability of the information owner. Management of Information is a joint Business and IT responsibility - Information Management will be orchestrated centrally but responsibilities will come from both IT and Business.
Enterprise Information Architecture Principles – Cont. Information is shared across organizational and business process boundaries - Considering the constraints of Privacy and Security, Information captured by one business process will be shared as needed through a common architected approach. Develop and promote re-usable data services - Data services must use a common reusable model when consumed by applications thus ensuring uniformity and data quality is not in jeopardy. Information must be managed real-time - Have systems that manage information real time to respond to changing business conditions. Information must be secure - Have systems that protect against unauthorized use and disclosure of information. Develop and promote re-usable data services - Data services must use a common reusable model when consumed by applications thus ensuring uniformity and data quality is not in jeopardy. Information must be managed real-time - Have systems that manage information real time to respond to changing business conditions. Information must be secure - Have systems that protect against unauthorized use and disclosure of information.
The TOGAF9 Framework – The ADM Method TOGAF 9.1 as an example A STEP-BY-STEP approach A METHOD for developing EA THE CORE of TOGAF HELPS ESTABLISH an EA Framework
TOGAF9 - The Technical RA A Model and Taxonomy of Generic platform services
Enterprise Information Management – What It Is Enterprise Information Management Architecture describes the principles, standards, patterns, and software components for managing information assets throughout the enterprise. It encompasses applications and services that integrate and manage data, content, and information. As an enterprise discipline, Enterprise Information Management is concerned with the management of structured and unstructured information and the delivery of information across the enterprise to business processes and their supporting applications. The key sub-domains of enterprise information management include: Master Data Management, Data Integration, Business Intelligence, Content Management, and Knowledge Management. Information Management (IM) is the sustaining organizational capability chartered to manage, govern, build and support BI across the organization.
Information Management– What It Is The core capabilities of Information Management: • Acquire and Understand Information – this capability is concerned with analyzing business processes and underlying data management practices to understand information needs and gaps. It includes conceptual and logical modeling of our information, driving semantic reconciliation, profiling data, uncovering data quality issues and gaps, identifying system or record, and defining the sourcing mechanism. • Integrate Information – a core capability of information management is integrating data and information. This capability includes application integration capabilities, data integration capabilities, and master data management techniques. • Store Information – the storage, retention, and management of data and information at rest. Concerned with structure, unstructured, and metadata storage and retention. Data management practices for transactional and analytical repositories. Relational and dimensional physical structures and supporting infrastructure. • Publish and Present Information – is concerned with delivering information to both internal and external information consumers. This includes metadata (business, operational, and technical), reporting, analytics, and content. • Govern and Secure Information – data governance & stewardship, data quality management, information development and delivery (SDLC), managing identity, controlling access, auditing access, and encrypting sensitive information.
Reference Architecture – What It Is • A Reference Architecture (RA) is a proven template solution for an architecture in a specific domain (i.e. Master Data Management, Business Intelligence Reference Architecture, Service Oriented Reference Architecture.) It captures the essence of existing architecture and the vision of the future needs and evolution to provide guidance to assist in developing new needed architectures. • From EA Charter document - Reference Architecture (RA) consists of information accessible to all project team members that provides a consistent set of architectural best practices. • The Reference Architecture has several Viewpointsthat together provide complete blueprints - Capabilities, Processes, Information, Components, Infrastructure • It is enterprise focused vs project • Directed by business needs, goals, objectives – use of Capabilities and Standards
Reference Architecture – cont. • Originates from Enterprise Architecture Principles (contained in the EA Charter) • Describes the architecture layers, principles, major components, and patterns used • Introduces a common vocabulary to all constituents • Based on best practices within the industry and specific domains as a strong versatile reference point baseline for future projects • Enables conformity of specific project solutions, leading towards a desired target state, governing and guiding architectural decisions – used as a blue print.
Benefits of the Reference Architecture • Communication – identifies and defines architecture components, patterns, and layers increasing understanding across stakeholders • Common point of arrival for projects – defines vision state of the architecture and provides guidance across projects. Projects solution architecture moves the current state architectures one step closer to the target state architecture • Reuse – Solutions that leverage the reference architecture for guidance will also be able to leverage common architectural components and patterns of preceding solutions. This provides incremental value at a lower cost due to reuse. • Strategic Planning and Roadmaps – provides a prescription for future work and facilitates the understanding of sequencing, dependencies, and gaps that exist within the architecture • Risk Mitigation – Based on industry best practices, standards, patterns, and proven solutions. We do not need to re-invent, we only innovate.
The Viewpoints for RA • Relationship between the viewpoints in the Reference Architecture • Capabilities – What is provided by the Information Management architecture • Processes – How capabilities and services are provided within the architecture • Services – Interface to Capabilities and Processes, this view point describes the interface channels and the publicly consumable products offered by the IM architecture (people, process, technology) • Application and Technology, software components and technologies used to realize capabilities, processes, and services. • Infrastructure – represents the runtime, operational, or physical realization of the capability, process, and technology.
Data Integration Data Integration Patterns
Data Integration Data Integration Patterns(cont.)
