[Pansophy] Pansophy

Thu Jun 25 15:12:08 EDT 2020

Go ahead and send it...

From: Jacob Harris <jharris at jlab.org>
Sent: Thursday, June 25, 2020 2:58 PM
To: Valerie Bookwalter <bookwalt at jlab.org>
Subject: RE: Pansophy

Minor edits and I moved a few of your comments to better fitting questions.

1-     Can a traveler have multiple approvers?

Yes. See answer to 2nd question.

2-     Is there an electronic work flow for traveler approval?

Creating the traveler document is done is MS Word using a macro template and approval is done electronically through our document management system (DocuShare). The template provides approval space for 1 Author and up to 3 others. Approved travelers are converted into the Pansophy system using programming/scripting tools custom written by JLab. For QA purposes we consider the approved traveler 'document' to be the MS Word file.

During work operations completing a traveler in the Pansophy system is done by any authorized Pansophy user with access to the project space. Closing a traveler is done only by persons established by the project team. Each traveler can have its own set of authorized closers and Non-Conformance SMEs. We consider the traveler 'record' to be the data saved in the Pansophy system.

 We also have the ability to create Hold Points in the Traveler which will halt data input until such time an approved designee (SME/Work Center Lead) clears the hold point. Non-Conformance Reports (NCRs) are a type of traveler within the system and are tied to a traveler step and signed off electronically by only designated SMEs/Work Center Leads/ Project Leads. Additionally, hold points and NCRs are automatically emailed to those whose approval is being requested.

3-     Is there revision control for a traveler?

Revision of a traveler document is done through MS Word and the document management system. Once a revised traveler is approved, it is put into Pansophy using the same programming/scripting tools.

Traveler data is entered and updated as work happens, with all entries tied to the user's ID. When the traveler is "closed", the revision number of the traveler document is recorded automatically and the data is locked to prevent further changes. A closed traveler can be reopened by ??? to make corrections, but no traveler data is deleted. Incorrect data is obsoleted within the system, thus providing a history of all changes to the traveler data.

4-     What is the age of the system?  Are there any plans for a re-write?  Is it web based?

The first version was implemented about 2001. The underlying database has been changed and upgraded several times, and it is currently Oracle. The development platform is Coldfusion/HTML/Javascript and it also has been upgraded several times. All the user interactions are through a web interface.

5-     Can an operation sign off be done by paper or does it have to be done electronically?

There is no paper process in our system. Some work stations may use a printout to collect data as work is performed then a supervisor reviews and enters it into the Pansophy system. We consider the traveler 'record' to be the electronic data stored in the system. Traveler data may continue to be collected and updated until such time as the Traveler is "closed". At which time the data is locked and no further changes are permitted. We also have the ability to have Hold Points in the Traveler which will halt data input until such time an approved designee (SME/Work Center Lead) clears the hold point after validating data. Similarly, Non-Conformance Reports (NCRs) are also signed off electronically by only designated SMEs/Work Center Leads/ Project Leads. Additionally, hold points and NCRs are automatically emailed to those whose approval is being requested.

6-     How many and what type of people support/administer the system?

Three comp sci people do all the support, administration, and programming. A few more IT folks typically get involved during upgrades to the database or the development platform.

7-     If BNL wanted to use the system can it be shared?

The system has been a patchwork of build/upgrade over many years and it is tailored to specific requests from Jlab. We have created a user manual and development documentation, but they are focused on our own internal use. It would be very difficult for someone else to simply copy our code and implement it on their systems. When JLab is doing a project for others, especially another DOE Lab, select people can be given access to view data, clear hold points, or approve NCRs, within their project space.

If such an external collaboration was desired, approval would be at lab management level. I suggest contacting Andre Seryi (seryi at jlab.org<mailto:seryi at jlab.org>; 757-269-6997) Associate Director for Accelerator Operations, Research and Development,  Mike Spata ( spata at jlab.org<mailto:spata at jlab.org>; 757-269-7497) Deputy Associate Director for Accelerator Operations, Research and Development, or Tony Reilly (areilly at jlab.org<mailto:areilly at jlab.org>  ;757-269-7658) SRF Operations.

 A demo could still be done if you would like to see the system in action. I like the idea of offering a demo, but I tried to make it clear in the last question that Pansophy isn't really an 'off the shelf' solution that can be installed or set up at another lab.

From: Valerie Bookwalter <bookwalt at jlab.org<mailto:bookwalt at jlab.org>>
Sent: Thursday, June 25, 2020 9:46 AM
To: Jacob Harris <jharris at jlab.org<mailto:jharris at jlab.org>>
Subject: Re: Pansophy

My comments in Red....
I wouldn't mind a collaboration, but I don't know if management is willing.
Doesn't hurt to put it on them and try.
Also, It would probably be good to give him a demo. Even if he can't use our system
maybe it could give him some ideas about what works and doesn't work.
If you would like to reach out and setup something, that would be good.

Thanks for the help.

Valerie

________________________________
From: Jacob Harris <jharris at jlab.org<mailto:jharris at jlab.org>>
Sent: Thursday, June 25, 2020 8:58 AM
To: Valerie Bookwalter <bookwalt at jlab.org<mailto:bookwalt at jlab.org>>
Subject: FW: Pansophy

