METRO POWERMetro Power Academy lessonPlan a project ↗

EV Charging InfrastructureLesson 4 of 5FOUNDATION LESSON

Site works, software and charging operations

A dependable charging site combines electrical work with parking layout, foundations, bollards, drainage, trenching, lighting, accessibility, communications, signage and vehicle circulation.

READING TIME
13 minutes
OBJECTIVES
3 learning objectives
SELF-CHECK
3 check questions
INTENDED FOR
Fleet, property, utility, engineering and charging-operations teams

Educational lesson. Confirm project-specific requirements before application.

Integrated DC fast charger with a pedestal unit (product render)
Manufacturer renderIntegrated DC fast charger

01LEARNING OBJECTIVES

After this lesson, you should be able to:

  1. 01Build the whole-site scope beyond charger supply
  2. 02Define uptime, access, payment and support ownership
  3. 03Recognize civil, safety and permitting dependencies

02EXPLANATION

What is physically and operationally happening?

A dependable charging site combines electrical work with parking layout, foundations, bollards, drainage, trenching, lighting, accessibility, communications, signage and vehicle circulation. These scopes can outweigh charger hardware cost, especially where transformer or service upgrades are required.

Software supports authentication, pricing, session records, monitoring, remote support and load management. Protocol support such as OCPP can enable integration, but it does not prove that every charger, backend, firmware and business workflow behaves correctly together. Exact combinations must be tested.

  1. 01

    Arrive

    Driver finds an available, accessible and safe charging bay.

    Access
  2. 02

    Authorize

    Site validates the user, vehicle, account or permitted charging method.

    Session start
  3. 03

    Charge

    Electrical and software systems deliver and record controlled energy.

    kWh + status
  4. 04

    Support

    Faults, payments, parking and customer questions reach accountable responders.

    Uptime
READING NOTEConceptual service architecture. Protocol, payment and personal-data obligations depend on the selected operating model and jurisdiction.
TECHNICAL VISUAL · SYSTEM-SPECIFIC MODEL

Charging service architecture

The physical and digital service must work from arrival through payment, charging and support.

Three vehicles connected. The earliest departure keeps full power and the others share what remains, so the site holds at its limit instead of reaching 150 percent.

  • AC power
  • Control and data
  • Power flowing, arrow shows direction
Illustrative arrangement, not a Metro Power project. Supplied equipment appears as Bescore renders and studio photographs of the equipment class; the grid, generation, buildings, vehicles and control equipment are drawn.
04OPTIONAL ENGINEERING DEPTHEngineering reasoning for this learning pathThe same design relationship, checks and evidence apply across every lesson in this path.
DESIGN RELATIONSHIPAllocated charging demand ≤ verified site charging cap while each priority vehicle meets its energy deadline
  • Separate connected load from controlled demand
  • Include existing site peak and reserve margin
  • Respect vehicle acceptance, arrival and departure
ENGINEERING CHECKS FOR THIS PATH
  1. 01Build the single-line diagram from utility service to connector
  2. 02Run vehicle-energy and managed-allocation scenarios
  3. 03Test controller fallback when communications or site metering fails
FAILURE ANALYSIS
Observed signalPossible causeDiscriminating test

Site peak exceeds the enforced cap

Control latency, stale data or unmanaged charger

Compare meter, controller and charger timestamps

Vehicles miss departure targets

Allocation ignores energy deadline

Replay arrivals, initial state of charge (SOC) and priorities

PROJECT EVIDENCE TO COLLECT
  • Vehicle schedule and session traces
  • Site interval load and capacity study
  • Controller logic and fallback test

05WORKED EXAMPLE

A technically working charger that customers cannot use

A public charger energizes correctly, but mobile authentication fails and no support number is displayed.

STEP BY STEP
  1. Classify the site as not operationally accepted
  2. Test the complete user journey and fallback access
  3. Assign fault, payment and customer-support ownership
  4. Set uptime and incident-response measures
INTERPRETATION

Electrical output alone does not constitute a dependable charging service.

06COMMON FAILURE OR MISCONCEPTION

“OCPP support proves complete charging-site interoperability.”

CORRECTION

It indicates a protocol capability. Exact messages, profiles, versions, backend behavior, load control and business workflows still require implementation testing.

RETRIEVAL PRACTICE · 3 QUESTIONS

Check what you can explain without looking back.

Choose an answer and report your confidence. The confidence signal is stored only until you submit this page.

OBJECTIVE · Build whole-site scope

Which item can be a major EV project cost?

How confident are you?
OBJECTIVE · Interpret protocol support

What does OCPP support establish?

How confident are you?
OBJECTIVE · Define acceptance

A charger outputs power but access and support fail. Status?

How confident are you?
Answer every question and confidence prompt.

08SOURCE NOTES

Sources for further study.

International references support further study. They do not replace Philippine laws, regulations, utility requirements or project specifications.

  1. 01State and Local Planning for EV Charging InfrastructureUS Department of Energy Alternative Fuels Data Center

    Charging infrastructure planning framework.

    Open source ↗
  2. 02Open Charge Point ProtocolOpen Charge Alliance

    Current OCPP versions and capabilities.

    Open source ↗
  3. 03EVCS Provider Obligations and EVCS Requirements, Specifications and InterconnectivityPhilippine Department of Energy

    Primary Philippine EVCS implementation context.

    Open source ↗
Read the complete technical paper

NEXT IN THIS COURSELesson 5 of 513 minutes

Feasibility, economics and phased rollout