Amended Attachment A - MASS17 VID-WS Functional Spec_3.8.16.docx

RFR Amended Attachment A – MASS17 Workstation/Database Functional Specs

RFR Amended Attachment A: MASS17 Workstation/Database Functional Specifications

Overview The following sections describe functional specifications for the Workstation hardware and vehicle inspection software. 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.

Workstation Hardware Specifications

Workstation Environment (See RFR Sections 3.2.1.3 and 6.3) The Workstation shall be durable and designed to operate in an automotive shop environment. The Workstation shall meet the following specifications:

· Power Requirements - The Workstation shall operate on 115 VAC ± 12 VAC and 60Hz. The Workstation shall be capable of being powered by a generator or power inverter. Variations in line voltage shall not impact Workstation accuracy more than 1/3 of any accuracy requirements.

· Temperate Range - The Workstation shall operate accurately in ambient air temperatures within 35 and 120 degrees Fahrenheit. The Workstation shall have adequate air flow to prevent overheating.

· Humidity range - The Workstation shall operate accurately within 0 and 95% relative humidity, non-condensing.

· Vibration and Shock Protection - The Workstation shall be designed to withstand vibrations and shocks typical of an automotive shop environment, including dropping of hand-held components on hard surfaces.

· Electromagnetic Interference - The Workstation shall operate accurately in the presence of electromagnetic signals found in an automotive shop environment.

Workstation Equipment The Contractor shall provide the following two types of Workstations:

Light-duty Workstation:

The Light-duty Workstation shall be designed to perform ALL safety inspection types (non-commercial, commercial, and 7D) and OBD testing of light and medium-duty On-board Diagnostics (OBD) vehicles up to 14,000 lbs. Gross Vehicle Weight Rating (GVWR). The Light-duty Workstation shall include the following equipment:

· Workstation cabinet;

· Computer;

· Barcode scanner;

· OBD scan tool and cables for light and medium-duty vehicles;

· Printer(s) ; and

· Cameras.

Heavy-Duty Workstation:

The Heavy-duty Workstation shall be designed to perform ALL safety inspection types (non-commercial, commercial, and 7D) and emission test types (OBD and opacity.) The Heavy-duty Workstation shall include the same equipment required for the Light-duty Workstation plus the following equipment:

· Diesel Opacity Meter;

· OBD cables for heavy-duty vehicles;

· Signature Pad for commercial safety inspections; and

· GPS receiver.

Workstation Cabinet All MASS17 Workstations shall include a Workstation cabinet to house and secure the inspection equipment and supplies. The Workstation cabinet shall be stable, durable, and use materials and finishes that prevent corrosion and withstand an automotive shop environment. The cabinet shall have adequate storage for all test equipment, accessories and supplies. The cabinet shall meet the following minimum specifications:

· Top surface no higher than 4 feet from the ground to support the monitor and other devices;

· Retractable tray(s) to store the keyboard and mouse;

· Tray, holster, or other device to store and easily access the barcode scanner. The barcode scanner shall not be supported by its cable only;

· Means to store and easily access the OBD scan tool and cables, hand-held camera, opacity meter, “Shepherd’s” hook, and flexible probe, if equipped;

· Secured means to store the PC, sticker printer, and books of unused stickers with locking mechanism to prevent unauthorized access. The secured area shall be large enough to store a minimum of 1000 unused stickers. A minimum of 2 keys shall be provided for the locking mechanism;

· Rear hinged door with locking mechanism to allow access to the rear of all equipment housed in the Workstation cabinet. The locking mechanism shall use the same key as above;

· Mounted power strip with Ethernet jack and surge protection, adequate outlets for all standard and optional equipment, and minimum 12 foot UL-approved power cord;

· Workstation ID tag prominently displayed on the front of the cabinet containing a barcode and plain text indication of the Workstation ID number. The Workstation ID number shall remain constant for the life of the workstation and transfer with the workstation;

· 4 rubber wheels having a minimum diameter of 4 inches and a locking mechanism to prevent rolling; and

· 120 VAC powered devices shall not be located less than 18 inches from the ground per National Electric Code.

As part of the RFR Technical Response, Bidders shall submit drawings of their proposed Workstation cabinet design, including dimensions, the locations of all Workstation equipment, security features, material/finish specifications, and any other relevant information. (See RFR Sections 3.2.1.3 and 6.3).

Workstation Computer The Workstation computer shall consist of a desktop style computer with separate processor, monitor, keyboard, and mouse and shall meet the following minimum requirements:

· Energy use – the computer shall meet the latest Energy Star guidelines;

· Processor – the processor shall be IBM PC-compatible and have a processing speed of 3 GHz or faster;

· RAM – the computer shall contain a minimum of 4MB of user-available RAM;

· Hard Drives – the Workstation computer shall include 2 internal hard drives: 1) a solid-state hard drive (SSD) with a minimum of 128 GB storage to be used for the operating system and any inspection software and associated files and 2) a SATA drive with minimum of 1TB storage to be used for storing video files from inspections;

