SSP_50627-RevA.docx

Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration Process for Future Portable Loads

International Space Station Program

Revision A

October 2017

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract Number: NNJ12GA46C

SSP 50627

Revision A

REVISION AND HISTORY PAGE

SSP 50627

Revision A

PREFACE

Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration Process for Future Portable Loads This document describes the process for integration of International Space Station (ISS) secondary power portable loads that utilize ISS Utility Outlet Panel (UOP) and/or Standard Utility Panel (SUP) outlet power for operation at a given Increment.

This document was developed and is maintained by the Systems Engineering and Integration Office of the International Space Station Program Office. The initial baseline release of this document is under the control of the Space Station Program Control Board (SSPCB). The SSPCB delegates control and approval authority for future updates and/or revisions to the Multilateral Systems Engineering and Integration Control Board (MSEICB).

See Directive Approval

10-18-17

Jeffrey A. Arend Manager, Systems Engineering and Integration Office National Aeronautics and Space Administration

Date v

INTERNATIONAL SPACE STATION PROGRAM

Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration process for Future Portable Loads

CONCURRENCE

October 2017

Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration process for Future Portable Loads

CONCURRENCE

October 2017

ESA/HSC-IC

head of columbus operations division org

See Directive Approval signature

DATE

ESA/HSO-ICF

HEAD OF FLIGHT OPERATIONS OFFICE

ORG

See Directive Approval signature

DATE

Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration process for Future Portable Loads

CONCURRENCE

October 2017

TABLE OF CONTENTS

APPENDIX

TABLE

FIGURE

Introduction This document describes the process for integration of US and International Partner (IP) International Space Station (ISS) secondary power portable loads that utilize ISS Utility Outlet Panel (UOP) and/or Standard Utility Panel (SUP) outlet power for operation during a given Increment.

This document defines and controls the requirements and processes that End Item Providers (EIPs), also known as “hardware owners,” – system and payload hardware developers and their sponsoring organizations (e.g., Codes OB, OD, and OZ) - shall follow to introduce new portable loads requirements to the ISS Plug-in Plan (IPiP) team in support of the pre-Increment planning and development of IPiP integrated product development. The integration requirements delineated in this document are mandatory and are subject to Certificate of Flight Readiness (CoFR) endorsement. End Item Providers compliance with these requirements ensures all portable loads are allocated UOP and/or SUP outlet(s) for ISS operation during their respective Increments. This document is under the control of the Space Station Program Control Board (SSPCB). The SSPCB delegates any changes or revisions to the Multilateral Systems Engineering and Integration Control Board (MSEICB).

PURPOSE

SSP 50627, Generic International Space Station (ISS) Plug-in Plan (IPiP) Integration Process for Future Portable Loads, documents a process for End Item Providers to follow to introduce and document portable loads requirements to the IPiP to support IPiP CoFR endorsement efforts. Portable loads requirements constitute hardware devices that will receive power directly from the ISS UOPs and/or SUPs or downstream of UOPs and/or SUPs via power strips (e.g., PS-120 Junction Boxes, ISS Power Inverter, etc.) and/or a power converter. This allows IPiP engineers to assess new requirements and incorporate those requirements into the IPiP configuration, ensuring proper allocation of new requirements to power outlets for their operation onboard ISS.

SCOPE

SSP 50627 establishes the integration processes that EIPs should follow in order to inform the IPiP team of new/refurbished portable loads that will be operated in future Increments on UOPs and SUPs. This includes all Systems hardware connected to UOPs and SUPs and their support hardware as well as aisle-deployed payloads. The IPiP data collection for aisle-deployed payloads is integrated into the ST&E process per SSP 57057 ST&E Integration Flow. Hardware designed for Expedite the Processing of Experiments to Space Station (ExPRESS) Racks, or Internal Camera Ports (ICPs) and hardware designed or designated for use solely in the Russian Segment are outside of scope of this document and do not require an IPiP response from those EIPs. The requirements and process to use portable hardware in the Russian Segment is documented in SSP 50578, International Space Station Cargo Certification Process, and is coordinated through the Joint Cargo Certification Team (JCCT). The IPiP team integrates the requirements for all end items and incorporates requirements to the respective Increment’s IPiP configuration, baselined at the appropriate Increment Joint Operations Panel (JOP) and delivered to the Plug-in Port Utilization Officer (PLUTO) for subsequent real-time implementation onboard ISS.

PRECEDENCE

If there are any discrepancies between the information contained in this document and documents identified in Section 2.0, Documentation, in Section 2.0 shall take precedence.

VERB APPLICATION

The use of the verb “shall” indicates a requirement which must be implemented and its implementation verified. Use of the verb “will” indicates a statement of fact and is not verified. Use of the verb “should” indicates a design goal but is not formally verified. “Shall” and “must” are synonymous terms denoting requirements.

1-2

DOCUMENTATION

APPLICABLE DOCUMENTS

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are applicable to the extent specified herein. Current versions of these documents are in the Electronics Document Managements System.

REFERENCE DOCUMENTS

The following documents contain supplemental information to guide the user in the application of this document. These reference documents may not be specifically cited within the text of this document.

November 2004

SSP 30482,

Volume 1 Electrical Power Specifications and Standards, Volume 1: EPS Electrical Performance Specifications

SSP 30482,

Volume 2 Electrical Power Specifications and Standards, Volume 2: Consumer Constraints

Volume 1: Station Program Management Plan

SSP 52051,

Volume 1 User Electric Power Specifications and Standards, Volume 1: 120 Volt DC Loads

SSP 52051,

Volume 2 User Electric Power Specifications and Standards, Volume 2: Multi-Segment, Portable, 28 Volt DC Equipment

2.0 3-2

ROLES AND RESPONSIBILITIES

The IPiP team coordinates the integration process for portable loads which will receive secondary power from the ISS during an upcoming Increment. The PLUTO team assists the IPiP team by providing real-time inputs to the integration process of these portable loads to keep the IPiP inputs in line with the real-time plan as executed. After the process is concluded, PLUTO takes inputs from the IPiP team and incorporates them into the real-time plan for the upcoming Increment. The IPiP Team coordinates with the various EIPs that provide portable loads inputs to the IPiP team and works to resolve issues with the Increment Management Team (IMT). The EIP provides technical and logistical support to the IPiP team before deployment of portable loads. The EIP is also responsible for the technical accuracy of the information it supplies and keeps the IPiP and PLUTO teams apprised as to when and how to deploy its hardware and to provide resolution of any issues that may arise during real-time operations as required.

ISS plug-in plan (IPIP) INTEGRATION process The following paragraphs describe the step-by-step process in which the IPiP team coordinates and integrates with all the necessary disciplines for developing an accurate and effective ISS Plug-In Plan.

CALL FOR IPIP requirement request forms IPiP engineers integrate, assess, process, and document submitted requirements to allocate appropriate UOP and/or SUP outlet(s) for those new/refurbished portable loads. (See Figure 3.1.1-1, Utility Outlet Panel (UOP2 at LAB1OS4) for a representative UOP, and Figure 3.1.1-2, Standard Utility Panel (SUP4 at COL1FD4) for a representative SUP, and Appendix F, IPiP UOP and SUP Capabilities, for basic specifications). The development and contents of the IPiP configuration is a direct result of the participation of EIPs by submission of portable loads requirements to the IPiP team. EIPs/sponsoring organizations (e.g., OB, OD, OZ) shall follow the IPiP integration process to ensure that their hardware will be included in the baseline product to support the CoFR process.

figure 3.1.1-1 Utility Outlet Panel (UOP2 at LAB1OS4)

Figure 3.1.1-2 Standard utility panel (sup4 at Col1fd4)

NON-PAYLOADS PROCESS

The IPiP team begins the formal integration process for non-payload portable loads at Increment start minus twelve months (Increment (I)-12 months (m)) to coincide with the start of Increment Planning. The IPiP Engineer assigned will have a First Call for IPiP Requirement Request Forms (RRFs) at an Increment Management Team (IMT) meeting. The IPiP Engineer requests IMT representatives to coordinate requirements with their respective organizations to coordinate with EIPs working on all projects involving new and refurbished hardware impacting UOPs and SUPs. The IPiP Engineer supplements the meeting with an email to the IMT distribution who might have knowledge of EIPs that are not aware of the requirement to complete and IPiP RRF. [CCM1] Coordination of systems hardware with the Internal Volume Configuration Working Group (IVCWG) [CCM1] may have occurred prior to this First Call. The process may involve payload end items, systems hardware, and technical demonstrations (AKA, “tech demos”).

