Quick Orientation: Where Are We Starting?

• Which title best describes your primary role in deciding on distribution automation investments? Options: Distribution Engineering Manager, Grid Modernization Program Lead, VP/Director of Operations, System Planning Engineer, Regulatory Affairs / Policy, Procurement / Capital Planning, Other
• Which geographic areas or specific circuits should we focus on for this conversation (names, feeders, or service territories)?
• How urgent is it for your team to show measurable reliability improvement from automation on those circuits? Options: Immediate — this quarter, Near-term — 3–12 months, Planned — 12–24 months, Longer horizon — 2+ years
• Who else outside your team needs to be convinced for a pilot or deployment to proceed (list roles or groups)?
• In one sentence, what single outcome would make this initiative feel like a clear win for you?

If Your Regulator Asked for Proof Tomorrow, What Would You Show?

• When you think about regulatory scrutiny, what specific reliability metric or threshold keeps coming up in conversations or filings? Options: SAIDI, SAIFI, CAIDI, Momentary Interruption Rate (MIR), Customer Minutes Interrupted (CMI), Other / Multiple
• What is your current baseline for those metrics on the target circuits (please list numbers or ranges)?
• What target improvement would your regulators or leadership expect to justify automation investment? Options: <10% improvement, 10–25% improvement, 25–50% improvement, >50% improvement, Not yet defined
• Are there financial incentives or penalties tied to those metrics today (e.g., performance-based rates, fines, reliability incentives)? Options: Yes — penalties, Yes — incentives, Both, None, Unsure
• How do you currently prove the cause and duration of outages (manual logs, SCADA/DMS reports, customer complaints, automated event logs)? Options: SCADA/DMS event logs, Manual crew reports, Customer call data, OMS integration, Combination / Other

Where the Grid Keeps You Up at Night

• If you had to name the one recurring reliability problem you’d eliminate first, what would it be and why?
• Which failure modes on these feeders generate the largest share of customer minutes interrupted? Options: Overhead conductor faults, Equipment failure (recloser,fuse,transformer), Vegetation/animal contacts, Transient faults that become permanent, Protection miscoordination, DER-related events/backfeed
• How often do crews perform manual switching or sectionalizing to restore service on the circuits you care about? Options: Daily, Weekly, Monthly, Rarely, Never
• Tell us about a recent outage that felt avoidable — what happened, who was impacted, and how did it feel internally?
• What downstream effects does that recurring problem cause (customer complaints, lost revenue, regulatory inquiries, crew overtime, safety risks)? Options: Customer complaints / PR, Regulatory reporting, Increased O&M costs, Crew safety / fatigue, System instability, Other

What DERs Are Doing That You Didn't Plan For

• How often do distributed energy resources create operating conditions on these feeders that force you to deviate from standard restoration procedures? Options: Regularly — every week, Often — monthly, Occasionally — quarterly, Rarely, Never / Not applicable
• What percentage of customer meters on your priority circuits are behind DERs (choose the best range)? Options: <5%, 5–15%, 15–30%, 30–50%, >50%, Unknown
• Which kinds of DERs are most common and relevant to restoration/protection complexity? Options: Rooftop solar PV, Battery storage, EV chargers, Microgrids, Commercial/industrial generation, Other
• How much visibility and control do you currently have over those DERs from your SCADA/DMS (none, partial, full)? Please give examples. Options: None, Limited (intermittent telemetry), Partial (some devices visible/control), Full visibility & control, Varies by vendor
• Have DERs ever prevented a simple sectionalizing restoration or created a protection coordination problem? Tell the story.

How Much Are You Willing to Spend to Stop Losing Sleep?

