Database(s) in TM

Thursday 3 Dec 2020, 15:00 → 16:00 Europe/Zurich

Franco Julio Mangiarotti (CERN), Matthias Bonora (CERN)

1 Database in SM18

Speaker: Ioannis Koukovinis Platias (CERN)

Database in SM18.pdf

Database in SM18.pptx

- Carpenter:

  - Web interface + Database

  - around 40 tables, >380k results stored

  - Quality Assurance and Quality Control tool

    - Test progress tracking & communication

    - different levels of authorisation

    - reporting, Data storage, and data fetching from DAQ

- Typical Flow

  - Registration of Assets, Assemblies,

  - Setup of Assemblies

  - Test plan

  - Progress report during tests

    - in future with more statistics

 

- 2 Versions of Carpenter

  - V1 is currently in use.

    - Complexity outgrew its technology

  - V2 will replace V1, in development now, but used internally (soon to be released for everyone)

    - Based on Frameworks and standardisation -> better to maintain

    - System is very flexible, new Requirements can be added easily (e.g Registering and tracking of DAQ systems)

2 Database for MM

Speaker: Eleni Tournaki (CERN)

MMDB_ETournaki_04_sf.pdf

MMDB_ETournaki_04_sf.pptx

Eleni's presentation:
* Client interacts mostly at the start (MM request creation) and at the end (MM report). Workflow mostly hidden from clients
* 3MIS includes asset management, measurements and reporting. Planned to add resouce and budget management
* Parts of 3MIS: databases and FFMM. FFMM communicates both ways directly with the 3 databases (Infor, EDMS, MM oracle)
* Infor chosen for long-term support, convenient for asset management
* Infor has limitations (example: maximum number of decimals), need custom database. Custom DB uses ID from Infor to link with magnet, tools, DAQ, etc
* Asset management very important, application to create new assets and put codebars. Calibration of sensors implemented, history data kept 
* Measurement systems are not standard and data structure neither. For now, they focused on a couple of systems which make for the bigger part of the work.
* MM request the "center" of the database, MM run is each instance of measurement. If many magnets tested simultaneously, one MM request per magnet. If magnet is re-tested, one new MM request.

--

Linking with Carpenter discussion: 
* 3MIS Magnet ID <--> Carpenter Magnet MTF code
* 3MIS MM request <--> Carpenter test plan
* 3MIS MM run <--> Carpenter activities