1. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Why to switch now? u existing database (db) at UIC incomplete and unlikely to be completed u a true db design (i.e. entity-relationship) is not existing and was never designed u we want structured queries in order to retrieve information on objects for assemblies s this will be almost impossible to implement in the existing db u real concern that this db project is for an undergrad student at UIC way too work u we have to pull the break now, otherwise we will not be able to have a good db during production testing and assembly

2. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Why Atlas SCT db? u solid and mature db design (v5.9) u Atlas db tasks are very similar to ours u their db design goes back to 1998 u it is developed by programmers with close contact to SCT people  Our approach u adopt Atlas design by requesting the designer file from them u get help from D0 professionals: Stu, Taka, Stan for implementation u Need contact person within Run IIb, who knows details of the detector: Eckhard v. Toerne (?) u strip the design file to the absolute necessary structures u use possibly MISWEB as Web interface for data entry and retrieval tools u The web-interfaces will be the most work to do

3. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Atlas db system architecture: u Relational db based on ORACLE 8 u Db follows client-server model: s ORACLE server in geneva s OMNIS client applications on PCs s Web client to allow access to db from any web browser s Java client to allow upload of special formatted data like labview program output etc.

4. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  The Atlas SCT db tracks components in four ways: u Item s An item record holds basic information of all SCT components s e.g. Serial number, item type, manufacturer, current location, passed test? etc. u Test s Test records are created whenever items are tested s certain test parameters are automatically checked against predefined tolerances u Assembly s Assembly record links component item to assembly item s There are automatic bookkeeping procedures, which keep the item’s location and status up to date, when it is assembled u Shipment/Tracking s Shipment records are created whenever an item is shipped/moved from one institute to another

5. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Data structures u data are organized in SQL tables, the contained data can be manipulated by operations u Several “classes” of tables: s Class 1 (in yellow): –description of item types, tests, assemblies, institutes, etc –read access by everyone –update access limited to few experts s Class 2: (in blue) –records of items, tests, assemblies, shipments, etc –each institute updates only entries it ‘owns’ s Class 3: (in green) –Is a history structure for assemblies, if a deletion is made

6. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb u Atlas SCT database works with a unique serial number for all items u This serial number is an intrinsic number within the db and does not coincide with any other serial numbers we have u part identification within the db s all items in db have internal nine-digit decimal serial number for unique identification s the first two digits are a numeric code which are assigned to each institute involved s then, there is a six digit sequential number automatically generated by the db, when the item is registered in the db for the first time s one other digit is reserved for other purposes

7. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Close-up of the Atlas entity-relationship

8. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  The item tables are the following: u Item_category: Item type category like sensor, hybrid etc u Item_description: Item type description like L0- sensor, L1-sensor etc u Items: this are the details of each item u Item_comments: comments on item u Item_images: optional gif or jpg images u Stocks: stock levels of items

9. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Of course, we are building assemblies: 20-20 stereos, 10-10 axials etc.  There are two Assembly tables: Assm_descr and Assm_items  together with the items and items_description tables they store a general description of each type of assembly, as well as records of which component items are mounted in any particular assembly  An item is ‘assembled’ in the databse when an assembly record is created linking it to a position on an assembly item. Deleting the record, ‘disassembles’ the item  Automatic procedures in ORACLE (ORACLE triggers) keep track of the location and status of assembled and disassembled items

10. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Tests  There are tables for a generic test information: u Each type of a test on an item or assembly has a short test description with a web pointer to a full specification u Every test has a test record with general details and pas/fail results. A sensor visual inspection would be recorded just in a normal test record u Raw data like C-V, I-V on sensors can be recorded in a spreadsheet (or XML-format) in a raw data record. The entire raw data record can be easily retrieved for display and analysis, but the db ignores its content u List of strip defects can be recorded as defects records associated with a test u Comments and web links can be attached u Tolerance limits and specs can be associated with any test parameter

11. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  There are also special test information tab les  The structures needed to hold parameters specific to a particular test are separated into special tables, which can be added as new tests are defined  Each special test record is associated with a generic test record, and thus with comments, web links or a list of defects

12. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Shipments:  Shipment tables keep track of items: u Ship: contains details of shipment: Carrier, data, sender etc u Ship_items: map items into shipment  Misc: u Location table: institutions u MFRS table: Manufactures/vendors u Persons: Databse users

13. Frank Lehner U Zurich Proposal to use the Atlas SCT database for Run IIb  Futher information: u SCT db welcome page: http://melb.unige.ch:3143/ http://melb.unige.ch:3143/ u http://www.hep.man.ac.uk/groups/atlas/SCTdata base/Database.html http://www.hep.man.ac.uk/groups/atlas/SCTdata base/Database.html u Atlas note ATL-INDET-2002-015  Next steps: u Request designer file from Geneva u Strip tables to a minimum necessary amount u use sensors to begin with