• Do you have an initial budget guardrail for a pilot or first-phase automation rollout on these circuits? Options: <$50k per circuit, $50k–$200k per circuit, $200k–$500k per circuit, >$500k per circuit, No predefined guardrail
• What types of funding vehicles are available or preferred for this work? Options: Capital (CAPEX), Operating (OPEX), Grants / Federal funding, Performance-based rate recovery, Third-party financing / ESCO, Other
• What is the minimum acceptable payback or justification you require (e.g., % reliability improvement, annual O&M savings, avoided penalties)? Options: Specific % reliability improvement, Dollar ROI within X years, Operational efficiency / crew time saved, Regulatory compliance / avoidance of penalties, Not quantified yet
• If a solution reliably delivered your target SAIDI/SAIFI improvement, how flexible would you be on budget to accelerate rollout? Options: Very flexible — accelerate now, Somewhat flexible — limited additional funds, Not flexible — must stay within current guardrail, Unsure
• What procurement or approval steps typically delay funding decisions (board approval, rate case timing, vendor evaluation, inter-departmental alignment)? Options: Board/Executive sign-off, Rate case schedule, Capital budget cycles, Vendor qualification / testing, Regulatory review, Other

What Would Real Success Feel Like to Your Operators?

• Beyond headline SAIDI/SAIFI numbers, what operational behaviors would signal to your crews and control room that the system is genuinely more resilient? Options: Faster sectionalizing & restoration, Fewer manual switching actions, Clearer fault location, Reduced customer escalations, Automated reclose success rates, Other
• What acceptance tests and evidence would you require before signing off on a deployment (end-to-end FLISR test, protection coordination validation, comms reliability tests, operator drills)? Options: End-to-end FLISR behavior, Protection coordination study results, Communications latency/reliability tests, Field acceptance test logs, Operator training & simulation, Other
• Who in your organization will be the ultimate signatory for acceptance (operations director, engineering manager, regulatory, third-party inspector)? Options: Operations Director, Distribution Engineering Manager, System Planning, Regulatory Affairs, Third-party QA/Inspector, Other
• How important is operator experience and training in acceptance — do you expect classroom + simulator + field training, or lighter refreshers? Options: Full training program (classroom+sim+field), Classroom + field only, Light refresher sessions, Train-the-trainer model, No strong preference yet
• What failure or shortfall would be a deal-breaker even if other metrics improved? Describe non-negotiable constraints.

Can Your Systems Talk to Our Equipment Without Holding Hands?

• Which SCADA/DMS/EMS platforms do you operate that our devices must integrate with (vendor names and version if known)?
• Which communications transports are acceptable or preferred for device connectivity on target feeders? Options: Fiber, Private RF / microwave, Public cellular (LTE/5G), Licensed radio, Powerline carrier, Satellite, Hybrid — combination
• Which protocols do your systems require or prefer for device telemetry and control? Options: DNP3, IEC 61850 (GOOSE/MMS), Modbus, Proprietary, MQTT/REST APIs, Other
• What are your minimum latency, packet-loss, and uptime expectations for field device comms that support FLISR? Options: <100 ms latency, <500 ms latency, <2 s latency, Uptime 99.9%+, Uptime 99%
• Are there cybersecurity or NERC/CIP requirements we must meet (PKI, role-based access, encryption standards, audit logging)? Please specify. Options: NERC CIP, Internal security policy only, Vendor security review required, Third-party penetration test required, Other / Unsure
• What data handoff formats and cadences do you need for performance reporting (raw event logs, aggregated reliability reports, near-real-time telemetry, daily summaries)? Options: Daily/weekly summaries, Custom API integration, Raw event logs (CSV/IEC), Aggregated reliability reports, Near-real-time telemetry stream

If We Could Wave a Wand — What Would the Post-Project Day Look Like?

• Imagine 18 months after deployment: what three measurable changes would make you tell leadership this project was a success? Options: X% reduction in SAIDI, X% reduction in SAIFI, Fewer manual switching events, Reduced crew overtime, Lower outage-related customer complaints, Faster mean time to restore (minutes)
• How would customers, regulators, and field crews each notice the difference — what stories would they tell?
• What ongoing operational model do you prefer after rollout (utility-owned operations, vendor-managed services, hybrid)? Options: Utility-owned operations, Vendor-managed services (O&M), Hybrid — vendor supports during warranty, Third-party integrator
• What metrics or reporting cadence would keep leadership confident the outcomes are sustained (monthly dashboards, quarterly reviews, annual audits)? Options: Monthly dashboards, Quarterly executive reviews, Real-time alerts + monthly summary, Annual performance audit
• What risks do you foresee in maintaining those outcomes after initial deployment (spare parts, staff turnover, firmware updates, funding for sustainment)? Options: Spare parts inventory, Staffing / turnover, Lifecycle firmware upgrades, Ongoing funding, Vendor support continuity, Other

