ARC
Sign inBook a call
Business Capabilities engine

Your systems, described in the language of the business.

ARC builds your organization's capability map, then reads each application's code to find the capabilities it actually delivers, every one backed by the rules, journeys and lines of code that prove it. Architects and the business finally look at the same picture.

Book a callSee Inventory
Corvane Mutual/Business capabilities

Business capabilities

Corvane's capability map for property and casualty insurance: 9 layers, 41 groups and 214 capabilities. Select a layer to open it.

  1. Capabilities

    Product & Rating

    Rate Filings
    Filing Preparation
    Filing Tracking
    Rate Change Impact
    Rating Engines
    Personal Auto Rating
    Homeowners Rating
    Commercial Package Rating
    Product Rules
    Coverage Definitions
    Eligibility Rules
    Form Selection

    Underwriting

    Risk Selection
    Appetite Guidelines
    Risk Scoring
    Third-Party Data
    Referrals
    Referral Routing
    Authority Limits
    Inspections
    Inspection Ordering
    Loss Control Reports

    Policy Servicing

    New Business
    Quote to Bind
    Policy Issuance
    Mid-term Changes
    Endorsements
    Cancellations & Reinstatements
    Renewals
    Renewal Offers
    Non-renewal Notices
    Re-underwriting

    Policy Documents

    Declarations
    Forms Library
    Regulatory Notices
    Integration

    Producer Channels

    Agency Portal
    Agent Quoting
    Service Requests
    Comparative Raters
    Rater Upload
    Bridge to Quote
    Direct Channels
    Online Quote
    Mobile Policy Access

Generated for "Property and casualty insurance" from the industry reference model and Corvane's intake answers.

01 Drafted, then refined

ARC drafts the map from your industry and intake. Ask for a change in plain language and it lands on the map.

Corvane Mutual/Business capabilities

Business capabilities

Corvane's capability map for property and casualty insurance: 9 layers, 41 groups and 214 capabilities. Select a layer to open it.

  1. Capabilities

    Product & Rating

    Rate Filings
    Filing Preparation
    Filing Tracking
    Rate Change Impact
    Rating Engines
    Personal Auto Rating
    Homeowners Rating
    Commercial Package Rating
    Product Rules
    Coverage Definitions
    Eligibility Rules
    Form Selection

    Underwriting

    Risk Selection
    Appetite Guidelines
    Risk Scoring
    Third-Party Data
    Referrals
    Referral Routing
    Authority Limits
    Inspections
    Inspection Ordering
    Loss Control Reports

    Policy Servicing

    New Business
    Quote to Bind
    Policy Issuance
    Mid-term Changes
    Endorsements
    Cancellations & Reinstatements
    Renewals
    Renewal Offers
    Non-renewal Notices
    Re-underwriting

    Policy Documents

    Declarations
    Forms Library
    Regulatory Notices
    Integration

    Producer Channels

    Agency Portal
    Agent Quoting
    Service Requests
    Comparative Raters
    Rater Upload
    Bridge to Quote
    Direct Channels
    Online Quote
    Mobile Policy Access

Generated for "Property and casualty insurance" from the industry reference model and Corvane's intake answers.

Your capability map. ARC drafts the map from your industry and intake. Ask for a change in plain language and it lands on the map.

Two maps, joined

Top down from the business. Bottom up from the code.

Capability maps drawn in workshops describe what the business wants and rarely match what systems do. Capabilities guessed from code read like class names. ARC keeps the two apart, builds each properly, and joins them with evidence.

L1
LayerThe broad areas of the business, such as Supply Chain or Client and Contract. Usually five to ten.
L2
GroupThe families of capability inside each layer: Purchasing, Inventory and Stock, Logistics.
L3
Business capabilityWhat the business must be able to do, in its own words. Up to 600 nodes across the map.
App
Application capabilityWhat one system actually does, found by discovery, with confidence and file-and-line evidence.
How the engine works

Generated, grounded, then confirmed by people.

Drafted from your industry

ARC drafts the map layer by layer, grounded in an industry reference model and in what intake told it about your business, rather than a generic template.

Edited like a document

Add, rename, move or remove nodes and mark the capabilities that are core to you, directly or by describing the change in chat. The map belongs to your architects.

Read out of the code

Discovery finds the ten to forty capabilities a typical application delivers, each linked to the business rules and user journeys inside it.

Every claim cited

Open any capability and see the rules, journeys and source lines behind it. If the evidence is thin, the confidence says so.

People confirm

Your experts accept, reject or deprecate each capability, and confirm where it belongs on the business map. Placements stay proposals until someone signs them off.

Feeds the plan

Confirmed capabilities become the units of the modernization plan: one specification per capability, built in order, traced back to the legacy code.

What it answers

The questions architecture boards actually ask.

Where do we have two systems doing one job?Overlap on the map
Which capabilities have no system at all?Empty groups
What breaks if we retire this application?Its capabilities and rules
What should the new system be built around?Confirmed capabilities

See your estate on one map.

Bring your current capability model if you have one, or let ARC draft it. Discovery on one application shows how the two maps meet.

Book a callSee pricing