SaaS / Enegaeru EV & V2H · Kokusai Kogyo
Show what a BEV and V2H can change at home.
Compare battery electric vehicles, charging and vehicle-to-home with rooftop solar, stationary batteries and Japanese household energy costs.
Make the BEV and V2H business case specific to Japan.
A battery electric vehicle (BEV) can change both mobility costs and household electricity demand. Vehicle-to-home (V2H) adds another decision: when and how the vehicle battery is available to supply the home.
For automakers, charging providers, homebuilders and energy retailers, compare driving patterns, charging timing, electricity tariffs, rooftop solar and stationary batteries within the supported scope. Explain the assumptions behind household energy-cost changes, rather than treating the vehicle battery as always available.
Use the EV TCO service for vehicle ownership-cost comparisons, and BizEV for commercial fleet and facility scenarios. Vehicle compatibility, charging hardware, battery use and V2H operating limits must be confirmed for the actual system.
Vehicle total cost of ownership → · Commercial fleets and site energy →
Designed for your team’s work
Automakers; vehicle dealers; charger and V2H manufacturers; installers; energy retailers.
What you bring
- Driving distance and energy use
- charging and home-connection times
- household demand
- tariff
- solar, storage and V2H configuration
What you can evaluate or receive
- Compare household and mobility energy costs
- evaluate equipment combinations
- explain the assumptions behind each option
A practical first evaluation
Choose a realistic weekday and weekend usage pattern. Compare charging-only and V2H scenarios with the same household and vehicle assumptions.
Scope to confirm
Vehicle availability, compatible equipment, conversion losses and operation determine the result. Economic simulation is separate from live charging control and emergency-power engineering.
A view of the product
Before you commit
Can we use this as part of our Japan launch?
Tell us your customer segment, local operating model and first use case. We will discuss product fit and any additional data, integration, training or specialist work required.
Is the software or delivery available in English?
This page is an English introduction. Confirm interface, documentation, report and support languages for the product or engagement. Bilingual outputs and localization should be specified explicitly.
How are commercial terms agreed?
Request a quotation for the product, users or usage, data rights, scope and support you need. Confirm implementation fees, recurring fees, contract term and any project work before ordering.
Product information and related routes
Bring us the next decision you need to make.
Tell us what you want to launch in Japan, who will use it, and where the work is getting stuck. We can discuss the right combination of software, APIs, data and specialist support.