RMV ATLAS Project Insurance Policy Management (IPM) Webinar #5 - - PowerPoint PPT Presentation

RMV ATLAS Project

Insurance Policy Management (IPM) Webinar #5 – Preparing for Testing

June 11, 2019

Agenda

• Policy Updates/Clarifications
• Notice To Carrier
• Working Batch Error Reports
• Interface Timeline
• Testing Preparation
• Key IPM Processing Details

June 11th, 2019

2

Policy Updates/Clarifications

Trailers

Trailers

• Reporting of private passenger trailers will be allowed, but optional
• Reporting of commercial trailers is required (regardless of weight) – subject to revocation
• Commercial trailer = Any trailer used by a commercially registered vehicle (regardless of weight)

Trailer Inspections/VIN

• Commercial trailers will require a VIN to support commercial trailer inspections
• For trailers without a VIN, the RMV will assign a pseudo VIN
• Pseudo VINs will be assigned at time of new registration or registration renewal
• Assigned VINs must be affixed to the commercial trailer once assigned

Trailer Insurance Stamps

• All trailers will continue to require insurance verification via a stamped application for a new registration
• r registration amendments
• Stamp not required at renewal unless the insurance has changed
• For cases where a trailer has been cancelled from an insurance policy in the prior year, an insurance

stamp is required

June 11th, 2019

3

Policy Updates/Clarifications

Policy Term Limits & Amending Policy Extension Policy Term Limit Update

• Policy term limits previously reported (6 months – 3 years) have been updated.
• New policy term limits
• Minimum policy term length – 1 Day (was 6 months)
• Maximum policy term length – 2 Years (was 3 years)

Amending Policy Expiration

• ATLAS will support the ability to amend a policy’s expiration date as long as the

amended term limit fits within the maximum allowable term limit (2 years)

June 11th, 2019

4

Policy Updates/Clarifications

Elimination of Premium Town Code Premium Town Code

• Premium Town Code will not be part of any new ATLAS processing, and is no

longer part of any interface between the RMV and Commonwealth Automobile Reinsurers (CAR).

• ATLAS will remove the field Premium Town Code from all interfaces.
• This will also eliminate the “Update Premium Town Code” transaction

June 11th, 2019

5

Policy Updates/Clarifications

New Registration and Title Application New Registration and Title Application

• Combines the current RMV1 and RMV3 Forms
• Latest version available (update - 6/21/2019)
• New Registration and Title Application will be accepted at launch
• Due to Electronic Vehicle Registration (EVR) transition, old RMV1 and RMV3

forms will be accepted for a limited time post launch.

• Timing for accepting old forms still under discussion

SHOW LATEST DRAFT OF NEW REGISTRATION AND TITLE APPLICATION

June 11th, 2019

6

Policy Updates/Clarifications

Registration Revocation Registration Revocation

• A Registration without an associated policy record will initiate revocation:
• New Registrations: Revocation notification initiated and sent to customer 23 days after

registration, revocation processed 10 days later

• Policy Expiration: Revocation notification initiated and sent to customer 10 days after policy

expiration, revocation processed 10 days later

• Policy Cancellation: Revocation notification initiated and sent to customer 10 days (this is a

change from 23 days) after cancellation, revocation processed 10 days later

June 11th, 2019

7

Policy Updates/Clarifications

Registration Revocation and Implementation Timeframes

Example – New Registration – No policy received

• New Registration processed by RMV 4/2/2020

June 11th, 2019

8

Date Action Days Registration Status Policy Status Action Notice to Carrier 4/2/2020 1 Active No Policy Customer Registers Vehicle Active Registration – No Policy 4/24/2020 23 Active No Policy Notice of Revocation mailed to Customer No Policy Reported – registration pending revocation; 5/4/2020 33 Revoked No Policy Registration Revoked due to no insurance No Policy Reported - Registration Revoked

• A policy record received prior to 4/24/2020 will ensure customer does not receive a

Notice of Revocation

• A policy record received prior to 5/4/2020 will stop the registration from being revoked

Policy Updates/Clarifications

Registration Revocation and Implementation Timeframes

Example – Policy expiration – No new policy received

• Policy Expires 5/15/2020

June 11th, 2019

9

