IRT_Processes_RevC_FINAL_Jan_2017.docx

RPWG-IRT-01

Revision DC – Sept 2016 Jan 2017

This document contains information that falls under the jurisdiction of the U.S. Department of Commerce Export Administration Regulations, 15 CFR 730-774, and is classified as EAR99. The Export, Re-export or re-transmission of this document or any of the data contained therein in violation of the Export Administration Regulations or applicable U.S. export control laws and regulations is strictly prohibited.

ii

REVISION CHANGE HISTORY PAGE

PREFACE

RESEACH PLANNING WORKING GROUP

INCREMENT RESEARCH TEAM PROCESSES

This document contains the processes used by the International Space Station (ISS) Increment Research Team (IRT) to ensure uniformity in products produced and processes used between increment to increment. The IRT is a multilateral body established to coordinate integrated science research, including ensuring the implementation of research prioritization requirements, re-planning as necessary, after the United States On-Orbit Segment (USOS) research requirements have been baselined for an increment. For the purpose of this document, the term USOS includes the European Space Agency (ESA), Japan Aerospace Exploration Agency (JAXA), and the Canadian Space Agency (CSA) research requirements as well as NASA requirements.

INTERNATIONAL SPACE STATION PROGRAM

RESEARCH PLANNING WORKING GROUP

INCREMENT RESEARCH TEAM PROCESSES

CONCURRENCE

REVISION A

Prepared by:

Book Manager ORG

Signature DATE

Signature DATE

Signature DATE

Signature DATE

Signature DATE

INTERNATIONAL SPACE STATION PROGRAM

RESEARCH PLANNING WORKING GROUP

INCREMENT RESEARCH TEAM PROCESSES

LIST OF CHANGES

MAY 2016

All changes to paragraphs, tables, and figures in this document are shown below:

TABLE OF CONTENTS

SECTION PAGE

TABLES

IRT-PRE.05 – TABLE 1 – GENERIC TEMPLATE FOR VOLUNTARY

SCIENCE IMPLEMENTATION 2-20

IRT-PRE.06 – TABLE 2 - TEMPLATE OF RESPECTIVE EXPERIMENT

IRT-EXE.07 – TABLE 6 - EXAMPLE 2 IMC/RSC-E UTILIZATION

FIGURES

IRT-PRE.02 – FIGURE 5 – SRTD PROCEDURE – INCREMENT

IRT-EXE.01 – FIGURE 7 – 4-WEEK LOOK-AHEAD UTILIZATION

PRIORITIES TEMPLATE: PRIME 3-3

IRT-EXE.01 – FIGURE 8 – 4-WEEK LOOK-AHEAD UTILIZATION

APPENDIX

i

INTRODUCTION

This document defines the operating processes for the IRT. These processes establish the operating procedures used in the real-time operations environment, near real-time operations environment, and the off-line environment to ensure timely development and delivery of data products for the integrated research program.

The IRT is a sub-team chartered by the Research Planning Working Group (RPWG) to provide research coordination, re-planning recommendations and evaluations of proposed additions/deletions/changes, and prioritizations of research requirements in order to de-conflict resources and to take advantage of any opportunity to optimize and maximize overall USOS research achievements.

PURPOSE

The purpose of this document is to provide consistent processes to conduct the IRT functions.

SCOPE

The processes defined in this document define the IRT interactions and tasks required to support the conduct of USOS research.

CHANGE CONTROL

This document is under the control of the RPWG. Changes to this document require agreement of the Multilateral RPWG (MRPWG) and will be managed by the NASA Research Planning Office (OZ5) as delegated by the Multilateral Research Integration Control Board (MRICB).

REFERENCE DOCUMENTS

1–1

PRE INCREMENT PHASE

The primary objective of the IRT activities in the near real-time environment is to use the products developed during the Tactical timeframe along with information form the real-time environment in order to actively support the science management of the USOS payload complement in a multilateral way.

IRT-PRE.01 CREW HUMAN RESEARCH COMPLEMENTS: ASSIGNMENT AND MODIFICATION

1. PURPOSE

To approve recommendations for assignment of Human Research Complements to individual crewmembers and subsequent modifications to those complements, when necessary.

2. PARTICIPANTS

IS

ISSMP ISC

*International Human Research Complement Working Group (IHRCWG) Representative designated by each Agency

3. GENERAL

As per its Charter, the International Human Research Complement Working Group (IHRCWG) is tasked to coordinate multilateral ISS human research plans for an increment in support of the MRPWG-produced Increment Research Plan (IRP). The IHRCWG also identifies inherent scientific conflicts between investigations as well as those related to scheduling of Baseline Data Collection (BDC) or other limited human resources (e.g., blood volumes over a certain timeframe on orbit). The IHRCWG, as led by representatives of NASA’s International Space Station Medical Projects (ISSMP), presents the results of its planning assessments to the IRT. This includes recommended options for resolving any issues and conflicts. The options and issues presented at IRT that cannot be resolved in this forum will be presented to the MRPWG.

