RFP Addendum No.2.pdf

SCHOOL TRANSPORTATION SERVICES ROUTING AND DISPATCH SYSTEM

SOLICIATION NO. 2526-118

ADDENDUM NO. 2

Date: November 7, 2025 To: All Document Holders

The following changes, additions, and/or deletions are made a part of the Request for Proposals as fully and completely as if the same were included in the original.

A. The following data referenced in the original RFP has been revised or added. Every point in the RFP where this data appears is changed to the following:

a. Total enrollment: 17,098

b. Transported students: 12,500

c. User Data

i. Bus Drivers - 200

ii. School-Based Staff (field trip requests, etc.) - 150

iii. Transportation Staff (other than drivers) - 34 broken out as follows:

1. Administrators - 3

2. Administrative Assistants - 3

3. Fleet - 8

4. Routers - 4.5

5. Dispatch - 4.5 (one FTE is shared with Routers)

6. Trainers - 8

d. Fleet Data

i. Total Fleet Vehicles, all with GPS: 181 (Type A 28, Type B 43, Type C 54, Type D 53, Trucks 3)

ii. Vehicles anticipated to need tablets 162 (Type A 18, Type B 43, Type C 48, Type D 53)

iii. A full list of the fleet is included as Attachment 1 - List of Fleet

B. Anticipated RFP Schedule The anticipated RFP schedule is changed as detailed below. All references to the following dates are changed to reflect the following. This change supersedes any previous published schedule references.

Deadline for Proposal Submission November 21, 2025 Project Demonstration of Finalists December 19, 2025 Notice of Intent to Award December 23, 2025 Board Action to Award January 15, 2026 Commencement of Contract January 19, 2026

C. Implementation, Customer Support, and Training:

Add: 1.c. The district plans for a go-live for the 26/27 school year with testing during the summer.

Initial go-live is not anticipated to include real-time ridership, and implementation schedule and pricing should reflect real-time ridership as a later phase.

D. Proposal Contents:

i. In subsection 5, Cost Proposal, add “Please separate out any costs related to implementation of real-time ridership as it is not anticipated to be included in Phase 1 implementation.”

ii. In subsection 6. Required Attachments, remove the words “hard copy.” Proposers should ensure that no sections of their response are hidden or unreadable due to sizing of fields. The district will score based upon the information the evaluators can see in the provided electronic file/document.

End of changes, additions, and/or deletions to Request for Proposals.

(Attachment 1 - List of Fleet included after questions) 1

Questions

The following questions were received by the district in relation to this RFP. The information provided does not change the details of the Request for Proposal and is provided for informational purposes only.

Question 1:

Can you please provide a fleet list?

Answer 1: A list of the Transportation fleet, including general education buses, specialized transportation, vans, and additional vehicles, is included as an attachment to this Addendum.

Question 2:

How many garage locations do you have where buses will be to install the equipment on?

Answer 2:One location with multiple bays.

Question 3:

Can you please confirm that we only need to submit this proposal via email and that hard copies will not be required? Page 14 states “please include a hard copy of Attachment C and D.” but page 8 says only need to email our submittal

Answer 3: Physical hard copies are not required. See change to RFP language in this Addendum.

Question 4:

From the RFP: 200 staff and drivers, and 20 active system users across departments. Question: Are the 20 active system users going to receive tablet training?

Answer 4: These numbers have been revised. Please see RFP changes in this Addendum.

Question 5:

Currently, are there (GPS, cameras) installed on your vehicles? Do these devices need to be removed?

Answer 5: Yes, GPS and cameras are installed. These do not need to be removed as part of this process.

Question 6:

Could the purchasing department provide an asset list with VINs?

Answer 6: A list of the Transportation fleet, including general education buses, specialized transportation, vans, and additional vehicles, is included as an attachment to this Addendum.

Question 7:

On pages 1 and 3, the deadline for submission is November 12th, but on page 9 it's October 24th. Could you please clarify the correct deadline?

Answer 7: Please see RFP changes in this Addendum.

Question 8:

Page 14 indicates we need to include a hard copy of attachments C and D with our electronic files in our response. Since we plan to submit via email, could you please advise on the best way to include a hard copy?

Answer 8: Physical hard copies are not required. See change to RFP language in this Addendum.

Question 9:

Are student ID cards currently used? If so, could you provide the vendor and any technical details on the cards?

Answer 9: ID cards are not currently in place across the district. Locations with student ID cards do not utilize RFID cards.

Question 10:

Per pages 1 and 3 of the RFP, the proposal due date is specified as November 12, 2025, 2:00 PM Pacific Time. Per page 9 of the RFP, “The proposals must be received by the District by 2:00 on October 24, 2025.” Can the District please clarify the proposal submission deadline?

Answer 10: Please see RFP changes in this Addendum.

Question 11:

The RFP specifies that proposals shall be submitted via email. Per page 14 of the RFP, “Please include a hard copy of Attachment C and Attachment D in your Proposal response and also include the electronic files with your response. In the event of a discrepancy, hard copy will prevail.” Please confirm whether proposals, including Attachment C and Attachment D, should be submitted as a soft copy via email, or if the proposals, including Attachment C and Attachment D, should be submitted as a hard copy via mail. If proposals should be submitted as a hard copy, please confirm the delivery address for the shipment of any hard copy proposals, and if an electronic copy of the proposal should also be submitted via flash drive.