One Small, Low-Risk Step We Could Take Together

• If we proposed a single pilot that would reduce outage minutes in a small area — which pilot scope would you prefer? Options: Single feeder FLISR pilot, Two-feeder comparative pilot, Targeted protection coordination + DER test, Communications reliability pilot only, Other
• What would you require to call that pilot a success after 3–6 months (specific metrics, operator sign-off, customer impact evidence)?
• What data, access, or approvals would we need from you to get a pilot running quickly? Options: Feeder models / protection settings, SCADA/DMS integration access, Site access for installation, Communications path details, Executive sponsorship / funding
• What concerns would make you hesitate to start a pilot, and what would reduce those concerns?
• Realistically, how soon could you be ready to greenlight a small pilot if the scope and budget aligned? Options: Immediately, Within 1–3 months, 3–6 months, 6–12 months, Longer / Unsure
• Who should be on the core decision and technical team from your side to move from conversation to pilot execution?

• Current State Confirmation
• Consequence & Target Outcomes Workshop
• Circuit Failure-Mode Simulation & Diagnosis
• Solution Experience — Live FLISR Walkthrough (Proof on Customer Circuits)
• Pilot Definition, Acceptance Criteria & Mutual Commit

• Engineering to itemize and prioritize any technical blockers uncovered during the live walkthrough.
• Prove (or disprove) that automated switching and sensing can achieve the stated future-state metrics on each simulated scenario.
• Identify specific technical gaps (telemetry, settings, communications) that must be closed to realize the outcome.
• Produce a prioritized list of changes/controls required before a field pilot or live deployment.
• Engineering team to produce simulation result packets (timelines, device logs, customer-restored counts) for each scenario.
• Customer protection and relay engineers to review and comment on suggested setting changes from the simulation.
• Agree on any additional scenarios to simulate before the live FLISR walkthrough.
• Confirm Preconditions & Acceptance Criteria
• Prove the future-state outcomes materially on customer circuits for prioritized failure modes.
• Obtain explicit stakeholder validation (verbal or written) that the demonstrated behaviors meet the agreed acceptance criteria.
• Document any remaining technical blockers and a clear path to resolve them during pilot preparation.
• Facilitator to capture and circulate demo logs, timelines, and the customer's validation responses within 48 hours.
• Introductions & Meeting Objectives
• Customer to confirm participants and sign-off (or list objections) to proceed to pilot planning.
• Pilot Scope & Equipment List
• Produce a fully scoped pilot plan with clear acceptance criteria that map directly to the customer's future-state metrics.
• Assign owners and dates for all pilot tasks so no ambiguity remains about responsibilities.
• Secure a mutual commit to the pilot execution plan and a schedule for the first acceptance test window.
• Draft and circulate the Pilot Statement of Work (scope, timeline, acceptance tests) for signatures.
• Customer to confirm site access, crews, and any procurement or permitting required before installation.
• Schedule the pilot kickoff and the first acceptance test window, and assign the data/reporting owner.
• Agree on one crystal-clear current state sentence that will drive the Solution Experience.
• Confirm the dataset (models, fault logs, protection settings, telemetry map) is complete or identify gaps and owners.
• Establish who will provide any missing artifacts and by what date so the next meetings run against accurate inputs.
• Customer to deliver circuit one-line(s), protection settings, recent fault logs, and telemetry map to the project folder.
• Facilitator to draft and circulate the agreed one-sentence current state for written confirmation.
• Assign data owners and deadlines for any missing artifacts required for simulations and live exercises.
• Review Current-State Consequences
• Make the consequence explicit in operational and financial terms for the selected circuits.
• Produce clear, measurable future-state outcome statements (one-liners) tied to regulatory and customer metrics.
• Agree on which circuits and failure modes will be used to prove value in the live experience and pilot.
• Customer to deliver baseline SAIDI/SAIFI calculations and outage cost assumptions for the selected circuits.
• Facilitator to convert future-state sentences into testable success metrics and provide an initial measurement plan.
• Jointly finalize the list of fault modes (single-phase, multi-phase, DER backfeed, communications loss) to be simulated/demonstrated.
• Scenario Selection & Hypotheses
• One-sentence Current State Draft
• Live Scenario 1: Isolation & Fast Restoration
• Run Fault Simulation: Traditional Fault Cases
• Regulatory & Customer Thresholds
• Acceptance Test Scripts & Pass/Fail Criteria
• Roles, Responsibilities & Timeline
• Run Fault Simulation: DER-Influenced Cases
• Define Future-State Outcome Statements
• Telemetry, Topology & Protection Inventory Review
• Validation Checkpoint 1
• Live Scenario 2: DER Interaction & Edge Case Handling
• Data Collection, Reporting & Regulatory Package
• Set Quantitative Targets & Success Metrics
• Diagnosis & Gap Analysis
• Fault History & Stakeholder Impact Review
• Validation Checkpoint 2 & Forced Confirmation
• Mutual Commit & Next Milestones
• Decision: Priority Circuits & Failure Modes
• Pre-demo Data Validation & Missing Items
• Capture Failures, Workarounds & Next Steps

