1 / 27

CERN Documentation management System Isabel Bejar Alonso

CERN Documentation management System Isabel Bejar Alonso. HL-LHC Standards and Best Practices Workshop (11-13 June 2014). Contents. LHC QAP Documents/Templates Tools. What existed for the LHC. Document Types and Naming Conventions Equipment Naming Convention Parts Ids

kira
Download Presentation

CERN Documentation management System Isabel Bejar Alonso

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. CERN Documentation management SystemIsabel Bejar Alonso HL-LHC Standards and Best Practices Workshop (11-13 June 2014)

  2. Contents • LHC QAP • Documents/Templates • Tools

  3. What existed for the LHC • Document Types and Naming Conventions • Equipment Naming Convention • Parts Ids • Configuration management • Design Process and Control • Purchasing and Contracting Process and Control • Manufacturing and Inspection of Equipment • Handling of Nonconforming Eq. And several documents templates The LHC project had a QAP that fixed some Quality parameters such as:

  4. What existed for the LHC Documentation was handled with EDMS, records with MTF … In EDMS there were several structures that adapted to the type of information. Only the Hardware Baseline followed the LHC QA naming convention. There was a dedicated team to ensure the quality of the documents uploaded on it

  5. Document categories The document categories were based on the project life cycle processes

  6. What to do in the meanwhile Set of simple rules compatible with the LHC QAP for the project on: • Identification: what kind of document shall be managed • Labelling: how the document shall be named • Lifecycle: how shall be ensured the adequacy of the document before distribution • Availability: how shall be ensured that the document arrives to the right person and can access it as long as required • Traceability: how it is record the changes and location of the document

  7. Example Visibility

  8. Documents and templates

  9. Systems life-cycle Decision gates (reviews)

  10. Baseline documentation (1/2) EDMS: 1361462 Project management Acquisition Technical

  11. Baseline documentation (2/2) (see also presentation from J. Gascon & Th. Otto) Safety File Links to already existing documentation will be made, whenever required EDMS: 1361462 Project management Safety Technical

  12. Baseline documentation EDMS: 1361462 • A template for each type of document • A guide to fill in he document • Examples for each type of template Project management Acquisition Technical

  13. Conceptual specifications https://edms.cern.ch/file/1311290/0.4/LHC-PM-QA-517.V04.21.01.2014.docx

  14. Functional Engineering Specification https://edms.cern.ch/document/1372969/0.1

  15. Architecture

  16. Processes

  17. Building blocks

  18. Eng. Specifications -> Procurement Procurement (IT/DO template) Requirements definition (conceptual specifications) Contractual requirements Functional specifications Technical requirements In-house design, manufacture, assembly, tests Engineering specifications Quality & Configuration management requirements

  19. Safety Hazard identification

  20. Launch Safety Agreement

  21. Tools

  22. EDMS structure (1/2) • Repository of the HL-LHC baseline documentation (under the LHC hardware baseline, for which specific nodes will be created in case of new equipment)

  23. EDMS structure (2/2) • Each Work Package will have a pre-created EDMS structure based on its systems architecture and on the required contents of the baseline documentation Example • WBS • Schedule • APT • Procurement • Specifications • Design • Fabrication, Assembly and Verification • Installation-Commissioning • Operation & Maintenance • Dismantling • Safety File • (links to documents in upper nodes whenever required)

  24. Other documentation • Non-baseline, documentation (e.g., follow-up meetings, scientific publications) can be stored in the WP workspace • Structure will be defined with each WP

  25. Records

  26. Too many?

  27. Thank you for your attention ! Questions?

More Related