Industrial & Manufacturing › Energy, Utilities & Sustainability › Grid Modernization & Distributed Energy

Distribution Automation

Long-cycle programs where regulation, capital, and grid reliability define the pace.

Example organizations in this space: ABB Siemens S&C Electric Eaton

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey

Pre-Sales

Qualify and diagnose before investing in a full evaluation cycle.
1. Qualification
  
  Confirm budget range, decision authority, timeline expectations, and high-level constraints before investing in a full discovery and evaluation cycle.
  Qualification Questions
  Deployment fit and constraints (quick readiness check)
  - Which integration endpoints must this project support? Select all that apply. Options: Existing on‑prem SCADA or DMS, Cloud‑based DMS/ADMS, Edge automation only (local control, no DMS), Telemetry/utility historian only, Not yet determined, Other (please specify)
  - What is the current communications availability across the targeted sites? Options: Fiber available at most sites, Reliable cellular coverage at sites, Licensed utility radio required, No reliable communications today, Not yet assessed
  - Are there specific cybersecurity or regulatory requirements we must meet for vendor selection or deployment? Options: Yes — NERC CIP or equivalent applies, Yes — security questionnaire / SOC2 / vendor assessment required, No specific cybersecurity requirements, Unsure / will confirm
  - Which device types and rough site count are you considering (briefly list devices and an approximate number of sites)?
  Budget
  - Is there an allocated budget range for automating these distribution devices? Options: Under $100,000, $100,000–$500,000, $500,000–$2,000,000, $2,000,000–$5,000,000, Above $5,000,000 (may exceed typical scope), No budget allocated yet / exploratory
  Decision authority
  - Who will approve the capital spend or vendor selection for this project? Options: VP‑level operations or engineering, Director‑level operations or engineering, Procurement/Finance signs final contract, Multi‑party executive committee approval, Not yet decided / will confirm
  Timeline
  - What is your target timeframe to have the first site deployed or a contract in place? Options: Within 3 months, 3–6 months, 6–12 months, 12–24 months, No firm deadline / exploratory
