20250212_RFP_24-07_NMCOG Traffic Counting Program.pdf

REQUEST FOR PROPOSALS

#24-07

Northern Middlesex Metropolitan Planning Organization

2025 Traffic Counting Program – Data Collection Services

SCHEDULE

RFP Released: Wednesday, February 12, 2025

Questions due: Wednesday, February 26, 2025, by 4:00pm

Answers to questions posted: Monday, March 3, 2025, by 4:00pm

Proposals due: Wednesday, March 12, 2025, by 4:00pm

Contract window: March 2025 – November 2025

QUESTIONS

All questions regarding this Request for Proposals (RFP) should be directed to:

Carlin Andrus, GIS and Data Program Manager

Email: candrus@nmcog.org

SUBMISSION

Responses will be received electronically until Wednesday, March 12, 2025 by 4:00pm.

Email an electronic file to: candrus@nmcog.org

RFP advertised at: www.nmcog.org and on COMMBUYS mailto:candrus@nmcog.org http://www.nmcog.org/

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 2

1. Background on the Northern Middlesex Traffic Counting Program The Northern Middlesex Council of Governments (NMCOG) works with communities in the Greater Lowell region to support and enhance a wide range of community and regional planning objectives. We plan for and advance actions related to climate resiliency and adaptation, energy, economic development, environmental protection, housing, land use, municipal service delivery, public health, public safety, regional collaboration, and transportation. NMCOG is governed by a policy board of local elected officials from its member municipalities of Billerica, Chelmsford, Dracut, Dunstable, Lowell, Pepperell, Tewksbury, Tyngsborough, and Westford. NMCOG also serves as technical staff to the Northern Middlesex Metropolitan Planning Organization providing comprehensive transportation planning services for the region under contract with MassDOT.

NMCOG is seeking to hire a consultant to assist with traffic count data collection for the 2025 season. Traffic count data is to be collected at a minimum of 100 locations and a maximum of 120 locations within the Northern Middlesex region of Massachusetts. 100 likely count locations have been provided at the end of this document. Further information on the count locations is forthcoming and will be provided prior to the beginning of the Traffic Count Season on May 1, 2025. A Scope of Work will be developed between the consultant and NMCOG prior to the beginning of the Traffic Count Season. NMCOG will work with the consultant to apply and gain approval for any permits required for counts conducted on State roadways in MassDOT Districts 3 and 4.

All traffic counts must be conducted no earlier than May 1, 2025 and conclude by October 31, 2025, with makeup counts occurring through November 30, 2025.

2. Bid Submittal Information All bids must be original and delivered via email to:

Northern Middlesex Council of Governments 672 Suffolk Street, Suite 100 Lowell, MA 01854 Attention: Carlin Andrus Email: candrus@nmcog.org

Bids must be received by 4:00pm, Wednesday, March 12, 2025. Bids should be submitted electronically, using the subject line, “2025 Traffic Count Program Data Collection Services Bid.” Bids received after the time set for the bid opening will be rejected.

NMCOG reserves the right to waive irregularities in bids, to reject any or all bids with or without cause, and to award the bid that it determines to be in the best interest of NMCOG. NMCOG does not discriminate on the basis of race, color, national origin, sex, religion, age, or disability status in employment or provision of service.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 3

NMCOG is not responsible for Proposals that are delinquent, lost, stolen, mismarked, sent to an address other than that given, sent by mail or courier service, and proposal postmark dates and times will not be considered as meeting the deadline.

3. Questions and Inquiries Carlin Andrus, GIS and Data Program Manager, is the point of contact for this Request for Proposals (RFP). Questions concerning this request should be directed no later than Wednesday, February 26 at 4:00pm to: candrus@nmcog.org.

