The Artificial Intelligence and Machine Learning (AI/ML) Survey is intended to inform the work of the Big Data and Artificial Intelligence (H) Working Group in support of its charge to:
Research the use of big data and artificial intelligence (AI) in the business of insurance and evaluate existing regulatory frameworks for overseeing and monitoring their use. Present findings and recommend next steps, if any, to the Innovation and Technology (EX) Task Force, which may include model governance for the use of big data and AI for the insurance industry.
The survey is being conducted under the examination authorities of nine requesting states (Connecticut, Illinois, Iowa, Louisiana, Nevada, North Dakota, Pennsylvania, Rhode Island, and Wisconsin). The survey will be sent to companies writing Private Passenger Auto business in one or more of these nine states, but the responses to the survey will be national in scope.
Any company licensed to write private passenger auto insurance in one of the nine participating states (Connecticut, Illinois, Iowa, Louisiana, Nevada, North Dakota, Pennsylvania, Rhode Island, Wisconsin) and has at least $75 million in national private passenger auto insurance premium for 2020 will be required to complete the survey.
The official call letter was sent September 28, 2021.
Through the survey, the Big Data and Artificial Intelligence Working Group will gain a better understanding of the industry’s use and governance of big data and AI/ML models, as used in systems incorporating AI/ML.
With this greater understanding of how AI/ML is used and governed by industry, the Working Group can more effectively meet its charge to:
Assess data needs and required tools for state insurance regulators to appropriately monitor the marketplace and evaluate the use of big data and intelligent algorithms, including AI in underwriting, rating, claims, and marketing practices.
IMPORTANT: When the Regulatory Data Collection (RDC) tool is ready to accept responses, companies will need at least one user who has the appropriate role, User ID, and password to open RDC and make the submission. To obtain the role, User ID, and password, use the link provided below the RDC login button or contact the NAIC Helpdesk at email@example.com. For more information on securing roles, User IDs, and setting passwords, see options in the User ID and Password section.
This AI/ML Survey webpage will be updated with new information and additional documentation (such as FAQs, definitions, filing dates, etc.) regarding the survey. You may wish to bookmark this page and return to it frequently for the latest information on the AI/ML Survey.
User ID and Password
You should request your User IDs and role assignments now, so you will be ready when the survey call letter is sent later in September. Here’s what you need to do:
To obtain your role, User ID, and password, use the link provided below the RDC login button or contact the NAIC Helpdesk at firstname.lastname@example.org. Indicate that you will need access to RDC for submission of the AI/ML Survey.
When the NAIC issues you a User ID, your password is set, and you are assigned the appropriate role, you will be able to log into RDC, but unable to access the AI/ML Survey or submit data until: 1) your User ID is associated with a CoCode and 2) the AI/ML Survey Call Letter has been distributed.
Each User ID must be associated to specified NAIC CoCode(s). Everyone with an AI/ML Survey RDC role will be limited to only submitting and reviewing validation errors for associated CoCodes. This ensures each company has control over who has access to its data.
Each company will need to assign a Primary user to its CoCode. The company’s Market Conduct Contact, MCAS Contact, or Governmental Relations Contact will need to send an email to email@example.com with the subject line of “AI/ML Survey CoCode Assignment” requesting Primary user assignment to their company CoCode. The email will need to include the User ID of the Primary user.
Once the Primary user is assigned, the Primary user will be able to login to RDC and assign additional Secondary users if needed.