diff --git a/src/sections/OED.rst b/src/sections/OED.rst index 7dd63cc..eb98b38 100644 --- a/src/sections/OED.rst +++ b/src/sections/OED.rst @@ -52,7 +52,7 @@ fields exist in OED which are not yet implemented in Oasis, and secondary modifi used by any Oasis based model. However, Oasis LMF continue to expand the scope of their `FM `_ with the aim to support as much of the OED functionality as possible. An in depth overview of the OED can be found `here `_. +ODS_OpenExposureData/blob/main/Docs/2_OED_Overview.rst>`_. OED can support :ref:`property`, :ref:`liability` and :ref:`cyber` classes of business. @@ -76,11 +76,10 @@ The OED format for property comprises of four input files: Together, these four files efficiently and practically represent exposure data that can be interpreted by a catastrophe model. The fields in each file and their corresponding data type are described in the ‘OED Input Fields’ tab in the `OED Data Spec -spreadsheet `_. +spreadsheet `_. .. note:: - Detailed documentation for the OED input files can be found `here `_. + Detailed documentation for the OED input files can be found `here `_. | Location ('loc') Import File @@ -127,15 +126,15 @@ separately, this would be represented in the location input file as shown below: | -The field names in the examples above are described further in `documents 4, 5 and 6 `_. +The field names in the examples above are described further in `documents 4, 5 +and 6 `_. The minimum fields required in a location file are **LocNumber, AccNumber, PortNumber, CountryCode, LocPerilsCovered, LocCurrency, BuildingTIV, ContentsTIV, BITIV, OtherTIV**. The full set of fields in a location import file can be found by filtering on ‘Loc’ in the 'Input File' column of the -'OED Input Fields' sheet within the `Open Exposure Data Spec spreadsheet `_. +'OED Input Fields' sheet within the `Open Exposure Data Spec spreadsheet +`_. There are over 200 potential fields that could be used within the location file. However, it is not mandatory to use a field that is not populated. @@ -159,8 +158,8 @@ multiple rows in the account file. The minimum fields required in an account file are **AccNumber**, **AccCurrency, PolNumber, PortNumber, PolPerilsCovered**. The full set of fields in an account import file can be found by filtering on ‘Acc’ in the 'Input File' column of the 'OED -Input Fields' sheet within the `Open Exposure Data Spec spreadsheet `_. +Input Fields' sheet within the `Open Exposure Data Spec spreadsheet +`_. Similarly, to the loc file, there are over 200 potential fields that could be used within the account file and it is not mandatory to use a field that is not populated. @@ -190,9 +189,10 @@ risk level terms. A facultative contract, a quota share treaty or even a catastr thus require a risk level to be defined. The full set of fields in a reinsurance info import file can be found by filtering on ‘ReinsInfo’ in the 'Input File' -column of the `Open Exposure Data Spec spreadsheet `_. There are over 20 potential fields that could be used within the -reinsurance info file. However, it is not mandatory to use a field that contains no data. +column of the `Open Exposure Data Spec spreadsheet +`_. +There are over 20 potential fields that could be used within the reinsurance +info file. However, it is not mandatory to use a field that contains no data. | @@ -208,16 +208,17 @@ The ``reinsurance scope`` file contains details of two different but related pie * The **CededPercent** for a surplus treaty: which can vary for each risk covered by the treaty. -More information on the two points above are discussed `here `_, and more information on reinsurance within the OED can be found in `document 7 -`_. +More information on the two points above are discussed `here +`_, +and more information on reinsurance within the OED can be found in `document 8 +`_. The scope of what a reinsurance contract applies to is defined by the ten ‘filter fields’ available in the reinsurance scope file: **PortNumber, AccNumber, PolNumber, LocGroup, LocNumber, CedantName, ProducerName, LOB, CountryCode, ReinsTag.** However, the minimum fields required are: **ReinsNumber**, at least one of the ten filter fields, and **CededPercent** for surplus treaties. A full list of the reinsurance variables can be found in the `Open Exposure Data Spec spreadsheet -`_ by +`_ by filtering for ‘ReinsScope' @@ -233,11 +234,11 @@ Liability The current OED schema for liability is a first version with the aim that it develops as market adoption increases and paths for development are suggested. -A full, detailed list of the liability data fields with addition information of the fields can be found `here -`_. +A full, detailed list of the liability data fields with addition information of the fields can be found `here +`_. -More information about ODS Liability can be found in the `GitHub repository `_. +More information about ODS Liability can be found in the `GitHub repository +`_. @@ -253,11 +254,11 @@ Like liability, the OED schema for cyber is a first version with the aim it deve modelling space is still in its infancy and is expected to develop relatively quickly so the OED is expected to develop in parallel to be appropriate for cyber data capture and modelling requirements. -Detailed documentation for the OED cyber documentation can be found `Open Exposure Data Spec spreadsheet -`_. +Detailed documentation for the OED cyber documentation can be found `here +`_. -More information about ODS Cyber can be found in the `GitHub repository `_. +More information about ODS Cyber can be found in the `GitHub repository +`_. @@ -273,6 +274,6 @@ Further information and community views of ODS can be found on the ODS website: The GitHub repository for OED can be found `here `_. -Also available is documentation on `OED currency support `_ and `OED validation guidelines `_ and `OED validation guidelines `_.