[Pansophy] C100R Window and Waveguide Status Board(s)

Tiffany Ganey ganey at jlab.org
Mon Feb 13 15:32:36 EST 2023


Minor change to table (corrected version below) - I'm planning on using the data field "PassInsp" instead of "ReadyForUse" in the C100R-INSP-WGD traveler revision.

Tiffany Ganey

From: Tiffany Ganey
Sent: Monday, February 13, 2023 3:12 PM
To: Megan McDonald <megan at JLAB.ORG>
Cc: pansophy <pansophy at jlab.org>
Subject: RE: C100R Window and Waveguide Status Board(s)

Hi Megan - I met with Greg to go over the draft status board.  In general, we felt that we could follow the workflow with the status board layout.  Greg would prefer to have more of the Yes/No columns than the dates.  Below is a list of the travelers with the columns he would prefer to have.  There were also a few traveler specific items/questions, listed with asterisk(s) under the applicable traveler name.  An overarching question for the status board - at the end of a cryomodule build, would it be possible to somehow note/report which SNs were used in the cryomodule and have those SNs hidden from the status board so that only the active ones are shown?

The table below can also be viewed in the linked spreadsheet, DashboardColumns tab: https://jeffersonlab-my.sharepoint.com/:x:/g/personal/ganey_jlab_org/EZkYP4hTWdVMvmD8ICFD6PIBXudQB-TsjpIDViII_iMbkQ?e=Qj51BS

C100R-FURN-CEBRZ-BRAZ
CEBRZSN
LeakCheckOk
CleanupBlastingDate
ReadyForWBA
CloseDate
C100R-FURN-WBA-BRAZ
CEBRZSN
WBASN
PassVisInsp
LeakCheck1Ok
RFTestOK
LeakCheck2OK
ReadyForIon
CloseDate
C100R-FURN-WBA-INSP
WBASN
InspReason
InspPass
LeakCheckOK
RFTestOK
RFLeakCheckOK
CloseDate
*Sort by InspReason, then sort by WBASN
** Is it possible to update the traveler data fields to be consistent with the other travelers?  LeakCheckOK --> LeakCheck1OK, RFLeakCheckOK --> LeakCheck2OK, RFLeakCheckComplete --> LeakCheck2Complete
C100R-FURN-WIN-ASSY
WBASN
WINSN
LeakCheck1Ok
RFTestOK
LeakCheck2OK
ReadyforEBW
WIN__OK
LeakCheck3OK
CloseDate
* In the section header (white background) the correct traveler name is shown (C100R-FURN-WIN-ASSY); under in the grey background an incorrect traveler name is shown (C100R-FURN-WIN-BRAZ)
C100R-INSP-WGD
WGDSN
PassInsp
CloseDate
Open NCRs
* Will revise traveler to include PassInsp Yes/No button
** Can a list of all open NCRs against that traveler be listed in a single row (do not repeat SNs in the list)?  If not, then just a Yes/No selection for if there are open NCRs against that traveler?
C100R-FURN-WINWGD-ASSY
WINSN
WGDSN
WINWGDSN
ReadyForEBW
WINWGD_EBW_OK
LeakCheckOK
RFTestOK
RFLeakCheckOK
PassCMMInsp
WGDReadyForUse
Close Date
Open NCRs

Tiffany Ganey

From: Megan McDonald <megan at jlab.org<mailto:megan at jlab.org>>
Sent: Thursday, February 9, 2023 1:02 PM
To: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Cc: pansophy <pansophy at jlab.org<mailto:pansophy at jlab.org>>
Subject: RE: C100R Window and Waveguide Status Board(s)

Tiffany,

I have somewhat of a rough draft of a status board for this. Here is the link https://pansophy.jlab.org/pansophy/Production/StatusBoards/C100R/C100R_WINWGD.cfm

Please let me know what you think in regards to layout, information, etc. I highlighted the SN columns in a dark gray in hopes to help with visibility but I can change that if you don't think it helps.

I noticed that for 2 of them, you requested close date. Would you like that on all? Would you like the sequence number with a link added? Are you interested in coloring of the sequence number to represent whether the traveler is open or closed?

Megan

From: Tiffany Ganey <ganey at jlab.org<mailto:ganey at jlab.org>>
Sent: Wednesday, December 14, 2022 1:50 PM
To: Megan McDonald <megan at jlab.org<mailto:megan at jlab.org>>; Valerie Bookwalter <bookwalt at jlab.org<mailto:bookwalt at jlab.org>>
Subject: C100R Window and Waveguide Status Board(s)

I took a quick try for listing the data fields that I think are needed to make the status boards for C100R Window and Waveguides.  I think this ends up being two status boards - one status board for the ceramic as it goes through the process of becoming a window, and a second status board for the waveguide being inspected through being welded to a window.

https://jeffersonlab-my.sharepoint.com/:x:/g/personal/ganey_jlab_org/EZkYP4hTWdVMvmD8ICFD6PIBXudQB-TsjpIDViII_iMbkQ?e=4SXqIU

I list the steps in sequential order, with a column for the work action description, traveler ID, SN, and data field.  The rows highlighted blue match up to the window status board (1st) and the yellow highlighted rows match up to the waveguide status board (2nd).

For the Window status board, the part changes SN as it goes through the process - it starts as a ceramic (CEBRZSN), becomes a window brazement adapter (WBA), and the finally becomes a window (WIN).  I'm not sure how you would handle this for the status board.  It probably makes more sense to have the status board left hand side be the CEBRZSN and maybe the other SNs can be added to the left column on the status board as they are created.  Also there is one traveler that gets used twice - first after ion implantation and second after anti-multipacting coating.  This is a radio button in the traveler so I just noted in the traveler ID column which should be true.  Please just let me know if the spreadsheet doesn't make sense.  I can probably explain it in person much easier than trying to type it up.

For many of the steps (leak check, RF Test, Degrease), there are separate travelers to capture this information but I did not include them on the status board. I would suggest that if someone needed that additional data, that they go through the Datamine Serial Number Search (or directly to the Traveler) to get that info for now.  Could the SN column on the status board be a hyperlink to that SN's datamine (for example, if on the window status board I click on a WINSN on the left hand side, it would open to the Datamine>>Queries>>Serial Number Search for that WINSN)?

It would also be helpful to have some indication if there is an open NCR on the component for both status boards.  Maybe the SN could be color coded to indicate overall part status (no color = "working, no issues", orange/red = "open NCR", green = "no open NCRs, all status board data fields complete, all travelers closed")?

I'm thinking that since this status board has multiple data fields from the same traveler, coloring the status board cells based on whether the traveler is closed is not needed.

Thank you!

Tiffany Ganey

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


More information about the Pansophy mailing list