 |
Jarus Real time ASAP™ helps carriers accelerate implementation of real
time and download capabilities. It uses sophisticated technologies to process inquiry, new business, policy admin transactions initiated by agents, fulfills them by invoking appropriate carrier backend systems and returns the result back to the agents
|
 |
|
 |
| Real time is the ability for an agent to click on a button from a client
file in an agency management system or comparative rater for immediate access to carrier information on that client. The transaction may be a quote, billing inquiry, claim inquiry/loss runs, policy view, endorsements or a request for information. This approach provides a single workflow for servicing or quoting for agents. For more info, see http://getrealtime.org |
|
|
 |
Independent agents and brokers face many issues:
| |
Independent agents typically work with 6 to 13 carriers and the workflow for each carrier is different. This makes quoting and servicing their clients complicated |
| |
Client data is not current in agency management system and this hinders agent’s ability to respond to client’s needs faster. |
Real time eliminates these issues by enabling connectivity between agency systems and carrier backend. It keeps the client file current and streamlines the workflow. |
 |
| |
Single, consistent workflow for agents across multiple carriers |
| |
No need to go to multiple sites or remember multiple passwords |
| |
Cuts quoting time in half |
| |
Electronic data capture reduces errors and results in faster turnaround. |
| |
Automation reduces workload for carriers, eliminates back logs and results in more sales. |
| |
Enables claims management from client’s file. |
|
 |
 |
| |
Personal Lines |
|
Commercial Lines |
| |
Quote and New Business for Auto,
Homeowners and Umbrella |
|
Quote and New Business for BOP,
Commercial Property and Commercial Auto |
| |
Billing Inqui |
|
Billing Inquiry |
| |
Policy Inquiry |
|
Policy Inquiry |
|
|
 |
|
| |
 |
| Real time ASAPTM is a sophisticated framework with a flexible architecture.
Deployed as a web service, it processes the ACORD XML request from agency management systems and uses standard SOA middleware
to fulfill the transactions by interfacing with carrier backend systems. It also employs a Business Rules Engine and a BPM engine to
intelligently route transactions and make critical decisions. |
 |
 |
| B2B Gatway |
The gateway is a service that listens for ACORD XML transactions initiated by the agency management systems. It is also responsible to verify security credentials to accept/reject the incoming transaction. It invokes the ACORD XML processor to understand and act on the ACORD XML stream. |
| Acord XML Processor |
A high performance, flexible, customizable XML processor that parses and understands the XML message. It also performs validations of business data and applies corrections as appropriate. |
| Soa Middleware |
Typically an Enterprise Service Bus that provides process orchestration and virtualization service. While it is not mandatory, it is recommended to reduce point-to-point integration needs. |
| BRMS Stack |
BRMS stack consists of a rule engine, rule repository and rule editors and testers. BRMS stack allows end user customization simple by allowing business analysts review and edit business rules. This makes the system very flexible and agile. |
| BPM Stack |
BPM stack consists of a BPM engine, Workflow editor and workflow definition files. Workflow component route the incoming request to appropriate personnel if manual intervention is needed to fulfill a transaction. For example, if an underwriter needs to get involved before a quote can be sent out, the BPM engine is able to detect this situation and routes the
request to the underwriter. |
|
|
| |
