Quick orientation — let's get on the same page

• To start, how many metered endpoints does your organization plan to include in this AMI program? Options: Under 10,000, 10,000–50,000, 50,001–250,000, 250,001–1,000,000, Over 1,000,000
• When is the regulatory or operational trigger that is driving this program, for example a TOU order or equipment end-of-life? Options: Within 3 months, 3–6 months, 6–12 months, 12–24 months, No firm date
• Who on your leadership team will make the final decision to move from pilot to full rollout? Options: VP Metering Operations, Director, Grid Technology, Regulatory Affairs Manager, CFO/Finance, Procurement, Executive Committee
• Which internal group will own day‑to‑day program management once deployment begins? Options: Metering operations, Network operations, IT/Integration team, Program management office, A joint team, Undecided
• Please upload or describe any existing AMI studies, cost-benefit filings, or recent regulatory filings you want us to review.

Where the current setup actually fails you

• If your current meter fleet cannot meet the TOU filing or fails across 30 percent of endpoints, what are the financial or compliance consequences you would face in the next 12 months? Options: Significant regulatory risk and fines, Major rework to billing and customer notices, Increased operating costs above budget, Unable to meet TOU rollout schedule, Other
• How many manual truck rolls per month does your metering organization currently perform for reads, service connects, and outage checks? Options: Under 100, 100–500, 500–2,000, 2,001–10,000, Over 10,000
• Describe the last time meter read accuracy or latency caused a customer or regulator complaint, and what downstream systems had to be fixed as a result.
• Estimate your current annual cost of estimated billing and associated adjustments that a full AMI deployment would reduce. Options: Under $100k, $100k–$500k, $500k–$2M, $2M–$10M, Over $10M
• What single technical or program failure during a rollout would make you stop the project immediately? Options: Network cannot reach target endpoints, MDM/head-end fails to scale, Major billing integration errors, Customer opt-out rate too high, Regulatory objection

Where connectivity actually breaks down

• How confident are you that a new communications network can reach a representative 95 percent of your endpoints in the most challenging service areas? Options: Very confident, Somewhat confident, Uncertain, Not confident
• Which terrain or urban conditions in your service territory create the biggest connectivity risk, for example dense canopy, steep elevation, or multi‑unit buildings? Options: Dense tree canopy, Hilly or mountainous terrain, Dense urban multi‑unit buildings, Remote rural pockets, Interior commercial meters, Other
• Tell me about any prior connectivity pilots or small deployments you've run, including where they were, the sample size, and the measured reach rate.
• What percentage endpoint connectivity during a field pilot would convince you the network design is viable for scaling? Options: 95% or higher, 90–94%, 85–89%, Below 85%
• If a pilot delivered 88 percent reach in one geography but 97 percent in another, what would you require before approving a full rollout? Options: Additional pilots in low-performing areas, Different radio/network architecture, Tiered rollout by geography, Refuse to proceed without 95% everywhere, Other

Where systems and data need to meet in the middle

• Which integration failure — billing, MDM, head-end, or outage management — would cost you most in regulatory exposure or customer harm? Options: Billing/CIS, MDM, Head-end/AMI server, Outage Management System, GIS
• List the key systems this AMI must integrate with and indicate whether APIs or batch interfaces exist for each. Options: Customer information/billing (API), Customer information/billing (batch), Outage management (API), Outage management (batch), GIS, Workforce management, Other
• Who owns each integration inside your organization, and will they be available to engage in sprint-style integration work during pilot months? Options: Metering ops, IT/Integration team, Third-party integrator, Procurement, Undecided
• How large are the expected hourly or daily interval data volumes at scale, and do your current systems have documented performance baselines for those volumes? Options: Under 1M intervals/day, 1M–10M, 10M–100M, Over 100M, Unknown/no baseline
• Which data mapping or timezone/consumption transformation error would cause the largest reconciliation exposure for a regulatory filing? Options: Meter timestamp shift, Incorrect billing class mapping, Lost interval data, Duplicate intervals, Other

Designing a pilot that actually proves the unknowns

