A-Charge
Why this design

Parking after generation, storage, and mobility disperse

Suomi Masuda (益田周防海) / I-S3 Co., Ltd.

Solar PV spreads generation across many sites. Batteries spread the ability to store power. EVs are transport—and also large batteries and demand that show up in many places. As those grow together, the practical question shifts from “how do we fully charge one car?” to “how do many vehicles and devices share a limited intake?” A-Charge is designed around that question.

What solar sites already taught

In solar work, interconnection, contracted capacity, 30-minute demand, and self-consumption often matter before panel count. Adding equipment does not remove the intake limit. “Everything at full output” can be written on paper and still fail on site. Monitoring and O&M are about the whole power and operations picture, not only individual devices.

EV growth brings the same structure to parking

Put chargers in a lot and the same structure appears bay by bay. More ports can grow demand; the facility power contract does not grow as easily. Some sites need a few DC stalls; others want wide AC coverage. Either way, once many units run at once, the question is who goes next and how much output each may use.

The question moves

What A-Charge implements today

The public A-Charge product is built as follows. We keep this to what is implemented—not a future roadmap mixed in.

Every bay on the same QR

Bays with or without a charger share the same intake and time-based parking fees. It is not designed as a special EV corner only.

No driver app

Scan the bay QR to start (NO APP.). Membership is not required.

Load sharing under the intake limit

Set the site intake limit and simultaneous charging is auto-allocated so the total stays under contract. Growing port count and raising contracted power stay separable.

Anonymous queueing (RightOS)

Busy-time order and usage rights use our RightOS. No names or phone numbers—only whether a valid right is present. RightOS is rights verification, not dispatch or a universal OS.

No gates or flaps required

Operations can start without new physical locks (NO LOCKS. NO CONES.). Different capital setups can still begin on the software side.

Kept separate as option / concept

Combining solar or storage with parking—self-consumption and disaster supply included—is covered on another page. Those ideas are not treated as mandatory A-Charge features. Read implementation and concept apart.

Read the resilience hub (solar × storage) →

Who is writing

The author is Suomi Masuda (益田周防海), Representative Director of I-S3 Co., Ltd. The company works in solar, EV installation, and software, and develops and operates A-Charge and RightOS. This article records design reasons—not a feature brochure.

Current-work profile →

A-Charge as a parking OS

Rollout conditions and fees are on the owners pages.

Owners guide Read the FAQ

A-Charge Talk to us about installing
027-384-4646Call us (weekdays 9:00-18:00 JST) Chat with us24h · AI answers first (i-s3.com)