NMCOG will post responses to any questions received to the NMCOG procurement page (https://www.nmcog.org/request-for-proposals) and COMMBUYS by Monday, March 3 at 4:00pm.

4. Scope of Services The Consultant shall be responsible for providing NMCOG with traffic count data for locations identified by NMCOG. Collection of the traffic data will be performed using an automated collection method to be agreed upon by the Consultant and NMCOG.

Prior to conducting counts, counting equipment shall be tested in accordance with FHWA requirements and test data shall be submitted to MassDOT and NMCOG for certification and acceptance prior to count data collection activities. All counts shall be taken in accordance with the 2025 RPA Traffic Counting Procedures prepared by MassDOT (provided at the end of this document).

Schedule The anticipated date for contract award is March 17, 2025. All counts and work performed under this contract must be invoiced monthly and completed prior to November 30, 2025.

Deliverables Required deliverables include:

• Traffic layouts for count locations where permits are required

• Count volumes, direction, vehicle classifications, and speed data in two file formats:

1) the agreed-upon MS2-compatible digital file format (see requirements below) and

2) exported to .csv or an Excel-compatible file format for use by NMCOG

• Count reports for each count location including total volume (ADT) by direction, peak hours by direction, vehicle class, and speed. PDF reports generated by counter software are acceptable.

• Traffic recorder test results and an Excel file with recorder ID numbers

• Completion of NMCOG’s traffic count tracking spreadsheet, including scheduled count dates, count completion status, count latitude and longitude, traffic recorder ID numbers, and notes describing count data or count location anomalies.

Additional detailed information on deliverables is included in MassDOT’s 2025 RPA Traffic Count Procedures.

mailto:candrus@nmcog.org https://www.nmcog.org/request-for-proposals https://www.nmcog.org/request-for-proposals

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 4

Additional Information For the bidder’s reference, a copy of MassDOT’s 2025 Counting Procedures is included at the end of this document. Unless otherwise noted in the Clarifications to the MassDOT Counting Procedures listed below, the bidder shall assume all responsibilities assigned to the RPA (NMCOG) in the Counting Procedures document.

Clarifications to the MassDOT Counting Procedures:

• Section 2 – Counter Accuracy: In the first paragraph, ‘recorder accuracy certification’ refers to a traffic simulation test offered by some counter manufacturers. If the traffic counters do not have this testing ability, the manual certification procedures in the paragraphs that follow need to be met. NMCOG may accept an alternative testing method to determine counter accuracy subject to review and approval by MassDOT.

• Section 6 – Count Intervals and Duration: In all instances, a valid count will require a minimum of 48 hours of consecutive data. For bidding purposes, assume all counters will be placed for 72 hours. Each location will have vehicle classification and speed data unless otherwise noted.

• Section 7 – Roadway Functional Class: NMCOG will provide the Federal Functional Class information along with the count locations to the Consultant prior to the beginning of the Traffic Count Season.

• Section 11 – Data Review: NMCOG can provide prior count information for reference, if available. In the proposal, please specify the total cost for conducting all vehicle counts, along with the average cost per vehicle count. In total, NMCOG is seeking counts at a minimum of 100 locations and a maximum of 120 locations. Count locations will be identified by NMCOG as MassDOT-assigned locations or NMCOG program locations.

• Section 4 – Data Format and Transmittal: The Consultant must provide count volume, classification, and speed data in a digital format that can be successfully uploaded and assigned to count locations in MassDOT’s MS2 statewide Traffic Count Database System (MS2 TCDS, at mhd.ms2soft.com). The file format may be .prn, JAMAR per vehicle .txt, .csv, or another format proposed by the consultant that has been confirmed by NMCOG and/or MassDOT for MS2 compatibility.

o Each count should include the tested and accepted recorder ID number. A separate Excel table indicating the recorder IDs used for each count is acceptable.

o Consultant will transmit files to NMCOG on a monthly basis with latitude and longitude coordinates for each collection location. NMCOG can provide access to the agency’s traffic counting web map to view prior count locations and other information.

• Section 14 – File Naming: Traffic count file names must match MassDOT’s MS2 location ID number, or in the case of new locations, follow the format specified in section 14 (RPA06 - XXX [3-digit town ID] – XXXX [NMCOG ID]). NMCOG will work with the consultant to ensure files are correctly named and will provide the required file names when available.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 5

• Note that for one-direction count files, the direction of traffic should be included following this format as an underscore followed by two-letter abbreviated direction.

