Specification of fault reporting system

[shroffk]

The goal of this Issue ticket is to collect the requirements for a fault reporting system to be used in NSLS2 operations.
@reidmsmith will be providing feedback on

• fault error data
• fault error reporting and consuming workflows

[reidmsmith]

Info needed from Fault reporting in CSS:
Accelerator Area: (Global, Linac, BR, SR)
Subsystem: (Diagnostics, EPS, RF, Controls, etc)
**Device: (thing that broke. Sometimes this will just be first symptom)
Description: (one sentence – what’d you see?)
Operator Details: (describe what happened. Could incl. olog entries, or a concise summary)

Time Fault Occurred: Problem started
Time Fault Cleared: Problem solved, start machine recovery
Beam Interrupted?: (Yes, No, Studies)
Time Beam Restored: When Operations starts again

Group Leader: Auto. by Subsystem
Person Assigned: Done as an action by G.L. or operator
ENG – Root cause:
ENG – Repair detail:
ENG – Corrective action: All three ENG slots *could be combined.

Calculations: (not on form, show up in spreadsheet view)
Fault duration: (Fault Cleared time) – (Fault start time)
Downtime: (Beam Restored time) – (Fault start time)

Workflow Stuff:
OPERATOR:
Has to make log entries in CS-Studio, dump pictures, Post-Mortem plots, etc
*Also has to start a FR in sharepoint (web browser)
*Also has to log state-changes in Machine State Tracking (sharepoint – browser)
SHAREPOINT:
FR is saved. On Creation, a table is referenced to assign Group Leader from Subsystem.
*GL is automatically emailed about creation of report, including a link to FR.
GROUP LEADER:
*Receives email; either fills in details or sends report to group member (email can be sent through sharepoint workflow)
*Options are now ‘Open’, ‘Closed’, and now ‘Pending’ for cases that won’t be fixed right away.
COORDINATION:
Downloads FR’s weekly as a spreadsheet, reports the week’s faults to GLs.
Uses times to calculate MTTR and MTBF
Tries to encourage GLs to fill in details on reports (should be easier once caught-up from 2015)

Needs For Whatever New Workflow Is:
Ability to email group leaders
*Ability for GL’s to fwd reports??? Could do without?
Ability to export list of FR’s easily (doesn’t need pictures)
Easier for ops to create FR’s (like, from log entries)
Ability to reference/link log entries for easy info attachment
Ability for GL’s to view/edit FR’s in web-browser / from Windows.
Automatic reminder emails to GL’s not necessary, but also a consideration.