4. PROCEDURE

1. Initial and Delta Human Research Complements:

a. Prior to the base-lining of the IRP for a given increment pair, members of the IHRCWG conduct meetings to develop human research complement scenarios for the increment crews, which are designed to minimize the risk of BDC oversubscription. Those scenarios, which are reviewed by the MRPWG, are submitted for approval by the various agency Institutional Review Boards (IRBs), after which Informed Consent Briefings (ICBs) are held with the crewmembers (at approximately I-12 months).

b. After the ICB is conducted and each increment crewmember’s survey of interest in human investigations is received, ISSMP will recommend a “best fit” scenario for each crewmember that maximizes the use of the crewmember’s post-flight BDC time while taking into account all agencies’ priorities. The recommendations will be discussed by the IHRCWG and, once agreement has been reached by its members, the recommendations will be presented to the IRT. If concurrence of all IHRCWG members cannot be obtained, the issue will be brought to the IRT for resolution, and subsequently to the MRPWG if necessary.

c. After the IRT has concurred upon the recommended complements, the ISSMP Increment Science Coordinator (ISSMP ISC) will contact each crewmember to obtain consent form signatures. Once signatures have been obtained, the ISSMP Increment Science Coordinator will inform the LIS and International Partner (IP) BDC coordinators of the finalized complements. The LIS then will inform the IRT members about the final status of the consent form signatures.

d. A Delta ICB is nominally planned in the I-6 to 9 months timeframe to accommodate experiments that were not ready for the initial ICB when feasible. Proposed additions will be solicited at the IHRCWG. The assessment of the feasibility of adding the BDC required to each individual crewmember’s complement will be discussed at this forum. If an addition is determined to be feasible, the agency sponsor is expected to submit a Change Evaluation Form (CEF) to add the experiment to the increment/crewmember. IRT approval of the addition is assumed with approval of the CEF. ISSMP will submit a page change notice to the IRBs, and coordinate a Delta ICB for the additional experiments. ISSMP may elect to proceed at risk with their coordination work prior to final approval of the CEF if time pressures warrant it, and approval of the CEF appears likely.

2. Reporting BDC-Related Science Issues

a. An IRT member (or IHRCWG member by way of its IRT member) shall inform the LIS if any problem occurs during pre-flight BDC that results in a science loss, which might affect future pre-flight, in-flight, or post-flight activities. This will allow the IRT to consider BDC issues during science prioritization conflict resolution, if applicable, as well as monitor science accomplishment during the pre- and post-flight phases.

b. The IRT will track any BDC science issues. This will allow the IRT to provide science priority input should BDC coordination conflicts arise and consider the “quality” or validity of the test subject in preparing priorities for the upcoming in-flight portion of the protocol.

c. The IRT, via the LIS, shall inform the IHRCWG of any IRT priority recommendations that may affect BDC planning or post-flight BDC activities. The LIS shall also inform the IHRCWG of any events that occur during on-orbit sessions, which might lead to deviations in planned post-flight BDC activities.

3. Late changes to a Human Research Complement:

All agencies are responsible for notifying the ISS Program as early as possible of any changes (e.g., deletion of experiments or portions of experiment protocols) that may affect the Human Research Complement of a crewmember. If this change frees up post-flight BDC time, it may be possible to identify another study that could fill this opening.

If such a change occurs prior to increment start (i.e., before the real-time planning stage):

1. The IHRCWG representative of the agency will inform the IHRCWG and IRT communities of the planned change.

2. Potential replacements will be examined by IHRCWG and, if any research candidates are identified that appear suitable to fill the gap, recommendations will be formulated for presentation at the IRT.

3. ISSMP will provide support in implementing the changes to the Research Complement (similar to that provided for Delta ICB additions).

If the change occurs during the real-time planning stage:

1. The agency deleting a subject from one of their human investigations will inform the LIS and the IRT community at the regular IRT telecon. This will inform all partners of an opportunity opening up and give them a chance to verify if they have any human research activities that could fill this opening.

2. The LIS will convey the information to IHRCWG by contacting the ISSMP Increment Science Coordinator.

3. ISSMP will coordinate an IHRCWG meeting to discuss options for filling the opening. If there is more than one candidate, recommendations will be discussed by the IHRCWG and, once agreement has been reached by the members, the recommendations will be presented to the IRT. If concurrence of all IHRCWG members cannot be obtained, the issue will be brought to the IRT for resolution, and subsequently to MRPWG if necessary.

4. ISSMP will provide support in implementing the changes to the Research Complement (similar to that provided for Delta ICB additions).

