Skip to main content Skip to office menu Skip to footer
Minnesota Legislature

Office of the Revisor of Statutes

SF 3133

1st Unofficial Engrossment - 90th Legislature (2017 - 2018) Posted on 03/21/2018 12:41pm

KEY: stricken = removed, old language.
underscored = added, new language.
Line numbers 1.1 1.2 1.3 1.4 1.5
1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24 2.25 2.26 2.27 2.28 2.29 2.30 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 3.30 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25 4.26 4.27 4.28 4.29 4.30 4.31 4.32 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.28 5.29 5.30 5.31 5.32 6.1 6.2 6.3 6.4 6.5 6.6 6.7
6.8

A bill for an act
relating to public safety; establishing certain requirements with respect to the
development and implementation of the Minnesota Licensing and Registration
System; appropriating money; requiring a report.

BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:

Section 1. new text beginMNLARS SUPPLEMENTAL APPROPRIATION; IMPLEMENTATION
REQUIREMENTS.
new text end

new text begin Subdivision 1. new text end

new text begin Supplemental appropriations. new text end

new text begin (a) The following amounts are
appropriated in fiscal year 2018 to the commissioner of public safety to develop, deploy,
operate, and maintain the driver and vehicle information system known as the Minnesota
Licensing and Registration System (MNLARS):
new text end

new text begin (1) $7,500,000 from the driver services operating account in the special revenue fund;
and
new text end

new text begin (2) $2,500,000 from the vehicle services operating account in the special revenue fund.
new text end

new text begin (b) The appropriations in this subdivision must be expended only in the specified amounts
for the following purposes:
new text end

new text begin (1) $551,000 for driver and vehicle services staffing, to perform general duties and
functions of driver and vehicle services;
new text end

new text begin (2) $694,000 for driver and vehicle services staffing, to support development and
implementation activities of the contracted driver services component of MNLARS;
new text end

new text begin (3) $195,000 for driver and vehicle services business costs, to expand customer service
and public information center capacity through additional staff and associated hardware
and software equipment;
new text end

new text begin (4) $4,776,000 for contracting, to perform software development on the vehicle services
component of MNLARS;
new text end

new text begin (5) $560,000 for driver and vehicle services staffing, to support ongoing development
activities of the vehicle services component of MNLARS;
new text end

new text begin (6) $624,000 for Office of MN.IT Services staffing, to support ongoing development
activities of the vehicle services component of MNLARS; and
new text end

new text begin (7) $2,599,000 for technology costs, which consists of:
new text end

new text begin (i) $100,000 for user authentication and access control management;
new text end

new text begin (ii) $20,000 for testing environment hardware, including servers and data storage;
new text end

new text begin (iii) $650,000 for partial relocation of data from the enterprise data center;
new text end

new text begin (iv) $780,000 for disaster recovery preparedness; and
new text end

new text begin (v) $1,049,000 for contracted software review and software development support services.
new text end

new text begin (c) The appropriations in this subdivision are onetime appropriations. Notwithstanding
Minnesota Statutes, section 16A.28, subdivision 1, the unencumbered balances of the
appropriations in this subdivision cancel on June 30, 2018, to the driver services operating
account or the vehicle services operating account, as appropriate.
new text end

new text begin Subd. 2. new text end

new text begin Executive agency appropriations; targeted reductions; transfer. new text end

new text begin (a) By
October 31, 2018, the commissioner of management and budget must, with the approval of
the governor and after consulting the Legislative Advisory Commission, reduce general
fund appropriations for executive agency operating expenditures by $10,000,000 for the
biennium ending June 30, 2019. In making reductions, the commissioner must prioritize
reductions to any increased central operating or administrative expenses within an agency
that resulted from the enactment of operating adjustments for that agency for the biennium
ending June 30, 2019, compared to appropriations enacted for the agency for the biennium
ending June 30, 2017. The commissioner must not reduce appropriations for client-facing
health care, corrections, public safety, mental health programs, or other services that are
provided directly to members of the public.
new text end

new text begin (b) By June 30, 2018, the commissioner of management and budget must transfer
$10,000,000 from the general fund to the driver services operating account in the special
revenue fund.
new text end

new text begin (c) For purposes of this subdivision, "executive agency" has the meaning given in
Minnesota Statutes, section 16A.011, subdivision 12, and includes constitutional officers.
new text end

new text begin Subd. 3. new text end

new text begin Project schedule; performance measures. new text end

new text begin (a) By the first business day after
21 days following the effective date of this section, the commissioner of management and
budget, in consultation with the commissioner of public safety and the state chief information
officer, must (1) establish a project schedule for the driver and vehicle information system
known as the Minnesota Licensing and Registration System (MNLARS), with specific
deadlines and milestones and based on the MNLARS Project Roadmap proposed in January
2018, and (2) develop performance measures for the MNLARS project.
new text end

new text begin (b) At a minimum, the performance measures must provide specific metrics to monitor
MNLARS development and implementation activities, including measures of:
new text end

new text begin (1) the extent to which MNLARS defects have been resolved;
new text end

new text begin (2) the extent to which gaps in MNLARS functionality have been resolved;
new text end

new text begin (3) improvements in the ability of MNLARS users to edit transactions;
new text end

new text begin (4) reduction in the backlog of vehicle titles;
new text end

new text begin (5) the extent of errors in driver or vehicle transactions;
new text end

