IDIT

1. What is it?

1.1. CRM

1.2. N-Tier Layered Arch

1.2.1. IDIT CORE

1.2.1.1. Policy

1.2.1.2. Billing

1.2.1.3. Claims

1.2.2. CORE Countries

1.2.2.1. Languages

1.2.2.2. Address & Name formats

1.2.3. Customer

1.2.3.1. Produts

1.2.3.2. Workflows

1.2.3.3. Interfaces

1.2.4. Customer Countries

1.2.4.1. Products

1.2.4.2. Rates

1.2.4.3. Clauses

1.2.4.4. Interfaces

2. Day 1 - Functional Overview - Contact Concept and Workflow & Tasks

3. Additional Information

3.1. User

3.1.1. Person that log into the application

3.2. Roles

3.2.1. Agents

3.2.2. Service Providers

3.2.3. Policy Holders

4. Pesquisar sobre:

4.1. Underwriting

4.2. Endorsement

4.3. Claims

4.4. Diferença sobre

4.5. Line of Business

5. Contact Management

5.1. CRM Overview

5.1.1. Single repository of all contacts

5.1.2. Contact overview

5.1.2.1. Policies

5.1.2.2. Claims

5.1.2.3. Accounting

5.1.2.4. Contact queue items

5.1.3. Multiple roles

5.1.3.1. Intermediaries

5.1.3.2. Services Providers

5.1.3.3. Policyholders

5.2. Contact Attributes

5.2.1. Legal types

5.2.1.1. Private Individuals

5.2.1.2. Legal Entities

5.2.1.3. Self Employed

5.2.2. Relationships

5.2.2.1. Created automatically (except for family members)

5.2.3. Affinity Group

5.2.3.1. Are clubs or associations

5.2.4. Contact Roles

5.2.4.1. Different roles has different data views

5.2.4.2. More at IDIT SECURITY

5.2.5. Contact Details

5.2.5.1. Statuses

5.2.5.1.1. Data may change depending of the contact status

5.2.5.2. Addresses

5.2.5.3. Identifiers

5.2.5.4. Phone and e-mails

5.2.6. Events

5.2.7. Data Access Restriction

5.2.7.1. Data restriction based on contact, contact role and user profile

6. Training access

7. Policy Administration

7.1. Generate the data to create insurance quotes and policies

7.2. Introduction

7.2.1. Terminology

7.2.1.1. Policy

7.2.1.2. Endorsement

7.2.2. Structure

7.2.2.1. Product

7.2.2.2. Product Version

7.2.2.3. LoB

7.2.2.4. Product Line

7.2.2.5. Product Line Option

7.2.3. Functionality

7.2.3.1. Customer questionnaries

7.2.3.2. Comprehensive data validation

7.2.3.3. Individualized prices quote

7.2.3.4. Policy actions triggers events

7.2.3.5. Collection Details

7.2.3.6. Policy Renewal

7.2.3.7. Policy Cancellation

7.2.3.8. Object Identifiers

7.3. Sales Process

7.3.1. Proposal

7.3.1.1. All the terms. All the conditions

7.3.2. Policy

7.3.2.1. After agreement of the proposal it becomes a Policy

7.3.2.2. Confirming the policy

7.3.2.3. Premium is calculated in the POLICY module

7.3.3. Endorsement

7.3.3.1. Are changes that a user can perform after a policy is issued

7.3.3.2. Types

7.3.3.2.1. General changes

7.3.3.2.2. Administrative changes

7.3.3.2.3. Premium Impacting changes

7.3.3.2.4. Policy cancellation/suspension

7.3.3.2.5. Renewal related changes

7.3.4. Renewal

7.3.4.1. can be a special kind of endorsement

7.3.4.2. When manually renewed, user can decide if its going to use the originalPolicy or the latest product versions/tariffs

7.3.5. Cancelation

7.4. Policy Model

7.4.1. Main classes

7.4.1.1. Policy

7.4.1.2. Endorsements

7.4.1.3. Insured objects and types

7.4.1.4. Covers

7.4.1.5. Contacts and links between contact and policy

7.4.2. Policy domain allows gathering of data and uses it to generate quotes and policies

8. Business and Functional Domains

8.1. Functional Domains

8.1.1. Secutiry

8.1.2. Workflow

8.1.2.1. Correspondence management

8.2. IDIT Business Domains

8.2.1. Contact

8.2.1.1. Access to all types of contact entities

8.2.1.2. Relationships between entities

8.2.1.3. 360 view of contact

8.2.2. Policy

8.2.2.1. Core

8.2.2.1.1. Sales (Quotations & Proposals)

8.2.2.1.2. Underwriting

8.2.2.1.3. Policy Approval

8.2.2.1.4. Billing & Collection

8.2.2.1.5. Policy Serving