· CD\DVD drive- the computer shall contain a CD/DVD ROM drive with a minimum 32x transfer speed;

· Keyboard – the keyboard shall be a fully sized MS Windows style keyboard with minimum 104 keys. The keyboard shall connect to the computer via a minimum 6 feet long USB cable. The keyboard shall include a protective cover to prevent the entry of debris during use.

· Mouse – The mouse shall use optical or laser technology and connect to the computer via a minimum 6 feet long USB cable;

· Monitor – the computer shall include a color LED monitor that meets or exceeds the latest Energy Star requirements and is EPEAT and TCO certified. The monitor shall meet the following specifications:

· minimum 22 inch display area (measured diagonally),

· HD with 1920 x 1080 resolution, and

· height adjustable.

The Bidder shall propose a method for securing the monitor to the Workstation cabinet to prevent damage from tipping over;

· I/O ports – the computer shall contain sufficient I/O ports to accommodate all workstation standard and optional devices. The computer shall contain a minimum of 2 additional unused USB ports. If a USB hub is required to meet this requirement, the Bidder shall propose the make, model, specifications, and image of the USB hub;

· Ethernet port – the computer shall contain an Ethernet port that supports 10 Mbps, 100 Mbps, and 1,000 Mbps network speeds for a wired internet connection;

· Wireless WIFI card – the computer shall contain a IEEE 802.11ac compliant WIFI card with minimum 500 Mbps data transfer rate. The card shall be permanently mounted inside the computer (e.g. PCI express slot.);

· Headset – the headset shall contain headphones and a microphone for video conferencing with the Help Desk. The headphones shall be designed to block out external noise inherent in an automotive shop environment. The headset shall include a minimum 6 foot cord and shall connect to the PC through the 3.5mm headphone and microphone jacks, located on the front of the computer; and

· Remote Control Device – the computer shall include a remote control device using RF technology to advance screens during the inspection without using the keyboard. The device shall be a minimum of 2 inches wide by 4 inches long for ease of handling. The device shall, at minimum, have clearly marked keys for [ENTER], Yes, No, Up arrow, and Down arrow. The device shall transmit successfully through automotive windshield and window glass a minimum of 50 feet.

Barcode Scanner Every Workstation shall be equipped with bar code scanner. The bar code scanner shall be used to read the following program barcodes:

· Vehicle Identification Number (VIN) bar code plate;

· 1D MASS08 inspection sticker number barcode;

· 2D MASS08 inspection sticker barcode containing inspection information;

· The 2D barcode printed on the Vehicle Inspection Report (VIR), ensuring the VIR printed legibly;

· The 1D and 2D barcodes generated for the daily bar code reader calibration check;

· The Inspector License 2D barcode;

· The QA/Staff License 1D barcode; and

· QR barcodes – for possible future use.

The bar code scanner shall utilize area-imager technology and be capable of reading:

· Both code 39 and 128 symbologies and all necessary interface software and hardware designed to read labels meeting SAE specifications J1877 and J1892 is required on all Workstations;

· Both 1D and PDF417 technology codes. The barcode scanner shall be able to auto-discriminate between the symbologies;

· AAMVA 2000 and AAMVA 2005 2D barcodes on the Inspector ID;

· A VIN barcode through the vehicle windshield;

· A barcode having a maximum length of 7¼" (seven and one quarter inches); and

· Data Matrix barcodes used on some new vehicle VIN plates.

The Workstation shall be equipped with a standard port configuration and standard connector for the bar code scanner to allow for simple installation and replacement. The supplied bar code scanner shall come with a 25 foot long self coiling cord. Manufacturers shall be expected to include any software necessary to utilize the data gathered from labels.

A wireless version of the barcode scanner shall be available that meets all of the above specifications and, at minimum, the following:

· Minimum 30 feet range of transmission;

· Backup power option if the battery is not charged or defective; and

· Method for docking/locating the barcode scanner to prevent loss (e.g. leaving in or on a vehicle following inspection).

OBD Scan Tool All Workstations shall include one OBD scan tool designed to scan the following Light, Medium, and Heavy-Duty OBD-equipped vehicles:

· Model Year 1996 and newer non-diesel Light-duty vehicles <=8,500 lbs. GVWR;

· Model Year 1997 and newer diesel Light-Duty vehicles <=8,500 lbs. GVWR;

· Model Year 2007 and newer diesel Medium-duty vehicles >8,500 lbs. and <=14,000 lbs. GVWR;

· Model Year 2008 and newer non-diesel Medium-duty vehicles >8,500 lbs. and <=14,000 lbs. GVWR; and

· Model Year 2014 and newer Heavy-duty vehicles >14,000 lbs. GVWR.

NOTE TO BIDDERS: The Contractor is responsible for ensuring that the OBD scan tool is able to communicate successfully with all new model year OBD equipped vehicles throughout the full term of the Contract, including all Contract extension periods.

