Cruise LLC
TypeSubsidiary
IndustrySelf-driving car
FoundedOctober 2013 (2013-10)
Founders
Headquarters,
U.S.
Key people
Mo Elshenawy (President & CTO)[1][2]
ProductsCruise AV, Cruise Origin
Number of employees
1800[3] (2020)
ParentGeneral Motors
Websitegetcruise.com

37°46′12″N 122°24′35″W / 37.7699°N 122.4098°W / 37.7699; -122.4098 Cruise LLC is an American self-driving car company headquartered in San Francisco, California. Founded in 2013 by Kyle Vogt and Dan Kan,[4][5][6] Cruise tests and develops autonomous car technology. The company is a largely autonomous subsidiary of General Motors.[7]

History

Cruise initially focused on developing direct-to-consumer kits to retrofit vehicles with limited self-driving capabilities.[8] The earlier generation of Cruise technology, RP-1, offered an autonomous on-demand feature available for the Audi A4 or S4 (2012 or later). The $10,000 kit is intended to eventually retrofit all vehicles into a highway autopilot system. Ultimately, Cruise determined that the greater challenge lay in conquering city driving. In January 2014, the company decided to abandon the RP-1 and produce a fully autonomous vehicle using the Nissan Leaf. In 2015, Cruise changed its strategy and began writing software to be used for fully self-driving vehicles.[8] The brand philosophy urges car owners to engage in shared ownership instead of individual ownership, in order to reduce environmental damage, the number of accidents, and congestion in big cities.[9]

Cruise received a permit to test self-driving vehicle technology from the California Department of Motor Vehicles in June 2015.[10] After it successfully graduated from Y Combinator, a startup accelerator that mentors up-and-coming entrepreneurs, Cruise was acquired by General Motors in March 2016.[11] The amount was undisclosed, and reports have estimated the number from "north of $500 million",[12] to $580 million[13] to over $1 billion.[11] Cruise forms the core of GM's self-driving efforts.[14]

Upon acquisition, Cruise had around 40 employees.[8] In a September 2016 interview with Darrell Etherington at the San Francisco TechCrunch Disrupt conference, Vogt confirmed that the company had over 100 employees.[15] Cruise's current headcount is unknown, but multiple outlets have reported that Cruise has continued to grow rapidly. In June 2017, Mary Barra stated that Cruise has close to 200 employees.[16]

Industry observers have noted, and GM CEO Mary Barra has stated, that GM allowed Cruise to remain responsible for both technology and commercialization, giving Cruise independence to avoid the pitfalls common when a large company acquires a technology startup.[7]

Acquisition by GM and investments

Since becoming part of General Motors in March 2016,[17] Cruise has been working on developing software and hardware to make fully autonomous vehicles using modified Chevrolet Bolts.

In April 2017, GM announced plans to invest $14 million to expand Cruise operations in California, adding an estimated 1,163 full-time employees by 2021.[18][12]

In May 2018, Cruise announced that SoftBank Vision Fund would invest $2.25 billion into the company, along with another $1.1 billion from GM itself.[19] In October 2018, Cruise announced that Honda would be investing $750 million into the company, followed by another $2 billion over the next 12 years.[20] In November 2018, the company got a new CEO, Dan Ammann, who had been a president of GM before accepting this position.[21] Cruise raised an additional $1.15 billion in new equity in May 2019, bringing its total valuation to $19 billion.[22][23]

In January 2021 Microsoft, Honda and institutional investors invested a further $2 billion in combined new equity bringing the valuation to $30 billion.[24] In March 2021, Cruise acquired Voyage, a self-driving startup that was spun off of Udacity.[25]

In March 2022, GM said that it is acquiring Softbank Vision Fund 1's equity ownership in Cruise for $2.1 billion. GM is also making an additional $1.35 billion investment in Cruise.[26]

Robotaxi testing and permits

In September 2021, Cruise received a permit from the California Department of Motor Vehicles to provide driverless taxi rides in the state. The permit allows the company to provide the service without the inclusion of safety drivers - staff that would accompany the vehicle and take control of it if necessary.[27] In November 2021, Cruise co-founder Kyle Vogt took the first driverless taxi drive in the company's history.[28]

In February 2022, Cruise announced that it is now open to the public.[29][30] Also in February 2022, Cruise petitioned U.S. regulators (NHTSA) for permission to build and deploy a self-driving vehicle without human controls.[31] At the end of the month, Kyle Vogt was officially named CEO.[32]

In June 2022, Cruise received California's first Driverless Deployment Permit, allowing it to charge fees for its service.[33] This was the first company to offer rides without a driver in a major public city. The company recalled and updated software in 80 self-driving vehicles in August, following a crash in June.[34] As of September 2022, the company operated 100 robotaxis in San Francisco, and announced their intentions to increase the size of their fleet to 5,000. However, this drew some criticism due to the potential for this to increase traffic within the city.[35]

In September 2022, the company announced it would expand its service to Phoenix, Arizona, and Austin, Texas, within three months, with the goal of adding $1 billion in revenue by 2025.[36] The Verge reported that the company lost $561 million in Q1 2023, with most of the $30 million in revenue coming from interest and other non-operating sources of income, but said it remains on the path to reach $1 billion in revenue by 2025 and $50 billion by 2030. The article noted Cruise CEO Kyle Vogt said a small portion of the company's fleet offered driverless rides 24 hours a day across the entire city of San Francisco.[37]

Suspension of operations

Cruise charging and storage facility in San Francisco (Nov 2023)

