Known Issue 354

The PerilSetCode in LOSS_ByContractSummary is different from that in LOSS_ByLayer table. This could indicate that different peril sets were used for the analyses performed using these tables. Note that this applies only to analyses run with the Next Generation Models (NGM) engine.

Issue ID	354
Summary	The PerilSetCode in LOSS_ByContractSummary is different from that in LOSS_ByLayer table. This could indicate that different peril sets were used for the analyses performed using these tables. Note that this applies only to analyses run with the Next Generation Models (NGM) engine.
Summary	[NGM only] The PerilSetCodes are different for a single analysis for any perils in the LOSS_ByContractSummary and LOSS_ByLayer tables. For example, in case of tropical cyclone, storm surge and Precipitation flood perils, LOSS_ByContractSummary table displays translated PerilSetCode as tropical cyclone while LOSS_ByLayer table displays translated PerilSetCode as tropical cyclone, storm surge and precipitation flood).
Resolved in	Touchstone 2023 (11.0)
Date posted	5/1/2023
Software versions affected	10.0, 9.1, 9.0
Feature set	Detailed loss
Models	Varies
Potential for loss numbers impact	Yes
Workaround	User needs to generate two different outputs, by following theses steps: (1) Select "loss by contract" to generate the contract summary table with the AAL only. (2) Generate the loss by layer table without selecting the contract summary option. This will help user to generate two tables without getting difference in peril set codes.