The Contractor shall provide State of California Bureau of Automotive Repair (BAR) certified Data Acquisition Device (DAD) hardware for the Massachusetts OBD scan tool. The DAD hardware shall be required to maintain certification according to the recertification schedule outlined in the DAD specification.

All Workstations (Light-duty and Heavy-duty) shall include a 16 pin SAE J1962 compliant cable to connect the OBD scan tool to Light and Medium-duty vehicles. Heavy-duty Workstations shall also include a SAE J1939 compliant 9 pin Deutsch adaptor or cable to connect to Heavy-duty vehicles. Each Workstation shall include 1 replacement cable for each cable required The OBD scan tool shall meet the following connectivity rates:

· 99.9% successful communication for Model Year 1996 and newer non-diesel Light-duty vehicles <=8,500 lbs. GVWR

· 99.9% successful communication for Model Year 1997 and newer diesel Light-Duty vehicles <=8,500 lbs. GVWR

· 99.9% successful communication for Model Year 2007 and newer diesel Medium-duty vehicles >8,500 lbs. and <=14,000 lbs. GVWR

· 99.9% successful communication for Model Year 2008 and newer non-diesel Medium-duty vehicles >8,500 lbs. and <=14,000 lbs. GVWR

· The connectivity rate for Model Year 2014 and newer heavy-duty vehicles >14,000 lbs. GVWR shall be established jointly by the Agencies and Contractor following development of the heavy-duty OBD test procedure The connectivity rate shall be calculated according to the following:

· Successful communication is defined as having retrieved all of the OBD data elements necessary to make a pass/fail decision for the OBD inspection.

· Calculations shall be on a per vehicle basis for vehicles receiving a regular OBD test (New Vehicle OBD scans shall be excluded)

· Calculations shall be based on a three month rolling average to allow for vehicles that are repaired and successfully communicate upon retest to not be counted as having failed communication.

A wireless version of the OBD scan tool shall be available that meets all of the above specifications and, at minimum, the following:

· Minimum 30 feet range of transmission;

· Backup power option if battery is not charged or defective; and

· Method for docking/locating to prevent tool loss (e.g. leaving tool in vehicle following inspection).

The OBD scan tool shall collect log data from all OBD scans. All log data files shall be transmitted to the VID and stored temporarily on the workstation hard drive. The log file shall have a unique identifier and date/time stamp to link it to the OBD inspection or function performed. After Contract Award, the Contractor, in cooperation with the Agencies, shall finalize details for the OBD scan tool logs.

Diesel Opacity Meter The Heavy-duty Workstation shall be equipped with the DieselTune DX-270 opacity meter or its replacement. Inspection stations that already own a DieselTune DX-270 opacity meter in the current inspection program shall have the option to continue using their meter with the Workstation(s) the Stations will purchase from the Contractor. The meter shall be equipped with a minimum 15 meter cable from the Workstation. The meter shall be equipped with 2 styles of probes: a flexible clamp-on probe for horizontal tailpipes and a solid probe with “Shepherd’s” hook for vertical tailpipes.

Printer(s) The Bidder shall propose a solution for printing the VIR and sticker, assuring that the correct sticker stock number was used and that all documents can be printed legibly. The proposed printer(s) and related software shall have the ability to self-report problems such as paper jams, no paper, low toner, photoconductor problems, etc, and display messages on the workstation screen to alert the user. The printer(s) and software shall have the means to track pages printed and estimate the remaining life of the toner, photoconductor, and other critical components.

Cameras Each Workstation shall be equipped with a total of 5 cameras used to capture still images and video during an inspection. All images and video files shall be automatically assigned a unique identifier that is associated with the inspection.

PC Monitor Mounted Camera Each Workstation shall be equipped with a color camera that mounts on the PC monitor to be used for the following functions:

· Capture still image of the inspector during login; and

· Video conferencing/live chat with the Help Desk.

The Bidder shall propose specifications for the PC monitor mounted camera.

Hand-held Camera Each Workstation shall be equipped with a hand-held camera to be used for the following functions:

· Capture the image of vehicle VIN plate;

· Capture the image of Vehicle license plates, front and rear;

· Capture the image of odometer reading; and

· Capture up to 5 additional images at the inspector’s discretion to document safety failures, tampering, and other inspection conditions of interest.

The hand-held camera shall be water resistant and ruggedized for an automotive shop environment. The hand-held camera shall automatically charge and upload images from the inspection when the camera is connected to the Workstation. The connection from the camera to the Workstation for charging and transmitting of images shall be rugged and designed to withstand a duty cycle of frequent connections and disconnections. The Bidder shall propose specifications for the hand-held camera and describe how it will meet the above requirements.

Inspection Bay Cameras As part of the Contract, the Contractor will be required to install 3 video cameras on the walls and/or ceiling of each inspection bay to capture video footage and images from several angles of the Vehicle during the Inspection. Each camera must be configurable in the MASS17 Management Application (see RFR Attachment D) to select whether the camera captures still images or video footage during the Inspection. Also, the Agencies must have the ability through the MASS17 Management Application to view and record live streaming video during any Inspection from any inspection bay camera.

