Orange Button Data Export
Every project in Load Factor exports as a structured JSON intelligence packet - aligned with the U.S. Department of Energy Orange Button solar data taxonomy.
What Is the Orange Button Standard?
Orange Button is an open data standard funded by the U.S. Department of Energy and managed by the SunSpec Alliance. It creates a uniform taxonomy for collecting, managing, and exchanging solar energy data across the industry value chain - from project origination through decommissioning.
The standard was developed through DOE's Solar Bankability Data to Advance Transactions and Access program (2016) with a target of adoption by stakeholders representing at least 60% of the U.S. solar industry.
In practice, Orange Button means that a project file from one system can be read by another without manual reformatting. Banks, investors, developers, and asset managers can exchange project data in a structured, machine-readable format.
How Load Factor Extends Orange Button
Load Factor exports a structured JSON packet for every project that follows the Orange Button data model and extends it with developer intelligence, evidence chains, and decision reasoning that the base standard does not cover.
The export is available on any project detail page - click Export to download the full intelligence packet as a JSON file.
Project
Queue number, project name, ISO, application status, fuel type, summer/winter capacity, study cycle, study phase, service type, in-service date.
Location
State, county, point of interconnection, transmission owner, latitude/longitude with coordinate source, confidence level, and accuracy classification.
Entities
Interconnection customer (SPV name), identified developer with confidence level, and owner - each tagged with their role in the project structure.
Evidence Summary
Total evidence count, resolution status, the kinds of source behind the attribution, and up to 25 individual evidence items with source URL, extracted name, and collection date.
Documents
Proof documents linked to evidence records - screenshots, filing PDFs, extracted pages. Each tagged with document type, filename, and capture date.
Load Factor Extensions
Decision reasoning: why we identified this developer, corroboration count, conflict count, ownership breakdown, and the full resolution narrative.
Sample Export: MISO J1410 - High Noon Solar (300 MW)
This is a solar project in Dane County, Wisconsin where two sources agree on the developer, with 109 evidence records from 7 independent kinds of source. The sample is trimmed: in your export, each item names its source and links to the record.
// Load Factor Orange Button Export - Project J1410 { "PacketMetadata": { "Standard": "Orange Button Style", "ProfileName": "Load Factor Project Intelligence Packet", "ProfileVersion": "0.1.0", "GeneratedAt": "2026-05-02T12:00:00Z", "ProjectNumber": "J1410" }, "Project": { "ProjectNumber": "J1410", "ProjectName": "High Noon Energy", "ISO": "MISO", "ApplicationStatus": "Active", "FuelType": "Solar", "SummerCapacity": { "Value": 300, "Unit": "MW" }, "Queue": { "QueueDate": "2019-04-29", "StudyPhase": "Definitive Planning Phase" } }, "Location": { "StateProvince": "WI", "County": "Dane County", "Latitude": { "Value": 43.0731, "Unit": "Degree", "CoordinateConfidence": "project_site" }, "Longitude": { "Value": -89.4012, "Unit": "Degree" } }, "Entities": [ { "EntityName": "High Noon Solar", "EntityRole": "InterconnectionCustomer" }, { "EntityName": "High Noon Solar", "EntityRole": "Developer", "Confidence": "confirmed_direct" } ], "EvidenceSummary": { "EvidenceCount": 109, "ResolutionStatus": "confirmed", "Sources": [ // the 7 kinds of source behind the attribution, named in your export ], "EvidenceItems": [ { "SourceType": "…", "DocumentTitle": "…", "ExtractedName": "High Noon Solar", "ExtractedRole": "Developer" }, // ... more evidence items (up to 25 in all), each with its source and link ] }, "LoadFactorExtensions": { "Reasoning": { "Summary": "Two sources agree. Two or more independent official records name this developer." }, "CorroborationCount": 7, "ConflictCount": 0 } }
More Examples
MISO J947 - Grant County Solar (200 MW, 73 Evidence Records)
A solar project in Grant County, Wisconsin where two sources agree on the developer, with evidence from 9 kinds of source. This project shows the depth of cross-referencing: federal, state and grid-operator records all converge on the same developer.
MISO J3144 - EDP Renewable (150 MW, 69 Evidence Records)
Solar project in Putnam County, Indiana. The interconnection customer field was empty in the original queue filing, but Load Factor identified EDP Renewable as the developer from 69 evidence records across independent public sources.
Who Uses Standardized Exports?
Investors & Lenders
Feed the JSON directly into your due diligence systems. No manual data entry from PDFs.
Asset Managers
Import project intelligence into your portfolio tracking tools. Machine-readable from day one.
Data Teams
Parse structured JSON into your data warehouse. Every field is typed, every source is cited.
Advisors
Export client-ready intelligence packets. The evidence chain and reasoning are built into the file.
Why Standardized Export Matters
Most energy data platforms give you a CSV download or a PDF report. The data is flat - you lose the relationships between evidence records, the confidence scoring, the reasoning chain, and the source citations.
Load Factor's Orange Button export preserves the full structure: which sources identified the developer, how many independent records corroborate the attribution, and whether any sources conflict. This is the difference between a data dump and an intelligence packet.
The export format is JSON - universally parseable, no proprietary readers needed. Hand it to your data team, import it into your asset management system, or attach it to an investment memo. The evidence chain travels with the data.