1. - 1 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS J.D. Schiemann / P. Boisvert ESA/ESTEC MSM-EPO MSFC / ESA TIM#3 Huntsville ; 17-19 August 2004

2. - 2 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS BACKGROUND  The ESA Operations Change process was presented at TIM # 2  An end-to-end flow was presented to capture the main elements  Focusing on payload operations  At TIM#2, the further Work was identified as  The identification and initiation of development of ESA/POIC OIPs regarding Payload Operations Changes  Columbus System changes (similar process as for Payloads, ESC=>USOC equivalent)  Process for CRFs with “Special Processing Requirements”  ISS level changes originating from Columbus  Identification of Change process for ESA Payloads in US-LAB  US-Segment changes affecting the ESA P/L Ops  Coordination and interaction for POIC - initiated (and TSC ?) changes for US P/Ls in Columbus

3. - 3 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS INTERFACE PROCEDURES (OIPs)  A bilateral OIP is outlined herein as draft  It addresses the Operations Change Request process for  Payloads in ESA racks located in Columbus  ESA payloads in US Lab  Payloads in NASA racks located in Columbus  ESA internal processes are also presented for information  CRF process – USOC level  Addressing the management of payload operations change requests at USOC level  Inputs for the ESA “MSM GS JOIP” document  CRF process - Col-CC level  Describing the change request process at COL-CC for any flight operations product  The bilateral OIP would possibly be integrated into an overall multilateral OIP based on this CR process  currently under review

4. - 4 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS MAIN STEPS  For ESA Racks in Columbus or ESA payloads in US Lab:  Initiation of a change request (USOC or Col-CC)  CRF internal submittal ; review at FRC level (if applicable)  For ESA P/L in US Rack: pre-coordination with respective TSC  CRF submittal at COL-CC level  ESA-level review ;  Disposition by ESA-FD  If CRF approved by ESA-FD: Transfer of pre-coordinated CRF to POIC OCR (for ESA P/Ls in US Lab)  Via FD (delegated to PAC ; TBC)  POIC review of ESA initiated OCR  Disposition of the OCR  Implementation actions for approved change request (CRF or OCR)  Appeal process (off-line)  OCR appeal process existing ?

5. - 5 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS MAIN STEPS (cont’d)  For NASA Racks in Columbus:  Initiation of a change request (OCR)  POIC review  Transfer of OCR to COL-CC CRF,  into ESA CR System by POIC Cadre position TBD  Rationale:  Col resources are affected  Col complement is affected  COL-CC review  Disposition of the CRF  Implementation actions for approved change request  Appeal process (off-line)

6. - 6 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS Main Issues  Inclusion of POIC in CRF review cycle  A CRF on ESA P/L in Col that affects the NASA ops baseline, e.g. change on EPM  POIC needs to be included in the review  Change Tool (OCMS) allows POIC inclusion as mandatory evaluator, or selective evaluator  POIC OCR initiation cycle  Required Pre-coordination via TSC, versus pre-coordination / pre-approval on ESA- level  Submission by ESA USOC via TSC vs. submission from ESA Col-CC for all ESA changes  Initiation of Columbus Changes into ESA system by POIC  NASA / POIC submit changes to the ESA CR system for changes to rack ops located inside Columbus  Rationale:  ESA's element responsibility requires integrated assessment  Changes of NASA racks inside Col affect Col-resources and/or Col-p/l complement  reviewed by all participants in Col Ops on ESA side, e.g. including Eng. support  NASA Users of ESA racks required to use ESA CR system  Later ; no such users identified, yet

7. - 7 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS BACKUP CHARTS

8. - 8 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – FRC LEVEL

9. - 9 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – FRC LEVEL (cont’d)

10. - 10 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – FRC LEVEL (cont’d)

11. - 11 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – COL-CC LEVEL

12. - 12 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – COL-CC LEVEL (cont’d)

13. - 13 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – COL-CC LEVEL (cont’d)

14. - 14 - MSFC / ESA TIM #3 – J.D. Schiemann / P. Boisvert; 17 August 2004ESA OPERATIONS CHANGE PROCESS OPERATIONS CHANGE PROCESS OUTLINE – COL-CC LEVEL (cont’d)