search

Haigutus / Energy-Reference-Data

Reference Data for Energy domain using SKOS
0 stars 2 forks source link

Create CSA ReferenceData #51

Open Sveino opened 1 year ago

Sveino commented 1 year ago

For the Coordinated Security Analysis (CSA) we will need the following:

Header Reference:

Payload Reference:

Haigutus commented 1 year ago

My idea would be for explicit role and party definition nc:zzz.SystemOperator -> Use http://energy.referencedata.eu/PartyRole/ -> Party X EIC

Implicit use would be nc:zzz.SystemOperator -> Party X EIC

Principle: One can use the explicit reference if the same ID is not used for multiple object within the data exchange One must use implicit reference ID the same ID would be used for multiple objects within the data exchange

Possible Examples:

SKOS

RDF/XML

Sveino commented 1 year ago

On 2023-07-13 we had a meeting with Cost sharing and we modified the following header from:

    <md:FullModel rdf:about="urn:uuid:4db995ef-d3af-433a-8099-8cb25f7d5dd2">
        <prov:generatedAtTime>2023-01-16T22:05:25Z</prov:generatedAtTime>
        <dcterms:creator>urn:eic:10X1001A1001A094</dcterms:creator>
        <dcat:keyword>RAS</dcat:keyword>
        <prov:wasInfluencedBy>urn:uuid:095c6b30-255d-40d5-85fe-2c9fe6c9846d</prov:wasInfluencedBy>
        <dcterms:license>https://creativecommons.org/licenses/by/4.0/</dcterms:license>
        <dcat:version>1.0</dcat:version>
        <eumd:applicationSoftware>PowerFactory-2022.SP2</eumd:applicationSoftware>
        <dcterms:description>This is an example of  remedial action schedule profile.</dcterms:description>
        <prov:wasAttributedTo>urn:eic:10X1001A1001A094</prov:wasAttributedTo>
        <!--There is no limitation on the period between start and end date-->
        <dcat:startDate>2022-12-18T23:30:00Z</dcat:startDate>
        <dcat:endDate>2022-12-19T23:30:00Z</dcat:endDate>
        <dcterms:identifier>urn:uuid:4db995ef-d3af-433a-8099-8cb25f7d5dd2</dcterms:identifier>
        <dcterms:conformsTo>http://entsoe.eu/ns/CIM/RemedialActionSchedule-EU/2.2</dcterms:conformsTo>
        <dcterms:conformsTo>http://entsoe.eu/ns/CIM/PowerSchedule-EU/2.2</dcterms:conformsTo>
    </md:FullModel>

