CMS Database Issues - PowerPoint PPT Presentation

About This Presentation
Title:

CMS Database Issues

Description:

Derek Barge. ROD INTEGRATION. Aachen. Karlsruhe. Strasbourg. Zurich ... CMS Database Issues-Derek Barge. DOE review, January 20, 2004. Keeping Track of Things ... – PowerPoint PPT presentation

Number of Views:44
Avg rating:3.0/5.0
Slides: 16
Provided by: affo
Category:
Tags: cms | barge | database | issues

less

Transcript and Presenter's Notes

Title: CMS Database Issues


1
CMS Database Issues
  • Derek Barge

2
(No Transcript)
3
Production Overview
Sensors
Hybrids
Production Overview
  • Quick Overview of Production Process
  • Hybrids (2755 TOB 5 types, 500-2613 TEC 3
    types)
  • 1. Receiving / Visual Inspection / Hybrid
    Assembly
  • 2. Testing Bonding Thermal Testing Module
    Assembly
  • Sensors (5510 TOB 2 types, 1000-5226 TEC 4
    types)
  • 1. Receiving / Probing (Special)
  • 2. Module Assembly
  • Modules (2755 TOB 6 types, 500-2613 TEC 3
    types)
  • 1. Assembly (using hybrids sensors)
  • 2. Wire-bonding
  • 3. Testing
  • Rods ( 460 - 24 types)
  • 1. Assembly / Testing / ? / Shipping

Slide 3
-Derek Barge
DOE review, January 20, 2004
4
Keeping Track of Things
Sensors
Hybrids
Keeping Track of Things
  • What Do we need to keep track of?
  • For Hybrids, Sensors, Modules Rods, we need to
    know
  • - Where is it? (What Test Center? UCSB, CERN,
    etc.)
  • - What Type is it? (Module or Hybrid? TEC or TOB?
    Single or Stereo?)
  • - How is it related to other objects?
  • - Does it contain any other parts? What are
    their serial numbers?
  • - Is it a part in another container? What is the
    containers serial number?
  • - Has it been Wire-bonded? (hybrids modules
    only)
  • - What channels were NOT bonded successfully?
  • - Has it been tested?
  • - What channels were faulty and why? Did it Pass
    or Fail?
  • - Is it ready for the next production stage?
  • - History Shipping (When was it Made? Bonded?
    Tested? Shipped?)

Slide 4
-Derek Barge
DOE review, January 20, 2004
5
Data Management
Sensors
Hybrids
Data Management
  • Need tools to track parts record information at
    different stages of production and centers
  • System must handle
  • 13,480 Total Objects of 46 types
  • Requirements
  • - Must be Reliable
  • - Must be Adaptable, needs to quickly
    accommodate changes
  • - Should be centralized
  • - Should be Internet based for accessibility
  • - Must be secure
  • - Should be easy to use
  • - Should be as fast as possible
  • What is the CMS collaborations solution?

Slide 5
-Derek Barge
DOE review, January 20, 2004
6
TrackerDB
Sensors
Hybrids
TrackerDB
  • Oracle (SQL) database for tracking CMS production
  • Relational Database format, data stored in
    tables
  • - Center - Sensor Data (ST, QTC)
  • - Bonding Data - Gantry Assembly Measurements
  • - Object Assembly - History Shipping
  • Data is uploaded and stored for later reference
  • - Uploading of Module Assembly Wire-bonding
    data almost fully automated, Hybrid data will be
    automated this month
  • Queries can be written to get data for
  • - A Specific Part (Example time history for a
    particular hybrid)
  • - All parts meeting certain criteria (Example
    all modules at UCSB that have been assembled and
    not wire-bonded)