IRT-PRE.02 SCIENCE REQUIREMENTS TRACKING DATABASE

Note: The IRT is developing a revisioned version of this process. Once validated, this process will be modified and sent for IRT review. The final updated process will be incorporated in the next revision of the IRT Process Document.

1. PURPOSE

The Science Requirements Tracking Database (SRTD) is a multi-purpose tool developed by the IRT to better understand, analyze and track the full set of mid-level multi-lateral research requirements to manage and execute sequential research plans on the ISS. It contains quantifiable data to:

· Support pre-increment and execution phase analyses required when the baseline research plan changes.

· Support complex priority decisions when mission resources are limited.

· Quickly illustrate the multi-lateral utilization requirements remaining to execute in any given increment pair.

This procedure defines the steps the IRT will follow to build the SRTD and refine the data set(s) as research objectives and mission parameters evolve.

2. PARTICIPANTS

3. GENERAL

The SRTD is a database of intermediate-level science requirements describing the on-orbit events necessary to successfully execute the investigations and utilization tasks. Each event/session in the database is a discrete and definable piece of work for a given investigation represented by the following data:

· Target date of performance (as tied to a specific flight or crew milestone or other research event)

· Scheduling flexibility

· Spacing requirements between events/sessions (if required)

· Crew time (Prime or reserve, if required)

Developed as part of the overall RPWG Research Plan – the SRTD will be used to meet the following IRT objectives:

· Research Planning Objectives

· Justify crew time requests for the increment via breakdown of experiment and utilization facility ops requirements into mid-level and discrete events/sessions with associated crew time.

· Identify crew time resource constraints to minimize the risk of base-lining a research plan that cannot be supported with available resources.

· Identify event/session target dates, scheduling flexibilities, enabling events, and drivers.

· Tactical Phase Objectives

· Use database to perform rapid analyses and research plan requirement re-planning when increment parameters and resources change.

· Validate that detailed experiment and facility planning inputs align with baselined requirements.

· Validate that the On-Orbit Operations Summary (OOS) design supports the baselined Research Plan reflected in the database.

· Increment Execution Phase Objectives

· Track requirements remaining to be completed in the increment.

· Support development of IRT 4-week look-ahead priorities.

· Identify candidates for re-planning and requirement acceleration/deferment as resources change.

An overview of the process for building, updating and maintaining the data set in the increment-pair specific SRTD files is illustrated in Figure 1 below and described in greater detail in the Procedure Section.

Figure 1 - Generic SRTD Development Process

4. PROCEDURE

The LIS is responsible for development and maintenance of each specific increment pair based SRTD for the duration of the increment pair. The LIS will coordinate with the IRT if and when from SRTD procedure is required.

Figure 2 - SRTD Procedure - Initial SRTD Build

1. Approximately 18 months prior to Increment pair start, the MSI will build and post to the IRT Sharepoint site an SRTD template based on the flights and parameters defined by RPWG for the research planning effort.

2. IRT Members will fill out their section of the SRTD template matching their research plan 2-pager inputs.

· For experiments performed in previous increments, Partners may use/modify existing SRTD data.

· SRTD inputs for new investigations or utilization tasks can be added as research plan data inputs are developed and submitted to MRPWG.

3. Each Partner’s initial input into the increment pair SRTD is due at approximately I-13 months together with final Research Plan inputs. It should include a complete set of trackable requirements matching the research plan content confirmed by the MRPWG.

4. The MSI will collect all the Partners’ inputs and incorporate them into a single database. For all SRTD updates prior to increment start, the MSI has five working days to incorporate submitted updates into the master SRTD file. This is to ensure that the IRT and any external users always have access to the latest SRTD data set matching the most up-to-date Research Plan.

5. At approximately I-12 months, the IRT will review and provide final updates and corrections to the content of the SRTD. This will be considered the original baseline of the increment pair SRTD.

Figure 3 - SRTD Procedure - Refinement Phase

6. After baseline, each Partner is responsible for refinement and maintenance of their respective SRTD data The SRTD should be updated as follows:

a. Quarterly:

i. At I-9 and I-6 months, refine the SRTD data based on improved products and approved CEFs, if not previously incorporated.

b. Increment Milestone Updates: the Partners will provide any necessary updates of the SRTD requirements 2 weeks prior to the following:

i. Preliminary OOS Technical Interchange Meeting (TIM). Updates are required to ensure the current SRTD contains requirements that match preliminary OOS inputs.

ii. Final OOS. Updates are required to ensure the current SRTD contains requirements that match final OOS inputs.

iii. Increment Start. Updates are required to incorporate any rollovers from the previous increment pair.

c. Ad Hoc Updates:

i. Changes to Flight Program dates:

1. SRTD updates based on changes to the flight schedule will be discussed and agreed by the IRT before the SRTD master file is updated.

ii. Approved CEFs: As a minimum, each Partner is responsible for providing an SRTD update for any research plan requirement change approved via CEF. These can be bundled as required into Quarterly or Increment Milestone Updates.

iii. Refinement of operations products

1. Update SRTD with any event detail refinements (i.e. session timing constraints, flexibilities, split of events into smaller trackable parts).

Figure 4 - SRTD Procedure - Finalization Phase

7. In certain cases the IRT may choose to update the SRTD in advance of a CEF approval (e.g. known Flight Program change, or Rollovers). In these instances, the partner proposing the out-of-process update to the SRTD should inform the IRT of their intent and seek IRT consensus approval for the change.

Figure 5 - SRTD Procedure – Increment Execution Phase

8. Increment Execution Phase. Once the increment starts, each Partner will provide weekly updates to the SRTD by the close of business on Monday, or the first day of the work week. The MSI shall update the master SRTD file within the following day. Updates during real time execution will primarily report the status of requirements as they are timelined and completed. However, weekly updates shall also include any corrections resulting from any events listed in #6c above.

· If any partner does not have any updates to make in a given week (due to inactivity on-orbit and no changes to existing requirements) then no SRTD update is required. E-mail notification to the IRT regarding no updates is acceptable.

9. IRT members shall provide all necessary SRTD updates via upload to the IRT Sharepoint site or ORBIT site. This includes the results of analysis performed using SRTD data.

IRT-PRE.03 CREW SCIENCE COMPLEMENT BRIEFING

1. PURPOSE

At approximately I-10 months, the LIS briefs the Increment crew on the overall content of the USOS science complement for the increment. This process includes the guidelines and coordination for the briefing.

2. PARTICIPANTS

IS

MSI

MSI

IDM

IDM

Program Scientist

3. GENERAL

The objective of the integrated Crew Science Complement Briefing is to provide an integrated overview across the USOS to the Increment crew. The Crew Science Overview portion of the briefing includes the main objectives of two featured investigations for each Partner, a list of other high priority, high visibility, and/or complex investigations, and science information resources. Also, the Voluntary Science philosophy for the Increment is provided to the crew to introduce the Voluntary Science and task list options available to the crew for additional performance of science.

4. PROCEDURE

1. At Briefing-2 months, each Increment Scientist (IS) submits a science overview package for their Increment science complement to the LIS. The science overview package includes a description of two featured investigations, along with the associated one pager information for each.

2. The overview will cover only experiments included in the Increment Research Plan baselined by the MRICB or added to the Research Plan by an approved CEF. Only science performed across the USOS segment will be covered (i.e. non-Russian).

3. The MSI will consolidate the inputs into an integrated science overview package and send to the IRT for review and concurrence.

4. The LIS will brief the crew (and provide paper and electronic copy of overview) based on an agreed schedule with the payload training coordinator. It is left up to each IS whether to attend the crew science briefing in person or by telecon.

5. The LIS will inform IRT members of any feedback or inputs from the crew members regarding an IP specific payload, if the IP IS not in attendance. If discussed during the Crew Science Overview or as part of a dedicated Voluntary Science briefing, the outcome on crew preferences including Voluntary Science / Task List will be documented via email by the LIS to the IP IS’s.

6. If the increment changes significantly after the original science overview briefing, another briefing may be provided to the crew. Revised inputs will be required accordingly, with minimum 2 weeks’ notice of due date.

IRT-PRE.04 INCREMENT RESEARCH TEAM SCIENCE REPLANNING AFTER RESEARCH DIRECTIVE BASELINING

1. PURPOSE

To define the process of science re-planning due to increment changes generated after increment baseline but before start of the execution phase. This is typically in response to flight(s) moving in or out of an increment, but could also be the result of the addition or deletion of major tasks (e.g., EVA, crew rotation, etc.), launch delays within an increment, etc. The procedure below outlines the process to be followed by the IRT for science re-planning during the “tactical” phase of an increment.

2. PARTICIPANTS

MSI

IHRCWG

Rep*

IS Rep IHRCWG Rep* IS Rep

IHRCWG

Rep* IS Rep IHRCWG Rep* MRPWG Chair

IDM

*IHRCWG Representative designated by each Agency

3. GENERAL

