Highway corridor DC fast charging
Most networks meet their compliance obligations after the award. We built ours first.
Ridgemont Charging Solutions develops and operates DC fast charging along Western freight and travel corridors — and runs it on charging management software we wrote ourselves, audited line by line against every requirement in the federal rule.
A Ridgemont Energy Capital company · Meridian, Idaho.
0Part 680 requirements audited against our own code
0OCPP versions supported — 1.6J and 2.0.1
0Per-port annual uptime the rule requires, measured its way
0Third-party network fees between us and the data
What we do
Two halves of the same job — and the second one is where most charging projects come apart.
01 / DEVELOP
We find the site and put the deal together
Corridor screening and siting, host negotiation and site control, utility service and make-ready coordination, incentive and grant strategy, application drafting, and assembling the capital stack. By the time equipment is ordered, the funding, the interconnection and the land are already solved.
02 / OPERATE
Then we run it, and stand behind the numbers
Network operation for the life of the asset: session management and settlement, driver support, availability monitoring, preventive and corrective maintenance dispatch, and every report the funding agency requires — filed on time, from data the platform captures automatically rather than reconstructs later.
23 CFR Part 680
Federal compliance is a software problem long before it is a paperwork problem.
Uptime has to be measured per port on the formula the regulation specifies, with excluded outages evidenced at the time they happen. Reporting has to come out in a prescribed schema on a fixed calendar. Neither can be reconstructed at the deadline from a vendor dashboard. We read all 83 requirements of the rule against our own codebase and built what was missing.
§ 680.116(b)
Uptime on the federal formula
Per-port availability computed as the rule defines it, across 525,600 minutes, with excluded-outage reason codes recorded against each event as it occurs.
§ 680.116(b)(2)
“Up” means able to dispense
A port counts as available only when it can actually deliver power — not merely when its network connection is alive. Faults and derating count against it.
§ 680.112
EV-ChART reporting
Quarterly and annual submittals generated directly from operating data, validated against the schema, with due dates computed rather than remembered.
§ 680.116(c)
Open public data
Station, port, pricing and real-time status published on a free, unauthenticated feed — no key, no registration, no rate limit.
§ 680.114
Sessions survive an outage
Authorization lists are pushed to chargers ahead of time, so drivers can still start and finish a session when the site loses its network link.
§ 680.114(a)
Authenticated charger links
OCPP security profiles 2 and 3, with each charger’s certificate bound to its own identity — a valid certificate issued to a different unit is refused.
§ 680.108
Roaming and interoperability
OCPP 1.6J and 2.0.1 to the hardware, OCPI 2.2.1 to other networks, so a driver’s existing credential works at our stalls.
§ 680.106(c)(1)
Pay without an app
Contactless card at the charger, plus a toll-free and text-message path that starts and pays for a session — the requirement most operators skip.
§ 680.106(c)(4)–(5)
Accessible and bilingual
Driver screens in English and Spanish, built to WCAG 2.1 AA — measured contrast, screen reader support, and keyboard operation, not an accessibility badge.
The platform
We own the charging management software, so compliance is a feature and not a vendor request.
Most operators lease their network software and inherit whatever it happens to record. When a regulator asks for something the vendor does not capture, the answer is a support ticket and a wait. Ours is built in house, which means the reporting obligations were designed in rather than bolted on.
Session & settlement
Metering, itemized pricing, pre-authorization holds, refunds, and printable receipts.
Availability ledger
Per-port outage records with cause codes and evidence, retained for the reporting period.
Load management
Site power shared across active sessions without dropping any port below its committed rating.
Roaming
OCPI 2.2.1 locations, tariffs, sessions, CDRs and remote commands with partner networks.
Driver support
Web, contactless, and a toll-free and SMS path for drivers without a smartphone or an account.
Regulatory export
EV-ChART modules and low-carbon fuel credit reporting for the Oregon CFP and California LCFS.
For site owners and co-investors
One counterparty from the first site visit to the last compliance filing.
We take charging sites from an idea about a parcel through to an operating asset, and stay on as the network operator. Host landowners keep their land and their traffic. Co-investors get an operator whose reporting obligations are already engineered.
- Screen and siteCorridor eligibility, traffic, utility capacity and interconnection cost.
- Secure the siteHost terms, option or lease, and the site control an application requires.
- Fund itGrant and incentive strategy, application drafting, and the capital stack.
- Build itEquipment selection, qualified installers, utility make-ready and commissioning.
- Operate itNetwork operation, driver support, maintenance dispatch and every required filing.
Contact
Talk to us about a site, a corridor, or an application deadline.
- Offices
- Meridian, Idaho
- Operating region
- Idaho · Oregon · California · Nevada