Answer 11: Please see RFP changes in this Addendum.

Questions 12:

Can the District please specify the anticipated contract end date and if there will be options for renewals?

Please provide the contract term with any additional optional years.

Answer 12: The district anticipates an initial 5-year agreement with options to renew but this is subject to negotiations.

Question 13:

When does the District expect the school transportation services routing and dispatch system to be fully operational? The RFP specifies that the commencement of the contract will occur on January 19, 2026.

Does the District expect training and full implementation to be completed by January 19, 2026? If not, please provide a date for the expected full implementation.

Answer 13: Please see RFP changes in this Addendum.

Question 14:

Per Attachment C, "Will your platform access or store student data? If yes, we will require a signed data privacy agreement. Our preference would be to use the Student Data Privacy Consortium Agreement.”

Should bidders submit a Data Privacy Agreement with our proposal or will a DPA be signed after an award of contract?

Answer 14: A signed DPA is not required with the proposal. If applicable, a DPA will be executed with the awarded vendor during contracting.

Question 15:

Please provide a breakdown of the District’s fleet by vehicle type and quantity per type (e.g. 25 Type A, 100 Type C, etc.)

Answer 15: See changes made to RFP in this Addendum. In addition, a list of the Transportation fleet, including general education buses, specialized transportation, vans, and additional vehicles, is included as an attachment to this Addendum.

Question 16:

Will bids be open publicly? If so, what information will be provided? Can we attend in-person or virtually?

Answer 16: The district does not conduct public openings for requests for proposals. A list of proposers shall be available via the public records process after the response deadline.

Question 17:

What type(s) of hardware is the District interested in, and how much of each type is needed?

Answer 17:The District requires non-proprietary tablets or mobile data terminals for in-bus use that meet the listed specifications. Please see RFP changes in this Addendum for estimated tablet needs.

Question 18: Could the District please clarify which types of users will require training and approximately how many users of each type? For example: routers, dispatchers, drivers, IT staff, district administrators, district office staff, field trip staff, fleet maintenance personnel, attendants/monitors, etc.

Answer 18: Please see RFP changes in this Addendum.

Question 19:

How many Bus Drivers and Monitors will need training? If there is a large number of Bus Drivers and Monitors that requires training, will a train-the-trainer model be sufficient?

Answer 19: Please see RFP changes in this Addendum. The vendor should propose the details of their recommended training model. A train-the-trainer model may be sufficient for drivers and school-based staff.

Question 20:

Does the District have an estimated budget range or any pricing restrictions for the routing software and associated services?

Answer 20: The district desires to acquire the needed products and services at the best price possible.

Proposers are welcome to include pricing options if clearly identified as such (see Proposal Content, section 5 Cost Proposal, page 14 of RFP).

Question 21:

Regarding the Evaluation Criteria, is the weighting for pricing/costs based solely on Year 1 costs, or is it evaluated on the total cost over the full term?

Answer 21:The evaluation criterion Total Cost to the District considers the proposal that accomplishes the stated objectives at the lowest cost. The Cost Proposal section requests all initial costs and ongoing costs for the first 3 years, which will inform evaluation.

Question 22:

What routing solution is the district currently using?

Answer 22: The district uses Versatran software and has since prior to its acquisition by Tyler Technologies.

Question 23:

As part of this RFP request, is the district interested in a public website with school, eligibility, and stop information for parents/realtors?

Answer 23: See RFP System Requirements section, subsection “Student/Parent App.”

Question 24:

1. For your 200 vehicles, could the district please break down by route busses, spares, special needs vans, shuttles, etc. Are there additional non-metered assets that the district would like the fleet maintenance software to track? If so, how many?

Answer 24: A list of the Transportation fleet, including general education buses, specialized transportation, vans, and additional vehicles, is included as an attachment to this Addendum.

Question 25:

How many total students are enrolled?

Answer 25: Please see RFP changes in this Addendum.

Question 26:

Of your 17,000 students transported, how many are regular vs. special needs?

Answer 26: Please see RFP changes in this Addendum for correction of number of students transported.

There are a total of 124 bus routes (Special Needs Routes - 32, Van Routes (Special Needs) - 17, General Transportation Routes - 75.)

Question 27:

For home-to-school transportation, in which county(s) are you transporting students?

Answer 27:The district currently transports to Clackamas County, Washington County, Marion County, Polk County, Clark County, Skamania County, Multnomah County, and Columbia County

Question 28:

Does the district own and operate the school bus fleet or are private contractors used? If contracted, how many and what bus contractors are used? If contracted, will contractor personnel be required to use any of the software? If yes:

a. Will the contractors be responsible for performing route creation and maintenance? How many contractor employees will need training?

b. Will the district also perform route creation and data maintenance?

c. Will they need read-only access to the data, reporting and maps?

Answer 28: The district owns and operates its own fleet.

Question 29:

1. What is the desired date for full implementation/go live of the specified software systems, including all district, student, map, route, field trip and other required data?

2. How many users will require full access licenses and training for the routing software?

Answer 29: Please see RFP changes in this Addendum.

Question 30:

1. Is GPS hardware currently installed on district vehicles? If so,

a. What type of hardware is installed and who is the vendor? Is it all via Verizon?

b. Does the district intend to continue using its current GPS technology?

