Upload
dewei
View
42
Download
0
Embed Size (px)
DESCRIPTION
LHC Hardware Commissioning Review Contribution ID: 20 – Quality assurance and documentation of results Database Management for the ELQA Activities A case study Wednesday, 11 May 2005 Davide Bozzini, AT-MEL-EM Contribution: A. Dafinei, L. Furman, R. Saban, F.R. Mateos, E. Barbero. Outline - PowerPoint PPT Presentation
Citation preview
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
1
LHC Hardware Commissioning ReviewContribution ID: 20 – Quality assurance and documentation of results
Database Management for the ELQA Activities A case study
Wednesday, 11 May 2005
Davide Bozzini, AT-MEL-EM
Contribution: A. Dafinei, L. Furman, R. Saban, F.R. Mateos, E. Barbero
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
2
Outline
– Why do we have an ELQA database and what does it contain
– Structure of ELQA database activities
– Who are ELQA data's suppliers – clients – neighbours
– What data are available
– How data will be accessible
– MTF for Hardware Commissioning and ELQA database
– Selection of data to be stored in HC MTF
– Communication between ELQA and HC coordination team
– Conclusion
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
3
Why do we have a ELQA database and what it contains
Why– To store and manage the overall reference and qualification data for the
correct execution of the ELQA activities
– To gather online the data produced by the data acquisition systems driven by LabView software
– To flexibly and rapidly modify the structure based on ELQA needs
– To be able to rapidly develop applications for data analysis
– To be independent from other existing data bases
What does it contain– Assembly and electrical schematic parameters generated from the LHC
reference database (details on the next slide)
– Manufacturing and qualification data of some electrical components
– Data acquired during the machine assembly and hardware commissioning
– Data generated by non conformities
– The on line status of ELQA crews activities
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
4
Electrical schematic parameters generated form the LHC reference database
Tables for the automatic verification of the ARC corrector circuitsHALFCELL
PLANE_NAME
PLANE_POSITION ASSEMBLY WIRE PORT_A MAGNET
_TYPE POSITION BEAM VOLTAGE_TAP
LAYOUT_VERSION
16R7 IC1516R7 20648243,1 15 6.402
16R7 IC1516R7 20648243,1 16 6.402
16R7 IC1516R7 20648243,1 18 6.402
16R7 IC16R7_2 20663903,1 LBARA.16R7 9 US MCS A INTERNAL MBA_EE931 6.402
16R7 IC16R7_2 20663903,1 LBARA.16R7 19 US MCS A INTERNAL MBA_EE931 6.402
More than 100.000 entries
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
5
Structure of ELQA database activities
ELQA_DB is an Oracle application on cern.devdb
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
6
Who are ELQA data's suppliers – clients – neighbours
Suppliers– The ELQA systems and activities coordinators
– The LHC Reference DB
Clients (who need data for a technical reason)– Quench protection experts (inductance)
– Power converter experts (transfer function, insulation, polarities)
– Hardware Commissioning coordination team
Neighbours (who want to receive data for information only)– EDMS, MTF
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
7
What data are available
Test applied to Method Assembly
HC warm
HC cool-down
HC cold
Electrical insulation
segment - ground DCV supply
segment - segment I leakage
segment – groundDCV supply
segment – segment
Capacity Circuit - groundDCV
Measurement of C
Continuitysegments DCA supply
Circuit Closed loop
Polaritysegments DCA supply
Circuit Voltage drop via V_taps
Instrumentation Current lead V_taps
DCA supply
Voltage drop via V_taps
Diode polarity MB,MQ diodesPolarity
Turn on voltage
Transfer function
Circuit Z(f)
To ground Z(f)
List of ELQA tests for the electrical qualification of superconducting circuits during assembly and hardware commissioning
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
8
How data will be accessible
Suppliers– Read and write access to all data. For people not members of the ELQA
team a password will be provided
Clients (who need data for a technical reason)– All data and if requested direct access to the ELQA _DB
• Quench protection experts
• Power converters experts
• HC coordination team
Neighbours (who want to receive data for information only)– Activities follow-up and general parameters will be available via dedicated
web interfaces (read only)
– Upon request a test report on electronic format can be automatically generated and dispatched to a recipient list
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
9
Formats of data (1)
Direct query to ELQA_DB – Ex: Benthic Software, Golden32 + login
Specific software interface tools for data analysis – Ex 1: follow-up of arc assembly polarity checks (see next slide)
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
10
Formats of data (2)
Direct query to ELQA_DB – Ex: Benthic Software, Golden32 + login
Specific software interface tools for data analysis – Ex 1: follow-up of arc assembly polarity checks
– Ex 2: Line N segment manufacturing http://pcat0129.cern.ch\status.htm
Automatically generated test reports and non-conformity reports – html, excel, jpg, pdf formats
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
11
MTF for Hardware Commissioning and ELQA database (1)
SECTOR 7-8Sector
D1Q3Q2Q1.L8
Region Equipment group
Superconducti
ng Circuits
Equipment / Activity
RCBXH1.L8.UA83
ELQA
Quench Protection SystemPower Converter
……………………….
MTF structure for the HC of the superconducting circuits
The question: What data of ELQA_DB need to stored in the MTF?
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
12
MTF for Hardware Commissioning and ELQA database (2)
Aims of the HC MTF– HC MTF is not a copy of the ELQA_DB
– To make available only the significant information to carry out the HC
– To track the ELQA activities
– To allow the traceability of non conformities documentation
The ELQA team will provide to the HC coordination the followings:– Summary and status reports of the ELQA activities
• Summary reports containing the test results
• Status reports to track what goes on with a given circuit or element
– Measured electrical parameters• Inductance, resistance, insulation to ground,….
– Non conformity reports generated during the ELQA activities• Activation of a red flag
• Documentation of the non conformity
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
13
MTF for Hardware Commissioning and ELQA database (3)
From the practical point of view– The ELQA team will provide the data in electronic format
– Upload of the files in HC MTF will be done by HC coordination team
Some additional remarks– The ELQA team will not use MTF as reference tool for their activities.
The ELQA team will rely on the ELQA_DB that contains more information and that are updated regularly every 3-5 hours
– The ELQA team will need to know the status of other activities. MTF contains the status of all individual system test and activities
– The updating frequency of HC MTF is a key point for a profitable and optimized chaining and follow up of activities
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
14
Communication between ELQA and HC coordination team (1)
ELQA team will organize:– Daily meetings for the ELQA activities follow up
– “Troubleshooting” meetings to solve technical non conformities
Share of information with HC coordination team– ELQA team will report on a daily basis to the HC team
• The status of the ELQA activities (delays, conflicts, unforeseen problems,..)
• The status of the non conformities and the actions taken to come to a decision on how to proceed
LHC
Har
dwar
e C
omm
issi
onin
g R
evie
w 1
1-13
May
200
5, C
ER
N, 1
211
Gen
eva
23
15
Conclusion
Databases– ELQA_DB is a tool designed to cover the ELQA activities from assembly of
components to the machine operation
– The HC is a short term client of the ELQA_DB database
– All the information required for the HC MTF will be provided Hardware commissioning MTF
– MTF cannot be the tool for managing the sequencing of activities
– Work will slow down mainly due to non conformities. MTF has shown evident limits to handle non conformities.
General– Communication via MTF and mailing is not enough. Meetings are required
on a regular basis
– The decision makers structure for the non conformities has to be established according to quality assurance rules