RFI NTA Enterprise Software Final v3~1.docx

NTA Database Solutions – Request for Information

State of Nevada, Department of Business & Industry, Nevada Transportation Agency Request For Information (RFI) for a Licensing & Enforcement Software Solution June/July 2024

State of Nevada, Department of Business & Industry, Nevada Transportation Authority Request For Information for an Enterprise Software Solution

Contents

Introduction

The State of Nevada Department of Business and Industry, Nevada Transportation Authority (“NTA”) is currently seeking an enterprise software solution that will support NTA’s core business functions. The solution will need to be built using their current technology and enabling a transfer to a new system to support NTA’s operations. In addition to the software, the vendor will need to provide services to implement and maintain the system and provide training and ongoing support.

The purpose of this document is to reach out and identify viable vendors/contractors who have implemented similar systems and estimate the cost and timeline to implement a solution for the NTA.

Note: This is not a Request For Proposal (RFP) so there are no restrictions on communication between the state and vendors/contractor. Also, RFI responses do not represent a contractual agreement between the vendor/contractor and the state.

We encourage interested and qualified vendors to participate in this RFI process.

NTA Website: https://nta.nv.gov/

Contractor Submission and Timeline

Please send email correspondence to this email address: jberry@nta.nv.gov , hdibart@nta.nv.gov; and kgreynolds@business.nv.gov.

The following outlines our next steps in the RFI process:

· Step 1 – Question & Answers – Vendors can submit their questions to NTA up to Friday July 19ths. Email questions:

· Title email subject: NTA RFI – Questions

· Body of email: Include your questions

· To: Include all three of the above individuals

· Step 2 – Vendors to submit your RFI Responses. Respond by Friday, July 26, 2024.

· Title email subject: NTA RFI - Submission

· Body of email: Attach your RFI submission response

· To: Include all three of the above individuals

Project Funding

NTA will need to secure additional funding from the Governor’s Finance Office. This will include both one-time implementation and ongoing costs.

Project Overview

The State of Nevada Transportation Authority (NTA) is currently seeking an enterprise software solution that will support their core business requirements. This will replace their legacy standalone systems. The general scope of work is to assess, design, develop, implement, and provide data conversion and maintenance services for licensing software for NTA:

· The aim is to transition from legacy aging software program(s) with limited support to one integrated seamless program that includes: Driver’s Application Processing, Carrier Processing, Permitting, Registration, Compliance, Payments and Administrative functions without losing any operational functionality.

· The new system will allow the NTA to create accounts and provide the ability to view, apply, change, renew and submit information pertaining to their licenses, Permits, Registrations or services online.

· The new system shall have capacity for enhancements through the next 5-10 years.

· The new system shall have reliable support from the contractor to resolve system issues.

· The new system will be flexible and stable enough to allow Agency staff to resolve all their customer service issues within the system and while online.

· The new system will allow Agency staff to update specified control data maintenance and templates, so the system can remain current with standards. The Agency may require vendor to add/select additional features during this development.

· The system shall meet the security requirements as defined by Governor’s Office of the CIO (OCIO).

· The system shall be stable without crashes, available 24/7 and maintain data and functional integrity.

· The vendor shall have the ability to host and provide a cloud storage solution for the entire operation.

· In the event that NTA and the vendor terminate the contract, the vendor will provide NTA all it’s data (including attached electronic documents) in a timely and organized manner so that NTA can migrate to a new system. The vendor shall return NTA’s data in a format the conforms to:

· Industry standard format, such as Microsoft SQL Server DB, Oracle DB, csv, etc.

· The data files must include all data keys (primary, secondary, etc.) to link tables.

Goals and Objects

The Nevada Transportation Authority (NTA) administers and enforces state laws pertaining to passenger transportation, household goods movers, storage of household goods, and tow cars. The NTA has been charged with the responsibility of providing fair and impartial regulation, to promote safe, adequate, economical and efficient service, and to foster sound economic conditions in motor transportation. The NTA encourages the establishment and maintenance of reasonable charges for intrastate transportation by fully regulated carriers and non-consent towing services. The NTA also has responsibility for the taxicab industry throughout the state except in Clark County. Statutory Authority: NRS 706, 706A, 706B and 712.

In light of this, the following objectives are highly desirable outcomes of this RFI and replacement process:

· Support business processes with a next generation software platform for the future. Choose a solution that is easy to implement and easy to understand, but designed for configurability so that we can match our business processes as much as possible.

· Have greater flexibility in adapting the out-of-the-box user interface to fit NTA’s business practices. In particular, a more “role based” interface, where particular staff can see all the information relevant to them, and not have to see things they use less often.

· Have a more robust workflow engine, with greater capabilities for providing workflow automation and customization, better tools for enforcing data rules and business rules, and a flexible tool set to quickly respond to future statute and regulation changes, reporting, directives and business process changes.

· Decrease complexity and our maintenance burden through good design, use of best practices, reliance on industry standard platforms and technologies, and greater re-use of code and business rules.

