At the minimum, consider reviewing the following requests to ensure that your requests are compatible with the updated financial engine:
Inputs | Detailed loss / Loss Modification analyses / Loss Export | Import / Hazard / Loss Groupings / Marginal Impact / Geospatial Requests |
---|---|---|
Minimum and Maximum Cores |
(Optional) Minimum Cores = Two (Optional) Maximum Cores = Multiples of two The existing requests with odd cores will run "as is". The public internal validation will round the odd cores as follows: For core count equals one : the validation rounds to two cores. For core count equals three, five, and seven : the validation rounds down to the nearest even cores. Review the existing templates:
|
(Optional) Minimum Core = One (Optional) Maximum Core = One These analyses require extensive SQL operations, which take 1:1 ratio of cores. Review the existing templates:
|
BySubperil |
(Optional) Save loss analysis results by subperil
|
(Optional) Save the Marginal Impact results by subperil when the underlying loss results for both of the selected analyses are also saved by subperil
|
IncludeSubPeril |
(Optional) Export detailed loss results by subperil
|
|
ApplyInParallelToTreaties |
Obsolete
| |
ApplyInSerialToTreaties |
Save facultative reinsurance options in the detailed loss analysis templates.
| |
IsNGM |
All analyses uses the NGM financial engine.
| |
SaveFacultative SaveTreaty |
Not in scope for this release
| |
IsMinMaxLogic |
Obsolete
| |
Enable Correlation |
Obsolete
| |
Apply Deductible Before Limit |
Default = True
|