Confirm controlled versions, configurations and prerequisites.
A.M.P.E.R.E. TOOLKIT · ANNEX G
Acceptance Testing and Validation
Tests end-to-end function, communications, data, security, billing and readiness.
A decision instrument, not a paperwork exercise.
Verify that the complete AMI operating chain performs as specified and that exceptions are resolved through controlled evidence.
Start with uncertainty.
Use the annex to make the decision and its missing evidence visible before discussing a preferred product or schedule.
- 01Do devices, communications, HES, MDMS and integrations work together?
- 02Are reads, events, commands and billing transfers accurate and traceable?
- 03Are security, privacy, field and customer-service controls functioning?
- 04Who accepts defects, retests and residual risks?
Required inputs
- Approved pilot and acceptance plan
- Controlled configurations and test data
- Installation, commissioning, system and security evidence
- Defect, exception and corrective-action records
Controlled outputs
- Test and acceptance evidence
- Defect and corrective-action register
- Retest and residual-risk record
- Conditional acceptance, rejection or approval recommendation
Four disciplined moves.
Execute functional, performance, integration, security and operational tests.
Trace failures to evidence, owner and corrective action.
Repeat affected tests and document the authorized disposition.
What this page does not do.
A successful demonstration or isolated meter read is not end-to-end acceptance. This educational page explains the instrument but does not reproduce its complete working tables. Use the controlled Protocol PDF and the responsible professional or authority for actual project work.
Open the complete working instrument in Protocol 3.2.
The downloadable publication preserves the full annex, version context and framework limitations.