Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-601 Collector for EiReport Issues
  3. ENERGYINTEROP-614

EIReports section is still very unclear

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd33
    • Fix Version/s: wd34
    • Component/s: None
    • Labels:
      None
    • Environment:

      Ed Koch

    • Proposal:
      Hide

      The section should start with a basic description of the core functionality and what is trying to be accomplished which is to exchange report information. Describe what reports are and the services that are used to describe the exchange of reports. After that you can start laying on some of the support services that MAY (let me re-emphasize the word MAY) be used to control the reporting behaviour and define the meta-data. Again the latter services are necessary evils and should not be required for the VEN to send the VTN a simpler report. Perhaps we should find someone other than Toby to write this section to make sure that there is at least more than one person that understands this stuff.

      Show
      The section should start with a basic description of the core functionality and what is trying to be accomplished which is to exchange report information. Describe what reports are and the services that are used to describe the exchange of reports. After that you can start laying on some of the support services that MAY (let me re-emphasize the word MAY) be used to control the reporting behaviour and define the meta-data. Again the latter services are necessary evils and should not be required for the VEN to send the VTN a simpler report. Perhaps we should find someone other than Toby to write this section to make sure that there is at least more than one person that understands this stuff.
    • Resolution:
      Hide

      See narrative in the comments. Section rewritten for wd34.

      Show
      See narrative in the comments. Section rewritten for wd34.

      Description

      I honestly still do not understand how to use the EIReports to do some of the very simple feedback use cases that I want to support. The sections seems to be a muddled collection of services and it is not clear what services are really required and how you would use them. There seem to be a bunch of bureaucratic services for creating "historians" and "report specifications", but how they are tied together and used is very unclear. If I can't understand this then I honestly don't know how someone coming into this cold has a hope of understanding it.

      For example on line 1707 it says "EiReport is prepared by a Party upon request and supplied to the requesting party. It may also be defined in the expectations of the Market Context." Does this mean that the only way a report can be generated is by request? The simple use cases deployed today do not require any registrations or report specification services or any of this overhead. The report specifications and what not are created by convention and while some systems may want to employ all these extra meta data services they should not be required.

        Attachments

          Activity

            People

            • Assignee:
              ed.koch Ed Koch (Inactive)
              Reporter:
              ed.koch Ed Koch (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: