Grid-Integrated Charging
Long-cycle programs where regulation, capital, and grid reliability define the pace.
Inside this journey
-
Pre-Discovery
Align operational, utility, and fleet stakeholders on goals, constraints, and decision roles before technical analysis.
-
Stakeholder Alignment
Confirm decision roles, timelines, utility and fleet contacts, and what ‘good’ looks like for each stakeholder before technical work begins.
Alignment Questions
Quick hello: What's brought you to this conversation today?
- Tell us in one sentence what pushed you to explore grid-integrated charging right now.
- How long have you been tracking elevated demand charges or responding to a DR solicitation?
- Who first noticed the issue (role or team) and what happened when they did?
- On a practical timeline, how urgently do you feel this needs to be resolved?
- When you think about this problem, what emotion comes up first (e.g., anxiety, frustration, opportunity)?
Who's steering the ship (and who needs convincing)?
- If this project stalls, whose day-to-day job will feel the biggest impact?
- Which of these stakeholder roles are involved in the decision (select all that apply)?
- Who will have final sign-off on commercial terms or capital spend?
- Which stakeholder(s) are most likely to push back on bidirectional cycling due to battery warranty or degradation concerns?
- Please provide the primary project contact (name, role, email) for day-to-day coordination.
If we keep doing what we’re doing, what breaks next?
- Describe the worst recent incident that came from unmanaged charging (impact, date, consequence).
- By approximately what percentage have your peak demand costs grown since EV charging began at scale?
- Do you currently have an estimate for a utility service upgrade or transformer replacement if load growth continues unchecked?
- How often have you received warnings or constraints from the utility about feeder/transformer capacity?
- What would happen operationally if you had to defer charging for 1–3 hours during a peak without alternative capacity?
What would success actually feel and look like here?
- If this project exceeded expectations, what unexpected wins would you celebrate six months after deployment?
- Which single outcome is most important for you to achieve with a grid-integrated charging platform?
- What specific, measurable target would represent success (e.g., % demand reduction or $ DR revenue per year)?
- What daily or monthly battery cycling limits would you consider acceptable for V2G participation?
- Who on your team will be responsible for verifying that the project met the success metrics?
Show me what’s actually plugged in and available today
- If some chargers or vehicles can’t integrate with our stack, how constrained would that leave your operations?
- Please list charger makes/models on site and approximate counts (e.g., 20x VendorA OCPP 1.6).
- Which charging and EV protocols are present on site (select all that apply)?
- Do your vehicles officially support bidirectional charging today?
- Which of these best describes your meter and site topology?
- What historical electrical load data is available to share (format and granularity)?
- Who manages interconnection and meter ownership (customer, landlord, utility, third-party)?
How real is the DR and revenue opportunity for your team?
- If DR revenue disappeared tomorrow, would the business case still stand — why or why not?
- Are you currently enrolled in any utility DR / grid services or time-of-use programs?
- What annual DR revenue would you need to justify this investment?
- Do you have records of past DR dispatch frequency, duration, and payments?
- Who will own program enrollment and incentive paperwork (internal team or third-party)?
- Which modeling approach do you prefer for revenue forecasts?
What keeps you awake at night about moving forward?
- Which single scenario would make you pause the project (warranty claim, incentive change, failed interconnection, operational disruption)?
- Which of these risk areas concern you most right now (select all that apply)?
- Have you discussed V2G impacts with vehicle OEMs or maintenance teams regarding warranty and lifecycle?
- Have you performed or requested a thermal/aging model to quantify battery degradation under projected cycling?
- What specific mitigation (insurance, caps, guaranteed performance, fallback modes) would make you comfortable proceeding?
If we agreed to move forward today, what would success look like at each milestone?
- If we set a go-date now, what's the realistic window from start to first DR revenue for your team?
- Which internal approvals must clear before any field work begins (select all that apply)?
- Who on your side will own integrations (meter data feeds, DERMS, fleet management) during deployment?
- What meeting cadence and decision checkpoints do you prefer during discovery and deployment?
- What would you need from us next week to keep momentum (data requests, executive briefing, pilot scope)?
How will we know we've won — your acceptance and verification needs
- If I handed you an acceptance checklist today, what items would absolutely have to be checked before you sign off?
- Select the acceptance criteria that must be satisfied (select all that apply).
- What verification timeframe do you require to declare success after commissioning?
- Do you require third-party M&V or are internal analytics sufficient?
- Who will be the final signatory on the acceptance certificate?
-
Current State Mapping
Document existing charger fleet, site electrical capacity, meter topology, historical load profiles, and failure modes that drive cost and reliability risk.
Current State
Start Here — a quick snapshot of this site
- Give a concise description of this site (site name, address or feeder area, facility type such as depot/garage/yard, and any immediate context we should know).
- How many total parking stalls and how many are currently used for EV charging?
- Tell us about the fleet that charges here (approx. number of vehicles, vehicle classes, and notable powertrain types).
- Which roles are directly responsible for day-to-day charging operations at this site?
- Has the size or usage pattern of the fleet changed in the last 12 months? If yes, briefly describe what changed and why.
What’s Actually Happening at Peak?
- When you look at your electric bill or meter data, how often do you see a single EV‑related event push your site to a new monthly demand peak?
- How much higher is your typical monthly demand charge spend today compared with before significant EV charging began (estimate % or $)?
- What time(s) of day do your highest 15‑ or 30‑minute demand intervals tend to occur? Please list typical hours and any days of the week that matter.
- Describe a recent incident when charging behavior created a costly peak or service disruption — what happened, and what was the operational impact?
- Have you tracked whether peaks are caused by clustered vehicle arrivals, simultaneous plug‑ins, charger faults, or something else?
Could Your Electrical System Survive Scaling to 10x?
- If you added the next tranche of chargers (your planned growth), what is the most realistic single technical barrier that would force a utility service upgrade?
- What is your site’s service entrance size and main breaker rating (or closest estimate)?
- How many separate revenue meters or meter points serve the charging area (single meter, submetered stalls, per building, etc.)?
- Do you have a recent electrical one‑line diagram and transformer/spec data available for review?
- Are there other on‑site distributed energy resources (solar, batteries, CHP) or large flexible loads that interact with the chargers today?
Who Pays the Bills—and Who Panics When They Spike?
- If demand charges rose by 30–50% next month because of EV charging, who in your organization would feel the operational pressure most acutely?
- Which utility rate schedule currently applies to the charging meter(s)? (If you don’t know, select 'Unsure'.)
- What is the cadence and granularity of the billing meter data you can access (for example, 15‑minute AMI, hourly, monthly only)?
- Roughly how much do demand charges contribute to your average monthly bill for the charging meter(s)?
- Has your site been approached for or participated in any utility demand response (DR) or capacity programs in the last 24 months? If yes, which and what was the outcome?
Where Do Things Break—and How Bad Is It When They Do?
- When charging reliability fails, is the most severe consequence operational (missed routes), financial (penalties/bills), or reputational (public service impact)?
- Which failure modes occur most often at this site (select all that apply)?
- How frequently do these failures occur and what’s a typical time‑to‑repair or mitigation?
- Do you have formal uptime or response SLAs for chargers and charging services? If yes, what are the targets?
- When a charger or meter fails, what sequence of teams or vendors get involved? (i.e., in‑house tech → third‑party vendor → utility → OEM)
What Would You Be Willing to Trade for Reliability or Revenue?
- If enabling vehicle‑to‑grid or deeper dispatching could materially reduce your demand charges, what operational constraint would you find unacceptable to change?
- What minimum state‑of‑charge (SOC) must be guaranteed at scheduled departure for routed vehicles (pick a single typical requirement)?
- How many vehicles must be reserved from any dispatch or export event to guarantee operations on an average day?
- What level of battery cycling/throughput do you consider acceptable per vehicle per year from a warranty/degradation perspective?
- Would you prefer a solution that prioritizes guaranteed SOC by time, revenue maximization, or a defined hybrid policy (explain your preference briefly)?
Data & Integration Reality Check — are we ready to connect?
- If we asked your team to provide live meter and charger telemetry for a 30‑day test window, how ready would you be to share it?
- What communications protocols and systems support your chargers/meters today (select all that apply)?
- Which fleet management, telematics, or energy platforms must we integrate with for scheduling or driver assignments?
- Do you have IT/security or vendor onboarding requirements (certs, pen tests, VPN) that could slow integration? If yes, note the top blockers.
- Are there upcoming firmware updates or vehicle OEM firmware changes planned in the next 6 months that we should know about?
If This Fails, What’s the Worst That Happens — and What’s an Acceptable Next Step?
- What is the single worst operational or financial outcome you fear if charging remains unmanaged over the next 12–24 months?
- What is your target timeframe to decide on a managed/grid‑integrated charging approach (choose the closest option)?
- Who ultimately signs off on capex or program enrollment for this site, and who are the internal blockers we should engage early?
- What would you consider a successful small‑scale pilot at this site (define 2–3 measurable outcomes we must achieve)?
- If we proposed a next step (metering study, short pilot, or financial model), which of these would you prefer to start with?
-
-
Outcome Discovery
Define target demand charge reduction, acceptable battery cycling limits, required DR revenue, and measurable success signals.
Discovery Questions
Quick introductions — who are you and what you manage?
- What's your primary role with respect to the charging sites we're discussing?
- How many chargers and vehicles are currently in the depot(s) you manage (or oversee)? Please list counts and any notable variety (AC vs DC, power levels).
- Roughly how long have you been tracking the depot’s electricity bills and charging behavior?
- If you had to pick one top objective for engaging with a grid-integrated charging solution today, what is it?
Are you comfortable leaving obvious savings on the table?
- When your recent bills showed a 30–50% spike in demand charges, what did you first think the root cause was—and how confident are you in that diagnosis?
- How often do unexpected demand charge spikes occur today?
- Tell us about a time a high demand event caused a business impact (budget overrun, delayed ops, lost contract). What happened and how did that feel for the team?
- If a solution could reliably avoid the next two high-demand events, what would that be worth to your team this year (ballpark $ or avoided capital spend)?
How much savings would actually move the needle for you?
- If we asked you to pick a target demand charge reduction that would justify the project, what percentage reduction would you need to see?
- Over what timeframe would you expect to realize those demand-charge savings to consider the project successful?
- Would you accept a combination of demand-charge reduction plus DR revenue as your success threshold, or do you require demand-charge savings alone?
- What internal stakeholders need to sign off on the savings assumptions (finance, procurement, operations, fleet mgmt, utilities)? Please name roles or teams.
What would you be willing to trade to unlock grid services?
- How concerned are you that bidirectional cycling (V2G) could accelerate battery degradation or affect warranties?
- What is the maximum average depth-of-discharge (DoD) or cycle count per vehicle per week that you would view as acceptable?
- Do you have existing vehicle warranty or OEM cycle limits we must honor? If yes, please specify how these constraints are tracked and enforced.
- Would you prefer DR participation protocols that prioritize battery health over revenue, or revenue-first with battery guardrails?
- Who on your team is authorized to set or change battery cycling policies (title/role) and how would you like those policies communicated to us?
How dependable does DR revenue need to be for you to count it in forecasts?
- If DR revenue represents a meaningful portion of the project ROI, what minimum annual DR revenue would make the project a clear yes?
- How tolerant are you of revenue variability from program rule changes, dispatch frequency, or seasonal shifts?
- Have you experienced a utility program rule change that materially reduced expected revenue in the past? Tell us what happened and how you coped.
- Would you prefer a contractual guarantee, shared-risk model, or best-effort forecasting for DR revenue?
Which signals should we measure so you can trust the outcome?
- Beyond $ savings and DR payouts, which of the following metrics matter most to you for acceptance (select up to 5)?
- What reporting cadence do you need to feel confident (real-time dashboard, daily digest, weekly summary, monthly verified report)?
- How accurate do demand-reduction measurements need to be for you to sign off (e.g., +/- 1%, +/- 5%, +/- 10%)?
- Which stakeholders require independent verification of results (utility, corporate finance, OEMs, internal audit)? Please name roles.
What operational constraints could stop this from working?
- How is your site metered today (main service meter only, submetered for chargers, per-charger metering, utility AMI access)?
- Tell us about any recent or upcoming utility interconnection or service upgrade projects that could affect timelines.
- Which software or platforms must we integrate with for the pilot to be operational (fleet management, telematics, DERMS, building EMS, payment systems)? List names and access status.
- Who on your side will own day-to-day operations and who is the escalation contact for outages or performance misses? Please provide roles, not necessarily names.
- What timeline constraints are non-negotiable (contract renewal, grant milestones, seasonal fleet changes)?
If we delivered measurable demand reduction and DR revenue, what would that unlock for you?
- How would verified demand-charge savings change your near-term capital plans (defer transformer upgrade, expand fleet, reinvest savings)?
- Would demonstrating this success at one site lead to rollout across other depots or properties? If yes, what would scale look like (number of sites, timeline)?
- What would make you confident enough to sign an initial pilot agreement today? List the top three decision criteria in order.
- Who else should be in the next conversation to move this forward (roles and preferred level of involvement)?
Commitments and quick wins — what should we try first?
- If we proposed a 3-month pilot, which of the following outcome requirements would make it a clear success for you?
- What are one or two low-effort, high-impact tests we can run quickly to prove the concept on your site?
- How quickly could your team provide the baseline data we need (historical kW load profiles, meter data, tariff details)?
- Finally, what's the best way for us to present a modeled outcome that your finance and ops teams will trust (detailed runbook, conservative forecast, sensitivity scenarios)?
-
Solution Experience
Validate how our grid-integrated charging approach achieves the customer’s targets using their load profile, utility rate, and realistic dispatch scenarios.
Experience Meetings
- Solution Experience Readiness — Current State Confirmation
- Consequence Quantification Workshop
- Modeling & Solution Experience — Proof in Your Context
- Sensitivity & Risk Stress Test
- Validation & Mutual Confirmation — 'Is this what you meant?'
Issues & Enhancements
- Set explicit decision thresholds for proceeding to Solution Scope or requiring further experiments.
- Deliver the simulation workbook and a clear list of acceptance checks.
- Recap: Current State, Consequence, and Future State Target
- Prove whether the grid-integrated approach meets the agreed targets using customer data in at least one realistic scenario.
- Surface and document all assumptions, and get explicit customer validation for each key assumption.
- Identify any mismatches and agree immediate corrective modeling or operational experiments.
- Seller: Share the simulation workbook and slide summary with annotated assumptions and outputs within 24–48 hours.
- Customer: Mark any incorrect assumptions in the workbook and return comments.
- Seller: If targets are unmet, prepare two short alternative scenarios or mitigation experiments for the sensitivity session.
- Top Assumptions & Variable Ranges
- Produce a risk-adjusted P&L range and clearly identify worst-case exposures.
- Agree on mitigation measures and the commercial levers available to protect both parties.
- Introductions & Objectives
- Seller: Deliver a sensitivity report with recommended mitigation clauses and recommended operations limits.
- Customer: Provide acceptable worst-case threshold values and confirm whether mitigation measures are operationally acceptable.
- Commercial/Legal: Draft preliminary contract language for agreed guardrails and performance commitments.
- One-sentence Recap: Current State, Consequence, Future State
- Obtain explicit customer sign-off on the Solution Experience validation checklist.
- Confirm commitment to proceed to Solution Scope (or list required pre-conditions if not proceeding).
- Identify owners and timeline for any outstanding items to be resolved before Solution Scope kickoff.
- Customer: Sign and return the Solution Experience validation memo indicating accepted criteria.
- Seller: Create and distribute Solution Scope kickoff packet with timeline, owners, and required inputs.
- Both Parties: Assign and acknowledge owners for any open items with agreed deadlines.
- Produce a single, explicit current-state sentence agreed by customer and seller.
- List and assign responsibility for any missing or poor-quality input data required for modeling.
- Agree which consequence metrics (cost lines and KPIs) will be used to judge success.
- Schedule the Modeling & Solution Experience session with required attendees and data deliverables.
- Customer: Upload missing interval meter, charger telemetry, and fleet schedule files to shared workspace.
- Seller: Draft the one-sentence current state and circulate for approval within 24 hours.
- Seller: Prepare and validate modeling environment using supplied data and confirm scenario list for the next session.
- Baseline Billing & Demand Profile
- Agree on quantified baseline cost and risk figures that make the problem urgent.
- Set explicit numeric targets for demand charge reduction, DR revenue, and acceptable battery cycling.
- Document the assumptions to be used in the upcoming modeling session.
- Seller: Deliver a one-page baseline cost summary and a table of upgrade probability and expected cost scenarios.
- Customer: Confirm program enrollment history and any contractual constraints affecting DR participation.
- Seller: Finalize the target metrics to be used as pass/fail criteria in the Solution Experience.
- Sensitivity Runs: Best/Likely/Worst
- Baseline (Unmanaged) Simulation Results
- Proof Highlights
- One-sentence Current State
- Upgrade & Reliability Costing
- Data Review & Gaps
- Battery Degradation & Warranty Scenarios
- Validation Checklist Walkthrough
- Primary Grid-integrated Scenario Walkthrough
- DR Program Eligibility & Revenue Assumptions
- Alternate Scenarios: High-peak & V2G Export
- Decision & Next Steps
- Mitigations & Contractual Guardrails
- Operational Constraints & Battery Impact
- Consequence Metrics Needed
- Capture Open Items & Owners
- Pre-experience Checklist & Next Steps
- Tie Results Back to Problems
- Agree Success Targets
- Decision Thresholds & Go/No-go Criteria
- Force Validation Checkpoints
- Immediate Next Steps if Targets Not Met
-
Solution Scope
Define hardware compatibility, software integrations, enrollment tasks, revenue/cost modeling assumptions, timeline, and verification criteria.
Scope Configuration
- Install bidirectional chargers and power hardware
- Install utility-grade revenue meter and telemetry
- Submit utility interconnection application
- Integrate charging platform with utility DERMS
- Integrate charging platform with fleet management system
- Configure demand response automation and dispatch rules
- Enable V2G export controls and safety interlocks
- Deploy dynamic load management and phase balancing
- Integrate on-site energy storage and control
- Commission chargers and perform demand response testing
- Configure charger-to-vehicle BMS compatibility profiles
- Implement site cybersecurity and OT network segmentation
- Configure utility rate optimization and billing export
- Train onsite technicians on operations and maintenance
Scope Questions
Install bidirectional chargers and power hardware
- How many charging ports/connectors do you plan to equip with bidirectional capability?
- Do you currently have chargers on site that need retrofitting or are these new installs?
- List existing charger brands/models (if any) and their firmware version(s).
- What maximum per-connector and per-site power ratings are required (kW)?
- Are there preferred charger vendors or procurement constraints (vendor list or approved equipment)?
- Do you require AC-only bidirectional capability, DC fast V2G, or both?
Install utility-grade revenue meter and telemetry
- Will the site require a utility-approved revenue meter for billing/export verification?
- What type of interval data granularity is required by the utility or your billing process?
- Which telemetry protocols does the meter or telemetry system need to support?
- Where will the meter be installed (main service, submeter at charger array, per-connector)?
- Do you require direct data export to your billing/utility portal (format e.g., CSV, XML, API)?
- Are there physical site constraints for meter installation (metering room access, CT size limits, remote SES)?
Submit utility interconnection application
- Which utility and tariff / rate schedule governs this site (name and specific tariff)?
- Does the utility allow export or require net export limits for V2G?
- What level of study does the utility typically require (screening only, interconnection study, protection study)?
- Who will prepare and submit the interconnection package (customer, vendor, third-party engineer)?
- Are single-line diagrams, one-line, and site electrical drawings available for submission?
- What is the target timeline for interconnection approval (choose estimate)?
Integrate charging platform with utility DERMS
- Which DERMS/vendor does the utility operate (name all that apply)?
- Which integration protocols are required or preferred for DERMS (OpenADR, MQTT, proprietary API)?
- Does the utility require any certification, testing, or sandbox access prior to production integration?
- Are API credentials, IP allowlists, or security artifacts already available from the utility?
- What data points and control signals must be exchanged (e.g., aggregate kW, nodal setpoints, telemetry intervals)?
- Do you require real-time (sub-minute) telemetry vs. 5–15 minute intervals for DERMS use cases?
Integrate charging platform with fleet management system
- Which fleet management system(s) or telematics providers must be integrated (list names)?
- What vehicle and driver data are required for scheduling and dispatch (SOC, location, next-dispatch time)?
- Is two-way command/control required from FMS to chargers (e.g., pause charging, set charge priority)?
- Are API credentials, data schemas, and test accounts available for the FMS?
- Do you need mapping of vehicle IDs to connector IDs and a governance process for mismatches?
- Are there data privacy or PII constraints governing driver or vehicle telemetry sharing?
Configure demand response automation and dispatch rules
- Which DR programs or signals will the site participate in (utility DSO program, ISO/RTO, commercial aggregator)?
- What is the target demand reduction or export capacity the site should be able to deliver (kW or % of peak)?
- What constraints should the dispatch automation enforce (minimum SOC, required readiness for next route, max cycles/day)?
- How quickly must the system respond to DR events (seconds, <1 min, 1–5 min, 5–15 min)?
- Should dispatch rules be prioritized by revenue, customer-defined critical vehicles, or battery health preservation?
- Do you require automated reporting and settlement files for DR revenue reconciliation?
Enable V2G export controls and safety interlocks
- Does the site require export to grid (V2G) or only site load shaving (no export)?
- What anti-islanding and safety certification requirements must the system meet (UL, IEEE, local code)?
- Are vehicle BMS and OEM permission for export documented for the vehicle fleet?
- Do you require hardware-level interlocks (contactors, relays) in addition to software controls?
- What maximum export power per vehicle and per site should be enforced in software policy (kW)?
- Are there insurance or warranty considerations that limit export operations (fleet OEM warranties)?
Deploy dynamic load management and phase balancing
- Do you require per-connector dynamic load control or aggregate-area control?
- Is phase-by-phase metering available or required for phase balancing?
- What is the expected maximum simultaneous draw (kW) during typical peak periods?
- Are there operational priorities for load distribution (e.g., depot-critical vehicles, fast charging bays)?
- Do you want automatic phase rebalancing hardware or software-only approach?
- Do you require logging and alarm thresholds for phase imbalance and overload events?
Integrate on-site energy storage and control
- Is on-site energy storage already installed at the site?
- If storage exists or planned, what are the nameplate energy (kWh) and power (kW) ratings?
- Which storage inverter/EMS vendor is used or planned (list vendor/model)?
- Should storage dispatch prioritize grid services revenue, site peak shaving, or vehicle charging support?
- Are anti-islanding and interconnect controls for storage coordinated with charger export controls?
- Do you need integrated forecasting (solar, load) to optimize storage dispatch with charging?
Commission chargers and perform demand response testing
- What are the acceptance criteria for commissioning (response time, % load reduction, export power)?
- Which commissioning tests are required: load modulation, DR signal response, V2G export verification, failover tests?
- Will test vehicles be available on site to validate V2G export and SOC behavior?
- What data capture and reporting must be produced at commissioning (event logs, SCADA traces, meter intervals)?
- Who will sign off on successful commissioning and what is the sign-off process?
- Are there acceptance thresholds for battery degradation or cycle counts used in commissioning acceptance?
-
Mutual Commit
Finalize commercial terms, responsibilities for utility program enrollment and interconnection, and acceptance criteria tied to savings and DR performance.
Agreement Modules
- Statement of Work (SOW)
- Master Services Agreement (MSA)
- Equipment Purchase Order / Supply Agreement
- Commercial Terms & Payment Schedule
- Performance Guarantee & Acceptance Criteria
- Utility Program Enrollment & Interconnection Responsibilities
- Enrollment Authorization & Data Access Consent
- Commissioning & Validation Acceptance Test (CAVT)
- Service Level Agreement (SLA) & Support
- Warranty & Battery Degradation Acknowledgement
- Change Order & Scope Management
- Confidentiality & Data Processing Agreement (DPA)
- Insurance, Indemnity & Liability
- Termination, Renewal & Exit Plan
- Training, Handover & Operational Runbook
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm data feeds, meter and DERMS integrations, vehicle firmware alignment, and utility approval readiness before field work starts.
Readiness Questions
Quick Check: Can We Start Field Work?
- What earliest date window would you prefer for on-site field work to begin?
- Who should our field team call or badge in with on arrival at the site? Please provide name, role, and best phone/email.
- Are there site access constraints we should know about (security escort, limited hours, PPE requirements)?
- Is any concurrent construction, electrical work, or scheduled outage planned during the expected deployment window?
Are We Accidentally Betting on Hope?
- Which parts of this deployment are we assuming will 'just work' without verification?
- Which of these integrations do you currently believe are already available and reachable for testing?
- For each integration you selected above, can you point to the concrete evidence (API docs, test endpoint URL, contact with IT) that it’s ready?
- What recent surprises in similar projects have forced last-minute rework or schedule slips?
Who Actually Owns Each Piece of This Puzzle?
- Do you have named owners for these critical items: utility interconnection, meter owner, IT/security, fleet operations, and on-site facilities?
- Please list the person and contact for the owner of: utility interconnection (company, name, phone/email).
- Who will be the day‑to‑day owner for coordinating firmware updates and commissioning tests on-site?
- If an approval or test fails, who has the authority to sign off on a corrective action and what is the escalation path?
Can We Trust the Data We'll Be Using?
- How confident are you that existing meter and charger telemetry accurately reflect baseline load and will be available for real‑time control?
- Which historical and live data feeds are available today? Select all that apply.
- For the meter data you have, what is the typical latency and retention (e.g., 15min latency / 12 months retention)?
- Have you seen data quality problems (gaps, timezone shifts, mis-labeled meters) in historical files we should plan for?
- Would you be able to provide a recent sample (CSV or API test token) for our data engineers to validate before deployment?
What If a Vehicle Vendor Changes the Rules?
- If a vehicle OEM issues a firmware update that affects bidirectional charging mid‑deployment, how comfortable are you freezing vehicle firmware to preserve commissioning results?
- How many distinct vehicle makes/models and firmware families are in the fleet at this site?
- Do you have direct contacts at the vehicle OEMs or up‑fitter who can support testing and firmware coordination if needed?
- Are there warranty or fleet policies limiting allowable depth or frequency of bidirectional cycles we must observe during commissioning?
- If vehicle firmware variability prevents a test, what temporary operational mode would you accept to preserve DR enrollment or avoid utility upgrade?
Is the Utility on Our Side — Really?
- Have we validated the utility’s current interconnection and DR program rules against our project assumptions within the last 30 days?
- Which utility program(s) and tariff(s) will this site rely on for demand response and demand charge reduction?
- What is the current status of the interconnection application and expected approval date?
- Will the utility require meter replacement, reprogramming, or a revenue-grade CT install prior to enrollment?
- Are there fees or deposits the utility charges that could impact the deployment budget or schedule?
How Will We Verify Success On Site?
- What concrete, testable acceptance criteria must we achieve during commissioning for you to consider deployment successful?
- Which of these commissioning tests do you require as formal pass/fail criteria?
- What minimum DR response latency and duration would you expect (e.g., respond within X seconds and sustain for Y minutes)?
- What are acceptable thresholds for variance between our measured savings and your meter/metered bill reconciliation?
- Who will sign final acceptance after commissioning (name, role), and what documentation do they require?
If Things Slip, What’s Our Backup Plan?
- If critical approvals or integrations delay more than two weeks, which temporary operational strategy should we default to preserve revenue or avoid upgrades?
- Do you have an operational priority list for charging vs. mission needs (e.g., emergency vehicles first, then route vehicles, then others)?
- What communications cadence and channels do you prefer for schedule slips and technical blockers (daily standup, weekly summary, Slack/email)?
- What budget or resource flex is available to accelerate stuck items (expedited interconnection review, contractor overtime, temporary meters)?
Next Small Steps & Owner Commitments
- Based on this readiness check, which three actions should we prioritize in the next 7 days to keep the schedule intact?
- Please confirm the single point of contact we should use for daily coordination and their preferred method (name, role, phone/email, preferred channel).
- Which of the following best describes overall deployment readiness today?
- When would you like a readiness re-check meeting with our team (pick one)?
-
Deployment Enablement
Coordinate installation, interconnection submissions, firmware updates, and commissioning tests with detailed scheduling and owners.
-
Validation Checklist
Execute commissioning: load modulation tests, DR signal response, V2G export validation, and battery degradation monitoring against acceptance criteria.
Validation Questions
Let’s Start With Who You Are and What You Manage
- Which role best describes your primary responsibility for EV charging at this site?
- How many vehicles and chargers do you currently operate, and how many do you expect in 12 months?
- Which charger models, EV makes, and charger vendors are currently deployed or planned at this site?
- How would you describe the primary business driver behind managing this fleet’s energy (cost containment, reliability, revenue from DR, regulatory/compliance, sustainability, other)?
- What does this responsibility feel like day‑to‑day—calm and predictable, occasionally stressful, or consistently reactive?
What Keeps You Up at Night About Scaling Charging?
- When you imagine growing from tens to hundreds of vehicles, how confident are you that your current approach won’t trigger a costly utility service upgrade?
- Have you had any recent billing surprises, transformer overload warnings, or interconnection holdbacks from the utility? Describe the most recent example.
- How often do unmanaged charging patterns cause operational friction (missed dispatch, vehicle unavailable, or schedule conflicts)?
- Who at your organization feels this issue most acutely (operations, finance, maintenance, sustainability)? Tell us how it affects them.
- How long has this been a growing concern and what triggered it (fleet growth, new rate, utility program solicitations)?
If We Could Remove One Big Risk, What Would It Unlock?
- Imagine a scenario with zero unexpected demand charges and steady DR revenue — what immediate decisions would that enable for your fleet?
- What percentage reduction in demand charges would make this project a clear win for you?
- What minimum monthly DR revenue or annual uplift do you need to justify investment (either dollar amount or % of operating expense)?
- Which operational KPIs would prove success within the first 12 months (examples: peak kW reduction, % of charging completed by dispatch time, DR event pass rate)?
- How emotionally important is predictability versus maximizing short‑term revenue? (Which matters more to stakeholders?)
What Trade‑Offs Are You Willing to Make?
- Would you accept modest additional battery cycling if it significantly reduces demand charges and avoids a service upgrade?
- What is the maximum incremental battery cycle count or degradation (%) you consider acceptable over 3 years?
- Are there vehicle manufacturer warranty terms or procurement clauses that prohibit bidirectional energy export or specific cycle depths?
- Which internal stakeholders must sign off on battery cycling or warranty trade‑offs (operations, fleet OEM, legal, procurement, finance)?
- If DR dispatch frequency increased unexpectedly, how comfortable would you be with automatic additional cycles versus manual overrides?
Who Needs to Connect to Whom — and What Data Matters?
- If a single missing data feed could block project approval, which would it be (meter interval data, utility tariffs, DERMS feed, vehicle SOC/telemetry)?
- Which external systems must we integrate with for success (select all that apply)?
- What meter and telemetry feeds do you already have access to (interval granularity: 1s/15s/1min/5min/15min/30min/60min)?
- Who will own credentials and API access for integrations, and who is the day‑to‑day technical contact?
- Are there network segmentation, firewall, or cybersecurity policies we must plan around for remote control and telemetry?
How Do You Evaluate the Money Side — Realistically?
- If our model shows net savings but DR revenue is volatile, would you prioritize guaranteed capex avoidance or short‑term revenue?
- What is the minimum annual net financial benefit (savings + DR revenue − costs) you need to greenlight a rollout?
- How do you currently value avoided utility upgrades or extended transformer life in your financial model?
- Do you require conservative 'stress test' modeling assumptions (e.g., 30% lower DR call frequency) as part of approval?
- Are incentives, grants, or rate changes tied to your decision window that we should include in the financial case?
Timing, Milestones, and What’s Non‑Negotiable
- If interconnection or utility approval stretches beyond your fleet expansion date, will you delay expansion, accept partial rollout, or cancel the project?
- What are the absolute hard dates or windows (procurement cycles, grant deadlines, rate changes) we must hit?
- How long a pilot would you require before committing to site‑wide deployment (options in weeks/months)?
- Who will coordinate on your side for installations, firmware updates, and scheduling commissioning tests?
- What timeline do you consider acceptable for end‑to‑end adoption (enrollment, hardware install, interconnection, commissioning)?
What Proof Will Make You Confident This Works?
- If the system can’t reliably respond to DR dispatch or modulate load in a repeatable way, would you accept it as 'working'?
- Which commissioning tests are non‑negotiable for acceptance (choose all that apply)?
- For each selected test, what pass/fail criteria or thresholds must be met (e.g., % of events successfully executed, allowable response time)?
- Who on your side will witness or certify commissioning and who signs off on acceptance?
- If a single commissioning metric fails, what remediation path would you accept (fix & retest, partial acceptance with penalties, project pause)?
Decision Rhythm — Who Signs Off and How Do We Keep Momentum?
- Even with a clear savings model, who beyond you has veto power and why might they say no?
- Please list the decision roles, their expected approval artifacts, and typical review cycles (legal, procurement, finance, operations).
- What contractual or procurement constraints should we be aware of (preferred vendor clauses, insurance, SLAs, indemnities)?
- Would a defined pilot with commercial guardrails (scope, duration, acceptance criteria) make approvals easier?
- What would be a clear, small first step you’d be willing to take after this discovery conversation?
-
-
Success
Review realized savings and DR revenue, confirm acceptance, and keep a shared channel for issues, firmware updates, and enhancement requests.
Success Reviews
- Realized Savings & DR Revenue Review — Acceptance Decision
- System Health & Issue Triage — Shared Channel Setup
- Firmware & OEM Coordination — Compatibility & Update Policy
- Enhancement Roadmap & Continuous Value Optimization
Issues & Enhancements
- Define post‑pilot measurement approach to prove the incremental value and feed results into commercial review.
- Open tickets for any unresolved incidents with agreed owners and target resolution dates.
- Publish a 30‑day stabilization schedule (daily/weekly checkpoints) and share calendar invites.
- One‑Sentence Current State (Firmware Landscape)
- Agree on a firmware change policy that minimizes operational risk and preserves DR performance.
- Define validation tests and rollback criteria that prove the system maintains the future state.
- Assign owners for update approvals and OEM liaison responsibilities.
- Publish a firmware baseline report and compatibility matrix to the shared channel.
- Create a staged rollout plan with lab and small field pilot windows and clear rollback criteria.
- Set up OEM advisory monitoring (RSS/MAU contacts) and assign a primary OEM liaison.
- Draft notification templates for fleet operators and utilities for pre‑ and post‑update communications.
- One‑Sentence Future State (Customer Business Goal)
- Agree on a prioritized enhancement backlog focused on measurable increases in savings or reliability.
- Define pilots with clear success metrics and owners to validate the future state.
- Secure commitment on roadmap timing and any incremental resourcing or funding needs.
- Log prioritized enhancement items in the shared backlog with ROI estimates and target metrics.
- Kick off the first enhancement pilot with a test plan, owner, and timeline.
- Publish a 12‑month roadmap and identify budget approvals required for each major item.
- Introductions & Meeting Objectives
- Confirm whether realized savings and DR revenue meet the contractual acceptance criteria.
- Validate the measurement methodology and data sources so financial results are auditable.
- If acceptance is conditional, capture a clear remediation plan with owners and deadlines.
- Establish regular post‑acceptance reporting cadence and owners.
- Produce and sign the formal Acceptance Certificate or Conditional Acceptance memo.
- Deliver the reconciled financial spreadsheet with raw meter exports and calculation steps.
- If remediation required, create a remediation plan with owners, milestones, and validation tests.
- Schedule recurring monthly reconciliation and a quarterly business review slot.
- One‑Sentence Current State (Operations)
- Create and agree upon a persistent shared channel and its membership.
- Assign owners and SLAs for incident response and remediation tracking.
- Clear outstanding incidents or commit to concrete remediation timelines.
- Set an intensified monitoring cadence for the post‑acceptance stabilization period.
- Provision the shared channel, invite defined stakeholders, and publish channel rules and SLA expectations.
- Document the escalation matrix with names, phone numbers, and primary/secondary contacts.
- One‑Sentence Current State
- Risk Analysis: OEM Firmware Changes Impact
- Recent Incidents & Root Causes
- Gap Analysis: Measured vs Desired Outcomes
- Controlled Rollout & Validation Protocol
- Measurement Methodology & Data Sources
- Proposed Enhancements & Expected Impact
- SLA, Escalation Paths & Response Times
- Approval & Notification Workflow
- Shared Channel Launch (Tool, Owners, Access)
- Pilot Decision & Success Metrics
- Financial Reconciliation: Actual vs Modeled
- Roadmap & Funding Alignment
- Ongoing OEM Engagement & Change Alerts
- Operational Performance: DR Event Logs
- Short‑Term Triage Plan & First‑Month Cadence
- Acceptance Criteria Walkthrough & Vote
- Next Steps for Monitoring & Reporting