1 / 13

Development of AB Standard for Front End Equipment Software: Phased Approach and Objectives

The AB project initiated by AB/CO aims to address the diversity in front end equipment software while facilitating a seamless transition to the LHC era. The project encompasses three phases, including the establishment of a development standard by November 2003, deployment monitoring during the PS and SPS shutdown, and the operational launch of the AB standard by 2004. Key objectives include creating a development framework for front-end equipment integration, providing legacy software migration guidelines, and ensuring compliance across all involved equipment groups.

bin
Télécharger la présentation

Development of AB Standard for Front End Equipment Software: Phased Approach and Objectives

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. FECOMSA Overview • AB project triggered by AB/CO to: • Overcome the current diversity in AB front end equipment software. • Pave the way towards LHC era for efficient and coherent development, diagnostics and maintenance in this area AB/BDI TB - 16.04.2004

  2. We’ll concentrate on this today… Overview • This project will consist in 3 main phases: • Phase 1:Build version 1 of the standard for November 2003 • Phase 2: Start and monitor its deployment in PS and SPS during 2003-04 shut-down and organize its long term ‘active’ maintenance. • Phase 3: 2004 Start-up: Deliver it as the AB standard for front end servers development AB/BDI TB - 16.04.2004

  3. Objectives • Provide for Q4 2003 the AB standard for the development, test and operational integration of front end equipment software. • This standard will take the form of a development framework suitable for deployment in the AB complex including all the front end common functionalities. • It will propose guidelines for legacy software migration AB/BDI TB - 16.04.2004

  4. The Joined Core Team AB/BDI TB - 16.04.2004 [*] Project Leader

  5. The SCOPE (Key Points) • Included • The expert applications necessary to develop and diagnose the servers • VME/LynxOS and CPCI/Linux with priority to PPC/LynxOS for phase 1. • The entire AB machine complex with priority to the LHC injectors for phase 1. • All AB equipment groups and AB/CO. AB/BDI TB - 16.04.2004

  6. The SCOPE (Key Points) • Excluded (we obviously have to check compliance and compatibility on both sides but we will not interfere in each others developments) • Operation Application and Middle Tier. • Low-level Communication, I.e. libraries for GPIB, MIL1553, VME access… • Machine operation platforms/OS selection and deployment. AB/BDI TB - 16.04.2004

  7. Main Milestones • 10/04: Mandate approved • 30/05: Proposed framework functionality assessed by future testers and AB/CO sections/projects involvement agreed • 30/07: Working prototype implementing PS and current SPS timing available • 30/09: Architecture published and beta version functionality assessed by testers. • 01/11: Version 1 documented and delivered with guidelines for migration. FEComSA WG created and mandated. AB/BDI TB - 16.04.2004

  8. Consequences for BDI • Priority developments for this run: • TT40 Instrumentation • PS Orbit System Commissioning • EA N&W Renovation Program • LHC Urgent Prototypes AB/BDI TB - 16.04.2004

  9. Consequences for BDI • Postponed till 2004: • SPS Upgrade towards multi cycling and LynxOS 3.1) (MOPOS upgrade, OS9 elimination…) • ISOLDE instrumentation upgrade • EAE instrumentation software • CTF3 instrumentation • TT40 Travellers AB/BDI TB - 16.04.2004

  10. Traveller (ex: BTVI) A Screen A Camera A Tank A Motor A Support AB/BDI TB - 16.04.2004

  11. Traveller Define the ABS and extended equipment codes ‘A’ for Assembly Equipment Code • This ABS code could be BTVI.A01 • A Tank (BTVI.001) • A Support (BTVI.002) • A Screen (BTV.001) • A Motor (BMOT.003) • A Camera (BCAM.002) AB/BDI TB - 16.04.2004

  12. TravellerDefine a traveller for each part • Each screen has to be identified by its LHC Part Number • HCBTV__001-AA000001 • Define all important information to store and EST will build the traveller (Screen size,optical properties…) Supplier Code Sequential Number AB/BDI TB - 16.04.2004

  13. Traveller:Fill them during Production • Fill the item travellers during production • Fill the ABS traveller during installation • A machine slot will be attributed to a BTVI assembly • Items (1 motor, one tank…) will be linked to an assembly (HCBTVI_A01.ZZ000004) • This assembly will be linked to the slot. AB/BDI TB - 16.04.2004

More Related