• If a six-month pilot could validate meter accuracy, communications reach, and end-to-end billing integration, what obstacles would still keep you from greenlighting it? Options: Budget constraints, Procurement approval, Stakeholder buy-in, Regulatory timing, Other
• How many endpoints and which customer types do you think are necessary in a pilot to be statistically meaningful for your regulator? Options: Under 500, 500–2,000, 2,001–10,000, Over 10,000
• What specific acceptance criteria should a pilot meet on meter accuracy, connectivity, and integration before you consider it successful? Options: Accuracy within regulatory tolerance, Connectivity ≥ target percentage, No critical billing errors in a month, MDM ingest latency under threshold, Other
• Who in your regulatory or legal team must review pilot results before you can use them in a cost-benefit filing? Options: Regulatory Affairs, Legal/Compliance, Finance, Chief Counsel, Undecided
• If the pilot meets the technical targets, how quickly could procurement and contracting sign off to move to rollout? Options: Within 2 weeks, 2–6 weeks, 6–12 weeks, Longer than 12 weeks, Depends on commercial terms

Operational readiness — the practical gates that stop or start work

• What critical internal dependency, if missing, would prevent the project from starting on schedule? Options: Dedicated program manager, Integration resources in IT, Access to meter installation crews, Regulatory approval, Data ownership not assigned
• Which of these infrastructure prerequisites are already in place: site access agreements, GIS parcel data, meter inventory with serials, or API credentials to billing? Options: Site access agreements, GIS parcel data, Meter inventory with serials, API credentials to billing, None of the above
• Estimate the available FTEs your organization can assign to integration testing and field support during pilot months. Options: Under 2 FTEs, 2–5 FTEs, 6–10 FTEs, Over 10 FTEs
• Who is the named owner for data governance and will they be authorized to sign data sharing agreements needed for pilot data flows? Options: Yes, named and authorized, Named but not authorized, No named owner yet, Undecided
• Are there regulatory approvals, local permits, or municipal agreements that could gate timeline for meter installations or network radios? Options: Yes, known approvals needed, Possibly, depending on location, No known approvals, Unsure

The other options you are seriously weighing

• Who are the main alternatives you are evaluating right now, including incumbents and internal builds? Options: Incumbent AMI vendor, Point‑to‑point radio vendor, Cellular-based solution, Internal build/IT-led, No alternative yet
• What would have to be true about your current approach for you to decide to keep it instead of changing vendors or platforms? Options: Proven reach in all geographies, Lower total cost of ownership, Clear upgrade path without platform replacement, Regulatory acceptance, Other
• Has anyone proposed solving this internally without an outside vendor, and if so, who would lead that effort and what timeline were they proposing? Options: Yes, IT proposed (timeline <12 months), Yes, metering ops proposed (12–24 months), Yes, but timeline >24 months, No internal proposal
• Which vendor capability is most important in your evaluation — network resilience, meter lifespan, MDM scalability, or integration support? Options: Network resilience, Meter lifespan and accuracy, MDM/head-end scalability, Integration and professional services
• If the incumbent proposed a phased upgrade that avoided re-platforming, what evidence would you need to accept that route? Options: Scalability proof for target endpoints, Third-party performance audit, Successful large-scale reference, Regulatory endorsement, Other

Stakeholders, risks, and what can stop approval

• Which single stakeholder or governance gate in your organization could stop the program, and what would it take to address their concern? Options: Regulatory Affairs, Finance/CFO, Labor/Union, IT Security, Executive Sponsor
• Describe any anticipated customer objections to mass meter replacement, for example health concerns, opt-outs, or access refusals, and how you expect to mitigate them.
• How large a contingency budget do you require for network remediation or rework if a pilot exposes connectivity gaps? Options: Under 5% of capital, 5–10%, 10–20%, Over 20%, No contingency planned
• Are there union or workforce transition agreements that will affect installation staffing or timing? Options: Yes, active agreements, Negotiations in progress, No known agreements, Unsure
• Is there a non-negotiable regulatory filing date or program milestone that, if missed, ends the project? Options: Yes, fixed date, Flexible by 3 months, Flexible by 6 months, No firm date

Acceptance criteria and the deal accelerators

• If the pilot proves the technical and integration targets we agree, what commercial or procurement milestones would allow you to sign within the same quarter? Options: Budget approval, Legal contract terms agreed, Regulatory filing support committed, Reference site visits complete, All of the above
• Which performance metric would be sufficient on its own to accelerate your decision to award the rollout contract? Options: Network reach above target, Zero critical billing errors for a month, MDM handles full ingest latency under threshold, Clear TCO model validated by finance
• What commercial terms are non-starters for you, for example unacceptable indemnity, warranty length, or performance SLAs? Options: Insufficient warranty length, No performance SLA credits, Unacceptable termination terms, Price above capped amount, Other
• How soon after pilot success must commercial terms be agreed to keep the program on your target rollout timeline? Options: Within 2 weeks, 2–6 weeks, 6–12 weeks, Longer than 12 weeks
• If pilot metrics match your acceptance thresholds, who can sign the contract and what approvals would they still need? Options: VP Metering Operations with finance approval, CFO signature required, Executive Committee approval, Procurement + Legal signoff