Answer 30: Verizon Xirgo Vehicle Trackers are currently installed on all vehicles. The district is open to continuing to use the equipment and provider under the new agreement.

Question 31:

If purchasing new GPS hardware:

a. How many vehicles would need GPS tracking?

b. Will the district require our teams to remove any existing devices? How many?

c. Are all vehicles located at one location for removal/installation purposes?

d. Can you provide a fleet list with VIN numbers, make, model, and fuel types included? (This allows for proper GPS pricing)

Answer 31: Please see RFP changes in this Addendum for GPS vehicle numbers and vehicle listing. All vehicles currently have Verizon Xirgo Vehicle Trackers and the district is open to continuing to use the equipment and provider under the new agreement. If a vendor proposed different GPS equipment, they would need to anticipate removing old equipment at install. All vehicles are parked in one location.

Question 32:

1. Does the district have any tablets currently installed on district vehicles? If so,

a. What type/model tablets are they and how many vehicles have them?

b. Is the district interested in upgrading or purchasing new tablets as part of this request? How many vehicles would you plan to equip with tablets?

c. Would you be looking for the vendor to install the tablets? Would any old tablets or hardware need to be removed by the vendor as well?

d. Would any be installed on 3rd party contractor vehicles? If so, does the district have a contract to allow them to do that?

Answer 32:

The district does not currently have tablets installed on vehicles. Installation would be done by the vendor.

The district does not have 3rd party contractor vehicles.

Question 33:

Does the district have a preferred cell carrier through a district contract?

Answer 33:

Any carrier with a state of Oregon cooperative contract is acceptable to the district.

Question 34:

1. How many vehicles would you plan to equip with RFID scanners?

2. How many students would be issued cards?

2b. Are RFID cards currently used?

3. How many total drivers, including substitute drivers, aides, etc. would need access to the in-vehicle tablet for student tracking purposes?

Answer 34:

Please see RFP changes in this Addendum for data requested. It is anticipated all vehicles transporting students would need scanners and all students would be issued cards at time of real-time ridership implementation. There are no RFID cards currently in use.

Question 35:

A. Is it the district’s intent that district staff will place the district's existing stops and build the district's existing bus runs in the system during the training process, or does the district expect the vendor will implement everything noted above?

a. If it is the district's intent that district staff will place the stops and build the runs, then the below questions can be disregarded.

b. If it is the district’s intent that the vendor will implement everything noted above, please answer the following questions:

1. Regarding the route structure for your bus runs, are you picking up K-12 all in one bus run (i.e., single tier)? Do you pick up high school students and drop them off, then pick up middle school students and drop off, and then elementary school (i.e., three tiers)?

2. What is the total number of individual runs/trips performed by all general education buses in the morning?

3. (Ex: If 15 vehicles do a High School / Middle School run, then 17 vehicles do an Elementary run, that is 32 AM runs/trips total.)

4. How many general education runs/trips in the afternoon?

5. Are the afternoon bus runs essentially a 'mirror' of the morning runs? (Same core stop locations? Buses generally run in the same area AM & PM?)

6. How many special needs runs operate in the morning? How many in the afternoon

Answer 35:

A. It is the District's expectation that the selected vendor will transfer as much existing routing data as possible into the new platform. District staff will then refine, modify, and build routes within the system as part of their training and ongoing operational learning.

1. The District operates a three-tier routing structure consisting of:

a. Elementary school

b. Middle schools

c. High Schools (including four additional elementary schools served on high school routes)

2. Buses also operate daytime shuttles between the Career/Technical school and the five neighborhood high schools.

3. Between 6:00 a.m. and 9:30 a.m., approximately 224 runs are performed by general transportation (GT) buses, primarily for home-to-school service, with additional shuttle operations.

a. These figures do not include shuffle operations

4. Between 2:00 p.m. and 4:30 p.m., approximately 221 runs are performed by GT buses, primarily for school-to-home service, with additional shuttle operations.

5. In most cases, afternoon routes mirror morning routes to maintain consistency and ensure students ride the same bus both ways.

a. When necessary, routes are adjusted to avoid crossing students paths or to improve operational efficiency.

6. For Special Education (SPED) transportation:

a. 17 of the 49 SPED routes are operated using Type 10 vehicles (vans or secured cars)

b. There are approximately 109 a.m. runs and 108 p.m. runs, excluding midday shuttles and after-school activity runs.

Question 36:

In the introduction to the RFP it is stated: The selected vendor will support the transition from the department’s current system suite and Verizon Reveal GPS system. Can the District describe the current system suite and provide details about Verizon Reveal GPS to inform data migration planning?

Answer 36: The district currently uses Versatrans for all routing and planning, and fleet maintenance tracking. See questions 30 and 31 for additional information on GPS.

Question 37:

The RFP states that documents are available from OregonBuys and will not be mailed. However, the OregonBuys website does not appear to list this RFP. How will respondents be notified of addenda and responses to questions?

Answer 37:

The district utilities OregonBuys for all official documents related to the RFP. Please contact the Issuing Officer if you have difficulty locating the posting.

Question 38:

Can the proposal submittal deadline be extended by one week past November 12, 2025 due to the potential impact of responses on pricing and scope?

Answer 38: Please see RFP changes in this Addendum.

Question 39:

The RFP introduction references a transition from the department’s “current system suite and Verizon Reveal GPS system.” Could the District confirm which routing and/or dispatch software platforms are currently used alongside Verizon Reveal? Is the incumbent vendor eligible to submit a proposal under this

RFP

Answer 39: The district currently uses Versatrans for all routing and planning, and fleet maintenance tracking. See questions 30 and 31 for additional information on GPS. There is no vendor that has been declared ineligible to submit a proposal.

Question 40:

What was the total contract value and term length of the most recent routing and dispatch system agreement? Were any performance evaluations or post-contract assessments conducted at the conclusion of that term, and are summaries available?

Answer 40: The district purchased the current software from a predecessor company many years ago.

The original implementation contract is no longer accessible.

Question 41:

The anticipated contract commencement date is January 19, 2026. Can the District confirm the target “go-live” or full implementation completion date?

Answer 41: Please see RFP changes in this Addendum.

Question 42:

What is the intended initial contract term and any renewal options?

Answer 42: The district anticipates an initial 5-year agreement with options to renew but this is subject to negotiations.

Question 43:

For the Mobile Data Terminals (MDTs) described in the RFP, does the District plan to procure hardware separately, or should proposers include compatible hardware options in their pricing proposals?

Answer 43: Proposals should include all items needed to implement the proposed system, including hardware. Options, in addition to proposed solution - such as upgraded hardware, can be proposed and priced separately but must be clearly marked.

Question 44:

The RFP references Oregon’s Certification Office for Business Inclusion and Diversity (COBID). Does the District offer any preference, scoring credit, or documentation requirements for COBID-certified (Minority-, Women-, Emerging Small-, or Veteran-owned) firms for this RFP?

Answer 44: The RFP encourages COBID-certified participation, but provides there is no requirement or scoring preference. Vendors are encouraged to provide COBID certification documentation with their proposal if applicable.

Question 45:

Will all vendor-submitted questions and the District’s responses be published publicly as an addendum prior to the proposal submission deadline?

Answer 45: Yes. The District will publish all questions and responses as an official addendum prior to the proposal submission deadline via OregonBuys

Single Point of Contact Gustavo Chávez Senior Purchasing Specialist Chavezcardenasg@nclack.k12.or.us mailto:Chavezcardenasg@nclack.k12.or.us

YEAR BODY

MAKE/MODEL ENGINE LICENSE NO. SERIAL NO. Fuel Type PASSEN. COUNT Type A, B, C, DColumn

1 2019 BB T3RE4006 ISL 300 E277036 1BABNB6A8KF353232 Diesel 78 1 Type D

2 2012 BB D3FE4004S ISB 6.7L E 251394 1BABNCPA8CF287657 Diesel 84 2 Type D

4 2018 THOMAS C2 ISB 260 E 276074 4UZABRFCXJCJP8014 Diesel 81 3 Type C

5 2018 THOMAS C2 ISB 260 E 276070 4UZABRFC1JCJP8015 Diesel 81 4 Type C

7 2012 BB D3FE4004S ISB 6.7L E 251393 1BABNCPAXCF287658 Diesel 84 5 Type D

8 2012 BB D3FE4004S ISB 6.7L E 251395 1BABNCPA1CF287659 Diesel 84 6 Type D

9 2008 BLUE BIRD C 6.7 E 240196 1BABNCPA98F252732 Diesel 84 7 Type D

14 2012 BB D3FE4004S ISB 6.7L E 251396 1BABNCPA8CF287660 Diesel 84 8 Type D

15 2019 THOMAS ISB 260 E277015 4UZABRFC6KCKL5682 Diesel 81 9 Type C

16 2012 BB D3FE4004S ISB 6.7L E 251398 1BABNCPAXCF287661 Diesel 84 10 Type D

17 2019 THOMAS C2 ISB 260 E277034 4UZABRFC8KCKL5683 Diesel 81 11 Type C

21 2019 THOMAS C2 ISB 260 E277035 4UZABRFCXKCKL5684 Diesel 81 12 Type C

22 2019 THOMAS C2 ISB 260 E277037 4UZABRFC1HKCKL5685 Diesel 81 13 Type C

24 2012 BB D3FE4004S ISB 6.7L E 251399 1BABNCPA3CF287663 Diesel 84 14 Type D

25 2012 BB D3FE4004S ISB 6.7L E 251400 1BABNCPA5CF287664 Diesel 84 15 Type D

26 2019 THOMAS C2 ISB 260 E277016 4UZABRFC9KCKL5692 Diesel 66 16 Type C

29 2012 BB D3FE4004S ISB 6.7L E 251401 1BABNCPA7CF287665 Diesel 84 17 Type D

40 2019 BB T3RE4006S ISL 300 E277007 1BABNB6AXKF353233 Diesel 78 18 Type D

43 2012 BB D3FE4004S ISB 6.7L E 251402 1BABNCPA9CF287666 Diesel 84 19 Type D

59 2008 BLUE BIRD C 6.7 E 240198 1BABNCPA28F252734 Diesel 84 20 Type D

60 2008 BLUE BIRD C 6.7 E 240199 1BABNCPA48F252735 Diesel 84 21 Type D

61 2008 BLUE BIRD C 6.7 E 240200 1BABNCPA68F252736 Diesel 84 22 Type D