For example, eastbound and westbound counts should be formatted as RPA06-031-xxxx_EB, and RPA06-031-xxxx_WB, respectively.

Permitting Process:

Once NMCOG and the Consultant have finalized the proposed count schedule, NMCOG will transmit this schedule to the appropriate Police and Highway Departments along with the Consultant’s contact information. The Consultant shall inform NMCOG of any count rescheduling. NMCOG will coordinate with local officials regarding count locations, schedules, and any requirements for police details. Consultant is responsible for safety measures at all count locations, including cost of police detail if requested by Consultant. As soon as possible, the Consultant will prepare forms and materials necessary to secure permits from MassDOT Districts 3 & 4 for counts to be conducted on state highways. NMCOG will submit these materials to each District to secure the necessary permits.

5. Applicant Proposal Content NMCOG requires the Applicant to submit a concise Proposal that clearly addresses all the requirements outlined in this RFP. One copy of the Applicant’s Proposal shall be submitted and shall be organized in an easy to follow format. The Proposal must include the minimum sections below:

Background of Applicant:

• Include a cover letter stating that the Applicant has read and will comply with all the terms and conditions of this Request for Proposals. The cover letter shall be signed by an authorized individual.

• Provide a brief description of the Applicant’s firm including the size of the organization, location of offices, years in business, years of work in the Commonwealth of Massachusetts, organizational chart, name of owner and principal parties, and staff titles.

• Outline the qualifications of the staff who will perform the work described in the Scope of Services.

• Include contact information for the staff person who will be NMCOG’s main contact, as well as a backup contact in the event the main contact is unreachable.

Applicant Statement of Understanding and Approach:

• Describe the methodology to be used to complete the Scope of Services as detailed in this Request for Proposals.

• Discuss and describe their experience with traffic data collection, including experience working in Massachusetts.

• Provide a statement of the services the firm believes differentiates their firm from other firms.

• Identify the responsibilities of NMCOG and the Applicant.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 6

Scope of Work:

• Provide details with specific task descriptions to demonstrate that the Applicant has considered all sections of this RFP and that the Applicant will cover them thoroughly.

References:

• Provide the following information for Communities and/or Clients for whom the Consultant has performed traffic collection related work:

o Community and/or Client name, address, telephone number, email address.

o Person to contact for references.

o Time period that data collection was done.

o Brief description of the scope of services provided.

Cost Estimate:

• Provide a cost estimate for providing services to complete the traffic counts requested.

• Include an average cost per count location figure as well as an overall cost for all locations.

• For informational purposes, bids should contain unit costs for counts as they vary based on count type and roadway type. As an example, unit costs should be shown for:

o Classification counts for four-lane facilities.

o Classification counts for two-lane facilities.

Cost estimate should include all expenses necessary to prepare permit applications, requests for police detail (if preferred by consultant), processing / exporting of data into necessary file formats, and regular project management coordination calls.

6. Review of Proposal and Consultant Selection NMCOG staff will review proposals, scoring applicants based on their proposed ability to satisfy the requirements of this RFP, proposal completeness, and clarity of contents.

After evaluating all Proposals and discussing them further with the Applicant finalists, NMCOG reserves the right to further negotiate the Scope of Services and cost estimate.

7. Additional Information

• NMCOG will not reimburse Applicants for any costs associated with the preparation and submission of their proposal or interview.

• This Request for Proposals does not obligate NMCOG to award or accept a contract for any expressed or implied services.

• NMCOG reserves the right to reject or accept any and all Proposals and to waive minor irregularities in any Proposal reviewed.

• NMCOG reserves the right to request any Applicant submitting a Proposal to clarify its Proposal or supply additional material deemed necessary to assist in the selection of a Consultant, and to modify or alter any of the requirements herein.

• NMCOG reserves the right to make useful and well-informed amendments to this Request for Proposals prior to the Proposal due date.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 7

• An Applicant may withdraw their Proposal at any time prior to the awarding of a contract.

8. Comparative Evaluation Criteria:

NMCOG recommends that an Applicant review and fully comprehend the “Criteria for Evaluating Proposals” section below and use as a guide when completing their Proposal. All Proposals received by NMCOG shall be compared utilizing these criteria, which are based on:

