A few DC stalls, or make the whole lot EV-ready? Force a membership app, or finish with a bay QR? A-Charge® is the latter — simple checkout including AC chargers, designed as a parking OS for every bay.
Sites with longer stays benefit most from AC charging and time-based fees.
DC is costly and often needs a higher contracted demand. Where cars already stay (hotel, office, shopping), including AC usually balances cost and utilization. A-Charge’s wedge is simple checkout that includes AC.
Apps and sign-ups lose tourists and first-time visitors. A-Charge: bay QR → rates → card / Apple Pay / Google Pay (NO APP.). If you already have a facility app, queueing can optionally plug into the RightOS public API.
A small DC corner is a “charging spot.” As a parking OS, bays with and without chargers share the same intake and checkout — including timed parking for gasoline cars — so revenue depends less on EV adoption speed.
A parking OS on Google Cloud: payments, charge control, queueing, power sharing, and monitoring in one design.
Revenue and payback depend on location, occupancy, and rates — we do not guarantee them. Ballpark only:
Share use case, power intake, and target ports. Installation by I-S3 (and partners).
Rates, bay QR, load-share cap. You can start with time billing on bays without chargers.
Attach chargers over OCPP; place bay QR stickers.
Adjust time-band rates and add ports later. Cloud-side monitoring continues.
National and local EV charger subsidies depend on facility type, year, and equipment rules (e.g. OCPP). We do not guarantee approval or amounts. I-S3 helps sort eligibility against site conditions.
One residential or small-office install: I-S3 (i-s3.com/ev). Multi-bay billing and operations: A-Charge (this guide and /owners).
Start on the owners page — a conversation is enough.
Owners page FAQ Installation (I-S3)