1. Page 1 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status

2. Page 2 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status  Preliminary Columbus ODF content for all Books/Files has been defined including procedures for NASA SODF maintained Books/Files: –EMERGENCY Book –WARNING Book –CAUTION Book –Flight 1E Assembly Book  Authoring of flight procedures is proceeding for all Books/files, i.e. DMS, COMMS, ECLSS, TCS, EPDS, MSM, IFM, GND, POC, including inputs for NASA/SODF maintained Books/Files.  Functional validation of COL ODF procedures will be performed on the SITE and partly on the ETM or by desktop review in case of similarity.  Validation of layout and correctness of IFM and MSM procedures will be performed via desktop review. The feasibility of IFM and MSM generic procedures was already verified in the frame of 1-g and 0-g test campaigns.  Validation of multielement procedures will be performed by NASA during joint tests and simulations in the frame of the SODF development cycle.

3. Page 3 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status ODF Component Flight System / Books Procedure Type COMMS Malfunction Corrective Reference DMS ECLSS EPDS GND IFM MSM POC TCS COL ODF Payloads SODF Generic Set / 1E 1E Flight- Specific Set EMERGENCY WARNING CAUTION Generic Set Malfunction A&C Reference Assembly US Systems A&CNominal Corrective

4. Page 4 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status

5. Page 5 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status  The set of procedures contained in the QR/FAR data package are the Columbus C/D Phase procedure delivery and are considered as the Initial Input Publication (L-18) of the 1E ODF cycle.  Subsequent development and maintenance will be performed by the Industrial Operations Team as defined in the ESA ODF Management Plan and controlled by the ESA ODF Control Board.  The development and validation of these procedures is on the critical path with respect to QR-II and training milestones, but not with respect to new Columbus launch date.  In order to meet these milestones priorities for procedure development have to be defined and the concept for Ground ODF procedures has to be determined and agreed.

6. Page 6 ESA ODF Control Board #4 3.-5. Mar. 04 Columbus Flight ODF Status 2005 2004 2006 MAMJJASONDJF MAMJJASOND QR-II DP Delivery FAR-I DP Delivery PreliminaryBasic Final Content Def. ODF Authoring Update/CR L-18 L-12 L-6 L-3L-1 CoFRInitial Inputs ODF Delivery for COL Launch 3/06 JFM COL Launch (NET) Launch Prep ODF Validation Need Dates P-JMST#2EAC/Training

7. Page 7 ESA ODF Control Board #4 3.-5. Mar. 04 PCS Development Status  Columbus QPM 4. Dez. 2003 –Agenda Point: PCS Display (US side) Development –Presentation by EADS-ST (G.Hajen), see Annex 8. It was once agreed that NASA is providing ESA/EADS-ST with the documentation. For further progress on this topic ESA will get in contact with the responsible of NASA as the previously agreed steps were not fulfilled by NASA (January 03). –Action ESA AI-APM-Mgmt-4760: To clarify the development progress with NASA. –As soon as a clarification has been provided, industry support will be requested by a Work Order.  Columbus SD&I 18.-19. Feb. 2004 –Agenda Point 3.5 Differences in NASA/Columbus Display Nomenclature –Mr. Hajen explained the issue based on example (Attachment 3.5). The principle was already discussed at the last QPM where ESA took the action to define the next steps – the action is overdue. ESA will work the action now with Ops/Mikael Wolff.