Slide 6
-Derek Barge
DOE review, January 20, 2004
7
DB Problems
Sensors
Hybrids
DB Problems
  • Although the TrackerDB itself is reliable, and
    has the potential to meet our needs,
  • All the interface tools we need either dont
    exist or work
  • - BigBrowser is slow cant track parts through
    their containers
  • - Other interfaces track modules only or sensors
    only
  • - Interface servers go down (PISA server summer
    03)
  • Data Problems (being resolved)
  • - Sensors with incorrect or missing data
  • - Hybrids received with missing bonding data
  • Testing Tables not developed
  • - Hybrid Testing Tables not ready until DEC 2003
  • - Module testing data structures not sufficient
    for UCSB

Slide 7
-Derek Barge
DOE review, January 20, 2004
8
Solution
Sensors 2
Sensors
Hybrids
Solution
  • Combine TrackerDB local UCSB DB
  • Maximize mileage from Tracker DB, rely on it for
  • - Sensor Data (unavoidable)
  • - Bonding Data (also kept locally)
  • - Gantry Data (also kept locally)
  • - Relating Object serial numbers (also kept
    locally)
  • - Object Histories Shipping (unavoidable)
  • Local UCSB DB System handles TrackerDB
    shortfalls
  • - Hybrid Testing Data (migrating to DB JAN 2004)
  • - Module Testing Data
  • UCSB web interface designed to
  • - Query TrackerDB display results
  • - Interface to local testing data

Slide 8
-Derek Barge
DOE review, January 20, 2004
9
UCSB Interface Works
DB Problems
Sensors
Hybrids
UCSB Interface Working
  • Currently Relying on UCSB Interface for
  • Inventory for Hybrids, Sensors Modules, can
    sort by
  • - , Center, Type, Bonding Status, Production
    Stage (container?)
  • Sensor Data
  • - Position of Faulty Strips (CAC, IDIEL, ISTRIP,
    RPOLY)
  • - Depletion Voltage (used to pair sensors for
    module production)
  • - Current(Voltage) curve (compared to module
    I(V) in module testing)
  • All Hybrid Module Electrical Testing Data
  • Tracking incoming outgoing shipments
  • Frame inventory (otherwise untracked)

Slide 9
-Derek Barge
DOE review, January 20, 2004
10
UCSB Interface - Main
11
UCSB Sensor Inventory
12
Sensor 30210314308203
13
Hybrid Results
Sensors
Hybrids
Processed Hybrids
  • What have we done so far?
  • Hybrids (199 processed so far)
  • - 160 at UCSB (All wire-bonded)
  • - 126 TOB_P_4U (52 in modules)
  • - 7 TOB_P_4D (3 in modules)
  • - 7 TOB_P_6U (6 in modules)
  • - 6 TOB_S_4U (0 in modules)
  • - 8 TOB_S_4D (3 in modules)
  • - 6 TEC (4 in modules)
  • - 11 sent to Fermilab for module production
  • - 16 in module at FERMILAB
  • - 10 in modules at CERN
  • - 1 in module at STRASBOURG
  • - 1 in module in TORINO

Slide 13
-Derek Barge
DOE review, January 20, 2004
14
Automation
Sensors
Hybrids
Automation
  • Tasks previously done by technicians now done
    automatically
  • Example Module Checklist
  • - Paper Checklist (9 min / module)
  • - find what hybrid, near sensor, and far sensor
    are in the module
  • - lookup channel faults and I(V) curves for both
    sensors (PIZA interface)
  • - manually add sensor I(V) curves
  • - Automated Checklist ( 2 min )
  • - Enter Module serial number and wait
  • Efficiency improvement of at least 7 min /
    module, 1.75 hours / day _at_ 15 modules / day
  • Accuracy improved, no data entry errors

Slide 14
-Derek Barge
DOE review, January 20, 2004
15
Works in Progress
Sensors
Hybrids
Whats Left?
  • Still need systems to manage
  • Module Thermal Testing Data
  • Rod Assembly Testing Data
  • Also Distributed to Fermilab
  • Already using UCSB tools for Module checklist
    Sensor Data
  • Still need inventory tools

Slide 15
-Derek Barge
DOE review, January 20, 2004
Write a Comment
User Comments (0)
About PowerShow.com