ACCOR PROJECT - PowerPoint Presentation

Slide1

ACCOR PROJECTStrategy for Legacy Phase Out

M.Vanden

Eynden

on behalf of

all ACCOR project members and

MCCsSlide2

Agenda

ACCOR Motivation for Legacy Phase Out

First Case :

LynxOS-PowerPC platformACCOR Strategy for Legacy Phase OutKey Objectives for LS1Conclusions

2/2/12

2

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide3

Motivation

ACCOR PROJET DEFINITION REPORT – June 2009

2/2/12

3

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide4

Motivation

Several components beyond “end-of-life”

No support from industry (no spares)

Control system evolution almost impossibleGrowing number of Operational Performance issues Lack of clear eradication policy leads toMultiplicity of solutionsOver-complexity and incompatibilities for renovation

CO resources locked in adaptative and corrective maintenance

Managing “end-of-life” is NOT a straightforward processCorporate approach neededAdditional ACCOR complexity

Technology phase out goes together with new responsibility model at the front-end level

2/2/12

4

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide5

First Case

PowerPC Microprocessor Technology

No commercial contract anymore

Support limited to repairs only (if possible …)Out of performance for new software solutions (CMW, Inca, more users, …)Strategic decision to move towards Intel processors as common choice for cPCI, PICMG1.3 and

VMEBusLynxOSOut of date, no industry support

Potential security issuesPrevent usage of modern software technologies (CMW, …)Strategic decision to move towards Linux as THE multi-platform OS for

cPCI, PICMG1.3 and VMEBusRequires duplication of development and support for FESA, CMW, generic FESA classes, Device drivers,

etc

2/2/12

5

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide6

Strategy for Phase out

Communicate the criticality of the situation

Assess the impact inside CO

Resources and planning for procurement of new solutionImpact on interfaces and other SW and HW componentsAssess the operational impactNumber of systems concerned

Accelerators and Equipment groups concerned (induced effort, resources)Define what “end-of-life” meansEnd of BE-CO operational support (no intervention in case of problem)?

Removal of operational equipment?End of BE-CO procurement only?Propose and explain alternate (new) solution or migration path

In case of agreement -> publish decision and plansIn case of disagreementRe-asses alternate paths

R

e

-define roles and responsibilities

Re-iterate potential operation problems and their consequences (risk)

2/2/12

6

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide7

Strategy … but In Practice

BE-CO has to be more than Pro-active (MCCs)

The devil is in the

details (“travail de fourmis”)Identify ALL dependencies (“spaghetti effect”)Do not

underestimate priority clashes with other projects Make compromises and offer alternate paths

Write strategy and objectives formallyGet agreement with partners

2/2/12

7

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide8

Strategy

in a Nutshell

2/2/12

8

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide9

Key Objectives for LS1

LynxOS

-PPC platform eradication during LS1 for the following machines

LHC (> 200 FECs)Move towards SLC6 64 bits (CO must be ready !)BI : 125 FECs + 17 FESA Classes

BT : 7 FECs + SPS (6 FECs)CO : 5 FECsRF : 56 FECsInterlocks : 24 to 48 FECs

LINAC3-LEIR ChainOASIS Timing

System (TG8 eradication)Non-CO FECs (about 20-25)REXComplete

re-engineering

2/2/12

9

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide10

Key Objectives for LS1

Major Implications of CO

Procurement process for

VMEBUs MEN SBCsELMA CratesHW modulesGood synchronization with standard BE-CO HW modules roadmap (more on this later)

Linux 64 Bits kernelLinux Device driversFESA 3.0 by MID-2012 (we are trying hard …

)Timing renovation (eradication of TG8s)Generic FESA classes

Data Management tools for CCDB, Layout, Asset, CMM, including the migration to MTFExtensive Installation coordination and Planning (> 400 FECs)

2/2/12

10

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide11

Key Objectives for LS1

2/2/12

11

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide12

Key Objectives for LS1

Standard BE-CO “hardware Catalog” roadmap

Severe operation problem in 2011

Mandatory step before migration towards MTFOther “time bombs” regarding spares, responsibilities, test beds, etc.

Complete cleaning done by Christine, Claude, Erik

4 categoriesModules transferred to Eq.groups (+/- 25)Modules which are obsolete and not used

Modules which are supported and up-to-dateModules which are supported but under replacement (FMC, …)

2/2/12

12

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide13

Key Objectives for LS1

2/2/12

13

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide14

Many other things for LS1

Phasing out of

Elonex

platform and replacement by Kontron PICMG1.3 LHC : about 250 machines

Power convertersCryogenicsBeam instrumentation

Beam TransferEtc.Big KONTRON order launched 12/2011 (>400 systems)

Many other objectivesPS Continuous TransferAD High Tension PlatformOASIS (VXI replacement)

Etc

.

2/2/12

14

ACCOR PROJECT – BE-CO-TC – M.Vanden EyndenSlide15

Conclusion

Going for a formal (EDMS) Legacy Phase Out

Strategy

by Accelerator is now a priority for ACCOR (in addition to all the other initiatives) LS1 is a unique opportunity for ACCORImpact on ALL CO sections and key projects (Inca,

FESA, etc.)Very positive collaboration and agreement with

Eq.Groups

Machine Controls Coordinators : Thank you !

Key objective for LS1 :

LynxOS

-PPC phased out on LHC, REX, LINAC3 and LEIR

We are almost

there …

LHC 100%

LINAC3-LEIR :

see

presentation

of Marine

REX :

see

presentation

of Frank

2/2/12

15

ACCOR PROJECT – BE-CO-TC – M.Vanden Eynden