8.2.2.1.6. Policy Renewal

8.2.3. Claims

8.2.3.1. Claim Domain

8.2.3.1.1. Report Loss > THEN

8.2.3.1.2. Claim management > THEN

8.2.3.1.3. Claim settlement

8.2.3.2. Claim Administration

8.2.3.2.1. Functionalities

8.2.3.2.2. Retrieves relevant datails from the policy

8.2.3.2.3. Transfer payment

8.2.4. Billing & Tech accounting

8.2.4.1. Management

8.2.4.1.1. Creation of Payment Plans

8.2.4.1.2. Collection and Disbursement

8.2.4.1.3. Non Payment follow up

8.2.4.1.4. Reconciliation

8.2.4.1.5. Connection to Accounting

8.2.4.2. Functionalities

8.2.4.2.1. Single & multiple installment billing

8.2.4.2.2. Dunning processing & procedures

8.2.4.2.3. Interface with external clearinghouses & bank systems

8.2.4.2.4. Rejected premiums

8.2.4.2.5. Changes to payment arrangements

9. IDIT Security

9.1. Organizational Structure

9.2. Authentication

9.3. Authorization

9.3.1. Permissions

9.3.2. Actions

9.3.3. Authorization and workflow requires special permissions

9.3.4. Privilege

9.3.4.1. Mustn't add a privilege straight to the user

9.3.5. Limited Privileges

9.3.6. Role

9.3.6.1. Group of previleges gathered in on place as a role

9.3.6.2. Can have more than one role

9.3.6.3. Can have different and/or same privileges

9.3.6.4. User can create new roles

9.3.6.5. Security roles

9.3.6.5.1. Every user has this by default

9.3.6.5.2. Base role (inherits by all members of the company)

9.3.6.6. Role list

9.3.6.6.1. System Adm

9.3.6.6.2. CSR

9.3.6.6.3. Claims Settler

9.3.6.6.4. Collection Clerk

9.3.6.6.5. CFO

9.3.6.6.6. Mailroom

9.4. Data access restriction

9.4.1. To handle contacts with specified roles, a user must have the appropriate privileges

9.4.2. The user should be authorized to see the data as well

9.4.3. Security check will be perfomed at every check performed by the user

9.4.4. Contact Role

9.4.4.1. Family member is a direct member of the contact

9.4.5. Contact status

9.4.5.1. Need appropriate privileges to handle specific statuses (E.g. VIP)

9.4.5.2. Can't create a contact with the status you can't handle

9.4.5.3. Even though you can see the contact, if you don't have the privileges to edit it, you will not be able to do so

9.4.6. Can not update own details or family details (application parameter 10262)

9.4.7. Brand Company

9.4.7.1. User can only handle Contacts/Policies etc from their own BC

9.4.7.2. Each entity (contact/policy/claim) is related to a certain BC

9.4.7.3. If a policy or contact is not related to any BC, it is considered "unlimited" and everyone can see it

9.4.7.4. Contact limited view

9.4.7.4.1. Limited information displayed

9.4.7.4.2. No actions menu (to edit the contact)

9.4.7.4.3. Navigation three is fully displayed

9.4.8. Profiles

9.4.8.1. Only one assigned to a user

9.4.8.2. Channels of communication

9.4.8.2.1. B2C - Business to Customers - Can check owns data ONLY

9.4.8.2.2. B2E - Business to Employee - for company employees (internal users)

9.4.8.2.3. B2B - Business to Business - users can log in to IDIT on behalf of one or more agencies to check other peoples details

9.4.8.3. Admin Users

9.4.8.3.1. HQ Admin

9.4.8.3.2. NOT HQ Admin

9.5. General Security parameters

9.5.1. has a maximum logging failures allowed