Practical next steps and immediate asks

• Which three documents or artifacts would you be comfortable sharing to accelerate scoping — meter inventory, recent outage maps, pilot site list, or a cost-benefit filing? Options: Meter inventory, Outage maps, Pilot site list, Cost-benefit filing, None at this time
• Who should attend a technical kickoff to define pilot scope and integrations, and what are their contact roles? Options: Program manager, Lead integration engineer, Regulatory lead, Procurement representative, Field operations lead
• Realistically, when could your team commit to a two-day onsite discovery workshop to finalize pilot locations and acceptance criteria? Options: Within 2 weeks, 2–6 weeks, 6–12 weeks, Later than 12 weeks
• Before we finish, what single unresolved question in your leadership team could stop this project from moving forward?

• stakeholders
• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• decision_readiness
• gaps
• current_state
• desired_state
• stakeholders
• success_criteria
• stakeholders
• desired_state
• gaps
• success_criteria
• decision_readiness
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Meter Hardware Provisioning and Staging
• Mesh Network Infrastructure Deployment
• Field Gateway and Collector Installation
• Meter Endpoint Installation and Commissioning
• Over-the-Air Firmware Updates and Management
• Head-End System Deployment and Configuration
• Meter Data Management Platform Deployment
• Integrate MDM with Billing/CIS/OMS
• Remote Connect/Disconnect Activation
• Outage Detection and Automated Alerts Setup
• Voltage and Power Quality Monitoring Enablement
• Network RF Tuning and Performance Optimization
• Field Technician Training and Certification
• Meter Exchange, Recycling, and Disposal Logistics
• Financing and Incentive Qualification

Meter Hardware Provisioning and Staging

• How many metering endpoints do you plan to procure by physical form factor (residential single-phase, three-phase commercial, CT/VT metering)? Options: Residential single-phase, Three-phase commercial, CT/VT installations, Mixed
• Which meter accuracy class and calibration certificates must be supplied (for example ANSI C12.20 0.5 or better)? Options: ANSI C12.20 Class 0.5, ANSI C12.20 Class 0.2, Other / custom spec
• Where will batch staging and warehouse acceptance testing occur and what physical security controls (access logs, CCTV) are required for staged meter inventories? Options: Utility-owned warehouse, Third-party staging facility, Require vendor-managed staging
• Do you require serialized asset tagging linked to your asset management system (barcode, RFID) and which asset ID field maps to your CIS account record? Options: Yes - barcode linked to CIS account, Yes - RFID linked to CIS account, No tagging required
• Define the acceptance criteria for delivered meter batches (examples: correct firmware version, calibration certificate present, visual inspection, sample functional test pass rate). Options: Firmware and cert required, visual inspect, Sample functional test (1%) required, Full batch functional test required

Mesh Network Infrastructure Deployment

• Which deployment terrain profile applies to the target area for mesh planning (urban with high-rise, dense tree canopy/suburban, hilly rural) so we can size node density? Options: Urban high-rise, Suburban / tree canopy, Hilly rural, Mixed
• How many planned network gateway/relay nodes do you estimate per square mile and which mounting types are permissible at each planned site (utility pole, rooftop, indoor comms room)? Options: Pole-mounted, Rooftop, Indoor comms room, Mixed
• Require support for which radio standard or spectrum plan in your territory (example: IEEE 802.15.4g, licensed sub-GHz band) for RF compliance and coexistence planning? Options: IEEE 802.15.4g / sub-GHz, Licensed narrowband, Other / custom
• Specify the RF coverage threshold you require in the pilot area (for example 95% packet delivery ratio within three hops or minimum RSSI of -85 dBm) to qualify network performance. Options: 95% PDR within 3 hops, Minimum RSSI -85 dBm, Custom threshold
• Who will coordinate pole attachments, right-of-way, and local permitting for node installations and what documentation do you provide for that coordination? Options: We provide permits, We need vendor assistance, Third-party permit coordinator

Field Gateway and Collector Installation

