Attachment D - Management Application Spec FINAL 12 10 15.docx

ATTACHMENT D – MASS17 Management Application Functional Spec

RFR Attachment D MASS17 Management Application Functional Specifications Contents

Overview

The following sections describe functional specifications for the MASS17 Management Application Functional Specification. Bidders shall submit RFR Responses that generally address the functional specifications set forth below. (See generally, RFR Sections 3.2 and 6.0 et seq.) After Contract Award, the Contractor, working in cooperation with the Agencies, shall develop detailed design specifications based on these functional specifications.

The MASSS17 Management application shall be a web-based application used by the Agencies and Contractor to manage the following:

· Station Licensing

· Inspector Licensing

· Inspection Stickers

· Vehicle test exceptions and MAC referrals

· Workstation/VID Control and Reference files

· Motorcycle stickers

· Workstation messages

· Waivers/Extensions

· Inspector Training

· Registered Repair shops and technicians

· Covert Audits

The Management Application (“Application”) shall be a secure web-based application accessible from any computer with an internet connection. The Application shall require users to login in with a username and password. The password shall expire periodically, and the user shall have the ability to change the password at any time using the Application. The Application shall remain active as long as the user is logged in and the Application is open (i.e. does not time out.)

Because the Application will contain sensitive data (e.g. Station Automated Clearing House information) there shall be different levels of users for the Application. The highest level users shall have the ability to view and change all information, while the lowest level users may only be able to view selected information. Sensitive data will be restricted to very few Agency and contractor employees. The database will be built with complete audit capability and an audit trail. After Contract Award, user privileges shall be jointly defined and established between the Agencies and Contractor.

Home Page The home page shall display folders and sub-folders of the functions contained in the Application. The folders and sub-folders shall be displayed in a side bar that is constantly displayed throughout all functions of the Application. Users shall have the ability to expand and collapse folders.

Station Licensing Station licensing shall be represented by a folder called “STATIONS” in the side bar and shall contain the following sub-folders:

· Information

· License

· Inspectors

· Workstations

· Stickers

· History Selecting “STATIONS” from the side bar shall open up a search function with the following features:

· Stations shall be searchable by Station ID, Station name, Workstation ID, town, or Station manager name.

· The search function shall return all applicable data based on partial entries utilizing SQL “like” structure. Example: a Station ID entry of “5408” shall return Station PB005408.

· If a Workstation ID is selected, the software shall display the entire Station history (all Stations the Workstation has been assigned to), in chronological order.

· Once a Station is selected from the search results, the Application shall open the “Information” subfolder page

· Once a Station is selected, all subsequent pages displayed shall contain a header with the Station ID and Station name selected Information Display The Information page shall display the following:

· Station ID

· Station Name

· DBA Name

· Manager Name

· Federal Tax ID

· Nearest MAC

· RMV Region (1 – Boston, 2 North Shore, 3 – Central, 4 – South Shore, 5 – West)

· Location – address, town, state, ZIP, phone, fax, contact name for:

· Place of Business

· Mailing Address

· Billing address

· Geocodes for place of business

· Hours of Operation

· Displayed for each day of week

· Open, Close, Open, Close hours for each day

· 1st open and last close indicate business open and close hours

· Middle close and open indicate lunch break, if applicable Functions The information page shall contain the following functions:

· Edit - Allows user to edit Station information per user privileges

· Map - Opens Google Map based on Place of Business Geocodes License Display The License page shall display the following:

· License Status (active, inactive, or retired)

· License expiration date

· License last issued date

· Station License Class (A, B, C, D, E, F, M)

· 7D Station (check box)

· Lockout status (Clear, Locked)

· Licensed Expired (Y/N)

· License Suspended (Y/N)

· License Revoked (Y/N)

· Payment Default (Y/N)

· Cease & Desist (Y/N)

· Display box of Milestones Completed

· In the process of setting up a license, a Station must pass certain milestones before the license can be activated.

· This box shows which milestones have been completed.

Functions The License page shall contain the following functions:

· Change License status (active, inactive, retired)

· Change License class (A, B, C, D, E, F, M) via drop-down box

· Expire a License (set expiration date, allow comment)

· Suspend a License (set suspension start date, duration, allow comment)

· Revoke a License (set revocation date, allow comment)

· Cease and Desist Lockout (instantaneous, allow comment)

· Payment Default – Locks out a Station license when the Station is in payment default.

· The same function shall unlock a previously locked Station.

· License Payment - Updates the expiration date and creates a financial transaction

· Payment information (check, credit card, money order)

· Payment Date

· Check #

· Amount

· Expiration date

· Comments

· Application Payment - Allows the user to accept and begin the Station Application process. This creates a financial transaction of the payment

· Payment information (check, credit card, money order)

· Payment Date

· Check #

· Amount

· Comments

· Print Station License Inspectors Display The Inspector’s page shall display the following:

· Inspector ID

· Inspector Name The Inspector ID and Inspector name shall be a hyperlink that opens up the Inspector license functions described in Section 4.1 below.

Functions The Inspector’s page shall have the following functions:

· Add an Inspector to Station

· Inspector can be added by name or Inspector ID

· Delete an Inspector from Station

· Inspector can be deleted by highlighting Inspector ID or name and selecting “Delete” Workstations Display The Workstation page shall display the following:

· All Workstation IDs assigned to the Station.

· Workstation type (Light-duty, Heavy-duty) for each Workstation Selecting a Workstation ID shall display the following:

· Workstation ID

· Barcode scanner serial #

· OBD scan tool serial #

· Opacity meter serial #, if applicable

· Workstation software version #

· Stickers remaining

· Test Authorizations remaining

· Calibration expiration date

· For each device requiring calibration

· Display date in red if expired

· Workstation Lockout Status (Y/N)

· Workstation Lockout Reason

· Workstation Geo-fence status (on/off) and coordinates

· Google Map showing coordinates Functions The Workstations page shall have the following functions:

· Change Workstation type (Light-duty/Heavy-duty)

· View/Change Workstation Station menu password

· Activate/de-activate Workstation geo-fence

· Set Workstation geo-fence coordinates

· Workstation Lockout (Y/N)

· Select Reason from drop-down menu

· Allow Comment

· Inspection Bay camera set-up

· Allows user to specify which camera is used for video and which cameras are used for still images

· Live Stream Station Video

· Allows user to view and save live video footage from Station video camera

· Search Workstation history by entering Workstation ID

· Allows user to view all history of the Workstation, including all Station IDs and locations where the Workstation was assigned, and associated lockout history.

Stickers Display The Stickers page shall display the following:

· Current Year Unloaded Sticker books assigned to the Station

· Next sticker number for each Workstation

· Individual and books of stickers to be picked up by RMV (damaged, voided, or overstock) for the current calendar year and previous year

· 7D stickers assigned to Station, if applicable

· Next 7D sticker, if applicable Functions The Stickers page shall have the following functions:

· Sticker Lookup by Station

· User selects Sticker Expiration Year from drop down list to view the status (loaded/unloaded) of each sticker book assigned to the Station

· Note: 7D stickers do not have an expiration year

· Software displays a list of sticker books from the selected expiration year that have been assigned to the Station, including:

· Whether the book has been loaded or is unloaded and date/time and Inspector ID that loaded the stickers, if applicable

· A button called “Details” that opens up a new page to display the following:

· Date/time and Contractor personnel who received stickers from supplier

· Date/time, Contractor Personnel , and Station ID for stickers shipped to a Station or Motorist Assistance Center

· Shipping details such as Shipper, tracking number, etc.

· Date/time and Station personnel who received stickers from Shipper

· If sticker book has been loaded, the software shall display the Workstation ID, date/time, and Inspector ID that loaded the stickers

· A button called “explode book” that allows the User to view a list of all stickers in the book and the current status (unloaded or loaded). If a sticker is “loaded” it may have a status of available, issued, or gone.

· If the sticker is “unloaded” or “available”, no additional information shall be displayed

· If the sticker is “issued”, the software shall display, at minimum, the following inspection information:

· Date/time of inspection

· Station ID, Workstation ID, Inspector ID

· VIN, plate type, plate number

· Vehicle year, make model

· Overall inspection result, overall emissions result, overall safety result

· If the sticker is “Gone” it may have a status of Damaged, Voided, Stolen, or Overstock. The software shall display the following:

· Date/time the status became “gone”

· Status (damaged, voided, stolen, or overstock)

· User ID or Inspector ID

· If applicable, the VIN, plate, plate type, model year, make, and model the sticker was printed for

· Whether the sticker has been picked up by RMV (yes/no/unavailable), and RMV comments upon collection

· If the sticker is Stolen, the software shall display whether a Police report has been submitted by the Station and uploaded to the Application

· The user shall have the ability to upload an image of a Police Report to the Application for any stolen stickers

· The user shall have the option to print the report or download it as MS Word, MS Excel, or a pdf

· For stickers and books with multiple designations (e.g. assigned to a Station, unassigned, collected from a Station, then re-assigned to another Station or sent to a Motorist Assistance Center before being assigned and sent to a Station), the complete history of the sticker shall be displayed, not just the current status.

· Add Stickers – Allows user to assign stickers to a Station by entering the following:

· Sticker Book Start #

· Number of Books

· Expiration Year

· Sticker Type (Regular, 7D Green , 7D Orange)

· From Station ID (if transferring stickers already assigned to another Station)

· Comments Once the sticker books are added to the Station, the stickers become “available” for loading into the Workstation(s). Sticker books must be loaded by lowest sticker number first. Once sticker books become loaded, their status changes from “available” to “loaded”

· Void stickers – Allows user to void stickers assigned to Station

· Overstock – by book or individual sticker

· Used for end of year and Stations going out of business

· Damaged – by sticker number, to assist Station with printing problems

· Allows user to indicate if stickers picked up by RMV (yes/no/unavailable)

· Comments History Display The History page shall display all changes made by users within the STATIONS folder. The history shall contain the following:

· Date/Time of change

· User ID that performed the change

· Description of change

· Station license status following change

· Workstation Lockout status following change Functions The History page shall have the following functions:

· Print History

· User can select “ALL” or by Date Range

· Download History

· User can select “ALL” or by Date Range

· File format options

· MS Excel

· MS Word

· Adobe pdf

· View history by entering Workstation ID

· Allows user to view all history for the Workstation including Station IDs, locations, and lockout history Inspector Licensing Inspector licensing shall be represented by a folder called “INSPECTORS” in the side bar and shall contain the following sub-folders:

· License

· Assigned to

· Biometrics

· History Selecting “INSPECTORS” from the side bar shall open up a search function with the following features:

· Inspectors shall be searchable by Inspector Name or Inspector ID.

· The search function shall return all applicable data based on partial entries utilizing SQL “like” structure. Example: an Inspector Name entry of “Smith” shall return all Inspectors with the last name Smith.

· Once an Inspector is selected from the search results, the Application shall open the “License” subfolder page

· Once an Inspector is selected, all subsequent pages displayed shall contain a header with the Inspector ID and name selected License Display The Inspector License page shall display the following:

· Inspector name

· Inspector ID #

· Date License expires

· License Class (From ALARS)

· N = Non-commercial, C = Commercial, R = Restricted, 7 = 7D

· Status (Active, Inactive, Retired)

· State/QA Inspector (check box)

· Lockout Status (Clear, Locked)

· Lockout Reasons:

· ALARS Lock (Y/N)

· License Expired (Y/N)

· License Suspended (Y/N)

· License Revoked (Y/N)

· Cease & Desist (Y/N)

· Inspector Password Functions The Inspector License page shall have the following functions:

· Refresh from ALARS – Downloads most recent license information from ALARS

· Suspend (set suspension start date, duration, allow comment)

· Revoke (set revocation date, allow comment)

· Cease and Desist Lockout (instantaneous, allow comment)

· Change password – allows user to change password

· Suggest password – suggests random 5 digit password Assign to Display The Assign To page shall display the following:

· Station ID

· Station Name Functions The Assign To page shall have the following functions:

· Add Station – allows user to add Station by entering Station ID or name

· Delete – allows user to highlight Station ID/name and delete History Display The History page shall display ALL changes made ALL users within the INSPECTORS folder, including all Inspector lockouts and Station assignments. The history shall contain, at minimum, the following:

· Date/Time of change

· User ID that performed the change

· Inspector license status following change

· User comments Functions The History page shall have the following functions:

· Print History

· User can select “ALL” or by Date Range

· Download History

· User can select “ALL” or by Date Range

· File format options

· MS Excel

· MS Word

· Adobe pdf Stickers Functions The Stickers page shall have the following functions

· Sticker Lookup by Sticker Book

· Allows user to view the history for a book of stickers by entering the sticker book starting number

· The software shall display the following:

· Date/time and Contractor personnel who received stickers from supplier

· Date/time, User, and Station ID if book assigned to a Station

· Date/time and shipping details if book shipped to a Station

· Date/Time and Name of Station personnel that received the sticker book

· Date/Time, User, and Workstation ID if sticker book loaded into a Workstation

· Ability for user to “explode” sticker book once it has been “loaded” into the Workstation to view the status of each sticker as described in Section 3.5.2 above.

· For stickers with multiple designations (e.g. assigned to a Station, unassigned, collected from Station, then re-assigned to another Station), the complete history of the sticker shall be displayed, not just the current status.

· The user shall have the option to print the report or download it as MS Word, MS Excel, or a pdf

· Sticker Lookup by individual sticker number

· Allows the user to view the history for an individual sticker

· The software shall display the following:

· Date/time and Contractor personnel who received stickers from supplier

· Date/time, User, and Station ID if sticker assigned to a Station

· Date/time and shipping details if sticker shipped to a Station

· Date/Time and Name of Station personnel that received the sticker

· Date/Time, User, and Workstation ID if sticker loaded into a Workstation

· If loaded into a Workstation, the sticker status of available, issued, or gone

· If the sticker is “unloaded” or “available”, no further information shall be displayed

· If the sticker is “issued”, the software shall display, at minimum, the following inspection information:

· Unique inspection ID

· Date/time of inspection

· Station ID, Workstation ID, Inspector ID

· VIN, plate type, plate number

· Vehicle year, make model

· Overall inspection result, overall emissions result, overall safety result

· If the sticker is “Gone” it may have the status of Damaged, Voided, Stolen, or Overstock. The software shall display the following:

· Date/time the status became “gone”

· Status (damaged, voided, stolen, or overstock)

· User ID or Inspector ID

· If applicable, the VIN, plate, plate type, model year, make, and model the sticker was printed for

· Whether the sticker has been picked up by RMV (yes/no/unavailable), and RMV comments upon collection

· If the sticker is Stolen, the software shall display whether a Police report has been submitted by the Station and uploaded to the Application

· For stickers with multiple designations (e.g. assigned to a Station, unassigned, collected from a Station, then re-assigned to another Station), the complete history of the sticker shall be displayed, not just the current status.

· The user shall have the option to print the report or download it as MS Word, MS Excel, or a pdf RMV Payment Report Selecting this item opens up a report that allows the user to view a summary of payments made to RMV for the following:

