Celent EMEA PAS (Personal, Comercial, Specialty) 2018 ABCD Vendor View

Download as pdf or txt
Download as pdf or txt
You are on page 1of 290

EUROPE, MIDDLE EAST, AND

AFRICA POLICY
ADMINISTRATION SYSTEMS
2018
PERSONAL, COMMERCIAL, AND SPECIALTY ABCD VENDOR
VIEW

Craig Beattie
May 2018
CONTENTS

Executive Summary ............................................................................................................ 1


Introduction.......................................................................................................................... 2
Policy Administration Systems: Definition and Functionality .............................................. 8
Report Method .................................................................................................................. 16
Celent’s ABCD Vendor View ............................................................................................. 22
Vendor Profiles .................................................................................................................. 27
3i Infotech Ltd: PREMIA General Insurance Suite ............................................................ 29
Adacta Group: AdInsure .................................................................................................... 35
Adcubum AG: adcubum SYRIUS ..................................................................................... 42
adesso insurance solutions GmbH: in|sure General......................................................... 50
AdvantageGo: Navigator ................................................................................................... 56
AETINS SDN BHD: Insurance Solution Framework (ISF) ................................................ 61
Beyontec Solutions, Inc.: Beyontec Suite ......................................................................... 67
Cálculo S.A.: e-tica ............................................................................................................ 74
CCS: Roundcube Policy.................................................................................................... 80
Duck Creek Technologies: Duck Creek Policy ................................................................. 87
DXC Technology: GraphTalk A.I.A ................................................................................... 97
DXC Technology: Xuber for Insurers .............................................................................. 103
ESKADENIA Software: ESKA Insures - General Insurance ........................................... 108
Fadata: INSIS .................................................................................................................. 115
Faktor Zehn AG: Faktor-IPM ........................................................................................... 122
Guidewire Software Inc.: Guidewire PolicyCenter .......................................................... 129
i2S Informática - Sistemas e Serviços S.A.: i2S Non-life ................................................ 137
Insurance Business Applications (IBA): IBSuite ............................................................. 144
ICE InsureTech: ICE Policy............................................................................................. 150
Insicon AB: Insicon i2i ..................................................................................................... 156
Javision Ltd.: Inamon ...................................................................................................... 163
Keylane: QIS Policy Management .................................................................................. 168
Majesco Ltd.: Majesco Policy for P&C ............................................................................ 176
Markit Systems Limited: Markit - DA (Delegated Authority) ............................................ 182
msg systems ag (msg group): msg.PIA (Primary Insurance Application) ...................... 189
Oceanwide Canada, Inc.: Bridge Insurance Software Suite ........................................... 195
Prima Solutions: Prima Insure......................................................................................... 201
RDT Ltd: Landscape ....................................................................................................... 207
RGI S.p.A.: PASS_Insurance 3.0 ................................................................................... 213
SAP SE: SAP Policy Management ................................................................................. 223
Sapiens: IDIT .................................................................................................................. 229
Sequel Business Solutions: Eclipse Underwriting .......................................................... 238
SSP Limited: SSP Pure Insurance .................................................................................. 243
SSP Limited: SSP Select Insurance ............................................................................... 249
Tata Consultancy Services: TCS BaNCS for Insurance ................................................. 255
TIA Technology: The TIA Solution .................................................................................. 260
Total Systems PLC: Bluescape ...................................................................................... 269
Zov Solutions OOD: SID ................................................................................................. 276
Concluding Thoughts ...................................................................................................... 283
Leveraging Celent’s Expertise ........................................................................................ 284
Related Celent Research ................................................................................................ 285

Chapter: Executive Summary

1
EXECUTIVE SUMMARY

This report provides an overview of the policy administration systems available in Europe,
the Middle East and Africa for non-life, general insurance or property & casualty
insurance carriers. The report profiles 38 policy administration solutions, providing an
overview of the functionality, the customer base, lines of business supported, the
technology, implementation, pricing, and support. Some solutions qualified for profiles
that include customer references and a Celent opinion of the solution. Those solutions
are also ranked in the ABCD Vendor View. Some solutions did not qualify to be ranked in
the ABCD Vendor View, and those profiles do not include a customer reference or a
Celent opinion.

The following vendors are included in this report: 3i Infotech Ltd, Adacta Group, Adcubum
AG, adesso insurance solutions GmbH, AETINS SDN BHD, Beyontec Solutions, Inc.,
Cálculo S.A., CCS, Duck Creek Technologies, DXC Technology (two solutions),
ESKADENIA Software, Fadata, Faktor Zehn AG, Guidewire Software Inc., i2S
Informática – Sistemas E Serviços S.A., Insurance Business Applications (IBA), ICE
InsureTech, Insicon AB, Javision Ltd., Keylane, Majesco Ltd., Markit Systems Limited,
msg systems ag (msg group), NIIT Insurance Technologies Limited, Oceanwide Canada,
Inc., Prima Solutions, RDT Ltd, RGI S.p.A., SAP SE, SAPIENS, Sequel Business
Solutions, SSP Limited (two solutions), Tata Consultancy Services, TIA Technology,
Total Systems PLC, Zov Solutions OOD.

This report also names the winners of the XCelent Awards:

• XCelent Technology for the leading Advanced Technology score:


Sapiens IDIT
• XCelent Functionality for the leading Breadth of Functionality score:
Guidewire PolicyCenter
• XCelent Customer Base for the leading Customer Base score:
Fadata and RGI
• XCelent Service for the leading Depth of Service score:
Adcubum and Guidewire
INTRODUCTION

KEY RESEARCH QUESTIONS


Which systems win
What is a property
Who are the Celent’s 2018
& casualty/general/

1 specialty policy
administration
system?
2 vendors in the
EMEA marketplace
by line of business?
3 Property &
Casualty/General/
Specialty PAS
ABCD Awards?

Significant innovation is occurring in product management and underwriting in Europe,


Middle East, and Africa. Insurers are looking to grow, differentiate themselves, navigate
the regulatory environment, and do all of this efficiently. At the same time, they are faced
with an explosion of new technologies such as AI, the Internet of Things, drones,
wearables, and big data, to name only a few. As millennials become a larger proportion
of buyers, customer attitudes and expectations are changing. Mobile and social are
driving escalating expectations for customer service.

Insurers are focusing their investments on initiatives to drive growth and efficiency.
Underwriting is central to these goals as carriers drive to have the right products, priced
well and processed efficiently with consistent, often superb customer service.

Significant change has been happening in the processes of product development.


Certainly, many carriers still use legacy practices. More recently some insurers are
focusing on expanding their product set with more product innovation. Insurers are
utilizing more complex rating schemes and using a wide variety of data elements in their
rating algorithms. In commercial lines, insurers are generally moving to product
innovation on endorsements tailored to specific industries. Being able to take advantage
of these trends requires the ability to rapidly make product changes, ingest third party
data easily, and easily change business rules. Highly configurable product development
environments are a requirement to deliver rapidly changing products, along with systems
allowing fast change in distribution.

The most innovative insurers are focusing their product management efforts on unique
products such as behavior-based products, or products with services embedded.
Telematics is such a product. It bases the pricing of the product on the driving behavior of
the policyholder and often includes additional services such as driver tracking, fleet
monitoring, or gamification platforms.

Changes in pricing are occurring too. Multivariate rating algorithms are being used, and
product managers are using predictive analytics as a key tool in providing pricing
guidance for books of business. Some carriers have dynamic business rules, or are using
Chapter: Introduction

machine learning, to monitor the underwriter’s pricing behavior on a book of business and
dynamically providing pricing guidance. Some use predictive analytics to assess the loss
ratio going forward and adjust pricing in real time.

These kinds of advancements change the role of the product manager. Product
managers must add business rules management and analytics to their portfolio of skills.
In addition to providing oversight on individual policies or transactions, they now need to
be experts in formulating and monitoring rules. Managing when and how often
2
underwriters override rules, assessing the frequency and impact of the use of a rule, and
determining when to retire, modify, or enact a new rule are all critical tasks in the new
practice of rules governance.

Just as product management is changing, so the practice of underwriting is also


changing. The typical underwriting practice is for an individual underwriter to gather a
combination of customer-provided data and third party data such as financial information
through an application and third party data calls. Physical inspections or photos are
required on most properties over a certain value or in a particular fire zone. Data is
generally entered manually by an underwriter or is uploaded from an agency
management system into the policy administration system. The underwriter uses a
combination of company guidelines and their own underwriting judgment to assess the
risk and determine the appropriate terms, conditions, and price. Fully automated
underwriting is used only on standard lines such as personal motor and home. Cross-sell
occurs when the underwriter remembers to offer additional products. Most
correspondence is handled manually by the underwriter, and documents are often stored
in a document management system that is separate from the policy administration
system, requiring an underwriter to search a separate system when looking for
documents. Workflow is often depicted as screen flow in the policy administration system,
or is handled in a third party system. Many companies still have challenges handling out
of sequence endorsements. Most companies have some kind of automated renewal
process for business that meets certain criteria.

The typical process above can be quite costly because it requires substantial human
intervention and is prone to errors. Carriers are moving toward a more automated
process, which can streamline cost and improve decision-making. Carriers are providing
prefill — pulling in third party data to prefill an application, thereby reducing the data entry
needs of the agent and/or underwriter. Fully automated underwriting is extending to more
complex lines: small and medium business (SMB/SME) and workers comp. Business
rules and scoring are being used to provide risk assessment and pricing advice on more
complex business. Carriers are using business rules, predictive analytics, and machine
learning to automate the cross-sell of standard products such as cross-selling
commercial motor on a small business policy, or an umbrella on a property policy. Easily
changed business rules are a prerequisite for offering these capabilities. As carriers fully
automate the underwriting of a line of business, they have to be able to rapidly and easily
change a business rule as the business environment or regulation changes.

The most innovative carriers are heavily using analytics in a variety of ways. Analytics
have the most impact when used to assess risk quality and provide pricing guidance.
Insurers have reported loss ratio improvements of 4–10 points when implementing this
type of initiative. Analytics are also being used to minimize inspections or the ordering of
third party data. Why routinely order costly data to support rating? Carriers are predicting
which data are most likely to be material to the insurer and only ordering those, thereby
reducing their costs.

In commercial lines, carriers use analytics to determine which accounts should get a
physical audit versus a paper audit. Uber-like inspection services are being used,
allowing carriers to significantly increase the speed of getting a photograph. In addition,
carriers are experimenting with drones for property inspections. New sources of data are
being used, including social media scores (using social media presence to assess risk).
Chapter: Introduction

Other carriers use social media to assess a prospect’s risk profile and are driving cross-
sell initiatives based on that risk profile. Sophisticated product recommendation tools are
being created, and automated cross-selling of unique products is occurring. Carriers must
have the ability to create business rules and to have event- and data-driven workflow in
order to automate these tasks. The automated delivery of customer communications is a
key requirement, and some carriers are now using tailored video as a component of their

3
customer communications, using XML streams from the policy admin system to
dynamically create videos to deliver information such as a welcome letter.

To support these types of expansions, insurers have to have more capabilities in the
policy administration system. Business users expect a variety of improved capabilities.
They want to improve internal workflow to support business process changes to improve
efficiencies and reduce expenses. They are looking to improve consistency in handling
procedures, both to improve customer service and to avoid compliance issues. Insurers
need to improve flexibility in managing rules to respond quickly to regulatory changes. As
more insurers use predictive analytics, they want the ability to operationalize predictive
analytics through rules and workflow — especially to better assess risk and optimize
pricing. They expect increased data accessibility as they add new data elements and look
for new, unique insights in their data. In addition, they want a modern, intuitive user
interface for their employees, agents, and partners.

The IT organization wants everything the business wants because their goal is to enable
the business to perform well. In addition, IT is looking for a platform to enable an agile IT
department in order to facilitate great IT/business alignment. This means a highly
configurable system with a variety of strong granular tools including tools to manage the
testing and the release cycle. They want standards-based commodity technology that will
allow variable staffing strategies. One of the biggest drivers of the system selection
decision is the functionality. IT expects a minimal functionality gap with an out of the box
template for every line, in order to speed up the implementation process and reduce
customization. Inherent in all these demands is reduced technology risk — meaning a
modern architecture that simplifies the insurer’s footprint and a track record of success in
similar lines of business with similar size clients.

Policy administration vendors have responded by enhancing functionality. Significant


levels of research and development have been occurring in the vendor community.
Vendors are investing as much as 50% of their revenue in product enhancements. Most
have upgraded their system with a modern look, feel, and navigation and a functionally
rich UI. Configuration tools continue to become more user-friendly — and tools for the IT
organization are more likely to be included. More and more vendors have deep
partnerships with add-on technologies such as document creation, document
management, analytics, and reporting in order to simplify the application architecture for
a insurer. Mobile apps are common, and most vendors can offer a hosted solution for
insurers that want to outsource infrastructure management or obtain other managed
services.

A TRANSITION TO A NEW ARCHITECTURE BEGINS


In the past year or so, there has been an explosion of interest in a new architecture for
insurance systems (and for many other types of systems as well). This new architecture
is characterized by microservices and APIs which are typically cloud-based. (For a more
detailed discussion of microservices and APIs, see the Celent report Honey, I Shrunk the
Services: Microservices in Insurance, December 2017.)

For the purpose of this discussion:

• An application programming interface (API) is a method of communicating with a set


Chapter: Introduction

of microservices (or other services). An API Gateway a software tool that publishes
the API and allows a set of internal or external code to interact with the API.
• A microservice is a self-contained, deployable component that contributes an API to
a wider architecture. A microservice’s actions are typically limited in scope (for
example looking up GPS coordinates, as opposed to looking up GPS coordinates
and finding construction characteristics of a building at that location).

4
Figure 1 shows how programs or physical servers interact with an API Gateway and a set
of microservices.

Figure 1: Simplified Diagram for Microservices and an API Gateway

Source: Celent Report, Honey, I Shrunk the Services: Microservices in Insurance

In general, APIs and microservices may be built, maintained, and modified more quickly
and more efficiently than other types of functionality and integration methods in other
types of architectures. They are also more open in the sense that other internal or
external systems can access functionality or data more easily.

Over the next several years, microservices and APIs will likely coexist with legacy policy
administration and other core systems, as shown in Figure 2.

Figure 2: Near-Term Legacy Modernization Mixed Architecture

Source: Celent report, Honey, I Shrunk the Services: Microservices in Insurance

The third element of the new architecture is that it is cloud-based.

• Cloud-based in this context refers to a policy administration or other core system


deployed in a server located off-premise from an insurer, for which a cloud
provider supplies Infrastructure as a Service, or IaaS (including computing,
storage, and networking resources); and Platform as a Service, or PaaS (which
could include tools for programming, analytics, and database management).
Chapter: Introduction

5
A cloud-based policy administration system may be licensed by a vendor to an insurer,
which in turn deploys it in a cloud (Figure 3).

Figure 3: A Cloud-Based Core System Deployed by an Insurer

Source: Celent repor, Security for Core Insurance Systems in the Cloud

Or the vendor itself may deploy the policy administration system in the cloud, and give an
insurer access to that system either by means of a subscription (Software as a Service,
SaaS) or a license (see Figure 4).

Figure 4: A Cloud-Based Core System Deployed by a Vendor

Chapter: Introduction

Source: Celent report Security for Core Insurance Systems in the Cloud

There are several advantages in both types of deployment, including: transforming


certain capital expenditures into variable costs, rapid provisioning of computing and
storage resources, nearly unlimited scalability, shorter development cycles for both initial

6
implementation and ongoing maintenance, minimizing latency across widely dispersed
user locations, and improved business continuity and disaster recovery.

Taken together, microservices, APIs, and cloud-based systems have already begun to,
and will continue to, transform the architecture of policy administration and other core
systems.

With all these changes in the business and in the vendor community, it is no wonder that
we continue to see policy administration replacement as a high priority activity in EMEA.

Chapter: Introduction

7
POLICY ADMINISTRATION SYSTEMS: DEFINITION AND
FUNCTIONALITY

Key What is a property & casualty/general/specialty lines policy


Research administration system?
Question
The primary system of record for property &
1 casualty/general/specialty insurance business
operations, handling all transactions from the front
end of individual policyholder management to the
back end of billing and premium payments. They
also store all product rules and definitions.

DEFINITION
In one sense, the definition of a policy administration system (PAS) is very simple — it is
the system of record for all policies that an insurance company has written. At this most
basic level, a PAS is a repository of policy-level data related to objects of insurance,
coverages, limits, conditions, exclusions, duration of the policy, endorsements, and so
forth. A permanent policy record is created at the time a policy is issued, and it includes
the complete history of the policy through renewal, termination, cancellation, and/or
reinstatement.

Figure 5: Policy Administration System Core Processes

Suite Functionality Features and Functions

Chapter: Policy Administration Systems: Definition and Functionality


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Source: Celent

8
In actual practice, an insurer uses a PAS — either by itself or closely integrated with
specific point solutions — to execute a number of core processes, and relies on several
types of supporting capabilities, as shown in Figure 5. All modern core policy systems
provide basic functionality for the most standard processes of quoting, issuing, endorsing,
and renewing a policy. However, there is significant variation in the way the solutions
handle these functions.

TRANSACTIONAL SERVICING FEATURES


A variety of features are available to handle the day-to-day transactional activities of
quoting, issuance, endorsements, renewals and cancellations.

Scheduling/Calendar/Diary. A wide variety of tools are available to help the underwriter


manage their workload. Underwriter desktops typically include an area where new
business quotes, policies needing issuance or renewal, endorsements, and other
assigned tasks are easily found. User interfaces can vary widely but often include
features such as the ability to sort by clicking on columns, to filter columns, and to drag
and drop and rearrange columns. All solutions include search, but some include sounds-
like search, partial word search, Boolean search, or wildcards. Most systems allow
underwriters to create manual diaries, tasks, and notes and to easily see their work in a
calendar format. Many are integrated with email, allowing an underwriter to send an email
from the desktop. Many include a policy or account summary that contains the most
important information about a policy or account and is available at a glance from any
location within the policy. Some solutions allow the underwriter to customize their own
workspace, choosing which modules they want displayed, selecting a color scheme, or
adding links to commonly used third party websites. Other capabilities such as
configurable help text, hover-overs, and wizards can help an underwriter easily navigate
through the task.

Quick quote and full quote. Agents and underwriters often want to get a quick
indication of risk acceptability and price and to compare the price of different options.
Quick quote functionality allows a price to be generated with minimal data entry. The data

Chapter: Policy Administration Systems: Definition and Functionality


entry screen contains only those questions needed to calculate a rate or to determine the
basic terms and conditions of the policy. Sometimes the questions will include basic risk
acceptability questions, but quick quote is not usually intended to handle the full
underwriting of the policy. Many solutions include the capability for dynamic questions
that expand and change based on the answers to specific questions, allowing the system
to prompt the broker or underwriter to get more detailed information based on insured’s
responses. Multiple versions of the quote can be generated to see the impact of different
terms, conditions, and product choices. Some solutions handle the side-by-side quoting
by opening separate windows. Some allow different quote versions to be saved. More
and more are offering side-by-side quoting in a single window. Once a quote is
generated, some solutions allow for multiple side-by-side views of different options. The
user can change a deductible in version one, or a limit in version two. Some solutions use
dropdowns to show the different available options, with the price difference for each
option shown next to the label within the dropdown itself. Most solutions include the
ability to create and display rating worksheets (a detailed listing of how the premium was
calculated). Some have the ability to show simplified versions to the brokers, and detailed
versions to the underwriters.

ACORD upload. ACORD offers data standards in the insurance industry — although it
has less penetration in EMEA than in other regions. ACORD standards are used in the
London Market for specialty and reinsurance lines, as well as some use of (different)
ACORD standards in South Africa.

Data upload. Specialty and commercial lines policies often include large schedules of
drivers, locations, vehicles, or equipment. Many systems allow these schedules to be
imported or uploaded from an Excel spreadsheet. Some systems require that the

9
spreadsheet be formatted in a particular order. Some allow mapping of the spreadsheet
as the spreadsheet is being uploaded.

Data services. Underwriters rely heavily on third party data or reports from external data
services. Most systems have some level of preintegration with the most common data
service vendors. Some require the underwriter to manually request the external data.
Others use business rules to automatically send the data request and retrieve the data or
report. Some can take the data retrieved and populate the specific field; others store the
data as a record that the underwriter can review, and the underwriter can then enter the
data into the correct field in the policy record.

Automated underwriting. Many solutions have the ability to use business rules to
automate the underwriting process. The solutions use business rules to determine if the
transaction can proceed without human intervention, or if intervention is required, a task
is generated for the underwriter to review and take action. Some solutions can handle
basic yes/no questions only. Others can perform very sophisticated underwriting. The
capabilities are heavily influenced by the level of sophistication of business rules and
workflow capabilities.

Underwriter assignment. While some insurers still assign work manually, more and
more insurers are looking for automated support in the underwriting process. Solutions
handle underwriter assignment in a variety of ways, for example the ability to assign
policies/quotes to a team or individual using a round-robin capability, or the ability to
assign to specific individuals based on specific criteria. Some solutions can assign a
transaction very granularly, based on line of business, agent, geography, and workload.
Most systems allow multiple underwriters to be assigned to work on a single account
handling different policies. Carriers also look for capabilities for manual assignment or
reassignment for both bulk transactions or single policies or accounts.

Automated renewals. Most solutions have the ability to handle no-touch automated
renewals. If the policy meets the insurer’s defined requirements, the information from the
original policy carries over to the renewal, and the policy is issued. Some allow business

Chapter: Policy Administration Systems: Definition and Functionality


rules to be used to apply an inflation factor automatically, or to make other bulk changes
on policies as they renew. Those policies that do not meet the requirements are popped
out of the renewal cycle and assigned to an underwriter for intervention. Along with
automated renewals, look for automated non-renewals. Some allow a policy to be
marked for non-renewal. Some allow business rules to be used to determine whether an
underwriter will allow the policy to renew. In the case of an automated non-renewal, the
system generally can send out the appropriate documents in the right timeframe
according to the jurisdictional requirements of the policy.

Endorsements. Endorsements are changes to a policy, sometimes referred to as mid-


term adjustments or MTAs. All systems can handle endorsements. Almost all systems
can handle out-of-sequence endorsements as well. When it comes to out-of-sequence,
there are a variety of techniques in place. Some alert the underwriter to the fact that the
policy change is out of sequence. Each affected endorsement is identified, and the
underwriter can select which to back off and which to roll back on. Others handle the
back-off and roll-on automatically only highlighting conflicts for an underwriter’s
intervention. At least one solution can handle multiple policy changes with different dates
on a single endorsement. Mid-term broker of record changes can often be handled as a
bulk transaction, but some systems require the changes to be done policy by policy.
Some allow a lot of flexibility as to when commission changes occur, and some allow the
commission to begin accruing to the new broker immediately. Others begin the
commission accrual at the time of renewal.

Multiple Insurers or Coinsurance. A common requirement with commercial insurance


across EMEA, this allows multiple underwriters to be recorded against a single policy,

10
with some details on the lead insurer, share of risk, and any commission or pricing
scheme involved.

PRODUCT MANAGEMENT CAPABILITIES


In addition to transactional capabilities, a policy administration system is the primary
repository for the product rules, rates, and forms attachment logic for all products.

Rating. Most but not all solutions include rating engines as a key feature. As vendors are
creating more sophisticated configuration tools, rate changes can be done by business
analysts rather than developers. The rate tables, rules, and algorithms are externalized
from the programming code. There are wide variations in the level of sophistication of the
rating engines. As insurers have been moving to more complex rating algorithms, rating
engines have expanded their ability to support complex rating algorithms including
multivariate rating and by-peril rating. Most allow multiline, multilocation rating on a single
quote or policy. Many also allow multistate rating. Look for the ability to use external party
information sources (e.g., credit score, loss data, property data, predictive scores, etc.) in
the rate algorithms during real-time calculation. Other features to look for include the date
management capabilities — the ability to manage multiple dates based on the versions of
the rate, table, or algorithm changes. Some solutions require the versioning dates be
embedded in the code or script. Others provide fields to enter the dates. Some allow
different versions or effective dates for renewals versus new business.

Rate analysis. Some solutions include very robust tools for handling the rate analysis
function. Testing, modeling, and product analysis tools are included that allow an insurer
to do an impact analysis — calculating the overall impact of a rate change or a
displacement analysis — identifying the number of policyholders that will be impacted.
These types of tools are typically found in those solutions that include a stand-alone
rating engine that can be sold separately. Some vendors have business intelligence tools
included and are able to set up reports that can provide some level of analysis as well.
Many solutions do not include any functionality for handling rate analysis or testing.

ISO Support: Included here for consistency but is only relevant to the North American

Chapter: Policy Administration Systems: Definition and Functionality


region. Almost all commercial lines insurers rely on ISO for rates, rules, and/or forms.
The most significant new option is the ISO Electronic Rating Content (ERC). With ERC,
ISO offers their rating content in an electronic format. This service has many features —
all of which are intended to streamline the process for insurers, allowing them to take
revisions faster. ISO provide all circulars in an electronic format. They provide loss costs,
rules, and forms attachment logic in both XML and Excel format. They include a reporting
utility that helps insurers identify and understand the differences between the circular
revisions and the insurer’s current rating structure, including their program deviations.
Carriers can subscribe to ISO ERC, but to get full value, their policy administration or
rating system needs to be able to absorb the XML stream or Excel files.

Product Development Tools: The product architecture is a key component of a policy


administration system. Often when implementing a new system, this is an area that
requires significant work on the part of a insurer — redesigning their products to match
the architecture inherent in the policy administration system. Many solutions have a
product architecture that is depicted as a tree, which allows inheritance across
jurisdictions for common features. Some include color-coding that helps an insurer easily
identify where a product does not conform to the nationwide version. Some keep their
product architecture in an Excel or Excel-like format — which can be easy for the
business to maintain, but can sometimes result in additional complexity for insurers with
many lines of business across many states. Some solutions include wizards that make it
very easy for a business user to make basic parameter-driven product updates. Some
include a self-documenting product dictionary. The dictionary is the source of complete,
reusable insurance product definitions including rates, underwriting rules, calculations,
specifications, integration definitions, and data for managing forms so all of it can be

11
defined as reusable components that can be rapidly adapted to form new products or
enhancements. Some product dictionaries are very business user-friendly with natural
language definitions.

Reinsurance: One of the newer areas that vendors have begun to invest in is
reinsurance capabilities within the policy administration system. Most solutions do not
include this functionality. The most robust solutions allow for full program definition.
Carriers can identify multiple treaties based on perils, lines of business, geographies, or
other dimensions. Treaties can be assembled into programs with specific inurements
identified. The solution will create bordereaux reports tracking the exposures, the
commissions, and the premiums back to the reinsurer. Some allow an underwriter to
manually mark a policy as reinsured with some basic information about any facultative
contracts. Some have set up reports that allow for some basic reporting on policies that
meet basic treaty requirements.

COMMON FUNCTIONALITY
There are a variety of functions that are not specific to underwriting or product
management, but can generally be found in a policy administration system.

Workflow. Some solutions serve more as data capture tools. Workflow is simulated with
screen flow. Other solutions have true workflow capabilities — the ability to automatically
generate and assign tasks based on event changes in a policy, time lapse, or data
changes in a field. Some of the solutions profiled have the capability to visualize the
workflow through graphical depictions. Some have a graphic design environment, with
automated background code generation. This means graphical depictions are actionable
— clicking on a step allows the insurer to modify that step, or steps can be dragged and
dropped to rearrange the sequencing. It is not uncommon for a software vendor to use a
third party or open source tool to manage the workflow requirements.

Document creation. Most of the solutions include some sort of correspondence or forms
library for the most common forms and letters. Many integrate to third party solutions to

Chapter: Policy Administration Systems: Definition and Functionality


provide additional capabilities because many of the built-in solutions are not robust
enough to handle production-level policy generation. Look for standard templates out of
the box. Many of the solutions will come preloaded with ISO, NCCI, or Bureau forms out
of the box. The forms attachment logic is typically included as part of the product
definition, and the templates themselves are included in the document creation tools. In
addition to policy forms, many systems can automatically generate correspondence using
business rules and task generation capabilities. When an event occurs, or the data within
a field changes, the solution can automatically create correspondence that can often be
delivered using a variety of mechanisms: mail, email, or SMS.

Document management. Some systems contain a document management capability


allowing for storage of internally generated documents and external documents such as
photos, videos, and other media. Many integrate to external third party solutions to
provide more scalability. Look for the level of granularity in indexing forms being created.
When a policy file holds hundreds of items, being able to rapidly sort to find the document
needed can save time. Look for not just ability to search the metadata about the
document, but also ability to search within the document.

Reporting. Reporting capabilities vary widely across solutions. Virtually all solutions
integrate to a third party reporting tool. Some include a third party reporting tool out of the
box. Some solutions use open source reporting tools, and some have in-house built
solutions. Most include some level of prebuilt standard reports that can be subscribed to
or scheduled. Standard reports typically deliver operational reports, performance
measures, and some level of financial reporting. Look for the number of reports included
out of the box. Ad hoc capabilities vary widely. Some are quite easy to use, with the
ability to drag and drop data elements and build a report very simply. Many include
12
dashboards with graphical views of data, and many of those include drilldown
capabilities.

Mobile/multichannel access. Almost all solutions are browser-based and so are


available via a tablet or mobile device for an underwriter in the field. More and more have
been optimized for a mobile device using HTML 5 or responsive design. Some solutions
come with mobile applications out of the box meant for a potential policyholder to access
their policy, pay their bill, or get proof of insurance.

TECHNICAL FUNCTIONALITY
While assessing features and functionality is a critical step in selecting a policy
administration system, there are a number of technical considerations to be considered
as well.

Configuration tools. A general trend in insurance software is to create tools that allow
insurers to do more modifications of the system through configuration tools rather than
through code. The most robust tools allow insurers to easily add data elements, create
business rules, modify workflows, create forms, create screens, modify the user interface,
and even map interfaces, all using configuration tools. Some tools are extremely intuitive
with drag-and-drop and point-and-click capabilities. Others require knowledge of a
scripting language to make the changes. Many vendors are moving toward a dual
development environment with simplified tools and wizards meant for Business Analysts
to make general changes and a more robust environment meant for technical staff to
utilize.

Business rules. Look for the ability to design and execute business rules and
underwriting rules that are separate from the core program code. Carriers should assess
the ability to reuse and share rules. Some tools are extremely intuitive and use natural
language; others require knowledge of scripting. Some have visualization tools that allow
a insurer to use a Visio-like tool to build business rules. Some solutions include a
searchable and version-controlled rules repository. A few solutions offer tools to help

Chapter: Policy Administration Systems: Definition and Functionality


insurers conduct impact analysis of the rules or traceability tools to understand how and
when rules are being used. Since many insurers create hundreds or thousands of rules,
there should be a strong rules management environment with a well-organized
repository, version control and version storage, etc.

Data. Data is more and more important for insurers, and software vendors are
acknowledging this by building in more tools to help insurers with their data needs. Some
solutions deliver a certain number of extra fields that users can modify for their own use.
More common are configuration tools that allow the easy creation of data elements
including the ability to mask data, encrypt data, add context-specific help text, and modify
the data model. Self-documenting data dictionaries are available. Some solutions come
with an ODS out of the box and may even include a data warehouse with the appropriate
ETL tools. Most solutions are built on an industry standard model such as ACORD.

Security. Often desired is the ability to easily add a new role and define the permissions
for that role as well as the ability to easily add an individual to that role. Permissions may
simply mean read/write permissions. Some solutions offer access granularity down to the
data within the field level. For example, if party type equals insurer employee, limit
access to this claim to only those with permission to see employee data.

Scalability: While we typically think of scalability in terms of the number of policy


transactions, or the number of users, an additional area to examine is how the system
handles multiple locations or vehicles on a policy. Performance as the system scales is
another important consideration.

13
Integration: Policy administration systems integrate to large numbers of third party
systems and external data sources. Most solutions have been designed with a Service-
Oriented Architecture and have a variety of ways of handling integration including Web
Services, ACORD Standard XML, Other XML, RESTful HTTP style services, JSON
format, MQSeries, JMS or similar queue technology, Flat files, Custom API, or other
methods of integration. Most systems have some kind of accelerator, or experience
integrating to the most common third party data sources and the most common general
ledgers.

Implementation: Vendors use a wide variety of implementation methodologies. Some


prefer to handle all of the implementation themselves. Others prefer to work with third
party system integrators. More and more vendors are moving to agile or a hybrid
methodology as their preferred methodology. Look to see what methodology the vendor
uses and how it aligns with your own preferred methodology. Some vendors are very
good at helping insurers transition to an agile approach. Look for the artifacts they have
available for gathering requirements documenting the product architecture, and capturing
the business rules. Vendors claiming very fast implementation timeframes may indeed
have better artifacts and more configurable solutions, or they may be touting very simple
single product implementation with little or no configuration. Be sure to do customer
reference checks to understand how well the vendor handles project management,
knowledge transfer, and scope creep with insurers of a similar size and complexity as
your company.

Cloud: Few technologies are as talked about as cloud computing. Cloud-enabled


solutions are on the rise, with most of the responding vendors reporting that they have
cloud-enabled core systems. When it comes to the term “cloud,” there are many different
variations available. Most vendors offer a hosted version of their software. The software
is licensed by the insurer and is hosted by the vendor either in their own data center, in a
private data center like Rackspace, or in a public data center like Amazon or Microsoft.
Look for the level of managed services available if you are interested in this option.

SUITE CAPABILITIES

Chapter: Policy Administration Systems: Definition and Functionality


Celent has limited the definition of a PAS to include a set of core processes and key
supporting capabilities. However, vendors do not necessarily limit their definitions of a
PAS in the same way, and many have attempted to build out some or all of the end-to-
end components that an insurer might need. Some insurers are just looking for a best-of-
breed PAS to work with other core systems already installed, but other insurers may be
looking for a vendor who can offer broad solutions for multiple areas of their insurance
operations.

Some of the additional end-to-end components defined here are also listed as core
processes of the PAS. This is not a contradiction. A vendor might bundle a component
with their PAS (for example, a billing system), but also consider it (and also sell it as) a
separate, stand-alone product. Alternatively, a vendor might provide a basic level of
functionality in one area, but also have an upgraded, higher cost product or an ISV
partnership with a different vendor to provide an advanced solution (e.g., rating).

In order to help insurers with their comparison of different solutions, each profile in this
report has a table summarizing whether the vendor in question offers one or more of the
following end-to-end components and whether the components are part of the base
offering or sold as a stand-alone system.

Billing. A system to create invoices and handle collections from producers and
policyholders. It typically handles basic commission processing as well.

Claims management. A system to record and transact all matters relating to a claim
from first notice of loss through final settlement.
14
Reinsurance Management. A system to record any reinsurance contract related to a
policy or set of policies, and a claim or set of claims. The solution typically will calculate
the bordereaux, manage inurements, calculate claims reimbursements, and manage the
financial and reporting interactions with reinsurers and brokers including commissions.

Customer relationship management. Allows the aggregation of data on a customer or


at an account-level view and provides utilities that streamline the communication and
management of customer data. Typically includes lead management and campaign
management in addition to tracking the demographics of the customer.

Rating Engine: A stand-alone rating engine should be capable of handling complex


pricing algorithms and should integrate easily with multiple policy administration systems.
They typically include more robust rate analysis tools and can usually operate on a
headless basis if required.

Distribution management. A system that manages the compliance aspects of agency


management including onboarding of agents and tracking the licenses and appointments
as well as complex compensation transactions across multiple policy administration
solutions including incentive compensation.

Business Intelligence and reporting. Designing, storing, and accessing reports ranging
from simple lists to multidimensional calculated variables. In general, reports are used to
monitor activities by a user and by all levels of management. Tools generally allow
standard reports with scheduling tools and ad hoc reporting.

Chapter: Policy Administration Systems: Definition and Functionality

15
REPORT METHOD

CRITERIA FOR INCLUSION


Celent actively reviews vendor systems in the insurance software market. Some solutions
qualified for profiles that include customer references and a Celent opinion of the
solution. These solutions are also ranked in the ABCD Vendor View.

Celent’s ABCD Vendor View analysis is used to highlight vendors that have attained
success selling their systems in the EMEA market. In general, in order to have a full
profile and be included in the ABCD Vendor View grids, a policy administration solution
had to have:

• At least one new sale to one new customer within the last 24 months for a region.
• At least three live customers per region, at least one of which must be an insurer.
• Participation by at least three reference customers.

There are 18 solutions that meet these criteria and are included in this report with ABCD
profiles.

Even if a vendor is not included in the ABCD Vendor View, Celent provides a system
profile of many other solutions. Solutions that did not qualify to be ranked in the ABCD
Vendor View do not include a customer reference or a Celent opinion. There are 18
solutions that meet these criteria and are included in this report but are not included in
the ABCD Vendor View grids.

EVALUATION PROCESS
Celent sent a detailed request for information to a broad set of policy administration
system vendors. Not all vendors chose to participate. After completing the RFIs, each
eligible vendor provided a briefing and demo for Celent concentrating on usability and
functionality for everyday users, as well as configurability for IT and system
administration users.

Celent also asked the references provided by each vendor to complete a survey and/or to
be interviewed to obtain their view of the system’s business and technology value.

The RFIs and the reference surveys and interviews provided quantitative and qualitative
data, much of which is included in this report. Vendors had an opportunity to review their
profiles for factual accuracy and to provide their own perspectives, but were not permitted
to influence the evaluation. Some of the vendors profiled in this report are Celent clients,
and some are not. No preference was given to Celent clients for either inclusion in the
report or in the subsequent evaluations.

The data collection activities occurred on the second half of 2017 including the reference
surveys.
Chapter: Report Method

A detailed list of vendors profiled in this report is shown in Table 1.

16
What are the solutions in the EMEA marketplace by line of
business?
Key
Research
Question

2 This report indicates the lines of business for 38


policy administration solutions.

Vendors with full profiles are ranked in the ABCD Vendor Views. Table 1 details the
vendors, which lines of business are in production at one or more P&C EMEA insurers,
and the type of profile in the report.

Table 1: Profiled Vendors, in Alphabetical Order

Personal Commercial Workers Specialty


Vendor Product Lines Lines comp Lines ABCD

3i Infotech Ltd PREMIA     No


General
Insurance
Suite

Adacta Group AdInsure     Yes

Adcubum AG adcubum    Yes


SYRIUS

adesso in|sure     No
insurance General
solutions
GmbH

AETINS SDN Insurance     No


BHD Solution
Framework
(ISF)

Beyontec Beyontec Suite     Yes


Solutions, Inc.

Cálculo S.A. e-tica     No

CCS Roundcube     Yes


Policy

Duck Creek Duck Creek     Yes


Technologies Policy

   
Chapter: Report Method

DXC GraphTalk No
Technology A.I.A

DXC Xuber for     No


Technology Insurers

ESKADENIA ESKA®     Yes


Software Insures -
General
Insurance

17
Personal Commercial Workers Specialty
Vendor Product Lines Lines comp Lines ABCD

Fadata INSIS     Yes

Faktor Zehn Faktor-IPM     Yes


AG

Guidewire Guidewire     Yes


Software Inc. PolicyCenter®

i2S Informática I2S NON-LIFE     Yes


– Sistemas E
Serviços S.A.

Insurance IBSuite     No
Business
Applications
(IBA)

ICE ICE Policy     No


InsureTech

Insicon AB Insicon i2i     Yes

Javision Ltd. Inamon     No

Keylane QIS Policy     Yes


Management

Majesco Ltd. Majesco Policy     No


for P&C

Markit Markit - DA     Yes


Systems (Delegated
Limited Authority)

msg systems msg.PIA     No


ag (msg (Primary
group) Insurance
Application)

NIIT Insurance Advantage     No


Technologies Suite
Limited Navigator

Oceanwide Bridge     No
Canada, Inc. Insurance
Software Suite

Prima Prima Insure     No


Solutions

RDT Ltd Landscape     No

RGI S.p.A. PASS_Insuran     Yes


ce 3.0
Chapter: Report Method

SAP SE SAP Policy     No


Management

SAPIENS IDIT     Yes

Sequel Eclipse     No
Business Underwriting
Solutions

18
Personal Commercial Workers Specialty
Vendor Product Lines Lines comp Lines ABCD

SSP Limited SSP Pure     No


Insurance

SSP Limited SSP Select     No


Insurance

Tata TCS BaNCS     No


Consultancy for Insurance
Services

TIA The TIA     Yes


Technology Solution

Total Systems Bluescape     Yes


PLC

Zov Solutions SID     Yes


OOD

Source: Celent; Key: =in production in EMEA.


Note: Specialty lines include medical and professional liability, surety and fidelity, excess policies, and others
(pet, boat, travel, etc.).

It should be noted that although a particular system is shown as implemented in only one
major line, it still may be capable of supporting both commercial and personal business.
For example, an insurer looking for a personal lines solution may wish to contact a
particular commercial lines vendor because of that vendor’s technology or delivery
capabilities.

Given the significant differences between Europe, Africa and the Middle East below we
describe which systems have implementations in the different territories. Once again,
absence from a territory does not mean that it cannot operate there.

Table 2: Profiled Vendors by region, in Alphabetical Order

Vendor Product Europe Africa Middle East

3i Infotech Ltd PREMIA General   


Insurance Suite

Adacta Group AdInsure  

Adcubum AG adcubum SYRIUS  

adesso insurance in|sure General  


solutions GmbH

AETINS SDN Insurance Solution   


BHD Framework (ISF)
Chapter: Report Method

Beyontec Beyontec Suite   


Solutions, Inc.

Cálculo S.A. e-tica   

CCS Roundcube Policy   

Duck Creek Duck Creek Policy   


Technologies

19
Vendor Product Europe Africa Middle East

DXC Technology GraphTalk A.I.A   

DXC Technology Xuber for Insurers   

ESKADENIA ESKA® Insures -   


Software General Insurance

Fadata INSIS   

Faktor Zehn AG Faktor-IPM   

Guidewire Guidewire   
Software Inc. PolicyCenter®

i2S Informática – I2S NON-LIFE   


Sistemas E
Serviços S.A.

Insurance IBSuite   
Business
Applications (IBA)

ICE InsureTech ICE Policy   

Insicon AB Insicon i2i   

Javision Ltd. Inamon   

Keylane QIS Policy   


Management

Majesco Ltd. Majesco Policy for   


P&C

Markit Systems Markit - DA   


Limited (Delegated
Authority)

msg systems ag msg.PIA (Primary   


(msg group) Insurance
Application)

NIIT Insurance Advantage Suite   


Technologies Navigator
Limited

Oceanwide Bridge Insurance   


Canada, Inc. Software Suite

Prima Solutions Prima Insure   

RDT Ltd Landscape   

RGI S.p.A. PASS_Insurance   


Chapter: Report Method

3.0

SAP SE SAP Policy   


Management

SAPIENS IDIT   

Sequel Business Eclipse   


Solutions Underwriting

20
Vendor Product Europe Africa Middle East

SSP Limited SSP Pure   


Insurance

SSP Limited SSP Select   


Insurance

Tata Consultancy TCS BaNCS for   


Services Insurance

TIA Technology The TIA Solution   

Total Systems Bluescape   


PLC

Zov Solutions SID   


OOD

Source: Celent

Chapter: Report Method

21
CELENT’S ABCD VENDOR VIEW

Celent has developed a framework for evaluating vendors. This is a standard


representation of a vendor marketplace designed to show at a glance the relative
positions of each vendor in four categories: Advanced and agile technology, Breadth of
functionality, Customer base (i.e., relative number of customers), and Depth of client
services. The Celent Vendor View shows relative positions of each solution evaluated
and does not reflect an abstract evaluation. Each vendor solution is judged relative to the
others in the group.

While this is a standard tool that Celent uses across vendor reports in many different
areas, each report will define each category slightly differently. For this report, some of
the factors used to evaluate each vendor are listed in Table 3. Celent’s view of the
relative importance of each factor, and of the solution and vendor’s capabilities also
contributes to the final rating.

Table 3: Examples of Possible Factors Used in Celent Policy Administration System ABCD

ABCD CATEGORIES POSSIBLE FACTORS

ADVANCED TECHNOLOGY (AND Platform and Modernity (Code base, platform, databases, localization
FLEXIBLE TECHNOLOGY) capabilities, etc.)

UI (Ease of use, mobility)

Data and adaptability/extendibility (Openness of application, code


base, data model, etc.)

Integration (Web services, APIs, reference comments)

Scalability and cloud (Cloud readiness, largest installations, etc.)

Ease of change (Change tooling, debugging capabilities, etc.)

BREADTH OF FUNCTIONALITY Functions and features provided in base offering

In production lines of business and number of deployments for each

User experience

CUSTOMER BASE Number of live insurers using the system for personal, commercial, or
specialty lines of business

New client momentum

Size of professional services and support team in region


Chapter: Celent’s ABCD Vendor View

DEPTH OF CUSTOMER SERVICE Insurers’ post-implementation experiences

Source: Celent

THE XCELENT AWARDS


Within this framework, the top performers in each of the ABCD dimensions receive a
corresponding XCelent Award:

• XCelent Technology for the leading Advanced Technology score


• XCelent Functionality for the leading Breadth of Functionality score
• XCelent Customer Base for the leading Customer Base score
• XCelent Service for the leading Depth of Service score

22
Which systems win Celent’s 2018 North American Property &
Casualty/General/Specialty lines PAS ABCD Awards?
Key
Research XCelent Technology: Sapiens IDIT
Question
XCelent Functionality: Guidewire PolicyCenter

3 XCelent Customer Base: Fadata and RGI


XCelent Service: Adcubum and Guidewire
PolicyCenter
XCELENT TECHNOLOGY AND XCELENT FUNCTIONALITY
Firstly, it is worth pointing out that all the ABCD qualifying solutions in this report were
exceptional. All scored highly in our assessment as shown in Figure 6.

Figure 6: All the Solutions Scored Impressively in Technology and Functionality


Advanced Technology

Breadth of Functionality
Chapter: Celent’s ABCD Vendor View

Source: Celent

23
Figure 7 zooms in on the top right and positions each vendor along two dimensions: the
vertical axis displaying the relative rankings for Advanced Technology and the horizontal
axis showing relative Breadth of Functionality rankings. The XCelent Advanced
Technology winner is Sapiens. The XCelent Breadth of Functionality award goes to
Guidewire PolicyCenter.

Figure 7: XCelent Technology and XCelent Functionality

Keylane
Sapiens IDIT
Faktor Zehn Guidewire
Duck Creek Beyontec PolicyCenter
Adacta
Fadata
Advanced Technology

Total Systems RGI

Zov Solutions
Insicon AB
CCS
Markit Systems i2S
TIA
Adcubum
ESKADENIA

Breadth of Functionality

Source: Celent

Chapter: Celent’s ABCD Vendor View

24
XCELENT CUSTOMER BASE AND XCELENT SERVICE
As above, it is worth pointing out the vendors this year all scored well in our assessments
as shown in Figure 8.

Figure 8: All the Solutions Scored Impressively in Customer Base and Service
Depth of Customer Services

Customer Base

Source: Celent

Chapter: Celent’s ABCD Vendor View

25
Figure 9 positions each vendor along two dimensions: the vertical axis displaying the
relative level of depth of customer service and the horizontal axis displaying the relative
customer base. The XCelent Customer Base award is given to RGI for their customer
density in Southern Europe and to Fadata for their reach. The XCelent Depth of Service
award goes to Adcubum in part for their great customer feedback and to Guidewire
PolicyCenter for their extensive partner network and professional services capability.

Figure 9: Customer Base and Depth of Customer Service

Adcubum
Guidewire
PolicyCenter Adacta
Faktor Zehn
Keylane
Depth of Customer Services

Total Systems
Zov Solutions

RGI
Beyontec
ESKADENIA
Duck Creek Sapiens IDIT
Fadata
CCS i2S
TIA

Insicon AB Markit Systems

Customer Base

Source: Celent

Celent advises insurers to take into account past vendor results, but not to compare the
placement of vendors in the charts from prior years, because not only is the market
changing, but so has our analysis. The criteria used to determine the A, B, C, and D
rankings in this report are broadly similar, but not identical, to the criteria used in the
previous Celent PAS vendor report published in 2016. For example, in this report, we are
considering new criteria in Advanced Technology related to testing and speed of change
approaches. The market is also evolving due to acquisitions and partnerships, solutions
development, and alternative delivery models.
Chapter: Celent’s ABCD Vendor View

We suggest that insurers consider their specific needs and each vendor for what it offers.
Although they are very successful in one or more of the criteria, the XCelent Award
winners may or may not be the best match for an insurer’s specific business goals and
solution requirements.

26
VENDOR PROFILES

ABOUT THE PROFILES


Each of the profiles presents information about the vendor and solution; professional
services and support capabilities; customer base; functionality and lines of business
deployed; technology and partnerships; and implementations and cost. As stated earlier,
if a system was included in the ABCD Vendor View analysis the profile also includes
customer feedback and Celent’s opinion of the system in regards to usability, product
configuration, and workflow abilities as well as summary comments.

Each profile includes figure outlining available end-to-end components and the
features/functions availability within the systems. The profiles also include a list of in
production and supported lines of business and the number of clients currently using the
system for those products. Additionally, the profiles include a table of technology options.

If included in the ABCD Vendor View analysis, the vendor’s reference feedback gathered
through the use of an online survey is presented in the profile. Customer feedback
sections include a diagram that displays the average ratings given to the vendor in five
categories. Each average rating includes up to eight underlying ratings shown in Table 4
scored by the customer on a scale of 1 to 5, where 1 means poor and 5 is excellent.
Open-ended comments regarding the system and the vendor are also included in the
feedback section.

Table 4: Customer Feedback Ratings

DIAGRAM AVERAGE
(QUESTION ASKED) RATINGS INCLUDED IN AVERAGE*

FUNCTIONALITY Producer/Agent Portal


Policyholder Portal
(How would you rate the features and Customer Service Desktop
functions you are currently using?) Underwriter Desktop/Underwriting and Case Management
Product Configuration/Definition and Maintenance
Workflow / Business Process Design
Business Rules
Document Management
Business Intelligence
Analytics
Billing
Claims Management
Commission Management
Reinsurance Management
Regulatory Reporting

USER EXPERIENCE Underwriters


Underwriter support staff
(Do the following users find this system Policy service staff
easy and efficient to use? Using a 1 to System administrators
5 scale, where 1 is very difficult to use Business Analysts (doing configuration)
Chapter: Vendor Profiles

and 5 is very easy to use.)

27
TECHNOLOGY Ease of system maintenance
Flexibility of data model
(How would you rate the technology of Scalability
this solution on a scale of 1 to 5, where Continuous improvements in technical performance
1 means very poor and 5 means Configurability
excellent?) Ease of integration with internal and external data/systems

IMPLEMENTATION Responsiveness
Project management
(If you are familiar with the original Implementation completed on time
implementation of this system at your Implementation completed on budget
company, how would you rate this Overall project success
vendor in the following areas?) Knowledge of your business

SUPPORT Skill and knowledge of professional services staff


Timeliness of responses to service requests
(After implementation, how would you Quality of response to service requests
rate the vendor's professional services Cost of services
staff in the following areas?) Overall value of professional services

Source: Celent
*Scale 1 to 5, where 1 is poor and 5 is excellent. Not Applicable or No Opinion not included in average.

Concerning implementation costs and fees, Celent asked vendors to provide first-year
license and first-year other implementation costs (work by the insurer, vendor, or third
parties) for two hypothetical insurance companies:

• Insurance Company A, a regional insurance company that writes in the United


Kingdom for 8 lines of business, producing an annual GWP of €250 million.
• Insurance Holding Company B, a European insurance holding company, which has
four companies, writes in five countries (France, Germany, Italy, Spain, UK), across
24 lines of business and has GWP of €2.5 billion.

When discussing insurance customers of the various solutions, the profiles may use the
terms very small, small, medium, large, and very large insurers. Very small insurers (Tier
5) have under US$100 million in annual premium; small (Tier 4) have US$100 million to
$499 million; medium (Tier 3) have US$500 million to $999 million; large (Tier 2) have
US$1 billion to $4.9 billion; and very large (Tier 1) have US$5 billion or more.

Chapter: Vendor Profiles

28
3I INFOTECH LTD: PREMIA GENERAL INSURANCE SUITE

COMPANY
3i Infotech Ltd is a publicly traded company headquartered in Mumbai with sales and
professional services personnel located throughout the North American, European,
Middle Eastern, and African, and Asia-Pacific regions. 3i Infotech Ltd’s business is
providing software and services to the insurance and BFSI industries. The company has
over 4,500+ employees of which over 4,500+ are available to provide professional
services / client support for their PAS solution; 110 are physically located in Europe,
Middle East, Africa, and Asia-Pacific.

3i Infotech conducts annual events across the globe for its customers and industry
leaders, under the banner PREMIA CONCLAVE. Events were recently conducted in
Ghana, Ethiopia, Zimbabwe, and Dubai.

Table 5: Company and Product Snapshot

COMPANY Annual corporate revenues US$200 million+

Year founded 1993

Exchanges/Symbols 3IINFOTECH Traded both in NSE and BSE

Headquarters Location Global: Mumbai

PAS SYSTEM Name PREMIA General Insurance Suite

Current release and date of PREMIA 11 – 2013


release

Release intervals Minor enhancements: Every 6 months


Major enhancements: Every 4 to 5 Years

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0)

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite


Vendor support for prior versions: They support
all versions.

Target market Middle East and Africa


In 2018 – US

Source: Vendor RFI

29
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is configurable using tools targeted for IT users; data services, which is available
with integration to a third party solution; rate analysis, which is configurable through a
scripting language; multiple insurers, which is configurable using tools for a business
user; forms management, which is configurable using tools for an IT user; and
multichannel/mobile, which is available with integration to a separate module.

Figure 10: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite


module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

30
CUSTOMER BASE
3i Infoteech state they have a total of 110 insurer clients.

Table 6: Customer Base

EUROPE, MIDDLE EAST AND New clients since 2015 Middle East:
AFRICAN CUSTOMER BASE United Arab Emirates 3
Oman 1
Africa:
Kenya 2
Tanzania 2
Eriteria 1
Ghana 1
Malawi 1
Mauritias 1
Swaziland 1
Uganda 1
Zimbabwe 1

Existing client base by Europe: Not supported Applicable


country Middle East:
Total 40
Including:
Oman 2
Kingdom of Saudi Arabia 1
United Arab Emirates 3
Africa:
Total 51
Including:
Kenya 2
Tanzania 2
South Africa 1
Ethiopia 1
Eritrea 1
Malawi 1
Swaziland 1
Uganda 1

Deployment method On Premise: 80%


(percentage of client base)
Hosted: 20%

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite


Percentage of clients using 0%
PAS through BPO services

Marquee clients Not Applicable

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 7: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 91 Clients

HOMEOWNERS In production today 91 Clients

COMMERCIAL AUTO In production today 91 Clients

COMMERCIAL PROPERTY In production today 91 Clients

31
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

COMMERCIAL LIABILITY In production today 91 Clients

WORKERS COMP In production today 91 Clients

BUSINESS OWNERS POLICY In production today 91 Clients

Source: Vendor RFI

TECHNOLOGY
The technical architecture has end-to-end business process from underwriting till claim
and also integrated with reinsurance and finance. Premia 11 system is deployed on a 3
tier architecture using Oracle Forms report, and Database and can be accessed from
anywhere via the web.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, Windows, and Blackberry.

Table 8: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 15%
Other (Oracle Plsql, Forms,Reports,Java APIs): 85%
Business users:
Java: 15%
Other (Oracle Plsql, Forms,Reports,Java APIs): 85%
Developers:
Java: 15%
Other (Oracle Plsql, Forms,Reports,Java APIs): 85%

OPERATING SYSTEMS Operating systems deployed on: Windows


Planned change to code base: From D2K to Java by
2018

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite


APPLICATION SERVERS No

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; Custom API
Public API integrations: Google Maps is integrated

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: Yes
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

32
TECHNOLOGY SPECIFICS

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 6,600 users and 35,000 policies

Source: Vendor RFI

The data model is a proprietary database. It supports all modules in Oracle. For the
insurer to make changes to the data model, a set of tools is provided that allow technical
staff to extend the data model and the SQL database schema. The data model can be
released to an insurer. It can be published to an insurer’s data model and mapped to an
intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and role-based security integration. Interface definition
and data definition are configurable using tools targeted for an IT user. Changes to the
system are possible by copying and pasting between products.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is required for change to underlying data
model, new web service, or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 30 to 40 people consists of resources from the insurer (20%) and 3i
Infotech Ltd (80%). Service-level agreements are offered; a typical SLA is provided in
their AMC contracts measured on criticality of issues.

The average time to get the first line of insurance live in a single jurisdiction is typically 1
to 3 months depending on the integration requirements and the level of configuration

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite


required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

3i Infotech Ltd offers term license, perpetual license, usage-based, SaaS, and
subscription pricing options. The license fees are typically based on number of functional
components/modules, number of total or named users, number of states or geographies,
enterprise license / flat fee, and other. The vendor will offer a fixed price implementation
on pre-defined scope and functionality. Carriers may also need to license the following
third party software: Oracle DB and Forms Licenses required.

33
The total cost to implement PREMIA General Insurance Suite can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Table 9: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs Under €500,000 Under €500,000 Under €500,000 22%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 22%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four-year €1 million to €5 million €1 million to €5 million No cost, not 22%


implementation applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A No cost, not No cost, not 22%


implementation for a applicable applicable
European insurance
holding company

Source: Vendor

Chapter: 3i Infotech Ltd: PREMIA General Insurance Suite

34
ADACTA GROUP: ADINSURE

COMPANY
Adacta is a privately owned company headquartered in Ljubljana, Slovenia with sales
and professional services personnel located throughout the European, Middle Eastern
and African region. Adacta’s business is providing software and services to the
insurance, financial services and most other vertical industries. The company has 465
employees, of which 120 are available to provide professional services / client support for
their PAS solution; 120 are physically located in Europe, Middle East, and Africa.

Table 10: Company and Product Snapshot

COMPANY Annual corporate revenues €25m

Year founded 1989

Exchanges/Symbols N/A

Headquarters Location Global: Ljubljana, Slovenia

PAS SYSTEM Name AdInsure

Current release and date of 6.0 December, 2016


release

Release intervals Minor enhancements: Quarterly


Major enhancements: Yearly

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market Insurers in EMEA

Source: Vendor RFI

CELENT OPINION
Adacta offers a strong, modern policy administration system in AdInsure, which once
again received exceptional feedback from Adacta’s clients this year, consistent with the
year before. AdInsure is installed in Eastern Europe.

Celent is pleased to see Adacta’s plans to invest in the solution and welcomes the
addition of a web based interface as well as RESTful-based API approach.
Chapter: Adacta Group: AdInsure

AdInsure’s primary interface is a Microsoft Windows client. This offers a modern interface
borrowing from web style interfaces as well as thick client paradigms. There are menus,
tabs, and icons, as well as clickable text that looks like links. Configuration is done in this
rich interface with simple tasks using property lists and scripts available for some
business rules tasks. AdInsure also offers modern portals, and Adacta was able to
demonstrate mobile App support too.

Adacta has grown in the region since they were last covered in the report. There are
fewer wins this year, however; Adacta appears to be appealing to larger clients, and the
growth over the period is strong. Celent predicts a continuing trend of growth for Adacta.

35
OVERALL FUNCTIONALITY
A moderate amount of functionality is available out of the box. Exceptions include
ACORD, which requires coding; data services, which are available with integration to a
separate module; data upload, which is configurable through a scripting language;
endorsement, which is not available; ISO, which requires coding; reinsurance, which
requires coding; and forms management, which is configurable through a scripting
language.

Figure 11: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
Chapter: Adacta Group: AdInsure

They have a total of 11 insurer clients. The breakdown of the clients is as follows: Tier 3
(2 clients), Tier 4 (one client), and Tier 5 (8 clients).

Table 11: Customer Base

EUROPE, MIDDLE EAST AND In production with current 11


AFRICAN CUSTOMER BASE release or any release less
than four years old

New clients since 2015 Europe:


Russia 2
Romania 1

36
Existing client base by Europe:
country Russia 3
Slovenia 2
Serbia 1
Macedonia 1
Czech Republic 1
Bosnia and Herzegovina 1
Croatia 1
Romania 1

Deployment method 100% on premise


(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Marquee clients Triglav Insurance Slovenia,


VTB Insurance Russia,
Generali Romania

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on AdInsure. One is a Tier 5 insurer. two are Tier 3
insurers, and one is a Tier 2 insurer. Two references have been using the system for 1 to
3 years, one client for less than one year, and one client for more than three years. All
references use the system in EMEA. All references use the system for a mix of personal
and commercial lines. One reference uses the solution for workers’ compensation line of
business.

In terms of the best things about the vendor, clients noted that Adacta as a company
understands insurance well, reflected in the team’s experience and the responsiveness of
the team. Regarding the solution, references noted the flexibility and speed of product
development.

In terms of areas for improvement, one reference would like to see a SaaS model
offered, and more than one are keen for the new user interface refresh to be released to
them. Clients mentioned wanting more configurability around business processes and
reports — although note that even with the current system references were pleased with
the time to market on changes.

Chapter: Adacta Group: AdInsure

37
Functionality received above average scores overall, and within functionality portals for
policyholders and prospects received the highest score. Configurability scores were
above average, and within configurability data elements/entities (creation and
maintenance) received the highest score. Comments on the integration were above
average, and within integration your claim system(s) received the highest score.
Regarding their technology experiences, insurers gave above average marks, and within
technology vendor's level of investment in improving technical performance through new
releases and fixes received the highest score. The implementation was rated above
average overall, and within implementation knowledge of your business received the
highest score. Finally, Support received above average scores, and within support
knowledge of your business received the highest score.

Figure 12: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 4.57

Support Configurability
4.46
4.67

Implementation Integration
4.54 4.48

Technology 4.53

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 12: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today


Chapter: Adacta Group: AdInsure

HOMEOWNERS In production today

COMMERCIAL AUTO In production today

COMMERCIAL PROPERTY In production today

COMMERCIAL LIABILITY In production today

WORKERS COMP In production today

BUSINESSOWNERS POLICY In production today

Source: Vendor RFI

38
TECHNOLOGY
The technical architecture is a three-tier .NET architecture, web & windows presentation
layer, IIS -hosted web services for business layer, Oracle/SQL Server for database layer.
They use Identity Server (or other OpenId compatible module) for authentication. They
use ElasticSearch for full-text search.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, and Windows.

Table 13: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


.NET (C#): 100%
Business users:
.NET (C#): 100%
Developers:
.NET (C#): 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Oracle; Microsoft SQL Server


Additional options: DB2/UDB

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format (only option)
Additional options: ACORD Standard XML; Other
XML; MQSeries, JMS or similar queue technology;
Flat files; Custom API
Public API integrations:

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: No
Main UI thick client based: Yes
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Chapter: Adacta Group: AdInsure

Developer API portal: No


Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 3,000 users and 14 million


policies

Source: Vendor RFI

The data model is proprietary. It supports EUROTAX and AUDATEX. The data model
can be extended by carriers using an attribute-based data model. Physical changes to
the PDM are rarely required (i.e., fields to existing entities are added as attributes through
configuration). Core tables should not be modified by the client. They have separate
model namespaces for country/client specific functionality. Modification of data model, if
39
necessary, is done using tools. For the insurer to make changes to the data model, a set
of tools is provided that allow technical staff to extend the data model and the SQL
database schema. The data model is willing to be released to an insurer.

Carriers have access to core code; configuration tools targeted to a business user are
available for the following: insurance product definition, workflow definition, and business
rule definition. Screen definition, interface definition, data definition and role-based
security integration are configurable using tools targeted for an IT user. Changes to the
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules,
and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with National systems of
Slovenia, Croatia, Serbia, Russia for address verification; QlikView for business
intelligence systems; Dynamics NAV, Dynamics AX, and 1C (CIS region) for general
ledger and Microsoft Dynamics CRM for CRM.

Product changes can be analyzed using the configuration and development user
interface and can be tested using a specific tool provided. A restart of the system is not
required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 5 to 10 people consists of resources from the insurer (20%), Adacta
(60%), and external professional services firms (20%). Service-level agreements are
offered.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Adacta offers term license, perpetual license, usage-based, risk-based, linking fees to
process efficiency, cost reduction, business growth, number of claims, and the number of
policies pricing options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license / flat fee, per
transaction, and a case by case approach. The vendor will offer a fixed price
implementation after taking into account the following circumstances: maturity of
business processes in the company, uncertainty about scope and data migration risks.
Carriers may also need to license the following third party software: DBMS is licensed
separately. Chapter: Adacta Group: AdInsure

40
The total cost to implement AdInsure can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 14: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million Under €500,000 15%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for 8 lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 15%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €3 million €1 million to €3 million Under €500,000 15%
implementation
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post No cost, not No cost, not No cost, not 15%
implementation for a applicable applicable applicable
European insurance
holding company

Source: Vendor

Chapter: Adacta Group: AdInsure

41
ADCUBUM AG: ADCUBUM SYRIUS

COMPANY
Adcubum is a privately owned company (with outside investors) headquartered in St.
Gallen, Switzerland with sales and professional services personnel located in Switzerland
and Germany. Adcubum’s business is providing software and services to the insurance
industry. The company has 310 employees, of which 70 are available to provide
professional services / client support for their PAS solution.

The last user conference was the “Adcubum Innoday,” which took place on January 17,
2018. Main topics were information on the latest Major Release 3.08 and the innovation
pipeline. Every year Adcubum holds three Adcubum Innoday conferences for clients and
integration partners from Switzerland and Germany.

On top of that, there are regular meetings within the Insurance User Group (IUG) to share
views between Adcubum and its clients and partners on specific topics.
In addition, once a year Adcubum invites C-Level representatives of the customers to the
Adcubum Executive Circle (AEC) to discuss the further strategic development of the
solution.

Table 15: Company and Product Snapshot

COMPANY Annual corporate revenues 68.6 million CHF (2017 Results)

Year founded 1997

Exchanges/Symbols N/A

Headquarters Location Global: St. Gallen, Switzerland

PAS SYSTEM Name adcubum SYRIUS®

Current release and date of 3.08 / January 2018


release

Release intervals Minor enhancements: Quarterly


Major enhancements: Annually
Front components: Monthly Chapter: Adcubum AG: adcubum SYRIUS
Upgrades They support all versions
Vendor support for prior versions: They can skip
multiple versions (e.g., go directly from version
3.5 to version 3.7),

Target market Switzerland, Germany, Austria (mid to large size


insurers)

Source: Vendor RFI

CELENT OPINION
Adcubum SYRIUS is clearly a popular software vendor in Switzerland and Germany.
Adcubum received strong references from their customers. The solution supports health,
accident, property and casualty lines of business, although workers compensation lines
are the most widely deployed in P&C (see below).

42
SYRIUS offers two user interfaces, each intended for different groups of users. Both
interfaces look clear and modern. The web-based interface offers an easy to use
interface for data entry with a number of common workflow cues used throughout the
interface to aid the user. The web interface includes dashboard views, and offers a useful
card view of alternative quotes for comparison in one screen.

The local client interface is equally light and clearly takes some cues from modern web
interfaces, although it makes good use of menus and other common visual cues and user
interface features. This interface is clearly intended for more of a power user interface
with a good balance of work area, data display, context, and navigation around the data
in the system.

Given the activity in the countries where Adcubum is active and the clearly referenceable
clients, Celent predicts growth for the vendor and looks forward to following them in the
next report.

Chapter: Adcubum AG: adcubum SYRIUS

43
OVERALL FUNCTIONALITY
Much of the functionality is available out of the box as shown in Figure 13. Some
functionality is configurable with tools for a business user including quote, assignment,
rating, multiple insurers, forms management, and scheduling/calendar/diary. Exceptions
include ACORD, which is not applicable; data services, which is configurable using tools
for an IT user; assignment and rating, which are configurable using tools for a business
user; assumed reinsurance, which is not on the roadmap; document creation, which is
available with integration to a third party solution.

Figure 13: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable Chapter: Adcubum AG: adcubum SYRIUS
Source: Vendor RFI

CUSTOMER BASE
They have a total of 8 insurer clients. The breakdown of the clients is as follows: Tier 2
(four clients), Tier 4 (two clients), and Tier 5 (two clients).

Table 16: Customer Base

EUROPE, MIDDLE EAST AND In production with current 8


AFRICAN CUSTOMER BASE release or any release less
than four years old

New clients since 2015 Europe:


Germany 2

44
Existing client base by Europe:
country Switzerland 7
Germany 1

Deployment method On Premise: 50%


(percentage of client base) Hosted: 50%

Percentage of clients using 0%


PAS through BPO services

Marquee clients SUVA


SWICA
Württembergische Versicherung

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Adcubum SYRIUS. One is a Tier 5 insurer. Two are
Tier 2 insurers. One reference is still implementing the solution, one has been using the
solution for 1 to 3 years, and the last has been using the solution for over 3 years. One
reference is using the solution for a mix of personal and commercial lines, while the other
two are using the solution for all or mostly commercial lines.

In terms of the best things about the vendor references noted the deep knowledge of the
Swiss market, good strategy, responsiveness, professionalism, and reliability of the
vendor. In terms of the solution references noted it was innovative, was flexible, easy to
configure, and cited the speed of implementation.

In terms of areas for improvement it seems the references are keen for items already on
the roadmap or subjects of R&D — notably improved integration with business process
management systems and a story on AI and cloud. Some references would prefer an
alternative to the Oracle technology stack.

Chapter: Adcubum AG: adcubum SYRIUS

45
Functionality received above average scores overall, and within functionality policy
service processing received the highest score. Configurability scores were above
average, and within configurability products (design and maintenance) received the
highest score. Comments on the integration were above average, and within integration
your financial system(s) received the highest score. Regarding their technology
experiences, insurers gave above average marks, and within technology flexibility of the
data model received the highest score. The implementation was rated above average
overall, and within implementation responsiveness (handling of issue resolution) received
the highest score. Finally, support received above average scores, and within support
responsiveness (handling of issue resolution) received the highest score.

Figure 14: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 4.20

Support Configurability
4.93 4.42

Implementation Integration

4.86 4.50

Technology 4.89

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 17: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA
Chapter: Adcubum AG: adcubum SYRIUS
PERSONAL AUTO Supported but not in production 0

HOMEOWNERS In production today 1

COMMERCIAL AUTO Supported but not in production 0

COMMERCIAL PROPERTY Supported but not in production 0

COMMERCIAL LIABILITY Supported but not in production 0

WORKERS COMP In production today 7

BUSINESS OWNERS POLICY Supported but not in production 0

Source: Vendor RFI

46
TECHNOLOGY
The technical architecture is built as a modern 4-tier architecture (Database, Application
Server, UTC-Server / Web Server, and UTC - Ultra Thin Client / Web-Client). The UTC
Client and the Web-Client are designed for different groups of users.

Business functions are grouped into functional modules, which work together as a suite.
To integrate other systems and frontends a API Bridge is provided for all respective
business functions. The system can be parametrized to a very high degree (products,
processes, rules, integration). Parametrization information is stored in the database and
is automatically transformed to the next Version (Major, Minor, Patch).

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 18: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%

Front: HTML5 / JavaScript 100%Business users:


Other (Parametrization in SYRIUS) 100%
Developers: Java /JavaScript 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Various LINUX
implementations

APPLICATION SERVERS Oracle Weblogic 12.2.x and JBoss EAP 7

DATABASES Preferred: Oracle (current option – alternatives could


be discussed)
Additional options: Other SQL

INTEGRATION METHODS Preferred: Web Services; MQSeries, JMS or similar


queue technology (only option)Flat files;
Additional options: Other XML; RESTful HTTP style
services; JSON format
Public API integrations: Swisscom Directories for
addresses and Google Maps

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: Yes Chapter: Adcubum AG: adcubum SYRIUS
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 3,500 users and around 2.5


million policies

Source: Vendor RFI

47
The data model is proprietary and derived from various industry standards. It supports
none. The data model can be extended by carriers using tools. For the insurer to make
changes to the data model, they can extend it transparently according to the needs as a
part of parametrization. The data model is willing to be released to an insurer. It can be
published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and data definition. Interface definition and role-based
security integration are configurable using tools targeted for an IT user. Changes to the
system are possible by defining reusable parts that can be linked together.

The system is preintegrated with:

• An inhouse solution for address verification and geocoding.


• Audatex and more for third party data services (e.g., LexisNexis, ISO, etc.).
• IGB2B for agent/broker portal software.
• Centris DWH for business intelligence systems and data warehouse;
• Included solution for data mastery, master data management tools;
• SAP for general ledger.
• An inhouse solution module, Filenet, Camunda and others for business process
management systems.
• An inhouse solution, SAP FS/CD for billing systems.
• Filenet, Dok1, standard interface to others for document management systems.
• Mtext, Papyrus and others for document creation systems.
• An inhouse solution (Eclaim Plus) for medical and property bill review;.
• An inhouse solution, part of billing system (DE, CH) for payments systems
(disbursements).
• An inhouse solution for new business and underwriting, claims, product calculation
engine, and distribution management.
• An inhouse solution, SAP CRM, Microsoft Dynamics for CRM.
• An inhouse solution for producer portal (quick quote, illustration, bind, issue) and an
inhouse solution for policyholder portal (inquiries and transactions for in-force
policies). A prospective customer portal (quick quote, illustration, bind, issue) is
planned for the future.
• Also integrated to Enforcement: Credinkasso, and ASEM.
Chapter: Adcubum AG: adcubum SYRIUS
Product changes can be tested in a standard way using common tools and they provide a
set of prebuilt tests. A restart of the system is required for the deployment of a new web
service or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 20 people consists of resources from the insurer (50%), Adcubum (20%),
and external professional services organizations (30%).

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking around 1 to 3 months in the same
jurisdiction. Second and subsequent jurisdiction implementations typically take 1 to 3
months.

48
Adcubum offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based options. The license fees are typically based on number of functional
components/modules, premium volume, number of states or geographies, and other
pricing options. Carriers may also need to license the following third party software: DB
System and Application Server.

A typical SLA includes support and maintenance or operations together with a partner.

The total cost to implement Adcubum SYRIUS can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 19: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €500,000 to €1 million €500,000 to €1 20%


only: assuming a two- million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 20%


implementation costs applicable
for the regional
insurance company.

Assuming a four-year Over €25 million €15 million to €25 €15 million to €25 20%
implementation million million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €1 million to €5 million €500,000 to €1 20%


implementation for a million
European insurance
holding company
Chapter: Adcubum AG: adcubum SYRIUS
Source: Vendor

49
ADESSO INSURANCE SOLUTIONS GMBH: IN|SURE
GENERAL

COMPANY
ais is a privately owned company headquartered in Dortmund, Nordrhein-Westfalen,
Deutschland with sales and professional services personnel located throughout Germany
in 12 different Locations. ais’s business is providing standard software and services to
the insurance industry with focus on life, health, and P&C insurance. The company
currently has 130 employees located in Germany. The last user conference was the
Partner Congress, User Group in|sure IT-Architecture, User Group in|sure Policy
Administration, and User Group in|sure Claims Administration.

Table 20: Company and Product Snapshot

COMPANY Annual corporate revenues US$2.4 million (US$18.6 million in 2016)

Year founded 2014

Exchanges/Symbols N/A

Headquarters Location Global: Dortmund, Nordrhein-Westfalen,


Deutschland

PAS SYSTEM Name in|sure General

Current release and date of 1.0


release

Release intervals Minor enhancements: 2-3 per year


Major enhancements: 1 major release per year

Upgrades Insurers can skip one version (e.g., go from


version 4.0 to 6.0)
Vendor support for prior versions: They support

Chapter: adesso insurance solutions GmbH: in|sure General


current versions and up to two prior.

Target market Life, Health, and P&C Insurances

Source: Vendor RFI

50
OVERALL FUNCTIONALITY
A moderate amount of functionality is available out of the box. Exceptions include
ACORD, which requires coding; data services, which are configurable using tools for an
IT user; data upload, which is configurable using tools for a business user; assignment
andreinsurance, which require coding; multiple insurers, which is under development;
forms management, document management, document creation,
scheduling/calendar/diary, reporting/analytics, and multichannel/mobile, which are
available with integration to a third party solution.

Figure 15: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Multi
Workflow Channel/Mobile

Chapter: adesso insurance solutions GmbH: in|sure General


Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

51
CUSTOMER BASE
They have a total of 3 insurer clients. The breakdown of the clients is as follows: Tier 2
(one client), Tier 3 (one client), and Tier 5 (one client).

Table 21: Customer Base

EUROPE, MIDDLE EAST, In production with current 3


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


Germany 1

Existing client base by Europe:


country Germany 3

Percentage of clients using 0%


PAS through BPO services

Marquee clients 1

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 22: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1

HOMEOWNERS In production today 1

COMMERCIAL AUTO In production today 1

COMMERCIAL PROPERTY In production today 1

Chapter: adesso insurance solutions GmbH: in|sure General


COMMERCIAL LIABILITY In production today 1

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Supported but not in production

Source: Vendor RFI

TECHNOLOGY
The technical architecture is based on a Java architecture, the architectural platform is
the same as the in|sure PSLife product.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, Windows, and Blackberry.

Table 23: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


Business users: Java: 100%
Developers: Java: 100%

52
TECHNOLOGY SPECIFICS

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: CENT-OS Redhat
Linux / Unix

APPLICATION SERVERS Jboss >= 6.3.4, Wildfly, Weblogic 12

DATABASES Preferred: Oracle; DB2/UDB;


Additional options: Microsoft SQL Server; Sybase;
Other SQL

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format; MQSeries, JMS or similar
queue technology
Additional options: Other XML; Custom API.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 50 users and 250,000 policies

Source: Vendor RFI

Chapter: adesso insurance solutions GmbH: in|sure General


The data model is a proprietary data model. It supports BIPRO and GDV. The data model
can be extended by carriers using tooling and modification of the source code. For the
insurer to make changes to the data model, a number of extension points in the data
model are provided where the customer can store data of their choosing. The number of
slots is limited, and the underlying schema cannot be changed except by changing code.
The data model can be released to an insurer. It can be published to an insurer’s data
model.

Carriers have access to core code; a configuration tool targeted to a business user is
available for insurance product definition. Screen definition, workflow definition, business
rule definition, interface definition, and data definition are configurable using tools
targeted for an IT user. Changes to the system are possible by defining reusable parts
that can be linked together.

In Europe the system is preintegrated with in|sure partner system for address verification;
Camunda for business process management systems; SAP for billing systems; Icon
Dopix for document creation systems; SAP FS-CD for payments systems
(disbursements); in|sure general claims for claims; in|sure partner system for CRM;
in|sure general policy manager for product calculation engine; and in development for
prospective customer portal (quick quote, illustration, bind, issue).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. A restart of

53
the system is required for insurance product modification/configuration, new product
creation, screen configuration, change to underlying data model, new web service or
integration point, change to portal, and business rule change.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 8 people consists of resources from the insurer (30%) and ais (70%).
Service-level agreements are offered; a typical SLA includes support infrastructure is
inhouse available during 8-17h CET. Typical support reaction times are 2 hours;, for
SaaS-Installations they could offer. e.g., 99.9% availability.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

ais offers term license, perpetual license, usage-based, SaaS, subscription, risk-based,
and other pricing options. The license fees are typically based on number of functional
components/modules, number of total or named users, premium volume, number of
states or geographies, enterprise license / flat fee, and per transaction. The vendor will
offer a fixed price implementation after an analysis project with the aim to gain detailed
knowledge of the customers’ products, services, processes, and surrounding
subsystems. They can offer the core system integration for a fixed price. Eventually the
exemption would be made concerning the data migration.

The total cost to implement in|sure General can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 24: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €1 million to €5 million No cost, not 18%


only: assuming a two- applicable

Chapter: adesso insurance solutions GmbH: in|sure General


year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 18%


implementation costs applicable
for the regional
insurance company.

Assuming a four-year €1 million to €5 million €5 million to €10 No cost, not 18%


implementation million applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

54
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A €1 million to €5 million No cost, not 18%


implementation for a applicable
European insurance
holding company

Source: Vendor

Chapter: adesso insurance solutions GmbH: in|sure General

55
ADVANTAGEGO: NAVIGATOR

COMPANY
AdvantageGo is the new trading name of NITL and is a privately owned company (with
outside investors) headquartered in London, United Kingdom with sales and professional
services personnel located throughout the North American, European, Middle Eastern,
and African, Asia-Pacific, and Latin American regions. AdvantageGo’s business is
providing software and services to the insurance industry. The company has 300
employees, of which 280 are available to provide professional services/client support for
their PAS solution; 100 are physically located in Europe, Middle East, and Africa.

The last user conference was user groups, customer advisory groups and market lead
briefings.

Table 25: Company and Product Snapshot

COMPANY Annual corporate revenues USD 23.19 million (FY 2015-16)

Year founded 18th May 1990

Exchanges / Symbols N/A

Headquarters Location Global: London, United Kingdom

PAS SYSTEM Name Navigator

Current release and date of V47 - 31/03/17


release

Release intervals Minor enhancements: Quarterly


Major enhancements: 6 monthly

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g. 4.0 to 5.0).
Vendor support for prior versions: They support
all versions.

Target market Start-ups to established global(re) insurers,


commercial P&C and specialty market insurance

Source: Vendor RFI

Chapter: AdvantageGo: Navigator

56
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include rating,
which is available with integration to a third party solution; ISO, which is on the roadmap;
rate analysis, which is available with integration to a separate module; and document
creation and scheduling/calendar/diary, which are available with integration to a third
party solution.

Figure 16: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow
Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
Chapter: AdvantageGo: Navigator

They have a total of three insurer clients. All clients are Tier 5.

Table 26: Customer Base

EUROPE, MIDDLE EAST AND In production with current 3


AFRICA CUSTOMER BASE release or any release less
than 4 years old

New clients since 2015 Europe:


Ireland 3

Existing client base by Europe:


country United Kingdom 2
Switzerland 1

57
Deployment method (% of On Premise: 33%
client base):
Cloud 66%

% of clients using PAS 0%


through BPO services

Marquee clients Sompo Canopius Zurich,


Sompo Canopius London

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 27: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Supported but not in production

HOMEOWNERS Supported but not in production

COMMERCIAL AUTO Supported but not in production

COMMERCIAL PROPERTY In production today 3

COMMERCIAL LIABILITY In production today 3

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY In production today 3

Source: Vendor RFI

TECHNOLOGY
The technical architecture is Microsoft .Net SOA-based architecture using MS SQL
database, Windows and Web services and Windows .Net client. It is based on Windows
.Net 4.6 WPF, WWF, and WCF models following the ASP.NET MVC pattern.

The UI’s and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 28: Technology Options

TECHNOLOGY SPECIFICS
Chapter: AdvantageGo: Navigator

CODE BASE Core technology:


C: 100%
Business users:
.NET (C#): 100%
Developers:
.NET (C#): 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

58
TECHNOLOGY SPECIFICS

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format ;
MQSeries, JMS or similar queue technology; Flat files;
Public API integrations: N/A

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: No
Main UI thick client based: Yes
Windows interface available: Yes
Apple Mac interface available: No
Linux based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 75 users and 2,000 policies

Source: Vendor RFI

The data model is proprietary. The data model can be extended by carriers using
Insurance Product Manager tool. For the insurer to make changes to the data model, a
set of tools is provided that allow technical staff to extend the data model and the SQL
database schema. The data model is willing be released to an insurer. It can be
published to an insurer's data model.

Carriers do not have access to core code. Insurance product definition, screen definition,
workflow definition, business rule definition, and data definition are configurable using
tools targeted for an IT user. Interface definition requires coding. Changes to the system
are possible through reusable components, inheritance and other schemes. All product
components (including product features, coverages, benefits, transactions, rules and
calculations) are reusable for multiple products.

In Europe, Middle East and Africa the system is pre-integrated with Google and Trillium
for address verification; Sanctions Checking for third party data services (e.g. Northdoor,
World-Check, iso, etc.); a developed portal for agent portal software; Pyramid Analytics
for data discovery, business intelligence and analytics solutions; UNIT4 Financials for
general and technical ledger; MS Workflow Foundation for business process
Chapter: AdvantageGo: Navigator

management systems; ELGAR, XLRAS for reinsurance solutions; UNIT4 Financials for
billing systems; Sharepoint for document management systems; KOFAX for document
creation systems; EXACT for exposure management, ACUMEN for data management,
Google and Trillium for geo coding solutions and UNIT4 Financials for payments systems
(disbursements).

Navigator is also integrated with the AdvantageGo Platform of cloud based


Microservices.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. A restart of
the system is not required for any changes.

59
IMPLEMENTATION, PRICING, AND SUPPORT
The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 6 to 10 people consists of resources from the insurer (40%) and NITL
(60%). Service level agreements are offered; a typical SLA includes: Immediate: 4 hours,
Urgent: 1.5 business days; High: 4 business days; Medium: 12 business days and Low:
22 business days.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

NITL offers term license, perpetual license, usage based, SaaS, subscription and risk
based pricing options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license/flat fee and per
transaction. The vendor will offer a fixed price implementation for implementations not
requiring data migration. Carriers may also need to license the following third party
software: UNIT4 Financials, Kofax Lexmark (optional) and Pyramid Analytics (optional)

The total cost to implement Advantage Suite Navigator can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Chapter: AdvantageGo: Navigator

60
AETINS SDN BHD: INSURANCE SOLUTION FRAMEWORK
(ISF)

COMPANY
AETINS is a privately owned company headquartered in Petaling Jaya, Malaysia with
sales and professional services personnel located throughout the Asia-Pacific region.
AETINS’s business is providing software and services to the insurance industry. The
company has 160 employees, of which 130 are available to provide professional services
/ client support for their PAS solution. Forty are physically located in Europe, Middle East,
and Africa.

Table 29: Company and Product Snapshot

COMPANY Annual corporate revenues US $ 4.5 Million

Year founded 1998

Exchanges/Symbols N/A

Headquarters Location Global: Petaling Jaya, Malaysia

PAS SYSTEM Name Insurance Solution Framework (ISF)

Current release and date of 4.1


release

Release intervals Minor enhancements: Every Quarter


Major enhancements: Every Year

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


Upgrades Insurers can skip multiple versions e.g. go
directly from version 4.0 to version 7.0
Vendor support for prior versions: They support
all versions.

Target market All lines of business. Insurers of any size

Source: Vendor RFI

61
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is not available; data services, which could be developed (would be considered
customization); assignment, which is under development; ISO, which is not available,
rate analysis, which is under development; forms management, which is not available;
document management, which is available with integration to a third party solution; and
multichannel/mobile, which is available with integration to a separate module.

Figure 17: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of three insurer clients. The breakdown of the clients is as follows: Tier
4 (one client) and Tier 5 (two clients).

Table 30: Customer Base

EUROPE, MIDDLE EAST, In production with current 3


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Middle East:


Bahrain 1

62
Existing client base by Middle East:
country Bahrain 1
Saudi Arabia 1
Egypt 1

Deployment method On Premise: 100%


(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Marquee clients 1

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 31: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 2

HOMEOWNERS In production today 3

COMMERCIAL AUTO In production today 2

COMMERCIAL PROPERTY In production today 3

COMMERCIAL LIABILITY In production today 3

WORKERS COMP In production today 3

BUSINESS OWNERS POLICY In production today 3

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


Source: Vendor RFI

TECHNOLOGY
The technical architecture is a 3-tier architecture. Database is Oracle RDBMS 11g or 12
C. The main application is in Oracle Forms. The core application is designed to be
process-oriented and enable straight-through processing (STP) with complete integration
across modules. These are exposed as web services. They have all the branch
operations Java-based, and the roadmap has plans to offer a complete Java-based
solution as an alternative to Oracle forms UI.

They also have another variation, which is getting implemented, which is BPM based. It is
called ISFbpm. It is developed on IBM BPM and IBM ODM rules engine. One line of
business (Motor) is already live with a customer, and the rest are under development and
test phases.

63
The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 32: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 30%


C++: 30%
Business users: Java: 30%
Other (PLSQL, ORACLE FORMS): 70%
Developers: Java: 30%
Other (PLSQL, ORACLE FORMS): 70%

OPERAX`TING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Windows, Linux,
Unix
Planned change to code base: Java

APPLICATION SERVERS Oracle Weblogic Application Server

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services;


Additional options: ACORD Standard XML; Other
XML; JSON format ; Flat files;
Public API integrations: N/A

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 600 back office users and 1


million policies

Source: Vendor RFI

The data model is proprietary with the option to map to other standard data models. The
data model can be extended by carriers using tools. For the insurer to make changes to
the data model, a number of extension points in the data model are provided where the
customer can store data of their choosing. The number of slots is limited, and the
underlying schema cannot be changed except by changing code. The data model can be
released to an insurer. It can be published to an insurer’s data model and mapped to an
intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, workflow definition, and role-

64
based security integration. Screen definition, business rule definition, interface definition,
and data definition are configurable using tools targeted for an IT user. Changes to the
system are possible by copying and pasting between products.

In Europe, Middle East, and Africa the system is preintegrated with an inhouse solution
for agent portal software; an inhouse solution for agent management systems; an
inhouse solution for analytics solutions; an inhouse solution for business intelligence
systems; an inhouse solution for data warehouse; SAP, Oracle Financials, Sun. and
CODA for general ledger; IBM BPM as option for business process management
systems; an inhouse solution for reinsurance solutions; an inhouse solution for billing
systems; an inhouse solution for reinsurance systems; Docuflo by Infoconnect for
document management systems; an inhouse solution (Oracle tools) for document
creation systems; under development for supplier networks and portals; on roadmap for
geo coding solutions; an inhouse solution for payments systems (disbursements); an
inhouse solution for illustrations; an inhouse solution for eapplications; an inhouse
solution for new business and underwriting; an inhouse solution for claims; SugarCRM
support for crm; an inhouse solution for product calculation engine; an inhouse solution
for distribution management; an inhouse solution for producer portal (quick quote,
illustration, bind, issue); an inhouse solution for prospective customer portal (quick quote,
illustration, bind, issue) and an inhouse solution for policyholder portal (inquiries and
transactions for in-force policies).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Proprietary. A typical project team of 20
people consists of resources from the insurer (60%) and AETINS (40%). Service-level
agreements are offered; a typical SLA matrix goes by “Severity” measured from client’s
view and “Complexity” measured from AETINS’s view. The matrix has response times
and also average resolution times. These SLAs are tracked regularly and reported to

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


customers in a transparent manner.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 7 to 12 months.

AETINS offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of functional
components/modules, number of total or named users, premium volume, number of
states or geographies, enterprise license / flat fee, and per transaction. The vendor will
offer a fixed price implementation for green field operations, where there is scope for
customer to adopt the systems process “as is..” They go for fixed price implementation.
Even for legacy insurers, based on product study, they should be able to estimate the
likely size and go for fixed price implementation (if required). Carriers may also need to
license the following third party software: Platform software of Oracle DBMS and Oracle
Web logic application server

65
The total cost to implement Insurance Solution Framework (ISF) can vary according to
the capabilities and available resources of the client, and the overall scope of system
use.

Table 33: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million No cost, not 22%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 22%


implementation costs applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million No cost, not 22%
implementation applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A Under €500,000 No cost, not 22%


implementation for a

Chapter: AETINS SDN BHD: Insurance Solution Framework (ISF)


applicable
European insurance
holding company

Source: Vendor

66
BEYONTEC SOLUTIONS, INC.: BEYONTEC SUITE

COMPANY
Beyontec Solutions, Inc. is a privately owned company headquartered in Irving, TX with
sales and professional services personnel located throughout North America, the Middle
East, Africa, and South Asia. Beyontec Solutions, Inc.’s business is providing software
and services to the insurance industry. The company has 200 employees, of which 160
are available to provide professional services / client support for their PAS solution. They
do not provide an employee breakdown by region.

Their next user conference is coming in the next 12–18 months.

Table 34: Company and Product Snapshot

COMPANY Annual corporate revenues Between $5-$10M

Year founded 2008

Exchanges/Symbols N/A

Headquarters Location Global: Irving, TX

PAS SYSTEM Name Beyontec Suite

Current release and date of 1.4 in 2012


release

Release intervals Minor enhancements: About 4 times per year


Major enhancements: Every two years

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
all versions.

Target market Insurers with a premium income of less than


$500 million that process General Insurance,
Medical, and Life Insurance.

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


Source: Vendor RFI

CELENT OPINION
The Beyontec policy administration solution is one module in the Beyontec full suite
which can be deployed individually or as a full suite. The solution was built in 2008 on a
modern architecture and has been continuously upgraded since then.

The system has all the functionality required by most carriers including some nice
features such as the ability for a user to turn on or off help text, although it would benefit
from modernization of the user interface.

The configuration environment provides sufficient tools for most carriers to handle most
of the changes that are needed. Most common attributes are preconfigured, and wizards
are provided that allow for configuration of many predefined business rules, products, or
workflows. Complex rules include a visualization tool that is fairly intuitive and could be
utilized by a business user. Workflow also utilizes a visualization tool.

67
With business rules, workflow, task generation, and a business-friendly configuration
environment, this solution is a good option for small carriers who are looking for an
affordable option.

In EMEA the solution has proven popular in the Middle East with installations of the
solution in multiple countries and strong feedback in their first appearance in the EMEA
report.

OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include data
services, which is available with integration to a third party solution; assignment, which is
configurable using simple tools targeted for a business user; rate analysis, which is
available with integration to a third party solution; multiple insurers, which is configurable
using simple tools targeted for a business user; and multichannel/mobile, which is under
development.

Figure 18: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

68
CUSTOMER BASE
They have a total of nine insurer clients. All clients are Tier 5.

Table 35: Customer Base

EUROPE, MIDDLE EAST, In production with current 9


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Middle East:


United Arab Emirates 2
Oman 1

Existing client base by Middle East:


country United Arab Emirates 4
Oman 2
Bahrain 1
Kuwait 1
Kingdom of Saudi Arabia 1

Deployment method On Premise: 100%


(percentage of client base)

Marquee clients Dubai Insurance,


Marsh Middle East & North Africa,
Saudi Arabian Insurance Company

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on Beyontec Suite. Two are Tier 5 insurers, one is a Tier
4 insurer, and one is a Tier 3 insurer. Two references have been using the solution for 1
to 3 years, one for less than a year, and one for more than 3 years. Three of the
references used the solution for a mix of personal and commercial lines, with one of
those also offering workers’ compensation and specialty lines. One reference uses the
solution for only specialty lines.

In terms of the best things about the vendor references commented on how
knowledgeable and supportive they were. In terms of the solution, references valued the
workflow management process, the configurability, and the document and
communication management.

In terms of areas to improve in the system, references mentioned analytics and reporting

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


and a portal for policyholders and one mentioned an update to the underlying technology
itself. The only area mentioned for improvement of the vendor came from one reference,
who wanted to see improvement in project management, although the same reference
commented on how strong the support was if an issue came up.

69
Functionality received above average scores overall, and within functionality, portals for
policyholders and prospects received the highest score. Configurability scores were
above average, and within configurability user management (permissions, authority)
received the highest score. Comments on the integration were above average, and within
integration your claim system(s) received the highest score. Regarding their technology
experiences, insurers gave above average marks, and within technology flexibility of the
data model received the highest score. The implementation was rated above average
overall, and within implementation, “implementation completed on budget” received the
highest score. Finally, support received above average scores, and within support
knowledge of their solution and relevant technology received the highest score.

Figure 19: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
4.35

Support Configurability

4.47 4.20

Implementation Integration
4.46 4.81

Technology 4.42

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 36: Selected Lines of Business Supported

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 9

HOMEOWNERS In production today 9

COMMERCIAL AUTO In production today 9

COMMERCIAL PROPERTY In production today 9

COMMERCIAL LIABILITY In production today 9

WORKERS COMP In production today 9

BUSINESS OWNERS POLICY In production today 9

Source: Vendor RFI

70
TECHNOLOGY
The technical architecture is an SOA architecture, built on an Oracle database and
written in Java, with data purging and archiving done using Oracle scripts using PL/SQL
programming language. The product is delivered as a “thin” client, meaning nothing is
installed on the desktops or laptops of the user; access is granted with only an internet
connection and proper authorities and permissions managed by the user company. Note
that all current popular browsers are supported.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android and Windows.

Table 37: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


Business users: Java: 100%
Developers: Java: 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Windows / Linux

APPLICATION SERVERS Apache Tomcat 7.x

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services; ACORD Standard XML;


Additional options: Other XML; RESTful HTTP style
services; JSON format; Flat files; Custom API;
Public API integrations: Google Maps

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: no
Windows interface available: no
Apple Mac interface available: yes
Linux-based interface available: no

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: over 400 users and Over 10,000


per month policies

Source: Vendor RFI

The data model is handled using Hibernate ORM. Data models are proprietary to
Beyontec Suite. The data model can be extended by carriers using the configuration tools
supplied by Beyontec. For the insurer to make changes to the data model, a set of tools
are provided that allow technical staff to extend the data model and the SQL database
schema. The data model can be released to an insurer. It can be published to an
insurer’s data model, and mapped to an intermediate format.

71
Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and data definition. Interface definition is configurable
using tools targeted for an IT user. Changes to the system are possible by copying and
pasting between products.

In Europe, Middle East, and Africa, the system is preintegrated with Proprietary, which is
included in the Beyontec Suite, for agent portal software; Proprietary for e-signature;
Proprietary for general ledger; Proprietary for reinsurance solutions; Proprietary for billing
systems; Proprietary for reinsurance systems; Proprietary for document management
systems; Windward for document creation systems; Proprietary for supplier networks and
portals; Proprietary for payments systems (disbursements); Proprietary for eapplications;
Proprietary for new business and underwriting; Proprietary for claims; Proprietary for
producer portal (quick quote, illustration, bind, issue); Proprietary for prospective
customer portal (quick quote, illustration, bind, issue) and Proprietary for policyholder
portal (inquiries and transactions for in-force policies).

Product changes cannot be analyzed and can be tested in a standard way using common
tools and they provide a set of prebuilt tests. A restart of the system is required for
insurance product modification/configuration, screen configuration, change to underlying
data model, new web service or integration point, or change to portal.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 4-6 people
consists of resources from the insurer (10%), Beyontec Solutions, Inc. (85%) and
external professional services firms (5%). Service-level agreements are offered; a typical
SLA is available on client request.

The average time to get all the products up and running varies from the estimates for the
US. In EMEA when insurers utilize new software they bring up, at one time, all their lines
of business, as many as 50 in many cases. This effort, for all lines, is typically 6-8
months.

Beyontec Solutions, Inc. offers term license, perpetual license, usage-based, SaaS,
subscription, and risk-based pricing options. The license fees are typically based on
number of functional components/modules, number of concurrent users, number of total
or named users, premium volume, number of states or geographies, enterprise license /
flat fee, and per transaction. The vendor will offer a fixed price for implementations,

Chapter: Beyontec Solutions, Inc.: Beyontec Suite


whereas client facing activities are T&E. Carriers may also need to license the following
third party software: Oracle Database, Quadbase, and Espress Reports.

The total cost to implement Beyontec Suite can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 38: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs Under €500,000 Under €500,000 No cost, not 22%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

72
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A No cost, not No cost, not 22%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million No cost, not 22%
implementation applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A No cost, not No cost, not 22%


implementation for a applicable applicable
European insurance
holding company

Source: Vendor

Chapter: Beyontec Solutions, Inc.: Beyontec Suite

73
CÁLCULO S.A.: E-TICA

COMPANY
Cálculo is a privately owned company headquartered in Madrid, Spain with sales and
professional services personnel located throughout the European, Middle Eastern and
African region. Cálculo’s business is providing software and services to the insurance
industry. The company has 160–180 employees, of which 78 are available to provide
professional services / client support for their PAS solution; 160–180 employees are
physically located in Europe, Middle East, and Africa.

The last user conference was Reto Digital: De la palabra al hecho, focusing on
continuous delivery, devops, docker, cloud and microservices. It defined the digital
challenges in the insurance sector.

Table 39: Company and Product Snapshot

COMPANY Annual corporate revenues US$12.0 million

Year founded 1966

Exchanges/Symbols N/A

Headquarters Location Global: Madrid, Spain

PAS SYSTEM Name e-tica

Current release and date of Version 4, dated September 2016


release

Release intervals Minor enhancements: Every Month


Major enhancements: Annual

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
all versions.

Target market All type of insurers business models, direct


Internet channel (NUEZ, DIRECT), supported by
a web front, end customer as insurance
companies, insurance in core banking model
(segurcaixa) or companies with a strong weight
of channel agent & mediators (GES, ASEFA,
PSN, AMA).

Source: Vendor RFI


Chapter: Cálculo S.A.: e-tica

74
OVERALL FUNCTIONALITY
Some functionality is available out of the box, with most functionality configurable by
business users including quote, underwriting, assignment, renewals, endorsement,
rating, product management, reinsurance, multiple insurers, forms management,
scheduling/calendar, and workflow. Some functionality is delivered through integration to
a separate module, including multichannel/mobile, document management, document
creation, reporting/analytics, and ACORD. Finally rate analysis requires coding.

Figure 20: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Multi
Workflow
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of eight insurer clients. The breakdown of the clients is as follows: Tier
2 (one client), Tier 3 (one client), Tier 4 (five clients), and Tier 5 (one client).
Chapter: Cálculo S.A.: e-tica

Table 40: Customer Base

EUROPE, MIDDLE EAST, In production with current 5


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 3


or more years old

New clients since 2015 Europe:


Spain 3

75
Existing client base by Europe:
country Spain 8

Deployment method On Premise: 75%


(percentage of client base)
Hosted: 25%

Percentage of clients using 0%


PAS through BPO services

Marquee clients 0

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 41: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 4

HOMEOWNERS In production today 4

COMMERCIAL PROPERTY In production today 1

COMMERCIAL LIABILITY In production today 1

WORKERS COMP In production today 1

Source: Vendor RFI

TECHNOLOGY
The technical architecture is a WEB JEE application from the standards determined by
the frameworks: Struts, and Hibernate. They are currently evaluating change to SOAP
services layer to REST, facilitating integration to any type of device and technology.

The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 42: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 90%
JavaScript: 10%
Business users:
Java: 90%
Chapter: Cálculo S.A.: e-tica

JavaScript: 10%
Developers:
Java: 80%
e-tica language (DSL): 20%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: HP-UX 11.314, Red
Hat Enterprise Linux Server R.5.1, AIX 6.1, Red Hat
Enterprise Linux Server 64
Planned change to code base: Front-end languages
(NODE.JS…)

76
TECHNOLOGY SPECIFICS

APPLICATION SERVERS IBM WebSphere Application Server 7, Oracle


WebLogic Server 9.x,10x, 11x, 12x, Apache Tomcat,
6.,7.x

DATABASES Preferred: Oracle


Additional options: DB2/UDB

INTEGRATION METHODS Preferred: Web Services; Flat files


Additional options: Other XML; RESTful HTTP style
services; JSON format ; MQSeries, JMS or similar
queue technology; Custom API
Public API integrations: Google Maps

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 100 internal users and an


unlimited amount of Internet users and 700,000
policies

Source: Vendor RFI

The data model is a proprietary data model based on the insurance sector experience. It
supports a relational database. The data model cannot be modified directly by the
insurer. For the insurer to make changes to the data model, it is recommended that a
DBA extend the database schema in SQL because the changes to business logic and
screen designs are written in code. The data model can be released to an insurer. It can
be mapped to an intermediate format.

Carriers have access to core code; configuration tools targeted to a business user are
available for the following: insurance product definition, business rule definition, and
role-based security integration. Screen definition, workflow definition, interface definition
and data definition require coding. Changes to the system are possible by defining
reusable parts that can be linked together.
Chapter: Cálculo S.A.: e-tica

In Europe, Middle East, and Africa, the system is preintegrated with Dynamics for data
mastery, master data management tools; SAP and SAGE for general ledger; ODM for
business process management systems; e-Tica Financial for billing systems; e-Tica RE
module and Internal Developments for reinsurance solutions and systems; KTP
(Document Management) for document management systems and document creation
systems; e-Tica Claims module and Internal Developments for claims; Dynamics for
CRM and Drools (Business Rules management System).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. A restart of
77
the system is required for change to underlying data model, new web service or
integration point, change to portal, and workflow change.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 15–20 people
consists of resources from the insurer (20%), Cálculo (40%), and external professional
services firms (40%). Service-level agreements are offered; a typical SLA includes
response time, corrective support time, and software quality metrics,

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Cálculo offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license / flat fee, and per
transaction. The vendor will offer a fixed price implementation when customers accept
the standard implementation. Carriers may also need to license the following third party
software: It varies on the DB and Applications Server Selected. E-tica should also be
integrated with an external general ledger and document management.

The total cost to implement e-tica can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 43: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million €500,000 to €1 20%


only: assuming a two million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not Under €500,000 205


implementation costs applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million €5 million to €10 20%
implementation million
period, for a
European insurance
Chapter: Cálculo S.A.: e-tica

holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

78
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A No cost, not €1 million to €5 20%


implementation for a applicable million
European insurance
holding company

Source: Vendor

Chapter: Cálculo S.A.: e-tica

79
CCS: ROUNDCUBE POLICY

COMPANY
CCS is a privately owned company (with outside investors) headquartered in Woerden,
the Netherlands with sales and professional services personnel located throughout the
European, Middle Eastern, and African region. CCS’s business is providing software and
services to the insurance industry. The company has 152 employees, of which 80 are
available to provide professional services / client support for their PAS solution. Eighty
are physically located in Europe, Middle East, and Africa.

The last user conference was a half-day customer event introducing the latest release
and its new features. The conference consisted of market trends with speakers from
insurers, brokers, and research and consultancy agencies as well as a roundtable with C-
suite executives.

Table 44: Company and Product Snapshot

COMPANY Annual corporate revenues 20

Year founded 1983

Exchanges/Symbols N/A

Headquarters Location Global: Woerden, the Netherlands

PAS SYSTEM Name Roundcube Policy

Current release and date of 2.0


release

Release intervals Minor enhancements: Three times a year


Major enhancements: Once a year

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Medium to large general insurance companies

Source: Vendor RFI

CELENT OPINION
CCS continues to have a strong position in the Netherlands and is growing in its home
territory. CCS leverages the Software AG technology into Roundcube. CCS has focused
Chapter: CCS: Roundcube Policy

on opening up the architecture of the core system to adapt to insurers’ growing


requirements to integrate new systems, insurtech, and data. Such an investment in the
offerings architecture could appeal to larger, multinational insurers.

Roundcube Policy offers a very modern, web-based user interface to the digitally
conscious customers. The configuration screens in the demo all showed a modern, web-
based user interface. Some of the configuration processes use built-for-purpose tools
from partners.

In the prior report it was noted that Roundcube Policy was new then, and Celent would
be watching its impact. In Celent’s opinion, Roundcube Policy hasn’t yet had time to
demonstrate its capability or have its full impact on the market. It is clear that Level-7’s

80
heritage is driving success locally; perhaps, as has been seen with other vendors, it can
take time to understand how to sell what is a very different offering.

Celent will continue to watch with interest how Roundcube Policy emerges from the
chrysalis and is received in the market.

OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include
assignment, product management, and multiple insurers which are configurable using
simple tools targeted for a business user; and rate analysis, which is available with
integration to a separate module provided by this vendor. Reinsurance is not available,
and ISO is not applicable.

Figure 21: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap
Chapter: CCS: Roundcube Policy

customization)
No Not available Not applicable

Source: Vendor RFI

81
CUSTOMER BASE
They have a total of 30 insurer clients. The breakdown of the clients is as follows: Tier 2
(one client), Tier 3 (nine clients), Tier 4 (four clients), Tier 5 (16 clients).

Table 45: Customer Base

EUROPE, MIDDLE EAST, In production with current 30


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


Netherlands 2

Existing client base by Europe:


country Netherlands 29
Belgium 1

Deployment method On Premise: 95%


(percentage of client base) Hosted: 5%

Percentage of clients using None


PAS through BPO services

Marquee clients Generali,


Amlin,
Markel

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Roundcube Policy. All are Tier 5 insurers. Two of the
references have been using the solution for more than three years, and one was still
implementing the solution. All are based in EMEA. Two references used the solution for a
mix of personal and commercial lines, while the last reference uses the solution for
mostly commercial lines.

Regarding the best things about the vendor, the references highlighted the quality of the
consultants, and regarding the system, proven technology and stability.

Regarding things that customers might change, a few items were cited, including
improving the web solutions, connectivity, and integrating the web and back office.
Regarding implementation one reference sought better knowledge transfer after
implementation.
Chapter: CCS: Roundcube Policy

82
Functionality received above average scores overall, and within functionality document
management received the highest score. Configurability scores were above average and
within configurability workflow (design and maintenance) received the highest score.
Comments on the integration were above average, and within integration external data
sources received the highest score. Regarding their technology experiences, insurers
gave above average marks, and within technology scalability of the solution received the
highest score, while flexibility of the data model was an area in need of improvement. The
implementation was rated above average overall, and within implementation knowledge
of their solution and relevant technology received the highest score. Finally, support
received above average scores, and within support knowledge of their solution and
relevant technology received the highest score.

Figure 22: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.62

Support Configurability
3.67
3.93

Implementation Integration
4.00 3.11

Technology 3.39

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 46: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA
Chapter: CCS: Roundcube Policy

PERSONAL AUTO In production today 19

HOMEOWNERS In production today 22

COMMERCIAL AUTO In production today 19

COMMERCIAL PROPERTY In production today 22

COMMERCIAL LIABILITY In production today 14

WORKERS COMP In production today 12

83
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

BUSINESS OWNERS POLICY In production today 22

Source: Vendor RFI

TECHNOLOGY
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 47: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 60%


.NET (): 40%
Business users: Java: 60%
.NET (): 40%
Developers: Java: 60%
.NET (): 40%

OPERATING SYSTEMS Implemented in Microsoft .NET and JEE/Java


Operating systems deployed on: Windows

APPLICATION SERVERS Tomcat, latest two versions

DATABASES Preferred: Microsoft SQL Server


Additional options: Oracle; DB2/UDB; Sybase; Other
SQL

INTEGRATION METHODS Preferred: Web Services; ACORD Standard XML


Additional options: Other XML; RESTful HTTP style
services; JSON format ; MQSeries, JMS or similar
queue technology; Flat files; Custom API
Public API integrations: Google maps, MS Dynamics,
Salesforce

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: No
Chapter: CCS: Roundcube Policy

Is the design of the user interface responsive to


different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 5,000 users and 1.2 million


policies

Source: Vendor RFI

84
The data model is proprietary but can be converted to standard (e.g. Acord) through
MDM. It supports ADN. The data model can be extended by carriers using integrated
tools. For the insurer to make changes to the data model, a number of extension points in
the data model are provided where the customer can store data of their choosing. The
number of slots is limited, and the underlying schema cannot be changed except by
changing code. The data model can be released to an insurer. It can be published to an
insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and data definition. Interface definition and role-based
security integration are configurable using tools targeted for an IT user. Changes to the
system are possible by defining reusable parts that can be linked together.

In Europe, Middle East, and Africa, the system is preintegrated with Dutch postal code
service for address verification; RDW (Driver and Vehicle Licensing Agency), Friss
(Fraud, Risk, and Compliance Management solution), Roy-data (Claim-free years
database). Infofolio (property information) for third party data services; Own software for
agent portal, agent management systems, data warehouse, general ledger, billing
systems, document management systems, document creation systems, payments
systems (reimbursements), illustrations, new business and underwriting, product
calculation engine, distribution management, producer portal, prospective customer
portal, and policyholder portal; Colimbra for e-signature; Qlickview for analytics solutions;
Crystal Reports for business intelligence systems; webMethods for business process
management systems; Carglass, Nomot for supplier networks and portals; Google maps
for geocoding solutions; E-ABS (broking) for eapplications; EMS, CED for claims;
MSDynamics, Salesforce, and Siebel for CRM.

Product changes can be analyzed using an impact analysis tool that provides a report,
detailing products and channels affected, and can be tested in a standard way using
common tools. A restart of the system is required for change to underlying data model.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is proprietary. A typical project team of 10–20
FTE consists of resources from the insurer (30%), CCS (20%), and external professional
services firms (50%). Service-level agreements are offered; CCS offers a whole range of
SLAs: from extended working hours to 24 hour support, from support to functional
Application Management.

The average time to get the first line of insurance live in a single jurisdiction is typically 1
to 3 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.
Chapter: CCS: Roundcube Policy

CCS offers term license, perpetual license, usage-based, SaaS, subscription, risk-based,
and other (they have a risk and reward scheme, depending on results achieved [KPIs])
pricing options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license / flat fee, per
transaction, and other (license fees dependent on realizing the business case KPIs). The
vendor will offer a fixed price implementation after a thorough pre-analysis.

85
The total cost to implement Roundcube Policy can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 48: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million €500,000 to €1 22%


only: assuming a two million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 Under €500,000 22%


implementation costs
for the regional
insurance company.

Assuming a four year €500,000 to €1 million €1 million to €5 million €1 million to €5 22%


implementation million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €500,000 to €1 million €500,000 to €1 22%


implementation for a million
European insurance
holding company

Source: Vendor

Chapter: CCS: Roundcube Policy

86
DUCK CREEK TECHNOLOGIES: DUCK CREEK POLICY

COMPANY
Duck Creek is a privately owned company headquartered in Boston, MA, USA with sales
and professional services personnel located throughout the North American, European,
and Asia-Pacific regions. Duck Creek’s business is providing software and services to the
insurance industry. The company has over 1,100 employees. Duck Creek does not
provide a breakdown of employees by business unit or region.

The user conference is an annual event called FORMATION that is attended by


customers, prospects, partners, industry analysts, and thought leaders. FORMATION
provides these constituents with access to Duck Creek product and services insights,
networking opportunities with the Duck Creek employee and customers base, and an
opportunity to explore ways to maximize the value of Duck Creek's products and
services.

Table 49: Company and Product Snapshot

COMPANY Annual corporate revenues Confidential

Year founded 2000

Exchanges/Symbols N/A

Headquarters Location Global: Duck Creek Technologies


51 Sleeper Street | Boston, MA 02210 | USA

PAS SYSTEM Name Duck Creek Policy

Current release and date of 2017 R1, April 2017


release

Release intervals Minor enhancements: As needed


Major enhancements: 1-2 per year

Upgrades Insurers Can skip multiple versions (e.g., go

Chapter: Duck Creek Technologies: Duck Creek Policy


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and those released up to two
years prior.

Target market Duck Creek primarily targets Tier 1 to 4 Property


& Casualty insurance carriers, but also works
with MGAs and program writers.

Source: Vendor RFI

CELENT OPINION
In the prior report this solution was covered as Accenture Duck Creek, but is now Duck
Creek with new ownership and new branding.

Duck Creek continues to offer a very modern and functional system with a very strong
approach to product development and configuration. It is good to see the product growing
in customer base again in the EMEA region.

As noted in the prior report, Duck Creek offers a very modern and efficient front end.
There is a blend of a workflow-style approach offering a view of where the user is in the
process, where appropriate, as well as context-sensitive action menus — mixing

87
simplicity and putting alternative actions at the user’s fingertips. This attention to detail
and usability is not lost on the configuration screens, with Product Studio looking clean
and easy to use in the demo.

The solution comes with a dual configuration environment. Studio is meant for a business
user and includes wizards for the most common tasks in a very user-friendly construct.
Business rules are generated in easily understood sentence structure. Author is intended
for an IT professional and is a very granular development environment that lets a
professional make modifications to virtually any product, process, or function. Built-in
modeling tools include graphical depictions of the product/rate changes. A Test
Automation Center is included, which is a set of tools and scripts to easily create
automated test cases and run them in a batch mode.

In the prior report, Celent noted that the Duck Creek Suite had matured and queried if
this would translate into new clients for the solution in EMEA, and at this writing the
answer is yes, with growth shown in the region, presently concentrated in the United
Kingdom.

Chapter: Duck Creek Technologies: Duck Creek Policy

88
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include
assignment, which is configurable using simple tools targeted for a business user;
reinsurance, which is available with integration to a third party solution; and multiple
insurers, which is configurable using tools targeted for an IT user.

Figure 23: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development

Chapter: Duck Creek Technologies: Duck Creek Policy


partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 10 insurer clients. The breakdown of the clients is as follows: Tier 1
(three clients), Tier 2 (two clients), Tier 4 (three clients) and Tier 5 (two clients).

Table 50: Customer Base

EUROPE, MIDDLE EAST, In production with current 7


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 3


or more years old

New clients since 2015 Europe:


United Kingdom 3

89
Existing client base by Europe:
country United Kingdom 8
Ireland 1

Deployment method On Premises: 67%


(percentage of client base) Other: 33%

Marquee clients Zurich UK,


Atrium Underwriters,
RSA Ireland

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Duck Creek Policy. Two are Tier 5 insurers. One is a
Tier 4 insurer. Two references have used the solution for more than three years, and the
last one for less than a year. One reference uses the solution for all or mostly personal
lines, one for all or most commercial lines, and one for specialty lines.

In terms of the best things about the system references noted the configurability of the
system, including ability to configure complex product designs, the rich functionality and
capability, and scalability of the solution. One reference valued the multiple support
partner options.

In terms of areas of improvement, one was knowledge sharing between vendor and
system integrator — something that perhaps reflects the early development of these in
EMEA. Some references would like to see improvements in the user interface and in
supporting concurrent change.

One reference noted that the vendor has improved since they have been a client and
show ongoing improvements.

Chapter: Duck Creek Technologies: Duck Creek Policy

90
Functionality received above average scores overall, and within functionality portals for
policyholders and prospects received the highest score, while reporting was an area in
need of improvement. Configurability scores were above average, and within
configurability making minor changes received the highest score, while user interfaces
(design and maintenance) was an area in need of improvement. Comments on the
integration were above average, and within integration external data sources received the
highest score. Regarding their technology experiences, insurers gave above average
marks, and within technology scalability of the solution received the highest score while
flexibility of the data model was an area in need of improvement. The implementation
was rated above average overall, and within implementation knowledge of their solution
and relevant technology received the highest score, while implementation completed on
time was an area in need of improvement. Finally, support received above average
scores, and within support knowledge of their solution and relevant technology received
the highest score.

Figure 24: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 3.38

Support Configurability
3.76 3.13

Implementation Integration
3.40 3.83

Technology 3.50

Chapter: Duck Creek Technologies: Duck Creek Policy


Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 51: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1

HOMEOWNERS In production today 3

COMMERCIAL AUTO In production today 2

COMMERCIAL PROPERTY In production today 4

COMMERCIAL LIABILITY In production today 4

WORKERS COMP In production today 1

91
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

BUSINESS OWNERS POLICY In production today 1

Source: Vendor RFI

TECHNOLOGY
The technical architecture is developed on the .NET Framework, written in C# and runs
on a Windows Server environment. The overall architecture is a three-tier stack,
providing logical and/or physical separation between a web-tier, application-tier and
database-tier.

The web-tier provides a Web-based policy point-of-sale and administration application


through a browser interface. All business and application logic is supported as either XML
or RESTful services through the application-tier. The data tier stores full policy images
with history and system/user administration data. The current release of the Duck Creek
Platform uses MS SQL Server 2012, 2014 or 2016.

A key architecture feature of the Duck Creek Platform is the use of product definition data
to support all the application services related to an insurance product. All aspects of
rules, rating, data, screen workflow, forms, and policy processing are defined within the
product definition metadata (XML), not custom code, so that any insurance product can
be powered by the single Duck Creek Platform. The product definitions are managed
using the toolset, Duck Creek Author, and Duck Creek Product Studio, applications which
are targeted for the business user, therefore not requiring traditional IT for product
definition and maintenance.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS) and Android.

Table 52: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:

Chapter: Duck Creek Technologies: Duck Creek Policy


.NET (C#): 99%
JavaScript: 1%
Business users:
.NET (C#): 99%
JavaScript: 1%
Developers:
.NET : 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS N/A

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

92
TECHNOLOGY SPECIFICS

INTEGRATION METHODS Preferred: Web Services; Other XML; RESTful HTTP


style services
Additional options: ACORD Standard XML; JSON
format ; MQSeries, JMS or similar queue technology;
Flat files; Custom API
Public API integrations: Duck Creek has been
integrated with a large number of third party solutions
such as SalesForce, Dynamics, LexisNexis, etc.
Customers have the ability to create their own
integrations, and therefore Duck Creek does not have
a comprehensive list.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 140,000 users and 100,000


policies

Source: Vendor RFI

The data model is housed in a relational data model to enable delivery of full-featured
solutions for core capabilities required by P&C insurance customers spanning policy
administration and rating for the entire policy lifecycle.

Chapter: Duck Creek Technologies: Duck Creek Policy


Duck Creek Policy stores the policy data in an XML format. Duck Creek makes use of a
proprietary data model defined as an XML schema and supports unique definitions for
unique products. The system allows for any XML data structure to be defined for the
products as required. Each product will have common shared data schema, yet has the
ability to extend and define as required for product lines. For prebuilt products a data
model is provided, but can be modified. It supports a proprietary data model defined as
an XML schema. The Duck Creek Platform also provides an out-of-the-box ETL process
that provides for data transformation to any schema definition. If an insurer has
standardized on one of the established models of the industry (e.g., ACORD, IAA, etc.),
these structures can be configured into their software and used at runtime.

Duck Creek Technologies has begun integrating Duck Creek Turnstile and Duck Creek
Connect5 with the existing Upload/Download features in Duck Creek Policy. At this time,
Duck Creek WC Templates customers who also have an applicable Turnstile license can
prefill data from the ACORD application into the Duck Creek Policy system by uploading
native ACORD PDFs or scanned images of the ACORD forms. By offering this
integration, Templates customers no longer have to build complex, product-specific
transforms or use a separate vendor to process ACORD data into line of business
quotes. Additional Template products integration is underway. The data model can be
extended by carriers using the Duck Creek Policy configuration tools to extend the logical

93
data model via XML objects. No database changes or source code changes are required
in order to extend an insurance product definition. The data model can be released to an
insurer. It can be published to an insurer’s data model and mapped to an intermediate
format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, business
rule definition, data definition, and role-based security integration. Workflow definition and
interface definition are configurable using tools targeted for an IT user. Changes to the
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules
and calculations) are reusable for multiple products.

In Europe, the system is preintegrated with:

• Pitney Bowes - Geocoding, Melissa Address Verification (for Germany) for address
verification.
• Advisen, APlus, Equifax, IMS Risk Assessment, RiskMeter for third party data
services (e.g., lexisnexis, iso, etc.).
• Duck Creek AgencyPortal for agent portal software, for agent management systems
and producer portal (quick quote, illustration, bind, issue).
• AssureSign for e-signature.
• Duck Creek Insights, Microsoft SSRS, Microsoft Power BI for analytics solutions.
• Duck Creek Data Insights for business intelligence systems, data mastery, master
data management tools, and data warehouse.
• Duck Creek Billing for general ledger and billing systems.
• Hyland OnBase for document management systems.
• Duck Creek Forms, Aspose, OpenText Exstream, and ImageRight for document
creation systems.
• Duck Creek Billing for payments systems (disbursements).
• Duck Creek Turnstile for eapplications.
• Duck Creek Policy for new business and underwriting.
• Duck Creek Claims for claims.

Chapter: Duck Creek Technologies: Duck Creek Policy


• Microsoft Dynamics for CRM.
• Duck Creek Rating, CompuQuote for product calculation engine.
• Duck Creek AgencyPortal for producer portal (quick quote, illustration, bind, issue).
• Duck Creek My Account Portal for policyholder portal (inquiries and transactions for
in-force policies).
• Microsoft®-Gold Alliance: SSIS/ SSRS/ SSAS & SharePoint for Report Management.
• As well as Chase Pay Connection, ODEN, Salesforce, Servebase, ePNS, German
GDV interfaces. Type class (vehicle class classification), regional class (registration
number zones classification), evB online (register and cancel policies on the ZB –
Road Authority), evB batch (receive policy updates from ZB – Road Authority), car
policy portfolio (send to GDV auto policies that have third party liability and/or Casco
coverages).

Product changes can be analyzed using the configuration and development user
interface and can be tested using a specific tool provided. A restart of the system is not
required for any changes.

94
IMPLEMENTATION, PRICING, AND SUPPORT
The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 6–12 people consists of resources from the insurer (20 to 30%), Duck
Creek (70-80%), and/or external professional services firms (70-80%). Service-level
agreements are offered; Duck Creek OnDemand offers four SaaS SLA tiers, with varying
targets for application availability, recovery point objective ("RPO"), recovery time
objective ("RTO"), incident response time and speed to answer incoming calls.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Duck Creek offers term license and SaaS subscription pricing options. The license fees
are typically based on number of functional components/modules, premium volume, and
enterprise license / flat fee. The vendor will offer a fixed price implementation after the
completion of the project phases for plan and analyze, including final sign-off of
requirements, scope, and budget. Carriers may also need to license the following third
party software: On-Premises installations require standard Microsoft operating system
and database software. SaaS/Cloud solutions do not require additional third party
software.

The total cost to implement Duck Creek Policy can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 53: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million Total of both fees would be in the range: None
only: assuming a two €1 million to €5 million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing

Chapter: Duck Creek Technologies: Duck Creek Policy


an annual GWP of
€250 million.

One year post N/A €500,000 to €1 million Under €500,000 N/A


implementation costs
for the regional
insurance company.

Assuming a four-year €5 million to €10 Total of both fees would be in the range: None
implementation million €1 million to €5 million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

95
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A €1 million to €5 million €1 million to €5 N/A


implementation for a million
European insurance
holding company

Source: Vendor

Chapter: Duck Creek Technologies: Duck Creek Policy

96
DXC TECHNOLOGY: GRAPHTALK A.I.A

COMPANY
DXC is a publicly traded company headquartered in Tysons, VA, US with sales and
professional services personnel located throughout the European, Middle Eastern, and
African region. DXC’s business is providing software and services to the insurance,
banking & capital markets, healthcare & life sciences, travel & transportation, public
sector, energy, manufacturing, consumer products & retail, communications, media &
entertainment, aerospace & defence industries. The company has 155,000 employees, of
which 600 are available to provide professional services / client support for their PAS
solution. Five-hundred are physically located in Europe, Middle East, and Africa.

The most recent customer meetings in Europe were DXC's Digital Insurance as a Service
event, Amazon Web Service Summit, Microsoft Azure event, all in Paris in 2016. DXC
held their global Client Conference in Orlando in November 2017.

Table 54: Company and Product Snapshot

COMPANY Annual corporate revenues US$ 25.0 billion

Year founded 2017

Exchanges/Symbols (NYSE: DXC)

Headquarters Location Global: Tyson, VA, USA

PAS SYSTEM Name GraphTalk A.I.A

Current release and date of V4.92 - March 2017


release

Release intervals Minor enhancements: 6 months after the annual


major release.
Major enhancements: Annually.

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market All P&C insurers, and particularly multi-line


insurers (P&C and Life)
Chapter: DXC Technology: GraphTalk A.I.A
Source: Vendor RFI

97
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is configurable using tools targeted for an IT user; data services andassignment,
which are configurable using tools targeted for a business user; endorsement, which is
configurable using tools targeted for a business user; ISO, which requires coding;
reinsurance, which is available with integration to a separate module; forms
management, which is configurable using tools targeted for a business user;
reporting/analytics, which is available with integration to a third party solution; and
multichannel/mobile, which is available with a separate module.

Figure 25: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
Chapter: DXC Technology: GraphTalk A.I.A
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of seven insurer clients. The breakdown of the clients is as follows: Tier
3 (four clients) and Tier 4 (three clients).

Table 55: Customer Base

EUROPE, MIDDLE EAST, In production with current 2


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 5


or more years old

98
New clients since 2015 Europe:
Portugal 1
Belgium 1

Existing client base by Europe:


country Czech Republic 2
France 1
Luxembourg 1
Belgium 1
Hungary 1
Slovakia 1

Deployment method On Premise: 80%


(percentage of client base)
Hosted: 20%

Marquee clients La Luxembourgeoise,


Fidea,
Thélem

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 56: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 5

HOMEOWNERS In production today 6

COMMERCIAL AUTO In production today 3

COMMERCIAL PROPERTY In production today 3

COMMERCIAL LIABILITY In production today 3

WORKERS COMP In production today 1

BUSINESS OWNERS POLICY In production today 3

Source: Vendor RFI

TECHNOLOGY
GraphTalk A.I.A is a thin client architecture application: Chapter: DXC Technology: GraphTalk A.I.A

• The UI is HTML5 and can be run using any type of browser such as Chrome, Firefox,
Microsoft Edge, or IE11.
• The application server runs on standard operating system such as Linux or Windows.
A java middleware is provided out-of-the box that allows deployment of the solution in
multiprocess and multiserver architecture. That ensures both horizontal and vertical
scalability of the system. It is also possible to design an active/active architecture
deployment that allows a process to be restarted automatically on another server
when the main server is down.
• The database is preferably Oracle, although there is one customer in production on
DB2. SQL Server will be available in June 2018.

99
The UIs and process flows are designed to be mobile device independent. The solution
natively supports Windows, and there is a multidevice application that supports Apple
(iOS) and Android.

Table 57: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


GraphTALK A.I.A. Business application layer is
implemented using GraphTalk Developer: 100%
Business users:
The GraphTalk A.I.A Business application layer is
implemented using GraphTalk Developer: 100%
Developers:
Java: 10%
C++: 40%
The configuration layer is implemented using
GraphTalk Developer: 50%

OPERATING SYSTEMS Implemented in Microsoft .NET and JEE/Java


Operating systems deployed on: Windows; Linux
(prefered)
Other possible: AIX

APPLICATION SERVERS They provide their own application server

DATABASES Preferred: Oracle


Additional options: DB2/UDB;

INTEGRATION METHODS Preferred: SOAP Web Services; RESTful API


Additional options: ACORD Standard XML; Other
XML; JSON format; MQSeries, JMS or similar queue
technology; Flat files; Custom API
Public API integrations: No public APIs

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No

Chapter: DXC Technology: GraphTalk A.I.A


Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 1,200 users and 1.35 million


policies

Source: Vendor RFI

The data model is built on a DXC-proprietary insurance data model. This model is an
implementation-oriented model for efficient storage of data and business rules. It is
exposed via a data dictionary (i.e., a public data flow model) by web services and the
A.I.A. Public Data Model (PDM). The PDM is a relational database, multidimensional
(snowflake) model, fed from GraphTalk A.I.A production data. It contains all A.I.A data

100
that is relevant for reporting and extraction. It supports none. They provide a GraphTalk
A.I.A. schema based upon the GraphTalk A.I.A. Data Dictionary, which can be easily
mapped to industry standard or client-specific schema using standard technologies. The
data model can be extended by carriers using a set of tools that allow technical staff to
extend the data model and the database schema. The data model is not released to the
insurer. It can be mapped to an intermediate format.

Carriers have access to core code. Configuration tools targeted to a business user are
available for the following: insurance product definition, workflow definition, and business
rule definition. Role-based security integration is configurable using tools targeted for an
IT user. Screen definition, interface definition, and data definition require coding.
Changes to the system are possible through reusable components, inheritance, and
other schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa, the system is preintegrated with DXC Omnichannel
(DXC Front-end) for agent portal software; Docusign for e-signature; Sisense for
analytics solutions; SAP BusinessObjects for business intelligence systems; Oracle
Financials, SAP, and Microsoft Dynamics for subsequent clients for general ledger; SICS
Cede for reinsurance systems; Nuxeo for document management systems; Business
Document for document creation systems; and Salesforce for CRM.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested using a specific tool with a set of prebuilt tests. A
restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 6 to 30 people consists of resources from the insurer (40%) and DXC
(60%).Service-level agreements are offered, A typical SLA includes:

Table 58: Typical SLAs for GraphTalk A.I.A

PRIORITY DESCRIPTION RESPONSE TIME

Priority 1 Critical failure that affect production environment and impact a critical <2 hours
functionality of the system

Priority 2 Failure that affect production environment and impact an important <4 hours
functionality of the system, but a workaround is available

Priority 3 Production issue that does not impact an important function and the
system can still run
< 2 days
Chapter: DXC Technology: GraphTalk A.I.A

Priority 4 Minor issue <10 days

Source: Vendor

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

DXC offers perpetual license, usage-based, SaaS, and subscription pricing options. The
license fees are typically based on number of functional components/modules, premium
volume, number of states or geographies, enterprise license / flat fee, policies or insured
count, and a combination of subscription model and per policy count or per insured count.
The vendor will offer a fixed price implementation when a sufficiently detailed Discovery

101
phase (Scoping and Fit-Gap Analysis Phase) can be conducted with the client
(chargeable) to enable DXC to produce a detailed project definition (scope,
requirements); then DXC may negotiate a fixed price implementation. Carriers may also
need to license the following third party software: (On-Premises only) database system
such as Oracle.

The total cost to implement GraphTalk A.I.A can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Chapter: DXC Technology: GraphTalk A.I.A

102
DXC TECHNOLOGY: XUBER FOR INSURERS

COMPANY
DXC is a publicly traded company headquartered in Virginia, US with sales and
professional services personnel located throughout the North American, European,
Middle Eastern, African, and Asia-Pacific regions. DXC’s business is providing software
and services to the insurance healthcare and life sciences, travel and transportation,
public sector, energy, banking and capital markets, manufacturing, consumer products
and retail, communications, media and entertainment, aerospace and defense industries.
The company has 155,000 employees, of which 150 are available to provide professional
services / client support for this PAS solution in EMEA. DXC holds an annual user
conference for Insurance clients. In 2017 it was a three-day event held in Orlando,
Florida in November.

Table 59: Company and Product Snapshot

COMPANY Annual corporate revenues Over $12 million

Year founded 2017

Exchanges/Symbols DXC

Headquarters Location Global: 1775 Tysons Blvd


Tysons, VA 22102
USA

PAS SYSTEM Name Xuber for Insurers

Current release and date of 4.3, July 2017


release

Release intervals Minor enhancements: Two or three times a year.


Major enhancements: Once a year.

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Large commercial and specialty lines insurers


and reinsurers

Source: Vendor RFI Chapter: DXC Technology: Xuber for Insurers

103
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include quote,
which is configurable using tools for an IT user; ACORD, which is configurable using
tools for a business user; data services, which is configurable through a scripting
language; and rate analysis, which is not available.

Figure 26: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Workflow Multi
Reporting/Analytics Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Chapter: DXC Technology: Xuber for Insurers


Source: Vendor RFI

CUSTOMER BASE
They have a total of 14 insurer clients. The breakdown of the clients is as follows: Tier 4
(five clients) and Tier 5 (nine clients).

Table 60: Customer Base

EUROPE, MIDDLE EAST, In production with current 12


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 2


or more years old

104
New clients since 2015 Europe:
United Kingdom 4

Existing client base by Europe:


country United Kingdom 10
Ireland 1

Deployment method On Premise: 80%


(percentage of client base)
Hosted: 20%

Marquee clients Aegis,


Generali,
Travelers.

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 61: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Not supported

HOMEOWNERS Not supported

COMMERCIAL AUTO Not supported

COMMERCIAL PROPERTY In production today 10+

COMMERCIAL LIABILITY In production today 10+

WORKERS COMP In production today 1

BUSINESS OWNERS POLICY In production today 3

Source: Vendor RFI

TECHNOLOGY
The technical architecture is built on the Open Foundation Framework, which is an
enterprise grade application builder used to integrate heterogeneous environments,
allowing disparate systems to be connected to each other. In technical terms X4I consists

Chapter: DXC Technology: Xuber for Insurers


of three logical layers: a data layer, a service layer, and a presentation layer.

Components which make up the service layer include security, batch data uploader, rules
and calculation engine, data provider, work queue, document production, document
management, batch scheduler, workflow/state actions, email and mail and file server
monitoring.

Each component delivers its function to the end user through the web interface of the
presentation layer. Some administrative and set-up functions are presented using
Windows-based tools.

105
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 62: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


.Net: 100%
Business users:
HTML5: 100%
Developers:
WPF / XAML: 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: See OPEN
Foundation Technology Stack slide

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: None


Additional options: Web Services; ACORD Standard
XML; Other XML; Flat files; Custom API;
Public API integrations: Google Maps, Open
Streetmap, Bing

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by

Chapter: DXC Technology: Xuber for Insurers


developers: No

SCALABILITY Largest deployment: 375 users and over 1 million


policies

Source: Vendor RFI

The data model is Proprietary. It supports ACORD, Lloyds, LIRMA, and ILU Messaging.
The data model can be extended by carriers via configuration, without coding. For the
insurer to make changes to the data model, a set of tools is provided that allow the
technical staff to extend the data model and the SQL database schema. The vendor is
willing to release the data model to an insurer. It can be published to an insurer's data
model.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition and data definition. Screen
definition, workflow definition, business rule definition, interface definition, and role-based
security integration are configurable using tools targeted for an IT user. Changes to the

106
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules,
and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa, the system is preintegrated with MS Sharepoint for
document management systems and Xuber Xposure for geocoding solutions.

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. A restart of the
system is not required for any changes made using configuration tools.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is proprietary. A typical project team of 5 to 10
people consists of resources from the insurer (50%) and DXC (50%). Service-level
agreements are offered; a typical SLA includes time to first response based on business
impact followed by full resolution within a specified timeframe. Other SLAs relate to
business process outsourcing, where new slips are keyed into the customer system
within a specified timeframe.

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

DXC offers term license, perpetual license, usage-based, SaaS, subscription, and risk-
based pricing options. The license fees are typically based on number of concurrent
users, number of total or named users, premium volume, number of states or
geographies, enterprise license / flat fee, per transaction, or a combination of methods to
according to the client’s needs. The vendor will offer a fixed price implementation for
customers who operate in markets they are familiar with and whose requirements align
with their experience and expectations.

The total cost to implement Xuber for Insurers can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Chapter: DXC Technology: Xuber for Insurers

107
ESKADENIA SOFTWARE: ESKA INSURES - GENERAL
INSURANCE

COMPANY
ESKADENIA is a privately owned company headquartered in Amman, Jordan with sales
and professional services personnel located throughout the European, Middle Eastern,
and African region. ESKADENIA’s business is providing software and services to the
insurance telecom, enterprise, education, internet, and healthcare industries. The
company has over 220 employees, of which more than 60 are available to provide
professional services / client support for their PAS solution. Sixty are physically located in
Europe, Middle East, and Africa.

The last user conference was an insurance day event in Riyadh to showcase
ESKADENIA's systems and success stories with the KSA insurance industry

Table 63: Company and Product Snapshot

COMPANY Annual corporate revenues Confidential

Year founded 2000

Exchanges/Symbols N/A

Headquarters Location Global: Amman, Jordan

PAS SYSTEM Name ESKA® Insures - General Insurance.

Current release and date of 4.2.0


release 28/05/2017

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


Release intervals Minor enhancements: Quarterly Basis
Major enhancements: Yearly Basis

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
all versions.

Target market Medium to large insurance companies;


conventional and Takaful and brokerage
companies; retail and reinsurance.

Source: Vendor RFI

CELENT OPINION
Eskadenia’s ESKA Insures General Insurance System continues to be a very functional
system installed across the Middle East and Africa region. Eskadenia continues to win
deals in the region.

Eskadenia demonstrated a web-based interface, which was very functional with quite
busy data input screens. The solution makes strong use of tabs and grouping structures
to help expert users navigate through the screens. The user interface style is different
from some of the Western European interfaces, but is much more modern than many of
the systems in the region, and the functionality shines through.

108
The number of installations has grown since the report in 2014 but appears to be about
the same level as the 2016 report. Celent will watch with interest how ESKA Insures
performs in the region and how it stretches to new territories.

OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which could be developed (would be considered customization); data services, which
requires coding; rate analysis, which is not available; document management, which is
available with integration to a separate module; document creation, which is available
with integration to a separate module; scheduling/calendar/diary, which is under
development; and reporting/analytics and workflow, which are available with integration
to a separate module. Eskadenia has plans to implement ISO support for the US market.

Figure 27: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Multi
Reporting/Analytics Workflow Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

109
CUSTOMER BASE
They have a total of 21 insurer clients. The breakdown of the clients is as follows: Tier 4
(2 clients) and Tier 5 (19 clients).

Table 64: Customer Base

EUROPE, MIDDLE EAST, In production with current 21


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Middle East:


Jordan 1
KSA 1
UAE 1

Existing client base by Middle East:


country Kingdom of Saudi Arabia 5
Jordan 3
United Arab Emirate 2
Bahrain 1
Iraq 1
Qatar 1
State of Palestine 1
Africa:
Egypt 3
Tanzania 2
Botswana 1
Nigeria 1

Deployment method On Premise: 100%


(percentage of client base)

Marquee clients RAK Insurance,


Arab Orient Insurance – gig,
Solidarity Saudi Takaful

Source: Vendor RFI

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


CUSTOMER FEEDBACK
Four clients provided feedback on ESKA Insures - General Insurance. Two are Tier 5
insurers, and two are Tier 4 insurers. Three of the references have been using the
solution for 1 to 3 years, and one for more than 3 years. Three references use the
solution for a mix of personal and commercial lines, one for all or mostly commercial
lines. Two references also used the solution for workers’ compensation and specialty
lines of business. All are based in EMEA.

In terms of the best things about the vendor, the references noted good support, easy to
work with. In terms of the solution one reference noted it was quick and simple to use,
fully integrated, and uses the latest technology.

In terms of areas for improvement one reference asked for more advanced knowledge of
the business.

Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score, while processing new
business (mostly manual) was an area in need of improvement. Configurability scores
were above average, and within configurability user management (permissions, authority)
received the highest score. Comments on the integration were above average and within
integration your claim system(s) received the highest score. Regarding their technology
experiences, insurers gave above average marks, and within technology scalability of the
solution received the highest score. The implementation was rated above average
overall, and within the category implementation completed on budget received the

110
highest score. Finally, support received above average scores and within support
knowledge of your business received the highest score.

Figure 28: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 4.03

Support Configurability
3.94
4.11

Implementation Integration
4.36
4.46
3.88
Technology

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 65: Selected Lines of Business Supported

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 21

HOMEOWNERS In production today 21

COMMERCIAL AUTO In production today 21

COMMERCIAL PROPERTY In production today 21

COMMERCIAL LIABILITY In production today 21

WORKERS COMP In production today 21

BUSINESS OWNERS POLICY In production today 17

Source: Vendor RFI

TECHNOLOGY
In terms of architecture, the solution consists of the following layers: database layer, data
object layer, data access layer, integration layer (finance, CRM, DMS, workflow, and
report builder), application program interface layer, and user interface layer.

111
In terms of technologies, C# .NET object-oriented web programming language (front end)
and Oracle database (back end) are used.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, and Windows.

Table 66: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


.NET (C#): 45%
JavaScript: 15%
Oracle: 40%
Business users:
.NET (C#): 45%
JavaScript: 15%
Oracle: 40%
Developers:
.NET (C#): 45%
JavaScript: 15%
Oracle: 40%

OPERATING SYSTEMS Implemented in Microsoft .NET

APPLICATION SERVERS Microsoft .Net

DATABASES Preferred: Oracle (only option)


Additional options: Microsoft SQL Server; Other
NoSQL datastore

INTEGRATION METHODS Preferred: Web Services; JSON format


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; Custom API
Public API integrations: They integrate with many
Government entities and Public APIs such as: Najim

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


at KSA, Moroor at UAE, E-Gov at Bahrain, Yaqeen at
KSA, and Google Maps.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 1,347,174 users and 382 policies

Source: Vendor RFI

The data model is a Relational Model. It supports the Relational Database Management
System. The data model can be extended by carriers using by modifying the source
codes. For the insurer to make changes to the data model, a number of extension points
in the data model are provided where the customer can store data of their choosing. The
112
number of slots is limited, and the underlying schema cannot be changed except by
changing code. The data model is not released to an insurer. It can be published to an
insurer’s data model.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, workflow definition, and data
definition. Screen definition, business rule definition, and role-based security integration
are configurable using tools targeted for an IT user. Interface definition is not available.
Changes to the system are possible through reusable components, inheritance, and
other schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa, the system is preintegrated with Najim - KSA / Moroor
- UAE / E-Gov - Bahrain / Jif - Jordan / Yakeen - KSA / Auto Data - UAE for third party
data services (e.g., lexisnexis, iso, etc.). In addition the system is integrated to:

• ESKA Agent Portal for agent portal software and agent management systems.
• ESKA Report Builder for business intelligence systems and document creation
systems.
• ESKA Docs for document management systems.
• ESKA Business Manager for general ledger, billing systems and payments systems
(disbursements).
• ESKA WorkFlow for business process management systems.
• ESKA CRM for CRM.
• ESKA Insures - General Insurance is preintegrated supporting reinsurance solutions,
new business and underwriting, claims, product calculation engine, and distribution
management.
• ESKA Agent Portal and ESKA BMS for producer portal (quick quote, illustration, bind,
issue).

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


• ESKA Customer Portal for eapplications, prospective customer portal (quick quote,
illustration, bind, issue) and for policyholder portal (inquiries and transactions for in-
force policies).

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. They provide a set of
prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 20 people consists of resources from the insurer (30%) and ESKADENIA
(70%). Service-level agreements are offered; a typical SLA includes yearly support with
incident classifications.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

ESKADENIA offers term license, perpetual license, usage-based, SaaS, subscription,


and risk-based pricing options. The license fees are typically based on number of
functional components/modules, premium volume, and enterprise license / flat fee. The
vendor will offer a fixed price implementation for a fixed scope of work. Carriers may also
need to license the following third party software: Oracle Database License, Windows
License when applicable.

113
The total cost to implement ESKA Insures - General Insurance. can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Table 67: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million No cost, not 20%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 20%


implementation costs applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million No cost, not 20%
implementation applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €1 million to €5 million No cost, not 20%


implementation for a applicable

Chapter: ESKADENIA Software: ESKA Insures - General Insurance


European insurance
holding company

Source: Vendor

114
FADATA: INSIS

COMPANY
Fadata is a privately owned company (with outside investors) headquartered in London,
UK with sales and professional services personnel located throughout the European,
Middle Eastern, African, and Latin American regions. Fadata’s business is providing
software and services to the insurance industry. The company has approximately 250
employees, of which 90 are available to provide professional services / client support for
their PAS solution. Up to 185 dedicated professionals are physically located in Europe,
Middle East, and Africa.

The last user conference was the Fadata Community Forum, which took place May 31 to
June 1, 2017 to provide information and discussions between Fadata, its customers, and
implementation partners internationally.

Table 68: Company and Product Snapshot

COMPANY Annual corporate revenues Confidential

Year founded 1990

Exchanges/Symbols N/A

Headquarters Location Global: London, UK

PAS SYSTEM Name INSIS

Current release and date of v10.4.4 (May 2017)


release

Release intervals Minor enhancements: Quarterly to semi-annually


Major enhancements: Annually

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0),
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Midtier insurers: single business class and


composite. Expansion into Northern Europe and
select adjacent geographies

Source: Vendor RFI

CELENT OPINION
INSIS version 10 continues to be a highly configurable system with a strong
Chapter: Fadata: INSIS

implementation of a service-oriented architecture under the hood. The solution itself is


highly configurable, as the referees noted in terms of parameterisation.

INSIS is still one of just a few systems deployed in Europe, the Middle East, and Africa, a
fact that shows its flexibility both at a technical level and in working in different markets,
as well as in Asia and Latin America. INSIS support for life and health lines of business
likely appeals to composite insurers in these regions.

115
INSIS offers a web-based interface for internal users —both for use of the system and for
it’s configuration. In addition, Fadata has acquired Impeo and now offers digital portals.
The user interface is highly functional and suits expert insurance staff. This year Fadata
shared their plans for a new user interface for the INSIS platform. Celent welcomes the
investment in the system and believes existing clients and prospects will welcome this
too.

INSIS is currently mostly installed at midsize to small lients in the region, although the
company now has three tier 2 clients as well. In addition to the new ownership, new
partners and new investment are driving the Fadata offering forward.

OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is configurable using tools for an IT user; and rate analysis; which is available with
integration to a third party solution.

Figure 29: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Workflow Multi
Reporting/Analytics Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No
Chapter: Fadata: INSIS

Not available Not applicable

Source: Vendor RFI

116
CUSTOMER BASE
They have a total of 30 insurer clients. The breakdown of the clients is as follows: Tier 2
(three clients), Tier 3 (one client), Tier 4 (23 clients) and Tier 5 (three clients).

Table 69: Customer Base

EUROPE, MIDDLE EAST, In production with current 28


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 2


or more years old

New clients since 2015 Europe:


Austria 1
Finland 1

Existing client base by Europe:


country Bulgaria 5
Romania 4
Kazakhstan 2
Poland 2
Russia 2
Ukraine 2
Estonia 1
Finland 1
Greece 1
Hungary 1
Serbia 1
Slovakia 1
Sweden 1
Middle East:
United Arab Emirates 1
Africa:
Mozambique 2
Ethiopa 1
Kenya 1
Tanzania 1

Deployment method On Premise: 100%


(percentage of client base)

Marquee clients Zurich,


Groupama,
Societe Generale

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on INSIS. Two are Tier 5 insurers, and two are Tier 4
insurers. Three references have used the solution for more than 3 years, one for 1 to 3
years. One reference is using the solution for all or mostly personal lines, one for all or
most commercial and two references for a mix of both. One reference also uses the
solution for workers’ compensation and specialty lines. All references were from EMEA.

In terms of the best things about the vendor, references noted local support offices as a
Chapter: Fadata: INSIS

plus. The references had more to say about the solution, valuing the system architecture
that allows change in processes without adapting main code, parameterization of product
options, and the data model.

In terms of areas for improvement one reference called for more documentation of the
system and principles around its implementation. One reference sought improvements in
performance.

117
Functionality received above average scores overall, and within functionality policy
service processing received the highest score, while portals for agents and brokers was
an area in need of improvement. Configurability scores were above average, and within
configurability products (design and maintenance) received the highest score. Comments
on the integration were above average, and within integration your claim system(s)
received the highest score. Regarding their technology experiences, insurers gave above
average marks, and within technology scalability of the solution received the highest
score. The implementation was rated above average overall, and within implementation,
implementation completed on time received the highest score. Finally, support received
above average scores, and within support knowledge of their solution and relevant
technology received the highest score.

Figure 30: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.45

Support Configurability
3.81 3.69

Implementation Integration
4.04 4.02

Technology 3.76

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 70: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 20

HOMEOWNERS In production today 17

COMMERCIAL AUTO In production today 17


Chapter: Fadata: INSIS

COMMERCIAL PROPERTY In production today 18

COMMERCIAL LIABILITY In production today 20

WORKERS COMP In production today 16

BUSINESS OWNERS POLICY In production today 12

Source: Vendor RFI

118
TECHNOLOGY
The architecture is a multi-tier Technical Architecture, based on Oracle Technology stack.
The Database tier utilizes Oracle DB both for data storage and high-performance
business logic; the Middleware tier is realized with Oracle ADF by implementing common
Data Model and Controller functionality for all INSIS modules; and the View layer
comprises several applications, covering the operational and administrative functionality
of the system. INSIS provides several standard integration interfaces, including INSIS
Web Services and INSIS File Adapter for data exchange through various file formats.
INSIS implements internal Service Bus, which isolates the logical modules of the system
and manages the communication between them.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, Windows, Blackberry, and other.

Table 71: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 60%


C++: 60%
Business users: Java: 50%
Other (PL/SQL): 50%
Developers: Java: 50%
Other (PL/SQL): 50%

OPERAX`TING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: As JEE application
based on Oracle Technology Stack INSIS can run on
any OS supported by Oracle. They have deployments
on major server OS-es, including: Linux, AIX, MS
Windows, other *nix platforms.

APPLICATION SERVERS INSIS supports Oracle Weblogic application server for


its core components, because it perfectly fits INSIS
technology and nonfunctional requirements. For some
noncore components, like INSIS Integration
interfaces, non-Oracle Application servers are
supported like Tomcat and jBoss.

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services; Other XML


Additional options: ACORD Standard XML; MQSeries,
JMS or similar queue technology; Flat files; Custom
API
Public API integrations: They have integrated JBoss
jBPM as their workflow and BPM engine

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
Chapter: Fadata: INSIS

technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

119
TECHNOLOGY SPECIFICS

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 1,500 users and 14 million


policies

Source: Vendor RFI

The data model is proprietary. The data model can be extended by carriers in a separate
schema. This extension is provided through standard INSIS APIs (INSIS Service Bus)
and configuration tools. The data model can be released to an insurer. It can be mapped
to an intermediate format.

Carriers have access to custom code created specifically for them; configuration tools
targeted to a business user are available. Changes to the system are possible through
reusable components, inheritance, and other schemes. All product components
(including product features, coverages, benefits, transactions, rules, and calculations) are
reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with LexisNexis, FATCA
for third party data services (e.g., lexisnexis, iso, etc.); SAP, Oracle eBS for general
ledger; jBOSS BPM for business process management systems; Documentum,
OpenText, Oracle BI Publisher for document management systems; Oracle eBS
Accounts Payable for payments systems (disbursements); Integration is also available for
Siebel plus others for personal data synchronization for CRM; and various others for
producer portal (quick quote, illustration, bind, issue), including from Fadata’s acquisition
of Impeo and its digital front end portal offerings.

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. They provide a set of
prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of about 12
people consists of resources from the insurer (40%), Fadata (10%), and external
professional services firms (50%). Service-level agreements are offered; a typical SLA
includes response and fixed times under the support agreement.

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

In terms of licensing, term licenses are the norm. Fadata can also offer term license,
perpetual license, usage-based, SaaS, subscription, risk-based, and other pricing
Chapter: Fadata: INSIS

options. The license fees are typically based on number of functional


components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, per transaction, the number of
policies and the number of modules used. The vendor will offer a fixed price
implementation when a flexible time and materials model is recommended. Carriers may
also need to license the following third party software: Oracle database.

120
The total cost to implement INSIS can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 72: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs US$1 million to US$5 US$1 million to US$5 Under US$500,000 20%
only: assuming a two million million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post Under US$500,000 Under US$500,000 Under US$500,000 20%
implementation costs
for the regional
insurance company.

Assuming a four year US$10 million to US$15 million to US$1 million to 20%
implementation US$15 million US$25 million US$5 million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post US$500,000 to US$500,000 to US$1 Under US$500,000 20%


implementation for a US$1,000,000 million
European insurance
holding company

Source: Vendor

Chapter: Fadata: INSIS

121
FAKTOR ZEHN AG: FAKTOR-IPM

COMPANY
Faktor Zehn is a privately owned company headquartered in Munich, Germany with sales
and professional services personnel located throughout the European and Middle
Eastern regions. Faktor Zehn’s business is providing software and services to the
insurance industry. The company has 84 employees, of which 80 are available to provide
professional services / client support for their PAS solution. Eighty-four are physically
located in Europe, Middle East, and Africa.

The last user conference was the Faktor-IPS User Group which deals as a platform for
clients to foster communication, discuss specific needs, and possible developments.

Table 73: Company and Product Snapshot

COMPANY Annual corporate revenues US $5,730,397.5

Year founded 2004

Exchanges/Symbols N/A

Headquarters Location Global: Munich, Germany

PAS SYSTEM Name Faktor-IPM

Current release and date of Faktor-IPM 2.3


release

Release intervals Minor enhancements: Every four month


Major enhancements: Twice a year

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 2.4 to version 2.7).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market All non-life LoBs, target market: DACH and NL

Source: Vendor RFI

CELENT OPINION
Faktor Zehn is an unusual vendor in the report in that they offer some of their
components as open source solutions — making it easier to trial or adopt part of the suite
Chapter: Faktor Zehn AG: Faktor-IPM

with only the development time and costs incurred. Faktor-IPM is new to this report series
and offers a strong set of functionality and is already well deployed in Germany and
neighbouring countries.

Faktor Zehn demonstrated a robust, modern Java-based application. The interface for
the operations user was a modern web-based interface with the dynamic feedback and
interactive user interface components as you would expect from a modern system. The
configuration environment is offered in a thick client interface. The configuration
environment is clear, although it leans towards a developer-friendly approach for
delivering change quickly in the system.

The suite is also seeing further development including a new claims component, Faktor-
ICS, which is under development at the time of writing.

122
Faktor Zehn is particularly well placed to support insurers who wish to part-build their
core system and par- buy. For insurers looking to buy a suite they will find a modern,
functional system in Faktor-IPM.

OVERALL FUNCTIONALITY
A moderate amount of functionality is available out of the box. Exceptions include quote,
which is available with integration to a separate module; ACORD, which could be
developed (would be considered customization); data services, which requires coding;
assignment, which could be developed (would be considered customization); ISO,
reinsurance, which could be developed (would be considered customization); and
document creation, scheduling/calendar/diary, reporting/analytics, workflow, and
multichannel/mobile, which are available with integration to a third party solution.

Figure 31: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Under Development
Chapter: Faktor Zehn AG: Faktor-IPM
Coding required
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

123
CUSTOMER BASE
They have a total of 9 insurer clients. The breakdown of the clients is as follows: Tier 1 (3
clients), Tier 2 (5 clients) and Tier 3 (one client).

Table 74: Customer Base

EUROPE, MIDDLE EAST, In production with current 9


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


Germany 3

Existing client base by Europe:


country Germany 6
Austria 2
Netherlands 1

Deployment method On Premise: 100%


(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Marquee clients 1

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on Faktor-IPM. Two references are Tier 4 insurers, one is
a Tier 2 insurer, and the last didn’t specify. Two references have been using the system
for more than 3 years, one for 1 to 3 years and the last is still implementing it. All
references are based in EMEA. One reference uses the solution for a mix of personal
and commercial lines, one for all or mostly personal lines, and the last two for all or
mostly commercial lines.

In terms of the best things about the vendor, the references valued the excellent
collaboration and the highly skilled staff. In terms of the system, references valued the
model flexibility, state of the art technology, and the fact it was open source with a
growing community.

In terms of areas for improvement references offered some mixed ideas, including
improving scalability (no further detail given) and decoupling from the Eclipse platform. In
terms of the vendor, references asked for more partners / people for implementation. One
reference suggested enhancing marketing for the model-driven approach.
Chapter: Faktor Zehn AG: Faktor-IPM

124
Functionality received above average scores overall, and within functionality document
management received the highest score while tools for managers was an area in need of
improvement. Configurability scores were above average, and within configurability,
products (design and maintenance) received the highest score, while user management
(permissions, authority) was an area in need of improvement. Comments on the
integration were above average, and within integration, integration to the reference’s
claim system(s) received the highest score. Regarding their technology experiences,
insurers gave above average marks, and within technology, configurability of the solution
received the highest score. The implementation was rated above average overall, and
within implementation knowledge of their solution and relevant technology received the
highest score. Finally, support received above average scores, and within support
knowledge of their solution and relevant technology received the highest score.

Figure 32: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.48

Support Configurability
4.41 3.91

Implementation Integration
4.35 3.88

Technology 4.38

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 75: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
Chapter: Faktor Zehn AG: Faktor-IPM
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 4

HOMEOWNERS In production today 3

COMMERCIAL AUTO In production today 3

COMMERCIAL PROPERTY In production today 2

COMMERCIAL LIABILITY In production today 1

WORKERS COMP Supported but not in production

125
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

BUSINESS OWNERS POLICY In production today 1

Source: Vendor RFI

TECHNOLOGY
The technical architecture is on a JEE/SOA architecture, which offers maximum flexibility
and fast and easy integration of components as services. The JEE/SOA architecture
allows a high degree of automation and process flexibility and makes policy management
functions available to customers and sales partners. Operational systems can be
connected very fast via an integration framework and various adapters (e.g., SAP).

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 76: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


Business users: Java: 100%
Developers: Java: 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Microsoft Windows
Server, Linux/Unix/AIX

APPLICATION SERVERS JBoss EAP, Wildfly, WebSphere

DATABASES Preferred: Oracle; DB2/UDB


Additional options: Microsoft SQL Server; Sybase;
Other SQL; other (All supported databases Eclipse
Link JPA);

INTEGRATION METHODS Preferred: RESTful HTTP style services; JSON format


Additional options: Web Services; ACORD Standard
XML; Other XML; MQSeries, JMS or similar queue
technology; Flat files; Custom API
Public API integrations: SAP for Insurance (e.g. FS-
CD)

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Chapter: Faktor Zehn AG: Faktor-IPM

Interactive UI through the use of JavaScript or similar


technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

126
TECHNOLOGY SPECIFICS

SCALABILITY Largest deployment: About 100 users and an


unlimited number of policies

Source: Vendor RFI

The data model is based on the VAA insurance model with significant enhancements. It
supports any other customer data model because of their model-driven approach. The
data model can be extended by carriers using a modeling tool based on Eclipse RCP
(Faktor-IPS). For the insurer to make changes to the data model, a set of tools is
provided that allow technical staff to extend the data model and the SQL database
schema. A reference model for several lines of business can be provided for the
customer. It can be published to an insurer’s data model and mapped to an intermediate
format.

Carriers do have access to core code; configuration tools targeted to a business user are
available for the following: insurance product definition, workflow definition, and business
rule definition. Data definition is configurable using tools targeted for an IT user. Screen
definition, interface definition, and role-based security integration require coding.
Changes to the system are possible through reusable components, inheritance, and
other schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

In Europe and Middle East the system is preintegrated with SAP FI for general ledger;
SAP FS-CD for billing systems; SAP FS-CD for payments systems (disbursements); SAP
CRM and bsi.CRM for CRM; and Faktor-IOS for producer portal (quick quote, illustration,
bind, issue).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is required only for the addition of a new
field.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 10–40 people
consists of resources from the insurer (30%), Faktor Zehn (40%), and external
professional services firms (30%). Service-level agreements are offered; a typical SLA
includes feedback within four hours for level 1 defects, feedback within eight hours for
level 2 defects, and feedback within one week for level 3 defects. The feedback during
working days will be between 9 a.m. and 5 p.m.. Additional support can be available upon
request with an individual agreement. Chapter: Faktor Zehn AG: Faktor-IPM

The average time to get the first line of insurance live in a single jurisdiction is typically 12
to 18 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

Faktor Zehn offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of functional
components/modules, premium volume, and enterprise license / flat fee. The vendor will
offer a fixed price implementation If required by customer. After an inception phase with a
clear defined scope and requirements, this can be offered. In general the vendors
believes that T&M results are cheaper for customers due to less overhead.

127
The total cost to implement Faktor-IPM can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 77: Pricing estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million No cost, not €1 million to €5 19%


only: assuming a two applicable million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 19%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million No cost, not €10 million to €15 19%
implementation applicable million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post


implementation for a
European insurance
holding company

Source: Vendor

Chapter: Faktor Zehn AG: Faktor-IPM

128
GUIDEWIRE SOFTWARE INC.: GUIDEWIRE
POLICYCENTER

COMPANY
Guidewire is a publicly traded company headquartered in Foster City, California with
sales, product development, and professional services personnel located throughout the
North American, European, Middle Eastern, and African, Asia-Pacific, and Latin
American regions. Guidewire’s business is providing software and services to the
insurance, property /casualty and workers' compensation industries. The company has
over 1,800 employees, of which there are over 700 professional service staff worldwide.
They do not provide an employee breakdown by product or region.

The annual user conference, Guidewire Connections 2017, was held November 13-16 in
Las Vegas. Connections consists of three days of best practices, customer case studies,
networking, and an entire community of Guidewire experts. These include sessions,
workshops, and roundtables that allow customers to learn and ask questions of industry
experts, team leaders, and Guidewire’s software developers. This allows for exposure to
industry leaders, both from Guidewire and from partners and consultants who have
completed the complex process of connecting new opportunities to organizations who
can take advantage of them. Clients can network with hundreds of fellow customers who
work with Guidewire products and can answer questions and present case studies on
how they have worked with the products. The general session content includes
Guidewire’s senior product management and CEO as well as outstanding keynote
speakers, customers, and partners. Clients also discover what’s new in Guidewire
InsurancePlatform, including significant advancements to Guidewire’s core, data and
analytics, and digital engagement products. There were more than 2,000 attendees at

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


this year’s conference.

In EMEA, Guidewire held its annual customer Insurance Forum in spring 2017, this year
in Paris. The event was attended by insurers from across Europe, representing business
and IT functions. It provided an opportunity for thought-leadership discussion, with a
focus on current trends in Europe, and case studies on how Guidewire customers are
leveraging technology to adapt their business. Guidewire Insurance Forum 2017 drew
115 attendees. Guidewire Insurance Forum 2018 will be held May 2018 in London.

Table 78: Company and Product Snapshot

COMPANY Annual corporate revenues $514M (FYE 2017)

Year founded 2001

Exchanges/Symbols NYSE: GWRE

Headquarters Location Global: Foster City, California

PAS SYSTEM Name Guidewire PolicyCenter®

Current release and date of PolicyCenter 9, released June 2016


release

129
Release intervals Minor enhancements: Maintenance releases are
released on an as-needed basis
Major enhancements: Approximately every 2
years

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market Size of Company: Mid- to large-size General


insurers.
Product Lines: Personal and commercial lines,
including workers' compensation.
Primary geography: Austria, Belgium, France,
Germany, Italy, Netherlands, Nordics, Poland,
Russia, Spain, Switzerland, UK

Source: Vendor RFI

CELENT OPINION
Guidewire is a long-time participant in the EMEA reports, but here we see more live
clients and a demonstration of Guidewire’s momentum with PolicyCenter in EMEA.
Guidewire continues to invest significant sums of money in their products, and
PolicyCenter is no exception.

PolicyCenter’s user interface provides business users with a high degree of usability and
easy access to information and functions. Guidewire now offers various portal
components from its digital division, all with responsive design, and are available to
agents, prospective policyholders, and policyholders.

PolicyCenter has two configuration environments: Administrator, for business analysts (or
designated business users), and Studio, a more technical environment for developers. In
Administrator, rules are built with drop-down menus. The product design environment is
becoming more business user-friendly. In Studio, developers use Guidewire’s scripting
language, Gosu. Other noteworthy features of PolicyCenter’s configuration environment
include the ability to create wizards for common workflows and a workflow graphic user

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


interface.

Guidewire has integrated their predictive analytics tool with a nice visualization of an
account’s score. Guidewire continues to invest heavily in the ecosystem of vendors that
are “Ready for Guidewire” validated with prebuilt accelerators.

In this report PolicyCenter is installed at more clients and in more countries in EMEA than
in prior years and shows more deals in the territory too. Overall, Celent views
PolicyCenter as a leading policy administration solution with a well-designed UI, broad
functionality, and a substantial and growing EMEA and global customer base.

130
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include data
services, which are configurable using tools targeted for an IT user; reinsurance, which is
available with integration to a separate module; multiple insurers (or coinsurance) and
forms management, which are configurable using tools for a business user; and
multichannel/mobile, which is available with integration to a separate module. If required,
ACORD messaging is available with integration to a third party solution.

Figure 33: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Workflow Multi-
Reporting/Analytics Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 14 insurer clients live on PolicyCenter in the region. The breakdown
of the clients is as follows: Tier 1 (one client), Tier 2 (six clients), Tier 3 (one client), Tier 4
(four clients), and Tier 5 (two clients).

Table 79: Customer Base

EUROPE, MIDDLE EAST, In production with current 10


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 4


or more years old

131
New clients since 2015 Europe:
Germany 4
Finland 3
Italy 2
United Kingdom 2
Austria 1
Belgium 1
France 1
Netherlands 1

Existing client base by Europe:


country United Kingdom 7
Germany 5
Belgium 3
Finland 3
France 2
Italy 2
Switzerland 2
Russia 1
Poland 1
Austria 1
Denmark 1
Netherlands 1
Africa:
South Africa 1

Deployment method On Premise: 86%


(percentage of client base) Single-tenant public cloud: 7%
Hybrid cloud: 7%

Marquee clients Aviva,


Basler,
Direct Line Group,
Admiral,
PZU

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Guidewire PolicyCenter. One is a Tier 5 insurer, one
is a Tier 4 insurer, and one is a Tier 2 insurer. One reference has used the solution for
less than a year, the other two for 1 to 3 years. All three references use the solution for all

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


or mostly personal lines.

References noted the best things about the system were the richness and versatility of
the solution; also one reference particularly valued the tools based on IntelliJ and the
Gosu language.

In terms of areas to improve, references commented on the underlying technology in the


system. One commented on the complex data model supporting PolicyCenter. Another
commented on ease of upgrades and making deploying change easier. In both cases
Guidewire is addressing these already in their recent releases.

Functionality received above average scores overall, and within functionality, processing
new business (mostly automated) received the highest score. Configurability scores were
above average, and within configurability products (design and maintenance) received
the highest score. Comments on the integration were above average, and within
integration, integration to the insurers claim system(s) received the highest score.
Regarding their technology experiences, insurers gave above average marks, and within
technology, vendor's level of investment in improving technical performance through new
releases and fixes received the highest score. The implementation was rated above
average overall, and within implementation knowledge of their solution and relevant
technology received the highest score. Finally, support received above average scores,

132
and within support knowledge of their solution and relevant technology received the
highest score.

Figure 34: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 4.06

Support Configurability
4.08
3.85

Implementation Integration
4.14 4.08

4.08
Technology

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 80: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


PERSONAL AUTO In production today 9

HOMEOWNERS In production today 4

COMMERCIAL AUTO In production today 3

COMMERCIAL PROPERTY In production today 3

COMMERCIAL LIABILITY In production today 1

WORKERS COMP In production today 1

BUSINESS OWNERS POLICY In production today 1

Source: Vendor RFI

TECHNOLOGY
The technical architecture is a Java application server. Each Guidewire application runs
as a standard three tier architecture with a client on the front end running a standard web
browser, an application server hosting the application, and a database storing the
content. They offer plugins and project accelerators to quickly enhance the base product.

133
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 81: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


Business users: Java: 100%
Developers: Java: 5%
Other (Customers are able to extend system business
logic using Java or Gosu (A JVM-based language).
Gosu's ECMAScript-derived syntax is very accessible
to those with experience in existing object-oriented
languages. It was purpose-built for native and
automatic integration with the application data model,
and the platform's object-relational database mapping
layer): 95%

OPERATING SYSTEMS Implemented in Java

Operating systems deployed on:


All customers are required to use a 64 bit OS, and a
64 bit JVM for production. Guidewire supports
application servers running on the following operating
systems which are also supported by the application
server vendor:
RHEL 6 or higher
SUSE/SLES 11 or higher
OEL 6 or higher
Windows 2012 or higher
AIX 7 or higher

APPLICATION SERVERS Preferred: Apache Tomcat, Red Hat JBoss EAP, IBM
WebSphere Application Server, Oracle WebLogic
Server
Additional options: Guidewire’s Platform Support
Matrix identifies recommended JRE/JDK versions for
each of the preferred application servers.

DATABASES Preferred: Oracle; Microsoft SQL Server


Additional options: None

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


INTEGRATION METHODS Preferred: Web Services
Additional options: ACORD Standard XML; Other
XML; JSON format; MQSeries, JMS or similar queue
technology; Flat files; Custom API
Public API integrations:
The mating of the application to the systems in
question is undertaken during the implementation
project using the array of flexible integration
capabilities mentioned in the PolicyCenter
Architecture attachment. In addition, customers can
make use of existing integration design
documentation or even reference starter code in the
form of Accelerators, which are available at no extra
cost via the Guidewire Customer Portal.

134
TECHNOLOGY SPECIFICS

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: Over 5,000 users and over


1,000,000 policies

Source: Vendor RFI

The data model supports the full policy lifecycle and is designed to support
straightforward extension by each customer to meet their unique business needs.
Customers are free to feed data from PolicyCenter to external systems (such as reporting
systems) that may use industry models (such as IAA) as their basis. It is not based upon
any particular third party industry model. Each Guidewire application has an extensive
base data model, supporting the complete claims, policy, and billing lifecycles.
Customers use included tooling (Guidewire Studio) to further extend the base data model
with new entities and new fields to support their unique needs. The data model can be
extended by carriers using the Guidewire Studio configuration tool. Customers never
modify the application source code for any reason. For the insurer to make changes to
the data model, a set of tools is provided that allow technical staff to extend the data
model and the SQL database schema. The data model can be released to an insurer. It
can be published to an insurer’s data model and mapped to an intermediate format.

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


Carriers do not have access to core code; a configuration tool targeted to a business user
is available for insurance product definition. Screen definition, workflow definition,
business rule definition, interface definition, and data definition are configurable using
tools targeted for an IT user. Changes to the system are possible through reusable
components, inheritance, and other schemes. All product components (including product
features, coverages, benefits, transactions, rules, and calculations) are reusable for
multiple products.

In Europe, Middle East, and Africa the system is preintegrated with Guidewire
BillingCenter for billing systems; Guidewire Reinsurance Management for reinsurance
systems and Guidewire ClaimCenter for claims.

Product rating changes can be analyzed using an impact analysis tool that provides a
report, detailing products and channels affected, and can be tested using a specific tool
provided. A restart of the system has been required for insurance product
modification/configuration, new product creation, change to underlying data model, new
web service or integration point, change to portal, business rule change, and workflow
change. However, Guidewire now supports Product Model Rolling Updates which do not
require a server restart in version 9.

135
IMPLEMENTATION, PRICING, AND SUPPORT
The preferred implementation approach is Agile. A typical project team of 12 to 50 people
consists of resources from the insurer (75%), Guidewire (25%), and external professional
services firms (25%). Service-level agreements are offered.

The average time to get the first line of insurance live in a single jurisdiction is typically 12
to 18 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

Guidewire offers term license, perpetual license, and risk-based (available for Guidewire
Live, Predictive Analytics, InsuranceNow) pricing options. The license fees are typically
based on premium volume. Carriers may also need to license the following third party
software: Third party hardware and software (i.e., application servers, database,
document management systems, etc.)

The total cost to implement Guidewire PolicyCenter can vary according to the size,
capabilities and available resources of the client, and the overall scope of system use.

Table 82: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €1 million to €5 million No cost, not 15%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 15%


implementation costs applicable
for the regional
insurance company.

Chapter: Guidewire Software Inc.: Guidewire PolicyCenter


Assuming a four year Over €25 million €5 million to €10 No cost, not 15%
implementation million applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A Under €500,000 No cost, not 15%


implementation for a applicable
European insurance
holding company

Source: Vendor

136
i2S INFORMÁTICA - SISTEMAS E SERVIÇOS S.A.: I2S NON-
LIFE

COMPANY
i2S is a privately owned company (with outside investors) headquartered in Porto,
Portugal with sales and professional services personnel located throughout the
European, Middle Eastern, and African and Latin American regions. i2S’s business is
providing software and services to the insurance industry. The company has 220
employee,s of which 180 are available to provide professional services / client support for
their PAS solution. i2S does not provide an employee breakdown by region.

The last user conference was i2S User Group ‘17.

Table 83: Company and Product Snapshot

COMPANY Annual corporate revenues US$16.58 million

Year founded 1984

Exchanges/Symbols N/A

Headquarters Location Global: Porto, Portugal

PAS SYSTEM Name i2S Non-life

Current release and date of 6.24 November 2016


release

Release intervals Minor enhancements: 2 per year


Major enhancements: 2-3 years

Upgrades Insurers must upgrade by going from one version

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


to the next sequentially (e.g., 4.0 to 5.0),
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Non-life companies, from under $100 million to


$1 billion. Implementing new product lines or
replacing old core systems. Companies who
want to develop an omnichannel operation or
who need an autonomous rules engine.

Source: Vendor RFI

CELENT OPINION
Celent is glad to see the modernization of i2S Non-life is once again as apparent this time
around as it was in the last report. i2S Non-life is a functional system that has a
significant number of products live among their clients. The solution has been deployed
on premise and as a SaaS offering in Africa, further demonstrating its flexibility.

The demonstration of i2S Non-life to Celent showed much improved and clear web-based
pages that looked like a modern, angular-based version. At the time of the demo not all of
the system had been modernized but i2S is clearly moving apace, investing and listening
to their customers.

Of particular interest is the way the vendor is modernizing without losing the configuration
capability that is at the heart of the solution. To that end a new, modern looking
configuration capability was demonstrated, built around i2S Insurance business modelling
137
language (IBML). This configuration feature may prove to be the jewel in the crown on
this system.

i2S Non-life continues to be a functional, versatile system that is seeing increased


investment and that is well suited to its target markets. The investment in the new UI is
welcomed by Celent and looks set to prepare i2S Non-life for the next few years.

OVERALL FUNCTIONALITY
Some of functionality is available out of the box. Exceptions include quote, forms
management, data services, data upload, underwriting, assignment, which are all
configurable using tools for a business user. ACORD messaging (where appropriate) is
configurable using tools for an IT user, while rate analysis is available with integration to
a third party solution, and scheduling/calendar/diary, reporting/analytics, workflow, are
available with integration to a separate module. Mobile support is on the roadmap, but
multichannel is available already.

Figure 35: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

138
CUSTOMER BASE
They have a total of 17 insurer clients. The breakdown of the clients is as follows: Tier 3
(one client), Tier 4 (three clients) and Tier 5 (13 clients).

Table 84: Customer Base

EUROPE, MIDDLE EAST, In production with current 17


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Africa:


Angola 2

Existing client base by Europe:


country Portugal 6
Spain 1
France 1
Africa:
Angola 6
Mozambique 2
Cape Verde 1

Deployment method On Premise: 66.66%


(percentage of client base)
Hosted: 33%

Marquee clients GNB Seguros,


Seguradora Internacional de Moçambique,
Caravela Seguros

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on i2S Non-life. Two are Tier 5 insurers, and one is a
Tier 4 insurer. All three references have used the system for more than three years. On
reference uses the system for all or mostly personal lines, one for all or mostly
commercial lines and the last reference for a mix of lines of business.

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


In terms of the best things about the vendor, references valued the knowledge, quality
and availability of the professionals – as well as the knowledge of the Portuguese market.
In terms of the system the references valued the ease of use of the account model and
the business rules configuration.

In terms of areas to improve one reference noted improvements to the documentation,


and one better account integration with Solvency II requirements.

Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score, while portals for
policyholders and prospects was an area in need of improvement. Configurability scores
were above average, and within configurability business rules (design and maintenance)
received the highest score, while user management (permissions, authority) was an area
in need of improvement. Comments on the integration were above average, and within
integration your financial system(s) received the highest score, while your reinsurance
system(s) was an area in need of improvement. Regarding their technology experiences,
insurers gave above average marks, and within technology scalability of the solution
received the highest score. The implementation was rated above average overall, and
within implementation knowledge of your business received the highest score. Finally,
support received above average scores, and within support responsiveness (handling of
issue resolution) received the highest score.

139
Figure 36: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.03

Support Configurability

3.96 3.29

Implementation Integration
3.81 3.54

Technology 3.39

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 85: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


PERSONAL AUTO In production today 15

HOMEOWNERS In production today 17

COMMERCIAL AUTO In production today 12

COMMERCIAL PROPERTY In production today 13

COMMERCIAL LIABILITY In production today 13

WORKERS COMP In production today 15

BUSINESS OWNERS POLICY In production today 12

Source: Vendor RFI

TECHNOLOGY
The solution’s platform is a web type graphical interface layer which provides a visual and
functional integration of all i2S solutions — Portal concept. To use this layer, the end user
just needs a browser. The primary UI for business users, developers, and configurers is
browser based. Touch screen interfaces are enabled for developers and configurers.

140
The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 86: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 50%
RPG: 50%
Business users:
Java: 50%
RPG: 50%
Developers:
Java: 50%
RPG: 50%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Linux, Windows, IBM
iSeries

APPLICATION SERVERS WebSphere

DATABASES Preferred: Microsoft SQL Server and DB2/UDB


Additional options: None

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format
Additional options: ACORD Standard XML; Other
XML; MQSeries, JMS or similar queue technology;
Flat files; Custom API

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 8,000 users and 3 million policies

Source: Vendor RFI

The data model is based on industry standards. The data model can be extended by
carriers using a total Adaptive Model that enables their customers to define new
attributes, behaviours and relationships, almost eliminating data model or code change
needs.

They also have provided a number of extension points in the data model where the
customer can store data of their choosing. For the insurer to make changes to the data
model, a number of extension points in the data model are provided where the customer
can store data of their choosing. The number of slots is limited, and the underlying
schema cannot be changed except by changing code. The data model can be released

141
to an insurer. It can be published to an insurer’s data model and mapped to an
intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, business rule definition, and
data definition. Workflow definition, interface definition and role-based security integration
are configurable using tools targeted for an IT user. Screen definition is available in i2S
Channels, but requires coding in i2S Non-life. Changes to the system are possible
through reusable components, inheritance, and other schemes. All product components
(including product features, coverages, benefits, transactions, rules, and calculations) are
reusable for multiple products.

In Europe, Middle East, and Africa, the system is preintegrated with i2S Channels for
agent portal software; i2S Channels for agent management systems; Portugal electronic
identifier for e-signature; i2S Analytics for analytics solutions; an external integration
(e.g., Microstrategy, Qlik sense) for business intelligence systems; i2S Analytics for data
warehouse; Accounting for general ledger; Integration hub for business process
management systems; i2S Non-life for reinsurance solutions; Payments for billing
systems; GISdoc and all DM CMIS-compliant systems for document management
systems; InfoPrint document management and Crystal Reports for document creation
systems; i2S Non-life for medical estimation tools; i2S Non-life for medical bill review; i2S
Payments for payments systems (disbursements); i2S Channels for illustrations; i2S Non-
life for new business and underwriting; i2S Non-life for claims; i2S Configurator for
product calculation engine; i2S Channels for distribution management; i2S Channels for
producer portal (quick quote, illustration, bind, issue); i2S Channels for prospective
customer portal (quick quote, illustration, bind, issue) and i2S Channels for policyholder
portal (inquiries and transactions for in-force policies).

Product changes can be analyzed using the configuration and development user
interface and can be tested using a specific tool provided. A restart of the system is
required for workflow change.

IMPLEMENTATION, PRICING, AND SUPPORT

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 4 to 10 people consists of resources from the insurer (20%), i2S (75%),
and external professional services firms (5%). Service-level agreements are offered; a
typical SLA is jointly defined by the client and i2S. Some examples of service levels are:
response times to incidents or requests, incident resolution times, availability of service
information (number of issues, their classification, prioritization and allocation) and
implementation of workarounds to minimize impacts on customer activity.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

i2S offers term license, perpetual license, usage-based, SaaS, subscription, and risk-
based pricing options. The license fees are typically based on number of functional
components/modules and the number of active policies. The vendor will offer a fixed
price implementation when they have a well-defined scope and after performing an onsite
CRP. Carriers may also need to license the following third party software: Database and
the OS, and IBM J2EE application server and IBM portal server.

142
The total cost to implement i2S Non-life can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 87: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million Under €500,000 20%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 20%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million €1 million to €5 20%


implementation million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A No cost, not No cost, not 20%


implementation for a applicable applicable
European insurance

Chapter: i2S Informática - Sistemas e Serviços S.A.: i2S Non-life


holding company

Source: Vendor

143
INSURANCE BUSINESS APPLICATIONS (IBA): IBSUITE

COMPANY
IBA is a privately owned (with outside investors) company headquartered in
Copenhagen, Denmark with sales and professional services personnel located
throughout the European, Middle Eastern and African regions. IBA provides software and
services solely to the insurance industry. The company has 58 employees, of which 40
are available to provide professional services / client support for their PAS solution. The
majority of staff is physically located in Europe, Middle East, and Africa.

IBA does not hold a formal annual user conference at the moment, due to their relative
size and customer base. However, they keep their customers informed and receive
regular feedback using formal methods.

Table 88: Company and Product Snapshot

COMPANY Annual corporate revenues Confidential

Year founded 2010

Exchanges/Symbols N/A

Headquarters Location Global: Copenhagen, Denmark

PAS SYSTEM Name IBSuite

Current release and date of 1.10.1.200


release

Release intervals IBSuite was released in early 2011. There have


been six major releases since then. Two major
revisions,1.6 and 1.9, introduced the dynamic
framework and the underlying architecture for
flexible production definition, scripting, ease of
integrations and a new and enhanced
calculation, validation, and process engines to

Chapter: Insurance Business Applications (IBA): IBSuite


support click 2 configure for products, rating,
validations, and processes, respectively.
IBA is increasingly moving away from its
previous concept of 2-3 major releases per year,
and towards more frequent, non-disruptive
upgrades. This means that they maintain a
rolling roadmap with a 3-12 month perspective,
and a release process that is more function and
microservice focused than version-focused. This
enables them to deploy new functionality more
rapidly and respond to market- and customer
demand even faster.

Upgrades IBA guarantees backwards-compatibility and


therefore makes sure that a given customer is
always running on the latest tested and approved
version of the software.

Target market Personal and specialty lines

Source: IBA

144
CELENT OPINION
IBSuite and IBA are new additions to the policy administration series reports. While the
solution doesn’t appear in our ABCD chart, Celent chose to write a short opinion on this
offering given its impact in the EMEA market.

While the solution is relatively new, the architecture and flexibility of the system is proving
appealing to insurers in multiple Western European countries. Clients include new
insurtech-style propositions all the way to London Market specialist insurers.

OVERALL FUNCTIONALITY
The majority of functionality is available out of the box as shown below.

Figure 37: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-

Chapter: Insurance Business Applications (IBA): IBSuite


Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: IBA

CUSTOMER BASE
They have a total of 21 insurer clients. The breakdown of the clients is as follows: Tier 3
(two clients), Tier 4 (nine clients), Tier 5 (10 clients). There is one self-insured client.

145
Table 89: Customer Base

EUROPE, MIDDLE EAST, In production with current 21


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


Denmark 3
United Kingdom 2

Existing client base by Europe:


country Denmark 12
UK 3
Italy 2
Sweden 2
Germany 1
Finland 1

Deployment method Hosted: 100%


(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Marquee clients MRDP,


MAG

Source: IBA

LINES OF BUSINESS SUPPORTED


Table 90: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 10

Chapter: Insurance Business Applications (IBA): IBSuite


HOMEOWNERS In production today 15

COMMERCIAL AUTO In production today 5

COMMERCIAL PROPERTY In production today 5

COMMERCIAL LIABILITY In production today 5

WORKERS COMP Not supported 0

BUSINESS OWNERS POLICY In production today 1

Source: IBA

146
TECHNOLOGY
The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 91: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 80%; JavaScript: 20%


Business users: Java: 60%; JavaScript: 40%
Developers: Java: 30%; JavaScript: 70%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Ubuntu

APPLICATION SERVERS 16.0 LTS

DATABASES Preferred: Oracle (only option)

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services;
Additional options: ACORD Standard XML; Other
XML; JSON format ; MQSeries, JMS or similar queue
technology; Flat files; Custom API;
Public API integrations: IBsuite are open any Public
API integration

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes

Chapter: Insurance Business Applications (IBA): IBSuite


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 1200 users and 3.4 million


policies

Source: IBA

The data model is designed from industry standards like IIF and Accord. IBSuite doesn’t
fully support any industry standards; however, data architecture has been designed to
fulfil all industry standards. The data model can be extended by carriers using IBSuite,
which provides custom tables to extend or modify features based on requirements. The
data model is not typically released to an insurer, but it can be published to an insurer’s
data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, workflow definition, and
business rule definition. Screen definition and interface definition are configurable using
tools targeted for an IT user. Data definition and role-based security integration are
configurable through a scripting language. Changes to the system are possible by
copying and pasting between products.
147
Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is required for change to the portal.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 6 people
consists of resources from the insurer (20%), IBA (40%), and external professional
services firms (40%). Service-level agreements are offered; IBA offers a service desk and
business operational support for internal users, Second-level support for client-specific
implementations (fee-based or resource allocation-based) and second-level support for
the IBSuite SaaS platform (included in the license fee). As a SaaS provider all support
services are provided by IBA.

Standard operating hours are typically normal business hours 8 a m. to 5 p.m. in EU. IBA
also offers extended services such as 24/7, higher availability etc. The Tech support
services are operated from Copenhagen and provided globally. The Service Desk and
Business operational support services are currently provided from Copenhagen,
Lithuania, Germany, and UK with a forthcoming entry into the US.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

IBA offers term license, perpetual license, SaaS, and subscription pricing options. The
license fees are typically based on premium volume, number of states or geographies,
and enterprise license / flat fee. Based on the scope of project, lines of business, and
support level and the skillset that the customer has in-house, IBA could offer a fixed
price. This would be based upon IBA’s implementation delivery mechanism.

The total cost to implement IBSuite can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 92: Pricing estimates

INSURER THIRD PARTY MAINTENANCE

Chapter: Insurance Business Applications (IBA): IBSuite


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million Under €500,000 Under €500,000 25%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A €500,000 to €1 million Under €500,000 25


implementation costs
for the regional
insurance company.

148
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Assuming a four year €5 million to €10 €1 million to €5 million €500,000 to €1 25%


implementation million million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €1 million to €5 million €500,000 to €1 25


implementation for a million
European insurance
holding company

Source: IBA

Chapter: Insurance Business Applications (IBA): IBSuite

149
ICE INSURETECH: ICE POLICY

COMPANY
ICE InsureTech Limited (ICE) is a part of the Acturis Group and headquartered in Surrey,
UK. The ICE business provides software and services to insurers, MGAs, claims
administrators, and accident management companies. The Acturis Group has
approximately 600 employees, across five countries, of who 50 work for ICE and are
available to provide professional services and client support for their ICE Policy solution.
All 50 are physically located in the EMEA region.

The last user conference was an annual customer conference which provides the
opportunity to exchange feedback from customers and for ICE to advise on new
developments and new partner companies.

Table 93: Company and Product Snapshot

COMPANY Annual corporate revenues Acturis Group - £62 million

Year founded 2002 (as IT-Freedom Ltd - acquired by Acturis


Group in 2017)

Exchanges/Symbols N/A

Headquarters Location Global: Camberley, Surrey, UK

North American HQ: n/a

European: Camberley and London, UK

PAS SYSTEM Name ICE Policy

Current release and date of Version 18.1 - January 2018


release

Release intervals Minor enhancements: 3 further releases per year


Major enhancements: 1 Major release per year

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 17.1 to version 18.1).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Any size of insurer, Third Party Administrators,


MGAs and Syndicates. Product lines include
Property, Casualty, Motor, Personal and
Commercial. ICE Policy is capable of operating
Chapter: ICE InsureTech: ICE Policy

in any country and is multilingual and


multicurrency.

Source: Vendor RFI

150
OVERALL FUNCTIONALITY
A large proportion of functionality is available out of the box. Exceptions include quote,
underwriting, assignment, renewals, endorsement, rating, ISO, multiple insurers, forms
management, and workflow, which are configurable using simple tools targeted for a
business user; document creation, which is available with integration to a third party
solution; and ACORD, which is on the roadmap.

Figure 38: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI


Chapter: ICE InsureTech: ICE Policy

CUSTOMER BASE
They have one Tier 3 client and one TPA client in the region.

Table 94: Customer Base

EUROPE, MIDDLE EAST, In production with current 2


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


United Kingdom 2

151
Existing client base by Europe:
country United Kingdom 2

Deployment method On Premise: 50%


(percentage of client base) Cloud: 50%

Percentage of clients using 0%


PAS through BPO services

Marquee clients ERS Insurance Group,


Capita Insurance Services

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 95: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1

HOMEOWNERS In production today 1

COMMERCIAL AUTO In production today 1

COMMERCIAL PROPERTY Supported but not in production

COMMERCIAL LIABILITY Supported but not in production

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Supported but not in production

Source: Vendor RFI

TECHNOLOGY
ICE has a modern, component based, enterprise architecture. The components have
been built to run independently, or as part of an integrated suite. The configuration
applications are best of breed, aimed at business users but with the ability to support
complex product hierarchies. The browser user interface technology provides a
responsive, adaptive, and rich user experience. All integration is achieved via the
Enterprise Service Bus supporting message-oriented (MQ) and web service APIs.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports mobile browser HTML5 apps.
Chapter: ICE InsureTech: ICE Policy

Table 96: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 99%


Other (Groovy): 1%
Business users: Java: 100%
Developers: Other (No coding required. Configuration
only with Workbench): 100%

152
TECHNOLOGY SPECIFICS

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Windows Server,
Linux (Centos)

APPLICATION SERVERS All deployments use Tomcat 8

DATABASES Preferred: Microsoft SQL Server; MySQL


Additional options: Oracle; DB2/UDB; Sybase

INTEGRATION METHODS Preferred: Web Services; Other XML; RESTful HTTP


style services; JSON format; MQ/JMS or similar
queue technology
Additional options: ACORD Standard XML; Flat files;
Custom API
Public API integrations: Google Maps, Bing Maps,
PCA Predict

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 700-800 users and about 2


million policies

Source: Vendor RFI

The data model is proprietary / user configurable. It can support any industry standard
data model schema. The data model can be extended by carriers through ICE
Workbench. For the insurer to make changes to the data model, XML is used directly in
the database, which allows the customer to store any data in this format. The data model
will be released to an insurer. It can be published to an insurer’s data model and mapped
to an intermediate format.
Chapter: ICE InsureTech: ICE Policy

Customers do not have access to core code; configuration tools targeted to a business
user are available for the following: insurance product definition, screen definition,
workflow definition, business rule definition, data definition, and role-based security
integration. Interface definition requires coding. Changes to the system are possible by
using inheritance to help define products.

In Europe, Middle East, and Africa the system is preintegrated with PCA Predict for
address verification; HPI, PCA Bank Account Validation, Carweb, IIL for third party data
services; ICE Version Manager for agent management systems; DocuSign for e-
signature; ICE Analytics for analytics solutions; ICE Analytics incorporating Microsoft
reporting tools and Power BI for business intelligence systems; ICE Analytics for data
warehouse; Sun Accounts, Sage for general ledger; Activiti.org for business process
management systems; Kofax Customer Communications Manager for document

153
management systems and document creation systems; PCA Predict for geocoding
solutions; ICE Claims for claims; ICE Rating and POLARIS for underwriting and price
calculation engine; ICE Digital B2B quote and buy portal for producer portal (quick quote,
illustration, bind, issue); ICE Digital B2C quote and buy portal for prospective customer
portal (quick quote, illustration, bind, issue); ICE Digital Customer portal for policyholder
portal (inquiries and transactions for in-force policies); ICE Digital for agent portal
software.

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. They provide a set of
prebuilt tests. A restart of the system is required for a change to the underlying data
model, a new web service, or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 6-12 staff
consists of resources from the insurer (35%) and ICE (65%). Service-level agreements
are offered; a typical SLA includes support services including bug fixing.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

ICE offers term license, perpetual license, usage-based, SaaS, subscription, risk-based,
and other (ROI-based) pricing options. The license fees are typically based on number of
functional components/modules, number of concurrent users, premium volume, number
of states or geographies, and per transaction. The vendor will offer a fixed price
implementation after the model office and scope and resources are agreed. Interfaces
and data migration likely to be excluded

The total cost to implement ICE Policy can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 97: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €1 million to €5 million €1 million to €5 20%


only: assuming a two million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
Chapter: ICE InsureTech: ICE Policy

business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 Under €500,000 20%


implementation costs
for the regional
insurance company.

154
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Assuming a four year €1 million to €5 million €1 million to €5 million €1 million to €5 20%


implementation million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €500,000 to €1 million €500,000 to €1 20%


implementation for a million
European insurance
holding company

Source: Vendor

Chapter: ICE InsureTech: ICE Policy

155
INSICON AB: INSICON I2I

COMPANY
Insicon AB is a privately owned (with outside investors) company headquartered in
Stockholm, Sweden with sales and professional services personnel located throughout
the European, Middle Eastern, and African region. Insicon AB’s business is providing
software and services to the insurance industry. The company has 41 employees, of
which 37 are available to provide professional services / client support for their PAS
solution. Thirty-five are physically located in Europe, Middle East, and Africa.

The last user conference was a discussion about products that are on the roadmap and
business drivers in the Nordic market.

Table 98: Company and Product Snapshot

COMPANY Annual corporate revenues 4,700,000 USD

Year founded 2009

Exchanges/Symbols N/A

Headquarters Location Global: Stockholm, Sweden

PAS SYSTEM Name Insicon i2i

Current release and date of 2.3 released in January 2017


release

Release intervals Minor enhancements: Minor releases are


released each month
Major enhancements: Major release cycles are
usually between 1 and 2 years

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
all versions.

Target market Moving to Tier 4 to 1 companies

Source: Vendor RFI

CELENT OPINION
Insicon is a vendor with strong experience across the Nordics, and i2i offers a strong
technical solution currently deployed mostly in the Swedish market. Insicon supports third
party administrators and smaller insurers.
Chapter: Insicon AB: Insicon i2i

The interface is web-based and modern. The look and feel of the system offers a
significant alternative to many others on the market. The design of the user interface is
influenced by Microsoft’s design guidelines around the use of the ribbon and will appear
familiar to Microsoft Office users. The configuration is done through the same interface in
the same style. The configuration tooling appeared easy to use.

Insicon i2i is less well deployed in the territory than in the last report, but has more client
wins again in this report. Insicon i2i is a strong policy administration tool that has
demonstrated its ability to deliver for TPAs and smaller insurers in the Nordic market.

156
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is not available; data upload, which is on the roadmap; assignment, which is not
available; and multiple insurers, which is configurable using tools for a business user.

Figure 39: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 9 insurer clients. All clients are Tier 5.
Chapter: Insicon AB: Insicon i2i

Table 99: Customer Base

EUROPE, MIDDLE EAST, In production with current 9


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


Sweden 3

Existing client base by Europe:


country Sweden 9

157
Deployment method On Premise: 90%
(percentage of client base)
Public cloud, multi- tenant: 10%

Percentage of clients using None


PAS through BPO services

Marquee clients Not provided

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Insicon i2i. All are Tier 5 insurers. One reference has
been using the system for less than a year, one for more than 3 years, and one for
between 1 and 3 years. One reference uses the system for all or mostly commercial
lines, one for all or mostly personal lines and one for a mix of the two.

In terms of the best things about the vendor references noted that the vendor staff are
nice, have great knowledge, give great support, and are getting more mature. In terms of
the system, references value the flexibility, capability, and configurability, as well as the
roadmap.

In terms of areas for improvement references cited more documentation. There were
some differences in opinion on configurability and flexibility — some wanting more
stability in the solution, and some more configurability in other areas such as compliance.

Chapter: Insicon AB: Insicon i2i

158
Functionality received average scores overall, and within functionality policy service
processing received the highest score, while portals for agents and brokers was an area
in need of improvement. Configurability scores were above average, and within
configurability user management (permissions, authority) received the highest score,
while making major changes was an area in need of improvement. Comments on the
integration were above average, and within integration your financial system(s) received
the highest score. Regarding their technology experiences, insurers gave above average
marks, and within technology flexibility of the data model received the highest score. The
implementation was rated above average overall, and within implementation,
implementation completed on time received the highest score. Finally, support received
above average scores, and within support knowledge of their solution and relevant
technology received the highest score, while work completed on budget was an area in
need of improvement.

Figure 40: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 3.00

Support Configurability
3.41 3.25

Implementation Integration
3.86
3.25

Technology 3.56

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 100: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA
Chapter: Insicon AB: Insicon i2i

PERSONAL AUTO In production today 1

HOMEOWNERS In production today 1

COMMERCIAL AUTO In production today 1

COMMERCIAL PROPERTY In production today 2

COMMERCIAL LIABILITY In production today 1

WORKERS COMP In production today 1

159
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

BUSINESS OWNERS POLICY Supported but not in production

Source: Vendor RFI

TECHNOLOGY
The technical architecture is a service-oriented architecture where all functionality is
exposed through web services. The architecture is component-based and follows a
model-driven approach — where all aspects of an insurance business can be modeled
and configured within the system. At the most high level, the system is an n-tier
architecture built on the Microsoft platform.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 101: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


C: 100%
Business users:
.NET (Silverlight/C#): 90%
Other (HTML5/Javascript): 10%
Developers:
.NET : 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows
Planned change to code base: replacing Silverlight
with HTML5/Javascript platform is in process

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services
Additional options: Other XML; JSON format ; Flat
files; Custom API

Public API integrations: Integrated with insurance


related services available mainly on Scandinavian
markets regarding reconciliation with banks
synchronization with general ledger, persons and
Chapter: Insicon AB: Insicon i2i

organization registers, vehicle register, claim register.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

160
TECHNOLOGY SPECIFICS

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: About 200 users and more than


4 million policies

Source: Vendor RFI

The data model is proprietary, with static common part and dynamically generated from
configured customer’s business. The data model can be extended by carriers when the
business configuration is changed by business users using tools for business
administration. For the insurer to make changes to the data model, a set of tools is
provided that allow technical staff to extend the data model and the SQL database
schema. The data model can be released to an insurer. It can be published to an
insurer’s data model.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, business
rule definition, interface definition, and data definition. Workflow definition is configurable
using tools targeted for an IT user. Changes to the system are possible by defining
reusable parts that can be linked together.

In Europe, Middle East, and Africa the system is preintegrated with SPAR, PAR, BisNode
for address verification; VTR, D&B for third party data services (e.g., lexisnexis, iso, etc.);
a part of the system solution for agent portal software; a part of the system solution for
analytics solutions; a part of the system solution implemented in PowerBI for business
intelligence systems; Agresso, Dynamics AX, Visma for general ledger; a part of the
system solution for business process management systems; a part of the system solution
for reinsurance solutions; a part of the system solution for billing systems; a part of the
system solution for reinsurance systems; Reporting Service, Word, Crystal Reports for
document creation systems; BGC for payments systems (disbursements); a part of the
system solution for new business and underwriting; a part of the system solution for
claims; a part of the system solution for CRM; a part of the system solution for product
calculation engine; a part of the system solution for distribution management; a part of
the system solution for producer portal (quick quote, illustration, bind, issue); a part of the
system solution for prospective customer portal (quick quote, illustration, bind, issue); and
a part of the system solution for policyholder portal (inquiries and transactions for in-force
policies).

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. A restart of the
system is not required for any changes.
Chapter: Insicon AB: Insicon i2i

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is agile. A typical project team of 10 to 15 people
consists of resources from the insurer (20%) and Insicon AB (80%). Service-level
agreements are offered; a typical SLA includes SLA response time with different error
criteria.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

161
Insicon AB offers term license, perpetual license, usage-based, risk-based, and other (for
green-field business an additional option with no enhancements in the product) pricing
options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license / flat fee, and per
transaction. Carriers may also need to license the following third party software: Microsoft
SQL Server.

The total cost to implement Insicon i2i can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 102: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million No cost, not 20%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 20%


implementation costs applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million Under €500,000 20%
implementation
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €500,000 to €1 million Under €500,000 20%


implementation for a
European insurance
holding company

Source: Vendor
Chapter: Insicon AB: Insicon i2i

162
JAVISION LTD.: INAMON

COMPANY
Javision is a privately owned company headquartered in Lightwater, Surrey, United
Kingdom with sales and professional services personnel located throughout the
European, Middle Eastern, and African region. Javision’s business is providing software
and services to the insurance industry. The company has six6 employees of which five
are available to provide professional services / client support for their PAS solution. Four
are physically located in Europe, Middle East, and Africa.

Table 103: Company and Product Snapshot

COMPANY Annual corporate revenues 0

Year founded 1993

Exchanges/Symbols N/A

Headquarters Location Global: Lightwater, Surrey, United Kingdom

PAS SYSTEM Name Inamon

Current release and date of 61 - 13/06/2017


release

Release intervals Minor enhancements: Monthly


Major enhancements: No Schedule

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
all versions.

Target market Any company with full online self-service


requirements.

Source: Vendor RFI

Chapter: Javision Ltd.: Inamon

163
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
data services, which require coding, assignment, which is configurable using tools for a
business user, rate analysis, which is configurable using tools for an IT user, and multiple
insurers, which is configurable using tools for a business user.

Figure 41: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Multi-
Workflow
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have one Tier 5 client in the region.

Table 104: Customer Base


Chapter: Javision Ltd.: Inamon

EUROPE, MIDDLE EAST, In production with current 1


AND AFRICA CUSTOMER release or any release less
BASE than four years old

Existing client base by Europe:


country United Kingdom 1

Deployment method Public cloud, single tenant: 100%


(percentage of client base)

Percentage of clients using None


PAS through BPO services

164
Marquee clients Not provided

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 105: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Supported but not in


Production

HOMEOWNERS Supported but not in


Production

COMMERCIAL AUTO Supported but not in


Production

COMMERCIAL PROPERTY Supported but not in


Production

COMMERCIAL LIABILITY Supported but not in


Production

WORKERS COMP Supported but not in


Production

BUSINESS OWNERS POLICY Supported but not in


Production

SPECIALTY – AVIATION In Production 1

Source: Vendor RFI

TECHNOLOGY
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 106: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


.Net: 90%
JavaScript: 10%
Business users:
.NET : 90%
Chapter: Javision Ltd.: Inamon

JavaScript: 10%
Developers:
.NET : 90%
JavaScript: 10%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server


Additional options: Oracle

165
TECHNOLOGY SPECIFICS

INTEGRATION METHODS Preferred: Web Services


Additional options: Other XML; RESTful HTTP style
services; JSON format ; Flat files; Custom API
Public API integrations: Google Maps, Sanction
Checks etc.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: No known limit. Online self-


service so this is end-users. No known limit of
policies.

Source: Vendor RFI

The data model is proprietary. It supports none. The data model can be extended by
carriers using tools and extensions. For the insurer to make changes to the data model, a
number of extension points in the data model are provided where the customer can store
data of their choosing. The number of slots is limited and the underlying schema cannot
be changed except by changing code. The data model will be released to an insurer.

Carriers have access to core code; configuration tools targeted to a business user are
available for the following: insurance product definition, workflow definition, business rule
definition, data definition, and role-based security integration. Screen definition and
interface definition require coding. Changes to the system are possible through reusable
components, inheritance, and other schemes. All product components (including product
features, coverages, benefits, transactions, rules, and calculations) are reusable for
multiple products.

In Europe, Middle East, and Africa the system is preintegrated with Google for address
verification and ProEx and SagePay for third party data services (e.g., lexisnexis, iso,
etc.).
Chapter: Javision Ltd.: Inamon

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools, and they
provide a set of prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of three people
consists of resources from the insurer (67%) and Javision (33%). Service-level
agreements are offered; a typical SLA includes subscription-based up times.

166
The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Javision offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of
functionalcomponents/modules, number of concurrent users, number of total or named
users, premium volume, number of states or geographies, enterprise license / flat fee,
and per transaction. The vendor will always offer a fixed price implementation.

The total cost to implement Inamon can vary according to the capabilities and available
resources of the client, and the overall scope of system use.

Table 107: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €500,000 to €1 million No cost, not 20%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not 20%


implementation costs applicable
for the regional
insurance company.

Assuming a four year €5 million to €10 €1 million to €5 million No cost, not 20%
implementation million applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €500,000 to €1 million No cost, not 20%


implementation for a applicable
European insurance
holding company

Source: Vendor
Chapter: Javision Ltd.: Inamon

167
KEYLANE: QIS POLICY MANAGEMENT

COMPANY
Keylane is a privately owned company (with outside investors) headquartered in Utrecht,
Netherlands with sales and professional services personnel located throughout Europe.
Keylane’s business is providing software and services to the insurance industry. The
company has 750 employees, of which 350 are available to provide professional services
/ client support for their Non-life PAS solution. All of them are physically located in
Europe.

The last user conference was attended by over 150 insurers/users of the solutions. All
customers are present with one or more representatives. Most of the times there is a
formal part in which Keylane presents on trends and developments in relation to the
company and the solution. There are sessions with demos and customer presentations
with use cases and best practices. At the end of the day there is a getting acquainted
section for interactions and discussions.

Keylane also holds regular User Group Workshops for the customers to identify shared
requirements and to discuss subjects that have impact on the development of QIS.
Participation is free of charge.

Table 108: Company and Product Snapshot

COMPANY Annual corporate revenues 110,223,600 USD

Year founded 2014 (former vendor Quinity was founded in


2001)

Exchanges/Symbols N/A

Headquarters Location Global: Utrecht, Netherlands

PAS SYSTEM Name QIS Policy Management

Current release and date of 2018Q1, released January 1 2018


release

Release intervals Minor enhancements: 8 times per year


Major enhancements: 4 times per year

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0). Chapter: Keylane: QIS Policy Management
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market Any insurance company in the Nordics, Benelux,


DACH or UK (or a combination of these
countries) that has at least GWP of 50 million
and runs both private and commercial lines.
A company that can profit maximally of the
flexibility and large amount of facilities in the QIS
Product Definition System and that has a large
number of distribution channels with large
volumes and a strong need of high STP numbers
and percentages.

Source: Vendor RFI

168
CELENT OPINION
Keylane continues to be a formidable force in European insurance. Feedback from
customers for its non-life solution and the vendor is once again strong for this solution, as
it has been in the last few reports. Keylane continues to offer European insurers strong
technology and functionality in the system.

The interface is clear, with a modern browser-based feel to it. Keylane has invested in the
interface since the last report, and if anything, has managed to make the screens clearer
and easier to use. Keylane supports mobile apps and has a self-service portal for
policyholders. Keylane demonstrated a modern, responsive, mobile web-based interface
to Celent. The investment in user interface has also stretched to the configuration
screens which have seen attention. The prior screens were already web-based, but some
welcome attention has improved them further.

It is good to see Keylane continue to invest in the product and the underlying technology.
Once again, Keylane continues its growth in its core markets, and Celent will watch for
greater expansion in Europe with keen interest.

Chapter: Keylane: QIS Policy Management

169
OVERALL FUNCTIONALITY
Most of the functionality below is available out of the box. Exceptions include ACORD,
which is configurable using tools for a business user; assignment, which could be
developed (would be considered customization); rate analysis, which is available with
integration to a separate module; and multiple insurers, which is on the roadmap.

Figure 42: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow
Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI


Chapter: Keylane: QIS Policy Management
CUSTOMER BASE
They have a total of 23 insurer clients. The breakdown of the clients is as follows: Tier 2
(two clients), Tier 3 (seven clients), Tier 4 (12 clients), and Tier 5 (two clients).

Table 109: Customer Base

EUROPE, MIDDLE EAST, In production with current 23


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


The Netherlands 5

170
Existing client base by Europe:
country The Netherlands 16
Belgium 2
Germany 2
Norway 2
Switzerland 1
France 1
Antilles 1

Deployment method On Premise: 40%


(percentage of client base) Hosted: 60%

Marquee clients Not provided

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on QIS Policy Management. Two are Tier 4 insurers,
and one is a Tier 2 insurer. One reference is still implementing the solution, one has been
using it for less than a year, and one for more than 3 years. Two references are using the
solution for all or mostly personal lines, and the last one for a mix of personal and
commercial lines.

In terms of the best things about the vendor, references mentioned quality with respect to
the vendor and staff. In terms of the best things about the solution, references also
mentioned quality, speed and flexibility of configuration, ease of use, and richness of the
solution.

In terms of areas to improve references mentioned reporting and analysis, and opening
up the system. In terms of the vendor, references mentioned better project management
skills and more resources with knowledge of specialist functionalities.

Chapter: Keylane: QIS Policy Management

171
Functionality received above average scores overall, and within functionality, processing
new business (mostly manual) received the highest score, while analytics was an area in
need of improvement. Configurability scores were above average, and within
configurability products (design and maintenance) received the highest score. Comments
on the integration were above average, and within integration your reinsurance system(s)
received the highest score. Regarding their technology experiences, insurers gave above
average marks, and within technology, scalability of the solution received the highest
score. The implementation was rated above average overall, and within implementation
knowledge of their solution and relevant technology received the highest score. Finally,
support received above average scores, and within support knowledge of their solution
and relevant technology received the highest score.

Figure 43: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.67

Support Configurability
4.04
4.11

Implementation Integration
4.19 4.25

Technology 4.39

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 110: Selected Lines of Business Supported

NUMBER OF CLIENTS IN Chapter: Keylane: QIS Policy Management


LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 13

HOMEOWNERS In production today 13

COMMERCIAL AUTO In production today 8

COMMERCIAL PROPERTY In production today 7

COMMERCIAL LIABILITY In production today 7

WORKERS COMP In production today 1

BUSINESS OWNERS POLICY In production today 2

Source: Vendor RFI

172
TECHNOLOGY
The technical architecture is built in Java and is fully web based. The solution supports all
common markup languages and uses JavaScript for a dynamic user interface. Integration
with content management systems and existing front end systems is easily realized. The
online software is performed on a Java enterprise application server (JEE / J2EE). Any
application server that meets the standards is applicable (e.g., Apache Tomcat, IBM
WebSphere Application Server, and BEA WebLogic). The batch software can be
performed in a default Java environment (JSE/ J2SE).

The architecture is designed to support high volumes, very large numbers of concurrent
users, and high availability. The solution supports load balancing and database
clustering.

QIS supports service-oriented architecture (SOA) principles. It therefore fits in almost


every architecture. External systems can collect data online and perform transactions via
web services. The solution can also collect data from external systems via web services
or use these to perform transactions in external systems.

In a nutshell, the system consists of the following layers: data access model layer,
multichannel business logic layer, function layer, service layer, SOAP/REST service
layer, or Job (background processes) and View layer (screens, CSS, HTML, Script).

They also have the authentication/security layers. The security layer makes sure that only
authenticated users logged on to the correct portal can access services that need
authentication. Internal security is based on OAuth principles. The security layer also
includes support against the common attacks on the Internet such as cross site request
forgery, cross site scripting, etc.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS) and Android.

Table 111: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


C++: 100%
Business users: Java: 100%
Developers: Java: 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: QIS has been Chapter: Keylane: QIS Policy Management
deployed on Unix, Linux, Windows, but can also be
deployed on OS/390 or z/OS 0r IBM i (OS/400)

APPLICATION SERVERS Websphere, Tomcat are preferred, but Jboss, Oracle


and JRun, Weblogic Server are additional options

DATABASES Preferred: Oracle; DB2/UDB


Additional options: Microsoft SQL Server; Other SQL

INTEGRATION METHODS Preferred: Web Services; Other XML; RESTful HTTP


style services; JSON format; MQSeries, JMS or
similar queue technology; Flat files
Additional options: ACORD Standard XML; Custom
API

173
TECHNOLOGY SPECIFICS

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Select an option (yes / no)

SCALABILITY Largest deployment: 20,000 users and 5,900,000


policies

Source: Vendor RFI

The data model is proprietary design by Keylane, but supports various industry
standards. It supports NA. The data model can be extended by carriers using
configurable PDS of QIS. This includes the ability to define your own data model
extensions in terms of what are called “flexible fields.” The product configurator can add
new fields on policy level, object level, coverage level, clauses, and in-screen dialogs.

Because QIS is a standard solution that should support all data requirements of their
customers, they do extend the data model when it becomes clear that data attributes are
missing in their generic model. The data model can be released to an insurer. It can be
published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following. Changes to the system are possible through reusable
components, inheritance, and other schemes. All product components (including product
features, coverages, benefits, transactions, rules, and calculations) are reusable for
multiple products.

In Europe, Middle East, and Africa the system is preintegrated with:


Chapter: Keylane: QIS Policy Management
• TNT/Cendris Dutch postalcodes, Postcode Anywhere services (UK).
Swiss/Belgian/German Post postalcode, Norwegian population register (DSF) for
address verification.
• Fraud detection (FISH, FRISS, RSR(Belgium)), Dutch Chamber of Commerce, Car
registration (ABZ, Audascan, BGWF ), Broker platforms (Meetingpoint, Aplaza) for
third party data services (e.g., lexisnexis, iso, etc.).
• Google Analytics for analytics solutions.
• BIRT for business intelligence systems.
• Coda, Generic XML exports (XSLT per target system) for general ledger.
• via a standard web services for business process management systems.
• integrated as well by interfaces to AIA ITP, MS Word (via Webdav) for document
creation systems.
• SCS Herstel, Audaflow, Informex (Belgium) for supplier networks and portals.

174
• Google maps for geo coding solutions.
• Coda and integrated QIS module (QIS-CD) for payments systems (disbursements).
• an online channel on which customers can apply for policies for eapplications.
• Keylane's module or from other providers for new business and underwriting.
• Salesforce, Siebel etc. for CRM.
• integrated into the policy Admin Module for distribution management.
• integrated QIS module for agent portal software, agent management systems, e-
signature, data warehouse, reinsurance solutions, billing systems, document
management systems.
• integrated QIS module as well as by interfaces to specific external claim services
applications for claims.
• integrated QIS module for product configuration and premium calculation for product
calculation engine.
• Keylane portal wizards for producer portal (quick quote, illustration, bind, issue),
Keylane portal wizards for prospective customer portal (quick quote, illustration, bind,
issue) and Keylane portal wizards for policyholder portal (inquiries and transactions
for in-force policies).

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. They provide a set of
prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 5 to 10 people consists of resources from the insurer (40%), Keylane
(50%), and external professional services firms (10%). Service-level agreements are
offered; a typical SLA includes description of roles, processes, and procedures and all
kinds of service levels in relation to topics as availability, maintenance, releases, etc.
Keylane is increasingly offering a model with more involvement from system integrators
and partners.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Keylane offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of functional
components/modules, premium volume, number of states or geographies, enterprise Chapter: Keylane: QIS Policy Management
license / flat fee, and other. The vendor may offer a fixed price implementation.

The total cost to implement QIS Policy Management can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

175
MAJESCO LTD.: MAJESCO POLICY FOR P&C

COMPANY
Majesco is a publicly traded company headquartered in Morristown, NJ, US with sales
and professional services personnel located throughout the North American region.
Majesco’s business is providing software and services to the insurance industry. The
company has over 2,200 total employees, of which over 1,200 are available to provide
professional services / client support for their PAS solution; 200 work for Europe, Middle
East, and Africa.

The last user conference was Convergence.

Table 112: Company and Product Snapshot

COMPANY Annual corporate revenues US$121.8

Year founded 1992

Exchanges/Symbols Majesco (NYSE MKT : MJCO)

Headquarters Location Global: Morristown, NJ, USA

PAS SYSTEM Name Majesco Policy for P&C

Current release and date of v10 October 2017


release

Release intervals Minor enhancements: Minor releases are


quarterly.
Major enhancements: Major releases of the
product are offered in a span of 2-3 years.

Upgrades Vendor support for prior versions: They support


current versions and up to two prior.

Target market All tiers of insurers and MGAs.

Source: Vendor RFI

Chapter: Majesco Ltd.: Majesco Policy for P&C

176
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include data
services, reinsurance, and rate analysis, which are available with integration to a third
party solution.

Figure 44: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Chapter: Majesco Ltd.: Majesco Policy for P&C


Source: Vendor RFI

CUSTOMER BASE
There is 1 MGA in production.

Table 113: Customer Base

EUROPE, MIDDLE EAST, In production with current 1


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


United Kingdom 1

Existing client base by Europe:


country United Kingdom 1

Deployment method Public cloud, single tenant: 100%


(percentage of client base)

177
Percentage of clients using 0%
PAS through BPO services

Marquee clients Glemham Underwriting

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 114: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Supported but not in


production

HOMEOWNERS Supported but not in


production

COMMERCIAL AUTO Supported but not in


production

COMMERCIAL PROPERTY In production today 1

COMMERCIAL LIABILITY In production today 1

WORKERS COMP In production today 1

BUSINESS OWNERS POLICY In production today 1

Source: Vendor RFI

TECHNOLOGY
The technical architecture is a Model Driven Architecture to provide a solution via
Configuration Toolsets for both businesses functionally and technology. Majesco Policy is
based on Java/J2EE technology stack.

The presentation layer is a true thin client that runs on all leading web browsers without
any browser plug-ins and is built using Web 2.0 technologies. The middle tier hosts the
application within application servers and includes the flexibility to support clustering for

Chapter: Majesco Ltd.: Majesco Policy for P&C


horizontal scalability. All data resides on the database server within a single database.

The application architecture across each of their core systems is layered to ensure the
separation of concerns (change in one layer does not cause a ripple effect). Each layer
(UI and Business services) communicates over well-defined APIs (XML and REST
based). All the layers use a common set of cross-cutting logic (Logging, Authentication
etc.) across the application layers. Also, underlying the core system is a common way to
handle tasks, workflows etc. which again integrates with each of the core applications
over well-defined APIs.

178
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 115: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 50%
Metadata driven using configuration engine and some
PL SQL: 50%
Business users:
Metadata driven using configuration engine and some
PL SQL: 100%
Developers:
Metadata driven using configuration engine and some
PL SQL: 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Majesco Policy
supports flavors of Windows, Linux and Unix. Listed
below are operating systems on which Majesco Policy
has been successfully tested with deployment:
• IBM AIX 7.X
• Red Hat Linux AS 6.X , 7.X
• Windows Server 2012 and above

APPLICATION SERVERS Majesco Policy can be hosted on any J2EE compliant


application servers of open source or commercial
categories. Listed below are some of the application
server that have tested the Majesco Policy.
• IBM WebSphere 8.x
• Red-hat JBOSS EAP 7.x
• Oracle Application Server 11g

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format;
MQSeries, JMS or similar queue technology; Flat files;
Custom API
Public API integrations: Yes

Chapter: Majesco Ltd.: Majesco Policy for P&C


BUSINESS USER UI Main UI browser based: Yes
All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

179
TECHNOLOGY SPECIFICS

SCALABILITY Largest deployment: Around 1,200 users and Around


45,000 policies

Source: Vendor RFI

The data model is a Transactional and Enterprise Data warehouse, which is


complemented by a set of integration interfaces to work with industry-adopted data
models.

For the core system data model, Majesco has created a data model marrying the best of
the metadata and relational database-driven approach. This new approach provides
product and rules development flexibility using the metadata model, while promoting
scalability and performance using a transactional data model using relational database.
The additional benefits include a framework-based approach that helps speed up product
development, a high degree of reusability and consistency across products, automatic
extension of relational data model from metadata changes, automatic generation of user
interface from product metadata, relational access to data, declarative data integrity, and
support of complex insurance products.

It has some similarities between the ACORD and OMG data models, but there was no
objective to make the models compliant to either. The focus was on P&C lifecycle
coverage. The data model can be extended by carriers using the Majesco Configuration
Toolset. The toolset supports automatic data and object model management and
separation of base and custom content media. For the insurer to make changes to the
data model, a set of tools is provided that allow technical staff to extend the data model
and the SQL database schema. The data model can be released to an insurer. It can be
published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, business rule definition, and
role-based security integration. Screen definition, workflow definition, interface definition,
and data definition are configurable using tools targeted for an IT user. Changes to the
system are possible by using inheritance to help define products.

In Europe, Middle East, and Africa, the system is pre-integrated with PB Spectrum for
address verification; ISO for third party data services (e.g., lexisnexis, iso, etc.); DropIn,
Elafris, Splice and eGain are additional integrated partners; Majesco Digital1st Connect
for agent portal software; Majesco Business Analytics for analytics solutions; Majesco

Chapter: Majesco Ltd.: Majesco Policy for P&C


Business Analytics for business intelligence systems; Majesco Enterprise Data Model
and Data Warehouse for data mastery, master data management tools and data
warehouse; Majesco Billing for billing systems; Pitney Bowes for document management
systems; Pitney Bowes Spectrum for geocoding solutions; Majesco Claims for claims;
Majesco Distribution Management for distribution management; Majesco Digital1st for
producer portal (quick quote, illustration, bind, issue), prospective customer portal (quick
quote, illustration, bind, issue), and for policyholder portal (inquiries and transactions for
in-force policies).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested using a specific tool provided. A restart of the system
is required for screen configuration or change to underlying data model.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 10 to 12 people
consists of resources from Majesco (100%). Service-level agreements are offered. The
average time to get the first line of insurance live in a single jurisdiction is typically 4 to 6

180
months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 2 to 4 months.

Majesco offers term license, usage-based, SaaS, subscription, and risk-based pricing
options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, number of states or geographies, enterprise license / flat fee, per
transaction, and other usage-based factors.

The total cost to implement Majesco Policy for P&C can vary according to the capabilities
and available resources of the client, and the overall scope of system use.

Table 116: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs GBP 500,000 to GBP GBP 1 million to GBP GBP 500,000 to Included in annual
only: assuming a two 1 million 5 million GBP 1 million license fee
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not Included in annual
implementation costs applicable applicable license fee
for the regional
insurance company.

Assuming a four year GBP 1 million to GBP GBP 5 million to GBP No cost, not Included in annual
implementation 5 million 10 million applicable license fee
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

Chapter: Majesco Ltd.: Majesco Policy for P&C


One year post N/A No cost, not No cost, not Included in annual
implementation for a applicable applicable license fee
European insurance
holding company

Source: Vendor

181
MARKIT SYSTEMS LIMITED: MARKIT - DA (DELEGATED
AUTHORITY)

COMPANY
Markit Systems is a privately owned company (with outside investors) headquartered in
London with sales and professional services personnel located throughout the European,
Middle Eastern, and African region. Markit Systems’s business is providing software and
services to the insurance industry. The company has 50 employees, of which 12 are
available to provide professional services / client support for their PAS solution. Twelve
are physically located in Europe, Middle East, and Africa.

The last user conference was an informal gathering of key users to gather feedback.

Table 117: Company and Product Snapshot

COMPANY Annual corporate revenues £2m

Year founded 2014

Exchanges/Symbols -

Headquarters Location Global: London, United Kingdom

PAS SYSTEM Name Markit - DA ( Delegated Authority)

Current release and date of Markit Core© 2.0


release

Release intervals Minor enhancements: Monthly


Major enhancements: Quartley

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


Upgrades Insurers can skip multiple versions (e.g., go
directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
all versions.

Target market All delegated authorities

Source: Vendor RFI

CELENT OPINION
Markit Systems Markit – DA is one of a new crop of core systems aimed at the agility
required by the MGA market. Markit Systems moved swiftly and is building on their client
base with new live clients in the UK MGA and delegated authority market, as well as in
South Africa — with strong feedback from their clients.

The system itself is web-based and offers a modern, simple user interface. The UI is
focused on helping the system user navigate policy and risk details quickly. Most screens
feature navigation tabs, and some have a sidebar that allows access to different system
areas. Configuration is done through the same interface; this feels intuitive and well
suited to Markit Systems’s target market. Some features in white-labeling or
multibranding the solution were also demonstrated to Celent. Overall the solution already
feels rich with functionality.

Markit MGA is still relatively new, is already receiving strong feedback, seeing growth,
and now present in multiple countries.

182
OVERALL FUNCTIONALITY
The full suite is integrated to the policy administration system. Any part of the system can
be configured through PHP scripting, with the exception of Underwriter Assignment and
ISO.

Figure 45: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow
Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 10 insurer clients. The breakdown of the clients is as follows: Tier 3
(one client), Tier 4 (one client), and Tier 5 (eight clients).

Table 118: Customer Base

EUROPE, MIDDLE EAST, In production with current 10


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


United Kingdom 7
Africa:
South Africa 1

183
Existing client base by Europe:
country United Kingdom 7
Africa:
South Africa 1

Deployment method Hosted: 100%


(percentage of client base)
Other: 0%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Horizon Underwriting Limited, Stonehatch


Risk Solutions Limited, Infiniti Insurance
Limited

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on Markit - DA (Delegated Authority). All four are Tier 5
insurers. All three use the solution for a mix of personal and commercial lines. One
reference has been using the solution for less than 1 year, and the other three for
between 1 and 3 years. All four were from the EMEA region, albeit one is an insurance
specialist with business in North America.

Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score. Configurability scores were
above average, and within configurability user management (permissions, authority)
received the highest score. Comments on the integration were above average, and within
integration external data sources received the highest score. Regarding their technology
experiences, insurers gave above average marks, and within technology scalability of the
solution received the highest score. Finally, the implementation was rated above average
overall, and within implementation responsiveness (handling of issue resolution) received
the highest score. And finally, support received above average scores, and within support

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


work completed on budget received the highest score.

Regarding the best things about the system, references noted ease use and speed of
user experience, as well as scalability. Regarding the vendor, references noted the
accessibility of the team and key decision-makers as well as what one referred to as
“commerciality.”

184
Regarding areas to improve there were a number of suggestions around functional areas
including accounting set up, handling of direct debit cash handling, improvement to
bordereaux production, and communication with A&S systems. Celent expects this sort of
feedback in a relatively young system, and note that this was requested in the second
half of 2017. One reference noted some types of changes across different modules were
more difficult; while this is broadly true of all policy administration systems, prospects
may value a discussion on this point.

Overall, the feedback is strong.

Figure 46: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 4.10

Support Configurability
4.32
4.22

Implementation Integration
4.39 3.72

Technology 4.54

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 119: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1

HOMEOWNERS In production today 3

COMMERCIAL AUTO Not supported

COMMERCIAL PROPERTY In production today 2

COMMERCIAL LIABILITY In production today 3

WORKERS COMP Not supported

BUSINESS OWNERS POLICY In production today 2

Source: Vendor RFI

185
TECHNOLOGY
The architecture follows a principle of at least pairs of each physical machine to achieve
HA through complete redundancy. The entire installed base runs on Linux-based
technologies and is largely virtualised.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 120: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


JavaScript: 5%
Other - PHP: 95%
Business users:
JavaScript: 5%
Other - PHP: 95%
Developers:
JavaScript: 5%
Other - PHP: 95%

OPERATING SYSTEMS Implemented in PHP Stack


Operating systems deployed on: Linux

APPLICATION SERVERS None / PHP

DATABASES Preferred: None


Additional options: None

INTEGRATION METHODS Preferred: Web Services;


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format ;
Flat files; Custom API;
Public API integrations: Google Maps, Facebook,

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


Twitter

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 500 users and 10,000 policies

Source: Vendor RFI

The data model is a standard relational data model. The data model is typically not
extended by carriers. The data model could be released to an insurer or customer.

186
Carriers do not have access to core code; Business rule definition and role-based
security integration are configurable using tools targeted for an IT user. Insurance
product definition, screen definition, workflow definition, interface definition, and data
definition are configurable through a scripting language. Changes to the system are
possible through reusable components, inheritance, and other schemes. All product
components (including product features, coverages, benefits, transactions, rules, and
calculations) are reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with services for: address
verification; third party data services (e.g., lexisnexis, iso, etc.); e-signature; data
warehouse; billing systems; document management systems; document creation
systems; geocoding solutions; payments systems (disbursements); new business and
underwriting; claims; CRM; product calculation engines; distribution management;
producer portal (quick quote, illustration, bind, issue); prospective customer portal (quick
quote, illustration, bind, issue); policyholder portal (inquiries and transactions for in-force
policies)/

A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Hybrid of Waterfall and Agile. A typical project
team of eight people consists of resources from the insurer (25%) and Markit Systems
(75%). Service-level agreements are offered.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Markit Systems offers usage-based, SaaS, subscription, and other (SaaS plus a
percentage based on profitability [PC]) pricing options. The license fees are typically
based on premium volume. The vendor will offer a fixed price, based on business

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)


requirements.

The total cost to implement Markit - DA (Delegated Authority) can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Table 121: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs No cost, not Under €500,000 No cost, not 20%


only: assuming a two applicable applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A €1 million to €5 million No cost, not 20%


implementation costs applicable
for the regional
insurance company.

187
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Assuming a four year No cost, not €500,000 to €1 million No cost, not 20%
implementation applicable applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €1 million to €5 million No cost, not 20%


implementation for a applicable
European insurance
holding company

Source: Vendor

Chapter: Markit Systems Limited: Markit - DA (Delegated Authority)

188
MSG SYSTEMS AG (MSG GROUP): MSG.PIA (PRIMARY
INSURANCE APPLICATION)

COMPANY
msg is a privately owned company headquartered in Munich, Bavaria, Germany with
sales and professional services personnel located throughout the North American,
European, Middle Eastern, and African, Asia–Pacific, and Latin American regions. msg’s
business is providing software and services to the insurance, automotive, financial
services, telecommunications and media, public sector, life science & healthcare, travel &
logistics, utilities, food industries. The company has over 6,000 employees of which over
200 are available to provide professional services / client support for their PAS solution;
200 are physically located in Europe, Middle East, and Africa.

The last user conference was the msg.PIA user group, which is a yearly event, where the
product provider gives the status and presents the future roadmap. Also, the customers
exchange their requirements and discuss the user experience.

Table 122: Company and Product Snapshot

COMPANY Annual corporate revenues USD $852 Million

Year founded 1980

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)


Exchanges/Symbols N/A

Headquarters Location Global: Munich, Bavaria, Germany

PAS SYSTEM Name msg.PIA (Primary Insurance Application)

Current release and date of msg.PIA 7.1, released December 2016


release

Release intervals Minor enhancements: 2 per year


Major enhancements: Every 2 – 3 years

Upgrades Insurers can skip one version (e.g., go from


version 4.0 to 6.0),
Vendor support for prior versions: They support
all versions.

Target market Primary insurance, all LoBs, small and midsize


companies or single LoBs for large companies.

Source: Vendor RFI

189
OVERALL FUNCTIONALITY
Most of the functionality is available out of the box. Exceptions include quote, ACORD,
data services, data upload, and assignment, which require coding. Document
management, creation, reporting and analytics, and workflow are available through third
party solutions.

Figure 47: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)


Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 19 insurer clients. The breakdown of the clients is as follows: Tier 4
(six clients) and Tier 5 (13 clients). There are three self-insureds.

Table 123: Customer Base

EUROPE, MIDDLE EAST, In production with current 19


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 None

190
Existing client base by Europe:
country Germany 5
Austria 3
Greece 2
Switzerland 3
Belgium 1
Czech Republic 1
Hungary 1
Iceland 1
Italy 1
Portugal 1
Romania 1
Russia 1
Slovakia 1
Slovenia 1

Deployment method On Premise: 75%


(percentage of client base)
Hosted: 25%

Percentage of clients using 0%


PAS through BPO services

Marquee clients

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 124: Selected Lines of Business Supported

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)


NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 14

HOMEOWNERS In production today 17

COMMERCIAL AUTO In production today 13

COMMERCIAL PROPERTY In production today 12

COMMERCIAL LIABILITY In production today 12

WORKERS COMP Not supported

BUSINESS OWNERS POLICY In production today 12

Source: Vendor RFI

TECHNOLOGY
The technical architecture is based on SAP Netweaver technology and as such leverages
SAP investments. .

The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 125: Technology Options

TECHNOLOGY SPECIFICS

191
TECHNOLOGY SPECIFICS

CODE BASE Core technology:


SAP Netweaver, ABAP and ABAP Objects: 100%
Business users:
ABAP and ABAP Objects, SAP WebDynpro,
SAP UI5: 100%
Developers:
ABAP and ABAP Objects: 100%

OPERATING SYSTEMS Implemented in SAP Netweaver


Operating systems deployed on: msg.PIA is an
application on basis of SAP NetWeaver and therefore
supports all SAP-licensed operating systems.

APPLICATION SERVERS SAP Netweaver

DATABASES Preferred: SAP NetWeaver supported databases

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format ;
MQSeries, JMS or similar queue technology; Flat files;
Custom API
Public API integrations: None

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: No
Main UI thick client based: No

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)


Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 400 users and 700,000 policies

Source: Vendor RFI

The data model is based on the ICIS data model. It supports the ICIS data model. The
data model can be extended by carriers using SAP transaction and tools as part of the
standard code. Insurers can make changes to the data model by using the SAP Standard
Appends for unlimited extensions. The data model can be released to an insurer. It can
be published to an insurer’s data model and mapped to an intermediate format.

Carriers have access to core code; configuration tools targeted to a business user are
available for the following: insurance product definition and business rule definition.
Screen definition, workflow definition, data definition, and role-based security integration
are configurable using tools targeted for an IT user. Interface definition requires coding.
Changes to the system are possible by defining reusable parts that can be linked
together.

In Europe, Middle East, and Africa, the system is preintegrated with SAP FI for general
ledger and SAP BPM for business process management systems.

192
A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The implementation approach is chosen based on the project scope and customer know-
how. A typical project team of 6 to 10 people consists of resources from the insurer
(50%), msg (40%), and external professional services firms (10%).

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

msg offers perpetual license, SaaS, and subscription pricing options. The license fees
are typically based on number of total or named users, premium volume, enterprise
license / flat fee, and the number of policies. The vendor will offer a fixed price
implementation after a detailed blue print phase, where the expected project scope is
agreed with the customer. Carriers may also need to license the following third party
software: SAP ERP NetWeaver License.

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)

193
The total cost to implement msg.PIA (Primary Insurance Application) can vary according
to the capabilities and available resources of the client, and the overall scope of system
use.

Table 126: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €1 million to €5 million No cost, not 17%


only: assuming a two applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 17%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €5 million to €10 No cost, not 17%
implementation million applicable
period, for a
European insurance
holding company,
which has four
companies, writes in

Chapter: msg systems ag (msg group): msg.PIA (Primary Insurance Application)


five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A No cost, not No cost, not 17%


implementation for a applicable applicable
European insurance
holding company

Source: Vendor

194
OCEANWIDE CANADA, INC.: BRIDGE INSURANCE
SOFTWARE SUITE

COMPANY
Oceanwide, an Insurity Company, is a privately owned company (with outside investors)
headquartered in Montreal, Quebec, Canada with sales and professional services
personnel located throughout the North American, European, Middle Eastern, and African
regions. Oceanwide’s business is providing software and services to the insurance
industry. The company has over 230 employees, of which over 100 are available to
provide professional services / client support for their PAS solution; 20 are physically
located in EMEA.

The last user conference was Connected, an annual event which includes business and
technical sessions on their solutions; informative sessions on the hottest industry topics;
and networking opportunities for customers. The event also includes Insurity, SIMS
Claims, Tropics, an Insurity Company, and Valen, an Insurity Company, all of which will
be rebranded under a single corporate designation in 2018.

Table 127: Company and Product Snapshot

COMPANY Annual corporate revenues US$100M-250M

Year founded 1996

Exchanges/Symbols N/A

Headquarters Location Global: Montreal, Quebec, Canada

PAS SYSTEM Name Bridge Insurance Software Suite

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite


Current release and date of 1.0.103.064 / December 2017
release

Release intervals Minor enhancements: 11 times a year


Major enhancements: 4 times a year (quarterly)

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Targeted Segments include Tier 2, 3, 4, and 5


Carriers, Specialty Line/Niche Insurers, MGAs,
Regional Carriers and Brokers as an enterprise
solution. Tier 1 firms are targets as a tactical
solution.

Source: Vendor RFI

195
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include quote,
ACORD, assignment, reinsurance, multiple insurers, and workflow, which are
configurable using simple tools targeted for a business user. ISO is available through an
existing integration with Policy Decisions, an Insurity asset.

Figure 48: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Multi-
Reporting/Analytics Workflow
Channel/Mobile

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite


Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of six insurer clients. The breakdown of the clients is as follows: Tier 1
(four clients) and Tier 3 (two clients).

Table 128: Customer Base

EUROPE, MIDDLE EAST, In production with current 8


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 2

196
Existing client base by Europe:
country United Kingdom 5
Germany 1
Switzerland 1
Norway 1

Deployment method Hosted: 100%


(percentage of client base)
SaaS: 100%

Percentage of clients using 0%


PAS through BPO services

Marquee clients AIG,


Willis Towers Watson

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 129: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Supported but not in production

HOMEOWNERS Supported but not in production

COMMERCIAL AUTO Supported but not in production

COMMERCIAL PROPERTY In production today 1

COMMERCIAL LIABILITY Supported but not in production

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite


WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Supported but not in production

SPECIALTY (MARINE CARGO) In production today 4

SPECIALTY (TRADE CREDIT) In production today 1

SPECIALTY (FINANCIAL LINES) In production today 2

OTHER (YACHT) In production today 1

OTHER (ENERGY) In production today 1

OTHER (SURETY) In production today 1

OTHER (EMPLOYERS LIABILITY) In production today 1

OTHER (PROFESSIONAL INDEMNITY) In production today 1

Source: Vendor RFI

TECHNOLOGY
Oceanwide’s products are based on the Microsoft family of software development tools.
The preferred development environment is Visual Studio .NET 4. Web pages are
developed with HTML/DHTML, Javascript/JQuery/AJAX, and/or Active Server Pages
(ASPX) technology. Application components are built using C# and organized into shared
libraries used in web pages and/or .NET web services. Database development is based

197
on SQL Server 2012, where stored procedures are written. Databases are accessed
using a combination of Microsoft Entity Framework and ADO.Net. Communication
between software tiers is also initiated in XML, which is found throughout the application.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 130: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: .NET (c#, ASP.net): 100%


Business users: .NET (c#, ASP.net): 100%
Developers:
There is no additional coding/programming that is
required for insurer's staff to do configuration.

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Windows Server
Standard and Enterprise 2008 R2, 2012 R2 and 2014.

APPLICATION SERVERS Run heavy processing under a throttled queuing


mechanism to ensure the database tier is not
overloaded and are also used to run scheduled
processing. This delegation ensures web servers
remain unaffected.

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format ;
MQSeries, JMS or similar queue technology; Flat files;
Custom API
Public API integrations: Google Maps, Bing Maps

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite


BUSINESS USER UI Main UI browser based: Yes
All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


API management supports local or global standards
such as ACORD application creation and rendering.
Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: Over 200,000 policies

Source: Vendor RFI

The data model is proprietary. It supports ACORD. The data model can be extended by
carriers using self-service configuration tools available in the system. For the insurer to
make changes to the data model, XML is used directly in the database, which allows the

198
customer to store any data in this format. The data model can be released to an insurer.
It can be published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, interface definition, data definition, and role-based
security integration. Changes to the system are possible by defining reusable parts that
can be linked together.

In Europe, Middle East, and Africa the system is preintegrated with Google, Bing for
address verification; LexisNexis Bridger for third party data services; Bridge (own system)
for agent portal software, agent management systems, general ledger, billing systems,
document management system, document creation systems, new business and
underwriting, claims, product calculation engine, producer portal, prospective customer
portal, and policyholder portal; Vasco eSignLive for e-signature; IBM Cognos for business
intelligence systems and data warehouse; and Cybersource and Stripe for payment
processing (disbursements).

Product changes can be analyzed using an impact analysis tool that provides a report,
detailing products and channels affected, and can be tested using a specific tool with a
set of prebuilt tests. A restart of the system is required for new web service or integration
point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Iterative. A typical project team of 4-6 people
can consist of resources from the insurer, Oceanwide, and external professional services
firms both onshore and offshore Service-level agreements are offered; a typical SLA
includes availability and performance with credits for non-performance.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite


required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

Oceanwide offers usage-based, SaaS, subscription, and risk-based pricing options. The
license fees are typically based on number of functional components/modules, premium
volume, number of states or geographies, and enterprise license / flat fee. The vendor
will offer a fixed price implementation subject to confirmed requirements. Carriers may
also need to license the following third party software: ISO, ACORD content, third party
services as needed (Cybersource, Stripe, RMS, Lexis Nexis, Corelogic, etc.).

The total cost to implement Bridge Insurance Software Suite can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Table 131: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs US$250,000 to US$1 million to US$5 No cost, not Subscription fees
only: assuming a two US$500 000 million applicable include
year project for a maintenance
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

199
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A Under US$500,000 No cost, not 100%


implementation costs applicable
for the regional
insurance company.

Assuming a four year US$1 million to US$5 US$5 million to No cost, not Subscription fees
implementation million US$10 million applicable include
period, for a maintenance
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A US$1 million to US$ 2 No cost, not 100%
implementation for a million applicable
European insurance
holding company

Source: Vendor

Chapter: Oceanwide Canada, Inc.: Bridge Insurance Software Suite

200
PRIMA SOLUTIONS: PRIMA INSURE

COMPANY
Prima Solutions is a privately owned company headquartered in Paris, France with sales
and professional services personnel located throughout the North American, European,
Middle Eastern, and African, and Asia-Pacific regions. Prima Solutions’ business is
providing software and services to the insurance industry. The company has 250
employees, of which 200 are available to provide professional services / client support for
their PAS solution; 200 are physically located in Europe, Middle East, and Africa.

Since writing this profile, Prima Solutions has acquired a predictive analytics solution now
marketed as Prima Analytics, giving the company new customers across Europe, Middle
East, Africa and Asia beyond those already using Prima Insure.

The last user conference was an event dedicated to customers to present the latest
developments, the latest features and to share customers’ needs for preparing the next
version.

Table 132: Company and Product Snapshot

COMPANY Annual corporate revenues 2016: US$16 million and forecasted annual
revenue for 2017: US$23 million

Year founded 2000

Exchanges/Symbols N/A

Headquarters Location Global: Paris, France

PAS SYSTEM Name Prima Insure

Current release and date of 8.2 - Q3 2017


release

Release intervals Minor enhancements: usually every 6 months


Major enhancements: usually every 24 months

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0)
Vendor support for prior versions:

Target market Mid size (above €100 million premium) to large


companies, only P&C products Chapter: Prima Solutions: Prima Insure
Both distribution project andr complete
replatforming projects.

Source: Vendor RFI

201
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include multiple
insurers and forms management, which are configurable using simple tools targeted for a
business user; ACORD, data services, and data upload, which require coding;
reinsurance and document creation which are available with integration to a third party
solution; reporting/analytics, which is available with integration to a separate module
provided by this vendor; ISO, which is on the roadmap; and assignment, which could be
developed (would be considered customization).

Figure 49: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow
Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable Chapter: Prima Solutions: Prima Insure

Source: Vendor RFI

CUSTOMER BASE
They have a total of 12 insurer clients. The breakdown of the clients is as follows: Tier 2
(one client), Tier 3 (two clients), Tier 4 (three clients), and Tier 5 (six clients). There is one
TPA client.

Table 133: Customer Base

EUROPE, MIDDLE EAST, In production with current 12


AND AFRICA CUSTOMER release or any release less
than four years old

202
BASE In production with release four 0
or more years old

New clients since 2015 Europe:


France 10
Germany & Austria 1

Existing client base by Europe:


country France 12
Germany & Austria 1

Deployment method On Premise: 50%


(percentage of client base)
Hosted: 50%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Allianz France,


AXA,
MAIF.

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 134: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 6

HOMEOWNERS In production today 6

COMMERCIAL AUTO In production today 4

COMMERCIAL PROPERTY In production today 4

COMMERCIAL LIABILITY In production today 3

WORKERS COMP In production today 2

BUSINESS OWNERS POLICY In production today 1

Source: Vendor RFI

TECHNOLOGY Chapter: Prima Solutions: Prima Insure


The technical architecture is based on J2EE. The platform is built around an n-tier
architecture with the following tiers: a client tier that is initially JSP, then Web 2.0 / AJAX
as of V6 and Angular as of V8; a web tier (Servlet or Web Service) which serves as an
interface between the client and the business process; a business tier bringing together
all the business players, which contributes to business actions (business processes,
business entities, business operations, etc.); and a data tier ensuring persistence of
created business entities (quotes, policies, people, etc.).

203
The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps, although it can be integrated to apps through their
API.

Table 135: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 100%


Business users: Java: 100%
Developers: Java: 100%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Windows 2008 R2
Red Hat Enterprise Linux Server release 6.6
(Santiago)
CentOS release 6.7 (Final)

APPLICATION SERVERS Tomcat 8.5 - Wildfly 9 - WebSphere 8.5.5.10

DATABASES Preferred: Oracle; Microsoft SQL Server


Additional options: DB2/UDB

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format
Additional options: ACORD Standard XML; Other
XML; MQSeries, JMS or similar queue technology;
Flat files; Custom API
Public API integrations: Ogone payment system APIs
for example, Bank of France APIs, OpenTrust, motor
registration directory…

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No Chapter: Prima Solutions: Prima Insure
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: About 1,000 users and 20 million


policies

Source: Vendor RFI

The data model is proprietary. However, they provide a public database (or pivot
database) which provides all the Prima Insure data to other systems (for example BI
systems) and which is used for data import. This public database is based on ACORD IM
which was built from the Prima IBCS business model. It supports ACORD IM, DARVA
message exchanges for France (for Claims). The data model can be extended by carriers
using extension patterns for customers to extend the data model beyond the
configuration capabilities. The extension is done by code. For the insurer to make
changes to the data model, the vendor provides extension patterns which include the

204
extension of the SQL model, the extension of the data accessors (DAO), and the
extension of the data objects (beans). The data model can be released to an insurer. It
can be published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and role-based security integration. Data definition is
configurable using tools targeted for an IT user. Interface definition requires coding.
Changes to the system are possible through reusable components, inheritance, and
other schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with French Vehicule
Registration system, DARVA for third party data services; OpenTrust for e-signature;
QlikView for business intelligence systems; SAGE for general ledger; Alfresco for
document management systems; and SEFAS for document creation systems.

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. They provide a set of
prebuilt tests. A restart of the system is required for change to underlying data model,
new web service or integration point, or change to portal.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 5 to 7 (for a
small project) or approximatively 20 people (for a large project) consists of resources
from the insurer (30%), Prima Solutions (40%), and external professional services firms
(30%). Service-level agreements are offered; a typical SLA is based on the project's team
velocity and the number of story points delivered. During production, the SLAs are based
on response time for handling issues. For their SaaS offering, they have additional SLAs
linked to the availability rate of the platform and the performance.

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

Prima Solutions offers perpetual license, usage-based, SaaS, subscription and


risk-based pricing options. The license fees are typically based on number of functional
components/modules, premium volume, number of states or geographies, and enterprise
license / flat fee. Carriers may also need to license the following third party software:
When supplying Prima Insure on premise, a database license and an application server
license is needed. Otherwise, all licenses are included. Chapter: Prima Solutions: Prima Insure

205
The total cost to implement Prima Insure can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 136: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €5 million to €10 €5 million to €10 18%


only: assuming a two million million
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 Under €500,000 18%


implementation costs
for the regional
insurance company.

Assuming a four year €10 million to €15 €15 million to €25 €15 million to €25 18%
implementation million million million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €500,000 to €1 million €500,000 to €1 18%


implementation for a million
European insurance
holding company

Source: Vendor

Chapter: Prima Solutions: Prima Insure

206
RDT LTD: LANDSCAPE

COMPANY
RDT Ltd is a privately owned company headquartered in West Malling, United Kingdom
with sales and professional services personnel located throughout the European, Middle
Eastern, and African and Asia-Pacific regions. RDT Ltd’s business is providing software
and services to the insurance industry. The company has over 100 employees, of which
over 80 are available to provide professional services / client support for their PAS
solution. Eighty-two are physically located in Europe, Middle East, and Africa.

The user conference is a biannual event where the key contacts from client sites,
including their technical personnel, gather together. The user group is provided with an
opportunity to have open discussions including providing a company update, changes
they have implemented, and changes they would like to see within their software
package, and to discuss any areas of frustration that they have. Representatives from
RDT may present on a number of areas of interest including system developments,
pipeline projects. They are also provided with an opportunity to respond to any items
raised during the clients’ earlier meeting.

Table 137: Company and Product Snapshot

COMPANY Annual corporate revenues Over $15m

Year founded 1991

Exchanges/Symbols N/A

Headquarters Location Global: West Malling, United Kingdom

PAS SYSTEM Name Landscape

Current release and date of 5.2


release

Release intervals Minor enhancements: Monthly


Major enhancements: Biannually

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
all versions.

Target market UK retail insurance providers, third party claims


administrators.

Source: Vendor RFI


Chapter: RDT Ltd: Landscape

207
OVERALL FUNCTIONALITY
A moderate amount of functionality is available out of the box. Exceptions include
ACORD, which could be developed (would be considered customization)[ data services,
data upload, assignment, and reinsurance, which are configurable using tools for a
business user; forms management, which requires coding; document management,
which is available with integration to a third party solution; document creation, which is
configurable using tools for a business user; and reporting/analytics and
multichannel/mobile, which are available with a separate module.

Figure 50: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
Chapter: RDT Ltd: Landscape

They have a total of 19 insurer clients. The breakdown of the clients is as follows: Tier 2
(one client), Tier 3 (two clients), Tier 4 (six clients), and Tier 5 (10 clients). There are
three TPAs.

Table 138: Customer Base

EUROPE, MIDDLE EAST, In production with current 19


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


United Kingdom 2

208
Existing client base by Europe:
country United Kingdom 18

Deployment method On Premise: 88%


(percentage of client base)
Hosted: 12%

Percentage of clients using 12%


PAS through BPO services

Marquee clients Markerstudy,


Direct Line Group,
Key Claims.

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 139: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 14

HOMEOWNERS In production today 7

COMMERCIAL AUTO In production today 14

COMMERCIAL PROPERTY In production today 4

COMMERCIAL LIABILITY Supported but not in production

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Not supported

Source: Vendor RFI

TECHNOLOGY
The technical architecture is fundamentally modular with a set of core SQL Server
relational databases. A domain-driven modular software architecture sits on top of these
modules, and these are in turn compiled into a number of services and end user systems.
The main internal application is a Windows app based on a mixture of client server and
services architecture. There is a continuous rearchitecting process which is exposing
more of the key functionality as web services as required. A service bus intermediated
most external communication, providing a loosely coupled extension point. Synchronous
and asynchronous interactions are supported. The RDT real-time hub provides rules and
translation-based integrations supporting numerous internal and external interfaces. This
technology is the basis of the real-time rating hub (Equator).
Chapter: RDT Ltd: Landscape

The UIs and process flows are designed to be mobile device independent. The solution
natively supports mobile-friendly HTML5 apps.

209
Table 140: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


C: 79%
TSQL: 15%
JavaScript: 5%
Ruby: 1%

Business users:
.NET (C# and VB.Net): 90%
JavaScript: 10%

Developers:
.NET (C# and VB.Net): 99%
Ruby: 1%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows
Planned change to code base: They are in an ongoing
process of rewriting all of the core systems to make
them more web based. Within this they will revisit all
major system functions during the next 1-2 years. The
core technology set will not change from above.

APPLICATION SERVERS N/a

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: Other NoSQL datastore;

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format
Additional options: Other XML; MQSeries, JMS or
similar queue technology; Flat files; Custom API
Public API integrations: Google Maps for geolocation,
MyLicence for driving license validation and
endorsement information, Experian for identity
checking and credit scoring, Synectics for fraud
checks, HPI to retrieve full vehicle data, BACS for
Direct Debit and Direct Credit processing, WorldPay
and Westpac Quickweb for card payment processing,
MIB for MID, CUE for claims fraud.

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes
Chapter: RDT Ltd: Landscape

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: Approximately 1,400 users and 1


million active policies

Source: Vendor RFI

210
The data model is proprietary. It supports ABI Standard Code Lists. The data model can
be extended by carriers using RDT. The data model can only be changed in certain
cases. In cases where it can be changed by the customer, the data model can be
changed by the tools that allow the underlying data schema and mapping between
schemas to be changed. The data model can be released to an insurer. It can be
published to an insurer’s data model.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, data definition, and role-based security integration. Business rule definition and
interface definition require coding. Changes to the system are possible through reusable
components, inheritance, and other schemes. All product components (including product
features, coverages, benefits, transactions, rules, and calculations) are reusable for
multiple products.

In Europe, Middle East, and Africa the system is preintegrated with QAS, PAF for
address verification; LexisNexis, CUE, SIRA, Windscreen, Glass's Guide, MID1, MID2,
MyLicence, Synectics, ABI for third party data services (e.g., lexisnexis, iso, etc.); Google
analytics for analytics solutions; and Microsoft reporting services, Qlik, Microsoft Analysis
Services, Power Pivot, Power View, and Azure Data Services for business intelligence
systems; Cubes are available to client data warehouse for data warehouse; GL can be
exported to external package for general ledger; Yes for reinsurance solutions; Yes for
billing systems; Yes for reinsurance systems; Document Logistix, INVU, Kofax for
document management systems; Kofax for document creation systems; Audatex for
supplier networks and portals; OS for geocoding solutions; BACS for payments systems
(disbursements); Yes for new business and underwriting; Yes for claims; Yes for CRM;
Yes for product calculation engine; Yes for distribution management; Yes for producer
portal (quick quote, illustration, bind, issue); Yes for prospective customer portal (quick
quote, illustration, bind, issue); Yes for policyholder portal (inquiries and transactions for
in-force policies); and RDT Fraud module, enrichment via Experian, Cue, LexisNexis,
Callcredit, RDT Graphical Workflow for other.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. A restart of
the system is required for insurance product modification/configuration, screen
configuration, change to underlying data model, new web service, or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 6-10 people
consists of resources from the insurer (50%) and RDT Ltd (50%). Service-level
agreements are offered; a typical SLA includes up-time, response times, etc.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.
Chapter: RDT Ltd: Landscape

RDT Ltd offers term license, usage-based, SaaS, subscription, risk-based, and GWP-
based pricing options. The license fees are typically based on number of functional
components/modules, number of concurrent users, number of total or named users,
premium volume, enterprise license / flat fee, and per transaction.

211
The total cost to implement Landscape can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 141: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €1 million to €5 million Dependent on the No cost, not
only: assuming a two client applicable
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A €500,000 to €1 million Dependent on the No cost, not
implementation costs client applicable
for the regional
insurance company.

Assuming a four year Out of pricing model, Out of pricing model, Out of pricing Dependent on the
implementation needs to be needs to be model, needs to be client
period, for a negotiated negotiated negotiated
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A Out of pricing model, Out of pricing Dependent on the
implementation for a needs to be model, needs to be client
European insurance negotiated negotiated
holding company

Source: Vendor

Chapter: RDT Ltd: Landscape

212
RGI S.P.A.: PASS_INSURANCE 3.0

COMPANY
RGI is a privately owned company (with outside investors) headquartered in Ivrea, Italy
with sales and professional services personnel located throughout the European, Middle
Eastern and African region. RGI’s business is providing software and services to the
insurance and banking industries. The company has 769 employees of which 656 are
available to provide professional services / client support for their PAS solution; 523 are
physically located in Europe, Middle East, and Africa.

The last user conference was the RGI Next UX Factor. RGI Next is the yearly flagship
event of RGI. It takes place in the beginning of October and in 2016 reached its 5th
edition involving over 200 professionals from Insurance world. Last year, they discussed
usability as one of the main drivers for the digital disruption in the Insurance word.

RGI Next France event took place in June 2016 at Hotel W Opéra, in Paris. About 30
Insurance professionals, IT Directors, and CIOs attended the “RGI Matinale” that was
dedicated to the hot topics of the insurance industry in France.

The La Transformation Digitale Clè en Main is an event dedicated to the Benelux region
and organized in June 2017 in Luxemburg. The “Matinale” is dedicated to exploring the
innovation in the Insurance world with a focus on their Life and Digital value proposition.

Table 142: Company and Product Snapshot

COMPANY Annual corporate revenues €70.3 million (US$83.6 million) as per year 2016.

Year founded 1987

Exchanges/Symbols Not publicly quoted

Headquarters Location Global: Ivrea, Italy

PAS SYSTEM Name PASS_Insurance 3.0

Current release and date of 4.4 stable


release
Chapter: RGI S.p.A.: PASS_Insurance 3.0
Release intervals Minor enhancements: 4 per year
Major enhancements: 2 per year

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market Insurers of all size (Tier 1, Tier 2, Tier 3) in P&C,


General Insurance and Specialty Lines across
Italy, France, Dach Area, Benelux, Maghreb
Area, Nordics, and Spain.

Source: Vendor RFI

213
CELENT OPINION
Since the last report, RGI has demonstrated an ability to deliver in multiple countries
across Europe and has grown.

RGI has dominated their local market with a strong digital story around PASS_Insurance
and continued investment in the product. PASS_Insurance offers a modern, web-based
interface for its internal users along with support for mobile and tablet browsers. The
interface is clear and makes good use of the space in the browser. The assembly of the
portal experience is composed of cards that can be assembled into a user interface. The
acquisition of Kapia has clearly bolstered RGI’s capabilities.

Configuration is done through a web-based interface as well, with support for viewing
business processes from the browser. RGI also demonstrated support for mobile devices
and tablets.

RGI is increasingly investing in AI and analytics capabilities within their solution set
including a chatbot solution - Nexy, a recommender solution, and a predictive analytics
capability.

PASS_Insurance has grown up in a very digital and challenging market. The tool is
clearly a strong fit for insurers in other countries around Europe that are facing similar
challenges. This year we see consolidation in Tunisia as well. RGI has demonstrated an
ability to modernize technology, to be extremely relevant in a digital insurance world, and
now to grow beyond the Italian borders.

Celent will watch the continued investment and momentum with interest.

Chapter: RGI S.p.A.: PASS_Insurance 3.0

214
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
assignment, which is configurable using tools for an IT user; rating, which is configurable
using tools for a business user; ISO, which is not available; and
scheduling/calendar/diary, which is available with integration to a third party solution.

Figure 51: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow
Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

Chapter: RGI S.p.A.: PASS_Insurance 3.0


CUSTOMER BASE
They have a total of 53 insurer clients. The breakdown of the clients is as follows: Tier 1
(five clients), Tier 2 (seven clients), and Tier 3 (41 clients).

Table 143: Customer Base

EUROPE, MIDDLE EAST, In production with current 20


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 33


or more years old

215
New clients since 2015 Europe:
Italy 5
France 1
Germany 1
Africa:
Tunisia 1

Existing client base by Europe:


country Italy 45
France 2
Belgium 1
Netherlands 1
Ireland 1
Germany 1
Africa:
Tunisia 2

Deployment method On Premise: 74.54%


(percentage of client base)
Hosted: 25.45%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Not provided

Source: Vendor RFI

CUSTOMER FEEDBACK
Five clients provided feedback on PASS_Insurance. Two are Tier 5 insurers, one is a
Tier 4 insurer, and the last two are Tier 2 insurers. Three references have used the
solution for more than three years, one for less than a year, and the last reference for
some time in between. The references represent insurers using the system for personal
lines, commercial lines or a mix of both. Two of the references also use the solution for
specialty lines.

In terms of the best things about the vendor, references highlighted RGI’s knowledge of
the insurance industry, and their partnership with their customers. In terms of the system,
references valued the technology and functional completeness, and several particularly
referenced the product design and configuration as key benefits.

Areas of improvement in terms of the system, some references want a little more focus
on usability and user experience, and one sought improvements in reporting. Two of the
references asked for increased quality of delivery, but this was the only item for RGI.
Chapter: RGI S.p.A.: PASS_Insurance 3.0

216
Functionality received above average scores overall, and within functionality, analytics
received the highest score, while portals for policyholders and prospects was an area in
need of improvement. Configurability scores were above average, and within
configurability, products (design and maintenance) received the highest score.
Comments on the integration were above average, and within integration your claim
system(s) received the highest score. Regarding their technology experiences, insurers
gave above average marks, and within technology scalability of the solution received the
highest score. The implementation was rated above average overall, and within
implementation knowledge of your business received the highest score. Finally, support
received above average scores, and within support knowledge of their solution and
relevant technology received the highest score.

Figure 52: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.54

Support Configurability
3.75
3.78

Implementation Integration
4.03 3.73

3.70
Technology

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 144: Selected Lines of Business Supported

NUMBER OF CLIENTS IN Chapter: RGI S.p.A.: PASS_Insurance 3.0


LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 34

HOMEOWNERS In production today 50

COMMERCIAL AUTO In production today 34

COMMERCIAL PROPERTY In production today 50

COMMERCIAL LIABILITY In production today 50

WORKERS COMP Not supported

BUSINESS OWNERS POLICY In production today 50

Source: Vendor RFI

217
TECHNOLOGY
The technical architecture is a Web application that uses a “multi-tier” architecture, based
on J2EE standard, with a Presentation Layer (Front End) that consists of HTML and JSP
pages and JavaScript, a Business Layer (Middle Tier) that consists of Servlets and Java
classes, Service Layer that consist of Web services for integration with external systems,
and Persistence Layer. Portal FE is implemented using html 5, Angularjs framework, and
an API gateway to expose rest services from the back end.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android, and mobile-friendly HTML5 apps.

Table 145: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 60%
C++: 5%
JavaScript: 10%
Other (JSP): 25%
Business users:
Java: 60%
C++: 5%
JavaScript: 10%
Other (JSP): 25%
Developers:
Java: 60%
C++: 5%
JavaScript: 10%
Other (JSP): 25%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: The solution is
independent from the operating system and can use
any operating systems that supports a Java (J2EE)
environment.

APPLICATION SERVERS WebSphere 6.0, 6.1, 7.0, 8.0


(win,linux,aix,Z/OS,Z/VM)
JBoss 5.x, 7.x (win,linux)
Tomcat 5.x, 6.x (win,linux,solaris)

DATABASES Preferred: Oracle; Microsoft SQL Server; DB2/UDB


Additional options: Other SQL

INTEGRATION METHODS Preferred: Web Services; RESTful HTTP style


services; JSON format; Flat files; Custom API Chapter: RGI S.p.A.: PASS_Insurance 3.0
Additional options: ACORD Standard XML; Other
XML; MQSeries, JMS or similar queue technology
Public API integrations: The Mobile solution offers an
integration with Google Maps in order to have an
integrated map of the subject residence address.
RGI is evaluating a partnership with an innovative
startup which has developed a platform to monitor
profiles on social networks and other channels (such
as forums, portals, blogs). The main objective of the
collaboration is to enrich operational data on
customers/prospects.

218
TECHNOLOGY SPECIFICS

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: About 4.200 users and 19 million


policies

Source: Vendor RFI

The system uses a ERwin data model. The data model can be extended by insurers
using a number of extension points in the data model.. Generally, database extensions
also need a code implementation to manage new structure. For the insurer to make
changes to the data model beyond the provided extension points, it is recommended that
a DBA extend the database schema in SQL because the changes to business logic and
screen designs are written in code. The data model can be released to an insurer. It can
be published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code, generally changes do not affect the core code
and are isolated to client specific extensions. Configuration tools targeted to a business
user are available for the following: insurance product definition, screen definition, role
based security and business rule definition. Workflow definition is configurable using tools
targeted for an IT user. Interface definition, and data definition require coding. Changes
to the system are possible through reusable components, inheritance, and other
schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

The vendors solution, PASS_Insurance provides support for the following features: agent
portal software; agent management system; medical estimation tools and medical bill Chapter: RGI S.p.A.: PASS_Insurance 3.0
review; illustrations; new business and underwriting; distribution management and
producer portals and; prospective customer quote portal. The solution also integrates
with PASS_SmartQuote for producer and customer portals, and PASS_HomeInsurance
(both offered by this vendor). The solution is also integrated with several aggregators:
Facile.it, segugio.it and gocompare.com, and to the Italian Institutional Authority (IVASS)
Quotation System.

The solution is also integrated to the vendors offering, PASS_ePaper for e-signature and
document management. The solution is also integrated with Namirial for e-signature and
Auto store, Documentum, Filenet, Alfresco, and Sharepoint for document management.
For document generation there are integrations to an internal solution (PASS_Doc) and
Doc1, Papyrus, Adobe Server Pack, Xform, Xlaser, and Intraform.

For analytics and business intelligence the solution is preintegrated with both
PASS_Analytics and with QlikSense. For data warehouse the solution is integrated with

219
SAS, Oracle B.I., SAP BW, and Business Objects. For General ledger there are
integrations to SUN, SAP FS-CD, SAP FI-CO, and Oracle FI. PASS_Reinsurance and
Xlayer are preintegrated for reinsurance. For payments and disbursements there are
integrations to Credit Card (Visa, Mastercard), PayPal, SDD, MyBank, and Nexi.

For business process management there is the internal solution, PASS_BPM as well as
integrations to Camunda and JBPM. For CRM the system is integrated to Microsoft
Dynamics, Vtiger, SugarCRM, Salesforce, and Chorally.

For supplier networks the solution is preintegrated to Autosoft (Solera) and Sharepoint.
The solution is preintegrated to Google Maps for geocoding. In terms of claims
integrations more broadly the solution is preintegrated to an internal solution
(PASS_Claims), Autosoft (Solera), Pytagoras (counter-terrorism), Nexpansion (counter-
terrorism) Viasat, Octotelematics, and AIA (counter-fraud database).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested using a specific tool provided. A restart of the system
is required for screen configuration, change to underlying data model, new web service or
integration point, or workflow change.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 3 to 25 resources people consists of resources from the insurer (45%),
RGI (35%), and external professional services firms (20%). Service-level agreements are
offered; a typical SLA depends on the contract agreement and the Operating Model. The
Service Provider can provide the following main services. For each service, the Customer
and the Service Provider can agree upon SLAs.

There are several product services being offered. The Service Provider takes all the
measures necessary to keep the System continually updated by means of Product
Updates released by the Service Provider. They also provide Adaptive maintenance.
Modifications originating from requests from all Regulatory Bodies and/or any other
Authority, or originating from adjustments derived from whatever legislative changes,
within deadlines set by the relevant Regulatory Bodies and or Authorities and the
Customer. An example of Adaptive Maintenance is the update of system software in
order to bring it line with the requirements of the Regulatory Bodies and or Authorities.

They offer Application Development and Evolutionary Maintenance. They support the
customer with analysis services needed to compile a Requirement Package. They
analyze and quote the solution to the Customer request. They can Build and Test. They
Review Implementation Package and Business Acceptance Test (BAT): the Service
Provider can release the components built or modified into the appropriate environments Chapter: RGI S.p.A.: PASS_Insurance 3.0
in order that the Customer can perform the BAT. The Service Provider can migrate all
changes approved by the Customer following the BAT into the Integration Environment
and then into the Production Environment.

They provide second level user support. The service covers all the actions to be taken by
the Service Provider’s Help Desk to manage requests for support forwarded by the
Customer IT Support. The Service Provider can provide a Help Desk that is responsible
for handling Customer queries and issues relating to the provision of the Services.

The corrective maintenance covers all the actions necessary to identify and correct any
and all errors with the technical solution, either as reported by the customer or by the
service provider.

The preventative maintenance covers all the actions required to avoid future problems,
including but not limited to, those affecting the functionalities and processes, as well as
220
improving quality, stability, performance, and reliability of the software component and
infrastructure component. The Service Provider shall take a proactive role in providing
this service.

The Service Provider could be the responsible for the provision of facilities and system
management functions to ensure the provision of Services to meet the requirements for
the Technical Solution.

The backup and restore management covers the planning and preparation of all
procedures for backup and restoration of the database(s) and of all the information
required by the application (private application data) such as Management of the
Application Environments, Security Management, Disaster Recovery Management, and
Business Continuity.

IT Service Management and Control: the Service Provider could be responsible for
assuring the Customer that the Services are being delivered in accordance with the
Customer’s requirements (e.g., production of periodic service status reports,
management of critical issues, revision of the service scope, etc.)

HD3 manages the Ordinary Application Maintenance, in which a new software release is
required, this includes Minor Change Request. The primary aim is managing the first
escalation level raised by HD2. HD3 organizes the release management regarding the
bug fixing by integrating software components and performs preventive maintenance,
product fixing, and extension fixing. HD3 is split in two main groups: one provides support
regarding the Corrective Management, and the other one provides the Evolutionary
Management.

The average time to get the first line of insurance live in a single jurisdiction is typically 12
to 18 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 7 to 12 months.

RGI offers term license, perpetual license, usage-based, and SaaS pricing options. The
license fees are typically based on number of functional components/modules, premium
volume, number of states or geographies, and enterprise license / flat fee. The vendor
will offer a fixed price implementation after a gap analysis phase in order to define the
customer requirements and consequently to quantify in depth effort and cost of the
project

The total cost to implement PASS_Insurance 3.0 can vary according to the capabilities
and available resources of the client, and the overall scope of system use.
Chapter: RGI S.p.A.: PASS_Insurance 3.0
Table 146: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €5 million to €10 Depends on the 18%


only: assuming a two million client’s needs
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

221
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post No cost, not No cost, not No cost, not 18%
implementation costs applicable applicable applicable
for the regional
insurance company.

Assuming a four year €1 million to €5 million €5 million to €10 Depends on the 18%
implementation million client’s needs
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post No cost, not No cost, not No cost, not 18%
implementation for a applicable applicable applicable
European insurance
holding company

Source: Vendor

Chapter: RGI S.p.A.: PASS_Insurance 3.0

222
SAP SE: SAP POLICY MANAGEMENT

COMPANY
SAP is a publicly traded company headquartered in Walldorf, Germany with sales and
professional services personnel located throughout the North American, European,
Middle Eastern, and African, Asia–Pacific, and Latin American regions. SAP’s business is
providing software and services to the insurance and 24 other industries. The company
has over 85,000 employees. SAP does not provide a breakdown of the amount of
employees able to provide support for their PAS solution. SAP does not provide a
breakdown of employees by region.

SAP’s user conferences are Sapphire, SAP Digital Insurance Innovation Summit,
Insurance Forum Germany, SAP Next-Gen Boot Camp on Machine Learning in Financial
Services, SAP Next-Gen Boot Camp on Blockchain and a FSI Forum.

All events include education on products, roadmaps, and customer best practices.

Table 147: Company and Product Snapshot

COMPANY Annual corporate revenues €22.06bn (2016)

Year founded 1972

Exchanges/Symbols SAP

Headquarters Location Global: Walldorf, Germany

PAS SYSTEM Name SAP Policy Management

Current release and date of Release 5.4


release

Release intervals Minor enhancements: Every 6 months


Major enhancements: Every 12 to 18 months

Upgrades Insurers must upgrade by going from one version


to the next sequentially (e.g., 4.0 to 5.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Chapter: SAP SE: SAP Policy Management


Target market All LoBs, All Sizes of Insurance Companies

Source: Vendor RFI

223
OVERALL FUNCTIONALITY
Much of the functionality is available straight out of the box with the core solution or are
delivered through SAP components.

Figure 53: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
SAP does not disclose their client information, but they have an active marketing and Chapter: SAP SE: SAP Policy Management
sales team in the region.

Table 148: Customer Base

EUROPE, MIDDLE EAST, In production with current 7


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


Germany 1
Netherlands 1

Existing client base by Europe:


country Germany 3
Austria 2
Netherlands 2

224
Deployment method On Premise: 100%
(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Marquee clients Not provided

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 149: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today

HOMEOWNERS In production today

COMMERCIAL AUTO In production today

COMMERCIAL PROPERTY In production today

COMMERCIAL LIABILITY In production today

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY In production today

LIFE INSURANCE In production today

Source: Vendor RFI

TECHNOLOGY
The technical architecture is based on the SAP NetWeaver platform and communicates
via open interfaces with further components, which could be applications of SAP for
Insurance or even third party solutions.

In addition, main business transactions and functions of SAP Policy Management are
encapsulated as APIs in a manner that enables users to access those via different User
Interfaces and applications by well-established technologies like SOAP, oData, and
Chapter: SAP SE: SAP Policy Management
Remote Function Calls.

SAP Policy Management builds on a three-tier client server architecture (client interaction
server, application server, database server) which can be deployed in flexible ways to
cover individual security, availability, and system performance requirements. Internal
communication is handled by the application server. External communication is achieved
through multiple interaction methods such as web services based on a message bus,
e.g., SAP NetWeaver Process Integration (SAP NW PI), but also point-to-point
connections. The SAP Sybase Unwired Platform and the Afaria Management Console
help facilitate the integration and administration of mobile user devices.

With regards to Insurance Content, SAP Policy Management follows the principles of
decoupling products and processes, highly configurable system, extendable functionality,
and data model as well as supporting multiple lines of business on one single instance.

225
The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS) and other app types.

Table 150: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


ABAP Object
Business users:
ABAP Object / HTML5 ( e.g. SAP Fiori ), other user
interfaces can be connected to call business
transactions via remote function modules): 100%
Developers:
BAP Object (policy administration) and M10 for
msg.PM Designer (product development)): 100%

OPERATING SYSTEMS SAP Policy Management is based on SAP Netweaver.


Please have a look on the detailed product availability
matrix (PAM) to see which operating systems,
databases, and other platforms are supported:
https://apps.support.sap.com/sap/support/pam

APPLICATION SERVERS SAP Netweaver Application Server

DATABASES Preferred: SAP HANA;


Additional options: Oracle; Microsoft SQL Server;
DB2/UDB; Sybase; Other SQL

INTEGRATION METHODS Preferred: None


Additional options: Web Services; JSON format; Flat
files; Custom API
Based on the infrastructure of SAP NetWeaver,
several interfaces and methods for enhancements
and for an end-to-end integration are supported
without modification of the SAP standard.

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface: No
No out-of-the-box but easily usable as SAP Policy
Management is service-enabled.
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: Yes
In case other user interfaces are used those can be
connected to call PAS-related business transactions
Chapter: SAP SE: SAP Policy Management
and functions as SAP Policy Management is service-
enabled.
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment Several tens of thousands user


and more than 20 million policies.

Source: Vendor RFI

The data model is proprietary and is in alignment of VAA (German Insurance Application
Architecture). It supports VAA (German Insurance Application Architecture). In general
customers are advised to avoid a modification of the SAP standard core code. For this

226
purpose, SAP provides lots of interfaces, user exits, and configuration options to allow
insurer-specific enhancements without modification of the core code. Several tools and
concepts are integrated to make enhancements (e.g., ABAP Workbench, customer
includes, object wizard, and more).

For the insurer to make changes to the data model, a number of extension points in the
data model are provided where the customer can store data of their choosing. The
number of slots is limited, and the underlying schema cannot be changed except by
changing the code. The data model can be released to an insurer. It can be published to
an insurer’s data model.

Carriers have access to the core code; configuration tools targeted to a business user are
available for the following: workflow definition, business rule definition, and role-based
security integration. Insurance product definition, screen definition, interface definition,
and data definition are configurable using tools targeted for an IT user. Changes to the
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules,
and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with SAP Netweaver for
address verification; SAP Netweaver for third party data services (e.g., lexisnexis, iso,
etc.); SAP Hybris Cloud for Customer for agent portal software; SAP Incentive and
Commission Management for agent management systems; a third party solution
leveraging SAP Netweaver for e-signature; SAP Hana Analytics for analytics solutions;
SAP Business Intelligence for business intelligence systems; SAP Master Data
Management for data mastery, master data management tools; SAP Business
Intelligence for data warehouse; SAP Financials for general ledger; SAP Business
Process Management for business process management systems; SAP Reinsurance for
reinsurance solutions; SAP Collections and Disbursements for billing systems; SAP
Reinsurance for reinsurance systems; OpenText for document management systems;
OpenText for document creation systems; SAP Ariba, SAP Fieldglass for supplier
networks and portals; SAP HANA for geo coding solutions; SAP Collections and
Disbursements for payments systems (disbursements); SAP Policy Management for
illustrations; SAP Policy Management and SAP Underwriting for Insurance for new
business and underwriting; SAP Claims Management for claims; SAP Hybris Cloud for
Customer for crm; msg.PM, SAP Product Lifecycle Management for product calculation
engine; SAP Incentive and Commission Management for distribution management; SAP
Hybris Cloud for Customer for producer portal (quick quote, illustration, bind, issue); SAP
Hybris Products for Commerce for prospective customer portal (quick quote, illustration,
bind, issue); and SAP Hybris Products for Commerce for policyholder portal (inquiries
and transactions for in-force policies).
Chapter: SAP SE: SAP Policy Management
Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested using a specific tool provided. A restart of the system
is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team number depends on the specific insurer implementation approach and
consists of resources from the insurer (40%), SAP (10%), and external professional
services firms (50%). Service-level agreements are offered; a typical SLA includes
resolution time required for tickets, downtime for cloud services, etc.

The average time to get the first line of insurance live in a single jurisdiction is typically 12
to 18 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 4 to 6 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.
227
SAP offers perpetual license, SaaS, and subscription. The license fees are typically
based on premium volume.

The total cost to implement SAP Policy Management can vary according to the
capabilities and available resources of the client, and the overall scope of system use.

Chapter: SAP SE: SAP Policy Management

228
SAPIENS: IDIT

COMPANY
Sapiens is a publicly traded company headquartered in Israel with sales and professional
services personnel located throughout the North American, European, Middle Eastern,
and African and Asia-Pacific regions. Sapiens’ business is providing software and
services to the insurance and financial services industries. The company has over 2,500
employees. The Sapiens IDIT solution is distributed in EMEA and APAC, while other
P&C PAS solutions are available in the Americas. Sapiens IDIT is supported by over 800
employees who are physically located in Europe, Middle East, and Africa and APAC.

The last user conference was an annual client conference. The Sapiens 2016 event
attracted more than 150 participants from 13 countries, including insurance and financial
services customers, prospects, and analysts. Attendees networked, participated in
discussions and presentations, and learned about Sapiens’ strategy and future vision.
These conferences are held in both NA and Europe. The upcoming Sapiens’ Partnering
for Success 2017 client conference will take place at the Ritz-Carlton Penha Longa resort
in Lisbon, Portugal on October 16-18, 2017.

Table 151: Company and Product Snapshot

COMPANY Annual corporate revenues USD$216.19M FYE 2016

Year founded 1982

Exchanges/Symbols NASDAQ and TASE: SPNS

Headquarters Location Global: Israel

PAS SYSTEM Name Sapiens IDIT

Current release and date of V13.2 - end of year 2016


release V14 2017 – Full digital suite with portal and BI
API connectors to IoT, BOTS as well as GDPR
compliance readiness, No-SQL DB elastic
search

Release intervals Minor enhancements: Twice a year


Major enhancements: Once a year

Upgrades Vendor provides upgrade services and has


successfully completed 4 major upgrades this
year.
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.
Chapter: Sapiens: IDIT

See client feedback

Target market All personal and commercial and specialty


carriers either mono or multi line. Operating in
single or multiple locations in the region.
Generally, GWP of over $50m or greenfield
projects.

Source: Vendor RFI

229
CELENT OPINION
Sapiens IDIT continues to have a strong presence in Europe, with more clients in
BeNeLux, UK, and the Nordics in this year’s report. In addition, Sapiens IDIT has won
another client in Israel and in Africa — perhaps showing signs of being one of a few pan-
EMEA systems. Celent welcomes the continued investment and acquisitions in the
general insurance space.

Sapiens demonstrated their strong web-based user interface for IDIT and has continued
to invest here with interfaces demonstrated in a standard browser as well as on a tablet
as in previous years. Both are rich and offer a modern interface. This year Sapiens also
demonstrated ChatBot integration with Nanorep, image analysis with IBM Watson, and
integration with Slack. Also new is their investment in Sapiens’ own digital offerings with
customer and agent portals planned.

The solution comes with a variety of configuration tools, including a visual workflow editor
and rules engine editors. The jewel in the crown for their configuration environment which
enables business users to maintain insurance products and offerings, and control many
of the activities involved in launching a new insurance product.

This year’s customer feedback reflects Sapiens’ growth from new digital offering to an
established vendor across EMEA and APAC, dealing with the difficult challenges of not
leaving customers behind while growing the product set.

Sapiens IDIT continues to offer a very strong, digital policy administration system for
insurers across EMEA and APAC in Sapiens IDIT, and Celent expects to see further
growth in their customer base in coming years.

Chapter: Sapiens: IDIT

230
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is configurable using tools for an IT user; data services, which is available with
integration to a third party solution; and ISO, which is configurable using tools for an IT
user.

Figure 54: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine Document
Multiple Insurers Forms Management
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
Sapiens has a total of 21 insurer clients in EMEA, of which 16 are in production and 5 are
being implemented — with more clients in APAC. The breakdown of the clients is as
follows: Tier 1 (four clients), Tier 2 (one client), Tier 4 (five clients), and Tier 5 (five
clients).

Table 152: Customer Base


Chapter: Sapiens: IDIT

EUROPE, MIDDLE EAST, In production with current 11


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 4


or more years old

231
New clients since 2015 Europe:
United Kingdom 2
Denmark 1
Norway 1
Middle East:
Israel 1
Africa:
South Africa 1

Existing client base by Europe:


country United Kingdom 5
Belgium 2
France 2
Germany 1
Ireland 1
Netherlands 1
Poland 1
Russia 1
Turkey 1
Middle East:
Israel 1
Africa:
Mauritius 1

Deployment method On Premise: 77%


(percentage of client base)
Public cloud, single tenant: 23%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Hiscox - award winning multi line


multinational
Euler Hermes - multinational part of Allianz
global credit leader
PartnerRe - Global Primary wholesale of
liability products
Anadolu - multiline giant leader in the
Turkish market
BFD (Polis Direct) - over 15 years of
dedication to the Dutch market with
Sapiens IDIT

Source: Vendor RFI

CUSTOMER FEEDBACK
Four clients provided feedback on Sapiens IDIT. Two are Tier 5 insurers, one is a Tier 4
insurer, and one is a Tier 2 insurer. Two references have been using the solution for 1 to
3 years, one less than 1 year. and the other more than three years. Two references use
the solution for a mix of personal and commercial lines, one for all or mostly personal
lines, and one for all or mostly commercial lines. In addition, one reference uses the
solution for workers compensation lines of business and for specialty.

In terms of the best things about the vendor references valued the flexibility of the
partnership, supportiveness, and their willingness to be “in the trenches.” One reference
commented on their strong cultural alignment even with a multinational, multilocation
Chapter: Sapiens: IDIT

delivery team. In terms of the system, references valued the rich functionality,
configurability, and self-sufficiency.

In terms of areas for improvement for the vendor, references mentioned improving
knowledge of their customer (the insurer), and a few comments around the support
models for different types of customers and for specific countries. In terms of areas to
improve in the system, one reference noted the claims functionality could be improved
along with some other detailed functionality.

232
Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score, while analytics was an area
in need of improvement — albeit this likely refers to its absence until added to the
solution recently. Configurability scores were above average, and within configurability
user management (permissions, authority) received the highest score. Comments on the
integration were above average, and within integration your reinsurance system(s)
received the highest score. Regarding their technology experiences, insurers gave above
average marks, and within technology configurability of the solution received the highest
score. The implementation was rated above average overall, and within implementation
knowledge of their solution and relevant technology received the highest score. Finally,
support received above average scores, and within support knowledge of their solution
and relevant technology received the highest score.

Amongst the references was an insurer that upgraded through more than 5 versions of
the software. The project was both complex and lengthy, but was completed successfully
despite the challenges. The scores below include reference to this difficult upgrade
process.

Figure 55: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.60

Support Configurability
3.61 3.94

Implementation Integration
3.68 4.25

3.58
Technology

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 153: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA
Chapter: Sapiens: IDIT

PERSONAL AUTO In production today 8

HOMEOWNERS In production today 9

COMMERCIAL AUTO In production today 8

COMMERCIAL PROPERTY In production today 11

233
NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

COMMERCIAL LIABILITY In production today 14

WORKERS COMP In production today 5

BUSINESS OWNERS POLICY In production today 8

Source: Vendor RFI

TECHNOLOGY
The technical architecture is an end-to-end SOA-based distributed system, developed in
pure Java and JEE technologies. IDIT is component-based with core/country/customer
layers. The layered implementation separates the common infrastructure (Core Layer)
from country-specific elements (Country Layer) and customized features (Customer
Layer), as well as a common corporate layer for multinationals. IDIT is an n-tier system,
designed to distribute workload between the application server, which holds the
application logic, and the database, which manages the data. The presentation layer is a
web browser that is multi-browser supported with a dedicated look and feel for tablets.
Client-side installations are not required. A web-based RIA user experience is enabled by
the IDIT Web Framework, through the use of HTML 6, CSS3, Jquery, AJAX, and other
technologies. Sapiens also offers hosting on the Azure cloud.

The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), Android and Windows.

Table 154: Technology options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 90%


JavaScript: 10%
Business users: Java: 90%
JavaScript: 10%
Developers: Java: 90%
JavaScript: 10%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: Windows server,
Linux (RedHat, Suse), Unix (AIX, HP-UX, Solaris)

APPLICATION SERVERS WebSphere 9, WebLogic 12, Jboss EAP 7

DATABASES Preferred: Oracle; Microsoft SQL Server; DB2/UDB;


Additional options: None

INTEGRATION METHODS Preferred: Web Services; Other XML; RESTful HTTP


style services; JSON format ; MQSeries, JMS or
similar queue technology; Flat files
Additional options: ACORD Standard XML; Custom
Chapter: Sapiens: IDIT

API
Public API integrations: Public: GoogleMaps,
Facebook, Watson natural language and Google
photo API. Global private like DataCache for credit
card payments. Also multiple country-specific like
DVLA in UK, EDI in Denmark

234
TECHNOLOGY SPECIFICS

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: Hundreds of user and millions of


policies

Source: Vendor RFI

The data model is based on years of experience working with industry models like IBM’s
IAA and ACORD and other national structures along with required adaptations. It is joint
work with IBM indicated similarity and easy mapping to IBM IAA. The data model can be
extended by carriers using a configuration tool for selected entities, and using Sapiens
IDIT IDE plugin for doing data model change son the customization layer. For the insurer
to make changes to the data model, the company has a set of tools that allow technical
staff to extend the data model and the database schema. The data model may be
released to an insurer. It can be published to an insurer’s data model and mapped to an
intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and role-based security integration. Data definition is
configurable using tools targeted for an IT user. Interface definition requires the existing
interface library with a combination of reusable configuration mapping, and coding.
Changes to the system are possible through reusable components, inheritance and other
schemes. All product components (including product features, coverages, benefits,
transactions, rules, and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa the system is preintegrated with QAS and Local post
office for address verification; BACS, SEPA, DVLA, MID and CUE for third party data
services (e.g., lexisnexis, iso, etc.); Outsystems and Backbase for agent portal software;
CRM for agent management systems; DocuSign for e-signature; Jasper, SAP, Business
Objects, SQLServer and QlikView for analytics solutions; SAP, Business Objects and
SQLServer for business intelligence systems; ETL and Informatica for data mastery,
master data management tools; BO, QlikView and Cognos for data warehouse; SAP,
Chapter: Sapiens: IDIT

SUN and Oracle for general ledger; Filenet and TIBCO for business process
management systems; Sapiens RI, DXC and SAP for reinsurance solutions; an internal
solution for billing systems; Sapiens RI, DXC and SAP for reinsurance systems;
Documerge and Doc1 for document management systems; Documerge and Doc1 for
document creation systems; it is country-specific for medical estimation tools; it is
country-specific for medical bill review; SalesForce and SAP for supplier networks and
portals; Google, MapFlow, and RIMS for geocoding solutions; SAP, SUN, and Oracle for
payments systems (disbursements); life related for illustrations; Outsystems and

235
Backbase for eapplications; an internal solution for new business and underwriting; an
internal solution for claims; an internal solution CRM, Siebel, MS Dynamics and
Salesforce for CRM; an internal solution for product calculation engine; SAP, SUN and
Oracle for distribution management; Outsystems and Backbase for producer portal (quick
quote, illustration, bind, issue); Outsystems and Backbase for prospective customer
portal (quick quote, illustration, bind, issue); and Outsystems and Backbase for
policyholder portal (inquiries and transactions for in-force policies).

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is required for new web service or
integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile with advanced
DevOps tools and methodologies of continuous development and release. A typical
project team of 5 to 15 people consists of resources from the insurer (25%), Sapiens
(60%) and at times external professional services firms (15%). Service-level agreements
are offered.

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

Sapiens offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based (not used often) pricing options. The license fees are typically based on
number of functional components/modules, number of concurrent users, number of total
or named users, premium volume, number of states or geographies, and enterprise
license / flat fee. The vendor will offer a fixed price implementation after an in depth Blue
Print study (typically 1-2 months) for scope definition while applying change strict control
process and contingency

The total cost to implement Sapiens IDIT can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 155: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €1 million to €5 million Under €500,000 22%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.
Chapter: Sapiens: IDIT

One year post N/A €500,000 to €2 million Under €500,000 22%


implementation costs
for the regional
insurance company.

236
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Assuming a four year €1 million to €5 million €3 million to €10 Under €500,000 22%
implementation million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A €1 million to €5 million Under €500,000 22%


implementation for a
European insurance
holding company

Source: Vendor

Chapter: Sapiens: IDIT

237
SEQUEL BUSINESS SOLUTIONS: ECLIPSE
UNDERWRITING

COMPANY
Sequel is a wholly owned subsidiary of Verisk Analytics Inc, headquartered in London,
UK with sales and professional services personnel located throughout the European,
Middle Eastern, and African region. Sequel’s business is providing software and services
to the insurance industry. The company has 180 employees, of which 110 are available
to provide professional services / client support for their PAS solution; 110 are physically
located in Europe, Middle East, and Africa.

The last user conference was a quarterly Innovation Forum, attended by representatives
for each of their customers.

Table 156: Company and Product Snapshot

COMPANY Annual corporate revenues US$26.76m

Year founded 1993

Exchanges/Symbols NASDAQ:VRSK (Parent)

Headquarters Location Global: London, UK

PAS SYSTEM Name Eclipse Underwriting

Current release and date of 4.25


release

Release intervals Minor enhancements: Quarterly


Major enhancements: Annually

Upgrades Insurers can skip one version (e.g., go from


version 4.0 to 6.0).
Vendor support for prior versions: They support

Chapter: Sequel Business Solutions: Eclipse Underwriting


current versions and up to two prior.

Target market Specialty business in Europe

Source: Vendor RFI

238
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
data services and ISO which require coding and assignment which is on the roadmap.

Figure 56: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered

Chapter: Sequel Business Solutions: Eclipse Underwriting


On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 22 insurer clients. The breakdown of the clients is as follows: Tier 3
(three clients), Tier 4 (15 clients), and Tier 5 (four clients).

Table 157: Customer Base

EUROPE, MIDDLE EAST, In production with current 22


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


United Kingdom 8

Existing client base by Europe:


country United Kingdom 22

239
Deployment method On Premise: 70%
(percentage of client base)
Hosted: 30%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Markel International,


Tokio Marine Kiln,
Brit.

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 158: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO Supported but not in production

HOMEOWNERS Supported but not in production

COMMERCIAL AUTO Supported but not in production

COMMERCIAL PROPERTY In production today 22

COMMERCIAL LIABILITY In production today 22

WORKERS COMP Not supported

BUSINESS OWNERS POLICY Supported but not in production

Source: Vendor RFI

TECHNOLOGY
Eclipse is an n-tier Microsoft.NET application which uses SQL Server (currently 2012) for

Chapter: Sequel Business Solutions: Eclipse Underwriting


the database. Eclipse currently supports Windows 7 and 8. Eclipse has been designed to
support deployment on a Citrix platform allowing thin terminal access from a client
device. If deployed in this way the whole application can be made available using Citrix
Secure Gateway (CSG) via the Internet with no browser compatibility issues.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 159: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: .NET (C#): 100%


Business users: .NET (C#): 90%
JavaScript: 10%
Developers: .NET (C#): 90%
JavaScript: 10%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS Microsoft Windows

240
TECHNOLOGY SPECIFICS

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; Other
XML; MQSeries, JMS or similar queue technology;
Flat files; Custom API
Public API integrations:

BUSINESS USER UI Main UI browser based: No


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: Yes
Windows interface available: Yes
Apple Mac interface available: Yes
Linux-based interface available: Yes
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 2,200 users and 2,000,000


policies

Source: Vendor RFI

The data model is proprietary. It supports flexible industry standard data model schemas.
The data model can be extended by carriers using the Sequel Portal. For the insurer to
make changes to the data model, a set of tools is provided that allow technical staff to
extend the data model and the SQL database schema. The data model can be released
to an insurer. It can be published to an insurer's data model and mapped to an
intermediate format.

Chapter: Sequel Business Solutions: Eclipse Underwriting


Carriers do not have access to core code; Insurance product definition, screen definition,
workflow definition, business rule definition, interface definition, data definition are
configurable using tools targeted for an IT user. Changes to the system are possible
through re-usable components, inheritance and other schemes. All product components
(including product features, coverages, benefits, transactions, rules and calculations) are
reusable for multiple products.

In Europe, Middle East, and Africa the system is pre-integrated with Sequel Portal for
agent portal software; Sequel Re for reinsurance solutions; Eclipse Underwriting for
billing systems, document creation systems and new business and underwriting;
Microsoft SharePoint for document management systems; Sequel Impact for geocoding
and aggregation solutions; Sequel Claims for claims management; Microsoft Dynamics
for CRM; Sequel Portal & Rating Engine for product calculation engine and producer
portal (quick quote, illustration, bind, issue).

Product changes can be analyzed using the configuration and development user
interface and can be tested using a specific tool provided. A restart of the system is not
required for any changes.

241
IMPLEMENTATION, PRICING, AND SUPPORT
The preferred implementation approach is Hybrid of Waterfall and Agile. A typical project
team varies in size but consists of resources from the insurer (20%) and Sequel (80%).
Service-level agreements are offered; a typical SLA ensures guaranteed turnaround
times on issues and support tickets based on priority/urgency.

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

Sequel offers term license pricing options. The license fees are typically based on
number of total or named users. The vendor will offer a fixed price implementation after
undertaking a full implementation study in advance, in order to understand the total
project scale.

The total cost to implement Eclipse Underwriting can vary according to the capabilities
and available resources of the client, and the overall scope of system use.

Table 160: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €500,000 to €1 million €500,000 to €1 million No cost, not Included in the
only: assuming a two applicable annual license
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A Under €500,000 No cost, not Included in the
implementation costs applicable annual license
for the regional
insurance company.

Chapter: Sequel Business Solutions: Eclipse Underwriting


Assuming a four year €1 million to €5 million €1 million to €5 million No cost, not Included in the
implementation applicable annual license
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A Under €500,000 No cost, not Included in the
implementation for a applicable annual license
European insurance
holding company

Source: Vendor

242
SSP LIMITED: SSP PURE INSURANCE

COMPANY
SSP is a privately owned company (with outside investors) headquartered in Halifax, UK
with sales and professional services personnel located throughout the North American
European, Middle Eastern and African regions. SSP’s business is providing software and
services to the insurance industry. The company has 900 employees, of which 170 are
available to provide professional services / client support for their PAS solution. They do
not provide an employee breakdown by region.

There are regional conferences conducted in the UK, Asia-Pacific, Africa, and North
America for customers at least annually. Events typically include closed user sessions,
blue sky input into product strategy, and external analyst sessions.

Table 161: Company and Product Snapshot

COMPANY Annual corporate revenues USD$105m Group

Year founded 2002

Exchanges/Symbols N/A

Headquarters Location Global: Halifax, UK

PAS SYSTEM Name SSP Pure Insurance

Current release and date of V4.2 April 2017


release

Release intervals Minor enhancements: Ever 6 months


Major enhancements: Every 6 months

Upgrades Insurers can skip one version (e.g., go from


version 4.0 to 6.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market Personal and Commercial Lines sub £100 million


GWP

Source: Vendor RFI

Chapter: SSP Limited: SSP Pure Insurance

243
OVERALL FUNCTIONALITY
A large amount of functionality is available out of the box. Exceptions include ACORD,
which is configurable using tools for an IT user; and document management,
reporting/analytics, workflow which are available with integration to third party
components; and multichannel/mobile, which are available as a pre-integrated digital
insurance solution.

Figure 57: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics
Multi
Workflow Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI Chapter: SSP Limited: SSP Pure Insurance

CUSTOMER BASE
SSP have a total of 51 insurer clients globally, of which 25 are on latest technology, with
most of the remaining clients either planning or implementing upgrades. Of the 51 clients,
29 are in the EMEA region with the breakdown as follows: Tier 3 (one1 client), Tier 4
(three clients), and Tier 5 (25 clients).

Table 162: Customer Base

EUROPE, MIDDLE EAST, In production with current 17


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 12


or more years old

244
New clients since 2015 Europe:
United Kingdom 1
Africa:
Zimbabwe 4
Kenya 1
Swaziland 1

Existing client base by Europe:


country United Kingdom 7
Gibraltar 1
Africa:
Kenya 2
Nigeria 2
South Africa 2
Zimbabwe 2
Botswana 1
Malawi 1
Tanzania 1
Mozambique 1
Uganda 1

Deployment method On Premise: 80%


(percentage of client base) Hosted: 20%

Percentage of clients using 0%


PAS through BPO services

Marquee clients MS Amlin,


Geo Underwriting,
Hollard

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 163: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In Production 11

HOMEOWNERS In Production 12

COMMERCIAL AUTO In Production 11

COMMERCIAL PROPERTY In Production 14 Chapter: SSP Limited: SSP Pure Insurance

COMMERCIAL LIABILITY In Production 18

WORKERS COMP Not Supported

BUSINESS OWNERS POLICY In Production 17

Source: Vendor RFI

TECHNOLOGY
The technical architecture is an end-to-end insurance application underpinned by
Microsoft technology.

SSP exploits Microsoft's R&D budget by integrating SSP Pure Insurance with Microsoft
components such as Office and SharePoint, and connectivity is made easy by the

245
availability of an open and fully documented web services layer made up of more than
300 XML web methods.

The UIs and process flows are not designed to be mobile device independent. The
solution does not natively support mobile apps.

Table 164: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


.NET (VB.net and C#)
Business users:
.NET (VB.net and C# - 90%): 90%
JavaScript: 10%
Developers:
.NET: 90%
JavaScript: 10%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Windows Server
2014

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: Other XML; Flat files
Public API integrations: Various including Google
Maps

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? No

API API documentation: Yes


Developer API portal: No Chapter: SSP Limited: SSP Pure Insurance
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: 600 users and over 300,000


policies
Proven to accommodate 1,800 users and 500,000
policies

Source: Vendor RFI

The data model is proprietary. The data model can be extended by carriers using tools.
For the insurer to make changes to the data model, a set of tools is provided that allow
technical staff to extend the data model and the SQL database schema. The data model
can be released to an insurer. It can be published to an insurer’s data model and mapped
to an intermediate format.

246
Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: Product, Claims, Case and Party Build, rating, rules,
documents, workflow, MI, and BI. Changes to the system are possible by defining
reusable parts that can be linked together.

In Europe, Middle East, and Africa the system is preintegrated with:

• AFD among others for address validation.


• Relationships with LexisNexis, IIL and Experian for data services.
• Proprietary fully integrated Agent Portal.
• Various roker/agent management systems including SSP Broking used by c700 UK
brokers.
• QlikView for business intelligence.
• Various General Ledger systems such as SUN Accounts, Sage, MS Dynamics, etc.
• MS SharePoint for document management.
• Kofax CCM for document creation.
• LexisNexis for geocoding.
• MS Dynamics for CRM.
• Temenos edgeConnect for customer and policyholder portal.
• E5 for Workflow.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested in a standard way using common tools. They provide
a set of prebuilt tests. A restart of the system is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 15 people consists of resources from the insurer (40%) and SSP (60%).
Service-level agreements are offered; a typical SLA includes response and resolution
timescales, availability, and performance metrics.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

SSP offers term license, based on GWP inclusive of software license and support. The
vendor will offer a fixed price implementation on defined project scope and detailed Chapter: SSP Limited: SSP Pure Insurance
requirements. Carriers may also need to license the following third party software:
QlikView.

247
The total cost to implement SSP Pure Insurance can vary according to the capabilities
and available resources of the client, and the overall scope of system use.

Table 165: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs £450k per annum £2m to £4m £0 Included in license


only: assuming a two-
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A £200k to £400k £0 Included in license


implementation costs
for the regional
insurance company.

Assuming a four-year £1m to £1.5m per £3m to £5m £0 Included in license


implementation annum
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A £250k to £500k £0 Included in license


implementation for a
European insurance
holding company

Source: Vendor

Chapter: SSP Limited: SSP Pure Insurance

248
SSP LIMITED: SSP SELECT INSURANCE

COMPANY
SSP is a privately owned company (with outside investors) headquartered in Halifax, UK
with sales and professional services personnel located throughout the North American,
European, African, and Asia-Pacific regions. SSP’s business is providing software and
services to the general insurance industry. The company has about 900 employees, of
which 250 are available to provide professional services / client support for their PAS
solution. They do not provide an employee breakdown by region.

SSP operates a global user conference for its Select Insurance customer base, which
meets at least annually to provide input to future product direction and gain insight to
development plans and release content.

Table 166: Company and Product Snapshot

COMPANY Annual corporate revenues $110M Group

Year founded 2002

Exchanges/Symbols N/A

Headquarters Location Global: Halifax, UK

PAS SYSTEM Name SSP Select Insurance

Current release and date of Release 4.2 December 2017


release

Release intervals Minor enhancements: Every 6 weeks


Major enhancements: Twice a year

Upgrades Insurers can skip one version (e.g. go from


version 4.0 to 6.0).
Vendor support for current versions and previous
(n -1)

Target market Personal & Commercials Lines, Direct & Broker


Channels

Source: Vendor RFI

Chapter: SSP Limited: SSP Select Insurance

249
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD
and ISO, which could be developed (would be considered customization).

Figure 58: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 5 insurer clients within EMEA. The breakdown of the clients is as Chapter: SSP Limited: SSP Select Insurance
follows: Tier 2 (one Client), Tier 3 (two clients), and Tier 5 (two clients).

Table 167: Customer Base

EUROPE, MIDDLE EAST, In production with current 5


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 0


or more years old

New clients since 2015 Europe:


United Kingdom 3

Existing client base by Europe:


country United Kingdom 4
Africa:
South Africa 1

250
Deployment method On Premise: 20%
(percentage of client base) Hosted: 20%
SaaS: 60%

Percentage of clients using 0%


PAS through BPO services

Marquee clients 1

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 168: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In Production 1

HOMEOWNERS In Production 3

COMMERCIAL AUTO In Production 2

COMMERCIAL PROPERTY In Production 2

COMMERCIAL LIABILITY In Production 2

WORKERS COMP Not Supported

BUSINESS OWNERS POLICY In Production 2

Source: Vendor RFI

TECHNOLOGY
The technical architecture is Microsoft .NET and JEE / Java.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 169: Technology Options

TECHNOLOGY SPECIFICS
Chapter: SSP Limited: SSP Select Insurance
CODE BASE Core technology:
JEE / Java
Business users:
Delivered as a SAAS Solution, therefore languages
the solution is built in is not relevant, however the
solution does not contain legacy languages: 100%
Developers:
Delivered as a SAAS Solution, therefore languages
the solution is built in is not relevant, however the
solution does not contain legacy languages.
Configuration by the insurer staff is managed via data
rather than languages.: 100%

OPERATING SYSTEMS Operating systems deployed on: All required


Operating Systems are included within the Solution
delivered as a service

251
TECHNOLOGY SPECIFICS

APPLICATION SERVERS All required Applicaton Servers included within the


Solution delivered as a service

DATABASES Preferred: None


Additional options: Oracle; DB2/UDB;

INTEGRATION METHODS Preferred: Web Services


Additional options: ACORD Standard XML; RESTful
HTTP style services; JSON format ; MQSeries, JMS
or similar queue technology; Flat files; Custom API
Public API integrations: Google Maps, Price
Comparison websites, Credit scoring Agencies,
Address Validation Services, Bank Validation
Services, Vehicle Validation Services, Insurers Data
Enrichment, FloodRE, MyLicense,SalesForce,
Guidewire Claims, Google Analytics, MID, ELTO,
LDAP, BACS, to name a few. In addition the
underlying ESB also has standard connectors to many
cloud based APIs

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: More than 3000 users and more


than 7 million policies

Source: Vendor RFI

All of the above is delivered “as a Service” with a series of product accelerators that

Chapter: SSP Limited: SSP Select Insurance


support fast time to market.

The data model for SSP Select Insurance is proprietary, although it was developed in line
with the IAA data model. However, because the product definition is controlled by the
customer, the product data model can support any industry standard required. The data
model can be extended by carriers using the SIAAS Product definition tool (Select
Composer), which allows the insurer to define their own product data model (either
bespoke or standards based) through a standard browser interface. The product
definition is then held within the metadata of the system and therefore does not require
traditional development. The Select Composer tool also supports full product versioning,
to allow different product versions to have different data models. For the insurer to make
changes to the data model, XML is used directly in the database, which allows the
customer to store any data in this format. The data model can be released to an insurer.
It can be published to an insurer’s data model and mapped to an intermediate format.
SSP provides a suite of “accelerator products” out of the box, complete with data model,
staff engagement centre (UI), customer portal (Quote & Buy and Self-Service), with
document template triggers and BI reporting feed.

252
Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and data definition. Interface definition is configurable
using tools targeted for an IT user. Changes to the system are possible by using
inheritance to help define products.

SSP provide Select Insurance as a component of its Digital Insurance Platform. The full
suite includes:

• User Experience Platform – SSP UXP


• Rating, Pricing and Data Enrichment Hub – SSP Intelligent Quotes Hub
• Application Fraud and Watch Lists – SSP Verify
• Core Policy, Finance and Claims Administration – SSP Select Insurance
• Document Fulfillment – SSP Customer Communication Management
• Enterprise Workflow – SSP Workflow
• Business Intelligent and Reporting – SSP Business Analytics
• Relationships with LexisNexis, IIL and Experian for data services
• Various General Ledger systems such as SUN Accounts, Sage, MS Dynamics etc

Product changes can be analyzed using an impact analysis tool that provides a report,
detailing products and channels affected, and can be tested in a standard way using
common tools. They provide a set of pre-built tests. A restart of the system is required for
change to underlying data model, new web service, or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 25 to 40 people consists of resources from the insurer (30%), SSP (50%),
and external professional services firms (20%).

The average time to get the first line of insurance live in a single jurisdiction is typically 7
to 12 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

SSP offers multiple pricing options. The license fees are typically based on either GWP
or price per policy (SaaS) over an agreed minimum term.

Chapter: SSP Limited: SSP Select Insurance


The total cost to implement SSP Select Insurance can vary according to the capabilities
and available resources of the client, and the overall scope of system use.

Table 170: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs £400k to £600k per £2m to £4m £0 Included in


only: assuming a two- annum License Fee
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

253
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A £150k to £300k £0 Included in


implementation costs License Fee
for the regional
insurance company.

Assuming a four year £1m to £2m £4m to £10m £0 Included in


implementation License Fee
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A £250k to £500k £0 Included in


implementation for a License Fee
European insurance
holding company

Source: Vendor

Chapter: SSP Limited: SSP Select Insurance

254
TATA CONSULTANCY SERVICES: TCS BANCS FOR
INSURANCE

COMPANY
TCS is a global information technology services, digital, and business-solutions publicly
traded company headquartered in Mumbai, India with sales and professional services
personnel located throughout the North American, European, Middle Eastern, and
African, Asia-Pacific, and Latin American regions. TCS provides software and services to
the insurance, banking, financial services, telecoms, manufacturing, media &
entertainment, retail & consumer goods, transportation, health care & life sciences,
energy & utilities, s-governance, travel & hospitality industries amongst others. The
company has 389,213 employees and has dedicated staff available to provide
professional services / client support for their PAS solution. They do not provide
employee breakdown by region.

The last user conference was a product user group, where TCS BaNCS customers came
together and collaborated on the future roadmap requirements.

Table 171: Company and Product Snapshot

COMPANY Annual corporate revenues $17.58 Billion for FY 2016-17, ending 31st March
2017

Year founded 1968

Exchanges/Symbols TCS is listed on the BSE and NSE in India.


BSE: 532540, NSE: TCS

Headquarters Location Global: Mumbai, India.

PAS SYSTEM Name TCS BaNCS for Insurance

Chapter: Tata Consultancy Services: TCS BaNCS for Insurance


Current release and date of Release 11.0.0 in March 2015
release

Release intervals Minor enhancements: Half Yearly


Major enhancements: Yearly
The above is the normal release frequency and
is subject to change.

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0)
Vendor support for prior versions: They support
all versions.

Target market UAE, Bahrain, Saudi Arabia, South Africa,


Europe. Tier-1,2,3, Greenfield

Source: Vendor RFI

255
OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD,
which is available with integration to a third party solution; data services, which is
configurable using tools for an IT user; rate analysis, which is not available; and
reporting/analytics, which is configurable using tools for a business user.

Figure 59: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor

Chapter: Tata Consultancy Services: TCS BaNCS for Insurance


module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

CUSTOMER BASE
They have a total of 11 insurer clients in EMEA. The breakdown of the clients is as
follows: Tier 3 (eight clients) and Tier 4 (three clients).

Table 172: Customer Base

EUROPE, MIDDLE EAST, In production with current 9


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 2


or more years old

256
Existing client base by Middle East:
country Bahrain 2
United Arab Emirates 2
Africa:
Tanzania 4
South Africa 1
Ethiopia 1
Kenya 1

Deployment method On Premise: 100%


(percentage of client base)

Percentage of clients using 0%


PAS through BPO services

Source: Vendor RFI

LINES OF BUSINESS SUPPORTED


Table 173: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 11

HOMEOWNERS In production today 2

COMMERCIAL AUTO In production today 11

COMMERCIAL PROPERTY In production today 11

COMMERCIAL LIABILITY In production today 11

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Supported but not in production

Chapter: Tata Consultancy Services: TCS BaNCS for Insurance


Source: Vendor RFI

TECHNOLOGY
The technical architecture is a browser-based, thin client based, and has a native HTML5
based client interface for end users. The technical architecture is parameter-driven,
component-based, and n-tier with integration capabilities and based on service-oriented
architecture. The core functionality is furnished through various functional modules. The
solution is fundamentally built on coarse grained services enabling easy adoption to
multiple channels, ensuring multifaceted customer contact. Most of the data
communicate in JSON format for fast and lightweight communication.

257
The UIs and process flows are designed to be mobile device independent. The solution
natively supports Apple (iOS), and Android. TCS is investing in Digital offerings like
Analytics, Chatbot, and Blockchain, which are currently in progress.

Table 174: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: Java: 60%


Ruby: 10%
Other (PL/SQL): 30%
Business users: Java: 60%
JavaScript: 10%
Other (PL/SQL): 30%
Developers: Java: 60%
Other (PL/SQL): 40%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: N/A

APPLICATION SERVERS N/A

DATABASES Preferred: Oracle (only option)


Additional options: None

INTEGRATION METHODS Preferred: RESTful HTTP style services; JSON format


; Custom API;
Additional options: Web Services; Other XML; Flat
files;
Public API integrations: NA

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No

Chapter: Tata Consultancy Services: TCS BaNCS for Insurance


Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: No

SCALABILITY Largest deployment: Over 3,500 users and 90 million


policies

Source: Vendor RFI

The data model has distinct submodels. The entire data storage concept is parameter-
centric, to make it generic for any LOB and geography.

Product and rules refers to product and its various attributes, rules, various parties
associated with it, risks, coverage, exclusions, validations, etc. Policy details refers to
policy and its various attributes, risks, coverage, documents, endorsement, any other
business event, invoice, and payment data. Claims refers to claims and its various
attributes, various parties associated with it, reserve, payment, recovery, and documents.
All the different stakeholders involved in the insurance company’s operation are defined

258
as a party (e.g., policyholders, prospects, third parties, service providers, organization
structure, actuaries, risk surveyors, loss adjusters). Their contacts, branches, relations,
and hierarchy are also maintained. Accounting relates to GL Chart of Accounts, all
accounting transactions, JVs and account balance maintenance. Re-Insurance refers to
Treaty set up and Re Insurance Accounting.

It supports a proprietary hybrid data model. The data model can be extended by carriers
using the user interface for product configuration and business rule management.
Therefore changes in data model may not be required frequently. However, if data model
change is required in any case, then the same needs to be done by TCS only. For the
insurer to make changes to the data model, a set of tools is provided that allow technical
staff to extend the data model and the SQL database schema. The data model is not
released to an insurer. It can be mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, screen definition, workflow
definition, business rule definition, and role-based security integration. Interface definition
and data definition are configurable using tools targeted for an IT user. Changes to the
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules,
and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa, TCS BaNCS for Insurance offers agent portal
software, agent management systems, e-signature, analytics solutions, business
intelligence systems, data warehouse, general ledger, reinsurance solutions, billing
systems, payment systems (disbursements), illustrations, an inhouse solution for e-
applications, new business and underwriting, claims, an inhouse solution for product
calculation engine and distribution management.

Product changes can be analyzed using the configuration and development user
interface and can be tested in a standard way using common tools. A restart of the
system is required for new product creation, new web service, or integration point.

Chapter: Tata Consultancy Services: TCS BaNCS for Insurance


IMPLEMENTATION, PRICING, AND SUPPORT
The preferred implementation approach Agile based on customer readiness. A typical
project team of 30 to 50 people consists of resources from the insurer (10 - 60%) and
TCS (40 – 90%). Service level agreements are offered; a typical SLA is level based and
priorities based.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

TCS offers term license, perpetual license, usage-based, SaaS, subscription, and
risk-based pricing options. The license fees are typically based on number of functional
components/modules, number of total or named users, premium volume, number of
states or geographies, enterprise license / flat fee, and per transaction. The vendor will
offer a fixed price implementation when the scope is known and requirement is clear.
Carriers may also need to license the following third-party software: application servers
such as Oracle Weblogic or IBM WebSphere and Oracle Database

The total cost to implement TCS BaNCS can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

259
TIA TECHNOLOGY: THE TIA SOLUTION

COMPANY
TIA is a privately owned company (with outside investors) headquartered in Copenhagen,
Denmark and in Africa in Johannesburg, with sales and professional services personnel
located throughout the North American, European, Middle Eastern, and African, Asia–
Pacific, and Latin American regions. TIA’s business is providing software and services to
the insurance industry. The company has 160 employees, of which 80 are available to
provide professional services / client support for their PAS solution. All are physically
located in Europe, Asia, and Africa.

TIA acquired InsurTech company goBundl in early 2018 and hereby moved into the
customer portal space. goBundl provides a self-service front end that empowers insurers
to build a smart, fluid digital customer journey. TIA acquired Assurator in 2017, a TIA
implementation partner with more than 10 years’ experience, which enables TIA to
accelerate the build of their in-house services organization.

They hold an annual user conference. The event is two conferences for business and IT
leaders in the insurance industry. The latest conference attended by over 200 customers
and partners was held in Berlin in September 2017. The conference focused on the
theme “Destination: Change,” which included a focus on the drivers and solutions for the
growing insurance ecosystem with regards to digitalization, business intelligence, fast
time to market with targeted bespoke insurance offerings, and how to leverage AI.

Table 175: Company and Product Snapshot

COMPANY Annual corporate revenues €24.8m

Year founded Development start in 1986; incorporated in 1996

Exchanges/Symbols N/A

Headquarters Location Global: Copenhagen, Denmark

PAS SYSTEM Name The TIA Solution

Current release and date of TIA 7.6 (April, 2018)


release

Release intervals Minor enhancements: Ever 2 months


Major enhancements: Every 6 months Chapter: TIA Technology: The TIA Solution
Upgrades Insurers can skip multiple versions (e.g., go
directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and up to two prior.

Target market TIA core markets are northern Europe and sub-
Saharan Africa and all P/C companies including
composites. The only exception is London
Market/Lloyds

Source: Vendor RFI

CELENT OPINION
As predicted in the last report, in this profile we see TIA returning to a vendor with a
wealth of new deals and growth. After a few years of turmoil TIA Technology is turning
around the company. TIA has always been a strong EMEA player as demonstrated by
260
their more than 40 installations. With new clients in double figures Celent believes the
new CEO has found a fruitful path taking TIA into this age of insurtech.

TIA continues to be a member of a small group of vendors that can claim to have
installed policy administration systems in Europe, Middle East, and Africa. The TIA install
base demonstrates a diversity of insurer sizes, insurance products, and markets.

The latest version of TIA continues to benefit from a modern, web-based user interface
that provides strong context to the user and easy navigation around the data in the
system. Configuration of products and the TIA Solution are also much improved over
previous versions. TIA is continuing to invest in the product with a number of initiatives
offering different means of integrating to and using the solution.

The TIA Solution is well-established, proven to be flexible and installed widely, a trend
Celent expects to continue with the latest version.

OVERALL FUNCTIONALITY
A standard set of base functionality is available out of the box. Exceptions include
ACORD, which is configurable using tools for an IT user; data services, which is available
with integration to a separate module; data upload, which requires coding; ISO, which
could be developed (would be considered customization); rate analysis and forms
management, which are available with integration to a third party solution; document
creation and reporting/analytics, which are available with integration to a separate
module; and multichannel/mobile, which is available with integration to a third party
solution.

Prepackage approach allows for quicker time to market with a predefined initial
implementation, and the flexibility to then extend the platform’s capabilities to meet
individual needs.

Chapter: TIA Technology: The TIA Solution

261
TIA Policy functionality enables comprehensive administration of insurance policies
supporting one-stop processing. The tasks that can be performed on policies embrace
quotations, re-quotation, conversion to new business, issuing of policies (ordinary and
master agreements), midterm adjustments (MTA) (backward or forward in time), change
of the first entry date, change of cover on different start dates for several policy lines in
one transaction, cancellation, multiple quotes on an in-force policy, and reinstatement.

Figure 60: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI Chapter: TIA Technology: The TIA Solution

CUSTOMER BASE
They have a total of 42 EMEA insurer clients. The breakdown of the clients is as follows:
Tier 3 (7 clients), Tier 4 (11 clients), and Tier 5 (24 clients).

Table 176: Customer Base

EUROPE, MIDDLE EAST, In production with current 10


AND AFRICA CUSTOMER release or any release less
BASE than four years old

In production with release four 32


or more years old

262
New clients since 2015 Europe:
Denmark 3
Norway 3
Poland 3
Germany 1
Iceland 1
Ireland 1
Africa:
South Africa 4
Angola 2

Existing client base by Global 2


country Europe:
Denmark 7
Norway 6
Poland 5
United Kingdom 4
Czech Republic 2
Finland 2
Netherlands 2
Estonia 1
Faroe Islands 1
Germany 1
Iceland 1
Ireland 1
Latvia 1
Lithuania 1
Portugal 1
Sweden 1
Africa:
South Africa 5
Angola 2
Namibia 2

Deployment method On Premise: 96%


(percentage of client base)
Hosted: 4%

Percentage of clients using 0%


PAS through BPO services

Marquee clients Codan (RSA),


Hollard,
KLP.

Source: Vendor RFI

CUSTOMER FEEDBACK
Five clients provided feedback on The TIA Solution. Two are Tier 5 insurers, two are Tier
4 insurers, and one chose not to disclose their size. Chapter: TIA Technology: The TIA Solution

In terms of the best things about the vendors, references noted the vendor was always
willing to assist and that TIA now has more skilled resources to support customers. In
terms of the TIA solution clients noted the ease of use, short time to implement, flexibility,
and a single system for both policy and claims.

In terms of areas to improve regarding the TIA solution, front end capabilities and
converting the UI. Many of these items are being addressed with recent acquisitions. In
addition, references noted they would like to see easy single sign on, as well as more
flexible document archive integration.

One reference noted that Affecto was their implementation partner of the TIA system and
their project managers and consultants were excellent, and some of them have now
joined TIA.

263
Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score, while portals for agents
and brokers was an area in need of improvement. Configurability scores were above
average, and within configurability products (design and maintenance) received the
highest score. Comments on the integration were above average, and within integration
your claim system(s) received the highest score. Regarding their technology experiences,
insurers gave above average marks, and within technology scalability of the solution
received the highest score. The implementation was rated above average overall, and
within implementation knowledge of your business received the highest score. Finally,
upport received above average scores, and within support knowledge of their solution
and relevant technology received the highest score.

Figure 61: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


3.26
Functionality

Support Configurability
3.81
4.08

Implementation Integration
4.13
3.87

Technology 3.96

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 177: Selected Lines of Business Supported

NUMBER OF CLIENTS IN Chapter: TIA Technology: The TIA Solution


LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 33

HOMEOWNERS In production today 33

COMMERCIAL AUTO In production today 27

COMMERCIAL PROPERTY In production today 25

COMMERCIAL LIABILITY In production today 25

WORKERS COMP In production today 22

BUSINESS OWNERS POLICY In production today 18

Source: Vendor RFI

264
TECHNOLOGY
The technical architecture is organized into a multitier architecture which separates core
transaction-centric business functionality from user interfaces and other integrations
points. The foundation tier is based on an Oracle database and encapsulates all TIA
business logic spanning policy, product, party, claims, account, and reinsurance. The
middleware tier relies on Oracle Fusion middleware and Java EE and is responsible for
hosting the user interfaces based on Oracle Application Development framework and for
exposing SOAP and REST web services. The consumer tier contains mobile and web-
based clients and other types of consumers. TIA allows for bulk import or export of data
using the TIA staging area that acts as a relay for data being transported between TIA
and its surroundings. Data can be processed using a queuing mechanism that allows
asynchronous processing and volume throttling to minimize the impact of external
communication on the overall system performance.

The integration points for the APIs are owned and maintained by TIA, which ensures
compatibility with future releases.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps but does offer a mobile web interface and a
RESTful API. TIA now offers digital offerings including “my Page,” which uses a different
technology stack including Java, Spring, and Angular. The following table describes the
core TIA solution.

Table 178: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


Java: 30%
PL/SQL: 70%
Business users:
Java: 100%
Developers:
Java: 30%
PL/SQL: 70%

OPERATING SYSTEMS Implemented in JEE/Java


Operating systems deployed on: All Windows and
Linux variants supported by Oracle for the underlying
Oracle Database and WebLogic platforms.

APPLICATION SERVERS Oracle WebLogic Server 10.3.6 (REST is using


WebLogic 12.2.)

DATABASES Preferred: Oracle (only option) Chapter: TIA Technology: The TIA Solution
Additional options: None

INTEGRATION METHODS Preferred: REST


Additional options: SOAP based SOA Services
Public API integrations: Primary interface

265
TECHNOLOGY SPECIFICS

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: No
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
different size screens? Yes

Source: Vendor RFI

The data model is relational model. It supports flexible fields, and the data model can be
extended by carriers using these flexible fields. For the insurer to make changes to the
data model, they can use the flexible fields or extend the data model. TIA makes the data
model available to customers as a document.

Carriers do have access to core code but should not be changed directly for
upgradeability reasons; configuration tools targeted to a business user are available for
the following: data definition and roles based security integration. Data definition and
roles based security integration are configurable using tools targeted for an IT user. Data
definition and roles based security integration are configurable through a scripting
language. Data definition and roles based security integration require coding. Data
definition and roles based security integration are not available. Data definition and roles
based security integration are not applicable. Changes to the system are possible by
copying and pasting between products.

In Europe, Middle East and Africa the system is pre-integrated with:

Google Places and country specific software for address verification, and Google Places
for geocoding solutions.

• 2021.ai for analytics signature.


• TIA BI Cloud plus standard ETL process for business intelligence systems, plus a
standard ETL process for data warehouse.
• An inhouse solution for data mastery and master data management tools.
• An inhouse solution, Oracle and SAP for general ledger. Chapter: TIA Technology: The TIA Solution
• An inhouse solution for business process management systems.
• An inhouse solution for document management and document creation.
• An inhouse solution for product calculation engine.
• TIA reinsurance for reinsurance solutions.
• TIA Account and Payment/Collection for billing systems and disbursements.
• TIA sales and distribution for new business and underwriting and distribution
management.
• TIA claims for claims.
• Dynamics CRM and Salesforce for CRM.
• SI partners deliver portal for producer portal (quick quote, illustration, bind, issue), for
prospective customer portal (quick quote, illustration, bind, issue) and for policyholder

266
portal (inquiries and transactions for in-force polices).

A restart of the system is not required for any changes to the TIA Solution

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. A typical
project team of 4 to 30 people consists of resources from the insurer (20%), TIA (40%),
and external professional services firms (40%). Service-level agreements are offered; a
typical SLA includes scope Application Management, covering Application Support and
Application Enhancements. SLA are agreed individually (selected, standard SLA are
defined in TIA Support Lifecycle Policy).

The average time to get the first line of insurance live in a single jurisdiction is typically 1
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months.

TIA offers term license, perpetual license, usage-based, SaaS, subscription, risk-based
and the customers’ GWP in production pricing options. The license fees are typically
based on number of functional components/modules, premium volume, number of states
or geographies, enterprise license / flat fee, and per transaction. Carriers may also need
to license the following third party software: Oracle DB and Oracle Application server for
UI.

The total cost to implement the TIA Solution can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 179: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs €1 million to €5 million €1 million to €5 million Under €500,000 20%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

Chapter: TIA Technology: The TIA Solution


One year post N/A Under €500,000 Under €500,000 20%
implementation costs
for the regional
insurance company.

Assuming a four year €1 million to €5 million €1 million to €5 million Under €500,000 20%
implementation
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

267
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post N/A Under €500,000 Under €500,000 20%


implementation for a
European insurance
holding company

Source: Vendor

Chapter: TIA Technology: The TIA Solution

268
TOTAL SYSTEMS PLC: BLUESCAPE

COMPANY
Total Systems is a privately owned company headquartered in London, UK with sales
and professional services personnel located throughout the European, Middle Eastern,
and African region. Total Systems’ business is providing software and services to the
insurance industry. The company has 30 employees, of which 18 are available to provide
professional services / client support for their PAS solution; 18 are physically located in
Europe, Middle East, and Africa.

Table 180: Company and Product Snapshot

COMPANY Annual corporate revenues Over 2,200,000 GBP

Year founded 1971

Exchanges/Symbols Not Applicable

Headquarters Location Global: Islington, London EC1V 2QA

PAS SYSTEM Name bluescape

Current release and date of Version 3 - released 2016


release

Release intervals Minor enhancements: Every 6 months


Major enhancements: Every year

Upgrades Insurers can skip multiple versions (e.g., go


directly from version 4.0 to version 7.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market All Tiers, from Tier 1s to start-ups including


intermediaries

Source: Vendor RFI

CELENT OPINION
With Bluescape, Total Systems offers a modern, configurable system well suited to
distributing new products quickly, even with complex rating requirements. This capability
makes the solution of interest to brokers, MGAs, and increasingly to insurers themselves. Chapter: Total Systems PLC: Bluescape
Indeed the marquee client offered here acts as a price comparison website in its local
country.

Insurers looking at Total Systems and Bluescape could be forgiven for thinking this is a
new insurtech on the scene. In truth, Total Systems has been building insurance systems
at the distribution end of the value chain for years, with appearances with the Ultima
product even in our 2009 report, Policy Administration Systems for General Insurers in
Europe 2009.

In both the operational and configuration screens Bluescape offers a modern look and
feel. Total Systems demonstrated portals aimed at customers, agents, brokers, IFAs, and
an aggregator. These were of course, all modern looking web-based interfaces for
undertaking data capture, managing policies, quotes and where relevant, customer
details. The configuration tool demonstrated is a thick client, Windows-based tool for
managing the rating structure of the product. Workflow is managed through using
269
Microsoft’s Workflow Foundation which brings with it familiar workflow structures and a
basis for a configurable rules engine.

Given the increasing interest in systems that are cost-effective for launching new
products from brokers, MGAs, primary insurers, and reinsurers, Total Systems is well
positioned for growth with Bluescape.

OVERALL FUNCTIONALITY
The majority of the functionality is available out of the box. Exceptions include ACORD
and data services, which are configurable using tools for a business user; assignment,
which is configurable using tools for an IT user; reinsurance, which is under development;
and multiple insurers, which is configurable using tools for a business user.
Multichannel/mobile is available; however, integration to a third party solution is required
for mobile apps.

Figure 62: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Reporting/Analytics Workflow Multi-
Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor Chapter: Total Systems PLC: Bluescape
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable

Source: Vendor RFI

270
CUSTOMER BASE
They have a total of 4 clients. All clients are Tier 5.

Table 181: Customer Base

EUROPE, MIDDLE EAST, In production with current 4


AND AFRICA CUSTOMER release or any release less
BASE than four years old

New clients since 2015 Europe:


United Kingdom 1
Africa:
Zimbabwe 1

Existing client base by Europe:


country United Kingdom 3
Africa:
Zimbabwe 1

Deployment method Hosted: 100%


(percentage of client base)

Marquee clients ZimSelector

Source: Vendor RFI

CUSTOMER FEEDBACK
Three clients provided feedback on Bluescape. All three are Tier 5 insurers. Two
references have used the solution for 1 to 3 years, one for more than 3 years. Two
references use the solution for all or mostly personal lines, one for a mix of personal and
commercial lines.

In terms of the best thing about the vendor, references commented on their competence,
knowledge and experience of the insurance market, and their flexibility. In terms of the
system, references noted the flexibility of the system, particularly in terms of
customization products and variants.

In terms of areas to improve, one reference commented that they look forward to
migrating their front end to the one from Total Systems and wished it had existed earlier
in their development.

Chapter: Total Systems PLC: Bluescape

271
Functionality received above average scores overall. Configurability scores were above
average, and within configurability products (design and maintenance) received the
highest score. Comments on the integration were above average. Regarding their
technology experiences, insurers gave above average marks. The implementation was
rated above average overall, and within implementation responsiveness (handling of
issue resolution) received the highest score. Finally, support received above average
scores.

Figure 63: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality 5.00

Support Configurability
5.00 4.92

Implementation Integration
4.95 5.00

Technology5.00

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 182: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1


Chapter: Total Systems PLC: Bluescape
HOMEOWNERS In production today 1

COMMERCIAL AUTO Supported but not in production

COMMERCIAL PROPERTY Supported but not in production

COMMERCIAL LIABILITY Supported but not in production

WORKERS COMP Supported but not in production

BUSINESS OWNERS POLICY Supported but not in production

Source: Vendor RFI

272
TECHNOLOGY
Written in Microsoft .NET with SQL Server as the underlying database, Bluescape is a
true service-oriented architecture solution. Each business component (Rating, Quote,
Policy, Claims) is a self-contained entity and separates the database layer, the data
access layer (authentication and logical data exchange), the business objects layer
(which interacts with the data access layer via method calls), and the web service layer
which interacts with the website/portal via XML messages.

The UIs and process flows are designed to be mobile device independent. The solution
supports mobile apps through web service integration.

Table 183: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology:


C: 100%
Business users:
.NET (C#): 100%
Developers:
.NET (C# 80%, VB.NET 20%): 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Not Applicable

APPLICATION SERVERS Not Applicable

DATABASES Preferred: Microsoft SQL Server (only option)


Additional options: None

INTEGRATION METHODS Preferred: Web Services


Additional options: Other XML; JSON format ; Custom
API
Public API integrations: Site specific requirement. Not
yet done in core solution

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface: No
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: Yes
Windows interface available: No
Apple Mac interface available: Yes
Linux-based interface available: Yes Chapter: Total Systems PLC: Bluescape
Is the design of the user interface responsive to
different size screens? Yes

API API documentation: Yes


Developer API portal: No
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 822 users and over 20,000 policy


quotes

Source: Vendor RFI

The data model is a “Risk” data model that is a soft/freeform XML Schema defined by
each site. A default(s) is available for a range of standard lines of business (e.g., Motor,
Household, Travel, Health, Protection, Indemnity, etc.) that sites can adopt, adapt,
extend, or replace. The remaining application data model is proprietary. No industry
273
standard data model is employed, but they can support through the configuration of the
XML during implementation if an industry standard is required. The data model can be
extended by carriers using application configuration tools. For the insurer to make
changes to the data model, the XML Schema Editor is used to configure the risk data.
The data model can be released to an insurer. It can be published to an insurer’s data
model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, workflow definition, business
rule definition, data definition, and role-based security integration. Screen definition and
interface definition are configurable using tools targeted for an IT user. Changes to the
system are possible through reusable components, inheritance, and other schemes. All
product components (including product features, coverages, benefits, transactions, rules,
and calculations) are reusable for multiple products.

In Europe, Middle East, and Africa, the system is preintegrated with PCA Predict for
address verification; an inhouse solution for agent portal software; an inhouse solution for
agent management systems; WorldPay and BACS for billing systems; Invu for document
management systems; an inhouse solution for document creation systems; multiple
Insurer Quoting web services for supplier networks and portals; BACS for payments
systems (disbursements); an inhouse solution for illustrations; for applications; an
inhouse solution for new business and underwriting; an inhouse solution for claims; an
inhouse solution for CRM; an inhouse solution for product calculation engine; an inhouse
solution for producer portal (quick quote, illustration, bind, issue); an inhouse solution for
prospective customer portal (quick quote, illustration, bind, issue) and PCA Predict for
other.

Product changes can be analyzed using testing tools provided that help evaluate the
impact of change and can be tested using a specific tool provided. A restart of the system
is not required for any changes.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is a hybrid of Waterfall and Agile. For a project
deploying all the insurance components (Rating, Quote, Policy, and Claims), a typical
project team of about 10 people consists of resources from the insurer (50%) and Total
Systems (50%). Service-level agreements are offered; a typical SLA sets out how the
software will be supported based on the severity of incidents raised.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 1 to 3 months. Chapter: Total Systems PLC: Bluescape

274
Total Systems offers term license, perpetual license, usage-based, SaaS, subscription,
and risk-based pricing options. The license fees are typically based on number of
functional components/modules, number of concurrent users, number of total or named
users, premium volume, number of states or geographies, enterprise license / flat fee, per
transaction, and other usage-based factors. The vendor will offer a fixed price
implementation for the parts of the implementation that are completely within their control
The total cost to implement Bluescape can vary according to the capabilities and
available resources of the client, and the overall scope of system use.

Table 184: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs Under €500,000 €500,000 to €1 million No cost, not Support fees
only: assuming a two applicable commence from
year project for a go live
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

One year post N/A No cost, not No cost, not 20%


implementation costs applicable applicable
for the regional
insurance company.

Assuming a four year €500,000 to €1 million €1 million to €5 million No cost, not 25%
implementation applicable
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post N/A No cost, not No cost, not 25%


implementation for a applicable applicable
European insurance
holding company

Source: Vendor
Chapter: Total Systems PLC: Bluescape

275
ZOV SOLUTIONS OOD: SID

COMPANY
Zov Solutions is a privately owned company headquartered in Sofia, Bulgaria with sales
and professional services personnel located throughout the European, Middle Eastern,
and African region. Zov Solutions provides software and services to the insurance
industry. The company has 18 employees, of which 15 are available to provide
professional services / client support for their PAS solution. Fifteen are physically located
in Europe, Middle East, and Africa.

Table 185: Company and Product Snapshot

COMPANY Annual corporate revenues US$1.0 million

Year founded 2000

Exchanges/Symbols N/A

Headquarters Location Global: Sofia, Bulgaria

PAS SYSTEM Name SID

Current release and date of SID4: Release 17.1.14 from 20/06/2017


release

Release intervals Minor enhancements: Client-driven -- from


quarterly releases to continuous delivery
Major enhancements: Once in 5 years

Upgrades Insurers can skip one version (e.g., go from


version 4.0 to 6.0).
Vendor support for prior versions: They support
current versions and more than two prior but not
all versions.

Target market MGAs operating in the London Market and pan-


European insurers writing primarily commercial
risks and SME business.

Source: ZOV

CELENT OPINION
ZOV is a pan-European vendor although with little concentration in any one country in
Europe. With wins in the United Kingdom and Eastern Europe, SID continues to
demonstrate appeal to insurers across Europe.
Chapter: Zov Solutions OOD: SID

Since the last report ZOV Solutions have built a web-based front end, aimed at MGA
style requirements. The web-based interface follows the design of the thick client and
offers a simple, functional design with a consistent context shown on the left of the
screen. Some functions are still offered in the simple Windows-based interface.

An area on the left is given over to context with most of the screen given over to the work
or task area. The SID interface makes use of the UI features you would expect in a thick
client such as context sensitive right-clicks — as a result, the interface looks quite simple
with functions available in the relevant screens. Configuration of screen flow is done in
the same interface — although these screens are necessarily more complex in nature.

276
This year ZOV Solutions names more European insurers as marquee clients and has
clearly been busy. Mergers and acquisitions in Europe have both helped and hindered
ZOV Solutions. ZOV Solutions remains a solid European vendor with good commercial
insurance experience in the territory in multiple countries, who is clearly investing in their
offerings for the insurance industry.

OVERALL FUNCTIONALITY
All of the functionality is available out of the box except for ISO, which would be
considered customization.

Figure 64: Functionality

Suite Functionality Features and Functions


Quote ACORD Data Services
Billing

Data Upload Underwriting Assignment


Claims

Renewals Endorsement Rating


CRM
ISO Product Management

Reinsurance
Rate Analysis Reinsurance
Rating
Engine
Multiple Insurers Forms Management Document
Management
Distribution
Management
Document Creation Scheduling/Calendar/Diary

Business
Intelligence Workflow Multi-
Reporting/Analytics Channel/Mobile

Yes – integrated into Available out of the box Available with integration to a separate
the policy admin module provided by this vendor
module Available with integration to a third- Configurable using simple tools
party solution targeted for a business user
Yes – separate module Configurable using tools targeted to IT Configurable through a scripting
users language
Yes – through a formal Coding required Under Development
partnership with
another vendor Could develop (would be considered
On the roadmap customization)
No Not available Not applicable
Chapter: Zov Solutions OOD: SID

Source: ZOV

CUSTOMER BASE
ZOV have a total of 10 insurer clients. The breakdown of the clients is as follows: Tier 4
(one client) and Tier 5 (nine clients).

Table 186: Customer Base

EUROPE, MIDDLE EAST, In production with current 9


AND AFRICA CUSTOMER release or any release less
BASE than four years old

277
In production with release four 1
or more years old

New clients since 2015 Europe:


Slovakia 1
United Kingdom 1

Existing client base by Europe:


country Bulgaria 1
Denmark 1
France 1
Germany 1
Hungary 1
Italy 1
Slovakia 1
Spain 1
Sweden 1
United Kingdom 1

Deployment method On Premise: 100%


(percentage of client base)

Percentage of clients using None


PAS through BPO services

Marquee clients QBE European Operations,


Colonnade Insurance,
Sciemus Ltd. UK

Source: ZOV

CUSTOMER FEEDBACK
Three clients provided feedback on SID. Two are Tier 5 insurers, and one is a Tier 3
insurer. Two references have been using the solution for more than three years, and one
is still implementing the solution. Two references use the solution for all or mostly
commercial lines, one reference for a mix of personal and commercial lines.

In terms of the best thing about the vendor references noted support, responsiveness,
and price (although that may also have been directed at the system). In terms of the
system, references noted performance and flexibility.

In terms of things that could be improved about the system, one reference simply replied
they needed to upgrade to SID4. In terms of the vendor, one reference wanted to see
improvements in implementation support and cost of work order requests.
Chapter: Zov Solutions OOD: SID

278
Functionality received above average scores overall, and within functionality processing
new business (mostly automated) received the highest score, while tools for managers
was an area in need of improvement. Configurability scores were above average, and
within configurability products (design and maintenance) received the highest score.
Comments on the integration were above average. Regarding their technology
experiences, insurers gave above average marks, and within technology ease of system
maintenance received the highest score. The implementation was rated above average
overall, and within implementation responsiveness (handling of issue resolution) received
the highest score. Finally, Support received above average scores, and within support
responsiveness (handling of issue resolution) received the highest score.

Figure 65: Customer Feedback

Customer average rating (1=very poor; 5=excellent)


Functionality
3.90

Support Configurability
4.59 4.19

Implementation Integration
4.43
5.00

Technology 4.17

Source: 2017 Celent PAS customer feedback survey

LINES OF BUSINESS SUPPORTED


Table 187: Selected Lines of Business Supported

NUMBER OF CLIENTS IN
LINE OF BUSINESS AVAILABILITY PRODUCTION IN EMEA

PERSONAL AUTO In production today 1


Chapter: Zov Solutions OOD: SID

HOMEOWNERS In production today 2

COMMERCIAL AUTO In production today 3

COMMERCIAL PROPERTY In production today 9

COMMERCIAL LIABILITY In production today 9

WORKERS COMP In production today 8

BUSINESS OWNERS POLICY In production today 9

Source: Vendor RFI

279
TECHNOLOGY
SID is a horizontally scalable, cloud-ready, and operations-friendly non-life insurance
software system with web and native user interfaces. The system provides wide breadth
of functionality, deep configurability, and extensibility with time-tested robustness and
stability.

SID provides rich ability to interface with other systems. SID exposes and consumes
SOAP and REST web services, has ability to export and import files in wide range of
formats, and has mature frameworks for creating new interface points.

The UIs and process flows are designed to be mobile device independent. The solution
does not natively support mobile apps.

Table 188: Technology Options

TECHNOLOGY SPECIFICS

CODE BASE Core technology: .NET (C#): 100%


Business users: .NET (C#): 100%
Developers: .NET (C#): 100%

OPERATING SYSTEMS Implemented in Microsoft .NET


Operating systems deployed on: Microsoft Windows

APPLICATION SERVERS Microsoft Windows

DATABASES Preferred: Microsoft SQL Server;


Additional options: Oracle;

INTEGRATION METHODS Preferred: Web Services:


Additional options: ACORD Standard XML; Other
XML; RESTful HTTP style services; JSON format ;
MQSeries, JMS or similar queue technology; Flat files;
Custom API;
Public API integrations: Google Maps, Google Charts,
European Central Bank, MS Azure Machine Learning
API

BUSINESS USER UI Main UI browser based: Yes


All functions available through a browser interface:
Yes
Interactive UI through the use of JavaScript or similar
technology: Yes
Main UI thick client based: No
Windows interface available: Yes
Apple Mac interface available: No
Linux-based interface available: No
Is the design of the user interface responsive to
Chapter: Zov Solutions OOD: SID

different size screens? Yes

API API documentation: Yes


Developer API portal: Yes
Manage access to APIs and track API usage by
developers: Yes

SCALABILITY Largest deployment: 1,600 including 70 internal users,


1,530 external TP users. Customers of third parties
using web services are not included in the number.

Source: ZOV

280
The data model is derived from object model and not stored separately. The core of the
system is object model — the same principle as Microsoft Entity Framework. It supports
SID uses a proprietary data model. The data model can be extended by carriers by
modifying the source code. For the insurer to make changes to the data model, a number
of extension points in the data model are provided where the customer can store data of
their choosing. The number of slots is limited, and the underlying schema cannot be
changed except by changing code. The data model can be released to an insurer. It can
be published to an insurer’s data model and mapped to an intermediate format.

Carriers do not have access to core code; configuration tools targeted to a business user
are available for the following: insurance product definition, workflow definition, business
rule definition, interface definition, and role-based security integration. Screen definition
and data definition require coding. Changes to the system are possible by defining
reusable parts that can be linked together.

In Europe, Middle East, and Africa the system is preintegrated with London Market
Messages (ACORD) for third party data services (e.g., lexisnexis, iso, etc.); Oracle
Financials, PeopleSoft, SUN GL for general ledger; RISys for reinsurance systems; KC
Kcenter DMS, Oracle DMS for document management systems; EurotaxGlass (Vehicle
data) and; eVn Motor Bureau is used as well.

Product changes can be analyzed using the configuration and development user
interface and can be tested using a specific tool with a set of prebuilt tests. A restart of
the system is required for new web service or integration point.

IMPLEMENTATION, PRICING, AND SUPPORT


The preferred implementation approach is Agile. A typical project team of 10 to 20 people
consists of resources from the insurer (30%), Zov Solutions (40%), and external
professional services firms (30%). Service-level agreements are offered; a typical SLA
includes Support Services are subject to SLAs.

The average time to get the first line of insurance live in a single jurisdiction is typically 4
to 6 months depending on the integration requirements and the level of configuration
required, with second and subsequent lines taking 1 to 3 months in the same jurisdiction.
Second and subsequent jurisdiction implementations typically take 4 to 6 months.

ZOV Solutions offers term license and perpetual license pricing options. The license fees
are typically based on number of concurrent users, number of total or named users,
premium volume, and enterprise license / flat fee. The vendor will offer a fixed price
implementation when scope of implementation is agreed.

The total cost to implement SID can vary according to the capabilities and available
resources of the client, and the overall scope of system use.
Chapter: Zov Solutions OOD: SID

Table 189: Pricing Estimates

INSURER THIRD PARTY MAINTENANCE


SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

Implementation costs Under €500,000 Under €500,000 Under €500,000 20%


only: assuming a two
year project for a
regional insurance
company that writes
in the United Kingdom
for eight lines of
business, producing
an annual GWP of
€250 million.

281
INSURER THIRD PARTY MAINTENANCE
SCENARIO LICENSING VENDOR FEES FEES FEE / OTHER

One year post Not applicable Not applicable Not applicable Not applicable
implementation costs
for the regional
insurance company.

Assuming a four year €1 million to €5 €1 million to €5 €1 million to €5 20%


implementation million million million
period, for a
European insurance
holding company,
which has four
companies, writes in
five countries (France,
Germany, Italy, Spain,
UK), across 24 lines
of business and has
GWP of €2.5 billion.

One year post Not applicable Not applicable Not applicable Not applicable
implementation for a
European insurance
holding company

Source: ZOV

Chapter: Zov Solutions OOD: SID

282
CONCLUDING THOUGHTS

FOR INSURERS
There is no single best policy administration solution for all insurers. There are a number
of good choices for an insurer with almost any set of requirements. An insurer seeking a
new policy administration system should begin the process by looking inward. Every
insurer has its own unique mix of lines of business, geography, staff capabilities,
business objectives, and financial resources. This unique combination, along with the
organization’s risk appetite, will influence the list of vendors for consideration.

Some vendors are a better fit for an insurance company with a large IT group that is
deeply proficient with the most modern platforms and tools. Other vendors are a better fit
for an insurance company that has a small IT group and wants a vendor to take a leading
role in maintaining and supporting its applications.

Most policy administration systems bring some level of out-of-the-box functionality for
various lines of business and operating models. Many systems offer powerful
configuration tools to build capabilities for both known and future requirements.

We recommend that insurers that are looking for a policy administration system narrow
their choices by focusing on four areas:

• The functionality needed and available out of the box for the lines of business and
states desired. Check to see what is actually in production.
• The technology — both the overall architecture and the configuration tools and
environment.
• The vendor’s stability, knowledge, and investment in the solution.
• Implementation and support capabilities and experience.

FOR VENDORS
As a group, vendors continue to make significant investments in their policy
administration systems. The solutions are delivering more functionality, improving
configuration tools, and are more connected, with SOA and web services becoming the
de facto standard. Although these trends are all very good news for insurers, they do
make the competitive challenges facing vendors that much more daunting.
Celent recommends vendors differentiate themselves by:

• Focusing on improving usability for both new and experienced users and managers.
• Making implementation faster and less expensive.
• Continuing to build out configuration environments to put change controls in the
hands of the carriers.
Chapter: Concluding Thoughts

Was this report useful to you? Please send any comments, questions, or suggestions for
upcoming research topics to [email protected].

283
LEVERAGING CELENT’S EXPERTISE

If you found this report valuable, you might consider engaging with Celent for custom
analysis and research. Our collective experience and the knowledge we gained while
working on this report can help you streamline the creation, refinement, or execution of
your strategies.

SUPPORT FOR FINANCIAL INSTITUTIONS


Typical projects we support related to policy administration systems include:

Vendor short listing and selection. We perform discovery specific to you and your
business to better understand your unique needs. We then create and administer a
custom RFI to selected vendors to assist you in making rapid and accurate vendor
choices.

Business practice evaluations. We spend time evaluating your business processes,


particularly in [list several here]. Based on our knowledge of the market, we identify
potential process or technology constraints and provide clear insights that will help you
implement industry best practices.

IT and business strategy creation. We collect perspectives from your executive team,
your front line business and IT staff, and your customers. We then analyze your current
position, institutional capabilities, and technology against your goals. If necessary, we
help you reformulate your technology and business plans to address short-term and long-
term needs.

SUPPORT FOR VENDORS


We provide services that help you refine your product and service offerings.
Examples include:

Product and service strategy evaluation. We help you assess your market position in
terms of functionality, technology, and services. Our strategy workshops will help you
target the right customers and map your offerings to their needs.

Market messaging and collateral review. Based on our extensive experience with your
potential clients, we assess your marketing and sales materials — including your website
and any collateral.
Chapter: Leveraging Celent’s Expertise

284
RELATED CELENT RESEARCH

The New Recipe that Is Changing Insurance


February 2018

The New Build Vs. Buy Debate


February 2018

Honey I Shrunk the Microservices


December 2017

North American Policy Administration Systems 2018: Personal, Commercial, and


Specialty ABCD Vendor View
February 2018

Chapter: Related Celent Research

285
Copyright Notice
Prepared by

Celent, a division of Oliver Wyman, Inc.


Copyright © 2018 Celent, a division of Oliver Wyman, Inc., which is a wholly owned
subsidiary of Marsh & McLennan Companies [NYSE: MMC]. All rights reserved. This
report may not be reproduced, copied or redistributed, in whole or in part, in any form or
by any means, without the written permission of Celent, a division of Oliver Wyman
(“Celent”) and Celent accepts no liability whatsoever for the actions of third parties in this
respect. Celent and any third party content providers whose content is included in this
report are the sole copyright owners of the content in this report. Any third party content
in this report has been included by Celent with the permission of the relevant content
owner. Any use of this report by any third party is strictly prohibited without a license
expressly granted by Celent. Any use of third party content included in this report is
strictly prohibited without the express permission of the relevant content owner This
report is not intended for general circulation, nor is it to be used, reproduced, copied,
quoted or distributed by third parties for any purpose other than those that may be set
forth herein without the prior written permission of Celent. Neither all nor any part of the
contents of this report, or any opinions expressed herein, shall be disseminated to the
public through advertising media, public relations, news media, sales media, mail, direct
transmittal, or any other public means of communications, without the prior written
consent of Celent. Any violation of Celent’s rights in this report will be enforced to the
fullest extent of the law, including the pursuit of monetary damages and injunctive relief in
the event of any breach of the foregoing restrictions.
This report is not a substitute for tailored professional advice on how a specific financial
institution should execute its strategy. This report is not investment advice and should not
be relied on for such advice or as a substitute for consultation with professional
accountants, tax, legal or financial advisers. Celent has made every effort to use reliable,
up-to-date and comprehensive information and analysis, but all information is provided
without warranty of any kind, express or implied. Information furnished by others, upon
which all or portions of this report are based, is believed to be reliable but has not been
verified, and no warranty is given as to the accuracy of such information. Public
information and industry and statistical data, are from sources we deem to be reliable;
however, we make no representation as to the accuracy or completeness of such
information and have accepted the information without further verification.
Celent disclaims any responsibility to update the information or conclusions in this report.
Celent accepts no liability for any loss arising from any action taken or refrained from as a
result of information contained in this report or any reports or sources of information
referred to herein, or for any consequential, special or similar damages even if advised of
the possibility of such damages.
There are no third party beneficiaries with respect to this report, and we accept no liability
to any third party. The opinions expressed herein are valid only for the purpose stated
herein and as of the date of this report.
No responsibility is taken for changes in market conditions or laws or regulations and no
obligation is assumed to revise this report to reflect changes, events or conditions, which
occur subsequent to the date hereof.
For more information please contact [email protected] or:

Craig Beattie [email protected]

AMERICAS EUROPE ASIA

USA France Japan

200 Clarendon Street, 12th Floor 28, avenue Victor Hugo The Imperial Hotel Tower, 13th Floor
Boston, MA 02116 Paris Cedex 16 1-1-1 Uchisaiwai-cho
75783 Chiyoda-ku, Tokyo 100-0011
Tel.: +1.617.262.3120
Fax: +1.617.262.3121 Tel.: +33.1.73.04.46.20 Tel: +81.3.3500.3023
Fax: +33.1.45.02.30.01 Fax: +81.3.3500.3059

USA United Kingdom China

1166 Avenue of the Americas 55 Baker Street Beijing Kerry Centre


New York, NY 10036 London W1U 8EW South Tower, 15th Floor
1 Guanghua Road
Tel.: +1.212.541.8100 Tel.: +44.20.7333.8333 Chaoyang, Beijing 100022
Fax: +1.212.541.8957 Fax: +44.20.7333.8334
Tel: +86.10.8520.0350
Fax: +86.10.8520.0349

USA Italy Singapore

Four Embarcadero Center, Suite 1100 Galleria San Babila 4B 8 Marina View #09-07
San Francisco, CA 94111 Milan 20122 Asia Square Tower 1
Singapore 018960
Tel.: +1.415.743.7900 Tel.: +39.02.305.771
Fax: +1.415.743.7950 Fax: +39.02.303.040.44 Tel.: +65.9168.3998
Fax: +65.6327.5406

Brazil Spain South Korea

Av. Doutor Chucri Zaidan, 920 – Paseo de la Castellana 216 Youngpoong Building, 22nd Floor
4º andar Pl. 13 33 Seorin-dong, Jongno-gu
Market Place Tower I Madrid 28046 Seoul 110-752
São Paulo SP 04578-903
Tel.: +34.91.531.79.00 Tel.: +82.10.3019.1417
Tel.: +55.11.5501.1100 Fax: +34.91.531.79.09 Fax: +82.2.399.5534
Fax: +55.11.5501.1110
Switzerland
Canada
Tessinerplatz 5
1981 McGill College Avenue Zurich 8027
Montréal, Québec H3A 3T5
Tel.: +41.44.5533.333
Tel.: +1.514.499.0461

You might also like