62 2008 BLUE BIRD C 6.7 E 243766 1BABNCPA88F252737 Diesel 84 23 Type D

63 2008 BLUE BIRD C 6.7 E 243772 1BABNCPAX8F252738 Diesel 84 24 Type D

65 2018 THOMAS C2 ISB 260 E 276071 4UZABRFC3JCJP8016 Diesel 81 25 Type C

General Transportation Buses

Attachment 1-1 9

Attachment No. 1-List of Fleet

66 2018 THOMAS C2 ISB 260 E 276072 4UZABRFC5JCJP8017 Diesel 81 26 Type C

67 2018 THOMAS C2 ISB 260 E 276073 4UZABRFC7JCJP8018 Diesel 81 27 Type C

68 2018 THOMAS C2 ISB 260 E 276081 4UZABRFC9JCJP8019 Diesel 81 28 Type C

69 2018 THOMAS C2 ISB 260 E 276075 4UZABRFC5JCJP8020 Diesel 81 29 Type C

70 2018 THOMAS C2 ISB 260 E 276082 4UZABRFC7JCJP8021 Diesel 81 30 Type C

71 2008 BLUE BIRD C 6.7 E 243768 1BABNCPA88F252740 Diesel 84 31 Type D

72 2008 BLUE BIRD C 6.7 E 243770 1BABNCPAX8F252741 Diesel 84 32 Type D

75 2008 BLUE BIRD C 6.7 E 244060 1BABNCPA08F253347 Diesel 84 33 Type D

79 2008 BLUE BIRD C 6.7 E 244062 1BABNCPA28F253351 Diesel 84 34 Type D

81 2008 BLUE BIRD C 6.7 E 244064 1BABNCPA68F253353 Diesel 84 35 Type D

93 2016 BB AA T3FE4004 ISB 13 E 265828 1BABNCPAXGF320423 Diesel 84 36 Type D

94 2016 BB AA T3FE4004 ISB 13 E 265829 1BABNCPA1GF320424 Diesel 84 37 Type D

95 2016 BB AA T3FE4004 ISB 13 E 265830 1BABNCPA3GF320425 Diesel 84 38 Type D

96 2012 BB D3FE4004S ISB 6.7L E 251403 1BABNCPA0CF287667 Diesel 84 39 Type D

97 2016 BB AA T3FE4004 ISB 13 E 265831 1BABNCPA5GF320426 Diesel 84 40 Type D

98 2016 BB AA T3FE4004 ISB 13 E 265833 1BABNCPA7GF320427 Diesel 84 41 Type D

99 2016 BB AA T3FE4004 ISB 13 E 265834 1BABNCPA9GF320428 Diesel 84 42 Type D

100 2016 BB AA T3FE4004 ISB 13 E 265832 1BABNCPA0GF320429 Diesel 84 43 Type D

101 2016 BB AA T3FE4004 ISB 13 E 265835 1BABNCPA7GF320430 Diesel 84 44 Type D

102 2017 BB AA T3FE4004 ISB 13 E 267795 1BABNCPA2HF332647 Diesel 84 45 Type D

103 2017 BB AA T3FE4004 ISB 13 E 267796 1BABNCPA4HF332648 Diesel 84 46 Type D

104 2017 BB AA T3FE4004 ISB 13 E 267797 1BABNCPA6HF332649 Diesel 84 47 Type D

105 2017 BB AA T3FE4004 ISB 13 E 267798 1BABNCPA2HF332650 Diesel 84 48 Type D

119 2012 BB D3FE4004S ISB 6.7L E 251404 1BABNCPA2CF287668 Diesel 84 49 Type D

122 2012 BB D3FE4004S ISB 6.7L E 251405 1BABNCPA4CF287669 Diesel 84 50 Type D

Attachment 1-2 10

123 2012 BB D3FE4004S ISB 6.7L E 251406 1BABNCPA0CF287670 Diesel 84 51 Type D

124 2013 BB AA D3RE4006 ISB 6.7L E 256315 1BABNBPAXDF294041 Diesel 84 52 Type D

125 2013 BB AA D3RE4006 ISB 6.7L E 256316 1BABNBPA1DF294042 Diesel 84 53 Type D

126 2013 BB AA D3RE4006 ISB 6.7L E 256317 1BABNBPA3DF294043 Diesel 84 54 Type D

127 2013 BB AA D3RE4006 ISB 6.7L E 256314 1BABNBPA5DF294044 Diesel 84 55 Type D

128 2013 BB AA D3RE4006 ISB 6.7L E 256309 1BABNBPA7DF294045 Diesel 84 56 Type D

129 2013 BB AA D3RE4006 ISB 6.7L E 256310 1BABNBPA9DF294046 Diesel 84 57 Type D

130 2013 BB AA D3RE4006 ISC 8.3L E 256311 1BABNBXA0DF294047 Diesel 84 58 Type D

131 2013 BB AA D3RE4006 ISC 8.3L E 256313 1BABNBXA2DF294048 Diesel 84 59 Type D

132 2013 BB AA D3RE4006 ISC 8.3L E 256312 1BABNBXA4DF294049 Diesel 84 60 Type D

133 2015 THOMAS BUS ISB 6.7L E 264367 1T7YT4E23F1287061 Diesel 84 61 Type D

134 2015 THOMAS BUS ISB 6.7L E 264375 1T7YT4E25F1287062 Diesel 84 62 Type D

