top of page

ACSEL

Web Architecture

The customer centric approach of ACSEL facilitates marketing processes and the definition of products, plans and coverage as a function of business rules; it also generates dramatic time-to-market reductions, which means that products may be handled by any line of business and distributed over any media or channel, whether conventional, mass, niche, digital or specialized

The quote, inspection, underwriting, policy life-cycle, collection, premium and claim administration, coinsurance and reinsurance processes, as well as the automatic generation of accounts receivable, accounts payable, and accounting, are facilitated by the architecture by use of a series of collaborative engines and modules that allow the user to manage and maintain the data structure, layout, performance and processes of the application via business rules.

This Service Architecture (Framework) includes a development accelerator that builds components, processes, rules, engines, etc. Around a block-type base, and provides for the re-utilization thereof for the application's growth and maintenance, integrating with other tools, components, applications or standards available in the market, thanks to which obsolescence remains marginal.

There are no limits in the system as to the possibilities for the quick definition and maintenance of lines of business, products, plans or coverage; furthermore, the system is capable of combining lines of business and combos by use of configuration options.

Characteristics

ACSEL is a configurable and extensible architectural base for the insurance business whereupon different blocks are built and maintained dynamically, This blocks may be configured through templates engines for various purposes, which means that there is no need to modify source codes when introducing new products or changes, and that scenarios may be simulated before they are actually transferred to the production environment.

The most relevant features include:

  • It offers independence from platforms, operating systems and databases.

  • It is fully web-based.

  • It is multi-language, multi-country, and multi-currency.

  • It has a workflow integrated engine.

  • It provides for security provisions by role and performance range.

  • It may be installed in centralized or distributed models and in the cloud.

  • It is based on business rules, components and collaborative modules.

  • It provides for fully configurable policy life-cycles.

  • It provides for configuration of the information for exporting and importing purposes.

  • It features a Service-Oriented Architecture (SOA)

  • It features a mobile integrated platform.

  • There is no programming dependence, for it may be configured by the user.

Configuration Engine

The main components of the configuration engine include provisions for:

A Tool, Engine, or Editor

for Every Component.

  • Business Rules

  • Declarative Statements

  • Calculations Engine

  • Policy Life-Cycle Modeling Tool

  • Workflow Editor and Engine

  • Application Behavior Designer

  • Integration with Other Sources

  • Audit, etc.

  1. Product Configuration (line of business, plans, coverage, sale terms and conditions, territories, coinsurance/reinsurance, business rules, contents, product repository, etc.)

  2. Workflow (Editor and Engine) to design, execute, and monitor workflows and process management and repositories

  3. Policy Life-Cycle, to design and manage the life cycle of any policy and all processes involved in a policy's life (issuance, cancellation, endorsement, return, renewal, etc.) based on the line of business involved and on the business rules thereof.

  4. Generation and maintenance of data through a dynamic process managed by the user himself via templates and forms to relate fields with business rules and processes, in an environment where components may be reused for quick change management purposes.

  5. A naturally multi-company, multi-currency and multi-language based framework. It has no implementation limits as regards the centralization or decentralization of the infrastructure, database, instances, etc.

  6. Service Oriented Architecture (SOA)

Client-Centered

Clients and third parties are individually managed based on the role that they play within the core system, whether as natural persons or as legal persons. References to a person are centrally administered by the Universal Administrator based on the role involved; client, beneficiary, inspector, sales channel, service provider (attorney, medical, doctor, etc.) and may be evaluated and queried both globally and by role.

Business Information Model

  Presentation                                                                                       
  • ​User Roles, Preferences

  • Simplified View

  • Data Model

  Components / Semantics                                                                  

  • Dimension calculations

  • Validations, times

  • Rules, Life-Cycle

  Physical                                                                                                

  • Data Map

  • Connections

  • Diagrams, Instances

Value Proposal

  • It enhances a company's performance and competitiveness (through better and larger operational, technical and business capabilities).

  • It supports the core competences of the organization.

  • Knowledge flows naturally within the organization (without reliance upon individuals unwilling to share it).

  • It offers financial benefits by reducing costs​​

  • Infrastructure and services.

  • Transparent outsourcing integration capabilities (no core-mission activities).

  • On-demand insurer scalability

    • Generation of new businesses and faster generation of new premiums (Capacity to access new niches or neglected markets).​

    • Improved client and third-party retention (reduced client-customer turnover).

    • Larger and faster capacity for integration of distribution media, partners, channels (which creates synergy of financial, telecommunications and retail ecosystems with other groups).

Technical Platform

Our technology is based on Java/JEE architecture, Cloud and API Rest. Its building-block and collaborative module architecture facilitates the reutilization of the components and rules configured into the system, which makes ACSEL an ideal platform for global groups because it can be implemented in different regions and may be configured and reused when convenient (for example, product plans or concepts may be maintained at a higher level,  and  local  regulatory  aspects  and  practices  may  be  configured  in  every country where it is implemented).

Its  flexible  approach  provides  for  integration  with  other  solutions  via  open standards  such  as  XML,  web  services,  API’s,  etc. It  is  also  a  development accelerator where the client has the possibility to build - around the kernel or architectural base - any module that calls for extended functionalities. It may be implemented in centralized or decentralized models, where security, multi- language, multi-currency, and multi-country aspects are readily configured.

It is not dependent upon the database platform and application server, thanks to which the client is free to select the desired platform or standard. The system scales in terms of processing and of the number of concurrent users that it is capable to support. It has a number of collaborative modules responsible for integrating  various  functionalities,  from  the  execution  and  control  of  batch processes to a data extraction framework.

Each transaction leaves identity traces, including occurrence date and time, executing user, etc., which renders activities such as monitoring, reinstatement of operational continuity and auditing very easy to implement.

Mobile Platform

The mobile platform is framework-integrated and provides for maintenance of a substantial number of employee, client, sales channel and services functionalities in tablets and mobile smart phones, thanks to which queries and transaction searches of various types can be performed from any location via the mobile network or via wireless internet. The latter includes multi-purpose queries, quotes, inspection, policy issuance, collection, and claims management.

Additionally, certain functionalities that may be executed off the mobile network or off wireless internet (off-line) are later synchronized automatically when connection to the network is re-assumed.

Need more details?

We are here to assist. 

bottom of page