SA Project - Historical Events with start DateTime selection

In  alarm page DefaultSoE_HD1080 there in a hidden control on top left. I guess that it can be used to filter event from s selectyed Start Time. Se attaches images

¿How can we configure the page to to get that control visible and active?

Thanks in advance

Graphic Editor

RUNTIME

  • Hi Jose,

    This looks like the alarm page from the 2018 BETA? Those controls were removed. The default SOE page doesn't offer time filtering at this point in time.

    regards,

    bradley
  • Thanks for your support

    Yes, we are evaluating Citect 2018 for a building SCADA upgrade. Anyway, I think that a Start Time filter would be a very nice feature to improve Historical SOE usability.

    Regards
    José

  • Hi Jose,

    Absolutely agree. This is definitely in our backlog. As the topic has been raised, I would like to get a recent snapshot of feedback:

    Can I ask you and the community to outline your expectation around time filtering in the SOE/Active/Shelved pages?

    Consider:
    1. From an Operator point of view. What options would they frequently use? (e.g. Last Hour, Yesterday etc, Specific time)
    2. What would be the acceptable range of precision for selecting a start/filter time (minute? second? millisecond?)
    3. Would you ever use a range? (e.g. between date/time x and date/time y)
    4. For the first 3 questions, consider and identify frequency of use of those options
    5. From an Engineering perspective, do you see the options required by operators differ much between sites? If so how/ how often?

    cheers,
    bradley
  • as a reaction to Bradley his question,

    1. personaly i think Specific time/date would work the best? so that the Engineer and Operator have the most possible freedom to adjust, as for quick filter options, last hour, last 12 hours, last day/24H, last week and last month.

    2. i guess that unless you have multple events tringering within a second, millisecond is a bit too specific. at the same time, i am sure there is a group that does trigger multple events within a second and wouldnt mind being able to track it that precise. so i would say if possible leave it up to the Engineer to decide how precise they would like to have it.

    3.+4. as we tend to say here :"beter ermee verlegen dan erom verlegen" (prefer to have something too much than something too little)

    just my opinion and vieuw
    Arriën
  • I agree to Arriën, because Citect is a transversal SCADA covering many process areas. From elecrical substations (miliseconds) to BMS ( 1-10- seconds) applications.

    Besides standard quick filters mentioned, you may consider events by operator shifts (2-3 shifts/day )

    Start Time is my preferred wish

    José
  • Hi Bradley,

    From what we experience from the North Sea Oil&Gas sector and other O&G sectors around the globe, is being able to use a range. Where you enter from and to with date/time, the time is sufficient with Hours and Minutes. example: 2019-01-01 15:00 to 2019-05-26 09:00

    It would also be nice to have a quick button that is called "Current time". You enter from date/time and then click current time to set actual time as end date/time. We have done this with the Indusoft system.

    I would say that for our customers the range function is the search/filter option that is mostly in use by the operators and remote support offices. When an incident happens, they often turn to re-start the equipment/system as soon as possible if no major equipment failure is detected and they can manage to get the system ready to start. Then when production is up and running again they go back an investigate the incident an make a Root/Cause report from the historical data.


    We don't see this to differ at all from sites to sites. Date/time (with time in hh:mm) will do in almost any cases, when you are down to range of minute you have other filter options that could be used as well.

    This feature would be ,most appreciated if could be implemented as soon as possible.
    Could you anticipate any time frame for this, if decided to implement?

    Thanks,
    Rune
  • Thanks everyone for your feedback and suggestions. They will be valuable when we get to this feature.
    Unfortunately I can't give a timeframe for this other than to say I am quite certainl it would not come before Q3.
    In the meantime, if you have the time, this capability can be added to your alarm pages as Citect already exposes the necessary API's

    regards,
    bradley
  • Bradley:

    Is this still being worked on as we still don't see it in the product? Is there any information on how best to add it to the alarm pages as you say the APi's are already exposed for this?

    Thanks

    Byron
  • Hello Byron,

    Only bad news I am afraid. No we are not actively working on this. All of our focus is on finalising 2020 R2 at the moment. Although the scope of the release after is still being finalised, it is currently not making the cut.

    bradley
  • Hi Bradley,

    Just wanted to check with you once more on this topic, have there been any decision on the roadmap? 

    You mention above:

    In the meantime, if you have the time, this capability can be added to your alarm pages as Citect already exposes the necessary API's

    Is there available "none released"/beta code for this that could be shared and we could test/use, knowing that is is not an released version? 

    Thanks,

    Rune