1. Barrel Module Database Presented at the SCT Barrel PAR 15 th May 2003 Dave Robinson, Cambridge Introduction - Database access - Barrel module data User Interfaces - Examples: - Uploading ASIC-hybrid assembly data - Retrieving electrical characterisations Upload Status by Barrel Clusters - Database Actions - Schedule Summary

2. Oracle 9i DB Sun Ultra SPARC Web Interface Java Applications SCT Database Overview of Access Channels Geneva University Barrel Community http: read/write/update/delete JDBC: insert Data Retrieval And Display (GUI) Data Uploads (GUI) Geneva University: System maintenance, administration, table development, web interface, read/write channels. Barrel Community: User Interfaces for data upload and retrieval/display. Master DB JDBC: read

3. http://wacap.unige.ch:3146/phyprdwww/sctprd/welcome.html - Main Geneva database website. Read/write web interface and general database documentationhttp://wacap.unige.ch:3146/phyprdwww/sctprd/welcome.html http://www.hep.phy.cam.ac.uk/~silicon/jBarrels.html - Barrel specific upload utilities – download, installation instructions and user guide. (item registration, assemblies, metrology, datasheets, shipments, profiles)http://www.hep.phy.cam.ac.uk/~silicon/jBarrels.html http://www.hep.phy.cam.ac.uk/~silicon/jSCTDAQ.html - SCTDAQ electrical characterisation uploads, used also for endcap module/hybrid uploads. Download, installation instructions and user guide.http://www.hep.phy.cam.ac.uk/~silicon/jSCTDAQ.html http://www.hep.phy.cam.ac.uk/~silicn/jSCTDB.html - General data retrieval and display GUI for all SCT components. Download, installation instructions and user guide.http://www.hep.phy.cam.ac.uk/~silicn/jSCTDB.html Links to Database and User Interfaces The data upload and retrieval/display utilities are all standalone java applications (graphical user interfaces) that must be downloaded from the links below. They run on Windows, Linux and MacOSX.

4. Barrel Data ORACLE tables are implemented for the following data for barrel modules and their components: Item status eg current location, assembly status etc Shipments between institutes eg sender, receiver, date, items etc Assembly Information eg components, positions, assembly dates Dis-Assembly Information eg chip replacements etc XY and Z metrology Datasheets - baseboards - sensor-baseboards - passive hybrids - populated hybrids - modules Test Data - module/hybrid electrical data (SCTDAQ full electrical characterisations) - sensor data, eg IVs, defects, depletion etc - ASIC and ASIC wafer data, eg cap corr factors etc Given the module serial number, return its location, assembly details, shipment history, test history, test data for the module and any of its components.

5. Data Upload/Retrieval Utilities Standalone GUI applications written in java Run on Windows, Linux and MacOSX Flexible – upload one item of data or upload an entire backlog in one go Extensive interactions with database before upload (verification, authorisation etc). Tries to prevent you making a mistake. Upload utilities available for: - Item Registration - Shipments (sending and receiving) - Assembly Information - Metrology Data - Datasheets - Electrical (SCTDAQ) test data - Profiles (soon...) Data Retrieval/Display available for all the above plus all module subcomponents The utilities do not have direct write access to the database. Instead they generate one or many ‘upload files’ and then invoke a Geneva- supplied java upload utility to upload them all. Example 1: Upload ASIC-hybrid assembly Example 2: Retrieve/Display module SCTDAQ data

6. Module Sensor-Baseboard Baseboard Sensor ASIC Hybrid Sensor Passive Hybrid ASIC Barrel Module Assembly Tree Note: to assemble a device in the database from its various components, the serial number of the device and all the components must be registered and shipped to the same location. Eg before an institute can assemble a hybrid, it must receive a shipment (or shipments) containing all 12 ASICs and the unpopulated hybrid.

7. The institute that assembles ASICs to hybrids maintains an excel spreadsheet containing all data relevant to the assembly of that hybrid. Within this spreadsheet is information on which ASIC is attached at which position. ASIC labelled by: “TestSite”-”Lot Number”-”Wafer Number”-”Chip site on wafer” The upload application interprets this string and looks up the appropriate 14-digit serial number from the database. Eg RAL-Z39992-W05-X8-Y0 or RAL-Z3992-W05-2

8. 1.Select the ‘Assemblies’ tab 2. Select which device you wish to assemble from ‘Sensor-Baseboards’, ‘Hybrids’ or ‘Modules’ 3.Confirm institute and cluster (already set by default according to your preferences) 4.Click on ‘New...’ User Interface Example: ASIC to Hybrid Assembly

9. 5.Enter range of serial numbers corresponding to the assembled hybrids All valid assemblies within the serial number range are listed as a tree. Valid assemblies are defined as: All components registered in database All components located at your institute Components have not been assembled before Excel datasheet(s) present on your file system

10. Example 2: Retrieving SCTDAQ Data Eg Direct comparison in spreadsheet of any test parameter measured within and between different institutes Data retrieval/display GUI presents data as spreadsheets, web reports, images, raw data views etc.

11. ‘Full Data’ button creates a web report containing all data from that test

12. ‘All Tests’ button creates a web report of all tests on a module. Will soon be expanded to include links to non-SCTDAQ data (eg module metrology, sensor characteristics etc)

13. Upload Status by Barrel SCT Clusters November 02: ORACLE tables implemented for SCTDAQ December 02: Proposal by barrel community for serial number conventions Feb 03: ORACLE tables implemented for barrel XY and Z metrology Mar 03: Serial number conventions approved in barrel meeting during SCT week May 03: ORACLE tables implemented for datasheet uploads May 03: All necessary tables and upload utilities now available Barrel module production started before the production database became available: Timetable for database development work Barrel clusters therefore implemented their own bookkeeping and web reporting utilities during the first phase of production. Upload of data backlog and routine database interactions commence from May 03.

14. Database Actions by each Cluster Sensor-Baseboard Assembly Receive Sensors Receive bmBB Hybrid Assembly Receive Hybrid Receive ASICs Module Assembly Send bmSB Datasheet Assembly Datasheet Assembly SCTDAQ Datasheet Assembly SCTDAQ XY Metrology Z Metrology QA Institute SCTDAQ Macro Assembly SCTDAQ Send bmHASIC Receive bmHASIC Receive bmSB Send bmMODULE Receive bmMODULE Assembly Baseboard QC Sensor QC Datasheet Sensor Data ASIC QC Hybrid QC Send bmBB Send Sensors Receive Sensors Uploads Shipments

15. Starting to use the Database: Steps for each Cluster Register all serial numbers Upload backlog of all test data so far (once serial numbers are registered, test data can be uploaded at any time from any location) Establish shipment route to ensure module assembly information is registered in full (to assemble a device, the device and all its components must be located at the same institute, and this requirement imposes a strict ‘shipment route’ of components around the cluster) Establish fixed routine of shipments/uploads for every institute in cluster These actions are already underway by the UK-B cluster. The database and user interfaces have now been extensively debugged/exercised using UK-B data.

16. Summary Schedule of database development has meant that some clusters have a significant backlog of data. This has not been a problem so far, because their local bookkeeping/database systems are web-accessible ORACLE tables for SCT barrel module production are now fully established Interfaces to the database are available now to simplify and automate the upload and retrieval of data, including the upload of any backlogs. UK-B cluster now using the database routinely with uploads of some data backlogs ~100% All other clusters are scheduled to start using the database routinely from May 03 onwards. We are in good shape to start exploiting the SCT production database