Oshawa Camaro Production Ceases November 20, Reduced To Three Shifts

Mark Stevenson
by Mark Stevenson

First announced December 19, 2012, GM Canada’s Oshawa Assembly facility will officially cease production of the Camaro on November 20, 2015 in conjunction with the car’s next generation, GM announced today. Camaro production remained at the Oshawa plant a year longer than initially promised in 2012.

Assembly shifts will be reduced from four to three between the “Flex” and “Consolidated” lines. Currently, the “Flex” line is on three shifts while the smaller line is on one shift. GM Canada will “begin a voluntary retirement canvass” to reduce worker head count before implementing any layoffs. GM Canada President, Stephen K. Carlisle, stated “60 percent of our hourly workforce are nearing retirement” age and the company will offer incentives to eligible employees looking to retire early.

Chevrolet Impala, Buick Regal and Cadillac XTS production will continue on the “Flex” line for now. Regal production is scheduled to move to Germany by 2017 while the XTS will be discontinued at the end of its lifecycle in 2019. Both the XTS and Impala are also produced in Michigan. The “Consolidated” line currently builds the Impala Limited – a previous-generation W-body sedan – and the Chevrolet Equinox, the latter which is also produced in Ingersoll, Ontario.

GM Canada and Unifor are working together to “examine a range of longer-term opportunities and competitiveness enhancements for Oshawa Assembly,” stated the release today. The future of Oshawa will be announced after Unifor national bargaining next year.

On the same day, GM also announced $5.4b in investments aimed at the company’s Pontiac, Lansing, and Warren, Michigan facilities.

The announcement comes after GM Canada committed $800m to Ingersoll and another 100 jobs toward expanding connected car and green technology development at GM Canada’s Oshawa Engineering Centre.

Mark Stevenson
Mark Stevenson

More by Mark Stevenson

Comments
Join the conversation
3 of 7 comments
  • Danio3834 Danio3834 on May 01, 2015

    No one is surprised. There's little reason to expand in Ontario, and ever more reasons to leave.

    • Psarhjinian Psarhjinian on May 01, 2015

      Ford and Chrysler expanded production, though Chrysler was admittedly a near thing and depends on FCA's commitment to the minivan market. Honda expanded. Toyota did just move Corolla production out of Cambridge, but they'll be picking up high-value work to replace it, so there's no lost jobs. It also opened Woodstock a few years ago. I'd say this isn't really a problem with Ontario and more an issue with GM's production planning.

  • Arthur Dailey Arthur Dailey on May 01, 2015

    A number of factors negatively impacting D3 manufacturing in Ontario. The first was Bob White's enormous ego. In the mid to late 80's when he removed the Canadian autoworkers from the UAW and formed the CAW he never considered the long term consequences. Once NAFTA replaced the US-Canada Auto Pact, American and Canadian autoworkers were competing for jobs. Therefore the UAW was petitioning US politicians to move production to their facilities. Killing Canadian jobs didn't matter to American politicians. Just like British politicians could use colonial troops in suicidal situations with little repercussion during the World Wars. The Ontario government compounded the problem with its ludicrous and onerous electricity programs. There is no way that the cost of electricity should be so high in Ontario. Their refusal to invest in infrastructure also means that the highways between Ontario and the U.S. are now congested adding to fuel costs and transport time. Finally once the D3 were able to 'offload' much of the cost for medical care/coverage from their retirees and new hires, their costs were reduced dramatically. Not having to provide medical coverage in Ontario, due to universal healthcare, was a significant cost savings for employers in Ontario. So once again politics and cost trump quality and loyalty.

  • W Conrad I'm not afraid of them, but they aren't needed for everyone or everywhere. Long haul and highway driving sure, but in the city, nope.
  • Jalop1991 In a manner similar to PHEV being the correct answer, I declare RPVs to be the correct answer here.We're doing it with certain aircraft; why not with cars on the ground, using hardware and tools like Telsa's "FSD" or GM's "SuperCruise" as the base?Take the local Uber driver out of the car, and put him in a professional centralized environment from where he drives me around. The system and the individual car can have awareness as well as gates, but he's responsible for the driving.Put the tech into my car, and let me buy it as needed. I need someone else to drive me home; hit the button and voila, I've hired a driver for the moment. I don't want to drive 11 hours to my vacation spot; hire the remote pilot for that. When I get there, I have my car and he's still at his normal location, piloting cars for other people.The system would allow for driver rest period, like what's required for truckers, so I might end up with multiple people driving me to the coast. I don't care. And they don't have to be physically with me, therefore they can be way cheaper.Charge taxi-type per-mile rates. For long drives, offer per-trip rates. Offer subscriptions, including miles/hours. Whatever.(And for grins, dress the remote pilots all as Johnnie.)Start this out with big rigs. Take the trucker away from the long haul driving, and let him be there for emergencies and the short haul parts of the trip.And in a manner similar to PHEVs being discredited, I fully expect to be razzed for this brilliant idea (not unlike how Alan Kay wasn't recognized until many many years later for his Dynabook vision).
  • B-BodyBuick84 Not afraid of AV's as I highly doubt they will ever be %100 viable for our roads. Stop-and-go downtown city or rush hour highway traffic? I can see that, but otherwise there's simply too many variables. Bad weather conditions, faded road lines or markings, reflective surfaces with glare, etc. There's also the issue of cultural norms. About a decade ago there was actually an online test called 'The Morality Machine' one could do online where you were in control of an AV and choose what action to take when a crash was inevitable. I think something like 2.5 million people across the world participated? For example, do you hit and most likely kill the elderly couple strolling across the crosswalk or crash the vehicle into a cement barrier and almost certainly cause the death of the vehicle occupants? What if it's a parent and child? In N. America 98% of people choose to hit the elderly couple and save themselves while in Asia, the exact opposite happened where 98% choose to hit the parent and child. Why? Cultural differences. Asia puts a lot of emphasis on respecting their elderly while N. America has a culture of 'save/ protect the children'. Are these AV's going to respect that culture? Is a VW Jetta or Buick Envision AV going to have different programming depending on whether it's sold in Canada or Taiwan? how's that going to effect legislation and legal battles when a crash inevitibly does happen? These are the true barriers to mass AV adoption, and in the 10 years since that test came out, there has been zero answers or progress on this matter. So no, I'm not afraid of AV's simply because with the exception of a few specific situations, most avenues are going to prove to be a dead-end for automakers.
  • Mike Bradley Autonomous cars were developed in Silicon Valley. For new products there, the standard business plan is to put a barely-functioning product on the market right away and wait for the early-adopter customers to find the flaws. That's exactly what's happened. Detroit's plan is pretty much the opposite, but Detroit isn't developing this product. That's why dealers, for instance, haven't been trained in the cars.
  • Dartman https://apnews.com/article/artificial-intelligence-fighter-jets-air-force-6a1100c96a73ca9b7f41cbd6a2753fdaAutonomous/Ai is here now. The question is implementation and acceptance.
Next