The EiReport service interactions for Historian - eliminate StopHistorian, add flag to CancelHistorian to indicate "send final report"

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: Major
    • wd33
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:

      William Cox - EITC 20111026

    • Hide

      Eliminate StopHistorian and StoppedHistorian.

      Add to the CancelHistorian payload:

      sendFinalReport: boolean [1..1] - if absent or false, stop the historian and market buffered data for deletion. If true send a final report using the reportID

      reportID [0..1] MUST be present if sendFinalReport is true. Indicates what report to send the next/final of to take care of all flushed data. Normal rules apply for when the buffered data is marked for deletion or implicitly marked.

      Show
      Eliminate StopHistorian and StoppedHistorian. Add to the CancelHistorian payload: sendFinalReport: boolean [1..1] - if absent or false, stop the historian and market buffered data for deletion. If true send a final report using the reportID reportID [0..1] MUST be present if sendFinalReport is true. Indicates what report to send the next/final of to take care of all flushed data. Normal rules apply for when the buffered data is marked for deletion or implicitly marked.
    • Hide

      Eliminate StopHistorian and StoppedHistorian.

      Add to the CancelHistorian payload:

      reportToFollow: boolean [1..1] - if absent or false, stop the historian. If true send a final report using the updateReport

      reportID [0..1] MUST be present if reportToFollow is true. Indicates what report to send the next/final of to take care of all flushed data. Normal rules apply for when the buffered data is marked for deletion or implicitly marked.

      Show
      Eliminate StopHistorian and StoppedHistorian. Add to the CancelHistorian payload: reportToFollow: boolean [1..1] - if absent or false, stop the historian. If true send a final report using the updateReport reportID [0..1] MUST be present if reportToFollow is true. Indicates what report to send the next/final of to take care of all flushed data. Normal rules apply for when the buffered data is marked for deletion or implicitly marked.

      Discussion was around eliminating StopHistorian versus CancelHistorian. The former indicates that the rest of the recorded information may be picked up, the latter to discard.

      Gerry Gray suggested that a flag on CancelHistorian that says either
      (a) Stop what you're doing on this and you can toss everything you've saved, or
      (b) Stop what you're doing on this and send a final report
      would fit the interaction patterns better (rejected approach: add "ChangeHistorian" to say "stop" etc – too much complexity)

      BUT the historian is NOT the one sending the reports. It only records.

      So the change would be to add SendFinalReport: boolean to CancelHistorian AND to include a reportID so you know what report to finalize and send. In this way the receiver can call their internal code to mimic a "send final report" with the reportID, AND stop the Historian at the appropriate time.

            Assignee:
            William Cox (Inactive)
            Reporter:
            William Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: