Understanding Traffic Director Patterns in Coherent

Hello, I'm Brian O'Neill from Coherent. Today, I want to introduce you to a successful implementation pattern used by many of our insurance clients. This pattern utilizes a feature in Coherent called an X call, which allows one model to call another model within Coherent. This leads to various interesting applications, one of which is the traffic director pattern. Let's explore three examples of this pattern.

Example 1: Basic Traffic Director

The first example is a simple use of a traffic director to decide which version of a rater to call. On the left, we have a core system, such as Guidewire, Duck Creek, or Insurity. On the right, there is a CyberRater with multiple versions live simultaneously (versions 1 to 5). Complex business rules may dictate which version to use based on factors like policy renewal dates.

• Create a model called a traffic director.

• The traffic director examines inputs from the core system.

• It decides which version of the CyberRater to call using a decision table.

• Calls the appropriate version and returns outputs to the core system.

Example 2: Sophisticated Traffic Director

In this scenario, we have five algorithms (A, B, C, D, E) that can represent various processes, such as reserving algorithms or specialty lines products. The traffic director analyzes inputs from the user interface to determine which algorithm to call.

• Calls the selected algorithm (e.g., algorithm D).

• Algorithm D may have additional X calls to other models like expenses or taxes.

• These models can be shared across different services, enhancing reusability.

Example 3: Multi-State Workflow

Consider a scenario involving a commercial property policy. The traffic director evaluates inputs to determine eligibility and pricing based on state-specific rules.

• For a North Carolina property policy near the coast, it may decline immediately.

• If the property is further inland, it proceeds to quote using the North Carolina rating algorithm.

• This approach allows for more space in Excel models and avoids conflicts with different state rate filings.

These examples illustrate the advantages of using traffic director patterns, such as maintaining logic in one place and avoiding conflicts across teams. We will delve deeper into implementation details in future videos. If you have any questions or need assistance with your use case, feel free to reach out. Thank you very much.