In October 2023, following a barrage of safety concerns and incidents since Cruise received approval in August 2023 for round-the-clock robotaxi service in San Francisco,[38] the California DMV suspended Cruise's self-driving car permits following an investigation of a pedestrian collision, effective immediately.[39] Three days later, Cruise announced it would temporarily halt robotaxi operations nationwide.[40] Outside of California, the voluntary nationwide scope expansion suspended services in Arizona (Phoenix), Texas (Austin, Dallas, and Houston), and Florida (Miami).[41]

On November 8, Cruise announced a recall of 950 autonomous vehicles, to be implemented by an over-the-air software update, as a result of the pedestrian collision.[42] The next day, Cruise announced it had laid off an unspecified number of contingent workers who had supported autonomous vehicle operations; at the time, Cruise had an estimated 4,000 full-time employees.[43]

On November 19, CEO Kyle Vogt announced his resignation from Cruise in the wake of the suspension.[44] GM appointed Mo Elshenawy, Cruise’s executive vice president of engineering, and Craig Glidden, GM's General Counsel, as co-presidents.[45]

Products

Cruise RP-1

The first product offered by Cruise was the RP-1, announced in June 2014 as a kit to be available in 2015. The RP-1 was priced at US$10,000, including installation, and was intended to be retrofitted to 2012 and newer Audi A4 and S4. The RP-1 package included a roof-mounted "sensor pod" with cameras, radar, GPS, inertial sensors, and on-board computer linked to steering, throttle, and brake actuators. Once activated on a limited-access highway, the RP-1 would maintain speed and following distance and keep the car within its lane. Pre-orders were limited to 50 units via a US$1,000 reservation/deposit fee.[46] However, Cruise shifted its strategy in 2015 to focus on the creation of a fully autonomous vehicle platform rather than a retrofit kit and never released the RP-1.[47][48]

Cruise initially purchased Nissan Leaf battery-electric vehicles to test automated driving systems,[49] but these were not tested after December 2016.[50]

Cruise AV

A G3 Cruise AV based on the Chevrolet Bolt undergoing testing in San Francisco. The vehicle is equipped with numerous Velodyne LiDAR sensors.

The Cruise AV is a Chevy Bolt-based autonomous vehicle; the first generation (G1) were modified by Cruise in San Francisco while the subsequent second and third generations (G2 and G3) are manufactured at the Orion Township assembly plant in Michigan. The Cruise AVs feature "drive control algorithms and artificial intelligence created by Cruise."[51] The Cruise AV uses Lidar, radar, and camera sensors; according to Cruise, 40% of its hardware is unique to self-driving.[52]

In 2016, Cruise was conducting testing with a fleet of approximately 30 self-driving G1 Cruise AVs.[53] By June 2017, GM and Cruise had produced an estimated 180 G1 and G2 Cruise AV self-driving vehicles after GM announced the mass production of 130 new G2 Cruise AVs.[54]

In 2017, Cruise was conducting testing on public roads with Cruise AVs in San Francisco, Scottsdale, Arizona, and the metropolitan Detroit area. In early 2017, Cruise released a series of videos showing its self-driving vehicles navigating the streets of San Francisco.[55] In an interview with Fortune in July 2017, Vogt described the videos as "the most technically advanced demonstrations of self-driving cars that have ever been put out there in public."[56] Also in July 2017, Cruise announced "Cruise Anywhere," a program for San Francisco-based employees to use self-driving cars as a rideshare service.

In October 2020, the California Department of Motor Vehicles granted a permit to Cruise for testing fully driverless vehicles.[57] Cruise began testing Cruise AVs without a human safety driver present on the streets of San Francisco in December 2020.[58] In September 2021, Honda started testing program toward launch of Level 4 mobility service Business in Japan, using the G3 Cruise AV.[59]

Cruise Origin

In January 2020, the company exhibited the Cruise Origin, a Level 4–5 driverless vehicle,[60] intended to be used for a ride hailing service.[61] The Origin is purpose-built as a self-driving vehicle, rather than retrofitted from a non-autonomous vehicle, and contains no manual steering controls.[62] Costing approximately $50,000 to manufacture at scale,[63] the vehicle is all-electric and designed to have a lifespan of 1,000,000 mi (1,600,000 km).[64] Cruise announced that future Origin vehicles would be manufactured at GM's Detroit-Hamtramck plant.[65][66] It is built on the GM BEV3 platform using Ultium battery technology.[67]

In January 2021, Honda announced a partnership with Cruise to bring the Origin to Japan as part of Honda's future Mobility as a Service (MaaS) business.[68] By September 2022, Japan version prototype of the Cruise Origin for Tokyo was completed and started testing.[69]

In May 2021, Cruise announced they expected mass production of the Origin driverless shuttle would commence in 2023.[70] In June 2021, Cruise announced it had secured a $5 billion line of credit from General Motors to assist with commercialization and that it had begun assembly of 100 pre-production Origin vehicles for validation testing.[71] Prototype Origin vehicles were spotted testing with human operators at GM-owned proving grounds by July 2022.[72]

The State of California issued testing permits to Cruise in June 2021, allowing the company to provide limited revenue taxi service without human drivers.[73] In February 2022, General Motors and Cruise announced they had petitioned NHTSA for permission to build and deploy the Cruise Origin.[74][75] Because the Origin does not have manual controls, the NHTSA must issue an exception to the Federal Motor Vehicle Safety Standards to permit operation on public roads;[76] production was ready to begin by February 2023,[77] pending approval of the exception, which had not been granted by September 2023.[78]