Work continues at I-8m when IPiP Engineers present the “Last Call for IPiP RRFs” at the corresponding IMT. This “Last Call for IPiP RRFs” reiterates the message of the First Call for EIPs to introduce requirements for new and/or refurbished portable loads to IPiP engineers via the IPiP RRF if they have not already done so and provides a list of end items that have responded to date.

Figure 3.1.1.1-1 depicts an expected timeline of the IPiP Non-Payload Integration Process Flow. The dotted line indicates that the crew may elect not to have an IPiP crew training briefing for that particular Increment.

3-10

Figure 3.1.1.1-1 IPIP non-payload INTEGRATION PROCESS nominal timeline

PAYLOADS PROCESS

EIPs complete the On-Orbit Utilization Requirements Table in Annex 5, Payload Tactical Plan, according to the schedule supplied by OZ/OC for that Increment. After OZ/OC assessments begin at approximately I - 10 m, IPiP Engineers may collect data from the OZ Requirement Baseline and Integration (ORBIT) or EMBARK databases for each payload that requests secondary power. Annex 5 inputs will be baselined nominally by I - 5 m. This is one indication that a payload might be a portable load and part of the ISS Plug-In Plan.

IPiP integration for Payloads follows the process established in SSP 57057 ISS Program Science, Technology and Exploration (ST&E) Integration Flow to fly ST&E experiments to ISS as soon as possible, when they can be ready. Payloads will follow the template in SSP 57057 Rev F (and subs), Section 4 Figure 4.0-2, ISS Program ST&E Integration Flow High-Level One-Pager, which provides a high-level overview of the key milestones the ISS Program supporting organizations implement during the ST&E Integration Flow Phases to support payload customer integration to ISS. Sync Points at the conclusion of each Phase assess the progress of the payload integration yet do not preclude a payload from progress through the ST&E Integration Flow.

Individual Payloads may not support the I-minus 12 month First Call for IPiP RRFs or any other established IPiP milestones since each payload will have customized ST&E Integration milestones and schedule. To ensure power-related data collection from all aisle-deployed payloads, IPiP reviews Payload Interface Agreements (PIAs), attends kickoff meetings, attends and reviews presentations from the Payload Topology Forum (PTF), formally reviews Payload Integration Tasks and Assignments (PITAs) from the PTF to approve or comment on Payload analysis for every payload. Power-related data collection and analysis may occur at any time before or after the Joint Operations Panel baseline of the ISS Plug-In Plan for the upcoming Increment. IPiP integration will use the ISS Research Plan (updated continuously) and the payload topology plans synchronized with the Research Plan to identify payload requirements by increment. The complement information coupled with payload specific requirements collected via the ST&E Integration process allows IPiP to integrate payload requirements into end-item Increment plan.

Note that not all Payloads that receive power are under the purview of the ISS Plug-In Plan. Payloads that are solely powered on ExPRESS Racks or receive power from ICPs have processes through their respective organizations. To gain cognizance of any end item that requests power, IPiP is a member of the ST&E Core Integration Team. This enables IPiP to determine if a payload is aisle-deployed and if so, to guide it through the IPiP process.

The first step is that IPiP works with a Payload Developer (PD) during the ST&E Integration Flow Conception Phase to identify power requirements (120 Volts Direct Current (VDC) or less or 120 Volts Alternating Current (VAC) from a UOP or SUP). This typically occurs prior to the Payload Kickoff Meeting and should be complete prior to Sync Point Zero.

IPiP involvement with the ST&E process continues during the ST&E Integration Flow Plan and Prepare Phase, just prior to the Interface Requirements Baseline (IRB). At this point, the IpiP Engineer will provide a link the SharePoint site to direct the PD to complete the IpiP RRF, which may be a preliminary version. IPiP Engineers will review the form and note any deficient items. This should be completed prior to Sync Point One.

Involvement continues during the ST &E Integration Flow Design and Analyze Phase just prior to the Preliminary Design Review, where any IpiP RRF deficiencies should be satisfied. Since the design should be 10% complete, data items such as duty cycle, location, and modes of operations should be known and would have been provided to the PTF and on the IPiP RRF. A final update with a Plug-In Plan location will be made after the Plan and Prepare Phase Critical Design Review, where the overall design should be 90% complete. This should be completed prior to Sync Point Two.

