Software in the EV space is a super wide topic. There's OCPP, which allows us to control chargers. OCPI, which allows us to publish available public chargers on various networks. ISO-15118, which gets more nitty-gritty and allows us to receive data from both chargers and vehicles. And a ton more - it's a world of acronyms and standards and protocols, but at the end of the day, we have node apps in kubernetes clusters controlling distributed physical hardware (the chargers). We're solving some interesting problems - EV charger comms go over cell networks, so there's connectivity problems built right in. Chargers hold onto data while offline, but that amount of data varies and runtime decisions have to be made when a charger comes back online. I could probably talk for days about the whole problem space, but a high-level primer may make more sense for this talk. My teams specifically build software that manage the flow of energy to electric vehicles. We have fleets of thousands of chargers across the globe, which we maintain direct websocket connections to and control via a protocol called OCPP. Last year, we also launched the first OEM public charging network (Ford Charge Network), which allows the general public to charge their EVs at various locations across the US and Canada. There are a ton of other features we've built - power company integrations to help charge cheaply, complex authorization logic to determine whether a vehicle should be able to charge at a specific charger, EV route planning to ensure the vehicle receives enough energy before departure, provisioning systems for tracking the physical charger's lifecycle from manufacturing to installation to eventual decommissioning. Faults and error states, ton of reporting (built on kafka with the event-sourcing paradigm). I'm excited to talk about the EV charging ecosystem and the role software plays in that - chargers talk to vehicles, chargers and vehicles talk to our central systems, our systems talk to utilities, payment providers, public charging networks, etc. and all this is enabled by software. About Jake Hendley - Greenville, SC Senior Director of Engineering @ Ford Pro Socials - https://www.linkedin.com/in/jake-hendley-ab685151/ - http://jakehendley.com/ - https://www.fordpro.com/en-us/charging/ A bit about me - I'm a Greenville native and spent years working out of Openworks and arranging as many happy hours as possible. Over the last 4 years, I've gone from the first US engineering hire at a small startup in the bay area to leading an engineering org at Ford Motor Company. That small bay area startup was acquired by Ford in 2021, and we've been building cool stuff ever since. Presented on August 16, 2025 at the Carolina Code Conference in Greenville, SC https://carolina.codes Sponsored by... Vonage - https://developer.vonage.com/en/home Flywheel - https://www.flywheelgreenvillesc.com/ Times 20 Consulting - https://x20.io/ Organized by Brightball, Inc - https://www.brightball.com/

ジゴワッツとeMotion Fleetが、OCPP 1.6対応によるEV充電器と運行・エネルギー管理システムの連携検証を完了。

YouTube video by Dave Cadaqu

YouTube video by Dave Cadaqu