• Supply and install pole‑mount automated recloser
• Supply and install pad‑mount sectionalizing switch
• Install line‑mounted fault circuit indicators
• Install capacitor bank controller and wiring
• Install voltage regulator controller and CT/VT wiring
• Install pole‑top communications radio and antenna
• Deploy substation communications gateway (protocol translator)
• Integrate field devices into SCADA/DMS (DNP3/IEC 61850)
• Commission devices and perform onsite acceptance testing
• Program and deploy FLISR automation into the DMS
• Perform device firmware upgrades and cybersecurity hardening
• Deliver on‑site operator training for devices and DMS workflows

Supply and install pole‑mount automated recloser

• How many pole‑mount automated reclosers are you planning to deploy at initial rollout? Options: 1-5, 6-20, 21-50, 51+
• What distribution voltage class do the target circuits use? Options: 5 kV-15 kV, 15 kV-35 kV, Other
• Are the reclosers required to support sectionalizing, auto‑lockout, and auto‑self‑healing schemes? Options: Yes, No, Partially — specify in next field
• If partially or custom, specify required protection functions and coordination rules (e.g., reclosing counts, lockout thresholds, fuse saving priorities).
• Which communications methods are acceptable for these reclosers? Options: Cellular (LTE/5G), Private RF mesh, Utility fiber/leased line, Powerline carrier, Other
• Who will be responsible for physical installation and commissioning of pole‑mount devices? Options: Vendor turnkey, Utility crews, Contractor hired by utility, Hybrid (specify)

Supply and install pad‑mount sectionalizing switch

• How many pad‑mount sectionalizing switches are in scope for the initial phase? Options: 1-5, 6-20, 21-50, 51+
• What enclosure and environmental ratings are required (e.g., NEMA type, IK rating, salt fog)?
• Are there specific fault current / interrupting rating requirements for the switches? Options: Yes — provide values in next field, No — standard utility ratings acceptable
• Please provide required maximum fault current and continuous ampacity (or attach spec).
• Do these pad‑mount devices need integrated communications and remote telemetry out of the box? Options: Yes — include radio/PLC, No — telemetry via nearby pole device, Optional
• Will transformer ownership, clearances, or pad/grounding upgrades be required at installation sites? Options: Yes, No, Unknown — site survey required

Install line‑mounted fault circuit indicators