During the tactical timeframe, large scale re-planning occurs through the Multilateral Research Planning Working Group (MRPWG). This process is led and coordinated by the MRPWG Chair. Once the increment research directive has been baselined and approved at the Multilateral Research Integration Control Board (MRICB), the LIS takes the lead for the daily management of the science complement in regard to changes to the complement unless the changes in manifesting are significant enough to warrant a complete RPWG re-plan of the increment. In such situation, the RPWG Chair assesses the overall impact of the changes and decides whether such re-plan should occur at the MRPWG level or at the IRT level, including the IHRCWG if applicable. The procedure for the LIS/IRT-led process is described here. The process described below applies to all types of changes to the research directive after base-lining due to ISS programmatic changes, not just flights moving in and out of an increment. The LIS can choose to abbreviate the process, if warranted by the degree of complexity of the re-planning. Science re-planning performed by IRT during the Execution phase is covered by IRT-EXE.03.

4. PROCEDURE

1. The MRPWG Chair notifies the MRPWG that due to some ISS program changes, the baselined directive needs to be changed to reflect the new direction given by the ISS Program.

2. The MRPWG Chair assesses overall science directive consequences due to the changes, and decides whether changes are worked through the MRPWG or through the IRT.

3. If the MRPWG Chair decides that changes are worked through the MRPWG, then the role of the IRT is to reformulate the multilateral payload priority list once the research plan for the increment has been re-baselined.

4. If the RPWG decides that such changes should be worked through the IRT, then the LIS convenes the IRT to re-plan the affected increment.

5. The LIS, working with the IDM, assesses the crew time consequences as a result of the change and provides a revised increment crew time allocation for each IP.

6. The LIS calls a special meeting of the IRT to ensure that all IP ISs understand the nature and ramifications of the change in the increment.

7. Each respective IRT member identifies payloads that are affected by the programmatic changes.

8. Each IRT member coordinates internally within their respective agency to determine if their original IP prioritization list requires modification, and provides new priorities to the IRT as appropriate. Each IRT member is responsible for obtaining validation of the priority changes from the appropriate agency authority.

9. The IRT meets to assess changes in the research plan, from the updated crew time allocation and priorities and formulates a modified plan.

10. The results of the updated plan are presented to the MRPWG.

11. Once the MPRWG agrees with the updated plan, formal CEFs are submitted for evaluation and processed through the nominal process. This will ensure that the implementation communities are fully aware of the changes to the Research Plan, and can identify consequences to product development.

IRT-PRE.05 ISS VOLUNTARY SCIENCE PLANNING

1. PURPOSE

Voluntary Science is a process that enables crewmembers who have an interest in pursuing optional ISS utilization activities outside of the prime science on orbit. These utilization activities are performed during the crew’s off-duty time. These activities may be options chosen from existing Program science, other Program activities, or crew-generated personal science activities. This procedure describes the process the IRT will follow to plan Voluntary Science on an Increment basis.

2. PARTICIPANTS

EPT

3. GENERAL

On-orbit Voluntary Science execution depends on the agreement of crewmember representatives and flight surgeons that its implementation will not affect the health or safety of the crew.

Voluntary Science activities are performed during personal time on-orbit. Crewmembers are asked prior to launch if they are interested in receiving Voluntary Science options during their ISS stay. Participation by the crewmember(s) is entirely voluntary and the crewmember(s) can opt out at any time with no questions asked.

Generally, a list is provided with several options for the crew to choose from. All attempts will be made to accommodate crewmember preferences for Voluntary Science activities (within existing scope and budget).

In addition to personal crew preferences (if any), activities which are candidates for Voluntary Science comply with:

4. PROCEDURE

1. The first general introduction to Voluntary Science takes place during the Crew Science Complement Briefing (IRT-PRE.03) at about 12 months prior to Increment start. Each crewmember will receive a private overview of the Voluntary Science process and objectives. At approximately I-2 months, a meeting is held with the ISS crewmember and the LIS, IDM, POM, and Program Scientist to layout options and document crewmember preferences for Voluntary Science implementation. (See “Crewmember Preferences for Voluntary Science” questionnaire.) The results of these meetings are documented via email to IRT members, operations teams, Flight Surgeon, Flight Director, and Increment Manager. Any unique crew preferences are documented in the IP specific regulation document.

2. To the extent possible, Voluntary Science options will be provided to the crew based on crew preferences indicated prior to launch, or based on the most up-to-date crew preferences expressed by the crew member once on orbit.

Once on orbit, there are two methods to provide Voluntary Science options to the crew:

1. Task List (preferred method)

• Voluntary Science activities may be added to the Task List. This is the preferred method to implement Voluntary Science. Voluntary Science activities are identified as such in the Task List.

• IRT.EXE-01 describes how to identify Task List candidates as part of the 4-Week Look-Ahead Utilization Priorities Development process.

2. Orbital Communication Adapter (OCA) message

• In this method, the planning process begins approximately 2.5 weeks in advance of the planned operations to allow time for coordination with the science and operations teams.

• Steps to implement the OCA method follow:

a) The LIS coordinates with the IDM, POM, IM, and Crew Surgeon on the potential target dates to offer Voluntary Science to the crew. The results from this coordination will be provided to the IRT for VS planning.

b) Identification and selection of candidates for a particular VS session is typically made on Tuesday, 2.5 weeks before the target date. A list of candidates is identified at the weekly IRT telecon on Tuesday. The selection of candidates occurs through discussions among the IP IS, IDM and POM and their counterparts at the Wednesday Pre-WPR meeting. Generally, the selection is based on documented crewmember specific preferences, accomplishments to date, outlook for remainder of the Increment and other considerations for optimizing the Partner balance for participation.

c) Once a list of options is decided upon, a draft Orbital Communications Adapter (OCA) uplink message is prepared by the MSI with support from the IP teams (see Example section below). Following the successful planning and coordination for the candidates, the crew is presented with the options from the OCA uplink message. This message is uplinked to the crew approximately 11 days prior to the Voluntary Science session. A response from the crew is requested by the next day’s evening DPC, or via an alternate method the crew selected in their crew preference questionnaire.

d) If the crew chooses to perform Voluntary Science activities, the option(s) chosen are supported by the appropriate agency’s control center and payload operations teams, as necessary.

Table 1 - Generic Template for Voluntary Science Implementation Using the OCA Method

Voluntary Science Session

Note: This template can be adjusted for Voluntary Science sessions offered on weekdays as necessary.

Example OCA message We have four Voluntary Science options available for you this week! Please let us know by evening DPC on Tuesday if you would like to participate. Also, for the EPO options, if Fyodor and Oleg would like to help with the demonstrations, we welcome their participation as well. And as always, your participation is entirely optional.

Option 1: Capillary Flow Experiment (CFE) – Interior Corner Flow 2 (ICF2)

Option 2: Elastic Memory Composite Hinge

Option 3: Education Payload Operations (EPO) On-Orbit Hobbies

Option 4: EPO Living Area Tour

Objective: This video will provide a simple visual tour of crewmember's personal space and will be used to produce a video program for students in grades K - 4. Students are interested in personal items, personal space, and how crewmembers create a home in space.

Questionnaire: Crewmember Preferences for Voluntary Science (This questionnaire shows the type of questions asked to the crew and may change for future increments)

Preferences are communicated among the following: ISS Commander, ISS Lead Increment Flight Director, Increment Manager, Increment Deputy Manager, Payload Operations Manager, Lead Increment Scientist, ISS Program Scientist, CB Payloads Representative, and Lead Increment Flight Surgeon, with required elements passed on to the responsible teams.

1. Do you want to participate in voluntary science (“no” is a perfectly fine answer)?

2. Do you have any preference regarding which of your crew days off you would want to participate in voluntary science? Past preferences have included:

3. What is your preferred way to start receiving voluntary science option lists? Some previous examples are below.

4. Do you have specific preferences for types of activities that should be offered whenever possible? Items to consider could be length of activity, educational interest, interest in a specific payload or discipline, etc.

5. Do you have specific preferences for how you would like to “opt-in” when selecting activities from a voluntary science option list, or “opt-out” of a given off-duty day or weekend opportunity for voluntary science after you have previously “opted-in”? (In the past this has been handled by e-mail, DPC, discussion with flight director, etc.)

6. Similarly how you would like to “opt-out” if you find once in-orbit that you need to scale back or stop participating in voluntary science? (In the past this has been handled by discussion with flight director, program scientist, or crew support.)

7. Do you have any other questions or concerns about voluntary science approach that we can try to address?

IRT-PRE.06 LOAD SHED TABLE SCIENCE RACKS PRIORITIZATION

Note: A modified version of this process is still under development, in coordination with FOD, MSFC POIC, and other applicable organizations.

1. PURPOSE

This document outlines the IRT process for the Load Shed Table Science Racks Prioritization. The intent of this prioritization is to minimize the affect than an ISS load shed event would have on the science investigations.

2. PARTICIPANTS

MSFC PRO

JSC PRO

POM

3. GENERAL

The payload/science segment of the Load Shed Table (LST) is used to make science rack/facility power-off and -on decisions in case of an emergency or a power shedding situation aboard the station. LSTs are used to react to real-time, unplanned, contingency situations that require an instantaneous reduction of channel loading. Such events could be the following:

· Loss of critical station thermal control system

· Loss of critical Electrical Power System (EPS) primary power equipment

· Maintaining energy balance, and battery State Of Charge (SOC)

Increment payload power priorities are determined by the IRT, led by the LIS, and disseminated to all the agencies by their IRT representatives. Changes to payload power priorities are determined by the IRT.

The IRT generates an internationally-integrated, prioritized list of all the racks/ facilities operating during the increments in the LST period. An LST is initiated in one of two ways. Every CCS (Command and Control Software) release requires an update to the LST. However, if Flight Director approves a need for an update to the LST, an interim version can be made.