• List gateway sites that currently have backhaul available and indicate backhaul type for each (fiber handoff, cellular LTE/5G, microwave hop). Options: Fiber handoff, Cellular LTE/5G, Microwave, Site survey needed
• Do you already hold pole attachment licenses for the planned gateway locations or should a permitting plan be included in scope? Options: Pole licenses in hand, Permits required, Partial - some sites licensed
• State the minimum environmental enclosure rating required for gateways (for example IP65, NEMA 4X) and any site-specific heating/cooling constraints. Options: IP65, IP66, NEMA 4X / IP67, Other
• Provide the preferred operations ownership model for gateway maintenance after handover (your internal crew, contracted O&M partner, vendor-managed), and note existing SLAs if any. Options: Internal ops team, Contracted O&M, Vendor-managed
• Indicate which gateway telemetry metrics must route into your network operations center (examples: RSSI distribution, packet loss, CPU/Memory, WAN latency). Options: RSSI distribution, Packet loss, CPU/Memory, WAN latency

Meter Endpoint Installation and Commissioning

• Estimate the average number of endpoint installations per crew per day you expect during peak rollout and how many crews you can resource. Options: <50 installs/day/crew, 50-200 installs/day/crew, >200 installs/day/crew
• Require what customer access model for installs (scheduled in-home appointment with electrician, curbside install without entry, self-install kit with app-based commissioning)? Options: Scheduled in-home appointment, Curbside only, Self-install kit, Mixed
• List the commissioning records you require at the point of install (meter serial, firmware version, final meter reading, CT/PT ratios) and the submission method (mobile app, API, CSV upload). Options: Mobile app, API integration, CSV upload, Paper then upload
• Describe the mandated safety and lockout/tagout (LOTO) steps installers must follow for live-service meter changeouts according to your safety program. Options: Follow our LOTO, Follow vendor LOTO, Joint LOTO procedure
• Define acceptance for an installed endpoint (examples: successful first hourly interval upload to head-end, registration in MDM, and correct mapping to CIS account). Options: First hourly interval received, Registration in MDM and CIS mapping, Both conditions required

Over-the-Air Firmware Updates and Management

• Are signed firmware images and secure delivery (code signing with rollback support) required for meter OTA pipelines and key management integration? Options: Yes - signed with rollback, Signed not required, Custom requirement
• Specify the release cadence and change control gate you require for OTA pushes (for example monthly security patch window, quarterly feature release with CAB approval). Options: Monthly security patches, Quarterly feature releases, Ad hoc with CAB
• Indicate which staging environments must be available for OTA testing (pilot group, pre-production cluster, full production) and who approves promotion between stages. Options: Pilot / Pre-prod / Prod, Pilot and Prod only, Pilot then CAB approval required
• Outline the recovery behavior you require for failed OTA updates (automatic rollback, automatic retry schedule, follow-up field dispatch) and escalation triggers. Options: Automatic rollback, Scheduled retry then dispatch, Immediate field dispatch
• Confirm whether cryptographic key storage must integrate with a hardware security module (HSM) and your security operations center for key rotation audits. Options: HSM integration required, HSM not required, Undecided

Head-End System Deployment and Configuration

• Identify the head-end communication protocols and adapters that must be enabled (examples: DLMS/COSEM, ANSI C12.22, proprietary meter adapter). Options: DLMS/COSEM, ANSI C12.22, Proprietary adapter, Multiple
• Select target throughput load test scenarios for the head-end to validate performance (for example 1,000 meter messages/minute, 10,000 meter messages/hour). Options: 1,000 msg/min, 10,000 msg/hour, Custom
• State which integration methods to your MDM and downstream systems are required (real-time webhook, batch file exchange, REST API) and expected message formats. Options: Real-time webhook, Batch file, REST API, Other
• Name the operational owner who will approve configuration changes after handover and the expected change-control process (ticketing, CAB approval cadence). Options: Your ops team, Vendor-managed, Shared model
• Report any existing head-end redundancy or high-availability requirements (active-active, active-passive, RTO/RPO targets). Options: Active-active, Active-passive, Single site with DR

Meter Data Management Platform Deployment

• Estimate the day-1 endpoint population and the projected year-5 population the MDM must support so we can size storage and compute. Options: <50k, 50k-500k, 500k-1M, >1M
• Choose the interval granularity and retention policy you require for interval reads (examples: 1-minute, 5-minute, 15-minute intervals and retention years). Options: 1-minute, 5-minute, 15-minute, Custom
• Identify required data validation rules (gap detection, timestamp alignment, outlier filters) and who will own rule definitions and tuning. Options: We own rules, Vendor helps define, Joint ownership
• List required export connectors and formats for analytics and regulator filings (CSV extracts, EDI batches, REST API endpoints). Options: CSV, EDI, REST API, Other
• State the SLA targets you require for MDM data availability and query latency to support customer care and regulatory reporting. Options: 99.9% availability, 99.99% availability, Custom SLA