· Go beyond our current internal limitations and provide additional capabilities such as uniquely required functionalities within the 1) Compliance Team 2) Enforcement Team and 3.) Tariffs/Applications Teams as well as allow for cross functionality between these teams, mobile access, electronic review/markup, business intelligence, cloud-based computing, and post-license monitoring.

· Provide training and support help as needed during and after the process;

· Migration of all data from the existing database(s) to the new database;

· Data security;

· Online dashboard

· Vendor hosting and cloud storage, no equipment on site;

· 24/7 System availability;

· Allow limited access to third party’s (i.e. Carriers and/or Driver to share, transfer and upload data;

· Ability to accept online payments, e-checks, mobile payments etc.;

· Enhanced reporting functionality;

· Meet State of Nevada security requirements; and

· System should be capable of enhancements through the next 5-10 years.

Project Background

NTA has limited support for their Drivers, Carrier and Enforcement Databases. The use of the current model is antiquated, not flexible and the NTA must backup the databases each day to ensure that we can retain the data.

Agency Background

The Nevada Transportation Authority administers and enforces state laws pertaining to passenger transportation, household goods movers, storage of household goods, and tow cars. The NTA has offices in both Las Vegas and Reno with 43 employees. The Governor appoints three Commissioners to act as Hearing Officers as it relates to citations, impounding of vehicles, etc. The Agency is supported by five primary units:

· Applications/Administration

· Commissioners

· Compliance

· Enforcement

· Legal

A brief description of each area’s duties are listed below:

Applications/Administration:

· Provides front end customer service support and primary data entry support for the NTA.

· Review Annual Reports for Motor Carriers – financials, annual reports, tariffs, applications.

· Develop public notices, orders for General Session Meetings.

· Provide preparation materials for general session including backup materials.

· Research projects.

· Handle Public Records Requests.

· Process interim requests.

· Issue final tariffs and certificates.

· Track deadlines, temporary approvals, temporary discontinuances, temporary transfers of operating rights, PLTIs.

· Request hearings to be performed and testify at hearings as required.

· Track /monitor Transportation Network Company (“TNC”) changes – rates

· Review work of Financial analysts, and compliance reports – domicile, backgrounds, compliance

· Update annual reports each year for fully regulated carriers and TNC’s.

Commissioners:

· Conduct hearings and other proceedings.

· Help assist in writing regulations as necessary.

· Hold open meetings, and special sessions as necessary.

· Implement the laws under the 706, 706A, 706B and 712.

Compliance:

· Conducts comprehensive background investigations of carriers and drivers.

· Performs investigative and auditing functions to monitor compliance and detect violations of federal and/or state laws.

· Gathers and analyzes information and facts to make determinations regarding the extent of violations and issues citations based on findings.

· Develops case files and maintains case logs to record progression of cases.

· Prepares investigative and audit reports encompassing any identified violations, case summary, exhibits of evidence, conclusions, and recommendations; appears before commission to provide testimony.

Enforcement:

· Performs surveillance and/or covert activities by visually observing and recording information, taking photographs, and/or requesting services to gather facts, evidence or develop leads to detect violations of state and federal laws, rules, and regulations. Enforcement actions involve verbal or written warnings, operational stings resulting in the issuance of criminal and administrative citations, and/or arrests. Enforcement action is determined at the investigator’s discretion, consistent with appropriate laws, rules, regulations, policy, and procedure.

· Travels to various business and office locations for the purpose of completing casework, investigations, business inspections and other assignments as directed.

· Conducts interviews of the complainants, witnesses, employers, suspects, state and local governmental agencies and either sources to obtain information regarding violations or noncompliance; develops leads and facts pertaining to case to prove a violation exists.

· Develop case files and maintain case logs and reports, gathers evidence, and maintains chronological documentation regarding investigative steps taken and all contact made with complainant, respondent, witness, and other sources. Information is utilized to develop final case reports, administrative actions and/or criminal prosecution.

· Testify in administrative and criminal proceedings.

Legal:

· Advise Commissioners on the NRS and NAC and its applicability.

· Sit in on all hearings with the Commissioners.

· Attend all general and special sessions.

· Ensure all Commissioners follow the Nevada Open Meeting Laws.

· Communicate with the Commissioners separately on key issues.

· Respond to any and all legal questions pertaining to the NTA and its operations.

Current Computing Environment

Desktop PCs and Laptops The desktop PCs and Laptops run the Windows 11 operating system. NTA staff utilize Microsoft Office 365 desktop software (Word, Excel, PowerPoint, etc.).

Servers The server environment is Microsoft Server 2022.

Network The Department of Business & Industry (including NTA) utilizes the State of Nevada wide-area network, called Silvernet. Silvernet is managed by the State of Nevada Office of the CIO.

Current Systems NTA has several database applications based on .Net and SQL Server that are hosted on state virtual servers.

System Requirements

System Functions The new system shall automate and streamline NTA’s core business functions. This includes:

· Licensing of transportation carriers (companies).

· Applications

· Renewals

· Permitting of passenger drivers.

· Applications

· Renewals

· Driver association to carriers (a driver can be associated with up to 4 companies at any given time.

· Tracking transportation company’s fleets/vehicles

· Vehicle data

· NTA issued decals/stickers/plates

· Status – in/out of service

· Compliance with annual inspection from certified mechanic

· Compliance/Enforcement

· Compliance/enforcement staff need quick access to carrier, driver, vehicle information while in the field

· Issue and track citations

· Issue hearing date related to a citation

· Case Management

· Process cases through the complete lifecycle

· Capture case hearing results

· Track compliance actions

· Track fines and penalties Security The system shall meet State security standards for transmission of personal information as outlined in NRS 205.4742 and NRS 603A.

Protection of sensitive information shall include the following:

· Confidential personal data shall be encrypted.

· Any electronic transmission of personal information shall comply with NRS 603A.215 (2 & 3).

· Sensitive data shall be encrypted in all newly developed applications.

All information technology services and systems developed or acquired by agencies shall have documented security specifications that include an analysis of security risks and recommended controls (including access control systems and contingency plans).

Security requirements shall be developed at the same time system planners define the requirements of the system. Requirements shall permit updating security requirements as new threats/vulnerabilities are identified and/or new technologies implemented.

Security requirements and evaluation/test procedures shall be included in all solicitation documents and/or acquisition specifications.

Systems developed by either internal State or contracted system developers shall not include back doors, or other code that would cause or allow unauthorized access or manipulation of code or data.

Security specifications shall be developed by the system developer for approval by the agency owning the system at appropriate points of the system development or acquisition cycle.

All system development projects shall include a documented change control and approval process and shall address the security implications of all changes recommended and approved to a particular service or system. The responsible agency shall authorize all changes.

Application systems and information that become obsolete and no longer used shall be disposed of by appropriate procedures. The application and associated information shall be preserved, discarded, or destroyed in accordance with Electronic Record and Record Management requirements defined in NRS and NAC 239, Records Management.

Software development projects shall comply with State Information Security Consolidated Policy S.4.07.01, Security for System Development.

· Separate development, test and production environments shall be established on State systems.

· Processes shall be documented and implemented to control the transfer of software from a development environment to a production environment. New hardware/software is not introduced into a production environment until it is fully tested and accepted by the State.

· Development of software and tools shall be maintained on computer systems isolated from a production environment.

· Access to compilers, editors and other system utilities shall be removed from production systems.

· Controls shall be established to issue short-term access to development staff to correct problems with production systems allowing only necessary access.

· Security requirements and controls shall be identified, incorporated in and verified throughout the planning, development, and testing phases of all software development projects. Security staff shall be included in all phases of the System Development Lifecycle (SDLC) from the requirement definitions phase through implementation phase.

Scope of Work and Deliverables

The overall scope is to implement, maintain, and support a fully functional system that supports NTA’s key business functions across its agency. The system must include both backoff functionality (internal NTA users) and a public facing portal (for drivers, constituents, and other stakeholders). The following is a high-level summary of key project deliverables and milestones. NTA is open to contractors proposing a project delivery approach and methodology (e.g., agile method) they believe is appropriate for this project to ensure a successful outcome.

1. Project management, communication, and control.

2. Document and validate relevant NTA requirements, processes, and business rules (this can include a software “gap analysis” if appropriate).

3. System development/configuration/deployment (this should include organized interaction with users/subject matter experts to ensure the system functionality is in alignment with requirements and workflows).

4. Conduct software validation walkthroughs with NTA subject matter experts to verify that the system supports each business process end-to-end.

5. Data conversion/migration (migrate data and electronic documents from the legacy system).

6. User and system administration training.

7. User Acceptance Testing (two primary levels – specific processes/functions, and full end-to-end testing).

8. Go-live cutover to new system.

9. Go-live support for a specific period (e.g., 30 days).

10. Ongoing support and maintenance.

Vendor RFI Response Content

Please email your RFI response to: rfi@nta.nv.gov Below is a list of items vendors should include in their RFI response. Vendors have flexibility on how the information is presented as long as it is clear and concise. Vendors can present more than one option on the implementation approach or cost model. Vendors should include their assumptions where appropriate. The RFI response should include:

1. Introduction section.

2. Vendor contact information (Name/email/phone/address)

3. High-level estimated project timeline.

4. List of similar customers, description of project scope, relevant dates/timeframes, and customer contacts.

5. Estimated Cost – One-time and Ongoing over a 5-year period. Note: Vendor can give an estimated range.

[Example of format that may be used in response]

Implementation

SaaS Licensing

Other Costs

Annual Total

Footnotes/Assumptions:

6. Cost Model – Please describe your cost model, e.g., based on number of named users, number of license types, based on modules, etc.

7. Supplemental Information – Provide any additional information the vendor believes is relevant.

ATTACHMENT A

NTA Requirements Project Document

Please see the NTA Requirements Project document. These documents provide an insight into the NTA’s processes and requirements.

Key Database Fields:

· Driver Permits

· Enforcement

· Carrier (Company)

Fields used in each database:

Driver Database Fields (User Interface - Tabs):

Carrier Database Fields (Shows main tables with key required fields):

Enforcement Database Field (Authority/company type, Disposition Resolution, Reason for Investigation):

image1.emf

Business Requirements NTA Final.xlsx Driver Permit Database

Driver Permit Database

Req # Feature As a (role) Requirement Enhanced Requirement Version #

1.1 Combined database for NTA Administrator Role The ability add and edit Drivers Permits 1

1.2 Combined database for NTA Administrator Role New source code as we don't have access to the current source code

1.3 Combined database for NTA Administrator Role The ability to add/update and disable carriers 2

1.4 Combined database for NTA Administrator Role Require enforcement officers to be able to login and find data on drivers and carriers 3

1.5 Combined database for NTA Administrator Role A web based program 1

2.1 PII Security Administrator Role The site to be in PII Compliance 1

2.2 PII Security Administrator Role The program must comply with state security policies and standards. 1

2.21 PII Security As a https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/ 1

As a A configuration area for the auto-generated permit and application number A configuration area for the auto-generated permit and application number

3 Permit Application User Role Ability to add an application for a new Driver Permit 1

3.1 Permit Application User Role Ability to choose a picture and attach it to the application 1

3.2 Permit Application User Role Ability to configure certain fields to be Mandatory 1

3.3 Permit Application User Role Date Received field and have it be mandatory 1

3.31 Permit Application User Role Ability to click in the date received field and have a calendar pop up to choose a date or manually enter date 1

3.4 Permit Application User Role Provide a Temp Permit Date that is auto populated based on the received date 1

3.5 An Issue date field that will correspond to the printed date by manual entry

3.6 Permit Application User Role Provide an Expiration Date field 1

3.61 Permit Application User Role Provide the Expiration Date field to automatically populates 3 years out based on the issue date: Autogenerated 1

3.7 Permit Application User Role Add Driver Validating Information 1

3.71 Permit Application User Role Add the last 4 digits of the Drivers Social Security Number in a mandatory field 1

3.711 Permit Application User Role Automatically check if the social security number is already being used 1

3.712 Permit Application User Role Ability to see if there is a duplicate social security number 1

3.713 Permit Application User Role Ability to see if there is a duplicate birthday

3.714 Permit Application User Role Do not allow a duplicate entry made if there is a duplicate social security number. 1

3.72 Permit Application User Role Add the Drivers Birthdate as a mandatory field mm/dd/yyyy 1

3.8 Permit Application User Role Add a status area to set for Driver Status and as of date 1

3.81 Permit Application User Role Set the Status of driver 1

3.811 Permit Application User Role Status Active Field = Currently Employed 1

3.812 Permit Application User Role Status Inactive Field: Employer has notified NTA that they have separated from the driver 1

3.813 Permit Application User Role Status Denied Field = Denied based on a hearing 1

3.814 Permit Application User Role A Process Complete check box

3.9 Permit Application User Role The process complete box is an Indicator that have completed the procedure including printing has been completed., There is no way to determine in system that everything was complete. Ideally able to enter to see everything completed accept printing. Would like to see a status of what is complete. A list of tasks of what needs to be completed so we can status. A list of tasks of what needs to be completed so we can status. May have to wait for backgrounds to come back or additional information for background. 2

3.92 Permit Application User Role Add an Application function. 1

3.921 Permit Application User Role Create Application Number to be automatically generated. 1

3.922 Permit Application User Role Application number to be formatted as follows. Number = 4 digit year, 2 digit month, 2 digit day some sequencing numbers following. 1

3.923 Permit Application User Role I want each application number to be unique. 1

3.93 Permit Application User Role Permit application fields cleared after the application has been completed and saved into history 1

3.94 Permit Application User Role New application number assigned(linked) to the corresponding permit number 1

3.941 Permit Application User Role More than one application to be assigned to the corresponding permit number 1

3.95 Permit Application User Role Each driver will have one system generated permit number 1

3.96 Permit Application User Role Each driver can have multiple application numbers under their permit number 1

3.961 Permit Application User Role Each application signifies an application on file 1

3.962 Permit Application User Role Each application to have a unique application number 1

4 Permit Holder List User Role A Permit Holder List to display all Permit Holders Active and Inactive 1

4.1 Permit Holder List User Role Permit Holder list displays on the Permit Application Screen. 1

4.11 Permit Holder List User Role To enhance current search criteria Build out search out criteria, limited in parameters, would like date of birth added, current preview is sufficient, want to search for everything, choose for active or inactive or all, status already included. 2

4.12 Permit Holder List User Role The Permit holder list will display, Last name, First Name and Permit Number 1

5 Search Feature User Role A search feature for permits 1

5.1 Search Feature User Role Search feature to include first name 1

5.12 Search Feature User Role Need search feature to include last name 1

5.13 Search Feature User Role Need search feature to include permit number 1

5.14 Search Feature User Role Need search feature to include Application number 1

5.15 Search Feature User Role Ability to have search feature to include last 4 social security number. 1

5.16 Search Feature Ability to have search feature to include status of active or inactive 1

6 Drivers Personal Information User Role Sections to be able to enter Driver's Personal Information 1

6.1 Personal Information User Role An area to enter personal information 1

6.11 Personal Information User Role Ability to enter the Permit number 1

6.112 Personal Information User Role Ability to enter a date entered 1

6.113 Personal Information User Role Ability to enter applicant last name 1

6.114 Personal Information User Role Ability to enter applicant first name 1

6.115 Personal Information User Role Ability to enter applicant middle initial 1

6.116 Personal Information User Role Ability to be able to enter all names previously or currently being used 1

6.117 Personal Information User Role Ability to enter a mailing address 1

6.118 Personal Information User Role Ability to enter street or po box 1

6.119 Personal Information User Role Ability to enter city 1

6.12 Personal Information User Role Ability to enter state 1

6.121 Personal Information User Role Have a check box for Check here if Residence same as mailing address 1

6.122 Personal Information User Role If residence same as mailing checked auto populate the residence address information 1

6.123 Personal Information User Role Have a gender selection of male or female 1

6.124 Personal Information User Role Ability to have a contact information of phone number and alternate phone number 1

6.125 Employer Details User Role Ability to display all Driver Permit Application below the Status Section 1

6.126 Employer Details User Role Have Columns Headings: Permit #, Last Name, First Name, Application Number 1

6.127 Employer Details User Role When click check box to for view current employer in the Driver Permit Applications all employers will be displayed. 1

6.128 Employer Details User Role Ability to bring in carrier information from the carrier database (ability to update information as needed) Pull carrier data base into SQL server, then in this application can link to the same data base. They will both go to the same database tables. cpcn and name of carrier stay the same this go directly to updated database. carrier move into sql server login the same way. no difference in what you say. Want to see the carrier information here would need to be in phase one. Go to same database tables to pull information. Future roll in we can extend the features. For different feature. future .Merge sql database to have a single view of truth. 1/2

6.129 Employer Details User Role Ability to display the 4 digit CPCN number and corporate name of company 1

6.13 Employer Details User Role Have the name of the Certificated Carrier Employer 1

6.131 Employer Details User Role Ability to display the Start date is entry field date hired 1

6.132 Employer Details User Role Ability to display the End date, day of separation 1

6.134 Employer Details User Role Have an indicator displayed for Current Employer. This also signifies to the system to print only they CPCN with the box checked on the permit card. 1

6.135 Employer Details User Role Have ability to be able to add An Employer 1

6.136 Employer Details User Role No edit available to the Drivers Permit after the permit is printed 1

6.137 Employer Details User Role Only the administrator to have rights to edit the Drivers Permit after the permit is printed 1

6.138 Employer Details User Role N/A 1

6.139 Employer Details User Role Ability to have a change control Log added to current functionality Security of data entry of change control. Log history of who what and when they changed. Make it protected and correlate to their login. No other login can make an entry on another's behalf. 1

6.14 Employer Details User Role Have a change log report created and added to current functionality Requested report functionality. Identify who is entering what. Record specific. How do you want layer out . Everything over date and time and per person. Every time they move fill out a new application. Log and history of person. Moved, added a new company, any changes. 1

7 Child Support Information User Role An area to choose specific options in a section for Child support information 1

7.1 Child Support Information User Role Ability to add the last 4 digits of the drivers license number in the child support information. 1

7.11 Child Support Information User Role A state drop choice for "Other State" 1

7.12 Child Support Information User Role A "Driver History Received? Field" yes or no option 1

7.13 Child Support Information User Role A Save Cancel option at the end of the Child Support Information section 1

8 Background Details User Role Ability to have a section to enter received background details from the background check. The background checks can take months to come back. This section needs to remain editable 1

8.1 Background Details User Role Ability to select the corresponding application number from a drop down that lists application numbers. Mandatory selection. Should auto-populate current application. 1

8.11 Background Details User Role "Type" field with drop for DPS or FBI, mandatory field 1

8.112 Background Details User Role A "Result" drop down field 1

8.113 Background Details User Role Result defaults to Select 1

8.114 Background Details User Role Result options: Positive - Qualify Positive - Do Not Qualify Negative 1

8.115 Background Details User Role Have a Date Received field mandatory 1

8.116 Background Details User Role Have a Date of Hearing field if a hearing is required 1

8.117 Background Details User Role Have a Date Verified field 1

8.118 Background Details User Role Have an Ineligible Driver with choice of yes or no 1

8.119 Background Details User Role Have an Approved at Hearing choice of Yes or No 1

8.12 Background Details User Role Have an Approved at Agenda choice of yes or no 1

8.121 Background Details User Role Have an NTA Fines choice of yes or no 1

8.122 Background Details User Role Have an Amount Owed: field 1

8.123 Background Details User Role Addition of a Not Restricted box 1

8.124 Background Details User Role No restriction text: text box "(will be printed on card)" 1

8.125 Background Details User Role Restriction text: text box "(will be printed on card)" 1

8.126 Background Details User Role Provide for a Save and Cancel button 1

8.127 Background Details User Role Provide for a section for results 1

8.128 Background Details User Role Provide for a Heading for section: Application # Type Result Result Date Edit icon and X icon 1

8.129 Background Details User Role Display of all applications and data for corresponding headings 1

8.13 Background Details User Role The edit button allows anything under the background detail for the application editing to be updated 1

9 Financial Details User Role Provide for a Financial Details Section to record issued receipts 1

9.1 Financial Details User Role Wish to have different types of fields to record data 1

9.11 Financial Details User Role Have a Application # field 1

9.112 Financial Details User Role Have a Receipt No. field, mandatory 1

9.113 Financial Details User Role Payment Amount, field, mandatory 1

9.114 Financial Details User Role Receipt Date, field mandatory 1

9.115 Financial Details User Role Payment Type , drop down mandatory 1

9.117 Financial Details User Role Provide for a Check #, field 1

9.118 Financial Details User Role All of the Financial Details will be editable in the future 1

9.119 Financial Details User Role Provide for a Save and Cancel button 1

10 Notes User Role Develop a textbox to enter notes that have anything to do with the application or driver. 1

10.1 Notes User Role Provide for a save and cancel button 1

10.11 Notes User Role Log user, date and time below the saved note 1

10.112 Notes User Role Notes are shown as separate entries for each one saved 1

10.113 Notes User Role Ensure the notes are able to go to a report 1

11 Driver Report User Role Develop a Driver Report 1

11.1 Driver Report User Role Preview or Print Individual Driver Report 1

11.11 Driver Report User Role Add to Print Queue Option 1

11.112 Driver Report User Role Driver summary to contain: (Items 11.113 to 11.122) 1

11.113 Driver Report User Role Picture of driver 1

11.114 Driver Report User Role Status 1

11.115 Driver Report User Role Permit # 1

11.116 Driver Report User Role Date Received 1

11.117 Driver Report User Role Date Issued 1

11.118 Driver Report User Role Expiration Date 1

11.119 Driver Report User Role Driver Name 1

11.12 Driver Report User Role Address 1

11.121 Driver Report User Role Driver Phone Number 1

11.122 Driver Report User Role Date of Hire 1

11.123 Driver Report User Role Provide a Heading

Current Employer Name's & CPCN/MV's

11.124 Driver Report User Role List CPCN and Certificated Carrier Employer 1

11.125 Driver Report User Role Provide for a Comments section 1

11.126 Driver Report User Role Provide a list of the Notes that were entered under the driver permit 1

11.127 Print Permit User Role Ability to Print an Individual Permit 1

11.128 Print Permit User Role The Permit will Print on an 8 1/2 by 11 sheet of paper 1

11.129 Print Permit User Role Print Permit on Avery Standard Business Cards 1

11.13 Print Permit User Role Ability to batch print on 10 up card stock 1

12 Entry Log User Role Ability to be able to view a log of all activity for the driver application 1

12.11 Entry Log User Role Provide the log to be in a readable format 1

12.112 Entry Log User Role Provide for the log to show the recorded user 1

12.113 Entry Log User Role The log should have a date and time stamp for activity 1

13 Archive User Role Provide an Archive Button 1

13.111 Archive User Role If someone should pass away, ability to archive the Drivers Permit 1

13.112 Archive User Role Need the availability to access the permit after archiving 1

14 Delete Administrator Role Add a delete button for administrator use only 1

14.111 Delete Administrator Role Ability that the delete button is able to remove all records associated with the permit holder Should have a notes section of why you are deleting. Date stamp, and who processed the deletion. 1

15 Print Queue User Role Select permits to be printed 1

15.111 Print Queue User Role Print in Business Card format 1

15.112 Print Queue User Role Ability to click Permit 1

15.113 Print Queue User Role Print front on Avery8371 1

15.114 Print Queue User Role Ability to export to pdf and print Will work with Crystal License.

15.115 Print Queue User Role Print back from copied word document 1/2

16 Administration Administrator Role Develop an Administration Section 1/2

16.111 Administration/User Management Administrator Role Develop a User Management Section under the Administration section 1

16.112 Administration/User Management Administrator Role Ensure there is a Roles section under User Management 1

16.113 Administrator Role Ability to identify roles by Employee 1

16.211 Administration/User Management/User Information Administrator Role Include a Section to include user information 1

16.212 Administration/User Management/User Information Administrator Role Last Name mandatory 1

16.213 Administration/User Management/User Information Administrator Role First Name mandatory 1

16.214 Administration/User Management/User Information Administrator Role Middle Name 1

16.215 Administration/User Management/User Information Administrator Role Gender drop down: Mandatory 1

16.216 Administration/User Management/User Information Administrator Role Date of Birth 1

16.217 Administration/User Management/User Information Administrator Role Email mandatory 1

16.218 Administration/User Management/User Information Administrator Role Role drop down mandatory 1

16.219 Administration/User Management/User Information/Roles Administrator Role Admin: access to all functionality noted below and add new users, archive old users, delete permit entries, generate reports 1

Administration/User Management/User Information/Roles Administrator Role Supervisor: access to all functionality noted below and modify greyed fields for corrections, and generate canned reports, access to add, edit, modify enforcement notes

Administration/User Management/User Information/Roles Administrator Role Processor: ability to search, add, edit and produce permits

Administration/User Management/User Information/Roles Administrator Role Enforcement: ability to view records, create and execute search queries AND have access to enforcement notes. May NOT modify or delete records

Administration/User Management/User Information/Roles Administrator Role Viewer: ability to view records, create and execute search queries - may NOT modify or delete records

16.2191 Administration/User Management/User Information Administrator Role Password: mandatory, Administrator only edits passwords Let the users change their passwords. Admins can set a password, but never will never be able to see a users actual password. 1

16.220 Administration/User Management/User Information Administrator Role Develop a Repeat Password entry field as mandatory 1

16.230 Administration/User Management/User Information Administrator Role The ability to select if a driver is active or inactive 1

16.240 Administration/User Management/User Information Administrator Role A Save button to record the users information 1

16.241 Administration/User Management/User Information Administrator Role A cancel button to return to the entry screen without saving 1

16.311 Administration User List Administrator Role Ability to be able to display a User List 1

16.312 Administration/User List Administrator Role Create a list to show the columns for, Last Name, First Name, and an option to edit the user Have a configuration for Active or Inactive Users. Have a range selection or toggle to show active, inactive or both for User List 1

16.313 Administration/User List Administrator Role A Search option for Active or Inactive users 1

16.314 Administration/User List Administrator Role Ability to be able to enter a First Name 1

16.315 Administration/User List Administrator Role Ability to be able enter a Last Name 1

16.316 Administration/User List Administrator Role Ability to enter an Email address 1

16.317 Administration/User List Administrator Role Ability to select the User Role from a predefined list 1

17 Reports User Role Develop a Reporting program with Predefined Reports 1

17.111 Reports User Role Ability to connect to the Access database for my current reports 1

17.112 Reports User Role The ability to create new reports in access and have them listed in my Reports program 1

17.113 Reports User Role User Report - All Input primary, search from to and user, Permits entered between 2 dates, permits only, separate report for applications. Add filed for Status, status of permit, working on, denied, printed , based on checklist, checkbox. Currently building Crystal Reports. 1/2

17.114 Reports User Role All Applications Received for specified range selections 1

17.115 Reports User Role A permit expiration report. This report will tell you what permits are going to expire based on a date range. This report will be split by the carrier. The goal is to print all carriers at one time, then send (verify if by mail or email) a copy to the corresponding carrier. The columns will be Permit #, Expiration Date, CPCN and Drivers name. There will a total records at the end of the report with a Date and time of run. 1

17.116 Reports User Role Ability to Print Mailing Labels for the carriers. This pulls from carrier data base. Avery label 30 to a page 5160 avery, 10 down 3 across 1 x 2 5/8 1

17.117 Reports User Role A report of company drivers. The report information should contain the driver name, cpcn and company, permit #, date hire, exp date, used by enforcement, print physically per cpcn, status of current is = to active, 1

17.118 Reports User Role Reports currently for all records. Need to add the range selection and sort filters prior to running the report. 1

17.119 Reports User Role I want a Drivers with Restrictions Report. This pulls from the Restriction of the Driver Permit. The report should display the Driver name, Permit #, Restriction description, cpcn, status, restriction from field they enter in driver permit, pulls from restricted or not restricted flag setting. 1

17.120 Reports User Role At the end of all report to print the date and the time the report was run and a count of records. 1

17.121 Reports User Role A Permits Issues List. Create ability to to know how many permits are issued in a day. The headings should be Issue day, Permits count, need third column for applications count. ( will need a print screen to go with this.) 1

17.122 Reports User Role A report that shows how many applications each driver has on file. Headings on the report: Driver name, Permit #, application count, includes both active, inactive and denied General application or revision. If leave company before 10 days can do a revision of application instead of an initial application. Need a flag on the application to differentiate, fingerprints not required. Revision, expiration date does not change. only time expiration date changes is when a full background is done. Almost acts like sub-application or an amendment, Second button for add revision on driver application, lock the expiration date, able to change temp permit date should be locked as well. Add a revision date that isn't tied to anything, need to keep all info from original application, identify original vs revised. Keep the original info, but show revision data only, 1

17.123 Reports User Role All inputted permit, date received, date entered, permit number, cpcn. All permit numbers for a CPCN during a certain date range. 1

17.211 Reports User Role Queries, create own queries in data base. Carrier report, run for a period of time, batch report. a separate report printed for each carrier. 1

17.311 Reports User Role The ability to have an export on all reports to pdf, or excel, crystal reports if has a license would only work for 1 person. Wouldn't want in the drop down. 1

&16&G &"-,Bold"&16&A &"-,Bold"&16P2017-019 DPS PNP ORAS Tool

&9&F &"-,Bold"D R A F T &9Page &P of &N https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/

Enforcement Database

Enforcement Database

Req # Feature Role Requirement Version #

1 Combined database for NTA Administrator Role The ability add and delete users to set privileges. 1

2 Combined database for NTA Administrator Role Add/delete/update citations/fines/impounds for any carrier or driver.

3 Combined database for NTA Administrator Role Modify all records. 2

4 Combined database for NTA User Role Require enforcement officers to be able to login and find data on drivers and carriers 3

5 Combined database for NTA Administrator Role A web based program 1

6 PII Security Administrator Role The site to be in PII Compliance 1

7 PII Security Administrator Role The program must comply with state security policies and standards. 1

8 PII Security Requirements of State Security Policies/Procedures. https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/ 1

9 Record User Role Ability to add and or modify a new a citation and/or fine entry. 1

10 Record User Role Drop Down to determine type of record: Citation, Warning, Operational Inspection, Complaint and Impound.

11 Record Administrator Role Ability to configure certain fields to be Mandatory 1

12 Record User Role Date citation was issued field and have it be mandatory 1

13 Record User Role All date fields should have a calendar pop up to choose a date or manually enter date throughout the database as MM/DD/YYYY. 1

14 Record User Role Ability to have a history date log for a.) citations; b.) hearings; c.) citations. 1