Here are my quick thoughts on proposed responses. I am available today at 1pm if you think a Teams meeting is helpful.

I have P.T. 12 - 1:30 pm today. SNSPPU at 2pm.  Could meet afterwards if needed. Will try emails for now.

1-     Can a traveler have multiple approvers?

Yes. See answer to 2nd question.

2-     Is there an electronic work flow for traveler approval?

Creating the traveler document is done is MS Word utilizing a macro template and approval is done electronically through our document management system (DocuShare).The template provides approval space for Author and up to 3 others. Approved travelers are converted into the Pansophy system using some programming/scripting tools custom written by JLab. We consider the traveler 'document' to be the MS Word file.

During work operations completing a traveler in the Pansophy system is done by any authorized Pansophy user with access to the project space. Closing a traveler is done only by persons established by the project team. Each traveler can have its own set of authorized closers and Non-Conformance SMEs. We consider the traveler 'record' to be the data saved in the Pansophy system.

3-     Is there revision control for a traveler?

Revision of a traveler document is done through MS Word and the document management system. Once approved, the traveler is updated in Pansophy using the same programming/scripting tools. The traveler record data stored in Pansophy can also be changed, but it doesn't create a new revision And a new revision is put into Pansophy. This maintains the data collected with the revision of traveler at the time. No traveler data is deleted but rather obsoleted, thus providing a history of all changes to the traveler data. Any additions or changes to data, included the user ID of the person making the change are saved by the system.

4-     What is the age of the system?  Are there any plans for a re-write?  Is it web based?

The first version was implemented about 2001(?) and utilized for SNS cryomodule production. The underlying database has been upgraded several times and currently is Oracle. The development platform is Coldfusion/HTML/Javascript and it also has been upgraded several times. All the user interactions are through a web interface.

5-     Can an operation sign off be done by paper or does it have to be done electronically?

There is no paper process in our system. Some work stations may use a printout to collect data as work is performed then a supervisor reviews and enters it into the Pansophy system. We consider the traveler 'record' to be the electronic data stored in the system. Traveler data may continue to be collected and updated until such time as the Traveler is "closed". At which time the data is locked and no further changes are permitted. We also have the ability to have Hold Points in the Traveler which will halt data input until such time an approved designee (SME/Work Center Lead) clears the hold point after validating data. Similarly, Non-Conformance Reports (NCRs) are also signed off electronically by only designated SMEs/Work Center Leads/ Project Leads. Additionally, hold points and NCRs are automatically emailed to those whose approval is being requested.

6-     How many and what type of people support/administer the system?

Three comp sci people do all the support, administration, and programming. A few more IT folks typically get involved during upgrades to the database or the development platform.

7-     If BNL wanted to use the system can it be shared?

The system has been a patchwork of build/upgrade over many years and it is tailored to specific requests from Jlab. We have created a user manual and development documentation, but they are focused on our own internal use. It would be very difficult for someone else to simply copy our code and implement it on their systems.

For JLab work for other projects (W.F.O.) such as LCLS-II, SNS-PPU, etc., where JLab is producting the cryomodules, all data is housed on site and Customer Labs are given access to their data.

If such an external collaboration was desired, approval would be at lab management level. I suggest contacting Andre Seryi (seryi at jlab.org<mailto:seryi at jlab.org>; 757-269-6997) Associate Director for Accelerator Operations, Research and Development,  Mike Spata ( spata at jlab.org<mailto:spata at jlab.org>; 757-269-7497) Deputy Associate Director for Accelerator Operations, Research and Development, or Tony Reilly (areilly at jlab.org<mailto:areilly at jlab.org>  ;757-269-7658) SRF Operations.

 A demo could still be done if you would like to see the system in action.

From: Zipper, Joseph <jzipper at bnl.gov<mailto:jzipper at bnl.gov>>
Sent: Wednesday, June 24, 2020 3:50 PM
To: Jacob Harris <jharris at jlab.org<mailto:jharris at jlab.org>>
Cc: Valerie Bookwalter <bookwalt at jlab.org<mailto:bookwalt at jlab.org>>
Subject: [EXTERNAL] Pansophy

Hi Jacob,

Steve Smith gave me your name as a contact for information on you Pansophy system.  Valerie Bookwalter was very helpful initially but for some reason she has not returned a number of my emails.  Perhaps she is out.  I hope she is okay. Anyway, I just have the following questions about the system that I am hoping you can answer.

1-     Can a traveler have multiple approvers?

2-     Is there an electronic work flow for traveler approval?

3-     Is there revision control for a traveler?

4-     What is the age of the system?  Are there any plans for a re-write?  Is it web based?

5-     Can an operation sign off be done by paper or does it have to be done electronically?

6-     How many and what type of people support/administer the system?

7-     If BNL wanted to use the system can it be shared?

Thanks,

Joe Zipper

Quality Assurance Engineer

NSLS-II

Brookhaven National Laboratory

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20200625/8d1879e9/attachment-0001.html>