MCC ELOG

 

Minimum Requirements:

0 – Choose to eliminate JLAB-SLAC software dependence.

1 - User entries editable for length of shift +1 hour. Edit permission limited to entry’s author.

2 – Start of shift entry form. (Done?)

3 – End of shift summary report. (We will leave it as MS Access database and provide single click to move shift entry.)

4 – X-windows interface that works on NCDs. (See demo. Done?).

5 - Users must be authenticated.  User should timeout 15 minutes after shift change.

6 – Complete previously requested set of Web version look and feel modifications. (We are waiting on JLAB’s software support.)

7 – Machine timestamp. (View and sort by).

8- Auto entry into existing PEPLOG

 

 

Meeting minutes for 8/6/2004 meeting:

-         Debbie Rogind gave a demo of UNIX Foyer.  This program can be used on NCDs and could allow users to launch any UNIX program run in MCC (EPICS, Matlab GUIs, TCL based electronic log entry windows, etc.)

-         Geoff Milanovich gave a demo of two TCL based programs that run well on NCDs, MS Windows and Sun workstations. One program is a logbook entry window with fast screen capture and the ability to get ELOG print queue figures.  The other program is a logbook reader that works well on NCDs.

-         Minimum requirements for the logbook were discussed (see list above).

-         Other requirements were touched upon. We should look at these once we are getting close to meet all the minimum requirements.

 

Action items and comments for minimum requirement list:

0 – Roger will talk to Spencer to verify that the ELOG is fully supported by the ESD software group.

1 – Edits will not be allowed. The use of a user defined ‘Machine Time’ should help with the issue of edits. Log book reader programs will need to have an option to sort entries by ‘Machine Time’. This is easily implemented using the existing “timestamp” tag.

2 – The start of shift entry form has been completed. It needs the ‘Machine Time’ feature added.

3 – The existing MS ACCESS based end of shift summary report should have a feature to send the shift data to the log. (Machine time will default to 7:59:59, 15:59:59 or 23:59:59 so it appears just before the start of next shift entry form).

4 – DONE!!!

5 – Partially done. User authentication is done before an entry is moved to the database. (This item needs more discussion.).

6 – Waiting on JLAB. (Should we look at these ourselves?)

7 – Machine time: Partially done. (It needs to be added to web viewer.)

8 – Requiring that the operations group make “double entries” is not acceptable.  (If someone feels that a given entry belongs to the MCC ELOG and wants PEP physicists to view it, click on the PEP box of the logbook entry.)

 

Other Requirements:

 

1 – Spellchecker.

2 – Scanner (Done).

3 - Artemis integration.

4 – Tablet PC.

 

* checklist generation (common on RODs, MDs, and on busy shifts)

  - make list

  - add items to list (want ONE list, not multiple)

  - add comments/details to items

  - marking an item as completed

* the post-it note system of "stickies" to pass on "to do" items to the next crews

* "Bookmark" key entries for later reference.  Some people do occasionally use physical bookmarks in the logbook...