• How many line‑mounted fault indicators are targeted and on what conductor types (ACSR, AAAC, covered conductor)?
• Is real‑time communications required for each indicator or is periodic data collection sufficient? Options: Real‑time, Periodic (polling), No communications required
• Which reporting/trip data is required from indicators (fault time, magnitude, direction, GPS location)? Options: Fault time, Magnitude, Fault direction, GPS location, Other
• Are the indicators expected to integrate into the FLISR logic (yes/no) or only for crew location and analytics? Options: Integrate into FLISR, Crew location/analytics only, Both
• Are pole conditions and mounting accessories (brackets, insulated standoffs) required to be supplied as part of the scope? Options: Yes — supply mounting hardware, No — utility will provide mounts, Site survey to confirm

Install capacitor bank controller and wiring

• Is the capacitor bank existing or new? If existing, provide current controller type. Options: New bank to be supplied, Existing bank — replace controller, Existing controller — retain
• What control functions are required (automatic step switching, time scheduling, volt‑var control, remote ON/OFF)? Options: Automatic step switching, Time scheduling, Volt‑var control, Remote ON/OFF, Other
• Are CTs/VTs available on the bank for required metering and control, or does wiring and instrument transformer installation need to be included? Options: CT/VTs present, CT/VTs required to be installed, Unknown — site survey required
• What communications protocol and media are required for the controller (DNP3, Modbus, IEC 61850, cellular, RF)? Options: DNP3, Modbus, IEC 61850, Proprietary, Cellular, RF mesh, Other
• Define acceptance criteria for capacitor bank performance (voltage banding, response time to setpoint, switching cycle limits).

Install voltage regulator controller and CT/VT wiring

• How many voltage regulator controllers are required and what regulator types (line‑drop compensator, LTC, pole‑mounted regulator)?
• Are CT/VT secondary wiring and instrument transformers present at each regulator site or must they be supplied and wired? Options: Present and accessible, Must be supplied and wired, Partial — some sites need them
• Should controllers support advanced functions (CVR, volt/var coordination, remote setpoint control)? Options: Yes — CVR, Yes — volt/var coordination, Yes — remote setpoint, No — basic control only
• Preferred communications and telemetry protocol for regulators (DNP3, IEC 61850, Modbus, other)? Options: DNP3, IEC 61850, Modbus, Proprietary, Other
• Who will perform protection and tap coordination studies and approve regulator settings? Options: Vendor, Utility engineering, Third‑party consultant, Joint approval

Install pole‑top communications radio and antenna

• Which communications technologies are under consideration for pole‑top radios? Options: Licensed private RF, Unlicensed mesh (900 MHz/2.4 GHz), Cellular backhaul, LoRa/LPWAN, Other
• Do radios need to support secure tunnels and specific protocols (DNP3 over TLS, IEC 61850 Goose, MQTT)? Options: Yes — specify protocols, No — basic IP only, Optional
• Are there line‑of‑sight or topographic constraints that require directional antennas or tower mounts? Options: Yes — directional/towers required, No — omni antennas acceptable, Unknown — site survey required
• Will power for radios be drawn from device battery, pole service, or separate solar/battery systems? Options: Device internal battery, Pole service AC, Solar + battery, Other
• Any cybersecurity or vendor hardening standards to meet for radios (NERC CIP, IEC 62443, utility policy)? Options: NERC CIP, IEC 62443, Utility policy, No specific standard, Other

Deploy substation communications gateway (protocol translator)

• Does the substation gateway need to translate between which protocols? Options: DNP3 <-> IEC 61850, Modbus <-> DNP3, Proprietary <-> DNP3/IEC 61850, Other
• Will the gateway be installed in an existing substation rack or require new panel space and AC/DC provisioning? Options: Existing rack space available, New panel space required, Unknown — site visit required
• Is redundancy/high‑availability required for the gateway (dual units, hot standby)? Options: Yes — redundant, No — single unit, Optional
• What SCADA/DMS vendor(s) and versions will the gateway need to interoperate with?
• Are certificate management, PKI integration, or specific encryption requirements needed for SCADA links? Options: Yes — PKI/certificates, Yes — pre‑shared keys, No special requirements, Unknown

Integrate field devices into SCADA/DMS (DNP3/IEC 61850)

