1.1 	A bill for an act
1.2 	relating to state government; requiring certain use of verification software in 
1.3 	contracts related to the Minnesota Licensing and Registration System (MNLARS); 
1.4 	requiring a report.
1.5 	BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:

1.6 	Section 1. MNLARS DEVELOPMENT; VERIFICATION SOFTWARE.
 1.7 		Subdivision 1.Implementation. (a) For any contract relating to development or 
1.8 	implementation of the driver and vehicle information system known as the Minnesota 
1.9 	Licensing and Registration System (MNLARS), the commissioner of public safety and the 
1.10 	state chief information officer must require the contractor to meet the requirements under 
1.11 	this section.
1.12 	(b) This section does not apply to a contract for audit or technical assessment of the 
1.13 	MNLARS project.
1.14 		Subd. 2.Contract requirements. (a) A contract under this section must require a 
1.15 	contractor and any subcontractors to use verification software to verify that hours billed for 
1.16 	work under the contract that are performed on a computer are legitimate. The contract must 
1.17 	specify that the agency will not pay for hours worked on a computer unless those hours are 
1.18 	verifiable by the software or by data collected by the software.
1.19 	(b) The contractor must not charge the agency or an auditor of the agency for access to 
1.20 	or use of the work verification software, or for access to or retrievals of data collected by 
1.21 	the software.
1.22 		Subd. 3.Software capabilities. Verification software used in this section must:
2.1 	(1) automatically gather verification of state-funded activity at least once every three 
2.2 	minutes, while continuously monitoring keystroke frequency and mouse-event frequency;
2.3 	(2) include functionality for project management, including but not limited to progress 
2.4 	tracking, timelines, and task management tools;
2.5 	(3) permit the agency or an auditor of the agency to have real-time access to data collected 
2.6 	and provided by the software, including but not limited to visibility of keystroke and mouse 
2.7 	frequency data in real time and on request;
2.8 	(4) provide to the agency or an auditor of the agency automated real-time cost status of 
2.9 	each task;
2.10 	(5) provide to the agency or an auditor of the agency the identity and professional 
2.11 	qualifications of the individual who is performing a task;
2.12 	(6) permit the agency to provide immediate feedback to the contractor on work in 
2.13 	progress; and
2.14 	(7) ensure appropriate treatment of data that are not public data, as defined in Minnesota 
2.15 	Statutes, section 13.02, subdivision 8.
2.16 		Subd. 4.Data practices. The contractor or subcontractor must store, or contract with 
2.17 	another to store, data collected by the software for a period of seven years after the agency 
2.18 	has remitted payment to the contractor for the work. Data collected are data of the contractor 
2.19 	or subcontractor but must be treated as private data on individuals or nonpublic data, as 
2.20 	defined in Minnesota Statutes, section 13.02, except to the extent the data would be classified 
2.21 	as confidential data on individuals or protected nonpublic data under Minnesota Statutes, 
2.22 	section 13.392. The contractor or subcontractor must make the data collected by the software 
2.23 	accessible to auditors of the contractor or of the agency and to a state or federal agency for 
2.24 	purposes related to tax administration or an audit or civil investigation. The contractor or 
2.25 	subcontractor must retrieve data on request of the agency, in the format requested by the 
2.26 	agency, at any time during the seven years as needed to comply with requests under 
2.27 	Minnesota Statutes, chapter 13, at no charge to the agency.
2.28 		Subd. 5.Legislative report. By December 15, 2020, the commissioner of administration 
2.29 	must submit a legislative report on use of the verification software to the chairs and ranking 
2.30 	minority members of the legislative committees with jurisdiction over state government 
2.31 	finance and operations and transportation policy and finance. At a minimum, the report 
2.32 	must include a summary of the contracts entered into and verification software used, a 
3.1 	review of impacts of the verification software, and recommendations for implementing 
3.2 	verification software requirements.

3.3 	EFFECTIVE DATE. This section is effective the day following final enactment and 
3.4 	applies for contracts entered into on or after that date.