1 / 21

DOE Review of the LCLS Project 24-26 October 2006

This review provides an overview of the LCLS project's information management efforts, including document storage, web collaboration tools, CAD drawings, optics and components RDB, and other project needs. It also outlines future plans for the project.

america
Download Presentation

DOE Review of the LCLS Project 24-26 October 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DOE Review of the LCLS Project24-26 October 2006 Information Management Andrea Chan / SLAC

  2. LCLS Information Management • Overview • Document storage and web collaboration tool • CAD drawings • Optics and components RDB • Other project needs • Future plans • Summary

  3. Overview • ~0.75 FTE Effort level • Started August 2005 • Help from SLAC Computing Services (infrastructure, SharePoint, DB/applications), Mechanical Design, and other departments • Philosophy • Leverage SLAC resources • Utilize site infrastructure and expertise • Avoid duplicating data • Link separate databases through common fields

  4. Overview – cont’d • Focus for LCLS Information Systems • Analyze project needs to focus scarce resources • Utilize existing SLAC Directory as the LCLS people database, which provides integration with • Existing ESH training, reports,… • Financial and other business systems • Computing accounts and resources • Establish a web-based document storage system • Provide for RDB needs of LCLS Engineering and Controls • Map component alias/names

  5. Overview-Cont’d • Need to link with other site databases • Take advantage of experience from PEP-II Project in mid-1990’s • Developed ability to link to different accelerator and engineering databases using common fields and web applications • Focus on a few key systems, and make sure those have complete data

  6. Document storage and web collaboration tool • MS SharePoint was being set up at SLAC (November 2005) • SCCS established a system for LCLS that has: • Structured shared space for project documents (consolidated key documents from network drives, e-mail attachments, web servers, off-site servers, ..) • Easy to use web-based interface for remote read/write • Access control, password-protected • Version control, check in/check out • Tag documents with metadata (for searches and queries) • Search capabilities • Alerts for new items added • Learned to work with Sharepoint ‘out-of-the-box’, and not customize • Will upgrade to SharePoint 2007 at the beginning of 2007

  7. SharePoint Implementation - Top View of LCLS Site

  8. Announcements Conventional Facilities PDF drawings maintained on the SharePoint site.

  9. Sample SharePoint Site with Metadata Search Upload documents Setting alerts Check out Serial number, barcode and the link to a drawing image

  10. CAD Drawings • The Mechanical Design Department has implemented a web-based design management system for LCLS Solid Edge CAD Drawings (also based on MS Sharepoint). • Advantages of a user-friendly interface to: • Collaborate on files • Manage file associations (Bill of Materials) • Find files • List metadata (e.g., hazardous material) • Link to drawings from LCLS engineering database

  11. CAD Drawings - cont’d File links (parts, config, …) File status and other metadata

  12. Optics and Components RDB • Provide for RDB needs of LCLS Engineering and Controls • A single, comprehensive relational database to store optics, parameters, metrics for LCLS components • SCCS DBAs and developers help with design and implementation of the database schema, tools for data loading, data export, report generation, and APIs

  13. Optics and components RDB - cont’d • Beam Line Optics and Components database • Database to integrate Beam Line Optics and Engineering configuration data (instead of multiple, separate Excel spreadsheets) • Provide easy way to compare any two versions of optics output • Streamline integration of new versions of optics with components data (cabling, power supplies,...) • Database for optics output to enable on-line beam modeling, i.e. XAL • Inventory database

  14. Comparison Program for Different Optics File Versions Optics files are uploaded into the database Select 2 optics files to compare to # decimal places Change in suml value highlighted for element BPM24701 Change in area highlighted for element BPM24701

  15. Cabling Database (work in progress) Adding cables for element BFW04 (data from the LCLS database is transferable to the SLAC cabling database-CAPTAR)

  16. Cabling Database (work in progress) –cont’d If the new optics file version has values that are significantly changed for element BFW04, the cabling data below is re-checked and validated for the new version. Values from previous versions of the optics files are also available.

  17. Inventory Database Drawing # from SLAC document control Serial #, Barcode #, Alias name Optics name

  18. Other Project Needs (e.g., ESH) Database application for ESH Safety Observations

  19. Future Plans • Provide more RDB, applications and tools for LCLS Engineering and Controls • Collect data from fabrication • Migrate to new version of MS Sharepoint 2007 for better functionality • Link to other site databases and systems

  20. Summary In 14 month period: • Document storage and web collaboration tool (SharePoint) – implemented, preparing for upgrade • Optics and component RDB/applications needed by Engineering and Controls – (Optics and inventory implemented, work in progress on cabling and others) • Kept up with other project needs (ESH, …) • Plans to link to other DBs needed by LCLS • Large scope, but the focus is on quick deliverables in small increments based on limited resources

More Related