1. ISS Plug-in Plan (IPiP) Roadshow (or, IPiP 101) http://iss-www.jsc.nasa.gov/nwo/mio/cargo/ipip/web/index.shtml IPiP Engineers Kevin D. Moore/OP/OC42 281.244.8313 Kevin.moore-1@nasa.gov Adan Tellez/OP/OC42 281.244.2756 Adan.tellez@nasa.gov 07.22.15 This presentation is intended solely for the audience to which it is directed. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT

2. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 2 Purpose –Inform the ISS Community of nominal IPiP processes and functions; “What can you expect?” –Discussion of ISS Plug-In Plan Requirement Request Forms –Inform ISS community of Plug-in Plan End Items issues What is a Plug-In? IPiP Responsibilities IPiP Processes –ISS Plug-In Plan Approval –Chit Review ISS Plug-In Plan Requirement Request Forms (IPiP RRFs) IPiP Overview

3. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 3 3 Differences from your Home (Almost) Everything is Direct Current (DC) Lots of Cables Many different types of connectors Connectors on both ends of most cables More stringent current draw limitations Figure 1: Plug-In Plan Comparison

4. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 4 4 SUP1 (at COL1AD1) UOP6 (at LAB1SD4) Figure 2: Utility Outlet Panel (UOP), left, and Standard Utility Panel (SUP)

5. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 5 Recommend approach for connecting portable loads to the ISS Power/Data Subsystem –Does not include internal camera ports or ExPRESS Racks Develop Nominal and Contingency plans pre-Increment for approval by the Increment Operations Review (IOR) and Joint Operations Panel (JOP) Coordinate real-time updates with IMC and FOD –CHIT coordination –Concur with real-time changes uplinked to crew and posted to PLUTO web pages Maintain cognizance of real-time US portable loads plugged into IP modules IPiP Responsibilities

6. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 6 Based on above, IPiP identifies requirements, sources for new or replacement end items, then by consensus, determines a configuration, works with FOD, EP, and Vehicle Office to build and manifest end items, to meet strategic (long-term), tactical (mid-term) and real-time (operational) requirements. IPiP looks for answers to the questions: What power you need, when do you need it, and where do you need it ISS Plug-In Plan: the sum of products and services developed to support the Program Office Plug-In Plan (PIP): real-time working plan executed onboard. IPiP Responsibilities (cont’d)

7. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 7 7 IPiP Responsibilities ISS Plug-in Plan Engineers have been directly involved in analysis and planning for: Portable Loads Planning and Deployment –BEAM Deployment (future Increment 45/46) –Amateur Radio in ISS (ARISS) Ham Radio Redesign (2015) –Fluid Shifts Deployment in RSOS (2015) –Airway Monitoring Deployment (2015) –On-board Auto-Shutdown of Active Thermal Control System (ATCS) Loop B (2015) and Pump Module A Failure (2013) –Remote Power Controller Module (RPCM) LAP51A4A-A, Remote Power Controller (RPC) 18 Trip and Recovery Failure Investigation Team (FIT) (2014) –EVA 24/25 EETCS Loop A Pump Module (2014) –JAXA 4K Ultra High Definition Video Deployment (2013) –EVA 18/19 MBSU -1 Failure to Install (2012) –Node 1 Galley (SSPCB Action 040312-001 – ongoing, ACO SpX-12 –Pump Module Repair & Replace R &R) and Plug-in Plan Configuration De-Crewing Scenarios (2010) Plug-In Hardware –Develop requirements/ Build/ Upgrade/ Manifest of PS-120 Junction Box, PS-28 Junction Boxes, A-N ConnectorsDevelop requirements/ Build/ Upgrade/ Manifest of PS-120 Junction BoxPS-28 Junction BoxesA-N Connectors –Ku-Band Power SupplyKu-Band Power Supply –120 VDC / and 28 VDC - to -120 VAC ISS Power Inverter requirements, procurement, build, deploy120 VDC / and 28 VDC - to -120 VAC ISS Power Inverter –SpX-1 Inadvertent Return to Earth Reassignment, Relaunch Mission Evaluation Room (MER) Action Requests: AKA, Chits Certificate of Flight Readiness (CoFR) / Stage Operations Readiness Review (SORR) letters and Abstracts of Analysis Strategic planning for future portable loads and support equipment for portable loads

8. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 8 IPiP Working Group Process IOR JOP DRAFT ISS Plug-In Plan Schematics Contingency Tables Inc (mos)-8-4-3 < - 1 + Requirements from: ISS Users Increment Plug- Call for IPiP RRFsIP Draft Plan Coordination IPs (JCCT) Payloads Photo/TV IPiP (OC) PiP Tool Chits Previous Increment Plug-In Plan DRAFT ISS Plug-In Plan Schematics Contingency Tables Interim Working Data Posted Increment Specific Crew Training Briefings Increment Plug-In Plan Post Approved Data To IPiP Website Produce CoFR Letter CoFR FOD Annex 5 Coordination -12

9. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 9 SSP 50627 – Generic ISS Plug-In Plan Integration Requirements for Future Portable Loads - is the governing document Data Acquisition Annex 5 On-Orbit Utilization Table —› IPiP RRFs —› MIDAS link generates Automated IPiP Engineer email —› IPiP web-based question-answer format at the End Item Provider level —› Chits —› End Items Evaluation –End Item Provider requirements (Annex 5) –Completed IPiP RRFs –Joint Cargo Certification Team (JCCT) Analysis –Integration into overall IPiP IPiP Working Group Responsibilities

10. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 10 Improvement Recommendations –Consensus for Alternate Plans Products (Working Data posted at I - 8 to I - 3 months on IPiP Website) –PiP Schematics —› Contingency Tables for Power Channel Failures Approval process (Approved Data posted at I ~ 1 mo) OC4 —› IMT / IOR —› JOP —› baselined for flight —› FOD (upload to PIP Tool and Plug-In Port Allocation table at beginning of the Increment) Approval process leads to Approved Data for Certificate of Flight Readiness IPiP Working Group Responsibilities (Continued)

11. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 11 IPiP Chit Review Process : *For hardware in IDRD, IPiP, or otherwise agreed to prior to Increment. May also be an Internal Flight Note NASA ESA / JAXA IPiP PLUTO COSMO / CANSEI Pre-coordination Phase IMC / IPiP (ISSPO) PLUTO MER / Engineering Safety Flight Note* Chit Portable Plug-In Hardware Approved for Use on ISS Analysis Phase JCCT

12. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 12 Call for IPiP Requirement Request Forms ISS Plug-in Plan Requirement Request Forms (IPiP RRFs) Request for End Item Providers complete On-Orbit Utilization Table in Annex 5 Call for IPiP RRFs at respective IMTs at I - 8 mos and via email through IMT DL Request information needed to develop the ISS Plug-in Plan and related Increment-specific products End Item Providers may obtain a blank IPiP RRF through MIDAS When a Manifest Request submitter checks the box ‘Requires On-orbit Power’, the system notifies IPiP Engineers with –the MR Title, Initiator contact info, End Item Provider POC, dates of end item use –IPiP Engineer can then contact the end item POC and provide the link to the IPiP RRF. - Or - –The initiator can navigate to the IPiP Homepage. The IPiP RRF tab is on the left with a direct link to blank form, “IPiP Requirement Request Form.” Provide a digital picture of the hardware under separate cover http://iss-www.jsc.nasa.gov/nwo/mio/cargo/ipip/web/documents.shtml

13. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 13 Call for IPiP Requirement Request Forms (Continued) Form completes on SharePoint site and saves a copy. User clicks Save for Later or Submit (at bottom) −Attach supporting documents – test reports, etc.- directly on the form −Limits to file size are not known. Compress files by conversion to PDF. −‘Save for Later’ allows return at a later time to allow time to collect information − After click ‘Submit’, only IPiP Engineers may change IPiP may directly send end item providers send a Word file to complete an IPiP RRF Completed IPiP RRFs maintained on IPiP Website under IPiP Reference tab, “IPiP Requirement Request Forms” Call for IPiP RRFs at respective IMTs at I - 8 mos and via email through IMT DL –IPs ESA and JAXA IPiP RRFs and draft Plug-In Plans are due I- 4 mos per OIP Sample IPiP RRF also under IPiP Reference tab Accuracy and timeliness of data received affects ISS Plug-In Plans

14. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 14 Call for IPiP Requirement Request Forms (Continued) IPiP needs ISS community input! IPiP RRFs are used in responses to chits and in plans of where to locate end items Timely manner: the earlier the better especially for difficult requirements –Criticality 1 –Real estate intensive –High power consumption, usage rate, duty cycle, etc. Completed contact information for end item owner and alternate NOTE: requests to use black, cobalt, or emerald bricks, laptops, USB cables must go through the CRCP; https://iss-www.jsc.nasa.gov/nwo/ppco/cbp/web/crcp.shtml Contact Stephen Hunter at 281.244.7684 Notifying the CRCP does not mean that IPiP is notified.

15. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 15 Call for IPiP Requirement Request Forms (Concluded) Technical data –Electrical and data interfaces –“How it works” –“When do you need to be connected?” –Test reports, qualification or certification reports (GCARs, TIAs, etc.) Previously flown end items and refurbished end items both need a new IPiP RRF to document end item/data configuration changes (electrical characteristics, cables required, contact information, etc.) Tendency has been to submit incomplete forms New form is now NINE questions, down from 24. If End Item Provider POC has information, can cut down time to less than 30 minutes Accuracy and timeliness of information directly related to quality of ISS Plug-In Plans and of real-time responses

16. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 16 Questions for Hardware Providers The IPiP Engineer will send End Item Provider this list of questions as a check to determine if an IPiP RRF needs to be completed: End Item Name / ISS Part Number On ISS at the beginning of Increment 47/48? Y / N If NO, expected arrival flight Operates External to ISS? Y / N If YES, do not complete; IPiP considers only internal power requirements Operates only on an ExPRESS Rack? Y / N If YES, do not complete; IPiP nominally considers power through UOPs and SUPs IP End Item? Y / N If YES, has the end item received the appropriate JCCT Certificate? If NO, has the end item begun the JCCT certificate process? Expected location of operation (module and location code) Certification complete? Y / N If NO, expected completion date (certification is completed after successful end-to- end qualification and functional testing and paperwork is complete)

17. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 17 Questions for Hardware Providers (continued) Operating in Increment 47, 48, or 47/48? Power required (120 VDC, 28 VDC, 120 VAC, other) Powered by batteries? Y / N If YES, are batteries solely AA, AAA, C, D Cell, etc.? If YES, the equipment is not on the Plug-In Plan If YES, does the charger require 120 VDC, 28 VDC, 16 VDC, or 120 VAC? If YES, is certification complete for the charger Y / N? Expected duration of operation (e.g., 24/7; three hours per week; 6 hours per Increment, which day(s), etc.) Answers on this set of questions determine if end item needs to be on the Plug-In Plan. If not, Photo-TV or ExPRESS Rack will respond to your requirements

18. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 18 Manifest Request for On-Orbit Power

19. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 19 Blank IPiP Requirement Request Form (top portion)

20. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 20 CONCLUSION IPiP Plug-In Plan Recommends configuration of US portable loads to USOS UOPs and Columbus SUPs prior to each Increment Collects Utilization Table inputs from OC/OZ : Inc – 12 mos Collects IPiP RRFs - input in question-and-answer format - from OB, OC/OZ, OD, FOD, POIC, and IPs to produce nominal IPiP products: –Increment Schematics and Contingency Tables: Inc – 8 mos to Inc – 3 mos –Crew training: Inc ~ 3 mos IFF crew requests to support IOR (Inc – 4 mos), JOP (Inc - <1 mo), and real-time questions Provides real-time support for chits and other issues Identifies requirements, replacement hardware, sources for new end items, manifests equipment, and then projects the requirements, all to meet strategic and tactical requirements Accurate information on IPiP RRFs provided in a timely manner directly relates to quality of ISS Plug-In Plan and of real-time response

21. MISSION AND PROGRAM INTEGRATION (MAPI) CONTRACT | 21 Glossary End Item - Per SSP 30599, Safety Review Process, Rev F, February 2015 (in signature cycle): a final combination of end products, components, or materials that is ready for its intended use, used to identify payloads or other hardware. ExPRESS Rack - EXpedite the PRocessing of Experiments to Space Station: Racks which provide electrical power, water, and a stable platform for usually small experiments GCAR - Government Certification Acceptance Report: A document which provides test results and operational limits on ISS end items to certify an end item may operate on ISS MIDAS - Mission Integration Database Application System: the official repository for ISS Program data. It contains data for all parts launched to and returned from the ISS and includes part number, OpNom, mass and dimension data, and hazard and toxicity codes. MIDAS contains manifests for each vehicle that launches or has launched to the ISS. Portable load: any IVA-operated end item that operates from a UOP or SUP that uses 120 VDC or less or 120 VAC USOS - United States Operating Segment: All ISS modules other than those in the operated by the Russian Space Agency; US Lab, Nodes, Cupola, US Airlock, Columbus, JEM RSOS - Russian Operating Segment: All ISS modules other than those operated by NASA, ESA, and JAXA; FGB, Service Module, MLM, MRM1 and 2 TIA- Tailoring/Interpretation Agreement: processes exceptions or interpretations of requirements to assure that these meet the intent of the requirement.