IMRFR AMENDMENT 2 2 25 16.docx

DOCX document 23 KB Posted

Attached to
Vehicle Inspection and Maintenance Program MDOTBOSTON-IM
Solicitation number
BD-16-1030-0R100-0R001-00000006553
Issued by
Massachusetts

About this file

This document is an amendment to a Request for Response (RFR) issued by the Commonwealth of Massachusetts Registry of Motor Vehicles, a division of the Massachusetts Department of Transportation, for their Vehicle Inspection and Maintenance Program. The amendment revises the requirements for the OBD scan tool to specify that the program shall require the State of California Bureau of Automotive Repair (BAR) Data Acquisition Device (DAD) hardware. It also updates the requirements for the format of responses and attachments, specifically the Cost Response. The related state and local contract opportunity is for managing and implementing the Vehicle Emission and Safety Test Program in Massachusetts, including developing and managing the Inspection Station network, developing and implementing inspection protocols, and acquiring, providing, and maintaining Inspection Station equipment and data systems.

The amendment provides additional details on the required OBD scan tool capabilities and the format of the Cost Response, which must clearly address each Response Element, provide all other information requested, and include the Bidder Financial Qualifications. Bidders are required to ensure that cost information is contained exclusively in the Cost Response.

View the file

Other files

File Type Posted
Applus Technologies Volume 1_Technical Response_Applus.pdf PDF
Opus Ispection ProcessFlowDiagram.pdf PDF
SGS Interview Questions 6-20-16.docx DOCX document
Attachment C - Computing Environments FINAL 12 10 15.docx DOCX document
SGS RFR Cost Response.pdf PDF
NOTICE of Revised posting date for amended IM RFR documents 3 3 16.docx DOCX document
SGS MA_Final_Part7.pdf PDF
IMRFR Evaluation Process memo_3-21-16_for COMMBUYS.docx DOCX document
2017 Scope Exh H - Service Response Time FINAL 12 10 15.docx DOCX document
Applus Technologies eppform_Applus.doc DOC document
Commitment Letter Attachments.pdf PDF
Applus Technologies Microsoft Product Terms.docx DOCX document
Applus Technologies MA Cover Page-Volume2.pdf PDF
Applus Technologies CoreSite Data Center Agreement_Applus~1.pdf PDF
SGS MA_Final_Part1.pdf PDF
Parsons Cost Proposal for MASS17.pdf PDF
IM RFR Amendment no3_3 9 16.docx DOCX document
Attachment G - Program Costs FINAL 12 10 15.docx DOCX document
Applus Technologies Attachment 1 Cover Page.pdf PDF
Applus Technologies Microsoft Volume Licensing Agreement_Applus.pdf PDF
Parsons Attachment G - Program Costs_Parsons.docx DOCX document
Bidders Conference Agenda_Handout_Attendees.doc DOC document
Attachment B - ALARS Interface FINAL 12 10 15.docx DOCX document
Attachment F - IM RFR Draft Scope of Services FINAL 12 10 15.docx DOCX document
QandA_vehicle_inspection_maintenance_Round2~1.xlsx XLSX spreadsheet
Parsons 3.2.2.8 prompt-pay-frm.docx DOCX document
Applus Bid Bond.pdf PDF
IM Evaluation Report 9-26-16.doc DOC document
Parsons 3.2.2.8.1 sdp-plan-form-1-commitment.docx DOCX document
Applus Technologies Attachment 3 Cover Page.pdf PDF
NOTICE TO BIDDERS REGARDING AMENDED DOCUMENT POSTING DATE 3.8.16.docx DOCX document
SGS MA_Final_Part3.pdf PDF
Attachment D - Management Application Spec FINAL 12 10 15.docx DOCX document
Parsons Attachment I - Bidders Cost Breakdown_Parsons.docx DOCX document
Notice of Applus as Apparent Successful Bidder.doc DOC document
SGS MA_Final_Part4.pdf PDF
QandA_vehicle_inspection_maintenance.xlsx XLSX spreadsheet
Parsons 3.2.2.8 Business Reference Form.doc DOC document
IMRFR AMENDMENT 1 1 25 16.docx DOCX document
Bidders 1 27 16 Conference Webinar and Training Information.doc DOC document
Parsons Attachment K - Bidders Response Checklist.docx DOCX document
Applus Technologies prompt-pay-frm_Applus.doc DOC document
Attachment L - Cloud Procurement Terms FINAL 12 10 15.docx DOCX document
MassDOT_Std_Contract_Form.doc DOC document
Parsons Attachment J - Bidders Financial Plan_Parsons.doc DOC document
SGS MA_Final_Part2.pdf PDF
Applus Technologies Amended Attachment K_Response Checklist_Applus.docx DOCX document
Opus Inspection Project Plan r011.pdf PDF
MassDOT_TandC.docx DOCX document
IMRFR Internal Scoring and Procedure doc 4.7.16.docx DOCX document
Show 40 more

