---
schema_version: "1"
id: 014e5cf9a921a37c4ee0c714735de4c89e0d3de33a97e9ef48cb0e6a734f3b2c
title: Grouped Calculation Matrices (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_grouped_calculation_matrices.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_grouped_calculation_matrices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 26f010c8c753910bfecd3c702a84f3b7d7c2dbc845fc506a6b0e4889692f908d
description: For the managed package runtime, you can create groups of calculation matrices, and subgroups within each group.
products:
  - Omnistudio
release: "264"
---
# Grouped Calculation Matrices (Managed Package)

For the managed package runtime, you can create groups of calculation matrices, and subgroups within each group.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

Grouped calculation matrices have several benefits:

- Grouped calculation matrices are designed to work best for insurance carriers that have lots of matrices which are almost exactly alike: same input headers and same output headers.
- Grouped calculation matrices improve management and reduce size requirements.
- Vlocity uses only one SOQL query to query a group of matrix versions.
- Insurance carrier staff members who keep the calculation matrix data up to date can create and enable new versions of a matrix without touching any other versions.

However, grouped matrices have some limitations. Each matrix in a group must have all the same input and output column headers.

![example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

example

Property and Casualty Sample Use Case

An auto insurance carrier has different insurance rates for different jurisdictions (such as states). The carrier needs to manage each jurisdiction separately, but they don't want to have to create a separate calculation for each jurisdiction (because all the calculations are the same).

So this carrier creates a different calculation matrix for each state it offers insurance within, using Jurisdiction as the Group Key.

All the input and output headers are the same, only the values differ. Each state's calculation matrix can be updated at a different time, and new versions can be activated at different times.

![example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

example

Group Health Sample Use Case

Each provider in a health insurance carrier's network has a different fee schedule, and these fee schedules must be updated throughout the year as providers change or renew their contracts with the carrier.

The Group Key for this calculation matrix is ProviderFeeSchedule, and each version of the calculation matrix is for a specific provider.

At execution time, Vlocity uses the group key to find the correct grouped calculation matrix, and the provider code to pick the correct version of the matrix.