The priority associated with a rack/facility does not necessarily correspond with the science priority being performed in that facility, but rather with the samples and hardware shelf life, temperature constraint, total or partial science loss, and any other constraints associated with the experiment. The more sensitive a sample/hardware is to power loss, the more protection is afforded to that rack/facility in the LST.

4. PROCEDURE

1. At CCS Uplink-8.5 months, the LIS sends a request to the IRT members for science sample and hardware power outage constraints to initiate the payload facility LST prioritization.

2. At CCS uplink-8 months, (within two weeks of the LIS request to the IRT members), the IRT members send the requested inputs to the LIS.

3. At CCS uplink-7.5 months, the LIS integrates the inputs and generates a draft LST input (see Table 2) and convenes the IRT to discuss.

a. The IRT uses the samples and hardware power outage sensitivity and potential for science loss during a specific increment stage to determine which priority for Load Shed a payload facility should have during that stage.

b. Since many experiments can be operated in one facility during one stage, the most sensitive sample or sample with the potential of higher science loss during a power outage and/or the combined impact for experiments in that facility dictate where that facility should be placed in the LST.

c. The table shows the prioritized list of experiments located within each facility with their assigned priorities for Load Shed. Each facility is also listed in priority order based on the highest priority payload within the facility.

4. At CCS uplink-7.25 months, the final IRT priority list for Load Shed is generated and approved by the IRT.

5. At CCS uplink-7 months, the LIS delivers the IRT-agreed LST to the MSFC Payload Rack Officer (PRO) and Payload Operations Manager (POM).

a. It is the responsibility of the IRT members to make their respective agency functions aware of the final IRT product that was agreed to and sent out to the MSFC PRO.

6. MSFC PRO reviews the integrated LST facility/payload prioritization with IP Systems (Col-Sys and CANSEI). If MSFC PRO has issues or concerns, and believes he cannot implement or negotiate the IRT payload priorities with the JSC Power Resource Officer (JSC PRO), then the LIS convenes the IRT and other required parties to discuss and agree upon workable solutions. If there are changes, the LIS will then update the Excel spreadsheet, and deliver it to the MSFC PRO.

7. At CCS uplink-6 months, the MSFC PRO delivers Payload Priority Integrated LST inputs to JSC-PRO.

8. JSC-PRO integrates the Payload Priorities into the ISS LST with the rest of ISS disciplines. This Integrated Load Shed Table procedure is documented in the US SODF EPS Book (Procedure 5.106).

9. The final LST integrated facility/payload prioritization product is kept on console by the MSI and all IP IS-Reps.

5. REFERENCE DOCUMENTATION

The following OIP outlines the JSC_PRO requirements from each group so that the power analysis can be performed:

SSP-50643 Operations Interface Procedure-Generic, Section 7.4.1

Table 2 - Template of Respective Experiment LST Input

What is maximum allowed time of Facility power-outage before science or payload performance is impacted? Please provide rationale.

What is the science or payload performance impact of a power-outage of facility? Please quantify in percentage over time and provide rationale.

Duration of an experiment run in the stage?

Power drawn by the Facility / Experiment?

Possibility to re-do experiment if needed, commercial cost

Down mass Cold Stowage usage Crew Time

Table 3 - Integrated Payload LST X2R11 Load Shed Payload Racks Integrated Prioritization Increment Research Team (IRT)

AMS - survival Mode

MCE - survival Mode

MAXI - survival Mode

SOLAR - survival Mode

STP-H3 - survival Mode

SEDA - survival Mode

HREP - survival Mode

SMILES - survival Mode

MISSE-8 - survival Mode

SCAN Testbed - survival Mode

MSG

MILLER-UREY (MUE) (Lose Temp Control/100% loss)

CCF, SODI, SLICE, BASS, MICRO5, InSpace3 (Can repeat runs)

ER-3/EMCS

GRAVI-2 (2-3hrs/100% loss)

Plant Signaling (1st 5 days/100% loss, 6-10 days/partial loss)

EDR

FASTER

ANANDAMIDE CONTROL (New OpNom for RESLEM) (1st 56hrs/100% loss)

MSPR

Medaka Osteoclast (1 hr/5% loss, 2hr/30% loss, >3hr/50% loss)

BLB

GRAVI-2

SAIBO

CsPINS-2 (8hrs/10% loss, >24hrs/30% loss)

Resist Tubule (1st 6hrs/100% loss, >6hrs/80% loss)

RYUTAI

Ice Crystal2 (lose 1 experiment, can be repeated)

JAXA PCG (10 min/100% loss)

Marangoni UVP&Exp (possible liquid bridge silicon oil break, several hrs cleanup)

Nano Step (can be repeated)

KOBAIRO