Along with the suspension of Cruise's operations, GM paused production of the Origin in November 2023.[79]

Regulation

Cruise received a permit from the California Public Utilities Commission (CPUC) in June 2022, allowing them to operate revenue taxi services in San Francisco using cars without a human driver during limited hours in certain areas of the city.[33] Cruise and Waymo later submitted applications to the CPUC, seeking to expand the commercial operating hours for their robotaxi services in San Francisco. In January 2023, the city of San Francisco wrote to the CPUC, requesting that the applications be denied: "in the months since the Initial Approval [of autonomous taxi services in June 2022], Cruise AVs have made unplanned and unexpected stops in travel lanes, where they obstruct traffic and transit service, and intruding into active emergency response scenes, including fire suppression scenes, creating additional hazardous conditions."[80][81]

Although draft resolutions approving the expansion petitions were posted by the CPUC in May 2023,[82] the hearing was delayed from June 29 to July 13, pending further review.[83] Before the scheduled July 13 hearing was held, a group named Safe Street Rebel published a viral video to social media, showing that an autonomous vehicle could be disabled temporarily without permanent damage by placing a traffic cone on it and vowing to conduct a "Week of Cone" to demonstrate their concerns.[84][85] Cruise released a statement in response: "Intentionally obstructing vehicles gets in the way of [efforts to provide free rides, meal deliveries, and retrieve food waste] and risks creating traffic congestion for local residents."[86]

The CPUC delayed the hearing for the permit expansions again to August 10.[87] At that hearing, the CPUC approved the scope expansion by a 3–1 vote, allowing both Cruise and Waymo to offer robotic taxi services at all hours throughout San Francisco.[88]

On October 24, 2023, the California Department of Motor Vehicles suspended Cruise's permit to test and operate autonomous vehicles without a safety driver.[89] According to the suspension order, during their initial meeting with the California DMV on October 3, Cruise had shown a video captured by the AV's onboard cameras that depicted events up to the first complete stop after the Cruise AV struck the pedestrian; Cruise personnel neither described nor showed the remaining recording of the "pullover maneuver" that happened next, during which the pedestrian was dragged for 20 ft (6.1 m) at 7 mph (11 km/h). After learning about the dragging from another government agency, the DMV requested and received the full recording from Cruise. A spokesperson for Cruise disputed the dragging footage was withheld, saying the complete video was shown multiple times.[90] In its press release, the California DMV stated it had determined "the manufacturer's vehicles are not safe for the public's operation" and added "the conduct of autonomous vehicle testing on public roads by the manufacturer [makes] an unreasonable risk to the public". The suspension is effective immediately and does not have a set expiration; the permit will be reinstated after Cruise completes unspecified required actions.[91] The CPUC also suspended Cruise's permit to provide autonomous revenue taxi services the same day, following the DMV.[92]

Incidents

Interior of Cruise autonomous vehicle in San Francisco

Interference with police and fire services

In April 2022, the San Francisco Police Department (SFPD) stopped a Cruise AV for driving at night without its headlights on. The AV was empty, operating without any human safety attendants or passengers. The vehicle pulled over for SFPD ahead of an intersection, then proceeded across the intersection when an officer walked away from it;[93] on the other side of the intersection, the vehicle stopped again and turned on its hazard lights.[94] According to Cruise, the vehicle operated as intended, moving to the "nearest safe location" for the traffic stop in response to direction from Cruise personnel after the SFPD officer was clear of the vehicle.[94]

Also in April 2022, an empty Cruise AV blocked the path of a San Francisco Fire Department (SFFD) truck responding to a fire at approximately 4 AM; the fire truck was unable to pass a garbage truck doubled-parked in the lane by using the lane for oncoming traffic, as the AV was occupying the oncoming lane. The Cruise AV had stopped and yielded to the fire truck, but was unable to pull to the right to clear the oncoming lane because of parked cars.[95] While a human might have reversed to clear the lane, the Cruise AV did not move out of the way of the fire truck. San Francisco city officials filed a report to the CPUC, stating that "this incident slowed SFFD response to a fire that resulted in property damage and personal injuries."[96]

In June 2023, a video was taken of a Cruise car appearing to block police and fire services from responding to a mass shooting in San Francisco. Cruise denied that the car had blocked the road, stating that emergency response vehicles "were able to proceed around our car". The police and fire departments declined to comment.[97] The San Francisco Fire Department reported there had been 39 incidents between January and June 2023 where Cruise and Waymo robotaxis had blocked first responders.[98]

In August 2023, a San Francisco firetruck collided with a Cruise car while responding to an emergency call with lights and sirens active.[99] As a result of the incident, the California Department of Motor Vehicles requested that "Cruise to immediately reduce its active fleet of operating vehicles by 50% until the investigation is complete and Cruise takes appropriate corrective actions to improve road safety".[100]

City of Austin police and fire departments noted 12 "near miss" incidents occurred with Cruise vehicles between July and November 2023; Austin FD requested that Cruise set up an avoidance area around Fire Station 2, and Austin PD noted the vehicles were unable to recognize hand signals that conflicted with traffic signals.[101]

Other traffic collisions and clustering

On June 3, 2022, a Cruise AV taxi carrying three backseat passengers was involved in an accident with a Toyota Prius after making an unprotected left turn. According to Cruise, "occupants of both vehicles received medical treatment for allegedly minor injuries". According to GM, the Prius was speeding at the time of the accident and was in the wrong lane. In the aftermath of the incident, Cruise temporarily changed the vehicles' programming to make fewer unprotected left turns.[102]

