Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    FCC Availability - Robot Reliability and updates

    → Europe/Zurich
    CERN

    CERN
    Hide

    RAWG should be more specificaly refered to as FCC Availability Study for the context of modelling availability for FCC

    Robotic Reliability

    MN presented current approach for reliability estimates for the robotics.

    • Top down approach using available manufacturers data to give best case scenario
    • Able to provide MTBF to the FCC Availability Study in short term
    • Longer term:  create FMECA (Failure Mode, Effects and Criticality Analysis) to understand the failure modes and criticality to operations.

     

    Group discussion on the options for how to include robot reliability in FCC Availability Study:

    • Model the robots as isolated systems (not efficient)
    • Model the full integrated luminosity and get sensitivity values
    • Get a design goal from the master simulation.

     

    Agreed approach: Robotics team analyse reliability and criticality of robot concept -> Robotics team provide FCC Availability Study with MTBF of robots to critical failure and the tasks they perform -> FCC Availability Study calculate how many times per fault of e.g. power converters the robot fail to repair -> simulate final integrated luminosity metric

    Robotics team provides a range of MTBF values which are used to provide sensitivity values.

    Useful Resources:

    • Military handbook we should have access to.
    • AFT Fault tracking -> aft.cern.ch/cardiogram
      • API available for processing via python
    • Availability team have guidelines for designing for reliability that can be shared.

    Discussion on high priority infrastructure owners

    • No immediate candidates identified as an obvious potential for robotics.
    • Availability team still also looking for low hanging fruit.
    • Difficult to identify tasks applicable to robotics due to complexity and variety of fault causes
    • Addressing or advertising to other teams which also have electronics cards could be a good synergy with current power electronics concept.
    • Availability team will continue to investigate the simulation results and report when a new infrastructure team requiring automation is identified.
    • Currently not blocking robotic development, but additional stakeholders would be best contacted earlier, so any potential for automation to improve availability should be discussed with the robotics team for input.

     

    Action points:

    • Robotics team to continue to evaluate MTBF for current robotic concepts. Provide these values to availability team.
    • Robotics team to develop a FMECA / Fault Tree for further understanding of criticality of failures.
    • Availability team to tell robotics team how to access the military handbook
    • Availability team to share details of the API to query the AFT database (a link to the gitlab / an example script would be much appreciated)
    • Availability team to inform robotics team if / when a stakeholder identified with any potential need for automation to improve availability.

     

    There are minutes attached to this event. Show them.