Software in the EV space is a super wide topic. There's OCPP, which allows us to control chargers. OCPI, which allows us to publish available public chargers on various networks. ISO-15118, which gets more nitty-gritty and allows us to receive data from both chargers and vehicles. And a ton more - it's a world of acronyms and standards and protocols, but at the end of the day, we have node apps in kubernetes clusters controlling distributed physical hardware (the chargers). We're solving some interesting problems - EV charger comms go over cell networks, so there's connectivity problems built right in. Chargers hold onto data while offline, but that amount of data varies and runtime decisions have to be made when a charger comes back online. I could probably talk for days about the whole problem space, but a high-level primer may make more sense for this talk. My teams specifically build software that manage the flow of energy to electric vehicles. We have fleets of thousands of chargers across the globe, which we maintain direct websocket connections to and control via a protocol called OCPP. Last year, we also launched the first OEM public charging network (Ford Charge Network), which allows the general public to charge their EVs at various locations across the US and Canada. There are a ton of other features we've built - power company integrations to help charge cheaply, complex authorization logic to determine whether a vehicle should be able to charge at a specific charger, EV route planning to ensure the vehicle receives enough energy before departure, provisioning systems for tracking the physical charger's lifecycle from manufacturing to installation to eventual decommissioning. Faults and error states, ton of reporting (built on kafka with the event-sourcing paradigm). I'm excited to talk about the EV charging ecosystem and the role software plays in that - chargers talk to vehicles, chargers and vehicles talk to our central systems, our systems talk to utilities, payment providers, public charging networks, etc. and all this is enabled by software. About Jake Hendley - Greenville, SC Senior Director of Engineering @ Ford Pro Socials - https://www.linkedin.com/in/jake-hendley-ab685151/ - http://jakehendley.com/ - https://www.fordpro.com/en-us/charging/ A bit about me - I'm a Greenville native and spent years working out of Openworks and arranging as many happy hours as possible. Over the last 4 years, I've gone from the first US engineering hire at a small startup in the bay area to leading an engineering org at Ford Motor Company. That small bay area startup was acquired by Ford in 2021, and we've been building cool stuff ever since. Presented on August 16, 2025 at the Carolina Code Conference in Greenville, SC https://carolina.codes Sponsored by... Vonage - https://developer.vonage.com/en/home Flywheel - https://www.flywheelgreenvillesc.com/ Times 20 Consulting - https://x20.io/ Organized by Brightball, Inc - https://www.brightball.com/

YouTube video by Dave Cadaqu

YouTube video by Foreign Press Association USA

YouTube video by Foreign Press Association USA

Software in the EV space is a super wide topic. There's OCPP, which allows us to control chargers. OCPI, which allows us to publish available public chargers on various networks. ISO-15118, which gets more nitty-gritty and allows us to receive data from both chargers and vehicles. And a ton more - it's a world of acronyms and standards and protocols, but at the end of the day, we have node apps in kubernetes clusters controlling distributed physical hardware (the chargers). We're solving some interesting problems - EV charger comms go over cell networks, so there's connectivity problems built right in. Chargers hold onto data while offline, but that amount of data varies and runtime decisions have to be made when a charger comes back online. I could probably talk for days about the whole problem space, but a high-level primer may make more sense for this talk. My teams specifically build software that manage the flow of energy to electric vehicles. We have fleets of thousands of chargers across the globe, which we maintain direct websocket connections to and control via a protocol called OCPP. Last year, we also launched the first OEM public charging network (Ford Charge Network), which allows the general public to charge their EVs at various locations across the US and Canada. There are a ton of other features we've built - power company integrations to help charge cheaply, complex authorization logic to determine whether a vehicle should be able to charge at a specific charger, EV route planning to ensure the vehicle receives enough energy before departure, provisioning systems for tracking the physical charger's lifecycle from manufacturing to installation to eventual decommissioning. Faults and error states, ton of reporting (built on kafka with the event-sourcing paradigm). I'm excited to talk about the EV charging ecosystem and the role software plays in that - chargers talk to vehicles, chargers and vehicles talk to our central systems, our systems talk to utilities, payment providers, public charging networks, etc. and all this is enabled by software. About Jake Hendley - Greenville, SC Senior Director of Engineering @ Ford Pro Socials - https://www.linkedin.com/in/jake-hendley-ab685151/ - http://jakehendley.com/ - https://www.fordpro.com/en-us/charging/ A bit about me - I'm a Greenville native and spent years working out of Openworks and arranging as many happy hours as possible. Over the last 4 years, I've gone from the first US engineering hire at a small startup in the bay area to leading an engineering org at Ford Motor Company. That small bay area startup was acquired by Ford in 2021, and we've been building cool stuff ever since. Presented on August 16, 2025 at the Carolina Code Conference in Greenville, SC https://carolina.codes Sponsored by... Vonage - https://developer.vonage.com/en/home Flywheel - https://www.flywheelgreenvillesc.com/ Times 20 Consulting - https://x20.io/ Organized by Brightball, Inc - https://www.brightball.com/