1. DISCS - Distributed Information Services for Control Systems
Eric Berryman
FRIB-NSCL,
East Lansing, Michigan, USA.

2. Overview Problem Vision Collaborators Architecture
Development Methodology
Domains & Modules
Current Status
Conclusion

3. The Problem

4. Problem Statement
Disparate and Heterogeneous Systems Used During The Design, Construction, Commissioning, Operation, and Maintenance of an Experimental Physics Facility (EPF)
No Way to Share Data

5. Problem Illustration

6. DISCS

7. DISCS Vision
To Develop Collaborating Services That Any Experimental Physics Facility Can Easily Configure, Use, And Extend For Its Design, Commissioning, Operation, And Maintenance

8. DISCS – Scope I

9. DISCS – Scope II

10. DISCS Collaborators
Brookhaven National Lab, USA
Cosylab, Slovenia
European Spallation Source, Sweden
Facility for Rare Isotope Beam, USA
Institute for High Energy Physics, China

11. DISCS Challenges Integration Of Myriad Databases
Multiple Teams From Different Labs
Geographically Dispersed Collaboration
Labs Have Different Priorities
Labs Have Different Schedules
Labs Have Different Technology Platforms
Differing Software-engineering Processes

12. DISCS – Architecture

13. DISCS Architecture Application layer Service layer Data layer
Operator interfaces
High-level applications
Libraries
Service layer
Access to data
Programming Interface
Data layer
Managed data
Instrument data
No direct access

14. EPICS V4 - DISCS

15. Development Methodology
I – Divide
Entire System Is Broken Down Into Smaller Loosely-coupled Parts Or Domains
II – Develop
Each Domain Is Implemented Independently
III – Frame
Application Programming Interfaces Are Developed
IV – Integrate
Domains Are Integrated
Check Paper For Details

16. DISCS Modules
Module: An Implementation Of A Domain

17. DISCS - Status

18. DISCS Status Domain Team Status Configuration FRIB,ESS,Cosylab
In Production At FRIB
Cables
FRIB
Under Development
eTraveler
Lattice-Model
BNL, FRIB, ESS
Prototypes At FRIB and BNL
Logbook
BNL, FRIB
In Production At FRIB & BNL.
Inventory
Naming System
In Production at FRIB
Operations
Save/Restore
BNL
In Production at BNL
Security
ESS, Cosylab, FRIB
Signals (PV)
In Production at BNL, FRIB (ChannelFinder)
Unit Conversion

19. DISCS - Screenshots

20. Logbook: Web Client

21. Logbook: CSS Client

22. Logbook: pyOlog

23. eTraveler – List of Travelers

24. eTraveler – Devices Integration with Configuration Module

25. Configuration: Component Tree

26. Configuration: Magnet Measurement

27. Configuration: Live Signals (PV)

28. Screenshots – Configuration Module

29. Configuration: Component Relationships

30. Configuration: Component Relationships

31. Configuration: Lattice

32. Lattice-Model: Beamlines

33. Naming Convention – Name Elements
Name Elements Are Parts of A Name: System, Subsystem, Device Type etc

34. Naming Convention – Submit Requests
Submit Requests to Add, Modify, or Delete Name Elements

35. Naming Convention – Process Requests

36. Naming Convention - Reports

37. Screenshots – Unit Conversion

38. Screenshots – Save/Restore

39. Cables – Normal View

40. Cables – Manager View

41. Cables - Types

42. Conclusion
Described An Information Services Framework For Accelerator Design, Commissioning, Operation, And Maintenance
Discussed Challenges To Collaborative Development
Acknowledgements:
IRMIS, Control System Studio, EPICS V4, ChannelFinder, and PVManager Teams
DISCS Website:

43. – Fred Brooks, The Mythical Man-Month
Thank you!
“Nine people can’t make a baby in a month.”
– Fred Brooks, The Mythical Man-Month
“Computer science is no more about computers than astronomy is about telescopes”
– Edsger W Dijkstra