Overview

A job is a long-running process that consumes significant system resources, such as modeling a location, importing exposure data, or updating portfolios in bulk.

This page identifies the types of jobs that can be run on the Intelligent Risk Platform, discusses operations for polling the status of these jobs and retrieving response objects once they are complete, and describes how resource groups are used to allocate and manage tenant resource quotas.

Job Types

A platform job is a system-defined task that manages a time-consuming or computationally expensive workflow process.

The Intelligent Risk Platform supports two types of jobs: primary jobs and secondary jobs.

Primary jobs are jobs that require immediate processing of time-sensitive materials such as catastrophe modeling of exposures, accumulations, or rollups.
Secondary jobs are jobs that do not process time-sensitive data. This includes batch, bulk, and data migration operations such as importing and exporting data. These are also known as non-model jobs.

Tenants are assigned distinct quotas of model and secondary jobs for each licensed entitlement.

Primary jobs and secondary jobs are managed in distinct workflow queues to ensure that time-sensitive primary jobs are not delayed by long-running import and export jobs.

Primary Jobs

A primary job is a platform job that performs the principal modeling or analysis operation of an Intelligent Risk Platform application.

Primary jobs are known by different names depending on the entitlement.

For Risk Modeler and UnderwriteIQ, a primary job is any job that models a collection of location exposures using a modeling engine (ALM, DLM, or HD). These are also known as model jobs.
For ExposureIQ, a primary job is a job that creates an accumulation.
For TreatyIQ, a primary job is a job that creates a rollup.

A resource group is allocated resource quotas that specify the number of concurrent primary jobs that can be run at any one time. To learn more, see Resource Management.

The table lists primary job types and the entitlements required to initiate those jobs:

Job	Operation
`ACCUMULATION`	Create Accumulation Job
`ACCUMULATION_LIVE`	Create Accumulation Job
`ALM`	Create Model Job
`DLM`	Create Model Job
`HD`	Create Model Job

Secondary Jobs

A secondary job is a platform job that creates or updates a new resource. In general, these jobs are quite long-running and not time-sensitive. Examples of secondary jobs include import job and export jobs.

Secondary jobs are sometimes called secondary jobs. They are generally managed in a distinct job queue.

A resource group is allocated resource quotas that specify the number of concurrent secondary jobs that can be run at any one time. To learn more, see Resource Management.

Job	Operations
`ALM_IMPORT`	Create Import Job
`ARCHIVE_EDM`	Archive EDM
`ARCHIVE_SECURABLE`	Archive Securable
`AUTO_DELETE_ARCHIVE`
`BULK_EDIT`	Exposure Bulk Edit
`BULK_EXPORT`	Create Export Job
`BULK_GEOHAZ`	Create Bulk Geohaz Job
`CADOI`	Create Risk Data Report
`CEDE_IMPORT`	Create Import Job
`CLIMATE_CHANGE`	Calculate Climate Change
`CONVERT_ACCOUNT_CURRENCY`	Create Currency Conversion Job
`CONVERT_AGGREGATE_PORTFOLIO_CURRENCY`	Create Currency Conversion Job
`CONVERT_CURRENCY_LOSS_POSTPROCESSOR`
`CONVERT_EVENT_RATE_LOSS`	Convert Event Rates and Losses
`CONVERT_PORTFOLIO_CURRENCY`	Create Currency Conversion Job
`CONVERT_RESULT_CURRENCY`	Create Currency Conversion Job
`CONVERT_TREATY_CURRENCY`	Create Currency Conversion Job
`COPY_ACCOUNT`	Copy Job
`COPY_AGGREGATE_PORTFOLIO`	Copy Job
`COPY_PORTFOLIO`	Copy Job
`COPY_TO_ARCHIVE`	Create Archives from Snapshot
`CREATE_EDM`	Create EDM
`CREATE_MAP_LAYER`
`DELETE_ACCOUNT`	Delete Account
`DELETE_AGGREGATE_PORTFOLIO`	Delete Aggregate Portfolio
`DELETE_ARCHIVE`	Delete Archive
`DELETE_EDM`	Delete EDM
`DELETE_PORTFOLIO`	Delete Portfolio
`DELETE_RDM`
`DELETE_SECURABLE`	Delete Securable
`DEREGISTER_DATA_BRIDGE_EDM`	Deregister EDM
`DETACH_EDM`
`DOMAIN_DATA_LOAD`
`DOWNLOAD_EDM`	Create Export Job
`DOWNLOAD_DETACH_EDM`
`DOWNLOAD_EXPOSURE_RESOURCE`	Create Export Job
`DOWNLOAD_LOCATION_RESULTS`	Create Export Job
`DOWNLOAD_PEQT`	Create Export Job
`DOWNLOAD_RDM`	Create Export Job
`DOWNLOAD_REPORT`	Create Export Job
`DOWNLOAD_RESULTS`	Create Export Job
`EDM2EDM`	Create Export Job
`ENRICH_EXPOSURE`	Create Enrich Exposure Job
`EXPOSURE_BATCH_EDIT_WITH_GEOHAZ`	Create Batch Job
`EXPOSURE_BATCH_EDIT`	Create Batch Job
`GEOHAZ`	Create Geohaz Job
`GROUPING`	Create Group Job
`MAP_PERSPECTIVE`	Convert Financial Perspectives
`MARGINAL_IMPACT`	Calculate Marginal Impact
`MODEL_PRICING`
`MRI_IMPORT`	Create Import Job
`OED_IMPORT`	Create Import Job
`PATE`	Recalculate with PATE
`PLT_TO_ELT`	Convert PLT to ELT Result
`REGISTER_DATA_BRIDGE_EDM`	Register EDM
`RENAME_ANALYSIS`	Rename Analysis Result
`REPORT_GENERATION`	Create Risk Data Report
`RERUN_EP`	Recalculate EP and Statistics
`RESTORE_ARCHIVE`	Restore Archive
`SIMULATE_LOSSES`	Simulate PLT Analysis
`STEP_TOOL`	Create STEP Analysis Job
`UPDATE_RESULTS_COUNT`
`UPLOAD_EDM`	Create Import Job
`UPLOAD_RDM`	Create Import Job
`VARIATION_EXPOSURE_RESOURCE_IMPORT`