to the new header:

    <md:FullModel rdf:about="urn:uuid:4db995ef-d3af-433a-8099-8cb25f7d5dd2">
        <!--When you send a new version with the same data, the generatedAtTime is updated but the 'issued' attribute is not.-->
        <prov:generatedAtTime>2023-01-16T22:05:25Z</prov:generatedAtTime>
        <!--Instant in time when the dataset was made available. It cannot be after the generatedAtTime. -->
        <dcterms:issued>2023-01-14T18:05:25Z</dcterms:issued>
        <!--The publisher is the authority that makes these data available. By clicking on the link below you will get information on the publisher.-->
        <!--Another option is to put it like this: <dcterms:publisher rdf:resource="http://energy.referencedata.eu/Party/10X1001A1001A39W"/>-->
        <dcterms:publisher rdf:resource="http://energy.referencedata.eu/EIC/10X1001A1001A094"/>
        <dcat:keyword>RAS</dcat:keyword>
        <!--The one below is replacing the 'wasInfluencedBy' attribute. Meaning is still the same. It is the dependency, referring to the offline dataset where data can be linked to (see rdf:resource references). It should refer to the Remedial Action instance file delivered by your TSO.-->
        <dcterms:references rdf:resource="urn:uuid:095c6b30-255d-40d5-85fe-2c9fe6c9846d"/>
        <!--The license indicates what the user can do with the file.-->
        <dcterms:license rdf:resource="https://creativecommons.org/licenses/by/4.0"/>
        <!--The access rights attribute is indicating the security scheme. Now it is defined as 'OPDE confidential'. To be reviewed among TSOs.-->
        <dcterms:accessRights rdf:resource="http://energy.referencedata.eu/Confidentiality/4cd9b326-1275-4da7-9724-28c5e1deeb87"/>
        <dcat:version>1.0.0</dcat:version>
        <!--Preferably the following attribute is removed: <eumd:applicationSoftware>PowerFactory-2022.SP2</eumd:applicationSoftware>-->
        <dcterms:description>This is an example of  remedial action schedule profile.</dcterms:description>
        <!--There is no limitation on the period between start and end date-->
        <dcat:startDate>2022-12-18T23:30:00Z</dcat:startDate>
        <dcat:endDate>2022-12-19T23:30:00Z</dcat:endDate>
        <dcterms:identifier>urn:uuid:4db995ef-d3af-433a-8099-8cb25f7d5dd2</dcterms:identifier>
        <dcterms:conformsTo rdf:resource="http://entsoe.eu/ns/CIM/RemedialActionSchedule-EU/2.2"/>
        <dcterms:conformsTo rdf:resource="http://entsoe.eu/ns/CIM/PowerSchedule-EU/2.2"/>
        <!--The new attribute below is to indicate by which action/process it was created. The possible entries must be agreed with ROSC and CS.-->
        <prov:wasGeneratedBy rdf:resource="http://energy.referencedata.eu/CGM/Action/CGM-1D-RAS"/>
        <!--The attribute below is the persistent part between each of the RAS dataset versions.-->
        <dcat:isVersionOf rdf:resource="http://energy.referencedata.eu/Model/ELIA_CGM-RAS"/>
        <!--The attribute below indicates that this model is filling the frame of the Belgian grid-->
        <dcterms:spatial rdf:resource="http://energy.referencedata.eu/Frame/BE_Transmission_Grid"/>
        <!--The title below should be the name of the file. Convention could be start date, publisher and then the wasGeneratedBy.-->
        <dcterms:title>20221219_ELIA_CGM-1D-RAS</dcterms:title>
    </md:FullModel>
Sveino commented 1 year ago

For the payload (CIM model) reference I am unsure what we have agreed. Currently I am thinking that we need to create a Equipment Reliability (ER) reference dataset similar to the one that we have created for DIGIN (only including GeographicalRegion and SubGeographicalRegion : https://github.com/digin-energi/Grunnprofil/blob/develop/DIGIN10/Grid/CIMXML/DIGIN10-30-GeographicalRegion_RD.xml

We would need:

  1. GeographicalRegion
  2. SubGeographicalRegion
  3. OverlappingZone
  4. EnergyAlignmentCoordinator
  5. EnergyCoordinationRegion
  6. OutageCoordinator
  7. OutageCoordinationRegion
  8. CapacityCalculationRegion
  9. SecurityCoordinator
  10. BiddingZone
  11. BiddingZoneBorder
  12. LoadFrequencyControlArea
  13. LoadFrequencyControlBlock
  14. SynchronousArea
  15. TransmissionSystemOperator

If we do this, all reference would be rdf:resource="#_f75a282c-2b40-49a8-a32f-f33a241a562d (same as standard reference) We would need to add reference to this dataset as part of the individual ER from the TSOs.

Haigutus commented 1 year ago

@Haigutus @griddigit Please provide counter proposals, if needed

Topics

  1. IRI vs str IRI -> decised IRI is ok
  2. /EIC/ vs /EIC/Party -> /EIC/ is currently kept (noted: Svein is of opinion that is not good idea)
  3. wasGeneratedBy - used uuid or name? names tend to change, thus proposal to go to uuid - OPEN
  4. spatial - use uuid or name? currently name is used, with name some standard naming scheme should be provided