· Motorcycle sticker sales –

· Motorcycle sticker shipping/handling fee

· Station License fee

· Station License application fee

· Station Address change Motorcycle sticker sales are entered into the Application by the user as described in Section 10 below. Station license and application payments are entered into the Application as described in Section 3 above.

The user may search by following parameters:

· Date range (start and end date with point and click calendar available)

· Search type (All, Station license, or Motorcycle stickers)

· Station ID Upon selecting search criteria, the Application shall display a report containing the following information for each payment made to RMV based on data entered by the user in Sections 3 and 10:

· Date/Time payment entered by user

· Payment Information (check #, shipping #)

· Station ID

· Payment amount

· Payment type (MC sticker purchase, MC sticker handling fee, Station license, Station application)

· Comments

· User ID

· Transaction Key (a unique identifier assigned to each transaction)

· The following total amounts for the transactions in the reports

· Address change total

· Application fee total

· Licensing fee total

· Certificate fee total

· Shipping fee total

· Grand fee total Users shall have the ability to sort by each of the fields above and print a report of the data. Select users with the proper privileges shall also have the ability to perform the following:

· Update transaction – Allows user to update the following about a selected transaction:

· Payment information

· Amount

· Payment type

· Reason for Update

· Reverse transaction - Allows user to remove a transaction and provide a reason.

Reprint Sticker Select users with the proper privileges shall have the ability to reprint an inspection sticker for RMV approved reasons. Upon selecting this item, the software shall display the following search box:

· VIN

· Sticker Number The software shall display the following for all inspections that match the search criteria entered by the user:

· VIN

· Make

· Model

· Date Inspected

· Sticker Number

· Plate Number

· Test Result To reprint the sticker, the user shall select one of the inspections displayed by the software and select “Print.” The user must load sticker stock into the printer connected to the Application. The reprinted sticker shall be identical to the original sticker, including all barcodes, except the reprint shall include an “R” next to the inspection date to indicate it is a reprint. The print out shall also include the following as a record of the reprint:

· sticker number barcode

· date of reprint

· user that performed the reprint Vehicles Selecting this item shall open The Vehicle Details sub-folder.

Vehicle Details The Vehicle Details page shall display the following search box:

· VIN

· Plate Number

· Plate Type Once either a VIN or Plate Number is entered the user may submit a search. The Application shall search VID inspection records and display the following for Vehicles that are returned by the search:

· VIN

· Plate Type

· Plate Number

· Model Year

· Make

· Model

· Date/Time of last inspection For searches where only the VIN was selected, only the most recent plate/plate type for the vehicle shall be returned. For searches by plate type and plate number, all vehicles meeting those criteria shall be returned with the most recent VIN/plate combination displayed first. The user may select a vehicle returned from the search to view the following vehicle details:

· VIN

· Plate Type

· Plate Number

· Section 5 Reg #

· Section 5 Suffix

· Section 5 decal

· Model Year

· Make

· Model Name

· Vehicle Type

· Fuel Type

· GVWR

· Number of Cylinders (##, R = rotary, E = electric)

· Displacement

· Body Type

· EPA Vehicle Class

· Test exception details, if applicable

· MAC referral details, if applicable Once a vehicle is selected, the user shall have the option of creating a “VIN exception” and/or flag the vehicle for a MAC Referral.

Create VIN The user shall have the ability to create a new vehicle if it is not already in the VID. This may be necessary for giving test exceptions for new vehicles that have not yet been tested. To create a VIN, the user shall be prompted to enter the VIN. The VID VIN Decoder shall decode the VIN, if possible, and display all decoded information. If the VIN cannot be decoded, the Application shall display the Model Year, Make, and Model from ALARS.

Test exceptions Test exceptions may be required to override the current VID test selection logic or QA processes for special cases. The software shall allow vehicles to be identified for a test exception by any of the following methods:

· Individual vehicles by VIN

· Groups of vehicles by VIN stem (e.g. 1GNDT13S*4)

· Groups of vehicles by Model year, Make, Model, Fuel type, # cylinders, and displacement Upon specifying the vehicles(s), the Application shall display the following data entry form:

· Emission Model Year – replaces model year in VID logic

· Optional

· Default = null

· Safety Test Type

· Options = (N) non-commercial, (C) commercial

· Default = null

· Emission Test Type

· Options: (1) safety only, (4) diesel opacity, (5) HD OBD, (6) HD NVOS, (8) OBD, (9) NVOS

· “Default = null

· QA exception?

· Options: (Y) Yes, (N) No

· Default = No

· Duration

· Options: (O) Once, (P) Permanent

· Default =(O) Once

· Comment

· Optional , up to 255 characters allowed Selecting “null” for the safety test type or emissions test type does not change the software’s test selection process. Typically, when creating a test exception for an emissions issue, the safety test type will be left null so that only the emission test selection is overridden; when creating a test exception for a safety issue, the emission test selection will typically be left null so that only the safety test selection is overridden.

When an emission model year is entered, its value shall be used in place of the vehicle model year in all software functions. Examples:

· Emissions test selection process,

· OBD readiness requirements,

· opacity cutpoint requirements,

· any other requirements based on the vehicle’s model year.

When the QA exception is set to (Y) Yes, the vehicle shall be exempt from any QA processes such as test interruption, OBD VIN QA check, and OBD Parameter QA check as described in RFR Attachment A, Section 3.6.1.1.7.9.

When the duration is set to “Once”, the test exception is to only be in effect for 1 test cycle. When the duration is set to “Permanent” is selected, the test exception shall remain in effect until it is removed.

Upon hitting “Save”, the test exception shall be immediately stored on the VID. The user shall also have the option to remove a test exception by selecting the option “Remove test exception.”

· QA exception – allows the Agencies to exempt particular vehicles from the QA checks described in RFR Attachment A, Section 3.6.1.1.7.9 and automatic MAC referrals based on test results described in RFR Attachment A, Section 3.6.1.1.14.2. For example, this may be necessary for a vehicle that has a known PCM swap where the stored OBD VIN does not match the vehicle VIN.

MAC Referral Upon selecting this item, the Application shall display the following data entry form:

· MAC Referral Reason

· Options: Kit Car, Targeted

· MAC Referral Comment

· Optional , up to 255 characters allowed Upon hitting “Save”, the MAC referral shall be immediately stored on the VID. The user shall also have the option to clear a MAC Flag selecting the option “Clear MAC Flag.”

Workstation/VID Control and Reference Files Users shall have the ability to modify Workstation/VID Control and Reference Files. Except where noted below, changes to these files shall produce a test file that is available for testing in a test environment, not the production environment.

Network Control File This file shall contain, at minimum, the following settings for controlling critical functions of the Program. Unless otherwise noted, changes made by users to the NETWORK CONTROL FILE in the Management Application shall create a updated file for testing before being implemented.

· Allow tests offline to ALARS (Y/N)

· change goes directly to production, not test environment

· Workstation GPS geo-fence check (on/off)

· change goes directly to production, not test environment

· OBD QA check test interruption (on/off)

· change goes directly to production, not test environment

· MAC referrals (on/off)

· change goes directly to production, not test environment

· Non-commercial test fee

· 7D test fee

· Test authorization fee

· Free retest period (days)

· Free 7D retest period (days)

· Start model year for Light-duty OBD

· Start model year for Medium-duty non-diesel OBD

· Start model year for Medium-duty diesel OBD

· Start model year for Heavy-duty non-diesel OBD

· Start model year for Heavy-duty diesel OBD

· Start model year for diesel opacity

· End model year for diesel opacity

· Non-diesel Readiness MAC referral – Minimum number of turnaways

· Non-diesel Readiness MAC referral – Minimum time period (hours)

· Diesel Readiness MAC referral – Minimum number of turnaways

· Diesel Readiness MAC referral – Minimum time period (hours)

· Diesel Readiness Miles Driven since code clearing

· Diesel Readiness Warm Ups since code clearing

· OBD QA check time limit for response (seconds)

· After hours OBD QA test interruption (bypass/fail)

· Printer/barcode check frequency (hours)

· OBD System Operational check frequency (hours)

· Diesel opacity check frequency (hours)

· Opacity Time to detect snap (seconds)

· Opacity rise trigger (%)

· Opacity measurement duration (seconds)

· Opacity bandwidth limit (%)

· RMV phone number

· Contractor phone number

· # of sticker reprints allowed

· Inspection Bay Camera Checks (on/off) OBD readiness exception file This file shall contain vehicles that are exempt from the normal readiness rules programmed into the inspection software. The software shall allow vehicles to be identified for a readiness exception by any of the following methods:

· Individual vehicles by VIN

· Groups of vehicles by VIN stem (e.g. 1GNDT13S*4)

· Groups of vehicles by Model year, Make, Model, Fuel type, # cylinders, and displacement For each exception, the user shall have the ability to specify whether the following monitors are included or not included in the software’s readiness determination and specify how many Not Ready monitors are allowed for the vehicle to pass readiness.

· Misfire monitor

· Fuel monitor

· Comprehensive component monitor

· Catalyst/NMHC Catalyst monitor

· Heated Catalyst/NOX After-treatment monitor

· Evaporative System Monitor

· A/C System monitor

· O2 Sensor/Exhaust Gas Sensor monitor

· O2 Sensor Heater/PM filter monitor

· EGR/VVT system monitor

· Number of monitors allowed Not Ready OBD exceptions file This file shall contain vehicles that are exempt from the normal OBD scan procedure programmed into the inspection software. The software shall allow vehicles to be identified for an OBD exception by any of the following methods:

· Individual vehicles by VIN

· Groups of vehicles by VIN stem (e.g. 1GNDT13S*4)

· Groups of vehicles by Model year, Make, Model, Fuel type, # cylinders, and displacement For each vehicle or groups of vehicles selected above the user shall have the ability, at minimum, to specify the following exceptions:

· OBD communication – do not attempt

· Software prompts Inspector to perform visual Key-On-Engine-Off (KOEO) and Key-On-Engine-Running (KOER) checks instead to determine overall OBD result.

· OBD Communication – attempt

· If fails, software prompts Inspector to perform KOEO and KOER checks instead to determine overall OBD result.

· RPM – bypass requirement that RPM is >=250 for OBD scan to proceed Diesel Opacity Cutpoints The VID shall use the following reference file to determine the correct opacity cutpoint based on the VEHICLE TYPE and MODEL YEAR. The file shall allow for additional rows up for expanding model years.

MAC Referral Matrix The software shall allow users to select individual vehicles or groups of vehicles to receive an automatic MAC referral for a targeted inspection if the OBD test results meet any of the defined rules. Vehicles to receive an automatic MAC referral may be selected by the following methods:

· VIN

· VIN stem – ALL or specific VIN stem

· Model Year – ALL or particular MODEL YEAR

· Make – ALL or particular MAKE

· Model Name – ALL or particular MODEL NAME

· Fuel Type – ALL or particular FUEL TYPE

· Number of Cylinders – ALL or particular CYLINDERS

· Displacement – ALL or particular DISPLACEMENT For the selected vehicles, the software shall allow users to define rules that will cause an automatic MAC referral based on OBD test results. The following is an example of a rule:

· VEHICLE = ALL: IF fuel type = “diesel” and Evaporative monitor = “Supported”, THEN Targeted MAC referral The Software shall also allow users to EXEMPT particular vehicles from rules. Example:

· VEHICLE = 2003 Dodge Durango 8 cyl 4.7L, IF Catalyst monitor = “Unsupported”, THEN No Targeted MAC referral Motorcycle Stickers The Motorcycle Stickers folder shall contain the following subfolders:

· Search/Sell/Rebate Motorcycle Stickers

· Motorcycle Sticker Management Search/Sell/Rebate Motorcycle Stickers This folder shall allow the user to search, sell, and rebate Motorcycle stickers.

Search Stickers This function allows the user to search stickers by sticker # and expiration year. The search shall return, at minimum, the following:

· Sticker Number

· Date/Time of last status change

· Expiration Year

· Station ID

· Status Sell Stickers This function allows the user to sell stickers to a Station. The Station shall be searchable by Station ID, Station name, town, or Station manager name. The search function shall return all applicable data based on partial entries utilizing SQL “like” structure. Example: a Station ID entry of “5408” shall return Station PB005408. The Station must be an active (not locked out) motorcycle Station.

Once a Station is selected, the software shall open a window that displays the following:

· Station ID

· Station Status (locked or clear)

· Station Name and Address To sell stickers to the Station, the user shall be required to fill out the following:

· Number of sticker books

· Sticker starting number

· Expiration Year

· Payment Method (check, money order)

· Sticker Check #

· Check amount

· Shipping check #

· Shipping Cost (default $8.50)

· Waive shipping fee (check if yes)

· Total Amount

· Comments Once the form is completed the user shall select a button called “Sell Stickers” to continue the transaction. The user shall also have the option to “Clear All” and begin again. Once the user clicks on “Sell Stickers” the software shall display a verification screen showing the number of sticker books, total cost, and Station ID for the sticker sale. The user must select “save” to complete the transaction or select “cancel.” Once “save” is selected the software shall save a record of the transaction on the Database and allow the user to print or download a pdf receipt of the transaction.

Rebate Stickers This function allows the user to rebate the Station for unused stickers. The Station is selected in the same manner as described in section 10.1.2. The user then must select an expiration year and then “Find stickers.” The software shall list all unused stickers that were bought by the Station. The software shall allow the user to select sticker numbers that are not present, which will not be included in the rebate calculation. The user shall then select “Rebate stickers” to continue the transaction. The software shall display a summary of the transaction, including the number of stickers rebated, number of stickers missing, the Station ID, and the total amount of the rebate. The user shall have the option to select “save” to complete the transaction or “cancel” to begin again. Once the user selects “save,” the software shall save a record of the transaction on the Database and allow the user to print or download a pdf receipt of the transaction. After Contract Award, the RMV Revenue Control group shall approve the Contractor’s design of the pdf so that it can be used to process reimbursements to the Stations.

Motorcycle Sticker Management This folder shall allow the user to add stickers to RMV inventory, assign stickers to a Station, change the status of a sticker and void stickers from RMV inventory. Only higher level users shall be allowed to access this menu.

Add stickers to RMV inventory This function allows the user to add up to 99 books of stickers to RMV inventory at a time. The user shall be required to enter the number of books, the sticker starting number and the expiration year. Once the user selects “Add sticker book(s)” the software shall display a summary of stickers added to inventory and allow the user to “save” to complete the “transaction” or “cancel.”

Assign stickers to a Station This function is the same as selling stickers (section 10.1.2) except that no financial transaction takes place. This function would be used if a Station needed to replace lost stickers.

Change sticker status This function allows the user to select a sticker number and manually change the status to any of the following from a drop-down menu: Available, Damaged, On Hold, Inventory, Lost, Missing, Refunded, Stolen, Void, Expired. Once a sticker number is selected, the software shall display the following: sticker number, sticker status, sticker year, and Station number. Once the new status is selected, the user must select “Change status” to complete the transaction or “clear all” to begin again.

Void stickers This function allows the user to void a sticker by entering a sticker number or starting and ending sticker number and an expiration year. There may be restrictions in place that prevent a user from voiding a sticker or range of stickers. The user shall have the option to “force” the void, despite any restrictions.

Workstation Messages The Workstation Messages folder shall contain the following subfolders:

· View

· Create

· Send View The View subfolder shall allow users to view all sent Workstation messages. All Workstation messages and tracking by Inspector and Station shall be stored on the Database, not on the Workstation computer. There are two types of Workstation messages used in the Program: Contractor generated, and Agency generated. The user shall have the option of searching for Workstation messages by the following filters:

· Message Date/Time (user enters date range)

· Message Type (ALL, Contractor, or Agency)

· Sent to (ALL, RMV Region, MAC Region, Station ID, or Inspector ID) The search shall return the following:

· Message Date/Time (sorted reverse chronologically)

· Message Type (Contractor/Agency)

· Created by (User name)

· Message Title (hyperlink) Clicking on the Message Title Hyperlink shall open a pdf of the Message. Users shall have the ability of printing the message or downloading as a pdf or MS Word document.

Create The Create subfolder shall have the following functions:

· View Draft Messages

· Create New Message View Draft Message The View Draft Messages subfolder shall contain a search feature that is identical to the search described in section 11.1 except only contains draft messages. Users shall be able to view ALL draft messages, not just those created by the user. Once a particular message is selected to view, the user shall have the ability to edit and save changes to the draft.

Create New Message The Create New Message subfolder shall allow users to create new Workstation messages. The user shall be required to select whether it is a Contractor or Agency message. In the body of the message, users shall have the ability to type in a message or cut and paste from another application. The user shall have the ability to:

· insert images into the message body;

· change font size and font type and to bold, underline, and italicize text;

· save the message as a draft; and

· view the message as would appear on the Workstation screen.

Send The send subfolder shall allow users to send the message to the following groups:

· All Stations

· Public Stations or Fleet Stations

· Stations by RMV region or MAC region

· Individual or groups of Inspection Stations

· Individual or groups of Inspectors

· Individual or groups of Repair Stations

· Individual or groups of repair technicians A copy of the sent message shall be saved in the user’s mailbox.

Waiver/Hardship Extension Management The Application shall manage the waiver/hardship extension authorization process in accordance with the following requirements.

Waiver Requirements A waiver may be authorized for a vehicle if it meets all of the following criteria:

· a minimum dollar amount has been spent on emissions repairs related to the reason for the emissions test failure (excluding repair costs for tampering, readiness, or failure of the OBD system to communicate);

· For 2015 the waiver cost thresholds are: $820 for a vehicle five model years old or newer, $720 for a vehicle six to ten model years old, and $620 for a vehicle more than ten model years old

· Waiver thresholds are adjusted every year using the Consumer Price Index per EPA guidance

· the repairs were performed following the emissions test failure;

· the repairs were performed by a registered emissions repair technician;

· the vehicle has no DTCs for disqualifying conditions as determined by the Agencies (e.g., catalytic converter efficiency, misfire);

· the catalytic converter monitor is Ready/Completed if the vehicle initially failed for catalytic converter efficiency;

· the vehicle has passed the safety test;

· the vehicle has no obvious safety defects; and

· repairs have been verified, to the extent practicable.

A vehicle may receive successive repair waivers, or may receive a repair waiver after a change of ownership or an initial registration, (e.g. just moved to Massachusetts.)

Hardship Extension Requirements A hardship extension may be authorized for vehicles that DO NOT meet the requirements for a waiver but meet the following criteria:

· if motorist obtained a repair estimate from a registered repairer indicating that the cost to repair each remaining DTC exceeds 1.5 times the waiver cost threshold – it is not necessary to have attempted repairs; and

· if there is any DTC present that does not meet the 1.5x threshold, it must be repaired prior to qualifying for an extension (for example, if there is an oxygen sensor code and a transmission code, then the oxygen sensor code must be repaired before the vehicle may receive an extension – NOTE and disclaimer: this is meant to be a simple example – if a major vehicle problem prevents the successful repair of what would normally be a less costly repair, then this may be taken into consideration when evaluating DTCs for an extension).

A vehicle that receives a hardship extension must pass its next emissions test cycle, and may not receive a repair waiver or another hardship extension in lieu of passing. Therefore, hardship extension history is a disqualifying factor for a repair waiver or a hardship extension.

Users and Processes The Application will be used by the Contractor to pre-screen vehicles, schedule appointments at MACs, and authorize waivers/extensions. The Application may be used by the Agencies’ staff to authorize waivers/extensions and verify waivers/extension authorized by the MACs.

Once an appointment is scheduled, the following occurs:

· The motorist visits a MAC for further validation of their repair information;

· The MAC technician inspects the vehicle. The inspection shall include verifying vehicle information with ALARS, checking for obvious safety defects, and validation of receipts of repairs performed by the registered repair technicians.

· The MAC technician enters results from the inspection into the Application.

· Using the requirements listed in section 12.1, the Application will automatically determine if the motorist qualifies for a repair waiver.

· If not, the Application will prompt for additional information and check if the motorist qualifies for a hardship extension using the requirements listed in section 12.2.

· Once all information is entered and validated, the Application shall generate a waiver/extension authorization or a waiver/extension denial printed report.

Inspector Training Management Inspectors may receive up to 4 different types of training: Non-commercial safety and emissions, Commercial safety and emissions, 7D, and motorcycle safety. Details regarding Inspector training are contained in RFR section 6.7. The application shall include, at minimum, the following components:

· Ability to manage students and their training status, including

· Creating student profile (name, Inspector ID, and contact information)

· Ability to search students

· Tracking training received and training expiration date(s)

· Scheduling students for training

· Tracking test results

· Ability to manage training classes, including

· Creating, updating or canceling a class with minimum and maximum number of students

· Creating and updating an Instructor

· Creating and updating a class location

· Ability to manage exams, including

· Creating and updating exam questions

· Creating and updating exams

· Tracking exam results

· Ability to manage training fees and financial data, including

· Maintaining training fees

· Track fee payments and payment details Up to date Inspector training information is critical to the Program. Inspector information, training dates, and training results from the Application shall be uploaded to ALARS at least 4 times daily.

Registered Repair Shop/Technician Management To manage registered repair shops, technicians, Vehicle repair data, and repair shop ratings, the Application shall include, at minimum, the following components:

· An application for licensing registered repair shops and repairers, including the following:

· On-line application for existing and new registered repair shops and technicians to apply for the new Program

· Ability for repair shops and technicians to select all types of vehicles or specialize in specific vehicle makes (e.g. Ford) or fuels (e.g. diesel)

· VIR will only show repair shops relevant to the make/fuel of the vehicle that failed

· Ability to establish the geographic location of the repair shop (using geocodes) so that the 10 nearest repair shops to an Inspection Station can be determined and printed on the VIR

· Ability for repair shops to submit a slogan (100 characters maximum) that will appear along with their business name, address, and contact information on VIRs

· Ability for users to activate and deactivate repair shops. Shops must have at least 1 registered repair technician to be active.

· Ability to assign technicians to repair shops.

· Ability to track training and certifications for technicians. Technicians may be deactivated if certifications or training expire.

· Ability to upload images of repair shop and technician application forms and technician certification certificates (e.g. ASE L1)

· An application for registered repair shops and repairers to enter OBD repair data for particular vehicles, including the following:

· A secure login process using repair shop ID, technician ID, and PIN.

· Ability to search for a vehicle by license plate or VIN and view a chronological list of inspections for the vehicle

· Ability to view and choose a particular inspection for the vehicle that is relevant to the repairs performed (usually the most recent inspection)

· Ability to enter specific repair data including, at minimum, the following:

· Repair Date, including calendar feature to select the date without typing

· The condition of the vehicle prior to repairs

· MIL bulb/circuit failure (Y/N) and up to 10 DTCs

· DLC failure (Y/N)

· Communication failure (Y/N)

· The status of each non-continuous monitor (Ready, Not Ready, Unsupported)

· Repair Notes (up to 2,000 characters)

· Whether the motorist declined one or more of the repairer’s recommendations (Y/N)

· Ability to save or submit entered data

· Ability to print blank repair entry forms

· An application for determining repair shop ratings including the following:

· A methodology for calculating the Emission Repair Success Rating (ERSR)

· ERSRs shall be updated quarterly based on the previous 6 months repair data

· If the repair data entered is associated with a passing retest then it shall be counted as a successful repair

· If the repair data entered is associated with a failing retest or Not Ready turnaway then it shall be counted as an unsuccessful repair

· the repair success rate shall be calculated as the ratio of successful repairs to repairs attempted

· the repair success rate shall be translated into a 5 star system based on the following breakdown:

· 5 stars = 90 – 100% retests passed

· 4 stars = 70 – 89% retests passed

· 3 stars = 50 – 69% retests passed

· 2 stars = 25 – 49% retests passed

· 1 star = 1 – 24% retests passed

· N/A = no repairs entered

· The current ERSR, total repairs entered, and previous quarter ERSR shall be printed on the VIR next to the repair shop information Covert Auditing Management To manage the covert auditing process, the Application shall include, at minimum, the following components:

· Covert Vehicle Management, including:

· Covert vehicle masking in the Database to ensure the Workstation requires the intended test type and to prevent Inspection Stations, and others, from seeing the real test history of covert vehicle;

· Covert Vehicle masking on the Program website to ensure that the Inspection Stations and members of the public cannot see the real test history of covert Vehicles;

· Covert Vehicle set ups including implanting, and documenting the defects that result in Inspection failures;

· Covert Vehicle tracking, including Vehicle assignment to specific auditors and for specific audits; and

· Preparing legitimate vehicle information packets and fictitious registrations.

· Ability to conduct covert audits and enter covert data, including:

· View camera data from any inspection, with the ability to speed up video footage;

· For vehicle audits, readily compare inspection data from the vehicle set-up inspection, pre-audit inspection, post-audit inspection and the audit…