Automation Use Cases

There are a variety of automation use cases enabled by the Leap universal APIs and partners have the flexibility to choose which ones to automate and when. Below is a summary of these use cases and how they apply per program type. For help in determining which use cases to start with, check out the Residential Phasing or Commercial Phasing guides.

Use Cases by Program Type

As outlined in the table below, programs fall under one of three program types based on how meters are onboarded, interval data is collected, and dispatch event performance is measured. All markets/programs within each of these program groupings are structured very similarly and therefore have the same operational and automation use cases. Additionally, most integration use cases are also the same for all three program types meaning you can have a single program-agnostic integration that scales to all current and future programs without needing to make integration updates.

Program Type Differences

• Utility Meter - Authorization Required: Utility account data sharing authorization is required in order for Leap to enroll customers and/or calculate performance
• Utility Meter - No Authorization Required: Utility account authorization is not required as performance is calculated by the program operator
• Device Program: Partners are required to upload device interval data so Leap can calculate performance

🚧

Handling utility meter vs. device Leap meters

In most cases the same integration will work for both utility meter and device programs however note the processing differences between these two types of Leap meters in the Utility Meters vs. Devices developer guide.

📘

Use Case Phasing Recommendations

Prioritizing use cases and development hours is an important consideration. Check out the recommended use case phasing guides below in order to maximize time to launch and partner grid services revenue while managing upfront development resources.

• Residential Use Case Phasing
• Commercial & Industrial Use Case Phasing

Summary of Use Cases

A summary of use cases is below. Click on each link to see the relevant developer guide with additional details, recommendations, and API endpoints.

Preparing to Launch

Onboard Meters

• For Utility Meter - Authorization Required programs:
  • Leap Connect - Embed Leap Connect URL into both customer sales/install workflows as well as existing customer install base enrollment workflows
  • Connect Reminders - Automate customer re-engagement and increase enrollment conversion rates
• For Device Programs and Utility Meter - No Authorization Required programs:
  • Opt-out auto-enrollment campaigns recommended in order to maximize grid support and partner revenue
  • Create Meters - Add meters directly to Leap platform for enrolled customers and devices

Schedule Grid Events

• Meter Inventory [Use cases A-C] - Sync meters between Leap platform and partner systems in preparation for dispatching
• Dispatch Automation - Receive dispatch event notifications (webhook push recommended) and automate control of customer devices

Post-Launch Operations

Manage Meters

• Optimize Enrollments [Use case D] - Track customer meter eligibility and partner actions in order to maximize meter enrollments and revenue
• Manage Participation - Manage meter participation over time based on seasonal requirements or customer requests

Monetize Customer Meters

• For Device Programs:
  • Interval Upload - Automate device interval data uploads via SFTP client library
• Revenue Reporting - Sync revenue and settlement data to financial reporting systems, automate customer payments (if applicable), and alert on meters with high missed revenue in order to take corrective action
• Event Performance - Track performance and alert on poor performing meters in order to take corrective action