June – September 2020
1. Introduction and Executive Summary
At the time of writing, various initiatives across the insurance/reinsurance and catastrophe modeling communities are investing in establishing common operating standards, prioritizing open common data standards and catastrophe model interoperability. Aligned with these efforts, a group of industry practitioners and model and service providers convened in November 2019 to address key issues impacting use of catastrophe models, and initiate work to explore and advance work in these areas.
The resulting Catastrophe Modeling Operating Standards (CMOS) initiative comprises over 40 companies across the insurance and catastrophe modeling industries. In early 2020 and working under the guidance of The Institutes, the CMOS initiative determined to engage an exploratory survey and proof of concept project addressing implementing an open common exposure data standard and assessing model interoperability issues.
This document presents the proceedings, results, and recommendations from that project, which took place from June through September 2020.
1.1 Executive Summary
In Spring 2020 and under the guidance and support of The Institutes, the CMOS initiative participants (representing insurers, reinsurers, intermediaries and model/data/service providers) agreed to embark on a limited project to explore and survey issues regarding implementing a common standard in the marketplace, and advance multi-model interoperability. The Project Team comprised volunteers from AIR Worldwide, Aon, Chubb, Guy Carpenter, KatRisk, Renaissance Re, and Xceedance, all of whom represented the various constituencies concerned.
The Project Team adopted a project charter, agreed criteria for identifying a common standard, and selected the Open Exposure Database (OED is the Open Exposure Data standard, developed by Nasdaq and currently supported by the Oasis Loss Modeling Framework. More information is available at https://github.com/OasisLMF/OpenDataStandards. ) as the standard to use for the project. Key activities undertaken included:
Engaging Nasdaq and Oasis to educate the team regarding OED design, origins, and operations, and coordinating with the IDF ITWG regarding their work in developing technology tools to convert data to and from OED
Assessing OED implementation and operating issues at a high-level, leveraging the differing perspectives of the participating companies
Surveying OED capabilities by directly converting individual policy and portfolio level data to OED and back again, identifying challenging areas in describe exposures and contracts across standards while maintaining fidelity
Identifying interoperability opportunities and issues as respects converting between OED and other standards
- The community should unify the current diverse investments and initiatives in the marketplace regarding common standards and interoperability by forming a single consortium or collaborative to oversee carrying the work forward
- The community should start using OED in market areas where it can support business activity today
- The community should use the organizational model recommended above to address OED design, development, curation, and evolution by leveraging experience from OED use in market
- The community should encourage/assist/support model providers in consuming OED directly, and in the absence of that, and to address exceptional situations, continue the ITWG work to develop conversion and mapping assets with model providers owning mapping definitions/interpretations to ensure fidelity of treatment
- The community should promote choice and innovation by helping the community of model developers and service/data providers continue to advance risk analytics capability by protecting their unique IP
2. Project Proceedings
In November 2019, Chubb and SpatialKey hosted a Forum for Change in New York City to address issues affecting catastrophe modeling practices and operations across the insurance and reinsurance industry. Over 40 companies were represented, including insurers, reinsurers, intermediaries, model providers, and industry and risk analytics service providers. The Forum topics and speakers addressed multiple topic areas including data collection and establishing standards, modeling costs/transparency/interoperability, efficiency challenges, and industry collaboration.
Building on the discussions at the Forum, a call to action proposed forming two related Workgroups to address a) exposure and modeled loss data standards and solution interoperability, and b) risk modeling complexity, validation, industry data, new capabilities. Representatives of over 40 companies volunteered to participate in these Workgroups, and the collective group determined to collaborate with The Institutes to ensure appropriate compliance, governance, and to provide executional guidance where needed.
The Workgroup volunteers met in March 2020 to assess options for defining and progressing work addressing the issues raised at the Forum. As part of a supporting survey process, the Workgroup agreed that the top priorities to begin the work included identifying and implementing open common exposure data standards, and addressing multi-model interoperability issues.
The Workgroup reconvened in May 2020, adopting the acronym CMOS (for Catastrophe Modeling Operating Standards) to identify the initiative, and determined to proceed with a time-bound Proof of Concept project to explore and define issues and challenges in adopting a common data standard and enhancing model interoperability, using a small team of industry cat modeling practitioners and model providers. Working under the guidance of The Institutes, volunteers from AIR, Aon, Chubb, Guy Carpenter, KatRisk, Renaissance Re, and Xceedance agreed to pursue the project, facilitated by Mark Cravens as independent consultant (see Appendix).
2.2 Project Proceedings
The Project Team convened on 9-June-2020. In the initial meeting the team adopted a proposed charter, agreed criteria for selecting a common standard, and designated OED as the standard to use in the project based on those criteria (See Appendix for Project Charter and information on OED selection). The original intent included assessing CEDE (CEDE is an open exposure data format designed and implemented by AIR Worldwide, and on which parts of the OED design and code set are based. More information is available at https://www.air-worldwide.com/data- standards/cede-7-0-database-schema/) to OED mappings and conversion, and “field testing” any available conversion tools in a production environment (per below, these plans changed to avoid duplicating other efforts already underway).
The next two weeks focused on educating the team on OED and work underway by the Insurance Development Forum’s Interoperability Technical Working Group (ITWG) on building technology to convert CEDE format data to OED and back again. The Project Team arranged educational sessions with Oasis and Nasdaq as respects OED, and separate sessions with the ITWG team as respects their conversion work. In the course of that, it was clear the ITWG was already addressing one of the PoC goals in building the CEDE-OED technology, and the ITWG invited the PoC team to participate in a technical review of that work, initially scheduled for early July.
Change in Direction: OED Usage Profiling and OED Coding
The PoC team determined to change course so as not to duplicate the ITWG work, and addressed assessing OED operational readiness in two stages. Initially the team performed use case assessment work in which the team profiled OED usage through different operational use cases such as geocoding, vulnerability description, financial modeling, and data development, administration, and sharing.
Subsequently, the ITWG rescheduled the technical review to mid-August, and the PoC Team determined to continue survey work on OED by coding actual market data into that format. While the original intent was to execute this work in a short timeframe, the team needed to extend timing on the project to include the ITWG technical review, and also due to interruptions from tropical storm activity requiring immediate attention.
ITWG Technical Review
The ITWG technical review on 13-August-2020 provided the PoC team insight into the design and progress attained in prototyping a model-agnostic exposure mapping framework. The framework design uses independently defined mapping files defining conversion rules between a given individual standard and OED (avoiding choice constraints), and is built using commonly available technology for flexibility in deployment and development. Further information is available at https://github.com/OasisLMF/OasisDataConverter.
The meeting was an important step in cross-team collaboration, and surfaced strategic considerations that also had arisen in the usage profiling work regarding market adoption and collaborative governance going forward.
Ongoing OED Coding Work
The OED coding work focused on independent efforts by Aon and Guy Carpenter working with Chubb data already in each intermediary’s possession, thereby reducing the need for any data sharing agreements (as the data is already part of existing business relationships). The Guy Carpenter team focused on converting several individual accounts identified by Chubb to explore account and contract-specific aspects. The Aon team addressed conversion at the portfolio level, converting an agreed Chubb portfolio into OED, and then reconverting it back to its original format to test for data fidelity.
Consolidation of Project Outcomes
Alongside the OED coding work, the Project Team assembled assets for collecting observations and recommendations for this report from the individual teams/participants, with the intent to collate feedback and priorities using the voices of each company. This feedback collection addressed four dimensions:
OED Design/Content/Operations: design and operating considerations for the format as it exists today
Interoperability: recommendations from the teams regarding prioritizing expanding interoperability capabilities in the market
Market Adoption: Considerations in socializing, publishing, implementing, and supporting OED and relevant tools across the market
Organization and Governance: Perspectives on how best to organize around this work going forward
In the last weeks of September, the Project Team consolidated mutual observations from the combined education, profiling, and OED coding work, using those to formulate the recommendations presented in this document.
3. Accomplishments and Observations
3.1 Solution Precepts
The Project Team approached the work at hand using critical solution design precepts established in the November 2019 Forum for Change: Choice, Innovation, Transparency, and Efficiency.
- Choice includes choice amongst catastrophe models, modeling approaches, providers, and technology: solution options must seek to expand choices rather than becoming a barrier to market or a constraint to choices
Innovation includes leveraging new/changing modeling, data, technology, and business applications: solution options must encourage and not constrain the ability for community to innovate around these complex risk assessment and management challenges
Transparency includes the ability to understand the genesis of modeling output and analytics, and the differences between varied modeling approaches, data requirements, and risk analytics: solution options must seek to expand transparency, balancing that with respect to potentially proprietary intellectual property (IP) across the community
Efficiency issues span the entire catastrophe modeling process from data collection and coding, to manipulation for use in different models, and on to managing resulting results and analytics: solution options must push for improving efficiency without compromising the values of the other three solution precepts
As an exploratory and survey project, the Project Team engaged with generalized goals as expressed in the Project Charter (see Appendix). Key accomplishments related to the aims set forth in the Charter include the following.
Expanded the knowledge base for the participants and their respective firms regarding the specifics around OED design, origins, and evolution through focused educational sessions and actual experience working with that standard
Established a working relationship with the IDF ITWG to start synchronizing interests and efforts on interoperability, including participating in the technical review of data conversion technology prototype addressing CEDE to OED conversion
Assessed current OED capabilities and approach to describing simple and complex exposure aspects including basic exposure information (location, composition, values)more detailed and complex exposures including secondary modifiers (For the purposes of this document, secondary modifiers include construction and composition details supporting various modeling approaches, which are peril-specific, often differ by provider, and may be IP-sensitive), and complex policy conditions.
Assessed operational considerations such as exchanging data in OED format, describing/packaging complex portfolios, and identifying prospective technical support needs
- Assessed interoperability considerations, including manual conversion of data between formats, aspects of developing and supporting data conversion technology, and respecting IP considerations
- Assembled coordinated recommendations for progressing this body of work (presented below) with coordinated efforts while seeking to minimize operational and trading disruption
3.3 Summary Observations
Following are key observations resulting from the Project Team education, work with the ITWG, and the OED use profiling and coding work.
Overall, OED is comprehensive in terms of describing most exposures and contracts, especially commonly used policy forms and reinsurance structures
In its current form, OED does not clearly address some aspects common to current catastrophe modeling practices, such as describing builders risk, workers compensation and some watercraft/marine exposures
Similarly, while OED has the framework for addressing a variety of geographic/administration identification schemas, construction and occupancy classifications, and other exposure aspects, there may be need for commonly used cross-reference tables and classification schemas to either be directly included, or otherwise supported/cross-referenced for common usage without misinterpretation
The Project Team did not have the opportunity to directly assess complex portfolio hierarchies and/or reinsurance structures, and recognized that assessment of these aspects will benefit market implementation
Having coded data in OED, the Project Team agreed that there are clear challenges in fully addressing some aspects of exposure description (such as secondary modifiers) and complex contract terms (such as peril and/or geography-specific conditions), especially when working with multiple model constructs
Regarding interoperability, the Project Team recognized that the ideal solution for using a common standard would be for model developers to automatically consume the common standard
In the absence of models directly consuming a common standard, there is a need for mapping/conversion technology and supporting assets, and – importantly – model providers should be responsible for specifying mapping/conversion between their format and the common standard to avoid misinterpretation of data (e.g. by a third- party developer)
Implementing and using a common standard must not be bound by any one technological framework or stack, and need to be adaptable over time to keep up with technological changes
- Additional assets will be helpful for market adoption, including reference implementations and sample data, ongoing support documentation, and possibly technical assets such as APIs or other tools
“AIR will continue to support our clients and the industry through thought leadership on making it easier to consume and transform exposure data. AIR has historically both opened up our standard and supported interoperability with data sharing agreements and supporting the creation of OED. We have made an in-kind contribution of opening up our CEDE formats and can further support clients with this as needed. We will actively participate in these discussions to help the industry meet its goals.
We believe that any solution for common data formats must not stifle innovation. AIR will continue to develop state of the art models for supporting our clients and will evolve the CEDE formats to be able to support the needs of our clients.
With regard to the POC, we believe the problem statement and the end goal need further clarification. It must be acknowledged that as the CEDE has evolved over time, the OED may no longer be representative of the latest version of the CEDE. Ultimately, we believe that if we are able to develop and maintain a solution that satisfies the needs of the industry, that solution must have input and buy-in from all relevant parties.”
In creating these recommendations, the Project Team is hopeful to maintain and build the momentum already existing in the marketplace and advance these efforts around common standards and interoperability. Accordingly, the Project Team is making recommendations in five areas: Organization, OED Application, OED Evolution, Interoperability, and Choice and Innovation. The graphic below presents the conceptual construct for these recommendations, each of which is described in more detail in the body of this section.