SF 3133

4th Engrossment - 90th Legislature (2017 - 2018) Posted on 03/27/2018 08:28am

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; requiring a report; appropriating money.

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

Section 1. new text begin MNLARS SUPPLEMENTAL APPROPRIATIONS; REDUCTIONS,
TRANSFERS.
new text end

new text begin Subdivision 1. new text end

new text begin Appropriations; MNLARS. new text end

new text begin $9,650,000 in fiscal year 2018 is
appropriated from the special revenue fund to the commissioner of public safety for costs
related to continued development, improvement, operations, and deployment of the driver
and vehicle services information system known as the Minnesota Licensing and Registration
System (MNLARS). Of this amount, $2,150,000 is from the vehicle services operating
account and $7,500,000 is from the driver services operating account. This is a onetime
appropriation.
new text end

new text begin Subd. 2. new text end

new text begin Appropriations; Office of the Legislative Auditor. new text end

new text begin $100,000 in fiscal year
2018 and $250,000 in fiscal year 2019 are appropriated to the Office of the Legislative
Auditor from the vehicle services operating account in the special revenue fund for the
information technology auditor position established in section 3. This is a onetime
appropriation.
new text end

new text begin Subd. 3. new text end

new text begin Use of funds. new text end

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

new text begin (1) $7,051,000 for contracting to perform software development on the vehicle services
component of MNLARS; and
new text end

new text begin (2) $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 (b) The appropriations in this section must not be spent on:
new text end

new text begin (1) additional full- or part-time employees employed by the Department of Public Safety;
or
new text end

new text begin (2) an audit, evaluation, or assessment on the feasibility of a proposed plan to resolve
MNLARS defects and implement all MNLARS functionality conducted by the Department
of Public Safety, the Office of MN.IT Services, or an entity hired by the Department of
Public Safety or the Office of MN.IT Services.
new text end

new text begin Subd. 4. new text end

new text begin Adjustments. new text end

new text begin After May 1, 2018, if the commissioner of public safety and
state chief information officer determine the amounts allocated in subdivision 3 need to be
adjusted, the commissioner and state chief information officer may submit to the MNLARS
Steering Committee established under section 4 a request to adjust the allocated amounts
within existing appropriations. The commissioner and state chief information officer must
provide, at a minimum, the proposed changes and a line item explanation of how the
reallocated funds would be spent. The commissioner and state chief information officer
must also submit a written explanation of the need to adjust the funds. A majority of the
committee may, by affirmative vote, approve the adjustment to the appropriation amounts
in subdivision 3.
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

Sec. 2. new text begin MNLARS IMPLEMENTATION REQUIREMENTS.
new text end

new text begin Subdivision 1. new text end

new text begin Definitions. new text end

new text begin (a) For purposes of this section, the following terms have
the meanings given them.
new text end

new text begin (b) "Information technology auditor" means the individual appointed by the legislative
auditor under section 3, subdivision 1.
new text end

new text begin (c) "MNLARS" means the driver and vehicle information system known as the Minnesota
Licensing and Registration System.
new text end

new text begin (d) "Committee" means the MNLARS Steering Committee established under section 4.
new text end

new text begin (e) "Quarter" means a three-month period starting on July 1, October 1, January 1, or
April 1, in fiscal year 2019.
new text end

new text begin Subd. 2. new text end

new text begin Project timeline; deadlines; performance measures; plans. new text end

new text begin (a) By May 1,
2018, the commissioner of public safety and the state chief information officer must submit
to the committee:
new text end

new text begin (1) a detailed project budget;
new text end

new text begin (2) a proposed project timeline to develop and implement MNLARS that includes specific
deadlines and performance measures that must be met in each quarter;
new text end

new text begin (3) a proposed plan for user acceptance testing, including deputy registrars and auto
dealers located both outside the metropolitan area and within the metropolitan area, as
defined in Minnesota Statutes, section 473.121, subdivision 2, to the extent such testing is
deemed feasible by the Minnesota Deputy Registrars Association and the Minnesota
Automobile Dealers Association;
new text end

new text begin (4) a proposed plan for system stakeholder input on code releases to MNLARS;
new text end

new text begin (5) a proposed communications plan for transparent reporting on MNLARS outages and
slowdowns to system stakeholders, including how to communicate (i) status information
in a timely manner and usable format, (ii) actions taken in response to communication, and
(iii) responses from the Department of Public Safety and the Office of MN.IT Services;
new text end

new text begin (6) a proposed communications plan for postrelease reporting on features and fixes to
system stakeholders; and
new text end

new text begin (7) a proposed plan to create greater efficiencies and streamline the vehicle title process
to reduce the current backlog and to minimize any future backlogs.
new text end

new text begin (b) At a minimum, the performance measures required under paragraph (a), clause (2),
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; and
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.
new text end

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

new text begin Subd. 3. new text end

new text begin Progress reporting. new text end