2. Outcome Discovery
  
  Map the buyer's current state, targeted reliability outcomes, key stakeholders, and success signals required by regulators and operations teams.
  Discovery Questions
  Starting point, the parts we're looking at together
  - Tell me about the circuits, substations, or feeder segments you want to include in an initial outcomes review
  - Which voltage classes and equipment types are in scope for this effort Options: Low voltage secondary, Medium voltage overhead feeders, Medium voltage underground feeders, Substation protection and control, Pole-mounted devices only, Mixed across several types
  - How many physical sites or distinct feeders would you expect to include in a pilot Options: 1, 2-5, 6-20, More than 20
  - Describe the current field device footprint and telemetry, for example counts of reclosers, switches, fault indicators, and RTU nodes
  - Which communications links already exist on those sites Options: No communications in place, Cellular (private SIM), Cellular (public SIM), Private radio mesh, Fiber to site, SCADA RTU only, Other
  Where your network visibly shows strain
  - If a single recent outage had to illustrate the biggest systemic weakness you worry about, which feeder or failure mode would you point to and why
  - On average over the past 12 months, how often have those feeders experienced sustained outages large enough to require crew dispatch Options: Weekly, Monthly, Quarterly, Less often than quarterly
  - Which customers or customer classes are most exposed when those events occur Options: Critical facilities, Commercial/industrial, Large residential pockets, Rural single customers, Mixed
  - Describe the downstream operational or regulatory consequence when a repeated fault occurs on one of these feeders
  - Which reliability metric miss would make you stop a deployment until addressed, for example a worsening in SAIDI, SAIFI, or customer minutes lost Options: SAIDI increase of any amount, SAIFI increase of any amount, Customer minutes increase over target by >10%, A safety or compliance breach, Other
  Who needs to be convinced before you move forward
  - Who are the functional owners and approvers that must sign off on requirements, pilot scope, and budget Options: Distribution engineering, Grid operations, IT/OT security, Regulatory affairs, Procurement, Finance, Other
  - Walk me through the typical decision path for a capital pilot in your organization, from proposal to purchase order
  - Who on your team will own day-to-day communications and escalation during a pilot
  - Which internal stakeholder would stop or delay the project if their concerns were not addressed Options: Operations leadership, IT security, Regulatory counsel, Finance, Procurement, Field crews
  - If the pilot proves the expected reliability gains, who has the authority to accelerate procurement and scale the program quickly Options: VP operations, Distribution engineering director, Capital planning committee, Procurement lead, Other
  Integration realities, so hooking up actually works
  - Which control system or SCADA integration gap has blocked past automation efforts for you Options: Protocol mismatch, No test environment, Security policy prevents connections, DMS vendor limits integration, Lack of API documentation, Other
  - Which telemetry and protocols must be supported for the pilot to be meaningful Options: DNP3 serial, DNP3 over TCP, IEC 61850, Modbus, REST APIs, MQTT, Proprietary vendor protocol
  - Describe the availability of a test or sandbox DMS/SCADA endpoint that we could use for integration and acceptance testing Options: Full sandbox available, Partial test environment, No test environment, production only, Unknown
  - Who owns the interfaces and will approve credentials and firewall rules for integration Options: SCADA team, IT network team, Third-party integrator, Field engineering, Other
  - If you cannot provide a test endpoint or reasonable integration window, would that prevent running a meaningful pilot Options: Yes, prevents pilot, No, we can work around it, Unsure
  Practical constraints, the things that stop work before it starts
  - Which single internal constraint, if unresolved, would stop this project from starting on your target date Options: No available budget, Insufficient IT/OT headcount, Pending regulatory approval, Permitting or right-of-way issues, Lack of communications coverage
  - How many full time equivalents (FTEs) can your teams commit to a pilot for engineering, integration, and field support Options: None, 1-2, 3-5, More than 5
  - Are your field crews available for coordination windows, such as switching and commissioning shifts Options: Yes, flexible, Yes, limited to planned windows, No, very constrained, Unknown
  - Which approvals, permits, or external agreements typically add the most schedule risk for field deployments in your territory Options: Interconnection approval, Permits from local authorities, Landowner access agreements, Telecom lease agreements, None of the above
  - Describe the state of the data you will provide for acceptance and measurement, for example event logs, SCADA history, and device inventories
  Alternatives you are actively weighing
  - Which external vendors, incumbent suppliers, or internal teams are you currently evaluating or have used for similar automation or FLISR projects Options: Incumbent vendor, New external vendor, Internal development by engineering, Third-party systems integrator, No alternatives yet, Other
  - Please name the alternative approaches or teams you consider viable, so we understand overlap or gaps
  - What would have to be true about your current approach for you to stay with it instead of switching to an external solution Options: Lower total cost, Demonstrable reliability improvement, Faster deployment timeline, Minimal integration changes, Ability to run in-house
  - Has anyone internally proposed building the required automation capabilities without a vendor partner Options: Yes, fully in-house, Yes, hybrid in-house and partner, No, Unknown
  - Which past project or vendor experience makes you most skeptical about changing course now
  What success looks like and how you will measure it
  - If you were briefing regulators on the pilot next quarter, which measured signal would prove the work delivered value Options: SAIDI reduction, SAIFI reduction, Minutes to restoration improvement, Fewer field dispatches, Faster fault location accuracy
  - Which target ranges for SAIDI or SAIFI change would you consider a pass for a pilot of this size Options: SAIDI reduction 5-10%, SAIDI reduction 10-20%, SAFI reduction 5-10%, SAIFI reduction >10%, Other
  - Who will validate the pilot results and sign the acceptance report Options: Distribution engineering, Operations leadership, Independent auditor, Regulatory reporting team, Other
  - How long a measurement window do you require before declaring success Options: 2 weeks, 1 month, 3 months, 6 months, Depends on seasonality
  - If the pilot meets the published acceptance thresholds, what internal action would accelerate full program funding Options: Immediate approval and scaling, Formal review by capital committee, Further pilot expansion, No immediate action planned
  Timeline, budget posture, and decision triggers
  - If all technical and regulatory questions were answered today, how soon could you allocate budget and approve a pilot window Options: Immediately, Within 30 days, Within 60-90 days, Quarter or later, No budget in current cycle
  - Which budget model do you prefer for pilots and initial deployments Options: Capital expense with asset purchase, Capital expense with lease, Operational expense subscription, Mixed model, Undecided
  - Provide the ballpark budget range you would consider reasonable for a pilot covering the sites you listed Options: < $50k, $50k-$150k, $150k-$500k, $500k-$1M, > $1M
  - Which procurement or contracting pathway typically governs projects of this size in your organization Options: Standard purchase order, Request for proposal, Sole-source with justification, Existing vendor master agreement, Other
  - What single timeline risk would force you to delay awarding a pilot, for example a regulatory filing or a seasonal access constraint
  Final practical steps, blockers, and commitments
  - Who in your organization must sign the pilot order to enable field work within eight weeks
  - Which deliverables or artifacts do you need from us before you can brief your leadership Options: Detailed scope and site list, Integration test plan, Security posture and certifications, Budget estimate, Pilot acceptance criteria, Other
  - Walk me through the top three items your team must complete before crews can access sites for commissioning
  - Are there any known regulatory, legal, or third-party approvals pending that would stop the pilot Options: Yes, regulatory approval pending, Yes, land or access approvals pending, No known approvals pending, Unknown
  - If the pilot delivers the agreed acceptance results, what is the fastest path you would use to scale the program Options: Direct rollout funded by capital, Phased rollouts by region, Additional pilots to cover edge cases, Seek further executive approval
