Equipment Service Request Tutorial

MISCOMP/INT1 / CDFDB Test Database tutorial 3 : ESR -- Initiate a repair job request

version 1.2, John Yoh, 6/20/00
version 1.3, Linus Wong, 7/12/00

Notes :
A "Job" (repair job) could also be used to record checkout information for a new module.

ESRs (Equipment Service Request) to CMD should ONLY be used for CDF supported modules; repairs for those modules supported by PREP should be sent to PREP for repair, and THEY will enter the ESR there. Check the bottom of the Beginner's Info & Module Status page for a list of PREP supported module types.

If you are removing a broken module from a slot in a crate, you can submit an ESR in the process of doing a "Position Modification". When you click on a "M" box next to a slot, the new window that opens has a button named "Service Request" to initiate an ESR.

The procedure followed when a bad module was discovered consists of two steps :
(1) Job Initialization -- The module is moved from an activity (online, spare, etc.) into a special catagory -- "Broken Spare", and a Job request record is initiated. This record will include information such as the suspected problems, etc.
(2) Job Completion -- After the repair person has fixed the problem, he/she will enter a new record to the job record, giving the actual problem (which might differ from the suspected problem in step (1)), repair done, etc. The unit will then move from "broken spare", usually to "working spare"--though moving immediately to a rack/crate/slot location is also possible.

Note that a job could also indicate an alteration, etc.

Initiating a Repair Request Tutorial

Preparation:

Log onto the miscomp/int1 CMD on the web using netscape 4.5+ (or, if you have an account, you can use a "direct connection to Oracle" in fncdug) The easiest way is to use the CMD site--Choose "Module Maintenance form", then "int1" db for testing..
Use the CMD (Misweb) Reports to select a module on which you would initilize a job repair. --For example, using the "CDF Modules" report, type in %tracer% in the Module field to get a list of tracers and their serial number.
Go back to the main miscomp/int1 (CMD-test) site. Select the "Module Maintenance Forms" link, which will allow you to access any of the 6 forms, and change to a different form without resubmitting your password. For the test DB, use the account: cdf_test and password: run2
If moving the Broken module, follow the instructions below (you will use the Position Modification form at first). Otherwise, use the "Equipment Service Request" form, and skip to the secion on filling that form out below. If you try to submit a request for a module that is in a rack without moving it, a window will pop up making sure you don't want to move it first.
Don't forget that when filling out fields, the wildcard (%) can be used.

Moving the module and initiating a Repair Request:

Bring up the "Position Modification" form.
Type the name of the rack in the Rack Name field (or select one from a list by clicking on the ? next to it) and hit either return or press the "Query" button. This will bring up the rack information.
Click on the crate number in the given rack to bring up its specific slot information which will appear below in the Slot portion of the window.
Click the M button to the right of the desired module to open the Move window.
Enter the module's new location and new activity (Press the "CDF" or "ALL" buttons for a list of locations; press the triangle for a pulldown list of activities).
Change the default activity date (only if applicable).
Press the "Service Request" button to bring up a service request form or press the "Commit" button to move the asset to its new location.
Note: once the "Service Request" button is pressed, the asset will be moved to its new location.
Fill out the Service Request form as described below.
Insert a spare module into the now empty slot from the Position modification form as described in the Position Modification tutorial if needed.

Filling out the Repair Request:

Enter the name of the person who is requesting service (for this tutorial, you can use yoh, john). A list of names is available by pressing the (?) button (this lists everyone with an association with Fermilab).

Enter the description of the problem in the "Problem Statement" field. (presing ctrl-e brings up an editor).

Enter each asset to be serviced with the problem listed in the "Problem Statement" field. (Enter the property # or combination of serial number and model name). If the Equipment Service Request form was entered from the Position Modification form, These fields will already be filled out for you.

Press the "Commit" button. The request and its asset details will be saved and a job will be created for each detail.

click on "Exit" to quit. You may want to check on this job by using the Misweb report form "-->Reports Modules in Repair". To query a repair job on the module, enter the model and serial number. (Note that the link is to the test database, and NOT the production.)