15 Record Administrator Role History Log should for a.) citations; b.) hearings; c.) citations should only be able to be updated by an Administrator.

16 Record User Role List a Citation Number 1

17 Record User Role List the Investigator's Name 1

18 Record User Role Enter Respondent's Name 1

19 Record User Role Enter Respondent's Address 1

20 Record User Role Enter Respondent's Driver's License 1

21 Record User Role Enter Respondent's Date of Birth 1

22 Record User Role Enter Associated Carrier Information - CPCN Number which should automatically populate the name of the company.

23 Record User Role List field for reason of Citation: Drop Down of options: Written Complaint, Violation, Operational Investigation, Operational Inspection. 1

24 Record Administrator Role Administrator may only update the Reason for Citation Field. 1

25 Record User Role Provide a field that has the capability to list all of the violations - this will be a manual entry field. 1

26 Record User Role List a date field for when the investigative report is completed. 1

27 Record User Role Enter Authority Type: Bus, Limo, Mover, NEMT, Taxi, TNC, Tow, Autonomous 1

28 Record User Role Location dropdown field for where event occurred: Allegiant Stadium, Downtown LV, Lake Tahoe, Las Vegas Convention Center, Las Vegas Strip, Harry Reid Airport, Reno Airport, Respondents Address, Thomas & Mack, NTA Office, and list other. 1

