Since the ACORD framework first began just a couple of years ago, it's gone from concept to reality. With a lot of hard work from ACORD's members, the five facets are coming together. We're even in version 2 on the information model.

Just to summarize, the five facets are:

A business dictionary containing a business focused glossary of terms and definitions spanning the entire insurance industry
A capability model that defines the common business activities and business processes insurance companies do
An information model that provides the definitions of core insurance concepts such as policy, product, party, and claims and how these concepts relate
A data model that is created from the information model defined in an entity-relationship model format
A component model that is a set of reusable component definitions and data services bridging the gap between business process (capability model) and data (information model)

Those are the parts or the what. Many already know the “what” but now they want to know the “why.” Why did ACORD do it? Why do I want to know about it? Why do I need to be informed about it?

For You and For ACORD

We began the ACORD framework as a way to improve the way we deliver ACORD's Standards to you. In more than 40 years, the standards have grown in breadth and in geography. The framework was a tool that we, as ACORD could use to help keep them current and easily ingestible.

The reasons don't stop there. Models are essential for any business today.

Know Them And Use Them

Model driven development is not new. Architects are using them across the industry and around the world. However, many are looking for help either getting started or validating their concepts.

That's why the ACORD framework is essential for companies large and small. By setting up a standardized model with the required components, members can start off with the ACORD framework and begin building.

For those well into their own (or someone else's) model development, the ACORD framework can be used as a tool to validate work already done, identify gaps, and improve their own designs.

By the way, if you are involved with any of these architecture tasks, you can share your knowledge and expertise by joining any of the ACORD framework working groups.

Working Globally

The ACORD framework is getting attention worldwide. Members see the importance of it for the future and want to be involved as quickly as possible. I've traveled around the US, to London, as well as to Beijing and Sydney—to name just a few spots—all to discuss and educate on the ACORD framework. That's in addition to webinars and sessions at the ACORD Implementation Forum and ACORD LOMA Forum.

Why the interest? The ACORD framework is the future. It's how we'll be able to improve service to members and to the industry as a whole. It's also a way for companies to jumpstart their own architecture projects or they can just compare their models to ours.

What's Coming?

Work continues full force with the various faces of the framework. The Information Model 2.x continues to be refined and we continue to map to existing standards. Updates will be coming regularly as progress continues. At the same time, Data Model 2.x, based on the updated information model will continue and then be validated by ACORD's working group participants.

Capability Model 2.x is being revised based on member feedback and contributions while Data Dictionary 2.0, is being generated from newest versions of the Information Model. Finally, Component Model 1.x, the newest of the facets is being developed based on the initial design, components, and service maps for the most heavily implemented business functions.

To keep up with these developments, you can read the free ACORD Weekly Newsletter and follow me on Twitter (@acord_framework) or better yet, both.

Shane McCullough is a chief enterprise architect at ACORD focused on the development and implementation of the ACORD framework. In particular, he is applying his experience in enterprise architecture to supporting the growth of the ACORD information model as well as to the development of the product schema and product diagramming techniques. Prior to ACORD, Shane worked at Great American Insurance; Ohio Casualty Group where he was an application architect working on policy administration system development and enterprise architecture; and at IBM in the global services insurance division

Special Reports /

ACORD Framework: From Concept to Reality

Related Stories

Recommended For You