Traffic Director Design: Orchestrating Workflows

Hi, I'm Grace at Coherent, and today I'll be showing you the traffic director design to tie together the rating and the underwriting rules. This tool helps orchestrate workflows across different services or even different versions of a service.

Example Scenario

In today's example, we have a multi-state workflow with:

• 50 different eligibility rules algorithms, one for each state, each with multiple versions.

• 50 different rating algorithms, each with multiple versions.

The goal is to price a property policy by running it through the correct version of the eligibility rules algorithms and determine if it is an accepted policy, declined, or referred. If declined or referred, results are sent back to the core system. If accepted, we quote it by calling the correct version of the rater and send those rating outputs back to the core system.

Traffic Director Functionality

The traffic director simplifies integrations by managing them into one integration with the core system. It receives inputs from the core system, decides which eligibility rules algorithms to call based on defined logic, and routes inputs to the correct rating algorithm if eligible, returning results to the core system.

Demonstration in Spark

In Spark, I've uploaded all services used for this demo. For this example, there are rules and rating services for Florida and North Carolina, each with up to two versions.

Traffic Director Excel Model

The traffic director is flexible and can be set up for various routing needs between services or versions. It relies on inputs from the core system to drive dynamic routing.

Inputs and Decisions

• Inputs from the core system are tagged as X inputs.

• These inputs help determine the right path for the rater or rule service to call.

• Three sub-decisions for each call: folder, service, and version of the service.

Logic is used to determine the folder, service, and version of the service. In this demo, all services are within one folder, and service names are based on state. A decision table is used to determine the version based on state and policy effective date.

Using the X Call

The X call specifies the path, sends inputs to that path, and receives outputs. For example, for a policy, version one of the Florida rules is called, and if accepted, inputs are sent to the Florida rater version one, returning the output premium.

Conclusion

This demonstration shows how the traffic director can effectively tie together rules and ratings, simplifying the integration process and ensuring accurate policy pricing and decision-making.