• Qualifications of Applicant organization and key personnel.

• Experience and demonstrated knowledge of completing traffic data collection.

• Experience in NMCOG region and/or in Massachusetts.

• Applicant availability to be assigned work and respond expeditiously.

9. Criteria for Evaluating Proposals The Proposals shall be rated by NMCOG staff within the following “categories” and according to the following “Minimum Criteria” and “Additional Review Criteria”. In summary, the “Minimum Evaluation Criteria” and “Additional Review Criteria” include:

• Minimum Criteria o Submission of a complete Proposal.

o Minimum two (2) year experience completing traffic counts.

o Minimum of two (2) year experience working in Massachusetts and with

MassDOT.

• Additional Review Criteria o Quality of Proposal, Approach and Past Work.

o Staff Qualifications and Experience.

o Applicant Staffing and Other Resources.

o Years in Business, and Years Working in Massachusetts.

o Quality of Materials Presented by the Applicant.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 8

QUOTE FORM

Price proposed for the work outlined above:

Provide work described in the above Scope of Services:

TOTAL COST

(price in numbers)

Average Cost Per Count words)

Informational Cost Figures

Classification counts for 4 lane facilities

(price in numbers)

Classification counts for 2 lane facilities

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 9

2025 RPA TRAFFIC COUNTING PROCEDURES

The following Traffic Counting procedures are to be followed by each Regional Planning Agency:

1) Each RPA shall contact the MassDOT District office in their region to obtain any required permits prior to installing traffic counting equipment on state owned roadways. Installed traffic recorders on all roadways shall be clearly labeled with the name of the equipment agency/owner (RPA/consultant) and a phone contact number.

2)The Federal Highway Administration (FHWA) requires that all equipment used to gather traffic data for the Traffic Monitoring System for Highways (TMS/H) shall be tested prior to commencing the yearly program. Data collected with equipment that does not meet the following test requirements will not be accepted. Submitted recorder accuracy certification with an approved traffic counter tester is an acceptable alternative to the below testing requirements.

- Traffic recorder axle (not vehicle) volumes shall be tested against manual axle volumes for a minimum of two consecutive intervals per recorder. It is not necessary to set the recorder for a classification count.

- Submit a spreadsheet to MassDOT at the start of the season showing the counter ID #, manual volume, recorder volume, and % error for each interval. % Error = (manual volume minus recorder volume)/Manual volume x 100.

- Recorders showing a difference in axle volumes < 10% compared to the manual axle volumes for each interval are acceptable. Recorders that fail the test shall be repaired and tested again. MassDOT must accept the test and retest results prior to that recorder being used to collect MassDOT traffic counts.

3) Exact field locations and the count install/removal dates are to be uploaded to the GIS Traffic Data map via a phone application “ArcGIS Collector”. http://massdot.maps.arcgis.com/home/index.html

4) The data file for each collected traffic count should include the tested & accepted recorder ID number.

A separate listing (kept on file in your agency) is acceptable if your traffic recorders & software do not have that option. Electronic data shall be in a format that can be submitted and uploaded to the

Midwestern software website database (mhd.ms2soft.com).

5) Ensure that the MassDOT Station Number is used for the count data file name and is programmed into the recorder if possible. Stay as close to the MassDOT location description as possible. An explanation shall be submitted in writing (via email) if any MassDOT program location cannot be counted in the current season for some reason (construction, etc.) at the specified location. Any current season incomplete MassDOT program counts shall be counted in the following year after the issue

(construction, etc.) has been resolved. Maps or sketches of count locations may be emailed to Statewide

Traffic Data Collection for clarification.

6) 60-minute or shorter data collection intervals (15 min, etc) can be used for a minimum of 48 hours

(consecutive preferred) of weekday (Tuesday thru Thursday preferred) directional data. Each direction should be counted during the same time period. All uploaded counts shall have full 60-minute intervals and full 24-hour periods. Any first or last interval partial hour data should not be included in the uploaded data.

http://massdot.maps.arcgis.com/home/index.html

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 10

