Information Framework

Last updated

Information Framework (IFW) is an enterprise architecture framework, populated with a comprehensive set of banking-specific business models. It was developed as an alternative to the Zachman Framework by Roger Evernden. [1] [2] [3]

Contents

The banking specific business models are an extension to the Component Business Model.

Overview

The IFW business models describe the business of the bank and can be considered as an efficient communication bridge between business and technology communities. They are designed to be readily accessible to business users and focus on industry issues in areas such as Customer Insight, Multi-Channel Transformation, Core Systems, and Risk & Compliance.

The IFW comprises:

The IFW business models typically support over 80% of business requirements and can be customized and extended to cover the specific requirements of a bank. The IFW business models will assist a bank in implementing a flexible, reusable, extensible, and easily customizable architecture, which in turn will enable the bank to:

In its conception, the IFW was an enterprise architecture framework created as an alternative to the Zachman Framework. [1] In 1987 John Zachman proposed the Zachman Framework to describe Information Architecture with the six concepts: The what related to data, how related to process, where related to network and location, who related to actors and people, when related to time, and at last why related to motivation.

Industry Models

This framework has become part of what is commonly known as the Industry Models. [4] The IBM Industry Models are used primarily for the development of internal company standards, and provide an overall integration layer across an organization's existing and future IT investments. With their strong business and IT orientation, IBM Industry Models are designed to be customized to reflect the precise needs of every company using them. Hence, every company will have its own customized industry-specific version of IBM's data, process and service models, allowing them to represent areas that are unique to their business and constitute competitive advantage. In addition, the models can be easily augmented to embrace industry extensions, jurisdiction and company-specific extensions.

The Industry Models (IFW) has products for the following industries:

While in some markets IBM Industry Models have become de facto standards, their purpose is not to standardize at the level of an industry, but to provide the basis for defining corporate standards. IBM's approach is to facilitate or embody the most important industry standards, which are most often data models or messaging formats. Architectural elements in the IBM Industry Models are data models, process models and service models.

Banking and financial markets

The Information Framework for banking and financial markets contains products containing data, process and services models primarily focused on data warehouse and service-oriented architecture domains.

IBM Banking and Financial Markets Data Warehouse (BFMDW)

The banking and financial markets industry is tackling three core challenges head on. The first is focused on its medium-to-longer-term future and how the organization perceives the issues of revenue and risk. Central to the decision about what risks to accept is the need to accurately quantify those risks for trades, hedge funds, counter-parties and pricing. The management of risk is strategic to an organization's corporate intent and survival. The second area of focus is how to respond to the ever-growing demands of regulatory compliance including requirements such as Basel II/III, [5] the Single Euro Payments Area (SEPA), [6] the Standards Maintenance Organization (MISMO), [7] International Financial Reporting Standards (IFRS) [8] for International Accounting Standards (IAS), the Capital Adequacy Directive (CAD) and AntiMoney Laundering (AML) and others. The investments in meeting compliance requirements can be significant so the challenge is how to do this without impacting profitability. Organizations that can turn such investments into market advantage will reap the benefits. The third challenge is addressing the requirements of efficiency, growth and resiliency to provide more relevant, robust, timely, and cost-effective information to business decision makers. Customer retention is important in a volatile market, so attention must also be paid to enhancing the customer experience.

IBM Banking Data Warehouse (BDW)

The BDW is a derivative of the BFMDW and contains content only relevant to the banking industry.

IBM Financial Markets Data Warehouse (FMDW)

The FMDW is a derivative of the BFMDW and contains only content relevant to the financial markets industry.

IBM Banking Process and Service Models (BPS)

The pace of change in the financial services industry has accelerated markedly in recent years. Mergers and acquisitions, the introduction of channel architecture, the development of technologies such as internet banking and telephone banking, the introduction of product bundling and the shift in focus from transactional systems to customer-facing systems, such as operational single view of customer, have all brought about extensive changes in the way financial services organizations operate. By necessity, standalone solutions have been developed, supported by an array of individual processes and procedures that often mimic and duplicate each other, but are sufficiently disparate to cause cost and training issues for financial services organizations, impairing the synergies and savings available to a coherent, strategic organization. A structured approach to any business or IT initiative is imperative to the success of projects. Utilizing the BPS models can act as the formal blueprint for process and services design and be utilized as a tool to bring both business and IT together.

