Turbine Order Register

What it covers

One row per disclosed commitment for a gas turbine or turbine package, US first (77 rows) and every other order the same OEMs disclosed (Saudi Arabia, Taiwan, Poland, Canada and 15 more), grid, data center and peaker end uses: firm orders, slot and capacity reservations, framework agreements, letters of intent and option exercises. Each row carries buyer and ticker, OEM and ticker, project and location, units, turbine model and class, MW, configuration, end use, delivery start and end, expected COD, disclosed value, commercial terms, the source document with its date, the SEC accession where there is one, the verbatim quote that supports the row, and a confidence grade. A second table holds every change to a row after it was first recorded, with the field, the value before and after, and the document that changed it. Alternatives (reciprocating engines, fuel cells, mobile fleets) sit in their own table with the same columns. Derived tables roll the register up by OEM and quarter, by delivery year against stated OEM capacity, by ticker, and by OEM share of disclosed GW.

Cadence: Rows added within one business day of a disclosure; derived tables rebuilt on every change
Compiled from: 8-K, 10-Q and 10-K filings and exhibits on sec.gov; OEM and buyer press releases; investor presentations and earnings transcripts; state utility commission dockets; trade press only where it quotes a named party
Delivered as: Web table on this page for signed-in Institutional readers, JSON and CSV at api.open-factory.com, MCP tools get_turbine_orders, get_turbine_order_history, get_turbine_register
Updates: Continuous, every change recorded as an event
Onboarding: None needed: pay, the key is created, the register opens on this page
Support: Reply to any mail from hello@open-factory.com
Tier: Institutional; headline and counts free

Who uses it and what it decides

Investors in turbine OEMs and their suppliersHow much of a stated backlog is firm, how much is reservation, and which buyers hold the 2028 and 2029 slots.
Data center developers and IPPsWhich competitors have secured turbines for which delivery year, on what terms, and what a slot cost.
Utilities and their regulatorsWhich orders in a resource plan are contracted and which rest on a reservation that can lapse.

Methodology

What a row is

One disclosed commitment. The register records what a named party said in a document that can be opened: a filing on sec.gov, a press release on the company’s own site, a presentation or a transcript, a regulatory docket. Trade press counts only where it quotes a named party, and the quote is what goes in the row. Nothing is inferred: if a release says “multiple units” the units cell is blank, and if it says “a reservation agreement” the instrument is a reservation, not an order.

Each row carries a confidence grade. High means an SEC filing or a release from the buyer or the OEM with units or MW stated. Medium means a named party in a secondary document, or a release that leaves units or MW unstated. Low means a single trade-press report with a named source and no corroboration; low rows are kept, flagged, and watched for a confirming document.

How changes are kept

A row is never overwritten in silence. When a later document changes a field, the row takes the new value and an event is written with the date, the field, the value before, the value after, the document and its quote. A reservation converting to a firm order, a delivery year moving, a unit count rising, a value disclosed for the first time, a cancellation: each is one event. The event table is the audit trail and the history of the slot market in one.

Derived tables

Four tables are rebuilt from the register on every change, by script, and never edited by hand:

Announced by quarter, per OEM: records, GW announced, split by instrument, set beside what the OEM itself reported as signed and converted in the same quarter.
Supply by delivery year, per OEM: GW committed for each delivery year beside the OEM’s stated capacity for that year and the date it stated it.
Exposure by ticker: for every listed buyer and OEM, records, units, GW by instrument, GW for data centers, earliest and latest delivery.
OEM share by quarter: each OEM’s share of disclosed GW.

What is in preparation

An EDGAR watcher that reads each new 8-K from the tracked filers and queues a candidate event for review, and mail alerts to Institutional readers when a tracked row changes. Neither is live yet; rows are added by the desk today.

Version history

0.1 (October 2026). 127 records, 328 events, 260 sources, 40 alternatives, four derived tables. Served on this page, by API and by MCP.

Questions

What is a record and what is an event?

A record is one disclosed commitment, keyed by the date, the OEM and the buyer. An event is one later change to that record: a status moving from reserved to firm, a delivery year slipping, a unit count rising, a value disclosed for the first time. The record shows the current state; the events show how it got there, each with the document that said so.

Why do some rows have no MW?

Because the party that disclosed the order gave a unit count or a model and nothing more. The register never estimates MW; a blank cell is a blank cell. The derived tables count those rows separately as records without MW.

How current is it?

The as_of date on every table is the date of the newest source in it. A disclosure found in a filing or release is added within one business day. Alerts by mail on changes to a tracked row are in preparation and not yet live.

What is free?

This page: the headline, the counts, the column list and the method. The rows, their history, the sources table, the alternatives and the derived tables are Institutional, $1,500 a month per firm, and open on this page the moment a firm is signed in.

Articles built on this model

None published yet.The first piece built on this model appears here with its date and the figure it leads with.