While planning and implementation of Insurance Technology transformation, the following steps are taken: 

Identification of Key modules 

• Listing key areas for rules extraction 
• Policy Quote / Policy Validation / Coverages/ Discounts / Rating / Forms 

Addressing the challenges in Data Migration 

This is done by Converting Legacy EBCIDIC (COMP/ COMP3) format to latest data formats (XML / JSON etc) 

Review Process and Architecture Design 

During the review the following steps are done: 

• Defining existing architecture with key areas 
• On business rules extraction completion – planning future architecture in different technology streams

Insurance platform Key areas - Extraction 

Coverages 

• Identifying state specific coverages / Comprehensive and collision coverages 
• Coverage hierarchies and dependencies (BIPD / Collision etc) 

Discounts and Rating 

• Discount factors – Credit history, MVR, Clue, additional factors 
• Rating – Rating criteria with predetermined factors using table driven logic 

Forms 

• Gathering data for face sheet, endorsements requirements with legal approvals for each state and contractual validations 
• Mainframe copybook based field extraction will give the required mapping for future API based implementations 
• Understanding existing architecture and key batch sequences for future implementation 

Guidelines of Rules extraction  

• Explain Business description only with table names / cam names which is internal to Personal lines application 
• Technical description in terms ‘Value used from table and the Source 
• A separate column is required for: 
  • Move or Business Logic or Not applicable or Default value (Given reason for Not applicable in specific Like rating item / coverage description / States other than AZ not applicable – instead of mentioning only ‘Not applicable 
  • Another filter to say ‘Data passed to other interfaces – Billing / Claims / Folio systems 
• If same field in getting input from two sources, then provide business description like Move District code from agent of record  
  • Renewal commission agent from Policy table 
• If multiple conditions exist, provide summary details in business description 
  • Eg: a) Value 13 is passed - For cancel type ‘02' and reason code ‘22' from Vehicle data 
  • If Policy (Policy table) block code is '0' then value 09 is passed 
  • If policy is recancelled then value ‘CCS' is passed If above conditions not satisfied