There are many benefits to be derived from using the BPS models, such as:

The BPS models have coverage in the following areas: Sales & Relationship Management; KYC/Account Opening; Lending; Card Products Administration; Commercial / Syndicated Lending; Mortgages; Trade Finance; Savings, Investments & Term Deposits; Transfer Services; Payments -Direct Debit / Credit Transfer / Deposit / Withdrawal; Cash Management; Wealth Management; Product & Marketing Management; Regulatory & Compliance; Best Execution/MiFID; Trade Processing; Corporate Actions; Asset & Liability Management; and Human Resource Administration.

Insurance

Contains products containing data, process and services models primarily focused on Data Warehouse and Services Oriented Architecture domains.

IBM Insurance Application Architecture (IAA)

The Insurance Application Architecture (IAA) is a comprehensive set of insurance specific models that represents best practices in insurance and is a natural extension to the Component Business Model. The IAA models provide the insurance specific business content to accelerate the projects that result from moving to an On Demand Business and pick up the definition of the components that take you there. IAA describes the business of the insurer and is an efficient communication bridge between business and technology communities. It is designed to be readily accessible to business users and by focusing on industry issues such as Sales and Customer Services, Marketing and Analytics, Customer Relationship Management, Policy Administration, Product Development, Insurance Claims and Risk and Compliance.

The IAA models have coverage in the following areas: LOB Customer Acquisition (Individual Insurance), LOB Underwriting (Individual Insurance), LOB Customer Acquisition (Group Insurance), LOB Policy Administration (Individual), LOB Claim Management (Individual), LOB Policy Administration / Claim (Group), Financial Transaction / Investment, Reinsurance Management, Intermediary Management, Provider Management, Human Resource Management, Customer Relationship Management, Marketing Management, Product Development, Risk Policy Management, Risk Mitigation and Assessment, and Risk Reporting and Review.

Other industries

Related Research Articles

<span class="mw-page-title-main">Zachman Framework</span> Structure for enterprise architecture

The Zachman Framework is an enterprise ontology and is a fundamental structure for enterprise architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: identification, definition, representation, specification, configuration and instantiation.

Operational risk is the risk of losses caused by flawed or failed processes, policies, systems or events that disrupt business operations. Employee errors, criminal activity such as fraud, and physical events are among the factors that can trigger operational risk. The process to manage operational risk is known as operational risk management. The definition of operational risk, adopted by the European Solvency II Directive for insurers, is a variation adopted from the Basel II regulations for banks: "The risk of a change in value caused by the fact that actual losses, incurred for inadequate or failed internal processes, people and systems, or from external events, differ from the expected losses". The scope of operational risk is then broad, and can also include other classes of risks, such as fraud, security, privacy protection, legal risks, physical or environmental risks. Operational risks similarly may impact broadly, in that they can affect client satisfaction, reputation and shareholder value, all while increasing business volatility.

<span class="mw-page-title-main">SAS (software)</span> Statistical software

SAS is a statistical software suite developed by SAS Institute for data management, advanced analytics, multivariate analysis, business intelligence, criminal investigation, and predictive analytics. SAS' analytical software is built upon artificial intelligence and utilizes machine learning, deep learning and generative AI to manage and model data. The software is widely used in industries such as finance, insurance, health care and education.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

The chief risk officer (CRO), chief risk management officer (CRMO), or chief risk and compliance officer (CRCO) of a firm or corporation is the executive accountable for enabling the efficient and effective governance of significant risks, and related opportunities, to a business and its various segments. Risks are commonly categorized as strategic, reputational, operational, financial, or compliance-related. CROs are accountable to the Executive Committee and The Board for enabling the business to balance risk and reward. In more complex organizations, they are generally responsible for coordinating the organization's Enterprise Risk Management (ERM) approach. The CRO is responsible for assessing and mitigating significant competitive, regulatory, and technological threats to a firm's capital and earnings. The CRO roles and responsibilities vary depending on the size of the organization and industry. The CRO works to ensure that the firm is compliant with government regulations, such as Sarbanes–Oxley, and reviews factors that could negatively affect investments. Typically, the CRO is responsible for the firm's risk management operations, including managing, identifying, evaluating, reporting and overseeing the firm's risks externally and internally to the organization and works diligently with senior management such as chief executive officer and chief financial officer.

