1 / 27

power point blank chart

Samuel
Download Presentation

power point blank chart

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    8. ULF5, ULF6, & HTV2 Manifest Plan

    10. STS-134 (ISS-ULF6) Launch Package Description

    15. STS-134 (ISS-ULF6) Timeline Overview FD1 Launch FD2 SRMS Checkout; OBSS Survey; EMU Checkout; EVA Tool Config FD3 RPM, Rendezvous w/ Station & dock to PMA2 (on Node 2 forward port); Orion RNS DTO- 703; Ingress Station; Middeck transfers; Deploy ELC3 from Shuttle PLB to ISS P3 Upper Outer CAS FD4 Deploy AMS-02 from Shuttle PLB to ISS S3 Upper Inboard CAS, EVA Prep FD5 EVA 1 – Transfer MISSE 8 from PLB to ISS, Return MISSE 7a & 7b from ELC2 to PLB sidewalls FD6 Focused Inspection (if required), Water Dump, EVA Prep FD7 EVA 2 – Clean/lubricate Starboard and Port SARJ FD8 Late Inspection, Off Duty, EVA Prep FD9 EVA 3 – Transfer and stow Integrated Boom Assembly from PLB to S1 Truss OSE; Install PDGF on ISS; Middeck Transfers FD10 Off duty, Crew Conference, GLACIER stow, Hatch Close FD11 Undock from ISS; Flyaround; Re-rendezvous for Orion RNS DTO-703 FD12 Cabin Stow, Water Dump, FCS C/O FD13 Deorbit Prep, Landing

    20. AMS Schedule

    21. AMS Schedule

    23. AMS Schedule

    24. Phase III Safety Reviews Both Phase III Safety Reviews need to be completed at least 30 days prior to arrival at KSC. Safety Data Packages due 45 days prior to review. Currently planning to have at least one of the reviews prior to Christmas. The safety data package for that review is due by the end of October.

    25. Data Requirements In order to build the package, we need the following items from the collaboration. Acceptance Data Packages Written procedures for all operations which will occur at KSC. Any required updates to the data package text from Phase II. Please allow time for us to resolve any issues and ask questions.

    26. Export Control Now that we are in the standard integration flow, Boeing and USA will now need to interface directly with many collaboration members during integration tests at JSC and during integration activities at KSC List of high probability contacts has been provided to companies Companies have begun the process of getting Technical Assistance Agreements and DSP5s (MIT only) in place Many of you have already received input from some companies If you choose not to sign the agreements, none of your employees will be allowed to sit in meetings with employees from the companies, you will also not be allowed to sit in the Mission Control Center

    27. NASA Badging Sorry for the repeated questions and e-mails Process continues to change For the 130 people requesting badges, the current process would require as many as 1,040 electronic requests and 9,360 electronic signatures whether or not a person was to be escorted on a NASA facility Working with security office at JSC, KSC and HQ to simplify for AMS. Proposed solution would still require 260 electronic requests and 2340 electronic signatures…but it is still better. Trying to reduce this further.

    28. NASA Summary We are at L-375 days and every effort must be made to maintain schedule Use of slack time must be coordinated through Integration Team here at CERN Any potential slips must be brought up as soon as you know about them Use of slack time will be allowed only if technically prudent and approved by Sam Ting We are now into major integration activities for ISS and Shuttle, and my team needs your quick responses to our questions in order to support this integration. We will make every attempt to avoid asking questions of those directly involved with day-to-day integration, but questions will be required from time to time.

More Related