Date Action Days Registration Status Policy Status Action Notice to Carrier 5/15/2020 Active Active 5/16/2020 1 Active Expired Policy expired Active Registration, policy expired 5/25/2020 10 Active Expired Notice of Revocation sent to customer Policy expire, registration pending revocation 6/4/2020 20 Revoked Expired Registration revoked due to expired insurance Policy Expired, Registration Revoked

• A policy record received prior to 5/25/2020 will ensure customer does not receive a

Notice of Revocation

• A policy record received prior to 6/4/2020 will stop the registration from being revoked

Policy Updates/Clarifications

Registration Revocation and Implementation Timeframes

Example – Policy Cancellation – No new policy received

• Policy Cancelled by Carrier 1/15/2020

June 11th, 2019

10

Date Action Days Registration Status Policy Status Action Notice to Carrier 1/15/2020 Active Active 1/16/2020 1 Active Cancelled Carrier cancels policy, effective 1/15/2020 1/25/2020 10 Active Cancelled Notice of Revocation sent to customer 2/4/2020 20 Revoked Cancelled Registration revoked due to expired insurance

• Does not show on Notice to Carrier due to cancellation
• A policy record received from current or new carrier prior to 1/25/2020 will ensure

customer does not receive a Notice of Revocation

• A policy record received from current or new carrier prior to 2/4/2020 will stop the

registration from being revoked

Policy Updates/Clarifications

Registration Revocation and Implementation Timeframes

Example – Registration Transfer (from vehicle B to vehicle A – Policy not amended)

• Policy Effective Date – 3/1/2020; Registration Transferred on 3/2/2020

June 11th, 2019

11

Date Action Days Registration Status Policy Status Action Notice to Carrier 3/1/2020

• a. No Reg.
• b. Active
• a. No Policy
• b. Active

3/2/2020 1

• a. Active
• b. No Reg
• a. No Policy
• b. Active

Customer transfers existing registration to a new vehicle

• a. Active registration, no

policy reported

• b. Active policy, no registered

vehicle 3/24/2020 23

• a. Active
• b. No Reg
• a. No Policy
• b. Active

Notice of Revocation sent to customer

• a. No policy reported,

registration pending revocation

• b. Active policy, no registered

vehicle 4/3/2020 33

• a. Revoked
• b. No Reg
• a. No Policy
• b. Active

Registration revoked due to no insurance

• a. No policy reported,

registration revoked

• b. Active policy, no registered

vehicle

Notice to Carrier

• Combines current reports (e.g. Active Vehicles with No Policy, Expired Policies with no Other Coverage)

expanded to cover additional policy situations that require review/response

• Information will be current as of the time of access, and consistent regardless of

method:

• Via Secure Batch File transfer – Available daily. Notice to Carrier Transaction file (not paper report).
• Via SOAP web service – Available real-time. Returns Notice to Carrier transactions via web service.
• Via Insurance eService Portal – Available real-time. Screen based table within the ATLAS portal, not

a paper report (table will be exportable and printable)

• Each carrier will determine how they plan to consume this information
• Batch files will only be generated if that communication vehicle is chosen and fully tested.
• Web Service calls will only be authorized if that communication vehicle is chosen and fully tested.
• Information is cumulative and will show the changing status of a vehicle on the

report

• As soon as an issue is resolved, that issue will no longer show on the report

June 11th, 2019

12

Notice to Carrier

Reporting examples

June 11th, 2019

13

Notice to Carrier Notification Indicates one of the following Active registration, no policy reported

• New Reg. prior to receipt of policy;
• Registration transferred without policy amend

No policy reported, registration pending revocation

• New Reg. prior to receipt of policy – after 23 days;

No policy reported, registration revoked

• New Reg. prior to receipt of policy – after 33 days;

Active registration, policy expired

• Existing Registration after policy expiration date

Policy expired, registration pending revocation

• Existing Registration after policy expiration date –

after 10 days Policy expired, registration revoked

• Existing Registration after policy expiration date –

after 20 days Active policy, registration expired

• Policy still active after registration expiration

Active policy, registration plate number change

• Plate Swap

Active policy, registration cancelled

• Owner Cancelled Registration

Working Batch Errors

• Batch errors are returned as part of the batch response file
• The RMV expects carriers to review returned errors and take

corrective action

• ATLAS eService Portal will support real-time corrections

directly in ATLAS

• Batch errors will not be visible on the portal

June 11th, 2019

14

15

ATLAS Interface Timeline

June 11th, 2019

Testing Setup

