Choose your language

EnglishEspañolPortuguêsFrançais日本語DeutschItalianoالعربيةБеларускаяአማርኛУкраїнськаÍslenskaMagyarAfrikaansČeštinaCymraegHrvatskiMāoriРусскийKiswahiliBosanskiCatalàGalegoGàidhligБългарскиLietuviųTiếng ViệtCebuanoລາວМонголမြန်မာខ្មែរFilipinoBahasa MelayuગુજરાતીBasa JawaTürkçeAzərbaycanՀայերեն繁體中文Euskara简体中文DanskNederlandsहिन्दीSuomiBahasa IndonesiaGaeilgeҚазақшаNorskPolskiRomânăСрпскиSvenskaไทย한국어עברית

Explore TTH Pergola

TTH PERGOLA

Blog

Solar canopy decisions

Launching Public Solar Charging: Payment, Connectivity and Support

Test public solar charging through complete user journeys, covering payment, connectivity, fault messages and support before launch.

Concept solar parking canopy with an unbadged car, open door, empty wheelchair in a side transfer area and a clear route toward a plain charging pedestal.
Concept illustration: Concept solar parking canopy with an unbadged car, open door, empty wheelchair in a side transfer area and a clear route toward a plain charging pedestal.

Accept the service through the user journey

Begin acceptance when a user tries to find the site, not after someone has already connected a vehicle. Entrance information, bay signs, opening hours and vehicle restrictions should match online listings. Users must understand prices, identify an available charger, complete access or payment steps, and start and end a session. Canopy appearance and solar production do not replace these checks. Facilities, operations and the provider should walk through the journey together, recording photographs, times and equipment identifiers so that completed scope is understood consistently.

Check both successful and failed interactions

Use payment methods actually offered by the project, checking displayed fees, authorization, session closure and receipts rather than relying on the supplier's internal account. Document behavior after loss of mobile or site connectivity and how backend status corresponds to the device. DOE public charging guidance supports considering networks, payment and operations; local teams must establish applicable payment and data obligations. Conduct trials under an agreed test process so charges can be reconciled, retaining records for test settlements or refunds rather than generating unexplained transactions.

  • Check pricing, start, stop and receipts.
  • Test connection loss and status synchronization.
  • Verify support can locate the equipment by its identifier.

Include faults in launch preparation

Imagine a commercial lot where equipment is powered but scanning a code leaves the user on an unresponsive page. A generic brand label is insufficient if support cannot identify the site or unit. Test messages for failed starts, connection problems and unavailable equipment, ensuring staff can locate the charger and provide an actionable next step. Electrical safety concerns should trigger stopping use and contacting qualified personnel, not instructions for users to open equipment. This scenario tests the support process and is not a claim about a particular brand's defect.

Hand over responsibilities and outstanding items

Before opening, assign equipment maintenance, payment disputes, networking, on-site management and online information, with contacts for urgent and routine issues. Record outstanding items by impact; solar generation alone does not complete charging acceptance. Handover should include an equipment register, account permissions, service contracts and update instructions rather than leaving operators dependent on an installer's personal login. Review failed sessions and support records after an agreed operating period. Any availability commitment needs a defined calculation boundary, exclusions and contractual responsibility.

Is a powered, online charger ready for public opening?

Further service checks are needed. Verify discovery, pricing, successful starts and stops, receipts, connection failures and support identification. Record unresolved issues and owners, then assess readiness against the project's safety, operational and local requirements.

More questions, practical answers →

Continue planning

Topics

User journeyPayment evidenceFault support
View system details →Contact TTH
← Blog

Privacy