Integrate MDM with Billing/CIS/OMS

• Which billing/CIS interfaces must be supported for usage transfer (batch daily usage file, hourly billing API, or both)? Options: Batch usage file, Hourly billing API, Both
• Provide the mapping rules required between meter serials and CIS customer account IDs and indicate where the golden source file will come from. Options: We provide golden source, Vendor to reconcile with our file, Need mapping workshop
• Indicate the reconciliation cadence you prefer to validate MDM to CIS mapping (daily, weekly) and who signs off on reconciliation exceptions. Options: Daily, Weekly, Monthly
• Select the accepted tolerance for billing-ready data reconciliation (example tolerances: 0.1% energy mismatch, 0.5%, 1%). Options: 0.1% energy mismatch, 0.5%, 1%, Other
• Do you require direct forwarding of MDM events to your OMS and which event types should be included (power loss, tamper, voltage sag)? Options: Power loss, Tamper, Voltage events, All listed

Remote Connect/Disconnect Activation

• Estimate the percentage of endpoints that will need remote connect/disconnect capability at go-live so we can size command throughput. Options: <10%, 10-50%, 50-90%, >90%
• Which preconditions must be checked before issuing a remote disconnect (payment hold flag, active work order, LOTO tag) per your operating rules? Options: Payment hold, Active work order, LOTO tag, Other
• Choose the retry and escalation behavior you want when a remote command fails (automated retry policy, queue for manual retry, field dispatch after N retries). Options: Retry then dispatch, Queue for manual retry, Immediate dispatch
• Are audit trails required for each connect/disconnect action including operator ID, timestamp, and reason code integrated into CIS? Options: Yes, No
• Who is authorized to approve mass disconnect or reconnect campaigns and what role-based approval workflow do you require? Options: Named approver list, Automated rule-based approval, CAB approval

Outage Detection and Automated Alerts Setup

• Which meter-derived indicators should open an OMS ticket (examples: sustained loss of interval data, sudden zero consumption, tamper event)? Options: Loss of interval data, Sustained zero consumption, Tamper, Other
• Select the detection-to-notification latency you require for customer alerts and field dispatch (for example within 5 minutes of event confirmation). Options: <1 minute, <5 minutes, <15 minutes, Custom
• Do you require templated customer notifications and regulator-ready outage reports for extended interruptions and do they need statutory fields included? Options: Yes - notifications and regulator reports, Notifications only, Regulator reports only, No
• Specify the restoration-verification condition needed before auto-closing an OMS ticket (for example N consecutive normal intervals at the meter). Options: 1 normal interval, 3 consecutive normal intervals, 24 hours of normal readings
• Identify which stakeholder groups must be notified and in what order for major outages (distribution operations, customer care, regulatory affairs). Options: Distribution ops, Customer care, Regulatory affairs, All listed

Voltage and Power Quality Monitoring Enablement

• Which power-quality metrics must be captured at interval level (examples: RMS voltage, flicker, total harmonic distortion) and at what interval granularity? Options: RMS voltage 15-min, RMS voltage 1-min, Flicker, THD
• Where (which feeders or transformer zones) do you need prioritized voltage monitoring for early warning and regulatory reporting? Options: Feeder A list, Transformer zones, System-wide
• Do you require automated correlation between meter voltage events and SCADA/topology for root-cause analysis and which data exchange method do you prefer? Options: Direct SCADA link, Batch correlation, Manual analysis
• State the alarm thresholds for power quality that will trigger operational tickets (example: voltage deviation greater than 5% for 5 minutes). Options: >5% for 5 minutes, >10% for 1 minute, Custom thresholds
• Who will own ongoing power-quality analytics and periodic regulator filings produced from meter data? Options: Your analytics team, Vendor-managed, Shared responsibility

Network RF Tuning and Performance Optimization

