1 / 17

HCI convention

HCI convention. For controls and supervision applications in ST. Overview. Purpose of the standard Origin Contents What did not change What changed How to use it. Purpose of the HCI standard. Standardize the HCIs for different systems Important for TCR, user of all HCIs

kaleb
Download Presentation

HCI convention

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HCI convention For controls and supervision applications in ST P. Sollander

  2. Overview • Purpose of the standard • Origin • Contents • What did not change • What changed • How to use it P. Sollander

  3. Purpose of the HCI standard • Standardize the HCIs for different systems • Important for TCR, user of all HCIs • Re-use of local HCIs in TCR • Before: TCR developed views for eq. Groups • Now: Equipment groups develop for TCR • Re-use only possible if it follows guidelines • Ease development • No need to decide on shapes, colours… P. Sollander

  4. Origin of the ST HCI standard • Two sources • TCR HCI standards • Already existing/used. Defines shapes and colours • Scada Application Support Group (SASG) • CERN-wide PVSS guidelines (draft Nov-02) • One PVSS specific part + one general part • Developed in collaboration (ST, LHC, JCOP) • New ST standard • Extension rather than replacement of TCRHCI P. Sollander

  5. HCI standard - contents • TCR integration policy • View layout • Symbols, object, widgets • General HCI issues • Pop-up windows, navigation, command handling • Colour definition P. Sollander

  6. TCR integration policy 1/2 • It must be possible to access the view without any special software installation on the TCR side. Generic integration via for example a web browser is recommended. • It must be possible to directly access any particular view. It is not acceptable to access an overview of the local SCADA system and navigate to the specific view of interest. P. Sollander

  7. TCR integration policy 2/2 • The SCADA view must conform to the present conventions. • The view must be accepted by the TCR responsible before being made operational. In practice, the development of views for the TCR shall be done in collaboration with the TCR responsible. Collaboration in the early stages of a project will minimize correction and redevelopment specific to the TCR. P. Sollander

  8. View layout P. Sollander

  9. Symbols, object, widgets • General layout Object surrounding: selection state alarm/ interlock nature & blocking/masking status Data Quality 1 2 Body Object body Filling: operational state Control mode Object body color: operational state & alarm state 4 3 5 :Feedback & orders or option mode Operational state label Label: Name of object (bottom or middle-right) P. Sollander

  10. Symbols, object, widgets • Colours P. Sollander

  11. Colours P. Sollander

  12. Symbols, object, widgets • Shapes P. Sollander

  13. What did not change (from TCR HCI) • Colours • Same colours indicating states and alarms • Symbol shapes • Same standard shapes (ISO) • General recommendations • Line styles, units, equipment layout, … • The old recommendation is still valid! But, P. Sollander

  14. Additional guidelines • New colour • New framework • Additional codes • Object filling for valves, pumps and ventilators Data not defined P. Sollander

  15. How to use the standards • Use what is applicable • Not all applications can use all features • New development • Guidelines + View specifications + Interactive development/review process • LHC ventilation point 8 and LHC cooling (CCM) development about to start • Existing applications • TCR will update as far as reasonably possible • Symbols can be changed, UMMI framework cannot change.. P. Sollander

  16. First use • LHC Ventilation - point 8 • ST/CV contractor implement the local SCADA views using the standards. P. Sollander

  17. SF5 ventilation. P. Sollander

More Related