new text begin (a) By May 1, 2018, and between 20 and 30 days before
the start of each quarter, the commissioner of public safety and the state chief information
officer must submit a progress report to the committee and the information technology
auditor. At a minimum, each progress report must identify MNLARS project activity,
including but not limited to:
new text end

new text begin (1) information sufficient to determine whether deadlines under the project timeline
have been met, and an explanation of the circumstances for any deadlines that have not
been met;
new text end

new text begin (2) details on the status in achieving each performance measure;
new text end

new text begin (3) an overview of project activity during the reporting period, including compliance
with each of the plans;
new text end

new text begin (4) information on project staffing and contractors, including separate lists detailing the
amount spent for state employees and the amount spent for private contractors in the
preceding quarter, itemized by the number of employees and contractors, the project duties
for each, and the agency responsible for employees' or contractors' work; and
new text end

new text begin (5) information on any additional or unexpected costs identified to date, including a
detailed explanation of the additional or unexpected costs and the specific steps taken to
reduce other costs to ensure the overall MNLARS project expenditures remain within the
project budget.
new text end

new text begin (b) Each report must include the statement "I affirm that the statements submitted to the
committee in this document are complete and truthful to the best of my knowledge." The
commissioner of public safety and the state chief information officer must each sign an
acknowledgment of this statement.
new text end

new text begin Subd. 4. new text end

new text begin Stakeholder reporting. new text end

new text begin Between 20 and 30 days before the start of each
quarter, the Minnesota Deputy Registrars Association, the Minnesota Automobile Dealers
Association, and any other stakeholders are each encouraged to submit a report to the
committee regarding the progress on the relevant performance measures established under
subdivision 2, paragraph (b).
new text end

new text begin Subd. 5. new text end

new text begin Request for information; report. new text end

new text begin (a) No later than May 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 vehicle
information system that replaces functionality in MNLARS.
new text end

new text begin (b) The request for information must solicit advice on procuring a replacement 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 for vehicle services components and 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, except that a vendor's submission does not
constitute a response to a solicitation, as defined in Minnesota Statutes, section 16C.02,
subdivision 14. The commissioner is prohibited from using a vendor submission in response
to a request for information under this section 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 committee
and the information technology auditor that summarizes the responses and information
received from qualified vendors under this section.
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

Sec. 3. new text begin INFORMATION TECHNOLOGY AUDITOR; MNLARS ASSESSMENTS.
new text end

new text begin Subdivision 1. new text end

new text begin Appointment. new text end

new text begin The legislative auditor must appoint an information
technology auditor to actively monitor and report on the development and implementation
of the Minnesota Licensing and Registration System (MNLARS). At a minimum, the person
appointed to this position must have expertise in .NET software development and must have
project management experience.
new text end

new text begin Subd. 2. new text end

new text begin Duties. new text end

new text begin (a) The information technology auditor must conduct an assessment of
MNLARS. Upon completion, the assessment must be provided to the MNLARS Steering
Committee established under section 4. At a minimum, the assessment must include:
new text end

new text begin (1) a technical assessment of MNLARS;
new text end

new text begin (2) an assessment on the feasibility of the MNLARS Project Roadmap proposed by the
Department of Public Safety and the Office of MN.IT Services in January 2018, and the
project timeline under section 2, subdivision 2;
new text end

new text begin (3) an assessment of estimated funding needs for the continued development, operations,
and maintenance of MNLARS; and
new text end

new text begin (4) an assessment of process changes and business workflows for auto dealers and deputy
registrars.
new text end

new text begin (b) Each quarter, the information technology auditor must report to the MNLARS Steering
Committee whether the commissioner of public safety and the state chief information officer
are:
new text end

new text begin (1) meeting the deadlines and performance measures in the project timeline required in
section 2, subdivision 2; and
new text end

new text begin (2) in compliance with the plans required in section 2, subdivision 2.
new text end

new text begin (c) The quarterly reports under paragraph (b) must be submitted to the committee between
20 and 30 days before the start of each quarter.
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

Sec. 4. new text begin MNLARS STEERING COMMITTEE; QUARTERLY FUNDING REVIEW.
new text end

new text begin Subdivision 1. new text end

new text begin Definitions. new text end

new text begin (a) For purposes of this section, the following terms have
the meanings given.
new text end

new text begin (b) "Committee" means the MNLARS Steering Committee established in this section.
new text end

new text begin (c) "Commissioner" means the commissioner of management and budget or the
commissioner's designee.
new text end

new text begin (d) "MNLARS" means the driver and vehicle information system known as the Minnesota
Licensing and Registration System.
new text end

new text begin (e) "Information technology auditor" means the individual appointed by the legislative
auditor pursuant to section 3, subdivision 1.
new text end

new text begin (f) "Quarter" means a three-month period starting on July 1, October 1, January 1, or
April 1, in fiscal year 2019.
new text end

new text begin Subd. 2. new text end

new text begin MNLARS Steering Committee; membership. new text end

new text begin (a) A MNLARS Steering
Committee is established. The committee is made up of the following members:
new text end

new text begin (1) the chair of the senate Finance Committee, or a senator appointed by the chair of the
senate Finance Committee;
new text end