Enterprise risk management (ERM) in business includes the methods and processes used by organizations to manage risks and seize opportunities related to the achievement of their objectives. ERM provides a framework for risk management, which typically involves identifying particular events or circumstances relevant to the organization's objectives, assessing them in terms of likelihood and magnitude of impact, determining a response strategy, and monitoring process. By identifying and proactively addressing risks and opportunities, business enterprises protect and create value for their stakeholders, including owners, employees, customers, regulators, and society overall.

<span class="mw-page-title-main">System Architect</span> Enterprise architecture tool

Unicom System Architect is an enterprise architecture tool that is used by the business and technology departments of corporations and government agencies to model their business operations and the systems, applications, and databases that support them. System Architect is used to build architectures using various frameworks including TOGAF, ArchiMate, DoDAF, MODAF, NAF and standard method notations such as sysML, UML, BPMN, and relational data modeling. System Architect is developed by UNICOM Systems, a division of UNICOM Global, a United States-based company.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

<span class="mw-page-title-main">John Zachman</span> American computer scientist

John A. Zachman is an American business and IT consultant, early pioneer of enterprise architecture, chief executive officer of Zachman International, and originator of the Zachman Framework.

An operating model is both an abstract and visual representation (model) of how an organization delivers value to its customers or beneficiaries as well as how an organization actually runs itself.

Business–IT alignment is a process in which an organization uses information technology (IT) to achieve business objectives, such as improved financial performance or marketplace competitiveness. Some definitions focus more on outcomes which means ; for example,

Alignment is the capacity to demonstrate a positive relationship between information technologies and the accepted financial measures of performance.

In information systems, applications architecture or application architecture is one of several architecture domains that form the pillars of an enterprise architecture (EA).

<span class="mw-page-title-main">View model</span> Framework for enterprise and system engineering

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.

Business systems planning (BSP) is a method of analyzing, defining and designing the information architecture of organizations. It was introduced by IBM for internal use only in 1981, although initial work on BSP began during the early 1970s. BSP was later sold to organizations. It is a complex method dealing with interconnected data, processes, strategies, aims and organizational departments.

<span class="mw-page-title-main">FDIC Enterprise Architecture Framework</span>

FDIC Enterprise Architecture Framework was the enterprise architecture framework of the United States Federal Deposit Insurance Corporation (FDIC). A lot of the current article is about the enterprise architecture framework developed around 2005, and currently anno 2011 out-of-date.

<span class="mw-page-title-main">NIST Enterprise Architecture Model</span> Reference model for enterprise architecture

NIST Enterprise Architecture Model is a late-1980s reference model for enterprise architecture. It defines an enterprise architecture by the interrelationship between an enterprise's business, information, and technology environments.

<span class="mw-page-title-main">Federated architecture</span> Pattern in enterprise architecture that allows interoperability and information sharing

Federated architecture (FA) is a pattern in enterprise architecture that allows interoperability and information sharing between semi-autonomous de-centrally organized lines of business (LOBs), information technology systems and applications.

Roger Evernden is a British enterprise architect, musician, composer, and writer. He is a consultant at the Cutter Consortium, known for his contributions to Enterprise Architecture and as author of the Information FrameWork, an enterprise architecture framework presented in 1996 as a more generic alternative to the Zachman Framework. He has given talks on enterprise architecture.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

References

  1. 1 2 Information FrameWork [ permanent dead link ], Systems Journal article, Roger Evernden
  2. Rik Maes. A generic framework for information management Archived 2012-09-11 at the Wayback Machine . Universiteit van Amsterdam, Department of Accountancy & Information Management, 1999.
  3. Greefhorst, Danny, Henk Koning, and Hans van Vliet. "The many faces of architectural descriptions." Information Systems Frontiers 8.2 (2006): 103-113.
  4. Industry Models
  5. Basel II/III
  6. Single Euro Payments Area (SEPA)
  7. Mortgage Industry Standards Maintenance Organization (MISMO)
  8. (IFRS)

Further reading