Dispatch events, strike prices, and the miners affected when Foreman curtails or restores power.
Part of the Foreman Intelligence Data Dictionary. Model: customer_access. Generated from the live Looker model on 2026-09-04.
Contents
Explores in this group
Dispatch Data dispatch_history
Looker description: Historical dispatch information
One row per dispatch, which is a curtailment or restore instruction Foreman executed: when it was created, when it started and ended, the power target it aimed for, how the load was ramped, which miners it applied to, why it happened, and where the instruction came from. This is the audit trail for curtailment.
| Grain | One row per dispatch |
| Time field | Start Date and End Date (5 minute precision), plus Created Date |
| Best for |
|
Example questions
- How many hours were we curtailed last month, and for what reasons?
- What target draw did each dispatch set, and how long did it last?
- Which dispatches came from the grid operator versus a manual request?
Views in this explore: Dispatch History
Strike Price Data strike_price_history
Looker description: Historical strike price information
Foreman curtails when the price of power crosses a strike price. This explore records, every 5 minutes, the strike price in effect per client, miner type, and power mode, and joins the locational marginal price (LMP) at the same time, the client's curtailment configuration, and miner telemetry. It lets you see how close power prices came to your strike prices and what the fleet was doing at the time.
| Grain | One row per client, miner type, and power mode per 5 minutes |
| Time field | Timestamp (5m) |
| Best for |
|
Example questions
- How often did the LMP exceed our strike price last week?
- What strike price applied to each miner type and power mode yesterday?
- How many minutes per day were prices above the high strike price?
Views in this explore: Client Data (Historical), Client Power Cost, Coin Hash Price, LMPs, Miner Data, Strike Price History
Dispatched Miners dispatch_miners
Looker description: Historical dispatch and miner data
Dispatches joined to the miners they affected. Each row pairs a dispatch's 5 minute target draw with the telemetry of a miner during that same window, so you can measure how the fleet actually responded to a curtailment: power before, during, and after, hash rate lost, and revenue impact.
| Grain | One row per miner per 5 minutes during a dispatch |
| Time field | Timestamp (5m) |
| Best for |
|
Example questions
- How far below the target draw did we get during yesterday's dispatch, minute by minute?
- How much hash rate did each site give up per dispatch last month?
- Which miners were still drawing full power 10 minutes into a curtailment?
Views in this explore: Client Power Cost, Coin Hash Price, Dispatches Total (Historical), Firmware Error Codes, Miner Data, Miner Details (Current)
Fields by view
Each explore is built from one or more views. A view is a set of related fields, and the tables below list every visible field in each view this article owns. Dimensions are attributes you can group and filter by. Measures are aggregates that add up, average, or count across the rows you select.
Dispatch History
One row per dispatch, which is a curtailment or restore instruction Foreman executed. It records the timing, the power target and how the load was ramped, which miners were included, why it happened, and where the instruction came from.
Used by: Dispatch Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Created Date | Date / time (Time, Date, Week, Month) | When the dispatch was created in Foreman. |
| End Date | Date / time (Time, 5 minute, Date, Week, Month) | When the dispatch ended or is scheduled to end, to 5 minute precision. |
| Start Date | Date / time (Time, 5 minute, Date, Week, Month) | When the dispatch took effect, to 5 minute precision. |
| Was Cancelled | Number | 1 if the dispatch was cancelled before it completed, 0 otherwise. |
| Client | ||
| Client ID | Number | Numeric ID of the client the dispatch applied to. |
| Client Name | Text | Name of that client. |
| Control Details | ||
| Buffer Draw | Number | Safety margin kept below the target draw so brief spikes do not breach it, in Buffer Units. |
| Buffer Units | Text | Unit for Buffer Draw, for example kW or MW. |
| Load When Dispatched | Number | The site's power draw at the moment the dispatch was issued, in Load When Dispatched Units. |
| Load When Dispatched Units | Text | Unit for Load When Dispatched. |
| Miners Filter | Text | The filter that selected which miners the dispatch applied to, for example by tag, type, or site map group. Blank means all miners. |
| Ramp Down Interval | Number | Seconds between steps when ramping load down. |
| Ramp Up Interval | Number | Seconds between steps when ramping load back up. |
| Target Draw | Number | The power level the dispatch aimed to bring the site to, in Target Units. |
| Target Draw (MW) | Number | Target Draw converted to megawatts. |
| Target Draw (kW) | Number | Target Draw converted to kilowatts. |
| Target Units | Text | Unit for Target Draw. |
| Event Details | ||
| Curtailment Reason | Text | Why the dispatch happened, for example a strike price being crossed, a grid operator request, or a manual action. |
| External Event ID | Text | Identifier from the external system that triggered the dispatch, such as a grid operator or demand response program event. |
| Extra Data | Text | Raw JSON with any additional details the dispatch carried. |
| Source | Text | Where the dispatch originated, for example a Foreman user, the strike price automation, or an external signal. |
| Type | Text | The kind of dispatch, such as a curtailment or a restore. |
Strike Price History
Every 5 minutes, the strike price in effect for each combination of client, miner type, and power mode. A strike price is the power price above which Foreman curtails; setting different prices per miner type and power mode lets efficient miners keep running longer than inefficient ones.
Used by: Strike Price Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Client ID | Number | Numeric ID of the client. |
| Client Name | Text | Name of the client. |
| Miner Type | Text | Miner model the strike price applies to. |
| Power Mode | Text | Power mode the strike price applies to, for example sleeping for a full shutdown or a low power mode for a partial curtailment. |
| Price | Number | The strike price, in dollars per megawatt-hour. |
| Primary Key | Text | Internal unique key for the row. Not useful for analysis. |
| Strike Type | Text | How the strike price was set. manual-miner-type means a price set by hand per miner type. |
| Timestamp (5m) | 5 minute timestamp | The 5 minute mark the price applies to. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Miner Count of Type | Count (distinct) | Number of distinct miners of the given type. |
| Strike Price Average | Average | Average strike price across the selected rows. |
| Strike Price Sum | Sum | Sum of strike prices across the selected rows. Mostly useful for weighted calculations. |
Dispatches Total (Historical)
The combined target draw of all dispatches active for a client in each 5 minute window. Joined to miner telemetry in the Dispatched Miners explore so actual draw can be compared with the target.
Used by: Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| ID | Text | Internal key for the dispatch window. |
| Target Draw (MW) | Number | Combined target draw for the window, in megawatts. |
| Target Draw (kW) | Number | Combined target draw for the window, in kilowatts. |
| Timestamp (5m) | 5 minute timestamp | The 5 minute window. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Total Target Draw (MW) | Sum | Sum of Target Draw (MW) across distinct dispatch windows. |
| Total Target Draw (kW) | Sum | Sum of Target Draw (kW) across distinct dispatch windows. |
Shared views documented elsewhere
These views are joined into explores in this group but are documented in another article so the definitions live in one place.
- Client Data (Historical) (used by Strike Price Data)
- Client Power Cost (used by Strike Price Data, Dispatched Miners)
- Coin Hash Price (used by Strike Price Data, Dispatched Miners)
- Firmware Error Codes (used by Dispatched Miners)
- LMPs (used by Strike Price Data)
- Miner Data (used by Strike Price Data, Dispatched Miners)
- Miner Details (Current) (used by Dispatched Miners)
Comments
0 comments
Please sign in to leave a comment.