In Touchstone Re, the highest organizational unit is the business unit. In a business unit, various users can manage their exposure and results data in two types of containers: companies and portfolios. The following diagram illustrates the relationship between business units, companies, and portfolios.
For information about how Touchstone Re stores data, refer to Touchstone Re Database Reference on AIR's Developer Zone.
A company is a container for all the data associated with a reinsurance company. For example, in the illustration above, Company A includes:
You can run loss analyses on one or more reinsurance programs in a company. The results of the loss analyses are stored in the company container.
Touchstone Re supports complex reinsurance structures or groups of reinsurance programs that are interrelated through inuring or sourcing relationships. Using the Touchstone Re APIs, you can manage the direct relationships associated with a given program. For example, consider that each relationship can be represented as a parent-child link. You can manage parent-child relationships, not parent-grandchild or other relationships.
A portfolio is a container for one or more reinsurance treaties (or layers). The treaties can come from any of the programs in the business unit. For example, in the illustration above, Portfolio A includes treaties from Program A and Program B in Company A and from Program A in Company B.
You can include the same treaty in multiple portfolios.
Touchstone Re supports two types of portfolios: static portfolios and dynamic portfolios. To create a static portfolio, you select one or more treaties from a list of all the treaties in the business unit. The portfolio does not change unless you add or remove treaties. In contrast, to create a dynamic portfolio, you specify a set of filters. The portfolio changes as you add or remove treaties in the business unit that meet the filter criteria.
You can run loss analyses on some or all of the treaties in a portfolio. The results of the loss analyses are stored in the portfolio container.