29 Record User Role List Complainant Information: Name; Address; Phone Number; Email Address. 1

30 Record User Role Disposition Field: Dropdown field that has options of Carrier Respondent Fined; Citation Dismissed; Citation Voided; Citation Withdrawn; Customer Refunded Money; Customer/Public Satisfied; Duplicate Investigation; Fined, Impound Dismissed; No Fine Accessed; No Fine or Disqualification Accessed; No violations found, Not within NTA Jurisdiction; Other ; Warning Issued;

31 Record User Role MOT Notes: Open Typing of Notes 2

32 Record User Role Disposition Notes: Open Typing of Notes 1

33 Record User Role Schedule Agenda - Date field to be entered. 1

34 Record User Role List Settled - allow for a check box. 1

35 Record User Role List Settlement Date: Calendar date to be listed. 1

36 Record User Role Date of Agenda - Enter Date 1

37 Record User Role Fine Amount Field: List Dollar amount 1

38 Record User Role Abeyance Field: List dollar amount. 1

39 Record User Role Field when Abeyance expires - list date. 1

40 Record User Role Date Paid Field - list date 1

41 Record User Role Receipt Number field - open field. 1

42 Record User Role Remarks/Payment Planfield - open field 1

43 Record User Role Disposition Notes/Detail: Open field 1