135 2015 THOMAS BUS ISB 6.7L E 264368 1T7YT4E27F1287063 Diesel 84 63 Type D

136 2015 THOMAS BUS ISB 6.7L E 264374 1T7YT4E29F1287064 Diesel 84 64 Type D

137 2015 THOMAS BUS ISB 6.7L E 264369 1T7YT4E22F1287066 Diesel 84 65 Type D

138 2015 THOMAS BUS ISB 6.7L E 264370 1T7YT4E24F1287067 Diesel 84 66 Type D

139 2019 THOMAS C2 ISB 260 E 281527 4UZABRFC9LCLX9678 Diesel 81 67 Type C

140 2019 THOMAS C2 ISB 260 E 281536 4UZABRFC0LCLX9679 Diesel 81 68 Type C

141 2019 THOMAS C2 ISB 260 E 281528 4UZABRFC7LCLX9680 Diesel 81 69 Type C

142 2019 THOMAS C2 ISB 260 E 281529 4UZABRFC9LCLX9681 Diesel 81 70 Type C

143 2019 THOMAS C2 ISB 260 E 281530 4UZABRFC0LCLX9682 Diesel 81 71 Type C

144 2019 THOMAS C2 ISB 260 E 281537 4UZABRFC2LCLX9683 Diesel 81 72 Type C

145 2019 THOMAS C2 ISB 260 E 283103 4UZABRFC4LCLX9684 Diesel 81 73 Type C

146 2019 THOMAS C2 ISB 260 E 283109 4UZABRFC6LCLX9685 Diesel 81 74 Type C

147 2019 THOMAS C2 ISB 260 E 281539 4UZABRFC8LCLX9686 Diesel 81 75 Type C

Attachment 1-3 11

148 2019 THOMAS C2 ISB 260 E 281547 4UZABRFCXLCLX9687 Diesel 81 76 Type C

149 2019 THOMAS C2 ISB 260 E 281548 4UZABRFC1LCLX9688 Diesel 81 77 Type C

150 2019 THOMAS C2 ISB 260 E 281549 4UZABRFC3LCLX9689 Diesel 81 78 Type C

151 2019 THOMAS C2 ISB 260 E 281550 4UZABRFCXLCLX9690 Diesel 81 79 Type C

152 2019 THOMAS C2 ISB 260 E 283106 4UZABRFC1LCLX9691 Diesel 81 80 Type C

153 2019 THOMAS C2 ISB 260 E 281538 4UZABRFC8LCLY0157 Diesel 66 81 Type C

154 2025 THOMAS C2 CUM 6.7 E285044 4UZABRFC6SCUM5926 Diesel 78 82 Type C

155 2025 THOMAS C2 CUM 6.7 E285039 4UZABRFC8SCUM5927 Diesel 78 83 Type C

156 2025 THOMAS C2 CUM 6.7 E285043 4UZABRFCXSCUM5928 Diesel 78 84 Type C

157 2025 THOMAS C2 CUM 6.7 E285037 4UZABRFC1SCUM5929 Diesel 78 85 Type C

158 2025 THOMAS C2 CUM 6.7 E285041 4UZABRFC8SCUM5930 Diesel 78 86 Type C

159 2025 THOMAS C2 CUM 6.7 E285038 4UZABRFCXSCUM5931 Diesel 78 87 Type C

160 2025 THOMAS C2 CUM 6.7 E285354 4UZABRFC1SCUM5932 Diesel 78 88 Type C

161 2025 THOMAS C2 CUM 6.7 E285355 4UZABRFC3SCUM5933 Diesel 78 89 Type C

162 2025 THOMAS C2 CUM 6.7 E285356 4UZABRFC5SCUM5934 Diesel 78 90 Type C

163 2025 THOMAS C2 CUM 6.7 E285040 4UZABRFC7SCUM5935 Diesel 78 91 Type C

164 2024 BB CV3310S FORD 7.3L E285046 1BAKGCHA5RF805368 Propane 77 92 Type C

165 2024 BB CV3310S FORD 7.3L E285036 1BAKGCHA7RF805369 Propane 77 93 Type C

166 2024 BB CV3310S FORD 7.3L E285034 1BAKGCHA3RF805370 Propane 77 94 Type C

167 2024 BB CV3310S FORD 7.3L E285033 1BAKGCHA5RF805371 Propane 77 95 Type C

168 2024 BB CV3310S FORD 7.3L E285049 1BAKGCHA7RF805372 Propane 77 96 Type C

169 2024 BB CV3310S FORD 7.3L E285045 1BAKGCHA9RF805373 Propane 77 97 Type C

170 2024 BB CV3310S FORD 7.3L E285042 1BAKGCHA0RF805374 Propane 77 98 Type C

171 2024 BB CV3310S FORD 7.3L E285050 1BAKGCHA2RF805375 Propane 77 99 Type C

172 2024 BB CV3310S FORD 7.3L E285035 1BAKGCHA4RF805376 Propane 77 100 Type C

Attachment 1-4 12

173 2024 BB CV3310S FORD 7.3L E285351 1BAKGCHA6RF805377 Propane 77 101 Type C

Attachment 1-5 13

BUS # YEAR ENGINE LICENSE NO. SERIAL NO. Fuel Type PASSEN. COUNT Type A, B, C, DBODY MAKE/MO

500 2017 BB VISION ISV 5.0L E267799 1BAKBCRA2HF332654 Diesel 30 1 Type B

501 2017 BB VISION ISV 5.0L E267800 1BAKBCRA6HF332655 Diesel 24 + 1 2 Type B

502 2017 BB VISION ISV 5.0L E270751 1BAKBCRA4HF332656 Diesel 24 + 1 3 Type B

505 2017 BB VISION ISB 13 E270752 1BAKBCPA2HF332737 Diesel 28 4 Type B

506 2017 BB VISION ISB 13 E270753 1BAKBCPA4HF332738 Diesel 28 5 Type B

507 2019 ISB 220 E277008 4UZABRFC3KCKL5686 Diesel 24+1 6 Type B

508 2019 ISB 220 E277018 4UZABRFC5KCKL5687 Diesel 24+1 7 Type B

509 2019 ISB 220 E277017 4UZABRFC7KCKL5688 Diesel 24+1 8 Type B

510 2019 ISB 220 E277033 4UZABRFC9KCKL5689 Diesel 24 + 1 9 Type B

511 2019 ISB 220 E277009 4UZABRFC5KCKL5690 Diesel 24+1 10 Type B

512 2019 ISB 220 E277032 4UZABRFC7KCKL5691 Diesel 24 + 1 11 Type B

550 2013 BB VISION ISB-10 E256303 1BAKBCPA9DF294479 Diesel 24+1 12 Type B

551 2013 BB VISION ISB-10 E256304 1BAKBCPA5DF294480 Diesel 24+1 13 Type B

552 2013 BB VISION ISB-10 E256306 1BAKBCPA7DF294481 Diesel 24+1 14 Type B

553 2013 BB VISION ISB-10 E256305 1BAKBCPA9DF294482 Diesel 24+1 15 Type B

554 2013 BB VISION ISB-10 E256307 1BAKBCPA0DF294483 Diesel 24+1 16 Type B

555 2013 BB VISION ISB-10 E256308 1BAKBCPA2DF294484 Diesel 24+1 17 Type B

556 2015 DURAMAX 6.6L E264377 1GB6G5BL9E1206868 Diesel 18+1 18 Type B

557 2015 DURAMAX 6.6L E264378 1GB6G5BLXE1205535 Diesel 18+1 19 Type B

558 2015 DURAMAX 6.6L E264379 1GB6G5BL8E1207073 Diesel 18+1 20 Type B

559 2015 DURAMAX 6.6L E264380 1GB6G5BLXE1205471 Diesel 18+1 21 Type B

560 2015 DURAMAX 6.6L E264381 1GB6G5BL3E1207515 Diesel 18+1 22 Type B

561 2015 DURAMAX 6.6L E264382 1GB6G5BL5E1207404 Diesel 24+1 23 Type B

562 2018 ISB220 E 276083 4UZABRFC8JCJP8027 Diesel 24+1 24 Type B

563 2018 ISB220 E 276076 4UZABRFCXJCJP8028 Diesel 24+1 25 Type B

564 2018 ISB220 E 276077 4UZABRFC1JCJP8029 Diesel 24+1 26 Type B

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

CHEV MINOTOU

CHEV MINOTOU

CHEV MINOTOU

CHEV MINOTOU

CHEV MINOTOU

CHEV MINOTOU

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

Special Needs Buses

Attachment 1-6 14

BUS # YEAR ENGINE LICENSE NO. SERIAL NO. Fuel Type PASSEN. COUNT Type A, B, C, DBODY MAKE/MO

565 2018 ISB220 E 276084 4UZABRFC8JCJP8030 Diesel 24+1 27 Type B

566 2018 ISB220 E 276078 4UZABRFCXJCJP8031 Diesel 24+1 28 Type B

567 2018 ISB220 E 276085 4UZABRFC1JCJP8032 Diesel 24+1 29 Type B

568 2018 ISB220 E 276079 4UZABRFC3JCJP8033 Diesel 24+1 30 Type B

569 2018 ISB220 E 276080 4UZABRFC5JCJP8034 Diesel 24+1 31 Type B

570 2018 ISB220 E 276086 4UZABRFC7JCJP8035 Diesel 24+1 32 Type B

571 2018 ISB220 E 276087 4UZABRFC9JCJP8036 Diesel 24+1 33 Type B

572 2019 ISB220 E 283110 4UZABRFC5LCLY0147 Diesel 24+1 34 Type B

573 2019 ISB220 E 281526 4UZABRFC7LCLY0148 Diesel 24+1 35 Type B

574 2019 ISB220 E 283105 4UZABRFC9LCLY0149 Diesel 24+1 36 Type B

575 2019 ISB220 E 283111 4UZABRFC5LCLY0150 Diesel 24+1 37 Type B

576 2019 ISB220 E 283104 4UZABRFC7LCLY0151 Diesel 24+1 38 Type B

577 2019 ISB220 E 283101 4UZABRFC9LCLY0152 Diesel 24+1 39 Type B

578 2019 ISB220 E 283102 4UZABRFC0LCLY0153 Diesel 24+1 40 Type B

579 2019 ISB220 E 283112 4UZABRFC2LCLY0154 Diesel 24+1 41 Type B

580 2019 ISB220 E 283107 4UZABRFC4LCLY0155 Diesel 24+1 42 Type B