Solution Evaluation

Execute a field or lab evaluation against the buyer's acceptance criteria including interoperability tests with SCADA/DMS, communications performance checks, and measured reliability improvements.
- desired_state
- current_state
- decision_readiness
- stakeholders
- gaps
- success_criteria
- success_criteria
- decision_readiness
- current_state
- desired_state
- gaps
- stakeholders
- decision_readiness
- desired_state
- success_criteria
- stakeholders
- gaps
- current_state
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
Solution Scope

Define sites, equipment types, automation schemes, responsibilities, integration endpoints, and measurable acceptance criteria for deployment and commissioning.
Scope Configuration
- Supply Automated Reclosers
- Supply Sectionalizing Switches
- Supply Capacitor Bank Controllers
- Supply Voltage Regulators
- Supply Fault Circuit Indicators
- Install Pole- and Pad-Mount Devices
- Deploy Communications Network and Backhaul
- Commission Protection and Control Settings
- Deploy FLISR Automation Scheme
- Configure Volt-VAR Optimization
- Integrate Devices with SCADA/DMS (DNP3/IEC 61850)
- Operator Training and Operational Procedures
- Field Maintenance Handover and Spares Kit
- Performance Acceptance Testing and Diagnostics
- Financing and Incentive Qualification Package
Scope Questions
Supply Automated Reclosers
- Which automated recloser models and frame sizes are required for your circuit(s) based on nominal voltage and maximum fault current ratings?
- How many recloser units are planned in the initial deployment and what is the planned ramp schedule for additional units? Options: 1-5, 6-20, 21+
- Who will provide the single-line diagram (SLD) revisions and coordinate pole/hardware locations for each recloser site?
- Do you have existing pole loading, conductor clearance, and right-of-way notes documented for proposed recloser mountings? Options: Yes, No, Partial
- When is the target in-service date for reclosers on your top-priority feeders? Options: Within 3 months, 3-6 months, 6-12 months, Custom
Supply Sectionalizing Switches
- Provide the list of feeder sections, pole numbers or GPS coordinates where sectionalizing switches are requested.
- Specify the required switching capability at each sectionalizer location (load-break, fault-interrupting, visible-break). Options: Load-break, Fault-interrupting, Visible-break
- List the maximum continuous current and peak short-circuit duty for each sectionalizer location.
- Confirm whether motor operators, local manual handles, or remote key-switch panels are required at the switch locations. Options: Motor operator required, Local manual only, Key-switch panel required, None
- Identify any sites on third-party poles or with known permitting constraints that will require special access agreements.
Supply Capacitor Bank Controllers
- Are you retrofitting existing capacitor banks or planning new capacitor bank installations? Options: Retrofit existing, New installation, Both, Undecided
- Estimate per-bank kVAr ratings, number of steps, and switching cadence you expect for Volt-VAR targets.
- Describe required coordination between capacitor controllers and substation LTC or upstream voltage regulators (including time delays or deadbands).
- Where will controller telemetry terminate in your topology (RTU/SCADA, substation LAN, direct DMS connection, or other)? Options: RTU/SCADA, Substation LAN, Direct DMS, Other
- Which industry standard or your utility practice must capacitor switching comply with (reference an IEEE or IEC guideline or internal procedure)?
Supply Voltage Regulators
- Which control protocols, analog points, and digital I/O do your regulators need to support (for example DNP3 analog, IEC 61850 logical nodes)?
- Who approves regulator voltage setpoints and droop curves within your organization (distribution engineering, operations, or joint approval)? Options: Distribution engineering, Operations, Joint approval
- What single-line diagram pages or protection coordination documents will you provide to validate regulator selection?
- Which sites require step-voltage regulation versus coordination with substation LTCs?
- How do you prefer tap change logging and archival (real-time historian, event-only, or summary batches)? Options: Real-time historian, Event-only, Summary batches
Supply Fault Circuit Indicators
- Which fault indicator communication mediums are acceptable for your network (RF mesh, cellular, or wired telemetry)? Options: RF mesh, Cellular, Wired telemetry, Other
- Will fault indicators require GPS tagging and site photos to populate your asset registry and GIS? Options: Yes, No
- Do field crews need local test buttons or visible LEDs for on-pole verification during patrols? Options: Yes, No
- Which internal teams should receive fault indicator alarms (operations console, field technicians, GIS), and how should alarms be prioritized?
- How should fault indicator events be formatted for downstream systems (DNP3 binary input, IEC 61850 report, or e-mail/SMS notification)? Options: DNP3 BI, IEC 61850 report, Email/SMS, Other
Install Pole- and Pad-Mount Devices
- Which spare parts and consumables must accompany each pole- or pad-mount device deployment (fuses, gaskets, control cables, mounting hardware)?
- What acceptance evidence will validate mechanical installation and site readiness for pole- and pad-mount devices (as-built photos, torque logs, and lockout/tagout certificates)? Options: As-built photos, Torque logs, LOTO certificates, All of the above
- Which ground-grid, bonding, and foundation details from your standard drawings must installers follow at pad-mount locations?
- How often are field inspections required before energization per your work-order and safety procedures? Options: Pre-energization and final, Once only, As required by site
- What mechanical clearance and pole-loading thresholds (wind, ice, conductor clearance) must be validated against your utility standards during installation?
Deploy Communications Network and Backhaul
- Which backhaul medium do you prefer on each feeder (cellular LTE/5G, licensed microwave, fiber, or private RF), and for which sites? Options: Cellular, Microwave, Fiber, Private RF
- Which gateway or concentrator device types are pre-approved on your network (RTU, protocol gateway, certified cellular modem)?
- What latency and packet-loss service levels are required for protection-related messaging on each backhaul segment? Options: <100 ms, 100-500 ms, >500 ms, Custom
- Who provides SIM/APN credentials and signs the network access agreement for cellular backhaul?
- Which party will own and monitor the network operations center (NOC) for the deployed communications (your NOC, carrier, third-party, or shared)? Options: Your NOC, Carrier, Third-party, Shared
Commission Protection and Control Settings
- What protection coordination study file name/version and relay curve references will be used to derive trip settings?
- What is the maximum permitted upstream breaker clearing time and minimum pickup thresholds that settings must honor for coordination?
- How will you verify protection settings during commissioning (secondary injection reports, primary fault injection with current clamps, staged tests)? Options: Secondary injection reports, Primary fault injection, Staged tests, All of the above
- Which relay standard or internal practice (reference IEEE/IEC or utility guide) governs your protection-setting tolerances?
- Identify device tags, trip logic blocks, and the single-line diagram pages that must be updated after commissioning.
Deploy FLISR Automation Scheme
- Are FLISR sequence-of-operations and manual fallback procedures already documented for the target feeders? Options: Yes, No, Partial
- Estimate the number of switching devices and sectionalizing points required for a functional FLISR loop on each feeder. Options: 1-3, 4-8, 9+
- Describe the end-to-end FLISR response-time requirement from fault detection to reclosing and customer restoration target.
- Where will FLISR control logic execute (local device, edge gateway, or DMS) and which platform must be certified for runbook execution? Options: Local device, Edge gateway, DMS, Hybrid
- Which DNP3 or IEC 61850 objects and command sequences must FLISR use for isolation and reclose actions?
Configure Volt-VAR Optimization
- Who owns volt-var curves and setpoints (distribution engineering, DER integration team, or operations)? Options: Distribution engineering, DER integration team, Operations, Joint
- What feeder load profiles, historical SCADA voltage logs, or voltage excursion reports can you provide to size VVO strategies?
- Which telemetry granularity do you require from regulators and capacitor controllers for VVO control (1s, 1min, 5min)? Options: 1s, 1min, 5min, Other
- How do you define acceptable tap-change rates to prevent excessive regulator operations (max taps per day or per event)?
- Which reserve margin (percent headroom or fixed kVAr) must VVO algorithms preserve for rapid DER ramp events?
Integrate Devices with SCADA/DMS (DNP3/IEC 61850)
- What acceptance tests will validate device SCADA/DMS integration (DNP3 point mapping verification, IEC 61850 logical node mapping, telemetry delta tests, and end-to-end alarm delivery)? Options: DNP3 point mapping verification, IEC 61850 LN mapping, Telemetry delta tests, End-to-end alarm delivery, All of the above
- Which SCADA or DMS endpoints must devices speak to (RTU IP endpoints, historian endpoints, or DMS API) and what are the endpoint identifiers?
- How often must device clocks be synchronized and which protocol is required (NTP daily, PTP continuous, other)? Options: NTP daily, PTP continuous, NTP hourly, Other
- Which security mechanisms must be enforced for protocol transport (DNP3 Secure Authentication, TLS for IEC 61850 MMS, VPN tunnels)? Options: DNP3 Secure Authentication, TLS (IEC 61850 MMS), VPN, Other
- Where should the definitive tag-to-point mapping be documented for handover (single-line diagram, SCADA tag list, or integration workbook)? Options: Single-line diagram, SCADA tag list, Integration workbook, Other
Operator Training and Operational Procedures
- Who are the operator roles requiring training and certification (SCADA operators, field switching crews, protection engineers)? Options: SCADA operators, Field switching crews, Protection engineers, All
- What operational procedures or switching orders do you require as deliverables (FLISR runbooks, switching sequences, emergency rollback)?
- Which training format do you prefer for operators: classroom, hands-on device lab, simulator-based DMS training, or a blended approach? Options: Classroom, Hands-on device lab, Simulator-based DMS, Blended
- Will you require formal certification assessments and training completion records for compliance auditing? Options: Yes, No
- Do you need training materials packaged for your learning management system with SCORM or xAPI compatibility? Options: Yes, No
Mutual Commit

