Asset Management¶

Asset management handles the upload and validation of Schedule of Values (SOV) data. Assets can be property addresses (LOCATION type) or custom types (CUSTOM — e.g. vessels, aircraft, vehicles). It is most commonly used in DUA (bordereau) workflows.

Asset types¶

Type	Description
`LOCATION`	Property/address-based assets. Uses Workbench address fields and can integrate with address cleansing services.
`CUSTOM`	Non-address assets (vessels, aircraft, equipment, etc.). Columns are fully defined by the client.

Key configuration¶

Risk action config¶

In the asset_management risk action additionalProperties:

Config	Description
`assetType`	`LOCATION` or `CUSTOM`
`displayCoreAddressColumns`	`true` / `false` — toggles standard address fields on/off

be_config.json (S3 business config)¶

Config	Description
`allowedProcessingFileExtensions.asset_management`	Allowed SOV file types: `XLSX`, `XLSM`, `XLSB`, `CSV`
`maxFileSizeInMBProcessingLimits.asset_management`	Max SOV file size in MB (default: 30)
`defaultAddressCleanseApi`	Address cleanse provider: `MOCK`, `GOOGLE_MAPS_API`, `PRECISELY`, etc.
`bypassAddressCleanse`	`true` to skip external cleansing and use submitted data as-is

Asset values (coverages)¶

Asset values are the data fields captured for each asset row. They are configured in two business constants files:

business-constants/coverage.json — individual field definitions
business-constants/coverage_group.json — groups of fields

Then linked to the business class in the business class JSON under coverages[].

Coverage field	Description
`coveragePurpose`	`ASSETS` for asset management fields
`coverageItemCode`	References an `itemCode` from `coverage.json`
`coverageValueType`	`ENUM`, `NUMBER`, `MONEY`, `PERCENTAGE`, `INTEGER`, `TEXT`, `DATE`, `NUMERICAL_TEXT`, `YEAR`
`enumTypeCode`	For `ENUM` type: the business constant type providing options
`displaySequence`	Column order in the asset grid
`alwaysDisplayed`	Show in both mapping and edit views
`hiddenFromMapping`	Hide from the initial mapping step but show in edit view

Operations within asset_management¶

The asset_management action contains multiple operations, with display logic controlled by sub-status flags:

Operation	When shown
`asset_mapping`	After `SCHEDULE_MAPPING_AI_COMPLETE` sub-status. Maps SOV spreadsheet columns to defined coverage fields.
`manual_entry`	When `assetCount` equals 0. Allows manual entry of individual assets.
`address_cleanse_verification_v2`	After `ADDRESS_CLEANSE_COMPLETE` sub-status. Review screen for cleansed addresses (v3.4.0+).
`edit_assets`	When `assetCount` is not 0. Edit existing uploaded assets.
`remove_assets`	When `assetCount` is not 0. Remove all assets to restart processing.

Note

address_cleanse_verification_v2 (available from v3.4.0) replaces the older address_cleanse_verification operation. Use the v2 version for all new implementations.

AI column mapping¶

When an SOV spreadsheet is uploaded, Workbench uses AI to suggest which spreadsheet columns map to which defined coverage fields. The underwriter reviews the suggested mapping in the asset_mapping operation and confirms or corrects it before the data is imported.

Address cleansing¶

For LOCATION type assets, Workbench can validate and standardise addresses using an external cleansing service (Google Maps API, Precisely, etc.). Configure the provider in defaultAddressCleanseApi.

To skip external cleansing (e.g. in development or when addresses are already standardised), set bypassAddressCleanse: true.