The 3 inspection bay cameras must meet the following minimum requirements: 1) the cameras shall capture color images and video; 2) the cameras shall have a minimum resolution of 1280 x 720; and 3) the cameras shall have a minimum frame rate of 5 frames per second.

As part of the RFR Technical Response, the Bidder must propose specifications for the inspection bay cameras that address the requirements of this Section 2.2.7.3.

Signature Pad Heavy-duty Workstations must include a signature pad for Inspectors to sign the Commercial safety Inspection VIR so that the signature becomes part of the electronic VIR document. As part of the RFR Technical Response, the Bidder must propose specifications that address this requirement.

GPS device Inspection stations shall be required to have a GPS device connected to their Workstation during all Inspections. GPS coordinates of the Workstation shall be recorded at the start of each Inspection. During the term of the Contract, the Contractor and Agencies must have the ability using the MASS17 Management Application (see Attachment D), to establish a “geo-fence” for each Workstation, a boundary outside which the Workstation shall be locked out from performing Inspections. As part of the Contract responsibilities, the Contractor shall install and test the GPS devices on all non-mobile workstations to ensure GPS coordinates can be reliably obtained.

As part of the RFR Technical Response, the Bidder must propose specifications for the GPS device that address the requirements of this Section 2.2.9.

Workstation/VID Software Specifications Overview This section describes the functional specifications for the Workstation/VID software. As part of the RFR Technical Response, the Bidder must propose specifications that address the requirements of this Section 3 (See RFR Sections 3.2.1.3 and 6.3).

Software Version Each version of software shall have a unique version number. The first 2 digits shall indicate the year the software was developed. The second set of 2 digits shall indicate the release within the specific year starting with 01. The third set of 2 digits shall indicate the version within the release that was created, starting with 01. An example software version would be 170114, indicating it was developed in 2017, it was the first release for 2017, and it was version 14 of that software release.

Start up When the Workstation computer is turned on, it shall start the MASS17 software program only and not allow operation of any other programs or access to operating system functions unless a daily Field Service Representative (FSR) security code is entered. The first screen displayed following start up shall be the Status Screen described in section 3.5.1 below. Upon closing the status screen following start-up, the software shall display the main menu described in section 3.6 below.

Header/footer All screens displayed by the Workstation shall have, at a minimum, the following information in the header or footer:

· Date/Time, format MM/DD/YYYYY HH:MM:SS AM/PM, updated every second;

· Station ID;

· Workstation ID;

· Database software version; and

· Workstation software version.

Toolbar The software shall display a toolbar that is accessible at all times and contains the following shortcuts:

· Status Screen;

· Data File Refresh;

· View Messages;

· View/Reprint VIR;

· Contact Helpdesk; and

· Inspection and Maintenance (IM) Program Regulations.

Status Screen A Workstation status screen shall be displayed upon starting the MASS17 program and be available from the toolbar. The status screen shall contain, at minimum, the following information:

· Station DBA Name;

· Operating System Version;

· Workstation Software Version;

· VID Software Version;

· Current GPS coordinates (mobile Workstations only);

· Test Authorizations Remaining (Bold red if 10 or less);

· Regular Stickers Loaded (Bold red if 10 or less);

· Next Regular Sticker Number;

· 7D Green Stickers in Inventory (if applicable);

· Next 7D Green Sticker Number (if applicable);

· 7D Orange Stickers in Inventory (if applicable);

· Next 7D Orange Sticker Number (if applicable);

· Safety Inspection Status; including

· Available (green) or Unavailable (red);

· OBD Inspection Status, including

· Available (green) or Unavailable (red);

· Diesel Opacity Inspection Status; including

· Available (green), Unavailable (red) or N/A (black);

· Printer/Barcode Calibration Expiration Date; including

· Date/Time green if not expired, red if expired;

· OBD Calibration Check Expiration Date; including

· Date/Time green if not expired, red if expired;

· Diesel Opacity Calibration Check Date (if applicable)

· Date/Time green if not expired, red if expired

· Lockout Status – Unlocked (green) or Locked (red); including

· Station License Lockout;

· Software Version Lockout;

· Sticker Inventory Lockout;

· Sticker Not Assigned Lockout;

· Test Authorization Lockout; and

· Unread Messages Lockout; and

· Internet Connection Status.

Data File Refresh Upon selecting this item, the Workstation shall connect to the Database to update any files on the Workstation. The software shall display whether the data file refresh was successful or not. If not, the software shall display the reason for the unsuccessful attempt.

Bidder should propose the methodology by which unsuccessful attempts are resolved.

Bidder should also propose the deletion mechanism and frequency, from the workstation, of files which are successfully uploaded. Bidder should consider the workstation hard drive file size to determine how often file deletions should occur, to balance the need for retention of files should an upload not be determined successful.

View Messages See section 3.6.5 below.

