ACORD Reference Architecture

The ACORD Reference Architecture provides an enterprise architecture framework for the insurance industry. It consists of business processes, product models, development frameworks, information models, data models, and capability models which help organizations to run, develop, modify, and maintain various insurance industry applications.

The components of the Reference Architecture can be utilized individually or collectively. They also serve as the basis for model-driven standards development, and are flexible enough to cross lines of business and geographic borders.

ACORD members and non-members may subscribe to the Reference Architecture or its individual components. Some organizations may also receive access to the Reference Architecture through the terms of their ACORD membership. For assistance, please contact Member Services.

The Seven Components

The ACORD Reference Architecture is a series of seven interrelated industry models, or facets, which use different views to define the nature of the insurance industry.

ReferenceArchitectureComponents

Business Glossary

The Business Glossary contains standardized, non-technical definitions of insurance concepts, such as "Beneficiary," and includes applicable synonyms, business line-specific usage, and references utilized throughout the other components. The Business Glossary's consistent terminology will help improve communication between partners and within project teams.

Business Glossary 2.11

Business Glossary 2.10

Business Glossary 2.9

Information Model

The Information Model is a formal and conceptual representation of data elements across all lines of business. It provides a comprehensive framework of all fundamental insurance concepts – such as Policy, Product, Party, and Claims – and a broad view of the relationships among them. The Information Model is linked to all the ACORD Standards, and can be used to accelerate and enhance application development; as a semantic model for integration of disparate systems; and to provide a point of reference for information requirements to system designers, business users, developers, and other stakeholders.

Information Model 2.11

Information Model 2.10

Information Model 2.9

Data Model

The Data Model is a logical level entity-relationship structure, generated from the Information Model, which can be utilized in any database implementation. Some of the many uses of the Data Model include designing physical data models and data warehouses, or validating your own data models. The Data Model Implementation Guide provides guidance, tips, and best practices useful for creating a physical implementation. A Data Model Use Case is provided for a fictional P&C carrier. This document describes some of their systems, challenges, and goals as we walk through the process of how to use the ACORD Data Model to develop the fictional carrier’s data design.

Data Model 2.11

Data Model 2.10

Data Model 2.9

Capability Model

The Capability Model defines a baseline of the “activities” across the insurance value chain. It presents the tasks in a functional decomposition, without pre-defining an ordered workflow, to reflect the industry’s capabilities and un-sequenced processes performed. This model can be used in process engineering, merger/divestiture evaluations, and business operations analysis.

Capability Model 2.3.1

Capability Model 2.2

Capability Model 2.1

Component Model

The Component Model contains the relevant information and properties required for specific business activities, or components, which make up insurance business processes. It provides a bridge between business concepts in the Capability Model and data concepts in the Information Model. ACORD components are intended to be customized for independent development using your own system framework. This model has many uses, including portfolio rationalization design and the basis of specifications for software builds or buys. It uses technology-neutral concepts defined in business terms, allowing for implementation across development platforms.

Component Model 2.4

Process Model

The Process Model provides a workflow-oriented model for implementing insurance processes and ACORD messages across an enterprise. It defines a set of reference processes for the insurance industry, aligned to the Capability Model. It includes messages which are mapped to ACORD’s Data Standards. The result is a cohesive model, ready to be adapted and extended to meet specific enterprise needs.

Process Model 2.3

Process Framework 1.2

Product Model

The Product Model is a graphical notation which enables users to quickly, easily, and precisely represent insurance products in a manner that is useful to all levels of an enterprise. This is complemented by the ACORD Product Schema, which enables an XML representation of the product model, and data interchange across enterprise tooling.

Product Model 2.1

Product Framework 2.0

Reference Architecture subscribers can download the files from this page. Contact Member Services for more information on the Reference Architecture, or see our online guides. ACORD also offers Training and Consulting Services to help ACORD members and non-members implement and leverage the Reference Architecture most effectively, according to their particular business needs.