wir schaffen wissen – heute für morgen electronic logbooks revisited paul scherrer institute...

Wir schaffen Wissen – heute für morgen

Electronic Logbooks Revisited

Paul Scherrer InstituteAndreas Lüdeke

Presented at the ARW 2011

Wir schaffen Wissen – heute für morgen

Smart-Books

Paul Scherrer InstituteAndreas Lüdeke

Presented at the ARW 2011

What is a Smart-Book?

Andreas Lüdeke, Paul Scherrer Institute at the ARW11 in Cape town, 14-Apr-2011 Slide 3

Smart-Book Functions

FinderFinder ThreadingThreading EmailEmail

EntryCommand

EntryCommand FormsForms ExportExportActionsActions

StructuredInformationStructuredInformation


How to create different types of logbook entries?

• Operators have to add distinct type of information in an operation logbook– Failure reports– Results of beam optimization– Machine status information

• How can that be distinguished in a logbook?– Add new fields to all entries!



How to answer to last weeks entry?

• Any new entry can be created as a reply

• Threads may be shown like for email clients

• This allows to see relations between entries• Failure report• Answered: repair information• Answered: tested and okay

ThreadingThreading


Semi-Automatic failure reports

• The power supply group wants information about every PS error

EmailEmail

EntryCommand

EntryCommand


The Operators should fill out a Start-up Checklist

• Pre-filled text field for entry type• Check-lists• Maintenance sheets• Tuning procedures

FormsForms


How to keep track of Disabled Alarms?

• Have an entry type, e.g. “Alarms bridging” • Add a field “Status” that is “disabled” or “enabled”• Define “Status” to have “Field propagation”• Create an entry for an disabled alarm

• If alarm has been re-enabled: create a reply with Status = enabled

• Status propagated to all entries in thread

• List of all “disabled” alarms from Finder

FinderFinder

ThreadingThreading



Every group has their own failure tracking!

• The operator needs to know how to create failure reports• Report transient failures of diagnostics by e-mail• Enter computing issues in “trouble ticket” web-form• Controls uses an issue tracking system (e.g. Bugzilla)

• How can the logbook help the operator?• Define for the entry type “Failure report” a field “Responsible group”• You define for each “Responsible group” an action on entry creation

• Diagnostics: send entry as e-mail• Computing: create trouble ticket• Controls: create Bugzilla entry

• The logbook does all the work for the operator!

ActionsActionsStructuredInformationStructuredInformation


How to get all entries on RF trips into a spreadsheet?

• Failure reports should have a field “Responsible group”• Then you can search for “Responsible group”= “RF”

• For every search you can save the results in a spreadsheet format

• Just load with your favourite spreadsheet programme

FinderFinder


ExportExportAndreas Lüdeke, Paul Scherrer Institute at the ARW11 in Cape town, 14-Apr-2011 Slide 11

Of course, there would be more to say…

CSSCSS

ThemesThemes

RSS feedRSS feed

BookmarksBookmarks

ExtensionsExtensionsConditionalFormatting

ConditionalFormattingTooltipsTooltips

?!CharsetsCharsets

KerberosKerberos

Mirror ServersMirror

Servers

SSLSSL

Access Rules

Access Rules

FinderFinder ThreadingThreading EmailEmail

EntryCommand

EntryCommand FormsForms ExportExportActionsActions


Logbook Groups

Logbook GroupsIconsIcons

Calculated Fields

Calculated FieldsLanguageLanguage


Does it sound interesting?

• Then check ELOG home: http://midas.psi.ch/elog • Just download and give it a try! Runs on Linux, Windows, Mac, Solaris, …• All credits go to Stefan Ritt!


wir schaffen wissen – heute für morgen electronic logbooks revisited paul scherrer institute...

Documents