RDOS Concepts
This document discusses the framework of the Risk Data Open Standard (RDOS) concepts and schema. It describes the entities that comprise the exposure, settings, results, and reference schemas. While it provides some field-level details, it primarily focuses on main areas and concepts. For the full specification of fields, data types, and values, see the RDOS schema specification RDOS_Schema.xlsx.
Conventions
Table names—Table names are written as one word using initial caps for each word, e.g., AggregatePortfolioMembership. When a table is extended to create a new table, the name is written as ParentTable_ExtendedTable, e.g., RiskItem_RealProperty.
Field names—Field names are written as one word using camel case, where the first letter of the first word is lowercase, and the first letters of subsequent words are uppercase, e.g., replacementCostValue.
Abstract and Extended Entities
RDOS provides a layer of abstraction between the underlying storage technology and the physical representation. It includes the following abstract entities that act as master tables or templates from which other tables have been extended. The extended tables include all the fields from the abstract entities and add their own fields; see RDOS Entity Relationship Diagram and RDOS Provides Extensibility.
- Contract—Extended to create:
- Contract_Insurance
- Contract_Facultative
- Contract_Treaty
- RiskItem—Extended to create:
- RiskItem_RealProperty
- RiskItem_ContainedProperty
- RiskItem_TimeElement
- RiskItem_Population
- Result—Extended to create:
- Result_EP
- Result_ELT
- Result_PLT
- Result_Stats
- Settings—Extended to create:
- Settings_RiskAnalysisProfile
- Settings_ModelProfile
Read next: Exposure Schema