Latest 50 of 80 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

COMMONWEALTH OF MASSACHUSETTS

REGISTRY OF MOTOR VEHICLES, A DIVISION OF

THE MASSACHUSETTS DEPARTMENT OF TRANSPORTATION

VEHICLE INSPECTION AND MAINTENANCE PROGRAM

REQUEST FOR RESPONSE (IM RFR)

RFR BD-16-1030-0R100-0R001-00000006553

AMENDMENT #2 TO THE IM RFR

Amendment Date: February 25, 2016

The IM RFR (RFR BD-16-1030-0R100-0R001-00000006553), which was originally posted on the Commonwealth’s COMMBUYS website on December 17, 2015, has been amended as follows:

1. RFR Section 1.8, entitled “Overview of the Inspection and Maintenance Program:” THE FIRST BULLET WITHIN RFR SECTION 1.8 HAS BEEN DELETED IN ITS ENTIRETY, AND REPLACED WITH THE FOLLOWING:

● Scan Tool – The Program shall require State of California Bureau of Automotive Repair (BAR) Data Acquisition Device (DAD) hardware for the Massachusetts OBD scan tool.

2. RFR Section 3.1.2, entitled “Format of Responses and Attachments:” THE SECOND BULLET WITHIN RFR SECTION 3.1.2 HAS BEEN DELETED IN ITS ENTIRETY, AND REPLACED WITH THE FOLLOWING:

●The Cost Response, which must clearly address each Response Element andprovide all other information requested in RFR Section 3.3, (including any relatedAppendices and Attachments). The Cost Response shall also include BidderFinancial Qualifications required in RFR Section 3.3.6. Bidders shall ensurethat cost information is contained exclusively in the Cost Response.
3.RFR Attachment A, Section 2.2.4, entitled “OBD Scan Tool:” SECTION 2.2.4HASBEEN DELETED IN ITS ENTIRETY, AND REPLACED WITH THEFOLLOWING:

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.

4. RFR Attachment A, Section 3.6.1.1.7.7, entitled “Additional OBD system data:” SECTION 3.6.1.1.7.7 HAS BEEN DELETED IN ITS ENTIRETY, AND REPLACED WITH THE FOLLOWING:

At minimum, the following OBD data elements shall be captured during the OBD inspection:

1. OBD Visual Tampering (Pass, Fail)

2. OBD DLC Result (Pass, Damaged, Missing, Obstructed)

3. Key On Engine Off (KOEO) check (Pass, Fail), if applicable

4. OBD Communication Result (Pass, Fail, Excluded)

a. Comm Fail Scan Tool Self Check (Pass, Fail), if applicable

5. OBD Communication Protocol

6. OBD RPM reading

7. RPM Result (Pass, Fail, Excluded)

8. MIL Command (Pass, Fail)

a. Key On Engine Running (KOER) check (Pass, Fail), if applicable

9. Up to 10 DTCs (DTC1, DTC2,…) retrieved only if MIL Commanded on

10. Total DTCs

11. Status of non-diesel/diesel OBD Monitors (Ready, Not Ready, Unsupported)

a. Misfire

b. Fuel System

c. Comprehensive Component

d. Catalyst

e. Heated Catalyst/ NOx After-treatment

f. Evaporative System/Reserved

g. Secondary Air System/Boost Pressure System

h. AC System/Reserved

i. O2 Sensor/Exhaust Gas Sensor

j. O2 Sensor Heater/PM Filter

k. EGR/VVT

12. Total Monitors Not Ready

13. Readiness Result (Pass, Fail, Turnaway, Excluded)

14. Overall OBD Result (Pass, Fail, Turnaway, Excluded)

15. Mode 01 PID $1c response

16. OBD Fuel Type (PID $51 or PID $01/Byte B/bit3)

17. PCM ID for each module responding

18. Mode 01 PID00, PID20, PID40, PID60, and PID80 for each module responding

19. PID Count for each module responding

20. CAT DTC (Yes, No)

21. CAT DTC Previous Test (Yes, No)

22. OBD VIN QA Result (Pass, Fail, NA)

23. OBD Parameter QA Result (Pass, Fail, NA) Depending on the model year and fuel type of the vehicle, the following additional OBD data elements shall be captured:

1. CAL ID

2. CVN

3. MIL on Distance

4. Warm up since Codes Cleared

5. Distance Since Codes Cleared

6. MIL on Run Time

7. Run Time Since Codes Cleared

8. Up to 10 Permanent DTCs (PDTC1, PDTC2, …) After Contract Award, the Contractor, in cooperation with the Agencies, shall finalize the OBD data elements captured during the OBD inspection.

IN ALL OTHER RESPECTS, ALL TERMS AND CONDITIONS OF THE IM RFR REMAIN THE SAME AS OF THE DATE OF THE POSTING OF THIS AMENDMENT #2.

File details come from the government source that posted it. Updated .