View/Reprint VIR This function shall allow Inspectors to view and reprint the VIR from any regular inspection or 7D inspection performed in the Program. The Inspector shall login prior to viewing or reprinting VIRs. The software shall prompt the Inspector to enter the VIN using any of the following options:

· keyboard entry;

· Scanning the Vehicle’s previous Inspection sticker; or

· Scanning the Vehicle’s VIN plate.

The Inspector shall also have the option of entering a date range for inspections performed at the Station.

The software shall return a list of all inspections performed on the vehicle arranged in chronological order. The list shall contain all of the following test information:

· VIN;

· Plate number;

· Model Year;

· Make;

· Model;

· Inspection date/time;

· Overall inspection result;

· Overall emissions result; and

· Overall safety result.

The software shall allow the Inspector to select a VIR to be viewed. The VIR displayed shall be identical to the VIR printed during the inspection with the following exception: 1) the header of the reprint shall indicate it is a VIR reprint, not the original and 2) the 2D barcode printed in the sticker location shall have a sticker number of “VIRREPRINT” coded into the barcode instead of the number of the actual sticker associated with the inspection.

The Inspector may also view any images captured by the Inspector during the inspection. The Inspector shall have the option of printing the selected VIR or images. The VID shall track all VIR and image view/reprint requests by recording the following data:

· Date/time of request;

· VIN;

· Inspection Date/Time;

· Station ID;

· Workstation ID; and

· Inspector ID.

Contact Helpdesk Upon making this selection, the following shall be displayed on the screen:

· Helpdesk phone number;

· Helpdesk hours of operation;

· Approximate wait time to speak to the Helpdesk;

· An application to allow the user to send a text message to the Helpdesk;

· Text box for message shall allow up to 255 characters;

· Text box for inspector to enter name and contact number;

· Station ID and Workstation ID shall be automatically sent with message; and

· An application that allows the user to order workstation parts and consumables.

IM Program Regulations Upon making this selection, the software shall display a list of hyperlinks to RMV and DEP regulations by subpart. RMV regulation hyperlinks names shall be organized by safety inspection type (non-commercial, commercial, and 7D) and subpart hyperlink names shall match the name used during the inspection (e.g. Service Brakes.) DEP regulation hyperlinks shall be arranged by inspection type.

Main Menu Upon exiting the status screen following start-up, the following menu shall be displayed:

1. Vehicle Inspections;

2. Diagnostic Tests;

3. Calibrations/Checks;

4. Utilities;

5. View Messages;

6. Station Menu;

7. Service Menu;

8. QA/State Menu; and

9. Shutdown.

Vehicle Inspections Upon making this selection, the following sub-menu shall be displayed:

1. Perform Regular Inspection;

2. Alternate Inspections;

3. View/Reprint VIR;

4. Safety and Emissions Regulations;

5. Motorist Assistance Center (MAC) Functions; and

6. Return to Main Menu.

Perform Regular Inspection Upon making this selection, the software shall display the status screen described in section 3.5.1. The Inspector shall hit “ENTER” to proceed.

System lockout check If the system is locked out for any reason, the software shall display a message indicating that an inspection cannot be performed due to the lockout reason.

Inspector Login The Inspector is required to log in to begin the inspection. The login process shall have 6 steps:

1. Scan 2D barcode from Inspector license to enter Inspector ID;

2. Keyboard entry of 5 digit numerical PIN;

3. Verification of proper operation, image clarity, alignment of all cameras. Verification procedures shall be proposed by the Contractor as part of the detailed design specifications;

4. PC monitor mounted camera captures Inspector image. The Contractor shall propose a process for verifying that an image of the Inspector’s face was captured during login as part of the detailed design specifications.

5. 2 Inspection bay cameras (configured in the MASS17 Management Application, see Attachment D) capture images of the Vehicle in Inspection bay; and

6. 1 Inspection bay camera (configured in the MASS17 Management Application) begins to capture video footage of the inspection.

VIN/Plate Entry Screen The Inspector shall be prompted to enter the Vehicle information listed below. The inspector must hit [ENTER] after each entry to proceed to the next item.

· VIN

· Allow keyboard entry, scanning previous MASS17 Inspection sticker, or scanning Vehicle VIN plate barcode;

· Maximum of 17 characters;

· Display warning message if non-standard VIN (less than 17 characters, contains I, O, or Q, or 9th check digit does not compute correctly); and

· Prompt Inspector to capture image of Vehicle’s VIN tag for model year 1981 and newer vehicles.

· Plate State

· Allow keyboard entry or scanning previous MASS17 Inspection sticker;

· Default to “MA”;

· Select from Drop-down menu from Agency-provided list;

· Display warning message if state other than “MA” is selected; and

· Prompt Inspector to capture images of front and rear of Vehicle including license plates. Note: Vehicles with green PAN plates only have a rear plate.

· Plate Type

· Skip if state other than “MA” is selected;

· Allow keyboard entry or scanning previous MASS17 Inspection sticker;

· Default to PAN; and

· Select from alphabetical drop-down menu of Agency-provided list.

· Plate Number