44 Record User Role Date Closed: List the date 1

45 Record User Role CPCN Field: Open Field 2

46 Record User Role Principal Respondent Field: Open Field 1

47 Record User Role Associated Company Field: Open Field 1

48 Record User Role Complainant Field: Open Field 1

49 Record User Role Receipt Number 1

Example of Data Entry Form:

Search Function Options:

Carrier Database

Carrier Database

Req # Feature Role Requirement Version #

1 NTA Database Administrator Role The ability add and delete users to set privileges. 1

2 Carriers Administrator Role Add/delete/modify carriers.

3 Carriers User Role Modify all records. 2

4 Carriers User Role Be able to login and search data on carriers. 3

5 Carriers Administrator Role A web based program 1

6 PII Security Administrator Role The site to be in PII Compliant. 1

7 PII Security Administrator Role The program must comply with state security policies and standards. 1

8 PII Security Requirements of State Security Policies/Procedures. https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/ 1

9 Carriers User Role Ability to add/modify carrier data or information in all fields. 1

10 Certificates User Role Ability to enter certificate number, carrier name, dba, addresses, phone numbers, insurance information, contacts, fleet information, authority type, certificate activity, and status type.

11 Certificates Administrator Role Ability to configure certain fields to be Mandatory 1

12 Certificates User Role Ability to download pdf certificate document. 1

Certificates User Role Fields: Certificate number (drop down), certificate prefix (authority types), other restrictions (yes/no buttons), authority description (unlimited field), comments, fully regulated (yes/no button), vehicle restrictions (open field), scanned certificate (attachment), status dropdown (active, cancelled, other, temporary…