MPAC Connect

Programs

Add or change the rules a program is underwritten by. Every save becomes the next version automatically and goes to MPAC for approval.

Underwriting guidelines

Every guideline in use in this program, in one place: the built-in limits and the guidelines made from custom rules. A guideline always creates an underwriter action (refer or decline). Changing one creates its next version (for example UW-CPSF-FRAME@85 → @95). “Make it a guideline” on a custom rule moves it here; once MPAC activates it, other programs can add it from their “Not in use” list. Untick a guideline to take it out of this program.

OnGuidelineThreshold or conditionOutcomeActive versionHits

Risk score model — runs in MPAC

A points scorecard. MPAC checks every band of every factor for each location, scores the points of the band it accepts, adds them up and flags a score above 69 as High. The five component weights must add up to 100; changing them, the peril mix, the concentration settings or the limits those bands use makes a new model version in the MPAC rule registry.

Scorecard — every factor, band and points

Perils covered what the program insures against · used by Events

Choose every peril the program covers. A flood or storm surge event only counts against programs that cover flood; a wildfire only against those that cover fire, and so on. Locations an event reaches whose program excludes that peril are listed separately, not counted.

Placement types written full limit, shared & layered, or both

How the program's business may be placed. Full limit: one market writes the whole limit. Shared & layered: the schedule is placed as a tower of layers, each shared among markets, and every layer's position, attachment and limit is required. A submission of a type the program doesn't write is referred.

Capacity limits for this program on its capacity agreement · these refer or decline

Capacity is held at three levels, each summed by MPAC on its own: this program only (a limit on its capacity agreement that counts just this program), the whole agreement (every program on that capacity agreement together) and the MGA or MGU overall (every program it writes, under any agreement). So an MGA with two slips can give each slip its own limit and still have one overall limit. Each counts toward every level above it (the syndicate, the carrier, the reinsurer). Adding or changing one opens the Structure page's own rule form: saved as the next structure version, accepted by the other party and approved in MPAC.

Set above this program 🔒 protected: read-only here

The underwriting rules and capacity limits set higher in the structure, on this program's agreements and the parties above them (the carrier, its syndicate or division, the reinsurer). They apply to this program, and you can see them here, but you can't change them here: only the party that set one can, on the Structure page, as a version approved in MPAC.

Data specification

Which data elements a location must have for this program, and which it may have. The elements are one catalog in MPAC shared by every program, so "Roof age" here is the same Roof age every other program uses, and a check on it runs across the whole book. Required: MPAC checks every location for it, and a location without it comes back "Needs information" naming what to ask for. Optional: watched for completeness only. A column a file brought can be mapped onto an element that already exists (for example a file's "RoofShape" onto another file's "Roof Shape"), so every program reads it as the same element.

ElementIn this programComes fromThis programWhole bookOther programs

Concentration limits zones of counties or ZIP codes · these refer or decline

A limit on the bound TIV in a zone (for example South Florida: Miami-Dade, Broward and Palm Beach together, with a cap on each county), set on this program's capacity agreement or above it: the carrier, the reinsurer. MPAC sums the zone from the current book and answers for every submitted or quoted location in it: would binding it take the zone, or its county or ZIP, over the limit? If so it is referred or declined. Each limit is an MPAC rule version, approved in MPAC.

Risk concentration in the score

Points only: this adds to the risk score and never refers or declines on its own (for limits that do, see Concentration limits above). How the concentration part of the risk score is built. Choose the levels this program measures concentration at (ZIP code, county, 1 mile, a radius of its own miles, share of the submission), the weight of each one that's on (they must add up to 100), and the point at which it counts as full risk. MPAC sums the book's TIV at each level. The ZIP and 1-mile factors are measured against this program's limits above; county and the radius against the amount you set.

OnFactorWeightFull risk at
Custom factors

Your own concentration measures. MPAC sums the book's TIV for the locations that share a location's values of one or two fields, or attributes a file carried (book imports keep every column). Optionally count only locations that meet conditions, for example frame buildings built before 1990, grouped by county.

Custom rules

Conditions on the submitted values: the standard fields, and any column an uploaded file brought (Columns from files, below). MPAC checks each condition on the location's record; a location hits the rule only when MPAC accepts all of them. Locations missing any of the values are not checked.

Columns from files

When an SOV or a portfolio import has a column no standard field takes, the column is added to MPAC (its column catalog) the first time it is seen, and each location keeps its value on its MPAC record. Every program can then use it in custom rules and in custom concentration factors.

System matching and validation rules — the same for every program
RuleTypeLogic

Version history