• Do you already have RF propagation heatmaps for the service territory or should a site survey be included to model path loss and canopy effects? Options: We have heatmaps, Include site survey, Partial data only
• Which RF health KPIs must be tracked continuously (packet delivery ratio, average hops per meter, RSSI/CINR distribution)? Options: Packet delivery ratio, Average hops, RSSI/CINR distribution, All listed
• How often should RF retuning be scheduled during rollout and what triggers should provoke an ad hoc retune (seasonal foliage changes, new construction)? Options: Monthly during rollout, Trigger-based, Quarterly
• Compare acceptable mitigation techniques for persistent coverage gaps (deploy relay nodes, install higher-gain antennas, add rooftop gateways) and indicate preferred order. Options: Relay nodes first, High-gain antennas, Rooftop gateways, Mixed approach
• Assign who will approve and fund additional RF infrastructure discovered during optimization (your capex, joint funding, vendor-funded with recovery). Options: You fund, Joint approval, Vendor funds with cost recovery

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Purchase Agreement - Hardware Order
• Subscription Agreement - Meter Data Platform
• Service Level Agreement (SLA)
• Acceptance Test Plan & Criteria
• Milestone Payment Schedule
• Regulatory Filing Support Addendum
• Data Processing Agreement (DPA)
• Hardware Warranty & Repair Terms
• Change Order Agreement
• Termination & Transition Agreement
• Integration & Cutover Addendum

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• 90-day Realization Review
• Quarterly Operational Review
• Annual Operational Review

• Deliver a prioritized incident closure plan with expected resolution dates for each open incident older than 30 days.
• Publish a closure plan for each remaining acceptance gap with target dates and verification steps.
• Deliver evidence of legacy system decommissioning or read-only configuration and data archive completion.
• Provide the regulatory filing extract samples that will be submitted if requested.
• Operational metrics dashboard
• Ensure network packet delivery rate and integration uptime remain within the tolerance recorded in Solution Scope.
• Reduce the count of persistent open incidents by a targeted percentage before the next quarter.
• Agree next-quarter priorities for enhancement requests that materially affect operations or reporting.
• Re-confirm success criteria and owners
• Publish a quarterly operational dashboard snapshot showing packet delivery rate and integration uptime.
• Capture and circulate the prioritized enhancement backlog for scheduling consideration.
• Year-to-date realized savings
• Confirm the year-over-year realized savings against the Solution Scope financial model and surface any material variances.
• Agree a 12-month plan to address any meter or network health trends that threaten service levels or regulatory obligations.
• Validate that regulatory reporting outputs meet the required formats and data completeness for filings.
• Produce a reconciliation of realized savings versus the Solution Scope model with explanations for material variances.
• Create a 12-month maintenance and refresh plan addressing meter and network health risks identified in the review.
• Deliver a regulatory reporting checklist confirming data sources, formats, and responsible owners for the next filing cycle.
• Confirm that the deployment components expected at go-live are present and communicating.
• Identify and assign owners for all critical go-live blockers with committed remediation windows.
• Ensure all parties understand where numeric targets and acceptance criteria are documented in Solution Scope.
• Publish an issues-and-owners list with remediation deadlines within 24 hours.
• Provide an updated inventory of meters and network nodes that reported during the first 72 hours.
• Circulate a confirmation of who owns each Solution Scope success criterion.
• Present first measurement data
• Determine whether daily endpoint reporting rate and truck roll reduction are tracking toward targets and why or why not.
• Agree a prioritized remediation plan with dates to address the top 1-3 root causes.
• Confirm when the next data re-check will occur and which dataset will be authoritative for that check.
• Produce a remediation plan addressing the top root causes with milestones and target completion dates.
• Run a focused integration test and deliver an API error-rate log for the last 14 days.
• Prepare a re-check dashboard snapshot for the agreed follow-up date.
• Present 90-day outcome data versus acceptance criteria
• Confirm which acceptance criteria from Solution Scope and Pilot & Field Evaluation are met, and which require remediation.
• Establish firm remediation timelines for any unmet criteria and a verification date for closure.
• Ensure the legacy metering system is either decommissioned or formally retained read-only with archived data and closed fallback habits.
• Persistent issues and incident burn-down
• Meter and network health trends
• Document remediation items and resolution timelines
• Integration stability summary
• Deployment and migration validation
• Support ticket trends and SLA adherence
• Incumbent system decommission status
• Integration stability and incident trend analysis
• Root-cause diagnosis for any gaps
• Early adoption and usage signals
• Regulatory reporting and compliance summary
• Blockers and open issues triage
• Agree corrective actions and timelines
• Enhancement request triage
• Regulatory reporting and deliverables check
• Agree immediate remediation actions
• Integration incident and escalation review