new text begin (6) system performance, including the extent of any slowdowns, outages, or other system
performance issues;
new text end

new text begin (7) customer service responsiveness, which may include the number of phone calls and
e-mails from the general public and stakeholders, and the timeliness of inquiry responses;
and
new text end

new text begin (8) deputy registrar satisfaction.
new text end

new text begin (c) The commissioner must submit the performance measures to the members and staff
of the legislative committees with jurisdiction over transportation policy and finance, state
government finance, and technology and responsive government.
new text end

new text begin (d) The performance measures under this subdivision are not administrative rules and
are not subject to Minnesota Statutes, chapter 14.
new text end

new text begin Subd. 4. new text end

new text begin Progress reporting. new text end

new text begin (a) On a monthly basis, the commissioner of public safety
and the state chief information officer must jointly provide progress reports on the Minnesota
Licensing and Registration System (MNLARS) project. At a minimum, each progress report
must identify activity and status toward successfully meeting outcomes within the project
schedule and within the project budget, including but not limited to:
new text end

new text begin (1) whether deadlines under the project schedule have been met and, if not, information
on schedule revisions to meet the deadlines;
new text end

new text begin (2) an overview of project activity during the preceding month and the total amount
spent on each activity;
new text end

new text begin (3) information on project staffing and contractors including, separately, the amount
spent for state employees and the amount spent for private contractors in the preceding
month, itemized by the number of employees and contractors, the duties of each related to
the project, and the agency responsible for their work;
new text end

new text begin (4) a summary of any new challenges or risks that were identified in the preceding month;
new text end

new text begin (5) a summary of any additional or unexpected costs that were identified in the preceding
month, including a detailed explanation of the costs and why the costs had not been identified
previously, the source and an itemization of funds expected to be used to cover the costs,
and the specific steps taken to reduce costs in other project activities to ensure the overall
project cost remains within the budget appropriated by law;
new text end

new text begin (6) details on the status for each performance measure established under subdivision 3;
and
new text end

new text begin (7) a clear statement, signed separately by the commissioner and the state chief
information officer, that certifies whether, as of the time of the report, the project is on
schedule and within the budget appropriated by law, and that includes the following: "I
affirm that the statements submitted to the Legislature in this document are complete and
truthful to the best of my knowledge."
new text end

new text begin (b) The commissioner of management and budget must submit each progress report
under paragraph (a) to the chairs, ranking minority members, and staff of the legislative
committees with jurisdiction over transportation policy and finance, state government
finance, and technology and responsive government.
new text end

new text begin (c) The requirements under this subdivision expire upon full implementation of
MNLARS, which includes but is not limited to resolution of all significant defects,
implementation of all functionality gaps identified in the project schedule, and
decommissioning of the legacy driver and vehicle services information technology system.
new text end

new text begin Subd. 5. new text end

new text begin Request for information. new text end

new text begin (a) No later than April 1, 2018, the commissioner
of public safety must issue a request for information as described in this subdivision. The
request for information must obtain advice from qualified vendors regarding the feasibility
of using a private vendor to develop, deploy, and maintain a driver and vehicle information
system that replaces the system known as the Minnesota Licensing and Registration System
(MNLARS).
new text end

new text begin (b) The request for information must solicit advice on procuring a replacement driver
and vehicle information system that:
new text end

new text begin (1) is cost-effective, reliable, consumer- and user-friendly, and implemented in a timely
manner; and
new text end

new text begin (2) contains functionality that substantially matches the functionality and features of the
legacy information technology system in place prior to initial implementation of MNLARS.
new text end

new text begin (c) The request for information must be designed to obtain implementation information
that includes:
new text end

new text begin (1) feasibility, costs, and a preliminary estimated timeline or schedule for implementation;
new text end

new text begin (2) a breakdown of costs and implementation timelines between driver services and
vehicle services functionality, including costs of integrating a vehicle services information
system with a separately developed driver services information system; and
new text end

new text begin (3) capacity and experience of a potential vendor.
new text end

new text begin (d) The request for information under this section must be published in the State Register
and on the Web site of the Department of Administration at least 14 days prior to closing.
The request must otherwise be administered according to the requirements of Minnesota
Statutes, chapter 16C, to the extent applicable, provided that a vendor's submission does
not constitute a response to a solicitation, as defined in Minnesota Statutes, section 16C.02,
subdivision 14, and may not be used by the commissioner to enter a contract unless the
terms of the submission are later included in a vendor's response to a formal solicitation,
as defined in Minnesota Statutes, section 16C.02, subdivision 7.
new text end

new text begin (e) No later than August 1, 2018, the commissioner must submit a report to the chairs,
ranking minority members, and staff of the legislative committees with jurisdiction over
transportation policy and finance, state government finance, and technology and responsive
government, that summarizes the responses received from qualified vendors under this
section.
new text end

new text begin Subd. 6. new text end

new text begin REAL ID Act extensions. new text end

new text begin The commissioner of public safety must coordinate
with the governor to seek any extensions available from the United States Department of
Homeland Security with respect to federal enforcement of the REAL ID Act of 2005, Public
Law 109-13, Division B. The commissioner must make all feasible efforts to promptly
obtain extensions.
new text end

new text begin EFFECTIVE DATE. new text end

new text begin This section is effective the day following final enactment.
new text end