· Skip to Registration Number if a “Section 5” plate type is selected;

· Allow keyboard entry or scanning previous MASS17 Inspection sticker;

· Display warning message if plate number does not conform to MA plate type mask; and

· Only allow alpha-numeric characters and “/” (for ham radio specialty plate).

· Registration Number - Section 5 Plate only

· Skip if non-section 5 plate type; and

· Display warning message if Registration Number does not match MA plate type mask.

· Suffix - Section 5 Plate only

· Skip if non-section 5 plate type; and

· Display warning message if Suffix does not match mask.

· Does Registration Document match vehicle (Yes/No)? Default = Yes

· Is Vehicle a Kit Car (Yes/No)? Default = No

· Only display if VIN is a non-standard format.

Upon completion of the VIN/Plate entry screen, the following shall occur:

· The software shall upload the entered data to the VID.

· If “Does Registration Document match vehicle” = “No”, the inspection is aborted with ABORT REASON = REG DOCUMENT, and the software shall print the REGISTRATION TURNAWAY document. The software shall return to the Vehicle Inspection Menu.

· If “Does Registration Document match vehicle” = “Yes”, the inspection shall proceed.

· The VID shall connect to ALARS to receive the authorization for the inspection to proceed. The ALARS authorization has 2 main components: 1) a check to see if the vehicle’s VIN and plate are active and 2) a check to see if the Station’s and Inspector’s licenses are active. The details of the VID/ALARS Start Test communication shall be developed jointly by the Contractor and the MassDOT/RMV.

· If ALARS authorizes the inspection to continue, the inspection shall proceed to the next section.

· If ALARS denies the vehicle authorization, an error message shall be displayed and the Inspector shall have the option to “retry” or “abort” the inspection.

· If “retry” is chosen, the VIN/Plate Entry screen shall be displayed showing the data entered previously by the Inspector and allow the Inspector to edit and retry.

· If “abort” is chosen, the test record shall be saved and sent to the VID with ABORT REASON = NO ALARS MATCH and the software shall return to the Vehicle Inspection Menu.

· If ALARS denies the Inspector or Station authorization, a warning message shall be displayed that describes the problem and the test shall be aborted.

· If the Workstation is unable to connect to the VID, an error message indicating the problem shall be displayed and the Inspector shall have the option to retry

· If the VID is unable to connect to ALARS, an error message indicating the problem shall be displayed and the Inspector shall have the option to retry.

Detailed Vehicle Data Initial Tests (Test Counter = 1) If the VIN is 17 characters and the 9th digit validates the VIN, then the VIN shall be considered a standard VIN. For a standard VIN, the software shall decode the VIN using a VIN decoder and return, at minimum, the following Vehicle information:

· Vehicle Type;

· Model Year;

· Make;

· Model Name;

· Fuel type;

· Number of cylinders;

· Engine displacement;

· GVWR;

· Body style; and

· Transmission type.

If the VIN cannot be decoded, detailed vehicle data from the previous inspection (if available) shall be displayed. If there is no previous inspection, the software shall retrieve the vehicle information from ALARS.

The software shall allow the Inspector to edit the Vehicle information. If the model year, fuel type, or GVWR are changed, the software shall record both the original and modified values. Changes to these parameters may alter the final test selections as described in Section 3.6.1.1.6.3 below and trigger a real-time inspection QA/test interruption as described in RFR Section 6.3.3.6. The Agencies may require certain vehicle data fields to be “locked”, preventing the Inspector from making changes.

Retests (Test Counter >1) For retests, the detailed vehicle data recorded from the previous inspection shall be displayed. The Inspector shall be able to edit the vehicle information. The Agencies may require certain fields to be “locked”, preventing the Inspector from making changes.

Odometer reading For all tests, the software shall prompt the Inspector to capture a digital image of the odometer reading on the dashboard using the hand-held camera. The software shall then prompt the Inspector to enter the odometer reading using the keyboard. For malfunctioning odometers, the software shall allow the Inspector to enter “BROKEN” as the odometer reading. For all tests, if the odometer reading entered is less than the previous test, a warning message shall be displayed. The odometer reading shall not be required for Trailers.

Emissions and Safety Test Selection Initial Emissions Test Selection The software shall use the vehicle information initially decoded from the VIN decoder (prior to Inspector changes) to determine the Initial Emission Test Selection (IETS):

The NETWORK CONTROL FILE (see MASS17 Management Application specification, RFR Attachment D) contains settings that are used to determine what emissions test, if any, a vehicle receives. The IETS shall be determined and recorded using the following logic:

IETS = 8 (LD/MD OBD) if the vehicle meets ANY of the following criteria:

· GVWR <=8,500 lbs. and Model Year >= “Start Model Year for Light-duty OBD” in the NETWORK CONTROL FILE (default = current year – 14)

· Fuel Type <>”Diesel” and GVWR <=14,000 lbs. and Model Year >= “Start model year for Medium-duty non-diesel OBD” in the NETWORK CONTROL FILE (default = 2008)

