1 / 13

JCOP Roadmap

JCOP Roadmap. JCOP External Review 10 th -12 th March 2003. Overview. Current situation and approach On-going activities New activities Looking forward Major milestones and resources Summary. Current Situation. CERN resources, both financial and manpower, are continuing to decline

chaka
Download Presentation

JCOP Roadmap

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. JCOP Roadmap JCOP External Review 10th-12th March 2003

  2. Overview • Current situation and approach • On-going activities • New activities • Looking forward • Major milestones and resources • Summary

  3. Current Situation • CERN resources, both financial and manpower, are continuing to decline • In such an environment common projects are very important • Reduce overall development effort • Ease maintenance • Common projects imply some level of compromise • Only activities which are required for the majority of the experiments • JCOP works via consensus

  4. Approach Essentially to continue the approach adopted up-to-now: • Commercial solutions where possible • Reduce resources • Ease maintenance • Where custom solutions are required • Agreed support and maintenance concept (includes proper documentation) • Monitor work of other domains and collaborate (where appropriate) to benefit from their work: • Controls Board – standardisation at CERN and exchange information with other controls domains, e.g. LHC/CP • LHC Data Interchange Working Group (LDIWG) - DIP • SASG - PVSS developments • LHC Cryogenics - UNICOS • Computer Centre Supervision Project - Computer/process monitoring

  5. On-going Activities • Complete current activities: • Provide the basic building blocks required by all experiments • Enhance the building blocks based on feedback from the sub-detector teams • Ensure that the documentation is appropriate • Majority of key components (prototype) should be available in 2003 • Continue to clarify/agree the interaction with external systems: • Conditions and configuration databases • Electrical distribution, JCOV, magnet control, etc. • DCS interfaces with rest of the experiment not part of JCOP; but will there be any impact?

  6. Sub-detector Interaction • Sub-detectors are now increasingly looking into controls issues • This year’s test-beam campaigns are seen as crucial • Collaboration with IT-CO contact people • Get sub-detectors using the technology in preparation for developing their final solutions • Tutorials/training for the JCOP components • Basic PVSS and FW tutorials already exist • Training courses exist for PVSS and the FW • Test technologies in an experiment environment • Refine experiment requirements • Better tailor solutions to the needs of the experiments • Validate the technology

  7. Future Activities - I • Review of DSS prototype and agree on implementation strategy and piquet • Develop and agree the maintenance concept for JCOP components and tools • Generally accepted that this should be handled by support groups • Must ensure that resources requirements are known and available • How do we maintain the required expertise? • Short-term versus long-term staff • Development versus pure maintenance • Support and maintenance for PVSS, OPC, PLCs and field buses already in place

  8. Future Activities - II • Propose strategy for configuration, operation and maintenance of large PVSS distributed systems • Scaling up PVSS project • Discussions with ETM • Security (remote access) and networking (use of technical network?) • Continue to work with companies providing common technologies to enhance them, e.g. • ETM for PVSS • CAEN • ISEG • Wiener • Installation and monitoring of DCS computers (CCSP and LCG?)

  9. Looking forward • Are there other areas where common solutions would be beneficial? • The higher in the control system the more commonality is possible • Nonetheless experiments should try to achieve as much commonality as possible even at the lower levels • As we move towards final systems the time is running out for defining new common items

  10. Major milestones for 2003 • RCS • Specification of PCB available 3rd quarter • DSS • Prototype completed and review 2nd quarter • Initial CMS system end of 3rd quarter • Initial LHCb system 4th quarter • GCS • ALICE TPC GCG completed in 2nd quarter with commissioning in 3rd/4th quarter • FW design completed in 3rd quarter • FW • Prototypes for configuration and data storage and retrieval, ISEG PS 2nd quarter • Access control, mass configuration and web access 3rd quarter • 1st version for configuration, and data storage and retrieval 4th quarter

  11. Major milestones for 2004/2005 • RCS • System available as stores item early 2004 • GCS • FW completed in 1Q2004 • Instances 2004-2006 • DSS • Initial systems for ATLAS and ALICE in 2004 • Final systems for all experiments 2006 • FW • RCS, DIP interface, improved alarm reporting, update of configuration and data storage and retrieval tools 2004 • Interface to histogramming tool 2005

  12. Resource Situation • Project resources from IT-CO and EP-ESS • Many temporary staff • Lack of continuity • Investment in training • In kind contributions from the experiments • Support and maintenance • Just keeping our heads above water • Assuming we can maintain the current level of resources • Still to be addressed: • Resources for the implementation of the 23 gas control systems • Specialised support for DSS • Long-term maintenance

  13. Summary • The more done by JCOP the easier is the task of the experiments • JCOP is one of the few, and earliest, common projects • Experiment approaches are different • But still possible to deliver common components • Resources are at best very tight • Maintenance still an issue long-term • Strategy needs to be defined

More Related