Alloy Semiconductor (Lose Power, Lose Crystal Growth, 100% loss)

Hicari (Lose Temperature, Lose Crystal, 100% loss)

MSRR / MSL

CETSOL-2 (1-5 minutes, molten state, total sample loss)

MICAST-2 (1-5 minutes, molten state, total sample loss)

SETA-2 (1-5 minutes, molten state, total sample loss)

ELC3

SCAN Testbed (< 6 hours/Okay, >6 hours/100% loss, $35k to rerun)

MELFI-1

Medaka Osteoclast

Bisphosphonates

CsPINS-2

CARD

Hair

IMMUNO

MILLER-UREY (MUE)

Myco

Mycrobe-III

Nutrition

Pro K

Repository

Resist Tubule

ANANDAMIDE CONTROL (New OpNom for RESLEM)

Stem Cells

Vascular

2D Nano Template

MELFI-3

MELFI-2

AMS - Ops Mode

MCE - Ops Mode

MAXI - Ops Mode

SOLAR - Ops Mode

STP-H3 - Ops Mode

SEDA - Ops Mode

HREP - Ops Mode

SMILES - Ops Mode

MISSE-8 - Ops Mode

SCAN Testbed - Ops Mode

HRF-2

Bisphosphonates

CARD

ENERGY

Nutrition/Rep/Pro K

SOLO

HRF-1

Integrated Cardiovasular

Integrated Immune

SOLO

USND

Vascular

VESSEL IMAGING

MARES

Rack Commissioning

SARCOLAB

EPM

NEUROSPAT

SOLO

ENERGY

WORF

EarthKAM

ISSAC

ER-5

SNFM

SpaceDRUMS

ELC4

RRM

ER-2

ALTEA DOSI

ALTEA SHIELD

CGBA-5/DTN

CSI-05

GLACIER-1

NLP Cells 7

SNFM

VCAM

ER-1

CGBA-4

CSI-05

DTN

MAMS

NLP Vaccine 17

SAMS-ICU,RTS

SNFM

ER-4

DECLIC

SAMS

SAMS-ICU

Cube Lab

CIR

MDCA/FLEX-2

FIR

LMM/ACE-1

LMM/CVB

LMM/ PACE-2

ER-8

Amine Swingbed

ER-6

Glacier-2

MERLIN/Galley

IRT-PRE.07 STAGE UTILIZATION PRIORITY LIST DEVELOPMENT AND UPDATING

1. PURPOSE

The purpose of this process is to provide the Increment Research Team (IRT) forum with an up-to-date understanding of the Stage Priorities per IP.

2. PARTICIPANTS

3. GENERAL

The Stage Utilization priorities for each IP agency are defined during the Increment preparation phase, in support of the On-Orbit Summary (OOS) process, which is a multilaterally agreed planning process. These Stage Utilization priorities are developed for preliminary OOS development activities and updated prior to the final OOS development exercise.

Once the Increment is in the execution phase, many factors contribute to deviations from the OOS plan. Examples include the following:

· Delays in vehicle traffic

· Anomalies to hardware on-orbit

· Items being de-scoped from manifests due to higher priority activities

· Activities being delayed due to other higher priority systems or utilization activities.

During the Increment execution phase, the IRT forum shall have at any moment the up-to-date insight to the remaining Utilization objectives and priorities. This process would allow a snapshot of the rest of the Increment which would complement the 4-week look-ahead Utilization priorities (IRT-EXE.01) that are discussed weekly at the IRT.

This process would allow each IP to bring to the IRT forum once a month the updated Stage Utilization priorities. These updates would take into account the past Utilization accomplishments for the on-going Increment and if necessary any changes in each IPs Stage priorities.

This process consists of priorities ordered within the IP agency, but are not yet integrated. The process documented in IRT-EXE.01 provides integrated USOS Utilization priorities during the execution phase of the Increment.

4. PROCEDURE

1. The template to be used for this process is a document that has a section for each IP. The Utilization priorities are presented in a numbered list, with highest priority at the top in the number 1 position.

2. The number of columns is determined by the number of stages in the Increment, which are defined periods of time on-board the ISS, based on vehicle traffic. These stages are explicitly defined in the (Increment Definition and Requirements Document) IDRD main volume for each respective Increment.

3. This list is first developed to support the preliminary OOS activities and then updated for the final OOS activities. Prior to development and updates to the list, each IP is responsible for coordinating within each respective agency.

4. Each IRT member maintains their Stage Utilization priority list for the Increment under execution, based on successful accomplishment of on-orbit tasks, experiments constraints, resource availability, etc.

5. During the execution phase of the Increment, each member submits updates of this Stage Priority list to the IRT on a monthly basis. These updates should include an indication of the activities which have been accomplished and should also include any additions or deletions from the Research Plan via the Change…