581 2019 ISB220 E 283113 4UZABRFC6LCLY0156 Diesel 24+1 43 Type B

600 2026 1BAKBCHA2TF819878 Propane 24+1 44 Type B

601 2026 1BAKBCHA4TF819879 Propane 24+1 45 Type B

602 2026 1BAKBCHA0TF819880 Propane 24+1 46 Type B

603 2026 1BAKBCHA2TF819881 Propane 24+1 47 Type B

604 2026 1BAKBCHA4TF819882 Propane 24+1 48 Type B

605 2026 1BAKBCHA6TF819883 Propane 24+1 49 Type B

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

THOMAS-C2 22

Blue Bird Propa

Blue Bird Propa

Blue Bird Propa

Blue Bird Propa

Blue Bird Propa

Blue Bird Propa

New Buses

Attachment 1-7 15

VEHICLE # YEAR

BODY

MAKE/MODE

L

ENGINE LICENSE NO. SERIAL NO. Fuel Type PASSEN. COUNT Type A, B, C, D

D-45 2017 Ford Explorer E285371 1FM5K8AR6HGD66863 Gas 4 1 Type A

D-46 2015 Ford Explorer E28378 Gas 4 2 Type A

V-1 2017 Toyota Sienna Gas 6 3 Type A

V-2 2017 Toyota Sienna E276054 Gas 6 4 Type A

V-4 2017 Toyota Sienna E276056 5TDJZ3DC9HS179776 Gas 6 5 Type A

V-5 2017 Toyota Sienna E276057 5TDJZ3DC7HS179906 Gas 6 6 Type A

V-6 2017 Toyota Sienna E276058 5TDJZ3DC2HS180056 Gas 6 7 Type A

V-7 2018 Toyota Sienna E277029 5TDJZ3DC5JS206395 Gas 6 8 Type A

V-8 2018 Toyota Sienna E277028 5TDJZ3DC3 JS207173 Gas 6 9 Type A

V-9 2018 Toyota Sienna E277027 5TDJZ3DC3JS203981 Gas 6 10 Type A

V-10 2018 Toyota Sienna E277026 5TDJZ3DC2JS205799 Gas 6 11 Type A

V-11 2018 Toyota Sienna E277025 5TDJZ3DC6JS206535 Gas 6 12 Type A

V-12 2018 Toyota Sienna E277024 5TDJZ3DC8JS206908 Gas 6 13 Type A

V-13 2024 Bluebird (Ford) E285372 1FDDR7PG8PKB82690 Gas 9 14 Type A

V-14 2024 Bluebird (Ford) E285363 1FDDR7PG9PKB82276 Gas 9 15 Type A

V-15 2024 Bluebird (Ford) E285362 1FDDR7PG4PKB83111 Gas 9 16 Type A

V-16 2024 Bluebird (Ford) E285364 1FDDR7PG7PKB83216 Gas 9 17 Type A

V-17 2024 Bluebird (Ford) E285375 1FDDR7PG7PKB83023 Gas 9 18 Type A

1FM5K8AR5FGA35544

E276053 5TDJZ3DC7HS178898

5TDJZ3DC3HS179465

Type 10 Vehicles

Attachment 1-8 16

VEHICLE # YEAR BODY MAKE/MODEL ENGINE LICENSE NO. SERIAL NO. Fuel Type PASSEN. COUNT Type A, B, C, D

D-25 2017 CHEV GIRARDIN GM 6.0L E274435 1GB3GRBG1H1181689 Gas 14

D-26 2017 CHEV GIRARDIN GM 6.0L E274436 1GB3GRBG3H1185310 Gas 14

D-30 1999 FORD GIRARD 7.3L V8 E 210338 1FDSE37F2XHA61718 Diesel 14

D-32 2001 FORD E350 MB11 7.3L V8 E 220527 1FDSE35F71HB06761 Diesel 14

D-33 2001 FORD E350 MB11 7.3L V8 E 220526 1FDSE35F91HB06759 Diesel 14

D-34 2001 FORD E350 MB11 7.3L V8 E 220525 1FDSE35F11HB06755 Diesel 14

D-35 2001 FORD E350 MB11 7.3L V8 E 220524 1FDSE35F71HB06758 Diesel 14

D-36 2001 FORD E350 MB11 7.3L V8 E 220523 1FDSE35F31HB06756 Diesel 14

D-37 2001 FORD E350 MB11 7.3L V8 E 220522 1FDSE35F51HB06760 Diesel 14

D-38 2001 FORD E350 MB11 7.3L V8 E 220521 1FDSE35F51HB06757 Diesel 14

T-1 2017 GMC 3500 4WD CREW CAB E 276100 1GD42VCY2HF247213 Diesel

T-3 2007 GMC 2500 HD 4WD 6.5 E 237088 1GDJC34F6NE536677 Diesel

T-4 2018 2018 GMC 2500 HD 4WD 6.0L V8 E 277014 1GT02REG3JZ206866 Gas

1 Type A

2 Type A

3 Type A

4 Type A

5 Type A

6 Type A

7 Type A

8 Type A

9 Type A

10 Type A

11 Shop Truck

12 Shop Truck

13 Shop Truck

DURAMAX 6.7L

Type 20 Vehicles

Attachment 1-9 17

Gustavo Chávez Highlight