Since the ST&E flow is customized for every payload customer it is possible that some power requirements will be identified very close to or after increment execution begins. These payload’s power requirements will be integrated using the standard Flight Operations Directorate (FOD) chit process. IPiP Engineers use any power-related data from an IPiP RRF to ascertain if the payload is safe to operate aboard ISS though more data may be needed. The PD shall be available to provide and verify such data. If the data is not provided, the FOD process results in an Open chit which will not allow to end item to be connected to the ISS Secondary Power/Data Subsystem.

Figure 3.1.1.2-1 depicts an expected IPiP ST&E Integration Process Flow. Sync Points are located within fluid spaces independent of Program milestones to indicate the IPiP process accepts inputs from Payloads as they occur.

Figure 3.1.1.2-1 IPIP ST &E INTEGRATION PROCESS nominal timeline CALL FOR IPIP requirement request forms – international partners An exception in the coordination timeline is for inputs from IPs. IPs receive the ‘First’, or “Last Call for IPiP RRFs” at the same time as other EIPs. However, IPs control deployment of portable loads in their modules. For that reason, Operations Interface Procedures (OIPs) for each IP list the deadline for Plug-In Plan configurations for the Japan Aerospace Exploration Agency (JAXA) Japanese Experiment Module (JEM) and for the European Space Agency (ESA) Columbus module as Increment Operations Review (IOR), at I – 4m, when all organizations must provide their procedures and facilities readiness for ISS mission operations for the upcoming Increment. –See also Figure 3.1.1.1-1, IPiP Non-Payload Integration Process Nominal Timeline.

Figure 3.1.1.1-1 depicts an expected timeline of the IPiP Integration Process Flow. The dotted line indicates that the crew may elect not to have an IPiP crew training briefing for that particular Increment.

submitting THE IPIP requirement request form The IPiP RRF requests all of the data IPiP engineers require to allocate ISS portable loads to UOPs or SUPs for the operation of portable loads. It further guides the EIPs to follow the proper hardware certification process for use with UOP/SUP outlets including applicable interface certificates, ensures allocation of outlets to loads and prompts the EIPs to coordinate with appropriate organizations for support equipment (e.g., cables, power converters or inverters, etc.) to support the end-to-end configuration of those loads. If executed in a timely manner, the IPiP RRF allows sufficient time for all these preparations to support real-time operations.

Internal Vehicle Configuration and MCC specialists use IPiP RRFs for responses to chits and in plans of where to locate hardware. These forms should be received by the IPiP team in a timely manner: especially for difficult requirements as Criticality 1 hardware, equipment that is real estate intensive, has high power consumption, usage rate, duty cycle, etc. IPiP RRFs require complete contact information for EIP and backup, complete technical data, test reports, qualification and/or certification reports.

Previously-flown hardware may need a new IPiP RRF to document hardware/data configuration changes (electrical characteristics, cables required, or contact information) or after refurbishment.

An EIP may obtain an IpiP RRF in two ways. The first is through the link to the IpiP RRF SharePoint site at, https://iss.sp.jsc.nasa.gov/Mapi-Ext/SitePages/Home.aspx.

The second method is for an EIP to complete a transactional or organizational queue, formerly known as a Manifest Request (MR), for an end item. A requestor indicates on the transaction form whether the hardware item requires onorbit power from the ISS Electrical Power System (EPS). This initiates an email to the IPiP Engineers with the following information: Transaction number and title, name, telephone number, and email address of the Submitter and of the Initiator (requestor), the date, and the Increment and timeframe for operation for the end item. The IPiP Engineer will then contact the requestor to send the above link to the EIP.

SharePoint notifies the IPiP Team that an IPiP RRF has been submitted. EIPs may attach supplementary information such as requested digital photos of the end item, drawings, certification documents, etc., directly to the form.

Access the site as follows: Click on the above link, go to left column, select “Vehicle Configuration,” scroll down to “IPiP” and move the cursor slightly to the right to “IPiP RRFs.” A list of all stored IPiP RRFs will present. Click on “new item” (all lowercase) to create a new form. To view a previously submitted form, scroll down the list; titles are on the left. Click on a title to see the submitted form.

A user may search on data such as hardware name, contact information, part number, voltage, maximum current, cable length, and whether a test report has been submitted. Clicking on the highlighted appropriate title in the IPiP – All Forms list allows simple sorts across the top of the form. A user may run the cursor over the attributes at top (beginning with HWName1, followed by Date Completed to its right continuing on to the right) to review selected responses to IPiP RRF questions).