Workflow Job Queues

A workflow queue is a mechanism for coordinating and scheduling platform jobs.

When a job is submitted, it is added to appropriate workflow queue based on the client’s entitlement and passes the quota capabilities to the workflow service.

The scheduler selects jobs for processing based on the rules specified in the workflow queue’s scheduling policy. A tenant is assigned dedicated queues for each entitlement? The jobs in a workflow queue are assigned a priority and a status.

The table lists supported workflow queues by entitlement.

Entitlement	Queues
`RI-RISKMODELER`	`RI-RISKMODELER.<ResourceGroupID>.DEFAULT`, `RI-RISKMODELER.<ResourceGroupID>.FIFO`, `RI-RISKMODELER.<ResourceGroupID>.INTERACTIVE`, `RI-RISKMODELER.<ResourceGroupID>.API`
`RI-UNDERWRITEIQ`	`RI-UNDERWRITEIQ.<ResourceGroupID>.DEFAULT`, `RI-UNDERWRITEIQ.<ResourceGroupID>.FIFO`, `RI-UNDERWRITEIQ.<ResourceGroupID>.INTERACTIVE`, `RI-UNDERWRITEIQ.<ResourceGroupID>.API`
`RI-EXPOSUREIQ`	`RI-EXPOSUREIQ.<ResourceGroupID>.DEFAULT`
`RI-TREATYIQ`	`RI-TREATYIQ.<ResourceGroupID>.DEFAULT`

Interactive Workflow Queues

Primary jobs are managed in the tenant's INTERACTIVE queue.

A RI-UNDERWRITEIQ resource group is provisioned with distinct workflow queues for managing and scheduling different types of jobs. New primary jobs are generally added to an INTERACTIVE queue --a queue that "fast tracks" the job, but these jobs may "fall back" to another workflow queue. The fallback queue is determined by the number of locations modeled in the job. If the number of locations modeled is less than 1000, it is directed to the FIFO workflow queue. Otherwise, it is managed in a WFS DEFAULT workflow queue.

The INTERACTIVE queue is one of four types workflow queues available to a RI-RISKMODELER or RI-UNDERWRITEIQ resource group.

FIFO Workflow Queues

Secondary jobs are managed in the tenant's FIFO queue.

The FIFO queue is one of the four workflow queues available to a RI-RISKMODELER or RI-UNDERWRITEIQ resource group.

Default Workflow Queues

The DEFAULT queue is the primary queue for most secondary jobs submitted by a RI-RISKMODELER, RI-UNDERWRITEIQ, RI-EXPOSUREIQ or RI-TREATYIQ resource group.

The DEFAULT queue also functions as a "fallback queue" for primary jobs.

The DEFAULT queue is only workflow queue available to the RI-EXPOSUREIQ or RI-TREATYIQ resource group.