On June 29, 2022, nearly twenty Cruise AVs blocked traffic for two hours by clustering at the intersection of Gough and Fulton in San Francisco.[103][104] A Cruise employee sent an anonymous letter to the CPUC, asserting that Cruise loses communication with the automated vehicles "with regularity", sometimes requiring a tow truck for recovery.[105] Additional documented occurrences of immobilized Cruise vehicles in 2022 include May 18 (fleet-wide communications loss), June 21 (Tenderloin),[105] and September 22 (two incidents; one near Sacramento and Leavenworth, the other near Geary and Franklin).[106] San Francisco has recorded 28 incidents reported by 9-1-1 involving autonomous vehicle failures between May 29 and September 5, 2022.[107]:4,31 In October, US News and World Report reported that Cruise autonomous taxis had blocked traffic in San Francisco on several occasions.[108]

In March 2023, two Cruise AVs operating without passengers drove through a blocked off intersection in San Francisco, and got tangled with downed power lines normally used by Muni trolleybuses.[109] The next day, a passengerless Cruise AV rear ended a Muni bus on Haight Street.[110]

Disengagement and remote assistance

In November 2023, The New York Times reported that on average, according to two people familiar with Cruise's operations, a remote operator had to intervene for every 2+12 to 5 mi (4.0 to 8.0 km) driven.[111] Vogt confirmed that its vehicles made a call for remote assistance "2–4% of the time on average, in complex urban environments", but clarified that "of those, many are resolved by the AV itself before the human even looks at things". A spokesperson for Cruise added that a call remote assistance is triggered every 4 to 5 mi (6.4 to 8.0 km).[112] Brad Templeton reported that remote assistance did not mean real-time remote operation by a human, citing reporting from Cruise that stated 98% of remote assistance calls connected to a human operator within 3 seconds, and 80% of remote assistance calls were resolved without action by the human operator.[113] Cruise reported an average distance between disengagements of 95,900 mi (154,300 km) in 2022.[114]

Detection

In November 2023, The Intercept reported that Cruise vehicles were unable to consistently recognize and track children and large holes, according to a review of internal safety reports.[115]

Pedestrian injuries

In August 2023, a Cruise AV starting to proceed through an intersection at 1.4 mph (2.3 km/h) on a green light struck a pedestrian, who subsequently was transported by ambulance after complaining of knee pain.[116][117]

At approximately 9:30 p.m. (PDT) on October 2, 2023, a pedestrian was struck by a driver traveling south on Fifth Street in San Francisco after crossing the intersection with Market Street. The driver continued without stopping after the pedestrian was tossed over the right side of the car into the adjacent lane, where a Cruise AV nicknamed "Panini", traveling alongside and operating without a safety driver, subsequently also struck and then dragged the pedestrian for approximately 20 ft (6.1 m), coming to a stop with a tire resting on the pedestrian's leg, pinning them beneath the AV. The Jaws of Life were used to free the pedestrian from underneath "Panini". The driver who initially struck the pedestrian fled the scene.[118][119] According to Cruise, the AV had attempted to avoid striking the pedestrian by first swerving to the right, then stopping immediately after a collision had been detected, followed by attempting to pull over to clear the road. The pedestrian was dragged during the pullover attempt.[120][121]

Investigations

The National Highway Traffic and Safety Administration (NHTSA) opened preliminary investigation PE22-014 on December 12, 2022, citing incidents in which the vehicles may have engaged "in inappropriately hard braking or [became] immobilized".[122][123] Three specific incidents of hard braking were described, all involving situations in which the automated driving systems, while operating under human supervision, initiated a hard braking maneuver in response to other road users approaching quickly from behind, resulting in the other road user striking the automated car.[122] Two letters were sent to Cruise on January 4, 2023, requesting relevant data.[124][125]

The California DMV opened an investigation in August 2023 following "recent concerning incidents" involving Cruise AVs.[126] The investigation resulted in the immediate suspension of Cruise's permit to test and operate autonomous vehicles, effective October 24, 2023.[127]

In response to the two collisions with pedestrians in August and October 2023, NHTSA opened preliminary investigation PE23-018 on October 16, 2023;[117][128] in addition, NHTSA identified two other incidents from publicly posted videos where AVs had encroached on pedestrians in or entering roadways.[129]

See also