7) The RPA shall input the below listed Federal “Functional Class” code, the “SF Group” (seasonal factor group), the “AF Group” (axle factor group), and the “Rural/Urban” designation for any RPA city/town (non-MassDOT program) counts uploaded to MS2.

1 = Interstate

2 = Principal Arterial – Other Freeways & Expressways

3 = Principal Arterial - Other

4 = Minor Arterial

5 = Major Collector

6 = Minor Collector

7 = Local

8) Route numbers and/or street names should be used in descriptions, whenever possible, for counts other than MassDOT coverage counts. One-way counts should be labeled as such and include the direction on the MS2 website.

9) Traffic counts should be evenly spaced throughout the counting season. Schedule the counts so they are not taken during an event that would affect the normal traffic flow (Legal holidays, local fairs, concerts, traffic detours, natural disasters, pandemics, etc.). Recreational area counts should be taken during the same time frame as previous years for better historical comparisons and growth trends.

10) Classification counts shall be done at all MassDOT requested locations if possible. Class counts shall be done with a separate recorder & hose setup for each lane of traffic unless the recorder is specifically designed to accurately class multiple lanes. Class counts with less than 10 % “unidentified” vehicles are acceptable and the percentages for the FHWA 13 class typology categories shall be reviewed (each lane, each direction, and totals) for count location appropriateness. The recorder classification column headings shall be set up to agree with the attached 13 FHWA classification categories. Volume data shall be created from the classification data in the MS2 website – volume data from a classification count does not need to be uploaded separately.

11) Review the collected data (including MS2 upload QC checks) and conduct recounts of bad data as necessary. Compare the count data with prior year data at that location on the MS2 website

(mhd.ms2soft.com). If the count varies significantly from previous years or has one direction significantly higher than the other, an explanation for the change should be furnished.

12) Contact MassDOT Traffic Data Collection (Misrak Sultan) if you believe a MassDOT program count needs to be edited (incorrect map location plot, description, FC, etc.) on MS2. MassDOT will review the location and make any appropriate edits since the RPA’s do not have administration privileges to modify the MassDOT location parameters.

13) Unfactored traffic counts shall be uploaded to MS2 on a regular basis during the counting season. All counts shall be uploaded to MS2 by the end of the year. This applies to both the MassDOT traffic program counts and other RPA city/town counts. Turning movement counts are to be uploaded via the

“TMC” button located at the top of the “TCDS” home page.

14) A file naming convention was developed for non-MassDOT program counts to facilitate system searches and custom queries. The MS2 location ID should be your Username (RPAxx), a dash, the city/town number, a dash, and then your own designation. The city/town designation numbers are in the attached excel listing. As an example, a count done by Old Colony (RPA09) in Abington (City # 001) for RPA count name/number xxxxxxxxxxxx would have the location ID in MS2 as RPA09-001-xxxxxxxxxxxx. Note that the file name can be up to a maximum of 25 characters.

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 11

15) Uploaded counts are QC checked with the results put in the “Count Group Assign List” on the MS2

Admin page. Data without errors can be “Auto Assigned” by the RPA to push them into the database.

The RPA shall review and resolve any data with errors codes generated by MS2. This involves assigning data deemed good, deleting data deemed bad, renaming/re-uploading files to agree with the correct “location ID” (error code 1), etc.

16) At the completion of the yearly program, all MassDOT Traffic Count Program counts, and other RPA

City or Town counts should be archived electronically by the RPA (separately from the MS2 website www.ms2soft.com).

Below is the contact information (email preferred) for questions regarding the RPA traffic Counting program or procedures:

Misrak Sultan

Statewide Traffic Data Collection

936 Elm Street Concord, MA

Concord, MA 01742

Email: Misrak.Sultan@dot.state.ma.us

Concord phone: (978) 287-6117

Cell phone: (617) 620- 7314 http://www.ms2soft.com/

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 12

2025 NORTHERN MIDDLESEX TRAFFIC COUNT DATA COLLECTION PROGRAM LOCATIONS (PRELIMINARY)

NMCOG

ID

MassDOT MS2 Location ID