· Fuel Type = “Diesel” and GVWR <=14,000 lbs. and Model Year >= “Start model year for Medium-duty diesel OBD” in the NETWORK CONTROL FILE (default = 2007) IETS =9 (LD/MD NVOS) if it meets the requirements for ITES = 8 and ALL of the following:

· ALARS NEW/USED INDICATOR = N (new)

· CURRENT DATE - ALARS PURCHASE DATE <= 365 days

· No previous test record for vehicle (aborts not included)

· Odometer <7,500

· ABSOLUTE VALUE (CURRENT YEAR – MODEL YEAR) <3

IETS = 5 (HD OBD) if the vehicle meets any of the following criteria:

· Fuel Type <>”Diesel” and GVWR >14,000 lbs. and Model Year >=” Start model year for Heavy-duty non-diesel OBD” in the NETWORK CONTROL FILE (default = 2050)

· Fuel Type = ”Diesel” and GVWR >14,000 lbs. and Model Year >=” Start model year for Heavy-duty diesel OBD” in the NETWORK CONTROL FILE (default = 2050) IETS =6 (HD NVOS) if it meets the requirements for ITES = 5 and ALL of the following:

· ALARS NEW/USED INDICATOR = N (new)

· CURRENT DATE - ALARS PURCHASE DATE <= 365 days

· No previous test record for vehicle (aborts not included)

· Odometer <7,500

· CURRENT YEAR – MODEL YEAR <3

IETS = 4 (Diesel Opacity) if the vehicle is not subject to an OBD test AND meets the following criteria:

· Fuel type = “Diesel” and GVWR<10,000 lbs. and Model Year >= “Start model year for diesel opacity” (default = 1984) and Model Year <=” End model year for diesel opacity” in the NETWORK CONTROL FILE IETS = 1 (safety-only) if Fuel Type = “Electric” or Vehicle Type = “Off-road” IETS = 1 (safety-only) if the vehicle does not meet any criteria to receive an emissions test.

IETS = 0 (undetermined) if there is insufficient data to make a determination.

If the vehicle has a test exception (see Attachment D, MASS17 Management Application, Section 8.3), the specified test exception shall override the VID test selection. If the vehicle has an “Emissions Model Year” assigned to it, that value shall be used instead of the vehicle’s model year in the test selection logic.

Initial Safety Test Selection For a regular inspection, the software shall determine whether the vehicle receives a (N) Non-commercial safety inspection or (C) Commercial safety inspection. Based on the detailed vehicle data initially returned by the VID (prior to Inspector changes), the “Initial Safety Test Selection” (ISTS) shall be determined and recorded by the software using the following table:

ATN[footnoteRef:1] [1: If vehicle type is trailer, and GVWR is <=3,000lbs, trailer exempt from inspection. If > 3,000lbs. GVWR, Commercial inspection.]

3 If body type is pickup, SUV, or van, non-commercial inspection.

Commercial

Commercial

Commercial

Commercial

MVN[footnoteRef:6]1 [6: ]

Commercial

Commercial

Commercial

Commercial

Commercial

Commercial

Commercial

Commercial

STN[footnoteRef:15]1 [15: ]

>10,000 lbs. GCVWR used in commerce, Commercial inspection >3,000lbs. GVWR, used in commerce, Commercial inspection.

>10,000 lbs. GCVWR used in commerce, Commercial inspection

>10,000 lbs. GCVWR used in commerce, Commercial inspection >3,000lbs. GVWR, used in commerce, Commercial inspection.

>10,000 lbs. GCVWR used in commerce, Commercial inspection

If there is insufficient data available to make the determination (e.g. no GVWR), the ISTS shall be null.

If the vehicle has a test exception, the specified test exception shall override the VID test selection.

The following additional logic shall be applied for determining the safety test selection:

· Vehicle Type = Trailer, plate type = ATN, MVN, or STN, and GVWR <= 3000 lbs.

· the trailer is exempt from inspection. The test shall be aborted and an aborted test record shall be created.

· Plate type = BDN, the Workstation shall prompt the Inspector “Is the GVWR greater than 3000 lbs.? Y/N”. If the Inspector enters “N”, the Workstation shall prompt the Inspector “Is the GCVWR greater than 10,000 lbs?

· If “Y” to either question, the default safety test selection shall be Commercial.

· If “N” to both questions, the test shall be aborted because an inspection is not required and an aborted test record shall be created.

· Plate type = TRN or TRR, the Workstation shall prompt the Inspector “Is this vehicle used for commerce? Y/N”

· If the Inspector enters “N”, the trailer is exempt from inspection. The Workstation shall abort the test and create an aborted test record.

· If the Inspector enters “Y”, the Workstation shall prompt the Inspector “Is the GVWR greater than 3000 lbs.? Y/N”

· If the Inspector enters “N”, the Workstation shall prompt the Inspector “Is the GCVWR greater than 10,000 lbs? Y/N. If the Inspector answers “Y” to either question, the default safety test selection shall be Commercial.

