Behavior for invalid construction / occupancy class codes

This topic describes how Verisk Synergy Studio handles import of invalid construction / occupancy class codes.

The application allows you to import all combinations of construction and occupancy codes, even if a particular combination does not produce loss during an analysis. However, if a location has a construction or occupancy code that is not a valid Verisk Synergy Studio-supported code, the application does not import the location. If you try to import a location with valid Verisk Synergy Studio-supported construction and occupancy codes, but one or both of these codes is invalid for the country or region in which the location is located, the application imports this location and notes the incompatibility in the import log.

During a detailed loss analysis, the application determines whether the construction and occupancy combination for each exposure is valid for the peril/model for which you are analyzing loss and for the country or region in which each location is located. See the application Help for information about specifying the defaults for invalid construction/occupancy pairs; in v.1.0.0, the only option is "Use Defaults". The application remaps invalid construction and occupancy code combinations using either Unknown construction (100) or General commercial occupancy (311) for each model individually within the analysis.
Note:

The application does not remap construction and occupancy codes for offshore locations; this is because all combinations of offshore asset construction and occupancy are valid. However, make sure that you do not accidentally assign an onshore construction or occupancy code to an offshore location. In some models the construction and occupancy class code combination 100-300 is not valid and the application remaps it to 100-311. For exposures in South America, the construction and occupancy class code combination 100-300 is valid, and the application does not remap it. During an analysis, upon identifying a location with an invalid combination, the application remaps the affected construction and/or occupancy codes by performing one of the processes listed in the following table for each model involved in the analysis.

Construction code valid? Occupancy code valid? Remapping process
Invalid for model Valid for model
  1. The application remaps the construction code to unknown construction (100). The construction and occupancy codes are each now valid for the model involved in the analysis.
  2. The application checks whether the construction code (100) and occupancy code are compatible with each other.
  3. If the construction and occupancy codes are incompatible, the application remaps the occupancy code to general commercial occupancy (311).
Valid for model Invalid for model
  1. The application remaps the occupancy code to general commercial occupancy (311). The construction and occupancy codes are each now valid for this model.
  2. The application checks whether the construction code and occupancy code (311) are compatible with each other.
  3. If the construction and occupancy codes are incompatible, the application remaps the construction code to unknown construction (100).
Invalid for model Invalid for model
  1. The application remaps the occupancy code to general commercial occupancy (311). The construction and occupancy codes are each now valid for this model.
  2. The application checks whether the construction code and occupancy code (311) are compatible with each other.
  3. If the construction and occupancy codes are incompatible, the application remaps the construction code to unknown construction (100).
Valid for model, but incompatible with occupancy code Valid for model, but incompatible with construction code
  1. The application remaps the occupancy code to general commercial occupancy (311). The construction and occupancy codes are each now valid for this model.
  2. The application checks whether the construction code and occupancy code (311) are compatible with each other.
  3. If the construction and occupancy codes are incompatible, the application remaps the construction code to unknown construction (100).
Note: When there are invalid pairs, you may see the same loss numbers in a portfolio/multi-peril analysis; the application does not remap the codes when using the defaults and the loss analysis includes a model for which a location's construction/occupancy pair is valid. (If you run an analysis with a single peril, the default option remaps the construction/occupancy code for the peril if the code is not valid for that peril, and will, therefore, produce loss results.)
>