• Which DMS/SCADA platform and version will be the primary integration target?
• Which protocols are required for each device class (map devices to protocol: recloser, switch, controller)?
• Will the utility require object mapping, data model alignment, and point naming standards (e.g., IEEE C37.118, utility naming convention)? Options: Yes — utility naming standard, No — vendor defaults acceptable, Partial — will provide guidance
• Is on‑site integration and DMS acceptance testing required, or can integration be performed remotely before site commissioning? Options: On‑site required, Remote acceptable, Hybrid
• Who owns change control for DMS schema and SCADA objects during integration (vendor, utility, third‑party)? Options: Vendor, Utility, Third‑party integrator, Joint control

Commission devices and perform onsite acceptance testing

• What acceptance tests are mandatory for you (mechanical, electrical, communications, protection functional tests)? Options: Mechanical checks, Electrical functional tests, Communications verification, Protection and relay testing, Other
• Do you require witnessing of acceptance tests by utility staff or regulatory/third‑party inspectors? Options: Yes — utility staff, Yes — third‑party, No — vendor test report sufficient
• What criteria define pass/fail for acceptance (e.g., successful DNP3 point updates within X seconds, protection trip times within Y ms)?
• Are test procedures and checklists required to be provided in advance for review? Options: Yes — provide prior to commissioning, No — standard vendor procedures OK
• Will the utility provide grounding/test equipment and site access or should vendor bring required tools and safety equipment? Options: Utility provides, Vendor provides, Shared — specify

Program and deploy FLISR automation into the DMS

• Does the utility already have FLISR logic blocks or do we need to design new automation schemes? Options: Existing FLISR — integrate, Design and implement new FLISR, Hybrid — modify existing
• What is the desired FLISR behavior (islanded restoration, automated sectionalizing, customer prioritization rules)? Options: Automated sectionalizing, Partial islanding, Customer priority restoration, Other
• Which failure modes must the FLISR solution handle (single‑phase fault, multi‑phase fault, sustained outage, momentary interruptions)? Options: Single‑phase fault, Multi‑phase fault, Sustained outage, Momentary
• What performance metrics and SLAs are required for FLISR response (e.g., detection to restore within X minutes, percent of faults auto‑restored)?
• Who will own coordination of automation rules and approve simulations—utility operations, distribution engineering, or a third party? Options: Utility operations, Distribution engineering, Third‑party consultant, Joint approval

Perform device firmware upgrades and cybersecurity hardening

• Do devices need to meet specific cybersecurity standards (NERC CIP, IEC 62443, utility policy)? Options: NERC CIP, IEC 62443, Utility policy, None specified, Other
• Is bulk firmware upgrade capability required remotely, and must upgrade windows be restricted to scheduled maintenance windows? Options: Remote bulk upgrades required, Local only, Must adhere to scheduled windows
• Are device inventories and firmware baseline reports required as deliverables? Options: Yes — full inventory and baseline, No — not required, Partial
• Will PKI/certificate provisioning, secure boot, and image signing be part of the hardening scope? Options: Yes — include PKI/cert provisioning, No — other mechanisms, Unknown — need utility guidance
• Who will be responsible for ongoing vulnerability management and future patching—vendor managed service or utility IT operations? Options: Vendor managed, Utility IT, Joint model

Deliver on‑site operator training for devices and DMS workflows

• Which audiences should be trained (field crews, protection engineers, system operators, IT/SCADA)? Options: Field crews, Protection engineers, System operators, IT/SCADA, All of the above
• Preferred training format(s) and duration (classroom, hands‑on lab, on‑the‑job, half‑day, full‑day, multi‑day)? Options: Classroom, Hands‑on lab, On‑the‑job, Half‑day, Full‑day, Multi‑day
• Do you require course materials, operator manuals, and test scenarios to be delivered electronically and in hard copy? Options: Electronic only, Electronic + hard copy, Electronic + LMS upload, Other

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Acceptance Test Protocol (ATP)
• Commercial Terms & Pricing Schedule
• Payment & Milestone Schedule
• Regulatory Justification & Cost-Recovery Package
• Performance Guarantees & Warranty
• Insurance, Bonds & Liability Coverage
• Change Order & Scope Management
• Integration & Interface Agreement
• Cybersecurity & Compliance Attestation
• Site Access, Permits & Installation Responsibilities
• Training, Operations & Maintenance Handover
• Spare Parts, Inventory & Logistics Commitments
• Termination, Exit & Post-Contract Support
• Renewal & Future Enhancements Agreement