Road Name and Location Municipality Functional

Class Latitude Longitude

14 4066 Concord Rd east of Middlesex Turnpike Billerica U4 42.548244 -71.280418

93 4061 Springs Rd at Bedford Town Line Billerica/Bedford U6 42.526427 -71.280917

98 4069 Treble Cove Rd north of Rte 3 Billerica U5 42.564136 -71.297346

113 4055 Dalton Rd west of Rte 4 (North Rd) Chelmsford U6 42.604826 -71.354083

127 4041 Parkerville Rd/S Chelmsford Rd at Chelmsford/Westford Town Line Chelmsford/Westford U2 42.569489 -71.393820

168 4056 Turnpike Rd south of Rte 129 (Billerica Rd) Chelmsford U5 42.598313 -71.339245

171 4042 Concord Rd at Carlisle Town Line Chelmsford/Carlisle U4 42.562049 -71.352625

259 4077 Central St south of Jackson St Lowell U5 42.642401 -71.308542

279 4145 Fleming St west of Stevens St Lowell U6 42.625776 -71.331656

297 4148 Industrial Ave under Connector Lowell U5 42.613762 -71.320291

304 4086 Lakeview Ave west of Rte 38 (Bridge St) Lowell U5 42.649268 -71.304801

321 4076 Market St west of Central St Lowell U4 42.644356 -71.308912

334 4101 Middlesex St west of Burnside St Lowell U5 42.638293 -71.341530

406 4074 Stevens St north of Princeton Blvd Lowell U5 42.635492 -71.334121

509 4107 Rogers St west of Whipple Rd Tewksbury U5 42.610872 -71.268278

552 4057 Dunstable Rd west of Rte 3 Tyngsborough U6 42.651827 -71.423143

777 4085 Mammoth Rd south of Eighth Ave Lowell U5 42.654559 -71.338566

6 251121 Billerica Ave north of "T" Station entrance Billerica U4 42.593270 -71.279566

25 236485 Faulkner St west of Station St Billerica U5 42.592439 -71.282978

34 250651 Lowell St east of Rte 3A (Boston Rd) Billerica U5 42.590822 -71.296190

59 RPA06-031-59 Rte 129 (Chelmsford Rd) west of Brick Kiln Rd (Town Line) Billerica/Chelmsford U3 42.588201 -71.308906

65 250656 Rte 129 (Chelmsford Rd) east of Brick Kiln Rd Billerica U3 42.588008 -71.308008

70 251124 Rte 3A (Boston Rd/Gorham St) at Billerica/Chelmsford Town Line Billerica/Chelmsford U3 42.600615 -71.298349

71 256483 Rte 3A (Boston Rd) north of Bridge St Billerica U3 42.574994 -71.281830

77 251125 Rte 3A (Boston Rd) north of Community Rd Billerica U6 42.527867 -71.226484

78 RPA06-031-78 Rte 3A (Boston Rd) north of Judy St Billerica U3 42.536673 -71.242125

84 256484 Rte 3A (Boston Rd) south of Floyd St Billerica U3 42.570644 -71.276673

109 239110 Rte 4 (North Rd) north of Technology Dr Chelmsford U5 42.627012 -71.369419

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 13

ID

MassDOT MS2 Location ID

Road Name and Location Municipality Functional

Class Latitude Longitude

122 205613 Middlesex St east of Princeton St Chelmsford U5 42.638841 -71.382171

126 235852 Old Westford Rd west of Rte 3 Chelmsford U5 42.621398 -71.367536

141 RPA06-031-141 Rte 129 (Billerica Rd) west of Rte 3 Chelmsford U5 42.589753 -71.315603

157 RPA06-056-157 Rte 40 (Groton Rd) E Rte 3 NB Chelmsford U3 42.632785 -71.402746

183 RPA06-079-183 Lakeview Ave west of Mammoth Rd Dracut U5 42.682854 -71.353468

184 240398 Lakeview Ave west of Tennis Plaza Rd Dracut U5 42.679530 -71.342190

185 252315 Mammoth Rd at Lowell/Dracut Town Line Dracut/Lowell U4 42.657764 -71.341821

