View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008175 | 10000-011: Historical Access | Spec | public | 2022-07-29 16:29 | 2022-12-07 20:04 |
| Reporter | Alexander Allmendinger | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.04 | ||||
| Fixed in Version | 1.05.03 RC1 | ||||
| Summary | 0008175: Specification is missing scenarios to describe certain bad StatusCodes | ||||
| Description | In Section 6.4.3 there is no definition what is expected from a Historian for scenarios e.g. where the data source is disconnected or not available. Currently there is no clear definition whether all historians are required to return Bad_DataLost when a history client is asking for a time range where the historian itself was shutdown. Nor whether a Bad needs to be stored in the historian when the connection to the data source has gone bad. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Added a section describing Historian and interruption of data, including expected error codes |
|
|
Agreed to changes edited in virtual F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-29 16:29 | Alexander Allmendinger | New Issue | |
| 2022-08-02 16:36 | Jim Luth | Assigned To | => Rod Stein |
| 2022-08-02 16:36 | Jim Luth | Status | new => assigned |
| 2022-12-05 07:04 | Paul Hunkar | Assigned To | Rod Stein => Paul Hunkar |
| 2022-12-05 07:15 | Paul Hunkar | Status | assigned => resolved |
| 2022-12-05 07:15 | Paul Hunkar | Resolution | open => fixed |
| 2022-12-05 07:15 | Paul Hunkar | Fixed in Version | => 1.05.03 RC1 |
| 2022-12-05 07:15 | Paul Hunkar | Note Added: 0018229 | |
| 2022-12-07 20:04 | Jim Luth | Status | resolved => closed |
| 2022-12-07 20:04 | Jim Luth | Note Added: 0018271 |
