METRO POWEREvidence controlsPlan a project ↗
Accountable local delivery
Metro Power connects principal technology to Philippine project realities while keeping technical claims, commercial commitments and delivery responsibilities explicit.
Every station on the verification chain refers to equipment like the meter above. Serial, model and configuration are what get checked.
01HOW A COMMITMENT IS CONTROLLED
Each step keeps the source, product, responsibility and acceptance condition visible before Metro Power makes a project commitment.
Stations 03 to 06 · Product images
02HOW METRO POWER PROTECTS THE PROJECT
The map above is the route. These are the same six stations, opened one at a time, so you can read what each station checks and the record it hands to the next team.
See the four engagements and what each one gives youSIX STATIONS · SELECT ONE TO OPEN ITS CONTROL
Begin with the current terms of reference (TOR), site data, operating objective and responsible decision, not an assumed or superseded scope.
Controlling revision, issuer, deadline and decision owner identified.
Before anything here is published: principal deployments are not presented as Metro Power installations, and targets are not presented as measured outcomes. Attribution, approval, scope, period and release authority are verified first, and the result is an approved claim record. Read the claim release gate on the proof page ↗
03Document controls
This is not a separate scheme. These are the four documents that carry the evidence, and each one is tagged with the level it sits at in the five evidence levels defined on the proof page. A document is shown only after its scope and release status are confirmed. Until then, no logo, project, authorization or certificate is treated as current.
Read the five evidence levels on the proof pagePublished only with client approval and a defined Metro Power scope.
Authorization letters and appointment scope shown only while current and verified.
Certificate, issuing body, model coverage and validity matched before presentation.
Factory, type and project tests kept distinct with their dates and applicable models. A test published by a principal sits at level 03; a test carried out on a Metro Power project sits at level 04.
04After-sales pathway
Record the equipment, serial, configuration and symptom.
Collect photos, logs, timestamps and operating conditions.
Separate installation, communications, firmware and integration causes.
Escalate to the responsible local or principal team with complete evidence.
Confirm action, owner, result and closure record.
Discuss the next controlled step