188 240399 Mammoth Rd south of Lakeview Ave Dracut U5 42.682359 -71.354354

198 254058 Phineas St south of Lakeview Ave Dracut U0 42.672489 -71.332356

199 250759 Rte 110 (VFW Highway/Merrimack Ave) at Lowell/Dracut Town Line Dracut/Lowell U4 42.650250 -71.287866

206 236616 Rte 113 (Pleasant St) east of Lakeview Ave Dracut U5 42.664830 -71.321594

209 4103 Rte 38 (Bridge St) at NH State Line Dracut/Pelham, NH U3 42.697234 -71.313467

231 3372953 Rte 113 (Pleasant St/Dunstable Rd) at Town Line Dunstable/Pepperell U1 42.669063 -71.532511

234 236617 Rte 113 (Kendall Rd/Main St) at Dunstable/Tyngsborough Town Line Dunstable/Tyngsborough U3 42.683918 -71.449662

244 RPA06-160-244 Arcand Dr east of Father Morrisette Blvd Lowell U5 42.647951 -71.313131

277 RPA06-160-277 Father Morissette Blvd at High School (Dutton St) Lowell U5 42.648103 -71.312884

287 RPA06-160-287 Gorham St north of Union St Lowell U3 42.639055 -71.308858

288 3372705 Gorham St south of Walnut St Lowell U4 42.636068 -71.308952

300 255102 Lakeview Ave at Lowell/Dracut Town Line Dracut/Lowell U5 42.662417 -71.319096

301 RPA06-160-301 Lakeview Ave south of Farmland Rd Lowell U5 42.659118 -71.314886

328 RPA06-160-328 Merrimack St east of Worthen St Lowell U5 42.645972 -71.313424

375 4084 Rte 113 (Pawtucket Blvd) west of Mammoth Rd Lowell U3 42.649735 -71.332272

380 216046 Rte 38 (Bridge St) north of VFW Highway Lowell U3 42.649303 -71.304192

385 240628 Rte 3A (Gorham St) at Chelmsford/Lowell Town Line Chelmsford/Lowell U4 42.614390 -71.303244

388 RPA06-160-388 Rte 3A (Gorham St) south of Butler Ave Lowell U3 42.632344 -71.308899

421 3373016 VFW Hwy (Eastbound) west of Rte 38 (Bridge St) Lowell U3 42.649168 -71.305239

425 4100 VFW Hwy west of University Ave Lowell U3 42.652259 -71.325642

435 RPA06-160-435 Woburn St south of I-495 Lowell U3 42.617266 -71.288475

448 250800 Brookline St at NH State Line Pepperell/Hollis, NH U7 42.704265 -71.619821

496 RPA06-295-496 North St north of Main St Tewksbury U5 42.611332 -71.231754

502 RPA06-295-502 Pleasant St south of Rte 38 (Main St) Tewksbury U5 42.611405 -71.233375

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 14

ID

MassDOT MS2 Location ID

Road Name and Location Municipality Functional

Class Latitude Longitude

515 RPA06-295-515 Rte 38 (Main St) at Lowell/Tewksbury Town Line Lowell/Tewksbury U3 42.628793 -71.274616

517 RPA06-295-517 Rte 38 (Main St) Btwn I-495 Ramps Tewksbury U3 42.627725 -71.272092

519 RPA06-295-519 Rte 38 (Main St) north of Dewey St Tewksbury U3 42.612797 -71.235339

522 RPA06-295-522 Rte 38 (Main St) south of Capitol Ave Tewksbury U3 42.619283 -71.253671

524 4111 Rte 38 (Main St) south of I-495 Tewksbury U0 42.626097 -71.268775

528 RPA06-295-528 Rte 38 (Main St) south of Villa Roma Dr Tewksbury U3 42.597540 -71.217442

563 RPA06-301-563 Middlesex Rd south of Rte 3 Ramps Tyngsborough U4 42.698350 -71.439864

635 3372952 Rte 110 (Littleton Rd) at Chelmsford/Westford Town Line Chelmsford/Westford U4 42.578854 -71.396448

