Direct Answer
When reviewing VPP, demand-response and load-aggregation projects, what checklist actually tells you whether a park "can really be dispatched"? Use the "Five Can's" to accept resources one by one — observable (status is visible), measurable (accuracy is enough for settlement), adjustable (an actuating mechanism exists), controllable (dispatch commands close the loop) and trustworthy (data is auditable); if any of the five is missing, that resource cannot enter the VPP aggregation pool. The "Five Can's" is the acceptance checklist for energy data infrastructure — check resource by resource, and send one back when an item is missing — only when all five pass is a resource truly "dispatchable and settleable".
A scene: a park says "we have installed meters and can report data" — the acceptance found meters but no switching — "observable but not controllable" — this resource cannot enter the VPP aggregation pool.
1. Why the "Five Can's" Are Needed
The pain point of aggregation — many contracted resources but few truly dispatchable: reporting capacity is easy, being dispatched is hard — an acceptance checklist is missing; The role of the checklist — accepting resources one by one: entering the pool only when all five pass — turning "paper resources" into "dispatchable resources"; The meaning of the Five Can's — observable, measurable, adjustable, controllable and trustworthy: checking from status to data item by item — the whole chain passes; The price of a missing item — five minus one means no entry: one resource missing one item — failing at dispatch time; The value of the checklist — acceptance with evidence: no gut feeling and no discounts — with all five passing, the resource counts.
In one sentence: the Five Can's is the acceptance checklist for energy data infrastructure — check resource by resource and enter the pool only when all five pass — with one missing, the resource cannot enter the aggregation pool.
A demand example — a project reported 30 resources — after acceptance, 18 passed all five — the pooled resources were counted as 18. Without the Five Can's, acceptance is by gut feeling — a few meters installed count as done — with the checklist, resources truly count.
2. Observable: Status Is Visible
The meaning of observable — status visible in real time: running, stopped and faulted — dispatch can see the resource status; The measurement points of observable — switch status and operating parameters: tele-indication and tele-measurement — status digitized; The scene of observable — check the status before dispatch: can this resource be regulated now — visible before deciding; The absence of observable — a status blind spot: meters installed but status not visible — dispatch dares not use it; The acceptance of observable — open the platform and see the status: real-time and accurate — status visible, observable passes.
In one sentence: observable = status visible in real time (tele-indication + tele-measurement) — dispatch can see the resource status — visible, then dare to dispatch.
An observable example — a project installed meters but did not report status — "invisible" — tele-indication added before observable passed. The pitfall of observable is "only meters, no visible status" — with status visible, dispatch dares to use it.
3. Measurable: Accuracy Enough for Settlement
The meaning of measurable — measurement accuracy enough for settlement: error and completeness qualified — the data can be used for settlement; The measurement points of measurable — meter accuracy and collection period: no gaps and no losses — reliable measurement; The scene of measurable — settlement looks at accuracy: error exceeding the limit — data not credible and not settleable; The absence of measurable — insufficient accuracy: the reading is a "reference value" — settlement does not recognize it; The acceptance of measurable — sample the measurement data: error within the red line and high completeness — accuracy enough, measurable passes.
In one sentence: measurable = measurement accuracy enough for settlement (error + completeness qualified) — data usable for settlement — with accuracy enough, data counts.
A measurable example — a project at 78% accuracy failed the standard — settlement discounted — meters upgraded to 95% before it passed. The pitfall of measurable is "meters installed but accuracy insufficient" — with accuracy enough for settlement, measurable passes.
4. Adjustable: An Actuating Mechanism Exists
The meaning of adjustable — an actuating mechanism that can act: switching, voltage regulation and load shedding — the resource can execute commands; The mechanisms of adjustable — the operating mechanisms of switches and breakers and storage PCS: devices that can act — executing commands; The scene of adjustable — dispatch wants to regulate this resource: the mechanism can act — commands have a landing point; The absence of adjustable — only monitoring, no execution: meters installed but no switching — visible but immovable; The acceptance of adjustable — remote-control test: remote switching and regulation — the mechanism can act, adjustable passes.
In one sentence: adjustable = an actuating mechanism exists (switching / voltage regulation / load shedding) — the resource can execute commands — movable, then dispatchable.
An adjustable example — a resource had meters but no switching — "visible but immovable" — an actuating mechanism added before it passed. The pitfall of adjustable is "only monitoring, no execution" — with the mechanism acting, the resource is adjustable.
5. Controllable: Dispatch Commands Close the Loop
The meaning of controllable — dispatch commands close the loop: command issued, executed and acknowledged — dispatch knows the command result; The chain of controllable — the command issued to the actuating mechanism: status returned after execution — closed-loop confirmation; The scene of controllable — dispatch issues a "shed" command: the mechanism acts and the status returns — the loop closes; The absence of controllable — commands issued without acknowledgement: not knowing whether the mechanism moved — dispatch has no certainty; The acceptance of controllable — closed-loop command test: issue, execute and acknowledge in three steps — the loop complete, controllable passes.
In one sentence: controllable = dispatch commands close the loop (issue → execute → acknowledge) — dispatch knows the command result — with the loop closed, dispatch has certainty.
A controllable example — a project issued commands without acknowledgement — "regulated but not knowing whether it moved" — status return added before the loop passed. The pitfall of controllable is "command issued, result unknown" — issue, execute and acknowledge in a loop — then controllable passes.
6. Trustworthy: Data Is Auditable
The meaning of trustworthy — data auditable: source, timestamp and chain traceable — the data can withstand inspection; The elements of trustworthy — consistent timestamps and a complete chain: no fabrication and no packet loss — the audit can pass; The scene of trustworthy — settlement reconciliation: how much was dispatched and how it was calculated — auditable data settles; The absence of trustworthy — a black-box data chain: the source unprovable — settlement disputes; The acceptance of trustworthy — sample the data chain: source, timestamp and completeness — auditable, trustworthy passes.
In one sentence: trustworthy = data auditable (source + timestamp + chain traceable) — data withstands inspection — auditable, settlement without disputes.
A trustworthy example — a project's data chain was unclear — the settlement did not reconcile — timestamps and chain completed before it passed. The pitfall of trustworthy is the "data black box" — with source, timestamp and chain traceable, the data is trustworthy.
7. The Typical Pitfalls of "Seemingly All Five, Actually Missing One"
Pitfall one: meters installed but no switching — observable and measurable present, adjustable missing — "visible but immovable"; Pitfall two: data can be reported but dispatch cannot be accepted — the data chain works and the control chain is broken — "reported but not dispatchable"; Pitfall three: an actuating mechanism without acknowledgement — adjustable present, controllable missing — "moved but not knowing whether it moved"; Pitfall four: accuracy enough but data not auditable — measurable present, trustworthy missing — "data cannot withstand inspection"; Pitfall five: all five look present but the linkage was never tested — single items present, the system not verified — "failing when combined".
In one sentence: the pitfalls of the Five Can's = meters without switching (not adjustable) + reportable but not controllable + movement without acknowledgement + measurable but not auditable + present but not linkage-tested — check item by item, send one back when missing.
A pitfall example — a project had all five individually — the linkage test found controllable missing — the loop added before it passed. Acceptance needs "item-by-item checking and linkage testing" — single items do not count — with all five passing and the linkage verified, the resource enters the pool.
8. Back to FEXLINK: The On-Site Acceptance Checklist of the Five Can's
FEXLINK's "Five Can's" acceptance of energy data infrastructure: observable status, measurable accuracy, adjustable mechanism, controllable loop and trustworthy audit — accept resource by resource, and no entry when one of the five is missing. The on-site checklist: ① observable — open the platform and see the status: tele-indication and tele-measurement real-time and accurate → ② measurable — sample the measurement accuracy: error within the red line and completeness qualified → ③ adjustable — remote-control test: switching and voltage regulation can act → ④ controllable — closed-loop command test: issue, execute and acknowledge complete in three steps → ⑤ trustworthy — sample the data chain: source, timestamp and completeness traceable — with all five passing, the resource enters the VPP aggregation pool.
One summary: the Five Can's = observable (status seen) + measurable (accuracy enough) + adjustable (mechanism acts) + controllable (commands close the loop) + trustworthy (data auditable) — five minus one, no entry into the pool. Accept with a checklist, not by gut feeling — all five passing and the linkage verified — the resource is truly dispatchable and settleable.
One reminder: when reviewing a VPP project, do not only look at "how many meters were installed" — run the resource through the Five Can's one by one: observable? measurable? adjustable? controllable? trustworthy? — with all five passing, the capacity is real. The "Five Can's" is both an acceptance checklist and a negotiation checklist — check item by item and send one back when missing — after the five, the resource enters the aggregation pool.
Scope and Limitations
- The conclusions in this article are intended for LV distribution and electrical-safety sites. Criteria are compiled from public codes and FEXLINK product documentation, and product parameters follow the latest selection handbook and product knowledge base.
- Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated.
- Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
- Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
- Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.
Frequently Asked Questions
The "Five Cans"
When reviewing VPP, demand-response and load-aggregation projects, what checklist actually tells you whether a park "can really be dispatched"