{ "$defs": { "BaseWork": { "additionalProperties": false, "description": "Common representation for work and work tasks.", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "status_kind": { "$ref": "#/$defs/WorkStatusKind", "description": "Kind of work status." }, "time_schedules": { "description": "All time schedules for this work or work task.", "items": { "$ref": "#/$defs/WorkTimeSchedule" }, "type": "array" }, "type": { "description": "Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).", "type": "string" } }, "required": [ "time_schedules" ], "title": "BaseWork", "type": "object" }, "DateTimeInterval": { "additionalProperties": false, "description": "Interval between two date and time points, where the interval includes the start time but excludes end time.", "properties": { "end": { "description": "End date and time of this interval. The end date and time where the interval is defined up to, but excluded. Follows the international date format of YYYY-MM-DD, i.e. 2024-12-31. When only a specific month is known, use *01* as day. This is the *Beoogde in bedrijfsname* in the previous implementation.", "format": "date", "type": "string" }, "quarter": { "description": "Yearly quarter indicator. Used for the coming two years relative to this dataset. Identified as *Q[number]* for the first year, *H[number]* for the second year.", "type": "string" }, "start": { "description": "Start date and time of this interval. The start date and time is included in the defined interval. Follows the international date format of YYYY-MM-DD, i.e. 2024-12-31. When only a specific month is known, use *01* as day. This is the *Startdatum* in the previous implementation.", "format": "date", "type": "string" } }, "required": [ "end" ], "title": "DateTimeInterval", "type": "object" }, "Document": { "additionalProperties": false, "description": "Parent class for different groupings of information collected and managed as a part of a business process. It will frequently contain references to other objects, such as assets, people and power system resources.", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "type": { "description": "Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).", "type": "string" } }, "title": "Document", "type": "object" }, "EnergyArea": { "additionalProperties": false, "description": "Describes an area having energy production or consumption. Specializations are intended to support the load allocation function as typically required in energy management systems or planning studies to allocate hypothesized load levels to individual load points for power flow analysis. Often the energy area can be linked to both measured and forecast load levels.", "properties": { "demand_alleviation_year": { "description": "Year (e.g. *2028*) from which any capacity issues have been alleviated for the EnergyArea.", "type": "integer" }, "demand_available_capacity": { "description": "The available demand capacity (in MW) at the EnergyArea. The value should reflect the capacity a network operator would make available to a connecting party. This is the *Aanwezige transportcapaciteit (in MW) afname huidige jaar* in the previous implementation.", "type": "integer" }, "demand_capacity_in_queue": { "description": "The contract value of demand requests not yet granted. This is the *Wachtrij in capaciteit - afname* in the previous implementation.", "type": "integer" }, "demand_constraint": { "$ref": "#/$defs/RAGKind", "description": "A RAG definition of the demand constraints at the EnergyArea. A utility should provide details on how this RAG status is calculated as part of the accompanying documentation. Only specify this attribute if no PostcodeArea-s are provided." }, "demand_forecast_capacity": { "description": "Sum of all demand (in MW) forecast for the current year at the EnergyArea.", "type": "integer" }, "demand_quoted_capacity": { "description": "Sum of all demand (in MW) currently quoted at the EnergyArea. This is the *Benodigde transportcapaciteit (in MW) afname* in the previous implementation.", "type": "integer" }, "demand_requests_in_queue": { "description": "Number of demand requests for new grid connections and capacity increases in queue. This is the *Aantal unieke transportverzoeken in een wachtrij - afname* in the previous implementation.", "type": "integer" }, "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "generation_alleviation_year": { "description": "Year (e.g. *2028*) from which any capacity issues have been alleviated for the EnergyArea.", "type": "integer" }, "generation_available_capacity": { "description": "Available generation capacity (in MW) at the EnergyArea. This is the *Aanwezige transportcapaciteit (in MW) invoeding huidige jaar* in the previous implementation.", "type": "integer" }, "generation_capacity_in_queue": { "description": "The contract value of generation requests not yet granted. This is the *Wachtrij in capaciteit - invoeding* in the previous implementation.", "type": "integer" }, "generation_constraint": { "$ref": "#/$defs/RAGKind", "description": "A RAG definition of the generation constraints at the EnergyArea. A utility should provide details on how this RAG status is calculated as part of the accompanying documentation. Only specify this attribute if no PostcodeArea-s are provided." }, "generation_forecast_capacity": { "description": "Sum of all forecast generation (in MW) for the current year at the EnergyArea.", "type": "integer" }, "generation_quoted_capacity": { "description": "Sum of all currently quoted generation (in MW) at the EnergyArea. This is the *Benodigde transportcapaciteit (in MW) invoeding* in the previous implementation.", "type": "integer" }, "generation_requests_in_queue": { "description": "Number of generation requests for new grid connections and capacity increases in queue. This is the *Aantal unieke transportverzoeken in een wachtrij - invoeding* in the previous implementation.", "type": "integer" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "postcode_areas": { "description": "Postcode Areas serviced by this EnergyArea.", "items": { "$ref": "#/$defs/PostcodeArea" }, "type": "array" }, "short_code": { "description": "Short code name for EnergyArea. This is the *Uniek ID voedingsgebied* in the previous implementation.", "type": "string" }, "works": { "description": "All the works performed for this EnergyArea.", "items": { "$ref": "#/$defs/Work" }, "type": "array" } }, "required": [ "demand_available_capacity", "generation_available_capacity" ], "title": "EnergyArea", "type": "object" }, "HeatmapDataSet": { "additionalProperties": false, "description": "A single instance of a published dataset. The descriptions of these fields are taken from the Dublin Core Standard.", "properties": { "conforms_to": { "description": "ID for the schema used to create the instance data.", "type": "string" }, "contributor": { "description": "An entity responsible for making contributions to the resource.", "type": "string" }, "coverage": { "description": "The spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.", "type": "string" }, "creator": { "description": "An entity responsible for making the resource.", "type": "string" }, "date": { "description": "A point of time associated with an event in the lifecycle of the resource. For this implementation this will represent the date the data set is valid from.", "format": "date", "type": "string" }, "description": { "description": "An account of the resource.", "type": "string" }, "energy_areas": { "description": "A list of energy areas with heatmap data.", "items": { "$ref": "#/$defs/EnergyArea" }, "type": "array" }, "format": { "description": "The file format of the resource.", "type": "string" }, "identifier": { "description": "An unambiguous reference to the resource within a given context.", "type": "string" }, "issued": { "description": "Date of formal issuance of the resource.", "format": "date", "type": "string" }, "language": { "description": "A language of the resource.", "type": "string" }, "publisher": { "description": "An entity responsible for making the resource available.", "type": "string" }, "rights": { "description": "Information about rights held in and over the resource.", "type": "string" }, "title": { "description": "A name given to the resource.", "type": "string" }, "valid": { "description": "A date range for the validity of a resource. This should be two dates to form a range. The first date is inclusive and the second date exclusive.", "format": "date", "type": "string" } }, "required": [ "conforms_to", "contributor", "coverage", "creator", "date", "description", "format", "identifier", "issued", "language", "publisher", "rights", "title" ], "title": "HeatmapDataSet", "type": "object" }, "IdentifiedObject": { "additionalProperties": false, "description": "This is a root class to provide common identification for all classes needing identification and naming attributes.", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" } }, "title": "IdentifiedObject", "type": "object" }, "Name": { "additionalProperties": false, "description": "The Name class provides the means to define any number of human readable names for an object. A name is not to be used for defining inter-object relationships. For inter-object relationships instead use the object identification 'mRID'", "properties": { "name_type": { "$ref": "#/$defs/NameType", "description": "Type of this name." } }, "required": [ "name_type" ], "title": "Name", "type": "object" }, "NameType": { "additionalProperties": false, "description": "Type of name. Possible values for attribute 'name' are implementation dependent but standard profiles may specify types. An enterprise may have multiple IT systems each having its own local name for the same object, e.g. a planning system may have different names from an EMS. An object may also have different names within the same IT system, e.g. localName as defined in CIM version 14. The definition from CIM14 is The localName is a human readable name of the object. It is a free text name local to a node in a naming hierarchy similar to a file directory structure. A power system related naming hierarchy may be Substation, VoltageLevel, Equipment etc. Children of the same parent in such a hierarchy have names that typically are unique among them.", "properties": { "description": { "description": "Description of the name type.", "type": "string" }, "name_type_authority": { "$ref": "#/$defs/NameTypeAuthority", "description": "Authority responsible for managing names of this type." } }, "title": "NameType", "type": "object" }, "NameTypeAuthority": { "additionalProperties": false, "description": "Authority responsible for creation and management of names of a given type; typically an organization or an enterprise system.", "properties": { "description": { "description": "Description of the name type authority.", "type": "string" } }, "title": "NameTypeAuthority", "type": "object" }, "PostcodeArea": { "additionalProperties": false, "description": "A geographic region that is defined by the initial letters or digits of a postcode.", "properties": { "demand_constraint": { "$ref": "#/$defs/RAGKind", "description": "A RAG definition of the demand constraints at the EnergyArea. A utility should provide details on how this RAG status is calculated as part of the accompanying documentation. This is the *Kleurcodering van het postcodegebied voor afname* in the previous implementation." }, "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "generation_constraint": { "$ref": "#/$defs/RAGKind", "description": "A RAG definition of the generation constraints at the EnergyArea. A utility should provide details on how this RAG status is calculated as part of the accompanying documentation. This is the *Kleurcodering van het postcodegebied voor opwek* in the previous implementation." }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "postcode": { "description": "Identifier for the postcode area. Contain four (4) numbers, followed by two (2) letters, uppercase. No spaces between the numbers and letters, i.e. \"1234AB\".", "type": "string" } }, "required": [ "postcode", "demand_constraint", "generation_constraint" ], "title": "PostcodeArea", "type": "object" }, "RAGKind": { "description": "Traffic light colors coding scheme for categorising status.", "enum": [ "transparant", "red", "amber", "yellow" ], "title": "RAGKind", "type": "string" }, "TimeSchedule": { "additionalProperties": false, "description": "Description of anything that changes through time. Time schedule is used to perform a single-valued function of time. Use inherited 'type' attribute to give additional information on this schedule, such as periodic (hourly, daily, weekly, monthly, etc.), day of the month, by date, calendar (specific times and dates).", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "schedule_interval": { "$ref": "#/$defs/DateTimeInterval", "description": "Schedule date and time interval." }, "type": { "description": "Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).", "type": "string" } }, "required": [ "schedule_interval" ], "title": "TimeSchedule", "type": "object" }, "Work": { "additionalProperties": false, "description": "Document used to request, initiate, track and record work. Use the *description* attribute to add additional information about this *Work*. This is *Toelichting bijzonderheden rondom planning* in the previous implementation.", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "project_name": { "description": "Name of the project this work belongs to. This is the *Projectnaam* in the previous implementation.", "type": "string" }, "status_kind": { "$ref": "#/$defs/WorkStatusKind", "description": "Kind of work status." }, "time_schedules": { "description": "All time schedules for this work or work task.", "items": { "$ref": "#/$defs/WorkTimeSchedule" }, "type": "array" }, "type": { "description": "Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).", "type": "string" } }, "required": [ "time_schedules" ], "title": "Work", "type": "object" }, "WorkStatusKind": { "description": "Kind of status, specific to work.", "enum": [ "cancelled", "completed", "inProgress", "scheduled" ], "title": "WorkStatusKind", "type": "string" }, "WorkTimeSchedule": { "additionalProperties": false, "description": "Time schedule specific to work.", "properties": { "description": { "description": "The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This is the *Herkenbare naam voedingsgebied* in the previous implementation.", "type": "string" }, "m_rid": { "description": "Master resource identifier issued by a model authority. The mRID is unique within an exchange context. Global uniqueness is easily achieved by using a UUID, as specified in RFC 4122, for the mRID. The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61970-552, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.", "type": "string" }, "names": { "description": "All names of this identified object.", "items": { "$ref": "#/$defs/Name" }, "type": "array" }, "schedule_interval": { "$ref": "#/$defs/DateTimeInterval", "description": "Schedule date and time interval." }, "type": { "description": "Utility-specific classification of this document, according to its corporate standards, practices, and existing IT systems (e.g., for management of assets, maintenance, work, outage, customers, etc.).", "type": "string" } }, "required": [ "schedule_interval" ], "title": "WorkTimeSchedule", "type": "object" }, "WorkTimeScheduleKind": { "description": "Kind of work schedule.", "enum": [ "actual", "earliest", "estimate", "immediate", "latest", "request" ], "title": "WorkTimeScheduleKind", "type": "string" } }, "$id": "http://data.netbeheernederland.nl/capaciteitskaart/v1.2.0", "$schema": "https://json-schema.org/draft/2019-09/schema", "additionalProperties": true, "description": "A single instance of a published dataset. The descriptions of these fields are taken from the Dublin Core Standard.", "metamodel_version": "1.7.0", "properties": { "conforms_to": { "description": "ID for the schema used to create the instance data.", "type": "string" }, "contributor": { "description": "An entity responsible for making contributions to the resource.", "type": "string" }, "coverage": { "description": "The spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.", "type": "string" }, "creator": { "description": "An entity responsible for making the resource.", "type": "string" }, "date": { "description": "A point of time associated with an event in the lifecycle of the resource. For this implementation this will represent the date the data set is valid from.", "format": "date", "type": "string" }, "description": { "description": "An account of the resource.", "type": "string" }, "energy_areas": { "description": "A list of energy areas with heatmap data.", "items": { "$ref": "#/$defs/EnergyArea" }, "type": "array" }, "format": { "description": "The file format of the resource.", "type": "string" }, "identifier": { "description": "An unambiguous reference to the resource within a given context.", "type": "string" }, "issued": { "description": "Date of formal issuance of the resource.", "format": "date", "type": "string" }, "language": { "description": "A language of the resource.", "type": "string" }, "publisher": { "description": "An entity responsible for making the resource available.", "type": "string" }, "rights": { "description": "Information about rights held in and over the resource.", "type": "string" }, "title": { "description": "A name given to the resource.", "type": "string" }, "valid": { "description": "A date range for the validity of a resource. This should be two dates to form a range. The first date is inclusive and the second date exclusive.", "format": "date", "type": "string" } }, "required": [ "conforms_to", "contributor", "coverage", "creator", "date", "description", "format", "identifier", "issued", "language", "publisher", "rights", "title" ], "title": "im-capaciteitskaart", "type": "object", "version": "1.2.0" }