Insurance Service Bus™ is a specialized services container of the insurance industry who simplifies the integration and reutilization of the business components, using an architecture based on ACORD standards and service-oriented (SOA). ISB™ provides core solutions of integration and process and service management for insurance companies, solutions of insurance central management, quotation and emission systems, portals for intermediaries, inspections management systems, sales systems.
Insurance Service Bus™ has tools that make a difference from the other bus market: API ISB and ISB CONF. The first is an API in order to allow access to channels for different languages to access resources ISB ™. Each service has its analgo SysOne SDK as service catalog as a REST API, enabling interoperability.The second, ISB CONF, is the configuration tool that allows through a website and agile intuitive configure products, rates and all aspects the operations of the company.
Insurance Service Bus (ISB™) is composed of three main pillars:
Insurance Service Bus™ supports the entire suite of insurance, as can be seen in the following graph:
Insurance Core™ architecture combines a focused processes and services designed to scale (SOA) with application integration and service partners approach. The platform supports both modules can be implemented with Open Source tools as container owners, obtaining a high availability environment.
100 % Web, supports multiple devices. It is not necessary to realize discharges to be able to use the system, it is enough to have only the direction URL.
It is service-oriented (SOA), based on REST API. HTTP services can be consumed by a wide range of clients including web browsers, mobile, other systems or tablets.
Each process and resource data is exposed through an HTTP service enabling communication and integration between various current or future devices.
The platform has an extended BPM (BPMN 2.0) with ability to solve RunTime time domain objects (insurance business). These objects can potentially be mapped to the data layer (relational database, partner service, etc).
This extension of the BPM generates an added value that gives simplicity and ease of reading process. Thus the processes have the ability to understand the business model with their corresponding objects in a natural way, avoiding technical actions within the process.
The process layer also has the ability to execute business rules thanks to embedded rules engine.
It maintains business rules, constantly updating.
The data access layer provides a separation of code by its function. This approach provides flexibility to change the data persistence mechanism in the desired time.