UnitCapacityDTO

UnitCapacityDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name Type Description
maximumHourlyHeatInputCapacity number The design heat input capacity (in mmBtu/hr) for the unit or the highest hourly heat input rate observed in the past five years, whichever is greater.
beginDate string Date on which a relationship or an activity began.
endDate string Date on which a relationship or an activity ended. This value will be null for active records.
id string Identity key for UNIT_CAPACITY table.
unitId number Identity key for UNIT table.
commercialOperationDate string The date a unit began, or will begin to generate electricity for sale, including the sale of test generation. It is the first date that a unit serves a generator and produces electricity when connecte
date string Date on which activity occurred.
boilerTurbineBeginDate string Date on which monitoring began for a boiler or turbine unit.
boilerTurbineEndDate string Date on which monitoring ended for a boiler or turbine unit.
userId string The user name of the person or process that created the record if the Update Date is empty. Otherwise this is the user name of the person or process that made the last update.
addDate string Date the record was created.
updateDate string Date of the last record update.
active boolean Flag for active monitor location record
boilerTurbineType string
View JSON Schema on GitHub

JSON Schema

cam-monitor-plan-unit-capacity-dto-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-schema/cam-monitor-plan-unit-capacity-dto-schema.json",
  "title": "UnitCapacityDTO",
  "description": "UnitCapacityDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "maximumHourlyHeatInputCapacity": {
      "type": "number",
      "description": "The design heat input capacity (in mmBtu/hr) for the unit or the highest hourly heat input rate observed in the past five years, whichever is greater.",
      "example": 2322.1
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which a relationship or an activity began.",
      "example": "2009-01-01"
    },
    "endDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which a relationship or an activity ended. This value will be null for active records.",
      "example": null
    },
    "id": {
      "type": "string",
      "description": "Identity key for UNIT_CAPACITY table.",
      "example": "50233"
    },
    "unitId": {
      "type": "number",
      "description": "Identity key for UNIT table.",
      "example": "4705"
    },
    "commercialOperationDate": {
      "format": "date-time",
      "type": "string",
      "description": "The date a unit began, or will begin to generate electricity for sale, including the sale of test generation. It is the first date that a unit serves a generator and produces electricity when connected to the grid, even if the owners are not compensated for that electricity.",
      "example": "1977-04-01"
    },
    "date": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which activity occurred.",
      "example": "2019-01-01"
    },
    "boilerTurbineBeginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which monitoring began for a boiler or turbine unit.",
      "example": "2009-01-01"
    },
    "boilerTurbineEndDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which monitoring ended for a boiler or turbine unit.",
      "example": "2009-01-01"
    },
    "userId": {
      "type": "string",
      "description": "The user name of the person or process that created the record if the Update Date is empty.  Otherwise this is the user name of the person or process that made the last update.",
      "example": "abcde"
    },
    "addDate": {
      "type": "string",
      "description": "Date the record was created.",
      "example": "2009-02-20"
    },
    "updateDate": {
      "type": "string",
      "description": "Date of the last record update.",
      "example": "2009-02-20"
    },
    "active": {
      "type": "boolean",
      "description": "Flag for active monitor location record",
      "example": true
    },
    "boilerTurbineType": {
      "type": "string",
      "example": "string"
    }
  },
  "required": [
    "maximumHourlyHeatInputCapacity",
    "beginDate",
    "endDate",
    "id",
    "unitId",
    "commercialOperationDate",
    "date",
    "boilerTurbineBeginDate",
    "boilerTurbineEndDate",
    "userId",
    "addDate",
    "updateDate",
    "active",
    "boilerTurbineType"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cam-monitor-plan-unit-capacity-dto"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.