All entries must be complete and answered in full. Accuracy and timeliness of information are directly related to quality of IPiPs and of speed of realtime responses to chits and other queries. If all requested data is not available, the EIP may save the form until all requested data is collected.

Concurrent with the Calls for IPiP RRFs, IPiP engineers send out an email with Incrementunique directions and deadlines, and post a copy of the text of that email to the IPiP website product page for the upcoming Increment.

CERTIFICATION OF PORTABLE LOADS IN RELATION TO IPiP REQUIREMENTS Responsibility lies upon EIPs to ensure the new/refurbished portable loads which will receive power from UOP and/or SUP outlets, either directly or downstream via a power converter (e.g., Cobalt Brick) or ISS Power Inverter, to undergo the proper testing certification process in order to assure the new/refurbished portable loads are electrically compatible with the UOPs and/or SUPs. This certification includes verification that interface certificates are in place to allow use of the item in the designated configuration. The new/refurbished portable loads shall conform to applicable ISS power quality and electromagnetic interference/ electromagnetic compatibility standards as required by SSP 52051, User Electric Power Specifications and Standards, Volume 1: 120 Volt DC Loads or Volume 2: Multi-Segment, Portable, 28 Volt DC Equipment, ensuring the loads will function properly without causing damage to the outlets or the ISS Power/Data Subsystem.

COORDINATION OF SUPPORT EQUIPMENT NEEDED FOR END-TO-END CONFIGURATION OF PORTABLE LOADS EIPs shall properly coordinate efforts with necessary organizations to guarantee all necessary support equipment (e.g., cables, power converters, ISS Power Inverters, etc.) needed for the portable loads end-to-end configuration are available at the time and location requested.

Presenting the ISS PLUG-IN PLAN CONFIGURATION IPiP engineers post schematics with a proposed plan to the IPiP website. Schematics are top-level representations of the UOP and SUP, power and data lines, and hardware. They picture 120 Volts Direct Current (VDC) power lines from UOPs and SUPs, power lines to and from 28 VDC or 16 VDC power supplies, and to and from the Power Strip (PS)-120 or ISS Power Inverter [Appendix G, Note 1]. Schematics also display ISS location codes, A-Clocked outlets, time share arrangements, alternate configurations, and items that have not completed certification, but should complete it by a specific time. Some may display data buses. Schematics are top-level graphical depictions and do not represent physical location or size, orientation, placement, or dimensions of support equipment or lengths of cable runs.

Generally, one schematic page displays portable loads for one UOP or SUP. Each portable load has a label number that is consistent for each time the equipment appears on a schematic. A page may contain Notes Flags which refer important information which would require a large text box. The graphics display a general time frame for use of the equipment. Location codes are to the general location of the UOP or SUP and do not display to the rack level or to where hardware would be located, To accommodate all the portable loads that require voltages supplied by the ISS Secondary Power/Data Subsystem and regulated 28 VDC or 16 VDC, etc., the Plug-in Plan includes PS-120 Junction Boxes, ISS Power Inverters, Ku-Band Power Supplies (28 VDC), and cobalt, emerald or black bricks (16 VDC). This support equipment and cables distribute voltages used by the portable loads and provide connectors or outlets for power.

However, the number of portable loads usually exceeds the number of available outlets at a given time or location. This is due to the actual number of portable loads and the fact that some portable loads that must be used concurrently with other portable loads which require the same voltage and must be operated in the same physical location. Other portable loads may operate with other hardware sequentially and due to crew time, stowage, or logistical reasons, the portable loads should not relocate. Accommodation of portable loads in the Plug-In Plan by utilizing one piece of support equipment to supply multiple users is called timesharing. Schematics depict timeshared equipment with a dashed line from the cable or connector that is common to each load, to the load itself.

IPiP engineers also produce Contingency Tables for United States On-orbit Segment (USOS) modules, except Columbus or the JEM. These tables provide guidance to PLUTO on operations in case an electrical channel fails [Appendix G, Note 2]. Each entry in the Contingency Table contains the location of the load in a habitable module by location code, the channel upon which that load resides, and instructions as to where the load should go if the channel is down [Appendix G, Note 3]. PLUTO approves these table entries for United States (U.S.) modules. IPs provide tables for their modules [Appendix G, Note 4]. The Russian Segment does not publish Contingency Tables in the same form as those for the USOS. Neither IPiP nor PLUTO include or review Russian On-Orbit Segment (RSOS) Contingency Tables.

PLUTO may use data in these tables to direct the crew to keep critical portable loads powered. Schematics and Contingency Tables are part of the IPiP configuration called “WORKING DATA,” and the address on the IPiP website at https://iss-www.jsc.nasa.gInwo/mio/cargo/ipip/web/index.shtml lists these files as such.

BASELINE of ISS PLUG-IN PLAN REQUIREMENTS The Increment IPiP configuration depicts the subscription of all UOP and SUP outlets for all the portable loads operated throughout an Increment. The respective Increment IOR and the JOP endorse the configurations by CoFR statements that document formal notification that the approved Increment IPiP configurations and are ready for real-time implementation.

After IPiP engineers have coordinated requirements for ISS portable loads for the upcoming Increment, the IPiP is ready to baseline. IPiP engineers post the schematics and Contingency Tables for community review on the IPiP website at https://iss-www.jsc.nasIov/nwo/seio/vcer/ipip/web/index.shtmlI, and then arranges for the Increment Flight Director (FD) to convene a JOP.

The purpose of the JOP is to examine the configuration proposed and determine if it meets the operational criteria for the upcoming Increment. All IPiP RRFs must be received and any open certification paperwork must be closed. If either of these is not the case, IPiP engineers take an action to close the review item. If all paperwork is closed or actions assigned, the FD takes a poll of FOD panel members. If panel members concur, the FD declares the IPiP configuration for that Increment as baselined.

After baseline, the IPiP engineer posts the baseline configuration to the IPiP website, and changes the designation on the IPiP website to “APPROVED DATA.” The IPiP engineer prepares a brief CoFR letter addressed to the lead CO55 Group (PLUTO) Lead, signed by the National Aeronautics and Space Administration (NASA) IPiP Lead or their designate, declaring that the IPiP configuration has been posted on the IPIP website listed as “APPROVED DATA.” The IPiP engineer may deliver this letter in person or electronically. At this time, PLUTO assumes control over the IPiP configuration, and it becomes the “Plug-In Plan (PiP).” [Appendix G, Note 5] PLUTO loads baselined data into the Plug-In Port Allocation Table and PIP Tool to assist in real-time operations and analysis.

See Appendix E, Sample CoFR Letter.

The pre-Increment phase ends with the baseline of the PiP. However some hardware may not be certified prior to the start of the Increment. Some EIPs provide hardware after baseline for any number of reasons. The process to integrate such hardware into the real-time plan is the established FOD chit process. In some instances, such hardware may be launched yellow-tagged; these exceptions will be noted in the baselined plan graphic by a dashed green or red oval around the end item and an asterisk. However, the fact that some hardware that has been identified as requiring power from a secondary source may not be certified prior to the start of the Increment does not preclude baseline of the PiP configuration.

Appendix a – Acronyms and abbreviations

A-1

APPENDIX b - GLOSSARY OF TERMS Certificate of flight readiness A process that certifies all organizations (NASA and contractor) have successfully completed their responsibilities and products per their individual implementation plans prior to flight.

Contingency Table Excel files that recommend to PLUTO to direct the crew which critical portable loads to keep powered or where to locate them in case an electrical channel fails.

ELECTRICAL POWER SYSTEM

The ISS EPS provides overall electrical power generation, control, storage and distribution to system loads and payloads.

EMBARK

Not a NASA acronym. The primary data entry interface for the ISS Customer.

END ITEM

Per SSP 30599, Safety Review Process, Rev F, February 2015, a final combination of end products, components, or materials that is ready for its intended use, used to identify payloads or other hardware. In this document, also known as a “portable load.”

End Item Provider A discipline engineer, principal investigator, or organization that owns a requirement for an item considered a deliverable, the ownership of which transfers to NASA. Also known as “Hardware Owner.”

Hardware owner See “End Item Provider”.

Increment Operations Review A major review between the ISS Program and the organizational elements responsible for exact operations planned for the Increments. The IOR assesses procedures and facilities readiness for ISS mission operations and assures that the ground facilities and operational documentation is ready to support the final phase of training for both flight and ground personnel, as well as executing the real-time operations planned for the Increment. It is held at I - 4m, chaired by the Increment Manager (IM), and attended by the IMT members and an attendance list determined by the IM.

INTERFACE CERTIFICATE

A certificate that documents and gives approval for hardware to be used in another IP module. The certificate will be reviewed and approved by each respective IP.