· If the Inspector answers “N” to both questions, the test shall be aborted and an aborted test record shall be created.

· Plate type = CON, COR, or COV, the Workstation shall prompt the Inspector “Is this a placarded vehicle? Y/N”.

· If the Inspector enters “Y”, the default safety test selection shall be Commercial.

· If the Inspector enters “N”, the default safety test selection shall follow the guidelines in the above table.

· If the safety test type is Non-Commercial, the Inspector shall be allowed to change it to Commercial. If the safety test type is Commercial, the Inspector shall NOT be allowed to change it.

Final Test Selection Based on the detailed vehicle data reviewed and accepted by the Inspector, a final emissions and safety test selection shall be determined and recorded using the same rules used for the initial test selection described above.

If the vehicle has a test exception, the specified test exception shall override the VID test selection. The software shall display the final test selections for safety and emissions, if required. If the Inspector is not licensed to perform the test(s) required (e.g. commercial safety) or does not have the proper license class to drive the vehicle (e.g. CDL required for 26,000 lbs. and greater GVWR), then the software shall display a warning message and automatically abort the inspection. A test record of the aborted inspection with “Abort Reason” = “Incorrect license Class” shall be stored on the VID.

If the initial emissions test selection is defined (not “0”) and does not match the final test selection, the software shall trigger the real-time inspection QA/test interruption process described in RFR Section 6.3.3.6. If the initial safety test selection is “Commercial” and the final safety test selection is “Non-commercial”, the software shall trigger the real-time inspection QA/test interruption process described in RFR Section 6.3.3.6.

Light and Medium-Duty OBD Inspection The Light and Medium-duty OBD inspection shall include the components described in the following sections:

Visual Tampering Check The software shall prompt the Inspector to check for visual tampering of the OBD system and choose Pass or Fail. If the Inspector chooses fail, the software shall display a follow-up screen to allow the Inspector to choose a different result or confirm the failure. Regardless of the result, the OBD inspection shall continue. A help menu shall be available to assist the Inspector with identifying tampering.

Connect to Vehicle As part of the RFR Technical Response, the Bidder shall propose a process that reduces/eliminates the need for the Inspector to walk back and forth between the Workstation and vehicle to perform the OBD scan.

If the Inspector is unable to connect to the DLC, the software shall prompt the Inspector to choose one of the following reasons for failing the DLC Check:

· D = damaged;

· M = missing; or

· O = obstructed.

The software shall record the DLC result, fail the OBD inspection and advance to the safety inspection, if applicable.

OBD Scan Details The software shall monitor pin 16 voltage of the duration of the OBD scan. If pin 16 voltage is lost at any time during the scan, the vehicle shall fail the OBD inspection for OBD communication. Once the scan is completed, the software shall upload the OBD result to the VID so that the OBD test QA checks described in Section 3.6.1.1.7.9 can be performed. The OBD scan tool logs that document communication between the scan tool and vehicle shall be uploaded to the VID for every OBD scan.

Particular vehicles with known communication problems may have an exemption from the normal OBD scan process as described in RFR Attachment D, section 9.3. Instead of failing the OBD test due to no communication, these vehicles shall receive Key-On-Engine-Off (KOEO) and Key-On-Engine-Running (KOER) visual bulb checks to determine whether they pass or fail the OBD inspection and shall skip the remaining steps normally required by these Sections of 3.6.1.1.7.

If the scan tool cannot communicate with the vehicle, the software shall prompt the Inspector to check the connection and try again. The software shall allow unlimited attempts and the option to discontinue after the second attempt. If the Inspector chooses to discontinue, the software shall prompt the Inspector to perform the OBD System Operational check described in Section 3.6.3.3 below. If the check passes, the OBD inspection fails and the software shall continue to the safety inspection, if applicable. If the check fails, the software shall abort the inspection and the Workstation shall be locked out from OBD inspections until the OBD System Operational check is successful.

RPM check The software shall retrieve and record the vehicle’s RPM. Note: particular vehicles (such as hybrids) may have an exemption from this requirement as described in Attachment D section 9.3. For all other vehicles, if the RPM cannot be retrieved or is less than 250, the software shall display a warning message and allow the Inspector to try again. If the RPM cannot be retrieved a second time, the software shall prompt the Inspector to choose if the vehicle is a hybrid. If “Yes”, the vehicle shall not be required to pass the RPM check. If “No”, the RPM check fails, the OBD inspection fails, and the software shall continue to the safety inspection, if applicable.

MIL Status Check The software shall retrieve the MIL status of the engine control module(s). If the MIL is commanded on, the MIL result shall be “FAIL” and the software shall retrieve and record the number of DTCs present and up to 10 DTCs stored. If the MIL is commanded on, the software shall also prompt the Inspector to perform a visible Key-On-Engine-Running (KOER) MIL bulb check and record the results. Vehicles that fail the KOER bulb check will require a Key-On-Engine-Off (KOEO) check during the retest.

Readiness Monitor Status The software shall record the status (R = Ready,…