1 / 14

Expectations to a Control System from Different User Groups Stefan Wilke DESY, MST

Expectations to a Control System from Different User Groups Stefan Wilke DESY, MST Heiko Ehrlichmann DESY, MPE. Until now: Status and Progress of Control Systems, Technical Details, System Administration, Concepts, Tools,. What’s about the users?.

hieu
Download Presentation

Expectations to a Control System from Different User Groups Stefan Wilke DESY, MST

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. Expectations to a Control System from Different User Groups Stefan Wilke DESY, MST Heiko Ehrlichmann DESY, MPE

  2. Until now: Status and Progress of Control Systems, Technical Details, System Administration, Concepts, Tools, ... What’s about the users? • (control system constructors) • chief of a machine • guest (WWW) • persons who care for components • operator on shift

  3. Requirements to a Control System other layer (no machine operating): secure, stable, uniform solutions, easy maintenance

  4. Main goal: efficient, stable, smooth operation and happy experiments. perfect control system pleased and motivated shift crew Could there be both? How? What do a operation crew want?

  5. The operation crew want: • A comfortable shift! • ergonomic • automation • participation in consol program design • stability

  6. Official rules for work at consols (ISO/DIS 9241-10, 1993) (DIN 66234-8) • Suitable for the task • Self-explaining • Controllability • Perform user expectations • Error tolerance • Modification for user individual needs are possible • ...

  7. Operators view Conventional Wisdoms I • eye friendly backgrounds / contrast (not white) • fonts (text and numbers), buttons and controls not too small • color codes (green: ok, yellow: selected or warning, red: error) • not too much color on the screen • no overlapping windows (prevent covered information) • no delay to user actions (at least a hourglass) • enough data - but not too much! • suitable update rate (not too fast, not too slow) • consistent data at all consol and all displays • separation of status and operating (no status on command button)

  8. Operators view Conventional Wisdoms II • stability in operation • no cryptic error messages (“Error 42”, “FPSS Time Out”) • a helpful alarm system! (only real errors, acoustic on main errors) • no extreme hierarchical menu structure (climbing up/down trees) • compact operation (e.g.: no switching sequence at different terminals) • no operation from outside without permission by the operator • variability (to changing and additional whishes) • archiving (all relevant information for offline - correlations) • documentation

  9. Automation!? good for But need of reliable data need of very(!) good error- and alarm system transparence needed (no hidden procedures) shift crew becomes stupid nobody could run the machine ‘by hand’ anymore lost of feeling to the machine which procedures should become automatic? how deep?

  10. Examples of automation at DESY HERA sequencer PETRA autopilot

  11. The Future?

More Related