References

  1. "Cruise co-founder and CEO Kyle Vogt resigns". TechCrunch. November 20, 2023. Retrieved November 20, 2023.
  2. "Cruise CEO Vogt Resigns at GM's Troubled Self-Driving Car Unit". Bloomberg. November 19, 2023. Retrieved November 20, 2023.
  3. Wayland, Michael (May 14, 2020). "GM's self-driving unit Cruise to cut 8% of staff". CNBC. Retrieved December 11, 2020.
  4. Waters, Richard (November 29, 2018). "General Motors president to control Cruise self-driving unit". Financial Times.
  5. Clifford, Catherine (April 26, 2016). "This 29-Year-Old Entrepreneur Was Rejected by 35 Potential Employers. Now, He's the Co-Founder of a $1 Billion Startup. Here's How". Entrepreneur.
  6. Gardner, Greg (April 15, 2016). "Former Cruise partner fires back in fight over GM deal". Detroit Free Press.
  7. 1 2 Michael Wayland (June 19, 2017). "GM lets its autonomous unit be autonomous". Automotive News.
  8. 1 2 3 Erin Griffith (September 22, 2016). "Driven in the Valley: The Startup Founders Fueling GM's Future". Fortune.
  9. "GM's Cruise unveils its first driverless vehicle". BBC News. January 22, 2020.
  10. Horatiu Boeriu (September 19, 2015). "These carmakers have licenses to test autonomous cars in California". BMWBLOG.
  11. 1 2 Dan Primack; Kirsten Korosec (March 11, 2016). "GM Buying Self-Driving Tech Startup for More Than $1 Billion". Fortune.
  12. 1 2 "GM's Cruise employees test-ride startup's robot cars". San Francisco Chronicle. August 9, 2017. p. C3.
  13. Matthew DeBord (July 21, 2016). "GM paid a lot less for Cruise Automation than everyone thought". Business Insider.
  14. David R. Baker; Carolyn Said (July 14, 2017). "How the Bay Area took over the self-driving car business". San Francisco Chronicle.
  15. Life Tips from Kyle Vogt of Cruise at Disrupt SF. September 14, 2016.
  16. Cadie Thompson (June 28, 2017). "GM wants the era of self-driving cars to be led by women". Business Insider.
  17. "GM to Acquire Cruise Automation to Accelerate Autonomous Vehicle Development" (Press release). General Motors. March 11, 2016. Retrieved November 10, 2023.
  18. "GM Announces More Than 1100 Jobs To Expand Cruise Automation Self-Driving Operations In California". California - Governor's Office of Business and Economic Development. April 14, 2017. Archived from the original on September 9, 2017. Retrieved September 8, 2017.
  19. "GM's Cruise gets $2.25B from SoftBank's Vision Fund, $1.1B from GM". TechCrunch. Retrieved August 24, 2018.
  20. "Honda to Invest $2.75 Billion in GM's Self-Driving Car Unit". Retrieved October 5, 2018.
  21. "Cruise Automation taps GM president Dan Ammann as its new CEO". TechCrunch. Retrieved November 30, 2018.
  22. Hawkins, Andrew J. (May 7, 2019). "GM's self-driving division Cruise raises another $1.15 billion". The Verge. Retrieved December 11, 2020.
  23. Marshall, Aarian (May 7, 2019). "Cruise's $1 Billion Infusion Shows the Stakes in Self-Driving Tech". Wired. Retrieved December 11, 2020.
  24. Wayland, Michael (January 19, 2021). "Microsoft is investing and partnering with GM's Cruise on self-driving cars". CNBC. Retrieved February 10, 2021.
  25. Korosec, Kirsten (March 15, 2021). "Cruise acquires self-driving startup Voyage". TechCrunch. Retrieved March 15, 2021.
  26. Korosec, Kirsten (March 19, 2022). "GM is buying out Softbank's stake in autonomous vehicle unit Cruise". TechCrunch. Retrieved March 20, 2022.
  27. Hawkins, Andrew J. (September 30, 2021). "Cruise gets the green light to give driverless rides to passengers in San Francisco". The Verge. Retrieved October 1, 2021.
  28. Bellan, Rebecca (November 3, 2021). "Cruise launches driverless robotaxi service in San Francisco". TechCrunch. Retrieved November 4, 2021.
  29. "Welcome, Riders". www.getcruise.com. Archived from the original on February 2, 2022. Retrieved February 2, 2022.
  30. Vijayenthiran, Viknesh (February 2, 2022). "Cruise opens up driverless taxi service to public in San Francisco". Motor Authority. Retrieved March 16, 2022.
  31. Shepardson, David (February 19, 2022). "GM seeks U.S approval to deploy self-driving vehicles". Reuters. Retrieved March 16, 2022.
  32. Crowe, Steve (February 28, 2022). "Cruise co-founder Vogt named CEO of autonomous driving company". The Robot Report. Retrieved March 17, 2022.
  33. 1 2 Kolodny, Lora (June 2, 2022). "Cruise gets green light for commercial robotaxi service in San Francisco". CNBC. Retrieved June 3, 2022.
  34. Wayland, Michael (September 1, 2022). "GM's Cruise recalls and updates self-driving software in cars following crash". CNBC. Retrieved September 1, 2022.
  35. McFarland, Matt (September 30, 2022). "GM's Cruise wants to add 5,000 more robotaxis to American streets. This city warns it could backfire | CNN Business". CNN. Retrieved December 15, 2022.
  36. Welch, David (September 12, 2022). "GM's Cruise Will Expand Robotaxi Service to Phoenix and Austin". Bloomberg News.
  37. Hawkins, Andrew J. (April 25, 2023). "Cruise continues to burn GM's cash as robotaxis expand to daylight hours". The Verge. Retrieved April 28, 2023.
  38. Bhuiyan, Johana (August 10, 2023). "San Francisco to get round-the-clock robo taxis after controversial vote". The Guardian.
  39. Field, Hayden (October 24, 2023). "California DMV suspends Cruise's self-driving car permits, effective immediately". CBNC.
  40. Feuer, Will (October 27, 2023). "GM's Cruise Pauses All Driverless Operations After California Crackdown". The Wall Street Journal. Retrieved October 27, 2023.
  41. Shepardson, David (October 26, 2023). "GM Cruise unit suspends all driverless operations after California ban". Reuters. Retrieved October 27, 2023.
  42. Hawkins, Andrew J. (November 8, 2023). "Cruise is recalling 950 driverless cars after one of its vehicles ran over a pedestrian". The Verge. Retrieved November 10, 2023.
  43. Korosec, Kirsten (November 9, 2023). "Cruise begins layoffs, starting with workers who supported driverless operations". TechCrunch. Retrieved November 10, 2023.
  44. "Cruise CEO quits after alleged cover-up". EV inFocus. November 20, 2023. Retrieved November 21, 2023.
  45. Lu, Yiwen; Mickle, Tripp (November 19, 2023). "Cruise's C.E.O. Quits as the Driverless Carmaker Aims to Rebuild Trust". The New York Times. Retrieved November 29, 2023.
  46. Strange, Adario (June 23, 2014). "Hands-Free Driving Coming to New Cars Starting in 2015". Mashable. Retrieved July 5, 2022.
  47. Bergen, Mark (March 11, 2016). "Meet Kyle Vogt, the 'Robot Guru' Who Just Sold His Second Billion-Dollar Startup in Two Years". Vox. Retrieved July 5, 2022. At some point [in 2015], Vogt shifted plans to focus on building a full self-driving platform. That strategy pits the startup against Google, which is, according to multiple industry sources, pitching a similar system to carmakers.
  48. Hyatt, Nabeel (March 11, 2016). "On Cruise, the hard things the hard way". medium.com. Retrieved July 5, 2022. Then, just a few months later, [Vogt] emailed to say he'd gotten the RP-1 highway autopilot fully working, only he was killing it. Oh, and he had something new to show me, I should come by.
  49. Ostojic, Sasha (December 22, 2016). Autonomous Vehicle Tester Program Annual Disengagement Report (PDF) (Report). California Department of Motor Vehicles. Archived from the original (PDF) on October 13, 2018.
  50. Boniske, Albert (December 29, 2017). Autonomous Vehicle Tester Program Annual Disengagement Report (PDF) (Report). California Department of Motor Vehicles. Archived from the original (PDF) on February 11, 2018.
  51. Alan Ohnsman (April 4, 2017). "GM's Cruise Poised To Add 1,100 Silicon Valley Self-Driving Car Tech Jobs". Forbes.
  52. "Technology / Our First-Gen AV". Cruise. Retrieved March 16, 2022.
  53. Darrell Etherington (September 14, 2016). "Cruise has around 30 self-driving test cars on roads right now". TechCrunch.
  54. Melissa Burden (January 19, 2017). "GM's Cruise Automation releases self-driving Bolt video". The Detroit News.
  55. Andrew J. Hawkins (January 19, 2017). "Watch GM's self-driving car navigate the streets of San Francisco". The Verge.
  56. Full Throttle on Self-Driving Cars. July 17, 2017.
  57. Hawkins, Andrew J. (December 9, 2020). "Cruise is now testing fully driverless cars in San Francisco". The Verge. Retrieved December 11, 2020.
  58. Said, Carolyn (December 9, 2020). "Cruise deploys true robot cars in S.F. — no backup drivers behind wheel". San Francisco Chronicle. Retrieved December 11, 2020.
  59. "Honda to Start Testing Program in September Toward Launch of Autonomous Vehicle Mobility Service Business in Japan" (Press release). Honda. September 8, 2021. Retrieved March 16, 2022.
  60. Howard, Bill (January 23, 2020). "GM's Cruise Origin Is an Autonomous Vehicle From the Future". Extreme Tech. Retrieved December 14, 2020.
  61. Baldwin, Roberto (January 22, 2020). "Cruise Unveils Origin, a Self-Driving Vehicle with No Steering Wheel or Pedals". Car and Driver. Retrieved December 11, 2020.
  62. Hawkins, Andrew J. (January 21, 2020). "Exclusive Look at Cruise's First Driverless Car Without a Steering Wheel or Pedals". The Verge. Retrieved December 11, 2020.
  63. Priddle, Alisa (January 22, 2020). "GM's Cruise Origin Self-Driving Pod Has No Steering Wheel, No Pedals, and No Driver". MotorTrend. Retrieved December 11, 2020.
  64. Wayland, Michael; Kolodny, Lora (January 23, 2020). "Debut of GM's Cruise Origin shows the future of ride-sharing, autonomous vehicles is a box". CNBC. Retrieved December 11, 2020.
  65. Hawkins, Andrew J. (January 27, 2020). "GM will spend $2.2 billion to build electric and autonomous vehicles at Detroit plant". The Verge. Retrieved December 14, 2020.
  66. Hawkins, Andrew J. (October 16, 2020). "GM rebrands its Detroit-Hamtramck plant as 'Factory Zero' for electric and autonomous vehicles". The Verge. Retrieved December 11, 2020.
  67. "GM Reveals New Ultium Batteries and a Flexible Global Platform to Rapidly Grow its EV Portfolio" (Press release). General Motors Newsroom. March 2020. Retrieved July 5, 2022.
  68. "Honda, Cruise and GM Take Next Steps Toward Autonomous Vehicle Mobility Service Business in Japan" (Press release). Japan: Honda Global. January 20, 2021. Retrieved April 5, 2021.
  69. "自動運転車両「クルーズ・オリジン」の試作車が完成、米国でテストを開始" [Prototype of self-driving car "Cruise Origin" completed, started testing in the United States]. Honda (in Japanese). September 29, 2022. Retrieved November 25, 2022.
  70. "Cruise expects GM to begin production of new driverless vehicle in early 2023". May 13, 2021. Retrieved June 21, 2021.
  71. "GM-backed Cruise secures $5 billion credit line as it prepares to launch self-driving robotaxis (www.cnbc.com)". June 15, 2021. Retrieved June 21, 2021.
  72. Lopez, Jonathan (July 22, 2022). "Cruise Origin Spied Undergoing Testing". GM Authority. Retrieved September 19, 2023.
  73. "California will allow GM-backed Cruise to transport passengers in driverless test vehicles (www.cnbc.com)". June 4, 2021. Retrieved June 21, 2021.
  74. David Shepardson (February 19, 2021). "GM seeks U.S approval to deploy self-driving vehicles". Reuters. Retrieved April 18, 2022.
  75. Brodkin, Jon (February 22, 2022). "GM seeks US approval to deploy self-driving car without a steering wheel". Ars Technica. Retrieved April 18, 2022.
  76. Shepardson, David (July 12, 2023). "US to decide on GM request to deploy self-driving cars". Reuters. Retrieved September 19, 2023.
  77. LaReau, Jamie L. (February 25, 2023). "GM's plan to deploy self-driving Cruise Origin on hold as feds weigh exemption request". Detroit Free Press. Retrieved September 19, 2023.
  78. Hawkins, Andrew J. (September 7, 2023). "Cruise 'just days away' from approval to mass-produce Origin robotaxis without steering wheels". The Verge. Retrieved September 19, 2023.
  79. Bellan, Rebecca (November 6, 2023). "GM halts production of Cruise Origin robotaxi amid suspended operations". TechCrunch. Retrieved November 10, 2023.
  80. "Protest of Cruise LLC Tier 2 Advice Letter" (PDF). San Francisco Municipal Transportation Agency. Retrieved February 1, 2023.
  81. Ingram, David (January 27, 2023). "Two companies race to deploy robotaxis in San Francisco. The city wants them to hit the brakes". NBC News. Retrieved February 1, 2023.
  82. Bellan, Rebecca (May 18, 2023). "Cruise, Waymo near approval to charge for 24/7 robotaxis in San Francisco". TechCrunch. Retrieved July 27, 2023.
  83. Truong, Kevin; Mojadad, Ida (June 27, 2023). "Robotaxi Service Expansion in San Francisco Delayed by State Regulators". The San Francisco Standard. Retrieved July 27, 2023.
  84. Taylor, Chloe (July 10, 2023). "Angry San Franciscans are sabotaging Waymo and Cruise robotaxis with one simple trick". Fortune. Retrieved July 27, 2023.
  85. Stumpf, Rob (July 6, 2023). "Grumpy Locals Are Sabotaging Cruise and Waymo Robotaxis With Traffic Cones". The Drive. Retrieved July 27, 2023.
  86. Bellan, Rebecca (July 6, 2023). "Robotaxi haters in San Francisco are disabling the AVs with traffic cones". TechCrunch. Retrieved July 27, 2023.
  87. Guaglianone, Carmela (July 11, 2023). "State vote on expanding Cruise, Waymo service in SF delayed — again". San Francisco Examiner. Retrieved July 27, 2023.
  88. Hawkins, Andrew J. (August 10, 2023). "Robotaxis score a huge victory in California with approval to operate 24/7". The Verge. Retrieved September 19, 2023.
  89. Korosec, Kirsten (October 24, 2023). "California DMV immediately suspends Cruise's robotaxi permit". TechCrunch. Retrieved October 24, 2023.
  90. Gordon, Aaron (October 24, 2023). "Cruise Self-Driving License Revoked After It Withheld Pedestrian Injury Footage, DMV Says". Motherboard. Vice. Retrieved October 25, 2023.
  91. "DMV statement on Cruise LLC suspension" (Press release). California Department of Motor Vehicles. October 24, 2023. Retrieved October 24, 2023.
  92. Bellan, Rebecca (October 24, 2023). "CAlifornia agency pulls Cruise's commercial robotaxi permit following DMV action". TechCrunch. Retrieved October 25, 2023.
  93. Hall, Kalea (April 11, 2022). "What happens when police pull over a driverless car? Watch this video and see". The Detroit News.
  94. 1 2 Wiggers, Kyle (April 11, 2022). "Autonomous Cruise car encounter with police raises policy questions". TechCrunch. Retrieved July 5, 2022.
  95. Templeton, Brad (May 27, 2022). "SF Fire Dept. Says Cruise Robotaxi Did Not Yield Properly And Delayed Fire Truck". Forbes. Retrieved July 5, 2022.
  96. Marshall, Aarian (May 27, 2022). "An Autonomous Car Blocked a Fire Truck Responding to an Emergency". Wired.
  97. Parker, Jordan; Swan, Rachel (June 10, 2023). "Cruise self-driving car appears to block S.F. mass shooting scene". San Francisco Chronicle. Retrieved June 15, 2023.
  98. Kukura, Joe (June 23, 2023). "SF Fire Chief Fumes Over Self-Driving Robotaxis Blocking First Responders Dozens of Times This Year". SFist. Archived from the original on July 27, 2023. Retrieved July 27, 2023.
  99. Rodríguez, Gloria; Melendez, Lyanne (August 19, 2023). "VIDEO: Driverless Cruise car struck by SF firetruck, injuring passenger, company says". KGO-TV.
  100. Rumpf-Whitten, Sarah (August 19, 2023). "California DMV requests Cruise to halve driverless car fleet after collision with firetruck in San Francisco". Fox Business .
  101. Marshall, Aarian (November 9, 2023). "GM's Cruise Rethinks Its Robotaxi Strategy After Admitting a Software Fault in Gruesome Crash". Wired. Retrieved November 10, 2023.
  102. Scott, Victoria (July 8, 2022). "Self-Driving Cruise Taxi Crashes With Passengers On Board". The Drive. Retrieved July 9, 2022.
  103. Bindman, Ariana (July 1, 2022). "'Surreal': Cruise's driverless cars block traffic for nearly two hours in San Francisco". San Francisco Chronicle.
  104. Bellan, Rebecca (June 30, 2022). "Cruise robotaxis blocked traffic for hours on this San Francisco street". TechCrunch. Retrieved February 1, 2023.
  105. 1 2 Marshall, Aarian (July 8, 2022). "Cruise's Robot Car Outages Are Jamming Up San Francisco". Wired. Retrieved July 8, 2022.
  106. Bartlett, Amanda (September 26, 2022). "Multiple driverless Cruise cars block traffic in San Francisco". SF Gate. Retrieved February 1, 2023.
  107. "Comment for Docket # NHTSA-2022-0067 (General Motors)". City and County of San Francisco. September 21, 2022. Retrieved February 1, 2023. The City has no information about whether the total of 28 incidents reported to 9-1-1 between May 29 and September 5, 2022 reflect recurrence of the same issues, or whether each reflects a unique issue. The large majority of these reported incidents occurred between the hours of 10 pm and 6 am when Cruise has been authorized by the California Public Utilities Commission to offer commercial service in 30 driverless Cruise AVs. We have identified an additional 20 incidents posted on social media during this three-month time period. It is reasonable to assume that the number of incidents reported to 9-1-1 and posted on social media or observed by San Francisco Police Officers are a fraction of actual travel lane road failures because few people are on the street during these hours to observe and make such reports.
  108. Motavalli, Jim (October 14, 2022). "GM's Self-Driving Cruise Cars are Causing Traffic Snarls". US News & World Report.
  109. Whiting, Sam (March 23, 2023). "Self-driving Cruise cars that tangled with S.F. Muni lines had no passengers, company says". San Francisco Chronicle.
  110. Mayer, Phil (March 24, 2023). "Cruise car appears to rear-end Muni bus". KRON-TV.
  111. Mickle, Tripp; Metz, Cade; Lu, Yiwen (November 3, 2023). "G.M.'s Cruise Moved Fast in the Driverless Race. It Got Ugly". The New York Times. Retrieved November 10, 2023.
  112. Kolodny, Lora (November 6, 2023). "Cruise confirms robotaxis rely on human assistance every four to five miles". CNBC. Retrieved November 10, 2023.
  113. Templeton, Brad (November 7, 2023). "Cruise Reports Lots Of Human Oversight Of Robotaxis, Is That Bad?". Forbes. Retrieved November 10, 2023.
  114. Juliussen, Egil (April 11, 2023). "Waymo, Cruise Dominate AV Testing". EE Times. Retrieved November 10, 2023.
  115. Biddle, Sam (November 6, 2023). "Cruise knew its self-driving cars had problems recognizing children—and kept them on the streets". The Intercept. Retrieved November 10, 2023.
  116. "Incident Report, ID 30412-6175-1" (PDF). United States Department of Transportation, National Highway Traffic Safety Administration. August 26, 2023. Archived from the original (PDF) on October 17, 2023.
  117. 1 2 Goswami, Rohan (October 17, 2023). "Federal regulators open probe into Cruise after pedestrian injury reports". CNBC. Retrieved October 24, 2023.
  118. "Hit-and-run driver strikes pedestrian, tossing her into path of Cruise car in San Francisco". NBC Bay Area. October 2, 2023. Retrieved October 24, 2023.
  119. Parker, Jordan; Mishanec, Nora (October 2, 2023). "Driver hits woman in S.F., then Cruise driverless car runs her over; photo shows victim trapped". San Francisco Chronicle. Retrieved October 25, 2023.
  120. "A detailed review of the recent SF hit-and-run incident". Cruise LLC. October 2023. Retrieved October 24, 2023.
  121. "Incident Report, ID 30412-6395-1" (PDF). United States Department of Transportation, National Highway Traffic Safety Administration. October 2, 2023. Archived from the original (PDF) on October 17, 2023.
  122. 1 2 Haugh, Thomas (December 12, 2022). "ODI Resume: PE 22-014" (PDF). National Highway Traffic and Safety Administration. Retrieved February 1, 2023.
  123. Korosec, Kirsten (December 16, 2022). "Cruise's autonomous driving tech comes under scrutiny from safety regulators". TechCrunch. Retrieved February 1, 2023.
  124. "PE22-014 to investigate allegations of Automated Driving System (ADS) equipped vehicles operated by Cruise LLC (Cruise) engaging in inappropriately hard braking while operating in the specified Operational Design Doman (ODD)" (PDF). National Highway Traffic and Safety Administration. January 4, 2023. Retrieved February 1, 2023.
  125. "PE22-014 to investigate allegations of Automated Driving System (ADS) equipped vehicles operated by Cruise LLC (Cruise) becoming immobilized while operating in the specified Operational Design Doman (ODD)" (PDF). National Highway Traffic and Safety Administration. January 4, 2023. Retrieved February 1, 2023.
  126. San Juan, Diana (August 18, 2023). "California DMV asks Cruise to reduce number of driverless cars in San Francisco". NBC Bay Area. Retrieved October 24, 2023.
  127. Liedtke, Michael (October 4, 2023). "California regulators suspend recently approved San Francisco robotaxi service for safety reasons". AP News. Retrieved October 24, 2023.
  128. Haugh, Thomas (October 16, 2023). "ODI Resume: PE 23-018" (PDF). National Highway Traffic and Safety Administration. Archived from the original (PDF) on October 17, 2023.
  129. Chapman, Michelle (October 17, 2023). "US regulators investigate GM's Cruise division over incidents involving pedestrians in roadways". AP News. Retrieved October 24, 2023.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.