Finalize commercial terms, warranties, SLAs, support commitments, and project governance so both parties are aligned on obligations and billing triggers.
Agreement Modules
- Purchase Agreement / Order Confirmation
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Product Workmanship and Performance Warranty
- Support & Spare Parts Agreement
- Acceptance Test Plan and Commissioning Criteria
- Project Governance and Change Control
- Payment Schedule and Billing Triggers
- Change Order Agreement
- Regulatory & Cybersecurity Compliance Addendum
Deployment

Operationalize rollout with readiness checks, execution, and outcome validation.
1. Pre-Deployment Readiness
  
  Lock concrete readiness facts — site access, owners, permitting, communications availability, and integration contacts — required before execution begins.
  Pre-Deployment Questions
  Environment and site access
  - Has physical site access been confirmed for all sites in scope? (so we can schedule crews and request keys/permits) Options: Yes — access confirmed for all sites, Partially — some sites confirmed, No — access not confirmed, Not applicable — remote-only work
  - If any sites are not confirmed, list the site identifier(s) and the expected access-ready date for each (one line per site)
  - Are final electrical drawings/single-line diagrams available for every site the deployment will touch? (these are required for protection coordination and safe field work) Options: Yes — final drawings provided, Provided but draft, No — drawings pending, Not applicable
  - If drawings are pending, what is the target delivery date or responsible team for each site?
  Communications and integration
  - Is site communications (cell/ethernet/utility radio) verified for every site in scope? (this confirms we can reach devices during install and commissioning) Options: Yes — connectivity verified at all sites, Partially verified, No — not verified, Not required — offline commissioning
  - If connectivity is not verified, who will resolve it and by when? (pick the responsible party and provide expected resolution date) Options: Buyer communications team — will resolve, Third-party carrier/vendor — will resolve, The seller to coordinate and resolve, Undetermined — need assistance
  - Has the buyer identified SCADA/DMS integration contacts and the type of integration endpoint (DNP3/IEC 61850/other)? (we need the integration owner to approve interface tests) Options: Yes — integration contact and protocol identified, Contact identified, protocol pending, No — integration contact not identified, Not applicable
  - If identified or partially identified, state the integration contact's role (e.g., SCADA engineer, IT/DMS lead) and the preferred integration window (weekday daytime, weekend, after-hours).
  People and ownership
  - Has the buyer assigned named owners for these workstreams: site access, electrical contractor, communications, SCADA/DMS integration, and safety sign-off? (owners enable approvals and issue resolution) Options: All workstreams have owners, Some workstreams have owners, No owners assigned yet, Single program manager assigned for all
  - If some or no owners are assigned, list the missing workstream owners and the planned assignment date for each.
  Permits, timing, and constraints
  - Are required permits, interconnection approvals, and any utility-specific compliance gates in place for each site? (permits block energization and legal acceptance) Options: Yes — all permits/approvals in place, Some permits pending, No — permits not started, Not required
  - Are there scheduling constraints or blackout windows (operational restrictions, seasonal weather, regulatory testing) that will limit field work? If yes, list constraint and date range.
