15 January 2003 N.P. Hessey, NIKHEF 1

SCT Part Numbers and DB

Part numbers: 2022028mnnnnnn 20: ATLAS 22: SCT 028: NIKHEF (033 for RAL) m:

=0: Scratch parts, prototypes, tests, mistakes…

=1: Sandra for modules etc (NIKHEF) Debbie for Endcap mech. (RAL)

=2: Patrick for discs etc. (NIKHEF) Andy Nichols for Barrel mechs. (RAL)

Use as primary key in all DB’s Seems OK to me

15 January 2003 N.P. Hessey, NIKHEF 2

DB

Purpose Store test results Parts inventory Shipping/location record Component history

Hold “actual items” Not drawings, does not alter EDMS/CDD use But an item can point to relevant CDD/EDMS docs

Central DB? Didn’t happen

Could not agree ATLAS-wideDid not find person/institute to do it

Geneva “SCT Production DB” is really“SCT Module Production DB”

Didier would put discs and wheels in at a simple level Is reluctant, would be difficult to get all we need

15 January 2003 N.P. Hessey, NIKHEF 3

Alternatives to Geneva DB

Local DB’s NIKHEF + RAL + Liverpool…

Easy for NIKHEF to implement Muon model: 3 DB’s

» Stock Inventory DB +» Items for ATLAS with test results etc. +» Reject items

Presumably RAL and Liverpool can also do that? Problems:

Triplicate set-up overheadsRAL needs access to NIKHEF DB etc.Disc created at NIKHEF then goes to RAL

NIKHEF loses track of it RAL needs original data And repeat problem when moving to Liverpool, SR, ATLAS

Pit

Information distributed over many (incoherent) DB’s

15 January 2003 N.P. Hessey, NIKHEF 4

Or can we improve on this?

E.g. NIKHEF makes a central “Disc Production DB” Would RAL and Liverpool prefer that? What about Cylinders, Wings, services, etc.? Can we arrange easy/secure access for RAL,

Liverpool… Is MS Access enough or do we need Oracle… Linux access? E.g. wheel DAQ is Linux

Default is NIKHEF will make DB like Muons Fast to start Easy for us to adjust with experience Later can shift to a central DB