Touchstone 4.0 Database Documentation
tRRRR_NONCAT_ByReinsurance Table
Stores the reinsurance treaty loss results from a non-catastrophe loss analysis.  This table is created when the user specifies any reinsurance type in the analysis Output Options.
Creation Date5/31/2016 9:46 AM
Text File Group
System Object
Published for Replication
Data Space Used0.00 KB
Index Space Used0.00 KB
 Column NameDescriptionDatatypeLengthAllow NullsDefaultFormula
Primary Key ReinsuranceSID

Unique system-generated sequential identifier for the reinsurance record.

For a complete list of records, see tReinsurance Table.

Primary Key PSOLDType

Code that represents the type of PSOLD data used during a Non-catastrophe analysis.

  • CP5 - Commercial Property 5 years 
  • CP20 - Commercial Property 20 years
  • HO5 - Home Owners 5 years
  • HO20 - Home Owners 20 years

Mean expected loss (expected value). 

Determined by taking the sum of all expected loss from the past "X" years data, where x is 5 or 20 years.

The expected loss (expected value) by layer is the Gross loss after layer conditions are applied to the Ground-Up loss.

 LimitedSeverityAverage severity of loss, by year. Double9  
 ExcessClaimCountExpected number of yearly claims for each layer.Integer4  

Layer average severity is the average severity per claim for each layer.


Percent of total expected loss that is Ground-Up loss.  Calculated using the following equation: (Gross loss / Ground-Up loss ) *100

Objects that tRRRR_NONCAT_ByReinsurance depends on
 Database ObjectObject TypeDescriptionDep Level
tRRRR_NONCAT_DimReinsurance tabletRRRR_NONCAT_DimReinsuranceTableThis table stores information about reinsurance treaties that experienced loss in a non-catastrophe loss analysis. This dimension table is created when losses are saved by treaty.1
See Also

Related Objects

AIRExposureSummary Database



AIR Client Confidential

© 2016. AIR Worldwide is a registered trademark. Touchstone is a registered trademark of AIR Worldwide.

Please contact AIR Worldwide with questions or comments. For database questions. For documentation comments.