COMPASS Architecture

The Gen Re COMPASS Suite is a comprehensive and powerful tool for underwriting. It consists of several components, applied according to your needs.
The architecture of COMPASS enables the easy integration into any quotation system.

COMPASS Architecture

COMPASS is a Client-Server application. It consists of four main components:

  • COMPASS Engine to underwrite captured application data
  • COMPASS Client(s) to capture application data and show the assessment result
  • Databases containing the assessment rules
  • COMPASS RuleManager to modify the assessment rules

Client applications call the COMPASS Engine. The clients can request different services, such as capture application data, assess an application, etc. They can use different channels to communicate with the COMPASS Engine: REST Services, WebServices (SOAP over HTTP) or RMI (Remote Method Invocation). Further channels are available on request.

All communication between your systems and COMPASS is done via XML or JSON interfaces.

Assessment rules are stored in databases that are evaluated by the COMPASS Engine for the assessment. Rules are modified by the underwriter with our COMPASS RuleManager.

COMPASS is a pure Java application. Thus, COMPASS can run on every environment that supports a Java Virtual Machine (JVM). Certain components require a WebServer.


COMPASS needs to be integrated into your quotation / administration system. As soon as the applicant has decided on a benefit, this information is transferred to COMPASS via an interface. Based on the benefit COMPASS starts asking the relevant health questions.

Once all details have been entered, the application is assessed. The assessment result is written into an output interface and can be processed by the quotation/administration system, e.g., to calculate a new premium.


The ScreenBuilder XML-protocol describes the communication between a client that captures application information (capture-request) and the COMPASS Engine. This protocol tells the client which information (questions) should be visualised, and how the customer’s answers should be passed back to the COMPASS Engine.

There are two COMPASS Clients available that design the visuals for this protocol for you:

  • CaseViewer
  • TouchClient

The look and feel of these Clients can be customised within limits to meet your company’s user interface  guidelines.

As an alternative, an individually designed Client, based on the ScreenBuilder protocol, can be built.


Java VM

A Java VM 1.8 or newer has to be available in the COMPASS environment.

Database System

COMPASS needs a RDBMS. This can be any database system that supports SQL-92 and owns a JDBC-driver. Most database systems fulfil these requirements, e.g., DB/2, Oracle.

Production Requirements

In production the requirements for the engine as server / service depend largely on the maximum number of parallel clients, the workload by other processes, CPU(s) and the operating system. It needs to be defined individually to ensure immediate processing.

The COMPASS Service can be installed in a Cloud environment, and scaled according to the demand.


COMPASS comes with technical and underwriting-related support by Gen Re developers, who work according to your needs. In addition to our Hotline Services, we offer workshops to enable you to start working with COMPASS quickly.

For further information please contact Klaus Künzel.