R2E R2E-EPC-Database General

Design & Operation Responsibles

Database Overview

Database Architecture

Database Design

Database Usage

Production Contract & Contact History

Involved Peoples

[an error occurred while processing this directive]	→ Project Leader & Designer	[BE-CO-DA]
[an error occurred while processing this directive]	→ CERN Database Section Leader	[BE-CO-DA]

Michel GEORGES	→ R2E-Database Linkman	[Converter]
Yves THUREL	→ R2E-EPC Leader	[Converter]
[an error occurred while processing this directive]	→ R2E test Expert	[EN-STI]
Markus BRUGGER	→ R2E-CERN Leader	[EN-STI]

Database Overview

This database intends to collect + trace + manage all components involved in the production of radiation-tolerant units to be used at CERN in the R2E project context. This database will be used in the R2E-EPC context first, and can be developped for CERN larger community if successful.

	2012				2013				2014
	Q₁	Q₂	Q₃	Q₄	Q₁	Q₂	Q₃	Q₄	Q₁	Q₂	Q₃	Q₄
LHC Status	Operation				L.S.1				Operation
Phases	Specifications		Design		Protoype	Production
Functionalities	NA				Component Level - Import radiation component test results - Visualize radiation individual or group test results		Integration Multi-Database Links Cpt <=> card Card <=> Item Item <=> area		Exploitation Multi-Database Links, tools

Projective Planning

Database Architecture

The database focus on component management, even if it could be possible to use its mechanism to also trace some full cards test results.

The database should fit with the approach, which consists in testing some units from a given batch of components, being then sacrified, to deduce the whole batch behaviour under radiation exposure.

The database should be able to take in account at least 3 different types of tests for radiation approval process (Total ionizing dose, Singe Event, Displacement Damage), and will have to cope with around 200 different types of components (transistor, optocouplers...).

The database should be able to manage component stock quantities, since repair maintenance will rely on component availability, and in some cases, remaining parts could be use for other new projects.

Detailed Component Test Procedure Detailed Component Test Procedure

Overview of the database - data flux .vsd

Name	Value	Unit	Comments
Record_Set	ID	N.A.	Set of records (points) for a final multi-points curve
X1-value	Numeric	[particles/cm²]	Irradiation main particles fluence, in non-mixed field case.
X2-value	Numeric	[Neutrons 1MeV.eq/cm²]	Displacement Damage axis.
X3-value	Numeric	[Hadrons >20MeV.eq/cm²]	Heavy Ions axis.
Y1-value	Numeric	[value?]	Observation (gain, leakage...).
Flag	ID	N.A.	Single Events, S.E.L., S.E.T. ... <=> database.

Remarks:
- These different several axis allow to describe irradiation stress, indicating for example the number of protons received, but also the according dose. It is not mandatory that the x-axis are proportional in between, even if more likely the case.
- Axis are to be used depending on the knowledge of the irradiation. Equivalent axis like particles1MeV.eq/cm² and particles >20MeV.eq/cm² can be used in case of Mixed-Field (too many particles), but also in case of known particles (test with heavy ions), to give more direct information.

Component Component

Batch Batch

Database Usage

Some example of dedicated uses of the database are described below.

User	Action / Usage
User	R/W type	Purpose	Keywords	Comment
Radiation Tester	Write	Rad. Tester will enter radiation test data (results, conditions) with all maximum info already proposed/pre-filled.	Handy, multi data inport (xls, manual), clear, pre-filled, guided, interface, copy, clone.	A lot of effort is required to obtain good definition of important test data to be filled. Data results must be easy to enter (xls import, possibility to manually enter it...)
Designer	Read	Designer will read data about components to chosse correct one.	Clear, export / display vs differents x,y cases, flexibility, interpretation.	This user will want to access quickly to information, but should not be biased by hidden test important settings. Quick but not biased browsing
Repair Engineer	Read	Repair Engineer will collect component information, and test result to understand failures.	Clear, precise, details, multi database links, multi database export.	This user acts like a designer but will certainly be more precise regarding to understand some potential issue. He will also try to link some potential sensitive components with installed material.

Production Contract & Contact History

Developped	CERN
	2012-2013
Manufactured	CERN

Involved Peoples

Database Overview

Database Architecture

Database Design

Database Layout Database Layout

Database Units Definition & Terms Database Units Definition & Terms

Test Test

Result Point (Record) Result Point (Record)

Component Component

Batch Batch

Database Usage

Production Contract & Contact History