2. Configuration Details
  
  Capture exact configuration values the deployment team will use — protection settings, protocol mappings (DNP3/IEC), IP endpoints, credentials, and commissioning parameters.
  Configuration Details
  ENVIRONMENTS & ENDPOINTS — production integration targets
  - Enter the production environment name (Default: prod)
  - Select the SCADA/DMS integration endpoint type the devices will talk to (choose one) Options: DNP3 (master over TCP/UDP), DNP3 over TLS (secure DNP3), IEC 61850 MMS, Modbus TCP, HTTPS REST API, Other
  - Enter the SCADA/DMS integration endpoint address the devices will connect to (format: tcp://<IP or host>:<PORT> or https://<host>; include protocol scheme)
  DEVICE IDENTITY & NETWORK — naming and addressing
  - Enter the device hostname prefix to apply to all deployed devices (Default: DA-). This prefix will be used verbatim at device naming time (e.g., DA-0001).
  - Select the device IP addressing method to apply to devices Options: Static, DHCP
  - If Static addressing: enter the device primary IPv4 address to apply (format: x.x.x.x). Leave blank if DHCP.
  PROTOCOLS & SECURITY — communication variant and auth
  - Select the communication protocol variant devices will use to the integration endpoint Options: DNP3 over TCP, DNP3 over TLS, IEC 61850 MMS, IEC 61850 MMS with TLS, Proprietary serial/tunnel (specify)
  - Select the authentication method for the integration (Default: Username/Password). DO NOT paste secrets — provide non-secret identifiers only. Options: None, Username/Password (secret exchanged via your secrets manager), Client certificate (certificate name; secret exchanged via your secrets manager), Mutual TLS (certificate name)
  - Enter the non-secret integration account identifier to use (username or client ID). DO NOT paste passwords, private keys, or tokens.
  COMMISSIONING & PROTECTION — applyable settings and templates
  - Enter the protection settings file location the deployment should apply (URL or file path — format examples: https://..., s3://..., file://...; include filename and extension)
3. Deployment
  
  Execute field installations, protection coordination, commissioning, system integration, and operator training with clear owners and timelines.
4. Go-Live Validation
  
  Complete mandatory pre-energization and acceptance checks — safety sign-offs, interconnection approvals, acceptance test results, and cybersecurity verifications — before declaring sites live.
  Checklist items
  - Obtain written Permission to Operate (PTO) / interconnection approval
  - Execute Lockout/Tagout (LOTO) and obtain safety sign-off
  - Validate energization rollback and abort procedures
  - Complete and approve commissioning acceptance test reports
  - Verify SCADA/DMS command and telemetry acceptance
  - Confirm communications performance tests passed
  - Complete cybersecurity hardening and verification
  - Deliver as-built documentation and configuration baseline
  - Confirm site inspections and physical compliance
  - Complete operator training and user acceptance sign-off
  - Obtain joint Go-Live Authorization document signed
Success

Monitor reliability KPIs (SAIDI/SAIFI), confirm performance against success criteria, and maintain a shared channel for issues, enhancements, and lifecycle support.
Success Reviews
- Go-Live Health Check
- First Measurement Review
- Acceptance Gate Decision
- Quarterly Reliability Review
Issues & Enhancements
- Schedule the remediation verification check that will confirm closure of conditional items.
- Document root causes for any out-of-tolerance metrics and assign corrective actions with dates.
- Confirm the evidence package and timeline required for the Acceptance Gate meeting.
- Produce the measurement evidence package including raw telemetry extracts, calculation spreadsheets, and data-source validation notes.
- Open remediation tasks for each identified root cause with completion criteria and target dates.
- Confirm the Acceptance Gate meeting date and the required deliverables listed in Solution Scope.
- Restate acceptance criteria
- A documented acceptance decision per Solution Scope criterion is recorded in the journey.
- For any non-passing criteria, a remediation plan with verification steps and target dates is agreed.
- Evidence package and decision artifacts are uploaded to the shared workspace for auditability.
- Publish the formal acceptance decision and evidence package to the shared workspace.
- Create remediation tickets for any conditional or failed criteria with verification steps and target resolution dates.
- Performance trends and variance review
- Confirm SAIDI and SAIFI remain within acceptable variance of the Solution Scope targets or document mitigation steps.
- Reduce the count of high-priority open issues and agree deadlines for remaining items.
- Maintain a clear lifecycle support plan for firmware, settings, and hardware replacement needs.
- Close or re-prioritize high-priority tickets and update the shared issue channel with status and next steps.
- Schedule targeted network or device stability work for sites with recurring communications outages.
- Prepare the next quarter's evidence package for SAIDI and SAIFI trend verification.
- Re-confirm success criteria and ownership
- Deployment checklists for all live sites are marked complete or have documented remediation plans.
- Operator onboarding status confirmed and any training gaps scheduled for closure.
- Critical blockers identified with remediation tasks and target dates.
- Publish the consolidated deployment validation checklist and evidence package to the shared workspace.
- Create remediation tickets for each critical blocker with target resolution dates.
- Schedule the data-collection window and the First Measurement Review meeting within the 4-10 week window.
- Present first-cycle measurements
- Determine whether SAIDI, SAIFI, and FLISR auto-restore rate are trending toward the targets recorded in Solution Scope.
- Communications and device availability
- Data quality and telemetry health check
- Deployment and commissioning validation
- Present outcome data and evidence
- Early operational signals and user onboarding
- Open issues, enhancements, and lifecycle support
- Record pass/fail per criterion and decision
- Root-cause diagnosis for gaps
- Agree remediation plan for failed or conditional items
- Agree corrective actions and timelines
- Open issues and immediate remediation
- Action plan and next quarter commitments

Explore more templates Use this template

CustomerNode™

CustomerNode™

Distribution Automation

Pre-Sales

Qualification

Outcome Discovery

Solution Evaluation

Solution Scope

Mutual Commit

Deployment

Pre-Deployment Readiness

Configuration Details

Deployment

Go-Live Validation

Success