Testing Setup – Batch

• Establish SFTP connectivity via MOVEit solution.
• Set-up will require IP whitelisting and SFTP service authentication or username/password setup
• Jonathan Magsino (Jonathan.Magsino@dot.state.ma.us)
• Smoke Testing (currently active)
• Receive test files via MOVEit SFTP and verify correct layout
• Sample files available via MOVEit
• No processing of data
• Connectivity Testing (July 1, 2019 – July 19, 2019)
• Verify ATLAS staging environment connectivity via MOVEit
• Full Integration Testing (July 22, 2019 – October 18, 2019)
• Data - A fully converted production database
• Refresh – Bi-weekly throughout Integration Testing.
• Batch files will normally be processed within 24 hours unless otherwise discussed

June 11th, 2019

16

Testing Setup

Testing Setup – Web Service

• Establish Web Service connectivity
• Whitelisting of All IPs from which ATLAS web service calls could originate.

IPs that attempt to access the ATLAS endpoint that are not listed will be blocked.

• A Client Certificate – A 2-year client certificate public key signed by a Certification Authority
• Smoke Testing (currently active)
• Web service end-point established and responsive to calls, but with no connected database.
• Web service will provide “canned” responses for partner verification of data structure.
• No processing of data
• Connectivity Testing (July 1, 2019 – July 19, 2019)
• Verify ATLAS staging environment connectivity
• Full Integration Testing (July 22, 2019 – October 18, 2019)
• Data - A fully converted production database
• Refresh – Bi-weekly throughout Integration Testing.
• Web service endpoint should be responsive 24x7, except for weekend conversion and unexpected

issues (it is a testing environment)

June 11th, 2019

17

IPM Processing Details

CAR-Codes

• 3-digit code Generated by Commonwealth Automobile Reinsurers (CAR) -

http://commauto.com/

• RMV’s primary identifier for interface processing with insurance carriers
• Verification edits will be more stringent in ATLAS (e.g. only valid CAR-codes being

accepted) Carriers

• Carriers can submit transactions using their assigned CAR-code directly
• Carriers can submit transactions for other “sister” carriers with different CAR-codes,

but part of the same Insurance Group

Service Providers

• Service Providers are assigned user ID (alphanumeric) to use in IPM processing.
• Service Providers can submit transactions for any customer’s carriers CAR-codes as

long as they have been authorized by the carrier

June 11th, 2019

18

ATLAS CAR-Code Processing

Examples

June 11th, 2019

19

REQUEST: As testing connectivity is established, please verify all CAR-Codes being processed by each Interface

Carrier = Basic Insurance CAR-Code = 823 Carrier = Boston Fire CAR-Code = 468 Carrier = Boston Casualty CAR-Code = 467 Carrier = Friendly Insurance CAR-Code = 118 Carrier = ABC Mutual CAR-Code = 530 Service Provider A = SPA Submitting = 530 Processing CAR-Code = 530 Submitting = SPA Processing CAR-Codes = 118 & 823 Carrier = Boston Accident & Indemnity CAR-Code = 469 Submitting = 467 Processing CAR-Codes = 467, 468, 469

IPM Processing

Web Service

• New operation to retrieve policy history for all policy terms
• Added Transaction Effective Date to allow specifying when a

transaction is effective

• Added "Latest Valid Date" to track the latest valid date of the

registration

• Added "Registration Status History" data block to show the

registration status over time

June 11th, 2019

20

IPM Processing

Batch

• Valid IPM transaction type/vehicle action code combinations

added to spreadsheet

• Two ways to add policies:
• Adding policy and all vehicles as one transaction:
• Adding policy only, and then adding each vehicle via an amend transaction:

June 11th, 2019

21

Trans Type Action Code Processing Comments 1 1 Both new policy and all associated vehicles are added. If any vehicles error for any reason, the entire add policy transaction is rejected Trans Type Action Code Processing Comments 1 New Policy added without vehicles Results in a Policy recorded with no associated vehicles 4 1 Add new vehicles via an amend transaction All valid vehicle transaction will be accepted even if one vehicles is rejected

Questions

Primary Interface Contact: Tedford.Armistead@dot.state.ma.us Interface Technical Team: DOT-DL-ATLAS-Interfaces-R2@dot.state.ma.us IPM Website: https://atlas.massrmv.com/IPMProgram.aspx

June 11th, 2019

22