ipip requirement request form A form required to be completed by an EIP that identifies the point of contact, OpNom, electrical requirements and characteristics, expected duty cycle, and required timeframe of usage. EIPs also supply a digital photograph for the portable load. EIPs should complete the necessary IPiP RRFs no later than I - 6m, except IPs, which, per their respective OIP, must complete the necessary IPiP RRFs no later than I - 4m.

ISS Power/Data Subsystem The portion of the secondary power distribution system, nominally regulated at 120 volts, that provides power to portable loads and may provide data to or receive data from portable loads via 1553 and Ethernet data buses.

Joint Operations Panel (Increment-Specific) A forum to integrate and coordinate the efforts to resolve operations and technical issues and to develop of flight techniques related to ISS design, assembly, and operations for all IPs (as applicable), chartered multilaterally by the MMIOCB, chaired by FOD FDs, the IM, and consisting of members from each IP. Its responsibility is to determine and baseline the techniques to accomplish various flight operations requiring integrated utilization of trajectory, attitude control, Station systems management, Station crew, and Mission Control Center support. Additionally, the JOP will make recommendations to the responsible Program elements and propose hardware and software changes that are designed to improve these operations. IPiP presents the final configuration at the Increment-specific JOP, which contains inputs from IPs, MOD, the IMT and NASA disciplines, for baseline. For IPiP, this usually takes place at ~ I-1m.

ORBIT

A web-based software system-of-systems intended to provide ISS payload developers with a single-source location for input and output of information required during the initial payload integration process for the purpose of launching, operating, and/or returning payloads on the ISS. Development of the ORBIT suite of applications is under the direction of JSC Code OZ6, Research Integration Management.

ORGANIZATIONAL QUEUE

Or, transactional queue. A list of end items owned by an organization, for example, Code OD, to be delivered to the ISS during a future period of time. Hardware may not necessarily be assigned to a specific flight.

Portable Load An Intravehicular Activity (IVA)-used, electrical equipment end item connected directly or indirectly to the EPS secondary distribution (ISS Power/Data Subsystem via UOPs or SUPs), or their support equipment, that will not receive power from an ExPRESS Rack or Internal Camera Port (ICP), that uses 120VDC or less or 120VAC in the US Segment. Portable loads include laptops, computer peripherals, environmental monitoring equipment, food preparation devices, etc. A portable load may be a payload, but not every payload is a portable load. In this document, also known as an “end item.”

Power Channel A portion of the EPS primary power system that provides from 133-177 VDC, 160 VDC average, at ~31 kW. ISS has eight ISS Power Channels, two channels per solar array wing.

Schematic Top-level PowerPoint representations of the UOP and SUP, power and data lines, and hardware. Schematics depict each UOP by outlet (J3 or J4) and SUPs by outlet (J01, J02, or J03, and sometimes J08). They also picture 120 VDC power lines from UOPs or SUPs, power lines to and from 28 VDC or 16 VDC power supplies, and to and from the ISS Power Inverter, Schematics also display ISS location codes, A-Clocked outlets, time share arrangements, alternate configurations, and items that have not completed certification, but should complete it at a specific time. These are graphical depictions and do not represent physical location within a module, lengths of cable runs, or hardware size, orientation, or placement.

Standard Utility Panel (SUP) A panel that provides crew members with direct access to secondary power, 1553 and Ethernet data bus connections to allow the use of portable equipment at various locations in the Columbus module. SUPs have three outlets that provide 120 VDC at 10 amps each outlet, J01, J02, or J03. Each SUP provides one outlet for Ethernet connection at J03.

ST&E Integration Per SSP 57057 ISS Program Science, Technology and Exploration (ST&E) Integration Flow, a process to fly ST&E experiments to ISS as soon as possible, when they can be ready. For the IPiP process, Payloads individually must follow a Conception Phase, a Design and Analyze Phase and a Plan and Prepare Phase, the end of which correspond to Sync Points which review the progress of the Payload.

Timesharing Use of a UOP, SUP, PS-120 Power Strip, ISS Power Inverter outlet or brick by more than one user over a short period of time. IPiP engineers arrange timesharing independent of most users. Certain hardware is not conducive to timesharing by virtue of its size or volume, electrical characteristics, power interface design, location, amount of current drawn, requirements to be left undisturbed, hardware has no ON/OFF switch, or available outlets have mismatched data interface requirements. These cases may limit timesharing. PLUTO may also plan timesharing for real-time operations as the need arises.

