70 likes | 187 Vues
The LCLS Components Database is a centralized relational database designed to facilitate beam simulation and manage component data effectively. It is built upon the PEP-II Components Database schema, allowing for flexible design to accommodate diverse components without the need for constant redesign. The SCCS Database Group will create the database schema, and provide tools for data loading, exporting, reporting, and APIs. Standardized alias names and key attributes will enable accurate linkage with other systems, enhancing overall data management and collaboration through tools like Microsoft SharePoint.
E N D
RDBOctober 27, 2005 • Outline • Components Database • LCLS Record Management • Component Names and Key Attributes • Summary
Components Database • A single, comprehensive relational database for LCLS components. In the short term, we need a database to enable beam simulation, i.e. XAL • The LCLS Controls group will be responsible for EPICS and XAL, which need parameters and metrics that can be stored in a relational database. • The SCCS Database Group will design/implement the database schema, and supply the tools for data loading, data export, report generation and API’s. • Use the PEP-II Components Database schema as a building block.
Advantages • Flexible design that has been used to store diverse components without needing to redesign the database for each set of measurements and component type. • The design and schema already exist. A copy has been customized for LCLS. • (To reduce the number of tables involved for queries, customized views can be created.)
Component Names and Key Attributes • Standardize alias names and map key attributes • Standard names will enable accurate linkage and search through other databases (e.g., CAD drawings, maintenance)
Summary • Customized an existing Components database for use by LCLS Controls • Pilot use of Microsoft Sharepoint for document management and web collaboration tool Q4, 2005 • Action items: • Test the Components database schema and develop tools • Standardize component names, and maintain the alias names and key attributes in a central database