Jump to content

Silly Tilley

  • Content Count

  • Joined

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @mikenoza Regarding the XDE60 buses, they are currently in production at New Flyer and delivery should begin anytime soon, likely sometime within the next few weeks. They will have the BAE HybriDrive like all the existing hybrids. They will also have the New Flyer Smart Rider system. However there is a good chance they won't hit the road until 2021, as any incidental things such as training, preparation of new buses etc. has been deferred due to staffing and budget pressures. As for the comments about the 53 being extended to Cooksville, the original MiWay Five plan did have the 53 terminating there however it was deferred due to the construction at the station. I do feel it will be extended there eventually as the current on street loop is not very sufficient from a operations perspective. Regardless of the routing, the round trip time (RTT) will increase so either the frequency gets reduced with less buses or an additional bus gets added. The current 35 minute midday and evening service (70 min RTT, 2 buses) can probably be adjusted to 40 minutes (80 min RTT) without adding any resources as ridership was light even before the pandemic. If peak ridership eventually returns to pre-pandemic levels then a extra bus would likely be required to avoid the existing 20-22 minute frequency being reduced (80-88 min RTT, 4 buses).
  2. Thanks to Kevin L for taking the time to create those pages so we can see what it would look like. Regarding the title, If the manufacturer has used one serial sequence for all models, which New Flyer and most others do, then I think it's better to just title the pages "New Flyer Industries 'L VINs'" as an example. While almost all the manufacturers will be able to be switched to the proposed format, Gillig is a outlier due to the way they assign their serials. While the 35' and 40' low floor models use the same serial sequences regardless of styling or propulsion, they do not necessarily assign serials in order, and go back and use skipped serials even years later. This means a higher serial does not necessarily indicate a newer built bus and it also means that model years are all over the place in the serial sequence. Given this, it may be best to have the Gillig pages done as serial number ranges rather than model year, such as in increments of 10,000. Additionally, the 29' low floor versions use a completely separate serial sequence than the 35' and 40' models and would require their own separate pages. Some further discussion on how to tackle Gillig will probably be necessary before any changes implemented. Perhaps some of the people more experience with Gillig's production lists can chime in. I understand what you're getting at because I do use the VIN pages occasionally for the same reason. That said, It would still be possible with the page format that has been proposed, as the table would be sortable by model (clicking the arrows in the header of the 'model' column) which would make it easy to then see who operates a specific model. As for the length of the page, given that sequential VINs will now be combined (1 row per order) It still wouldn't be as long as some of the existing pages which have hundreds and sometimes even thousands of individual rows on one page.
  3. The recent tender for buses for Simcoe LINX and Midland Transit was awarded to Grande West for 30ft Vicinity buses. Simcoe will receive 3 buses and Midland 1 bus. According to a council report, route 6 Midland-Orillia is still planned to start later this fall but this is based on recieving the rest of the buses from Alexander Dennis, which was delayed due to the pandemic.
  4. There is a report on next week's council agenda to purchase 4 30ft Vicinity diesel buses from Grande West. These 4 buses will be used on route 27 beginning in fall 2021. Grande West and City View (Eldorado) were the only 2 bidders. While pricing was requested for hybrid and electric buses, there was only one bidder for hybrid buses and neither submitted a bid for electric buses.
  5. Thanks for finding that document and confirming the second hand Gillig Low Floors. I've updated the Rogue Valley Transportation District wiki page to reflect this info.
  6. The 90 is being retained as is, MiWay is no longer planning on cancelling the route. It appears this decisions was made in very late 2019/early 2020 based on when updates to the MiWay Five proposed map were made. It's a bit tricky to find with the website redesign but MiWay Five webpage is still up on the MiWay site. After a 4 month absence, MiWay 0341 re-emerged last week with a fully redone exterior, complete with a nice shiny paintjob. It looks really good and I've attached a few photos. They didn't skimp - all 4 sides got repainted, even the doors got fully repainted and new wheel fenders on all wheels. The only thing that wasn't touched was a access panel on the roof that surrounds the exhaust, probably took it off when they started and just put it right back on afterwards. For those of you that follow MiWay you'll know that full repaints like this are rare, as MiWay does their major maintenance work on a 'as needed' basis, not scheduled intervals, and that includes body work. So usually with MiWay you will only see specific sections of the bus repainted if it's been worked on, or only one side of the bus repainted if it's the side that had the body work etc. Even with just body panel replacement often times it is just done in specific sections (past the rear doors, below windows only etc.) As for why 0341 has been repainted at this stage, it has everything to do with MiWay doing their major maintenance work on as needed basis. I wouldn't read anything into it as at this point, the city still plans to replace all the D40LFs in 2021. For example, 0319 received major body work in April-May 2019 which included both driver and passenger sides of the bus being fully repainted, but was retired 2-3 months later after suffering a major mechanical issue - and then there was all the Orion Vs that received major body work and repaints only to retire a year later.
  7. Bradford has a tender out for 3 transit vehicles, I'm assuming to replace the existing 2014 cutaway buses. The specs aren't very detailed but based on price it will probably be mor cutaways. Bradford West Gwillimbury - Supply and Delivery of Three (3) Transit Vehicles
  8. With many municipalities beginning to receive confirmation if ICIP funding applied for in 2019, it's bus purchasing time again. For Sault Ste Marie, they currently have tenders out for 6 40ft buses and 4 35ft buses. The tenders close on September 22. Sault Ste Marie Tenders and Proposals
  9. Regarding your points about the possibility of listing VIN ranges on the VIN page: Grouping together VINs/serials is common practice in production lists and seems to be the accepted standard. I don't see how it could be hard to comprehend where VINs fit into a sequence. The check digit in a VIN has nothing to do with sequencing or other component of the VIN, it's simply a validation for the VIN. I would suspect very few if any people are looking for check digits specifically. Even with grouped VINs as I proposed the full VINs will always exist on the wiki. The fleet pages with the full VINs would still be linked to from the VIN pages, should anyone want to view the full VINs including check digits for each bus. The starting portions of VINs consist of things like manufacturer identity and equipment information (engine, length, brakes, etc.). This is standard and I am unable to find any manufacturers who use different characters in the beginning portion of a VIN for buses of the same spec built in the same order. If there are cases, then it is probably warranted to have it's own separate entry on the VIN page regardless of format, much like 30/35/40' buses and diesel/CNG/hybrid buses are separated by color currently regardless of whether they were built in sequence in the same order. There are some cases where the end portion of a VIN may have been different for buses in the same order and same spec, such as early Orion I and their "counting numbers" or "line sequence numbers" and in this case, it is probably justified to leave those VIN pages as is. Even with copy and paste and any other rhythm I still find the current setup a incredibly time consuming process. Further to my suggestion #3 which was to have VIN pages set up by manufacturer sequence rather than each individual model, I'm glad there's support for this but it may be the trickiest to accomplish out of the 3 suggestions. Grouping the VINs would make this easier as the pages wouldn't be so long and it would be much easier to implement. Giving some examples of how this would have to be implemented: All New Flyer models would go on the same page, but would probably have to be separated by model year to prevent the page from getting so long. For example New Flyer Inudustries 'A VINs', New Flyer Industries 'B VINs' and so on. Orion pages could remain with the same set up as they are already based on serial sequence and not specific models Gillig low floor pages would probably have to be split by serial sequence as there are a few they use for the 35/40 ft buses and the 29ft buses have their own sequence. You can't split Gilligs by year due to the way they assign their serials. All Nova models would go on the same page but split by model year like the others. While some of the above can be easily accomplished with copy/paste and even easier if we just group VINs, There is the issue of the links from fleet pages to VIN pages, unless a redirect will work or a simple copy the contents to word, then find/replace all the links would also work.
  10. I would have to look through my photos but Columbus 1223 was apparently the last Orion to roll off the line. They had a nice little celebration with balloons, banner etc on the bus before it rolled out. It could be that the VINs and build numbers weren't in sequence and Columbus 1223 had a higher build number than Vermont 107. Build numbers are a separate 5 digit number from the VIN and is what production would go by. If Columbus 1223 had a higher build number then it would have been the last regardless of VIN. Of course, some people do prefer to go by the VIN so for some, Vermont 107 would be the last.
  11. After spending quite a bit of time lately editing various wiki pages, which includes updating the VIN pages, I feel it is time to have a discussion about the way they are formatted with a view to making it easier for editors. It has been ten years since we first started the 'special project' to document VINs so I think a discussion is warranted on several points. To be clear, my points are regarding the VIN pages and not the individual fleet series pages. Also, none of my comments should be interpreted as criticism of the status quo or any previous efforts but rather looking at ways to improve things and make wiki editing easier. 1) Currently, the VIN pages are set up that each VIN must be entered individually. This is incredibly time consuming, especially for large orders even with copy and pasting. I find I am spending more time putting VINs on the VIN pages than actually editing and improving wiki pages elsewhere, and can honestly say that adding VINs to the VIN pages is my least favorite part of wiki editing. I suspect I am not alone in this regard, and I can understand how this process could turn off people from editing the wiki due to how time consuming it is. Simplifying the way information is entered onto the VIN page would make wiki editing a lot easier and less time consuming. I would like to propose that rather than entering each VIN individually, that we instead enter the VIN ranges for buses in orders that have sequential VINs. To give an example, take the New Flyer Industries XN60 'L VINs' page. The current format has VINs listed individually in this format: 5FYC8YC12LF073655 5FYC8YC14LF073656 5FYC8YC16LF073657 .... 5FYC8YC19LF073667 5FYC8YC10LF073668 It would be much easier if we could just list the sequential VINs in the following format as a example: 5FYC8YC12LF073655 - LF073668. Individual VINs would continue to be listed on the respective fleet series pages, ensuring that anyone would be easily able to search for a VIN by simply entering it into the search function of the wiki. The first VIN in each group would become the "id" number in the VIN page tables. The main advantage of this proposed format would be the drastically reduced time in entering the information while still maintaining the ultimate goal of creating reference lists for production of each model. 2) The VIN pages should be narrowed in scope to only focus on buses/vehicles that have a integral chassis and/or unique serial sequence. There is no need to have VIN pages for cutaway buses like Ford Cutaways, GM Cutaways, IC Bus Chassis, etc. This is because these cutaway chassis will share the same serial sequence with whatever else the manufacturer is manufacturing whether it be cars, trucks or both. Thus, it would be impossible to compile a complete production list at any point and all these pages end up accomplishing is duplicating information already available on the fleet series pages. Since the fleet series pages would already have the VIN listed, anyone trying to search a VIN would be able to do that by using the search function. 3) In the long term it may be worth thinking about how the VIN pages are set up. It appears they were originally set up by model rather than being set up to follow the manufacturer serial sequence. I can understand it is probably way too far in the game to consider changing the format completely but there needs to be a way to perhaps integrate some of the pages. For example, Gillig Low Floor and BRT serials should have been on the same pages, same with all the various Xcelsior models. Some VIN pages (but not all) have links where any gaps in VINs are linked to the appropriate page that has those VINs, perhaps that would be a standard? Overall I think I would like to see some changes to the VIN pages based on points 1 and 2 I've raised. Point 3 is probably worth some discussion but I can understand if there isn't really much that can be done in that regard. In the ten years since the VIN project began we've come a long way. However I think it's always a good idea to discuss ways to make the wiki easier to edit and I would be also be interested in hearing if anyone else has had similar concerns to me, or has any different ways to approach the issues I've raised.
  12. https://cptdb.ca/wiki/index.php/Steamboat_Springs_Transit_55 To Steamboat Springs Transit 55-56
  13. https://cptdb.ca/wiki/index.php/Everett_Transit_B0700-B0706 to Everett Transit B0700-B0703 https://cptdb.ca/wiki/index.php/Everett_Transit_B0704-B706 can be deleted. I created the page, noticed the error right away and just made a page with the correct title. No edit history lost.
  14. A revised RFP was posted for the 4 30ft diesel buses yesterday. Bids are due August 6 and the region still requests delivery by April. Optional pricing is requested for hybrid and electric buses. https://regionofwaterloo.bidsandtenders.ca/Module/Tenders/en/Tender/Detail/44340c8e-ca9d-41c3-bff8-8ef58c3a6250
  15. RFP 2020-038 TRANSIT BUSES FOR COUNTY OF SIMCOE AND TOWN OF MIDLAND The County of Simcoe and Town of Midland are conducting a joint procurement for 30' low floor buses to be delivered in 2021-2023. 2021 delivery of 3 buses to Simcoe County and 1 bus to Midland. Delivery is required by June 15, 2021. 2022 delivery of 1 bus to Simcoe County. 2023 requirements to be determined. https://simcoecounty.bidsandtenders.ca/Module/Tenders/en/Tender/Detail/f3f1872d-ddc3-4ded-991c-d9012d2724c1
  • Create New...