• Outcomes Review — Reliability & Integration
• Lessons Learned — Technical & Field
• Operational Acceptance & Handover
• Regulatory & Commercial Closeout
• Continuous Improvement & Shared Channel Kickoff

• Identify any conditional deliverables that block regulatory sign-off and assign owners.
• Publish a concise Lessons Learned document with action owners and due dates.
• Revise the commissioning checklist and distribute to field teams and customer engineering.
• Create prioritized product tickets for any firmware/hardware fixes discovered.
• Handover Scope & Roles
• Complete formal operational acceptance with documented runbooks, dashboards configured, and users provisioned.
• Establish alarm-to-ticket mapping and escalation SLAs so incidents are handled consistently.
• Ensure operations feel confident to operate and troubleshoot without vendor intervention for Tier-1 events.
• Deliver final runbook package and recorded runbook walkthroughs to operations repository.
• Provision dashboard access for named operations users and verify permissions.
• Publish escalation contact list and SLA matrix into the shared channel.
• Commercial Reconciliation
• Secure approvals for regulatory submission and confirm commercial reconciliation steps to close the project financials.
• Agree on a repeatable benefits reporting cadence and responsible owners for continued measurement.
• Introductions & Meeting Objectives
• Finalize and file the regulatory justification package and archive supporting evidence.
• Complete invoice reconciliation and list any retained amounts with release conditions.
• Schedule the first benefits-status report for the agreed cadence and owner.
• Purpose & Access
• Stand up a secure shared channel with access, triage workflow, and agreed SLAs for issues and enhancements.
• Create a prioritized backlog template and agree first 90-day improvement initiatives.
• Schedule the recurring quarterly improvement review and assign owners for cadence management.
• Create the shared channel (Teams/Slack) with named access and post initial onboarding documentation.
• Publish the triage workflow, SLA definitions, and backlog template into the channel.
• Open tickets for the agreed first-90-day initiatives and assign owners and target dates.
• Validate measured reliability improvements against agreed acceptance criteria and secure sign-off or identify gaps for remediation.
• Confirm integration performance with SCADA/DMS and identify any telemetry or event reconciliation issues requiring action.
• Produce a clear list of remaining deltas, owners, and timelines to close them.
• Produce final Outcomes Report with SAIDI/SAIFI charts, event timelines, and integration logs; circulate to stakeholders.
• Create remediation tickets for any acceptance gaps with owners and target dates.
• Schedule a short follow-up verification meeting after remediation completion (date TBD).
• Brief Recap of Deployment Scope
• Capture a prioritized set of technical and field lessons with clear owners and timelines.
• Update commissioning and installation checklists to eliminate repeat issues on future sites.
• Feed high-impact product issues into the vendor backlog and agree on target delivery windows.
• Field Installation Variances
• Current State (one-sentence)
• Triage Workflow & SLAs
• Regulatory Submission Package
• Monitoring Dashboards & KPIs
• Runbook & Playbook Walkthrough
• Backlog Template & Prioritization Criteria
• Consequence Summary
• Benefit Realization & ROI
• Protection Coordination & Settings Lessons
• Alarm Thresholds, Ticketing & Escalations
• Measured Outcomes — Reliability Metrics
• Communications & Telemetry Findings
• Approval & Sign-Off Items
• Quarterly Review Cadence
• First 90-Day Focus Areas
• Integration Performance — SCADA/DMS & Comms
• Training & Access Provisioning
• Commissioning Checklist Updates
• Reporting Cadence
• Proof Points & Root-Cause Walkthroughs
• Product/Process Backlog & Prioritization
• Future State Confirmation
• Next Steps & Owner Alignment