Notes traceability and suspension

• Particularly interested in site perspectives
• What does central suspension mean? Overlap with how workflows are implemented, e.g. jobs should not just be checked on entry
• We need to define what should be blockable
• Bar should be sufficiently high but not overly expensive
• We need to be reactive, reachability as well as traceability. Must define “reasonable time scale”
• Need tools to be alerted very quickly as well
• Better to block first and ask questions later
• Pilot jobs mean that have to resort to wide blocking
• Focus on person to person processes rather than technical measures (to a reasonable extent)
  • Would rather spend lots of time here rather than create tools that don’t work
  • Need to get these contacts clear and available
• Because we have more of a gap between the grid and the end IdP blocking might take longer, though can block quickly within the grid domain
• Traceability working group was working on this topic and now on hiatus
• Next steps
  • David to start a doc with
    • understanding of what needs to be blocked
    • schematic of person to person contacts and processes
    • Ensure traceability WG outcomes are considered