new text begin (2) the chair and ranking minority member of the senate committee with jurisdiction
over transportation finance;
new text end

new text begin (3) the chair of the house of representatives Ways and Means Committee, or a member
of the house of representatives appointed by the chair of the house of representatives Ways
and Means Committee; and
new text end

new text begin (4) the chair and ranking minority member of the house of representatives committee
with jurisdiction over transportation finance.
new text end

new text begin Subd. 3. new text end

new text begin Meetings. new text end

new text begin (a) The senate chair of the committee with jurisdiction over
transportation finance must convene the initial meeting of the committee by May 1, 2018.
new text end

new text begin (b) The chairs of the house of representatives and senate committees with jurisdiction
over transportation finance serve as cochairs of the committee.
new text end

new text begin (c) The committee must meet at least once each quarter.
new text end

new text begin (d) The committee is subject to Minnesota Statutes, section 3.055, except that a member
may vote by submitting a written statement indicating how the member votes on a motion.
This written statement must be treated in the same manner as the votes of the members
present at the meeting. The vote must be submitted to all members prior to the start of the
meeting at which the vote will take place.
new text end

new text begin (e) The Legislative Coordinating Commission must provide meeting space and
administrative support for the committee.
new text end

new text begin Subd. 4. new text end

new text begin Committee duties. new text end

new text begin (a) The committee must review the proposed timeline,
including deadlines and performance measures, and the proposed plans submitted under
section 2, subdivision 2. The committee may request that the commissioner of public safety
and the state chief information officer make changes to the timeline and plans. Prior to
reviewing the July 1 quarterly allotment, the committee must approve a timeline and plans.
The cochairs must transmit copies of the timeline and plans to the information technology
auditor.
new text end

new text begin (b) The committee must review (1) the progress reports submitted under section 2,
subdivision 3; (2) reports from the information technology auditor under section 3,
subdivision 2; and (3) quarterly appropriations as provided in subdivision 5.
new text end

new text begin (c) The committee may contract with, hire, or otherwise consult with any individual to
assist the committee with its duties.
new text end

new text begin Subd. 5. new text end

new text begin Review of appropriations. new text end

new text begin (a) Funds appropriated in fiscal year 2019 to the
commissioner of public safety for MNLARS are divided into four equal quarters. The
commissioner must allot a quarter of the funds on July 1, October 1, January 1, and April
1, unless otherwise directed by the committee under this section. Twenty days prior to the
start of a quarter, the commissioner must submit a proposal to allot funds for MNLARS to
the members of the committee for review and recommendation.
new text end

new text begin (b) The committee members have 20 days from the receipt of a proposal to determine
whether the Department of Public Safety and the Office of MN.IT Services have met the
deadlines and performance measures established in section 2, subdivision 2. If during the
20-day review period a majority of the committee members affirmatively votes to:
new text end

new text begin (1) defer, reduce, or further condition the next quarterly allotment based on the failure
to meet deadlines or performance measures; or
new text end

new text begin (2) recommend further review to determine whether deadlines and performance measures
have been met,
new text end

new text begin the commissioner must defer, reduce, or condition the quarterly funds as provided in the
committee vote. If the committee votes to recommend further review, the commissioner
must defer the next quarterly payment.
new text end

new text begin (c) A committee member, by written notice to the commissioner, may withdraw the
member's affirmative vote made under paragraph (b) within 20 days of the vote. If within
20 days of the vote one or more members withdraw an affirmative vote under this paragraph
so that three or fewer affirmative votes remain, the commissioner may allot the quarterly
funds to the commissioner of public safety for MNLARS.
new text end

new text begin (d) If a quarterly allotment is not made under paragraph (a) or (b), the commissioner
must allot to the commissioner of public safety an amount sufficient to fund an additional
30 days for contracted technical staff working on MNLARS.
new text end

new text begin Subd. 6. new text end

new text begin Resubmission of proposal. new text end

new text begin If a proposed allotment is deferred under subdivision
5, the commissioner may submit proposed legislation to the chairs of the house of
representatives Ways and Means Committee and the senate Finance Committee for
consideration during the 2019 legislative session.
new text end

new text begin EFFECTIVE DATE; APPLICATION. new text end

new text begin This section is effective the day following
final enactment. Subdivisions 4 and 5 apply to any money appropriated in fiscal year 2019
for MNLARS in this act or any subsequent act.
new text end

Sec. 5. 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

Sec. 6. new text begin EXPIRATION.
new text end

new text begin Section 2, subdivisions 2 to 4, and section 4, 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 timeline, and
decommissioning of the legacy driver and vehicle services information technology system.
The MNLARS Steering Committee must determine when MNLARS is fully implemented.
new text end

Sec. 7. new text begin SEVERABILITY.
new text end

new text begin If any provision of sections 1 to 6 or its application to any person or circumstances is
held invalid, the invalidity does not affect other provisions or applications of sections 1 to
6 that can be given effect without the invalid provision or application. The provisions of
this section are severable.
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