Utility Outlet Panel (UOP) A panel that provides crewmembers with direct access to secondary power, 1553, and Ethernet data bus connections to allow the use of portable equipment at various locations throughout the Node 1, 2, and 3, Cupola, Airlock, U.S. Lab, and JAXA modules. UOPs in the U.S. Lab, Nodes, Cupola, and Airlock have two outlets that provide 120 VDC at 12 amps total per panel, J3 or J4. UOPs in the JEM Pressurized Module (JPM) have two outlets that provide 120 VDC at 10 amps total per panel. Six UOPs throughout ISS provide one outlet for Ethernet connection; these are always on J4.

B-3

Appendix c - open work Table C-1 lists the specific To Be Determined (TBD) items in the document that are not yet known. The TBD is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBD item is numbered based on the section where the first occurrence of the item is located as the first digit and a consecutive number as the second digit, e.g., <TBD 4-1> is the first undetermined item assigned in Section 4.0 of the document. As each TBD is resolved, the updated text is inserted in each place that the TBD appears in the document and the item is removed from this table. As new TBD items are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBDs will not be renumbered as new items are placed in order in the document, e.g., if a new TBD comes before <TBD 4-1>, that item will receive its own unique number, but not <TBD 4-1>.

Table C-1 to be determined items

Table C-2 lists the specific To Be Resolved (TBR) issues in the document that are not yet known. The TBR is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBR issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBR 4-1> is the first unresolved issue assigned in Section 4.0 of the document). As each TBR is resolved, the updated text is inserted in each place that the TBR appears in the document and the issue is removed from this table. As new TBR issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBRs will not be renumbered.

table C-2 TO BE RESOLVED ISSUES

C-1

Appendix d – Questions for End item providers

DO I NEED TO COMPLETE THE IPIP REQUIREMENT REQUEST FORM (IPIP RRF)?

The IPiP RRF allows ISS Plug-in Plan to assign what power you need, when you need it and where you need it. It also:

Provides preliminary data for the PIP Tool and Plug-In Port Allocation Tables Provides data for troubleshooting Allows us to identify your hardware It may not be necessary to complete this form. Before attempting to complete it, it is useful to have the answers to these questions:

If the answer to Questions 3a, 4a, or 10d is YES, your hardware is not in the Plug-In Plan. If the answers change, e.g., your hardware used an ExPRESS Rack, but now requests a UOP, before your hardware can operate on ISS, you will need to draft a chit and provide the information on the IPiP RRF.

D-2

APPENDIX e - SAMPLE COFR LETTER Immediately after baseline of the IPiP at the Increment-specific JOP, IPiP engineers send a CoFR letter to the CO55 Group Lead. Figure E.1-1, Sample IPiP CoFR Letter, depicts a sample IPiP CoFR letter.

Figure e.1-1 sample ipip cofr letter

E-1

APPENDIX f - IPIP UOP AND SUP CAPABILITIES IPiP power sources are addressed below, the EIP should address any different/lower power requirements/needs by certified power converters or ISS Power Inverters and their associated cables.

f.1 Utility Outlet Panel UOPs provide crewmembers with direct access to secondary power and data bus connections to allow the use of portable equipment inside United Stated On-orbit Segment (USOS) and JAXA modules. UOPs in the Lab, Nodes, Cupola, and Airlock output 120 VDC at 12A; UOPs in the JPM output 120 VDC at 10A. Each UOP contains two outlets per unit and certain UOPs have data configurations. Reference the latest revision of D68410094-01, Electrical Power System Architecture Notebook, Pages 5-4 to 5-6, for a complete list of UOPs with their respective data capability. Figure 3.1.1-1 depicts a representative UOP onboard ISS.

f.2 Standard Utility Panel SUPs provide crewmembers with direct access to secondary power and data bus connections to power portable loads in the Columbus module. Each individual SUP outlet provides 120 VDC at 10A. SUP1 J08 and SUP4 J08 outlets provide DC supply for Video Camera Assemblies and are for ESA use only. Figure 3.1.1-2 depicts a representative SUP onboard ISS. Reference SSP 42001, Space Station Manned Base to Attached Pressurized Module Interface Control Document, Revision T, Paragraph 3.3.6.1, Attached Pressurized Module (APM)-Standard Utility Panel, for a complete list of SUPs with their respective data capability.

F-1

Appendix g - references