Presentation is loading. Please wait.

Presentation is loading. Please wait.

GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist1 Lessons Learned / Needed Procedures / Documentation.

Similar presentations


Presentation on theme: "GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist1 Lessons Learned / Needed Procedures / Documentation."— Presentation transcript:

1 GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist1 Lessons Learned / Needed Procedures / Documentation Control B. Grist / L. Wai

2 GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist2 Lessons Learned The role of the “Test Conductor” is very important –Some EM activities early in the EM phase were uncoordinated The next activity was not clear or the there appeared to be conflicting ideas. –By clearly defining a “Test Conductor” allows for a central control of work. The Test Conductor can then delegate action as predetermined by the approved work order and procedures. –Toward the end of the EM phase the activities involving mechanical activities were much more coordinated. –All of the people on shift should know who is directing to work and who to bring issues.

3 GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist3 How does work get authorized? No mechanical, electrical, test, etc. operations involving flight hardware can occur without authorization. Work must be authorized 1.Procedure written 2.Procedure is approved and released into LATdocs 3.Work order is written to authorize proscribed work on a specific piece of flight hardware using an authorized procedure. 4.Work order is signed. 5.The “Test Conductor” schedules and work and directs it to start 6.NOW the work can be done 7.The results of the work are documented and attached to the work order as instructed by the work order and procedure.

4 GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist4 Documentation Documentation Control has several parts which need to be improved –Procedures released before operation/activity This means the DCN signed off and the procedure is in LATdocs During the EM operation most documents were only draft, this will not be acceptable during flight. –Work order prepared and signed off before operation/activity Work Orders should be prepared far enough in advance that the people required to sign can review carefully. Darren Marsh will be issuing written guidelines for work order QA inspection. –The work orders used during the EM phase would not have been acceptable for flight processing.

5 GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist5 Documentation –Completed Work Orders Closeout Process A work order once completed and all line items signed is supposed to be archived. –The EM work orders did not get archived. –Completed Work Orders and attached datapackages need review The process by which completed tests (i.e, the CPT) get reviewed by people other than I&T needs to be set up. Currently a test (i.e., CPT) is authorized by a Work Order then performed per a released procedure and then the test completion is signed off on the work order by I&T.


Download ppt "GLAST LAT Project Lessons Learned / Needed Procedures/ Documentation Control – October 23, 2003 B. Grist1 Lessons Learned / Needed Procedures / Documentation."

Similar presentations


Ads by Google