9.5.2. Has a defined structure to the user password (can't be a week one)

9.5.3. Has a valid period - after that you have to update your password

9.6. Security additional features

9.6.1. Has an auditing log

9.6.1.1. General logger tracks specifics made by users

9.6.1.2. Security logger tracks changes made by users using the security manager tool (e.g change user pwd)

9.6.2. SSO

9.6.3. Has last updates details

9.6.4. Audity history

10. Billing and Collection

10.1. Modules

10.1.1. Billing and Collection

10.1.2. Technical accounting

10.1.3. Reinsurance

10.1.4. Co-insurance

10.2. Installments are calculated in the BILLING AND COLLECTION module

10.3. Transactions are done in the ACCOUNTING MODULE

10.4. Account types

10.4.1. Contact

10.4.1.1. It holds information about all things done by account

10.4.1.2. Its not related to any specific policy or claim

10.4.2. Policy

10.4.2.1. Its open when opening a new policy

10.4.2.2. Reflects all financial activities

10.4.2.3. Every payer has one

10.4.2.4. Process and manages all financial transactions of the policy

10.4.3. Claim beneficiary

10.4.3.1. Holds all claims transaction to be paid

10.4.3.2. Beneficiary account is created on the first payment of the claim

10.4.3.3. One account per claim

10.4.4. Agent

10.4.5. Carrier

10.4.6. Service provider

10.4.6.1. Also has a separated account

10.4.7. Brand Company

10.4.8. General Letter

10.5. Installment

10.5.1. has

10.5.1.1. Due date

10.5.1.2. Grace date

10.5.1.3. Installment amount

10.5.1.4. Installment balance

10.5.1.5. Collection date

10.5.1.6. non-payment date

10.5.1.7. Installment status

10.5.1.8. Installment type

10.5.1.9. Collection method

10.5.1.10. Bank acount

10.5.2. statuses

10.5.2.1. Pending

10.5.2.1.1. Assigned as soon as installment is created on the DB

10.5.2.1.2. remains until collection date

10.5.2.2. Booked

10.5.2.2.1. Outgoing payment

10.5.2.3. Submitted

10.5.2.4. paid

10.5.2.4.1. When the paid installment balance is 0

10.5.2.5. Partially paid

10.5.2.6. Cancelled

10.5.2.6.1. Cancelled installment balance is set also to 0

10.5.3. Types

10.5.3.1. Recurring Installments

10.5.3.2. Non-recurring Installments

10.5.4. Installments in a Policy

10.5.4.1. Payment schedule is created once a proprosal is approved

10.5.4.2. Installments may change depending on the endorsement

10.5.4.3. Increases and decreases on the premium

10.5.5. Policy cancellation

10.5.5.1. not-paid not cancelled not partially paid payment with those status will be cancelled

10.5.6. Policy renewals

10.6. Transactions and entries

10.6.1. is financial activity performed in the system

10.6.2. may be generated automatically

10.6.3. An entry can be linked to only one account

10.6.4. either credit or debit

10.6.5. Accounting transactions

10.6.5.1. Entry status

10.6.5.1.1. Booked

10.6.5.1.2. Sent

10.6.5.1.3. Paid

10.6.5.1.4. Policy

10.6.5.1.5. Un-payable

10.6.5.1.6. Payable

11. Report a loss

11.1. Claims

11.1.1. Is an hierarchical structure of business entities

11.1.2. Needs minimum information before can be opened

11.1.3. Seamless Operation

11.1.4. Has specific date and location

11.1.5. May have irregularities

11.1.6. Contact

11.1.6.1. Contact related to a claim

11.1.6.2. A contact can have more than one role

11.1.6.3. Can be added automatically or manually by the user

11.1.6.4. Claimants are special kind of claim contact

11.1.7. Claim payment

11.1.7.1. Payment is broken down into one or more invoice

11.1.7.2. Each damage can have severalclaims payment (until all reserve is used)

11.1.8. Claim Recurring Payment

11.1.8.1. Can be payed at an end date or be lifelong

11.1.9. Grouped Claims

11.1.9.1. A chain of events

11.1.9.2. Goes with Catastrophe

11.1.9.3. Reserve will be individually split evenly between all children claims

11.1.9.4. The validation check

11.1.10. Questionnaires

11.1.10.1. Help IDIT understand the circumstances that the damage occurred

11.1.10.2. Enables high level of customer care

11.1.10.3. Every claim will have the same questions

11.1.11. Fast Track Claims

11.1.11.1. Handles noncomplex claims faster

11.1.12. Agenda

11.1.12.1. Tracks all steps and their statuses on the Claim Dashboard

11.1.12.2. In case of Catastrophe, the MASTER CLAIM will have the its statuses updated and then all children claim will inherit from the master

11.2. Catastrophe

11.2.1. Is a way to group claims that arise from a single event

11.3. Glossary

11.4. Represents an e event

11.5. Damaged Object/ Claimed Insured Object

11.6. Damage

11.6.1. Represents harm or injury to a object

11.6.2. More than one damage can be selected from the "Damage Tree"

11.6.3. Damage code will only be shown as per selected on the Damage tree

11.6.4. Can be Updated/Add both Damage and Reserves

11.7. Reserves

11.7.1. Are all expenses and indemnities the company expects to pay

11.7.2. Reserves can be changed on the dependencies tree

12. Workflow

12.1. Is a set of events, documents and tasks

12.2. Combination of building blocks

12.2.1. Action

12.2.1.1. Manual action

12.2.2. Events

12.2.3. Event Follow-ups

12.2.3.1. Follow-up is a task that will happen in the future and has due date

12.2.4. Queues

12.2.4.1. Queues is a method of organizing the follow-up that requires handling

12.2.5. Documents

12.3. Tasks

12.3.1. Can be escalated