640 RPA06-330-640 Rte 110 (Littleton Rd) east of Powers Rd Westford U3 42.557638 -71.437876

643 RPA06-330-643 Rte 110 (Littleton Rd) west of Boston Rd Westford U5 42.565800 -71.424397

677 257215 Drum Hill Rd south of Parkhurst Rd Chelmsford U3 42.625680 -71.360441

683 RPA06-160-683 Dutton Street south of Broadway Lowell U5 42.643299 -71.314985

703 RPA06-295-703 Rte 38 (Main St) south of Shawsheen St Tewksbury U3 42.588589 -71.201332

710 RPA06-295-710 East St west of North St Tewksbury U5 42.611925 -71.231853

711 RPA06-295-711 North St north of East St Tewksbury U5 42.612101 -71.231606

715 RPA06-295-715 North St south of East St Tewksbury U5 42.611630 -71.231678

720 257521 Dutton St north of Broadway St Lowell U5 42.643713 -71.314631

724 257523 Gorham St south of Lowell Connector Lowell U3 42.634748 -71.309006

725 257525 Jefferson St over Western Canal Lowell U6 42.645414 -71.317256

737 238425 Rte 3A (Thorndike St) btwn Highland and YMCA Dr Lowell U3 42.635669 -71.312217

738 RPA06-160-738 Rte 3A (Thorndike St) south of Madison St Lowell U3 42.634576 -71.311094

758 RPA06-056-758 Middlesex St at Lowell/Chelmsford Town Line Chelmsford/Lowell U5 42.635461 -71.363837

765 RPA06-081-765 Main St west of Rte 113 (Pleasant St) Dunstable U0 42.674569 -71.483268

796 RPA06-056-796 Brick Kiln Rd west of Rte 3A (Boston Rd) Chelmsford U6 42.604023 -71.300163

823 RPA06-160-823 Rte 110 (Chelmsford St) south of Parker St Lowell U5 42.627598 -71.322349

831 RPA06-160-831 French St east of Kirk St Lowell U5 42.647449 -71.309279

836 RPA06-079-836 Lakeview Ave north of Phineas St Dracut U5 42.673011 -71.332394

849 RPA06-160-849 Father Morissette Blvd east of Aiken St Lowell U5 42.650038 -71.319119

861 RPA06-301-861 Middlesex Rd north of Locust Ave Tyngsborough U5 42.691167 -71.433900

879 258028 Rte 110 (Chelmsford St) south of Rte 3A (Westford St) Lowell U3 42.637536 -71.316208

899 RPA06-160-899 Merrimack St east of Cabot St Lowell U5 42.648119 -71.318679

Northern Middlesex 2025 Traffic Counting Program Request for Proposals 15

ID

MassDOT MS2 Location ID

Road Name and Location Municipality Functional

Class Latitude Longitude

918 RPA06-079-918 Rte 38 (Bridge St) south of West Third St Lowell U3 42.649676 -71.303981

971 RPA06-295-971 East St west of Whittemore St Tewksbury U4 42.617024 -71.197967

973 3372608 Ledge Rd south of Dunstable Rd Chelmsford U4 42.647399 -71.406008

1027 RPA06-160-1027 Merrimack Street West of Kirk Street Lowell U5 42.645795 -71.311267

1033 RPA06-079-1033 Rte 113 (Pleasant St) west of Lakeview Ave Dracut U5 42.646189 -71.271552

1039 RPA06-056-1039 Rte 4 (North Rd) north of Parkhurst/Davis Rd Chelmsford U5 42.616090 -71.363622

1042 RPA06-031-1042 Rte 3A (Boston Rd) south of Lowell St Billerica U3 42.590338 -71.296192

1046 RPA06-079-1046 Rte 113 (Arlington St) east of Rte 38 (Bridge St) Dracut U5 42.669270 -71.302662

1047 RPA06-079-1047 Rte 38 (Bridge St) north of Rte 113 (Pleasant St / Arlington St) Dracut U3 42.669356 -71.303374

1049 RPA06-231-1049 Park St south of Brookline St Pepperell U5 42.685833 -71.601612