| Agent Policy Processing System for Major Insurance Company |
| Client |
Major Insurance Company in Southern California |
 |
| Project |
Agent Policy Processing |
Executive Summary:
Aviana has designed, developed, deployed and continues to support custom applications at a Major Insurance company. The Agent Policy Processing System (APPS) application is one such important solution. The core application platform used for this project was co-developed by Aviana for this client, and it provides a web-based interface for the company's agents to process insurance policies. The current system was mainframe based and hence very archaic. This application provides an easier, and more efficient way for agents to process the policies. |
|
| What Was The Problem ? |
| The client did have an archaic policy processing system that was |
 |
Extremely difficult to use and master for new agents, the system was not intuitive, and it was mainframe based and thus cryptic in appearance. |
|
Required extensive and frequent training investment for the insurance agents, due to the difficulty in using the application, as well as a high rate of staff turnover, and |
|
Based on old mainframe technology and lacked the user-friendliness, robustness and scalability desired. |
|
| Why Aviana ? |
| Aviana was tasked to design and implement this innovative system based on its well-recognized expertise in using J2EE technology for providing custom solutions to Fortune 1000 and other large organizations, as well as its functional knowledge of the insurance sector. In addition, Aviana had prior experience with the design and implementation of other financial transaction processing applications for many clients, over many previous projects, spread over several years. |
|
| Aviana's Solution |
The new application provides a web-based interface to existing systems (Auto Policy Processing System, Fire Policy Processing System, Customer Self Service, Billing Inquiries, Point of Sale Underwriting and Agent's Cash Advance). The existing system was originally developed for the insurance company and its agents to manage policy processing and client accounts using CICS, COBOL and DB2 on the IBM mainframe platform. Applications were built with layering in mind, isolating the primary business logic into a set of independent CICS/COBOL programs. The new system was able to take advantage of this by building a new CICS/COBOL layer in front of the existing business logic programs, in order to handle the communication between Java/J2EE and existing systems.
This application is composed of five discrete layers. Each layer addresses specific aspects of the application, and utilizes technologies designed to help realize the requirements assigned to each layer. |
|
| The presentation layer encapsulates all logic required for interacting with the user. This layer receives requests from clients, handles session management, interacts with business layer, and generates appropriate responses. This layer primarily utilizes Servlets and JSPs. It supports XML/XSLT and Single Sign-on integration. |
| Business layer encapsulates Event Processing, Event Flow, Validation Services, Valid Values, Business Object Model and Data Access Services |
| The integration layer provides connectivity to the Enterprise services to the business layer. This layer exposes a facade interface that hides the implementation details of the ECI communications. Upon receiving a request, the layer will "marshal" the request data by converting the contents of Java classes associated with the request to a COBOL structure. |
| The Legacy Application Integration ('E' framework) provides enterprise application integration services thru a defined set of APIs. Data capture is made up of user interactions with web pages. The data is placed in the CAM (Commarea access manager). The required data for the web front end from this CAM is retrieved and converted to ECAM and passed to the web front end using the 'E-Controller'. |
|
|
|
