Attachment 0

Reference : Ref.
Ares(2015)4084507
ICU-SA-RQ-001- 03/10/2015
Version : 1.0.0
Date : 02-Oct-2015
System Requirements Specification
ICE Cubes
Title : System Requirements Specification
Abstract : This document establishes the system level requirements of the ICE
Cubes Flight and Ground Models
Grant Agreement N° : 666815
Copyright by Space Applications Services – All Rights Reserved

Reference : ICU-SA-RQ-001
Version : 1.0.0
Date : 02-Oct-2015
Page : ii
DOCUMENT APPROVAL SHEET
Name Company Signature and Date
Prepared by: T. Peignier Space Applications Services
PA Checked by: L. Tazi Space Applications Services
Approved by: M. Ricci Space Applications Services
Space Applications Services NV/SA Tel: +32-(0)2-721.54.84
Leuvensesteenweg 325 Fax: +32-(0)2-721.54.44
1932 Zaventem, Belgium Web: www.spaceapplications.com
This document is the property of
Space Applications Services NV/SA.
All rights reserved.

Version : 1.0.0
Date : 02-Oct-2015
Page : iii
DOCUMENT CHANGE RECORD
Version Date Author Changed Sections Reason for Change / RID No

/ Pages
1.0.0 02-Oct-2015 T. Peignier Initial release

Version : 1.0.0
Date : 02-Oct-2015
Page : iv
Table of Contents
1 Introduction ................................................................................................................................. 1
1.1 Purpose and Scope .......................................................................................................... 1
1.2 Specifications Organization .............................................................................................. 1
1.3 Applicable Documents ...................................................................................................... 2
1.4 Reference Documents ...................................................................................................... 3
1.5 Acronyms.......................................................................................................................... 4
2 System Description ..................................................................................................................... 6
2.1 ICE Cubes System Overview ........................................................................................... 6
2.2 Ground Segment .............................................................................................................. 8
3 ICE Cubes Facility Requirements ............................................................................................ 12
3.1 Physical Requirements ................................................................................................... 12
3.2 Functional Requirements ............................................................................................... 13
3.3 Control Requirements .................................................................................................... 14
3.4 Interfaces Requirements ................................................................................................ 15
3.5 Design Requirements ..................................................................................................... 16
3.6 Environmental Conditions Requirements ....................................................................... 18
3.7 Design and Construction Requirements ........................................................................ 19
3.8 Instrumentation and Performance Requirements .......................................................... 21
3.9 Safety Requirements ...................................................................................................... 21
3.10 Lifetime Requirements ................................................................................................... 21
3.11 Reliability and Maintainability Requirements .................................................................. 21
3.12 Logistics.......................................................................................................................... 22
4 Ground Models Requirements ................................................................................................. 24
4.1 General Requirements ................................................................................................... 24
4.2 Engineering Model / Ground Model (EM/GM) ................................................................ 24
4.3 Training Model (TM) ....................................................................................................... 24
4.4 Demo Model (DM) .......................................................................................................... 25
5 GSE Requirements .................................................................................................................... 26
5.1 General ........................................................................................................................... 26
5.2 GSE to ICE Cubes H/W Interfaces................................................................................. 26
5.3 Detailed Requirements ................................................................................................... 27
6 Ground Segment Requirements .............................................................................................. 28
6.1 General ........................................................................................................................... 28
6.2 Detailed Requirements ................................................................................................... 28

Version : 1.0.0
Date : 02-Oct-2015
Page : v
List of Figures
Figure 1-1: Specifications tree ................................................................................................................. 1
Figure 2-1: ICE Cubes facility conceptual view ....................................................................................... 6
Figure 2-2: ICE Cubes facility (closed door, in EPM-compatible Drawer) .............................................. 9
Figure 2-3: Accommodation concept in EPM 8PU Drawer ..................................................................... 9
Figure 2-4: Accommodation concept in EDR2 Type 0 Insert ................................................................ 10
Figure 2-5: Accommodation concept in Columbus cabin ...................................................................... 10
Figure 2-6: Dimensions of the Framework (front view) ......................................................................... 11
Figure 2-7: Dimensions of the Framework (top view) ........................................................................... 11
List of Tables
No table of figures entries found.

Version : 1.0.0
Date : 02-Oct-2015
Page : 1
1 Introduction
1.1 Purpose and Scope

This System Requirements Specification establishes design, operational and verification requirements
and constraints for the execution of the ICE Cubes System development, and in particular of the
“Framework” and “Case/Drawer”.
Dedicated requirement documents will be prepared for PharmaLab, GSE and Ground Segment
according to the specification tree of Figure 1-1.
The set of functional and technical requirements here specified shall be applicable for the activities of
detailed definition, production and ground testing up to the acceptance of the flight hardware, the
relevant ground models, spares and the Ground Support Equipment (GSE).
As for the organisation of requirements, the present document stands in accordance with the
requirements for the establishment of “Technical Requirements Specification”, ECSS-E-ST-10-06C. The
requirements in this document are isolated, univocally defined, and numbered such as to allow for their
verification and for proper tracking to the Payload Specification and in the Verification Control Document
(VCD) to be generated.
1.2 Specifications Organization
The scenario of Technical Specifications (TS) and Interface Requirement Documents (IRD) is shown in
Figure 1-1.
ICE Cubes
Science
Advisory Experiment Cubes IRD
Board
PharmaLab Card IRD
PharmaLab GSE Ground Segment

Specification Specification Specification
X-ray Diagnostic
Specification
Microfluidics
Specification
Procurement Specification (as necessary)
Figure 1-1: Specifications tree

Version : 1.0.0
Date : 02-Oct-2015
Page : 2
1.3 Applicable Documents

Unless their applicability is specifically limited, the following documents, of the identified
issue/date/revision, are applicable in full to this SRD.
As per AD1, the list of applicable documents defined here below is derived from the applicable document
list typically adopted for the ESA payload facilities and experiments for the ISS as defined in RD1.
Lower tier applicable documents (i.e. documents called up as applicable in each of the documents listed
below and in their applicable documents) are as well applicable (to be tailored accordingly at Project
level, i.e. to an extent suitable to ensure the proper execution of the required work).
AD1 Space Applications Services – ICE Cubes Project Management Plan, ICU-SA-PL-002, latest
version.
AD2 Astrium – Columbus Pressurized Payloads Interface Requirements Document, COL-RIBRE-

SPE-0164, Issue 2A, 15-Nov-2013 (+ relevant IRNs).
AD3 NASA – ISS Pressurized Volume Hardware Common Interface Requirements Document:
International Space Station Program, SSP 50835, Rev. D, April 2013 (+ associated PIRNs).
AD4 ESA – Product assurance requirements for payload projects, GPQ-010, issue 3, January
2010.
AD5 ESA – Safety and Materials Requirements for ESA Payloads on ISS, GPQ-010-PSA-101,
issue 5, April 2013.
AD6 ESA – Reliability and Maintainability for ESA Research Payloads, GPQ-010-PSA-103, issue
3, August 2011.
AD7 NASA – International Space Station Flight Crew Integration Standard (NASA–STD–3000/T),
SSP 50005, Rev. C, 15-Dec-1999.
AD8 NASA – Cargo Transfer Bag (CTB) Interface Design Document (IDD), JSC 39233, latest
issue.
AD9 ESA – Commercial, Aviation and Military (CAM) Equipment Evaluation Guidelines for ISS
Payloads Use, GPQ-MAN-02, Issue 1, May 1999.
AD10 ECSS – Space engineering: Fracture control, ECSS-E-ST-32-01C, Rev. 1, 06-Mar-2009.
AD11 ECSS – Space engineering: Structural finite element models, ECSS-E-ST-32-03C, 31-Jul-
2008.
AD12 ECSS – Space engineering: Materials, ECSS-E-ST-32-08C, Rev. 1, 15-Oct-2014.
AD13 ECSS – Space engineering: Mechanisms, ECSS-E-ST-33-01C, 06-Mar-2009.
AD14 ECSS – Space engineering: Software engineering, ECSS-E-ST-40C, 06-Mar-2009
AD15 ECSS – Space product assurance: Material selection for controlling stress-corrosion
cracking, ECSS-Q-ST-70-36C, 06-Mar-2009.
AD16 ECSS – Space product assurance: Determination of the susceptibility of metals to stress-
corrosion cracking, ECSS-Q-ST-70-37C, 15-Nov-2008.

Version : 1.0.0
Date : 02-Oct-2015
Page : 3
AD17 ECSS – Space product assurance: Requirements for the manufacturing and procurement of
threaded fasteners, ECSS-Q-ST-70-46C, Rev. 1, 06-Mar-2009.
AD18 ECSS – Space product assurance: Software quality, ECSS-Q-ST-80C, 06-Mar-2009.
AD19 ESA – Training Model Requirements, MSM-AT-CPT-GNL-RQ-001, Issue 1 Rev. 1, 30-Mar-

2001.
AD20 ECSS – Space engineering: Thermal control general requirements, ECSS-E-ST-31C, 15-
Nov-2008.
AD21 ECSS – Space engineering: Structural design and verification of pressurised hardware,
ECSS-E-ST-32-02C, Rev. 1, 15-Nov-2008.
AD22 ECSS – Space engineering: Structures general requirements standard, ECSS-E-ST-32C,

Rev. 1, 15-Nov-2008.
AD23 ECSS – Space engineering: Factors of safety standard, ECSS-E-ST-32-10C, Rev. 1, 06-
Mar-2009.
AD24 NASA – Non-destructive Evaluation Requirements for Fracture-Critical Metallic Components,

NASA-STD-5009, 07-Apr-2008.
AD25 ECSS – Space product assurance: Derating - EEE components, ECSS-Q-ST-30-11C,

Rev. 1, 4-Oct-2011.
AD26 NASA – Payload Flight Equipment Requirements and Guidelines for Safety-Critical
Structures: International Space Station Program, SSP 52005, Rev. E, March 2012.
AD27 NASA – Space Station Ionizing Radiation Design Environment, SSP 30512, latest issue.
AD28 NASA – Space Station Electromagnetic Emission and Susceptibility Requirements, SSP
30237, latest issue.
AD29 ESA – Columbus EMC & Power Quality Requirements, COL-ESA-RQ-014, latest issue.
AD30 RSC Energia – International Space Station: Technical Requirements for Hardware to be
Stored and Operated on the ISS Russian Segment, Π32958-106, latest issue.
AD31 Space Applications Services – ICE Cubes Product Assurance & Safety Plan, ICU-SA-PL-
001, latest version.
AD32 Space Applications Services – ICE Cubes Configuration Management Plan, ICU-SA-PL-003,
latest version.
1.4 Reference Documents

The following documents of the issue/date/revision listed contain supporting and background
information, however they do not constitute formal requirements.
RD1 ESA – HSO-UP Applicable Document List, HSF-LI-ESA-001, Rev. 41, 04-Jun-2014.
RD2 ESA – User Guide to Low Gravity Platforms, HSO-K/MS/01/14, Issue 3 Rev. 0, December
2014.

Version : 1.0.0
Date : 02-Oct-2015
Page : 4
RD3 Astrium and Thales Alenia Space – Mechanical Environment Verification Guidelines for Soft
Stowed Equipment, ESO-IT-PR-0092, latest issue.
RD4 Space Applications Services – ICE Cubes: PharmaLab Functional Description, ICU-SA-TN-
001, v1.0.0, 16-Sep-2015.
RD5 Space Applications Services – ICE Cubes ISS Accommodation Survey, ICU-SA-TN-002,
v1.0.0, 16-Sep-2015.
RD6 Space Applications Services – ICE Cubes Framework Functional Description, ICU-SA-TN-
003, v1.0.0, 16-Sep-2015.
RD7 OHB System AG – Science Module Interface Requirements Document (SMIRD) for the
European Physiology Model (EPM), EPM-OHB-RQ-0001, Issue 4, 30-Apr-2010 (+ relevant
IRNs).
RD8 Thales Alenia Space – EDR2 EI H/W IRD, TASI-EDR2-IRD-0001, Issue 03, 19-Apr-2013.
RD9 Universal Serial Bus Power Delivery Specification 2.0, V1.1, 07-May-2015. Available from:
http://www.usb.org/developers/powerdelivery/
RD10 Wikipedia – USB [cited 2-Oct-2015]. Available from: https://en.wikipedia.org/wiki/USB
RD11 ECSS – Space engineering: Adhesive bonding handbook, ECSS-E-HB-32-21A, 20-Mar-

2011.
RD12 Epiphan Systems Inc. – Epiphan Video KVM2USB™ [cited 2-Oct-2015]. Available from:
http://www.epiphan.com/products/kvm2usb/
RD13 ESA – MPCC handout for MPCC Phase 2 TIM Houston, 26-29-May-2015.
1.5 Acronyms
AD Applicable Document
ATV Automated Transfer Vehicle
CAPL Center-Aisle Payload
CPU Central Processing Unit
CTB Cargo Transfer Bag
DC Direct Current
DM Demo Model
EC European Commission
ECSS European Cooperation for Space Standardization
EDR European Drawer Rack
EM Engineering Model
EMC Electromagnetic Compatibility
EPM European Physiology Module
ESA European Space Agency
ESD Electrostatic Discharge
EST Experiment Sequence Test
GM Ground Model
GSE Ground Support Equipment
HDD Hard Disk Drive
HTV H-II Transfer Vehicle
ICD Interface Control Document

Version : 1.0.0
Date : 02-Oct-2015
Page : 5
ICE Cubes International Commercial Experiment Cubes

ICF ICE Cubes Facility
IDD Interface Definition Document
IRD Interface Requirements Document
IRN Interface Revision Notice
ISS International Space Station
KVM Keyboard, Video and Mouse
LAN Local Area Network
LED Light-Emitting Diode
LOS Loss of Signal
MCC Mission Control Centre
MLM Multipurpose Laboratory Module
MPCC Multi Purpose Communication and Computer
N/A Not Applicable
NAS Network Attached Storage
NASA National Aeronautics and Space Administration
NDI Non-Destructive Inspection
NR NanoRacks
ORU On-Orbit Replaceable Unit
PIRN Preliminary Interface Revision Notice
RD Reference Document
R&D Research and Development
ROS Russian Orbital Segment
RSC Energia Rocket and Space Corporation Energia
TBC To Be Confirmed
TBD To Be Determined
TC Telecommand
TIM Technical Interchange Meeting
TM Telemetry
TM Training Model
TS Technical Specifications
U Unit (= 10 x 10 x 10 cm)
UHB User Home Base
USB Universal Serial Bus
VCD Verification Control Document

Version : 1.0.0
Date : 02-Oct-2015
Page : 6
2 System Description
2.1 ICE Cubes System Overview

The main characteristics in terms of physical conceptual configuration are briefly highlighted in the
following.
The ICE Cubes facility is composed of:
• The Framework, accommodating up to 16 or 20 (TBC) Experiment Cubes, and providing power

and data/commands connectivity. The location on the upper side of the Framework can host the
PharmaLab instead of Experiment cubes.
• The structural Case (or Drawer), to be finalized following the decision about the accommodation
on board ISS.
• External harnesses and hoses (is any), as necessary, to interface the ISS infrastructure
electrical jumpers and thermal control parts.
• Removable mass memory storage devices, namely the Hard Disk Drives (HDDs) and USB flash
drives necessary to host the operational software and to physically download the scientific data.
The Experiment Cubes are standardized plug-and-play research modules (1U = 10cmx10cmx10cm)
or modular combinations of that basic size.
The PharmaLab is a semi-permanent laboratory for pharmaceutical research and development (R&D)
of new medicines allowing for X-ray crystallographic analysis.
A conceptual view of the facility with the Frameworks and the Experiment Cubes is shown in Figure 2-1.
Figure 2-1: ICE Cubes facility conceptual view

Version : 1.0.0
Date : 02-Oct-2015
Page : 7
2.1.1 The Framework

The Framework is foreseen to host a number of Experiment Cubes from the structural, power, data and
thermal control points of view. The Framework is the central unit that accommodates each Experiment
Cube and offers services such as connectivity and data storage.
The Framework is designed following criteria of simplicity and cross-compatibility with the various
possible accommodation platforms on board the ISS. The role of providing external mechanical
interfaces is left to the Case/Drawer, whose design will be finalized following the agreements with the
Space Agency about the accommodation of ICE Cubes and the relevant service.
The Framework is powered by a single feed (10A, 28V, 280W). A LAN port is present for communication
to/from the ISS infrastructure and to/from ground. Additional dedicated telemetry line(s) could be added,
e.g. for hardwired temperature monitoring or smoke sensing, depending on the specific accommodation
needs. The system, including the Experiment Cubes, is monitored and operated mainly from ground.
Nominal intervention of the crew is limited to activation of power switches, exchange of Experiment
Cube / PharmaLab microfluidic cartridges (so-called ‘Cards’) and collection of scientific data on HDD
and USB flash drive, if requested.
More details about the concept and functional description of the Framework can be found in RD6.
2.1.2 Experiment Cubes

The Experiment Cubes will vary per experiment but will all have to meet basic interface requirements
with the Framework such as modular size, weight, interface, maximum allowable power, etc.
The size of the Experiment Cubes is set to mimic the CubeSat standard, i.e. 10x10x10cm (1 litre) for a
1U Experiment Cube, 20x10x10cm for a 2U Experiment Cube, etc. with one principal difference: the
Experiment Cubes can be scaled along 2 axes in order to offer more flexibility to customers.
The Experiment Cubes can be functionally interconnected via the network offered by the Framework.
The facility housekeeping and the scientific data will be stored on a removable HDD and will be
downlinked to ground according to the capabilities offered by the ISS infrastructure.
Different voltages / power profiles will be available for each Experiment Cube location.
For additional details on the Experiment Cubes, see RD6.
2.1.3 PharmaLab
The PharmaLab facility is intended to be a semi-permanent laboratory for pharmaceutical research and
development of new medicines allowing for X-ray crystallographic analysis and making use of
exchangeable microfluidic cartridges (so-called ‘PharmaLab Cards’).
The PharmaLab is planned to occupy ~12U and be hosted on the ICE Cubes Framework when required.
When not in use, the PharmaLab will be stowed to make space available for other Experiment Cubes.
As such, the PharmaLab can be considered a highly-specific multiple Experiment Cube.
For each experiment, PharmaLab will use a pharmaceutical compound and a specific protein for which
the aforementioned compound has been designed, both provided by the customer.
Just like for the Experiment Cubes, the in-orbit operations of the PharmaLab Cards containing proteins
and compounds will be fully automatic and monitored from ground to the maximum possible extent.
More details about the concept and functional description of the PharmaLab can be found in RD4.

Version : 1.0.0
Date : 02-Oct-2015
Page : 8
2.1.4 Experiment Cubes and PharmaLab as “Class 3 Payloads”

The ICE Cubes development approach is to be compatible with the possibilities offered by the
forthcoming ESA MPCC. Even if, at the beginning of the project, the accommodation on the ISS is not
decided yet, the programmatic assessment is done that the possibilities of interacting with payloads on
board the ISS via commercial IP protocols, will become a reality for the various ISS segments in the
future. For this reason, the Experiment Cubes and the PharmaLab will be developed as Class 3
payloads.
Quoting RD2: “ESA is currently implementing an enhancement of the Columbus avionics and
communication system that will enable bidirectional Internet Protocol communications with payloads on-
board Columbus to further encourage the Columbus utilisation.
This Multi Purpose Communication and Computer enhancement, referred as “MPCC Enhancement”,
would also enable a new class of payloads, sometimes referred as “Class 3 Payloads”, connected wired
and/or wireless to the on-board LAN, using commercial Internet protocols, capable to be operated and
be controlled remotely from the Principle Investigator(s) home base and having a short life cycle from
concept to launch and on-orbit utilisation, as long as inherently safe.
The MPCC Enhancement [is expected] to be available on-board the ISS from the second half of 2015,
with full functionalities implementation by the second half of 2017. This enhancement, in its final
configuration, will include the implementation of an independent Columbus Terminal allowing, even if
partial, future tele-operations payloads.”
2.1.5 Mechanical Configuration and On-Orbit Accommodation

The location of the ICE Cubes facility inside the ISS and specifically in Columbus has not been decided
yet and will be subject of a future discussion with Space Agencies.
A cross-platform compatible core of the ICE Cubes facility (the Framework and Experiment Cubes),
making the facility easily adaptable to different hosting locations in the ISS (different payload racks,
centre-aisle locations, etc.) shall be developed and the facility external interfaces will be completed once
the agreements with a Space Agency is finalized.
The design shall consider the accommodation concepts developed in the first phase of the project and
presented in Figure 2-2 to Figure 2-5.
2.2 Ground Segment

An out-of-the-box installable ground monitoring and control software will allow the customers access to
their experiments directly from their premises. Scientific data will directly be routed to the customers.
The control/monitoring of the facility will be performed from a ground control station (to be established
by Space Application Services specifically for ICE Cubes, as baseline) minimizing the need of crew time
on board the ISS. Details for this activity will be finalized in the frame of the agreements with the Space
Agency.

Version : 1.0.0
Date : 02-Oct-2015
Page : 9
Figure 2-2: ICE Cubes facility (closed door, in EPM-compatible Drawer)
Figure 2-3: Accommodation concept in EPM 8PU Drawer

Version : 1.0.0
Date : 02-Oct-2015
Page : 10
air/water heat
exchanger
Figure 2-4: Accommodation concept in EDR2 Type 0 Insert
fans for forced

air cooling
Figure 2-5: Accommodation concept in Columbus cabin

Version : 1.0.0
Date : 02-Oct-2015
Page : 11
Figure 2-6: Dimensions of the Framework (front view)
Figure 2-7: Dimensions of the Framework (top view)

Version : 1.0.0
Date : 02-Oct-2015
Page : 12
3 ICE Cubes Facility Requirements

Note 1: The text in italic style does not define system requirements. Its purpose is to provide information
to clarify the terms of the associated requirement.
Note 2: Unless otherwise specified, in the rest of the present document the terms “Experiment Cube”
and “Cube” encompass the PharmaLab as well.
3.1 Physical Requirements

The following requirements have been identified as preliminary interfaces requirements, based on the
current design. In due time, they will be replaced by a verified Interface Control Document (ICD).
3.1.1 Composition
3.1.1.1 The ICE Cubes Facility (ICF) shall comprise the following parts:
• the Framework, hosting the various Experiment Cubes and the PharmaLab
• the Case (or Drawer) including the rails to slide the Framework
• Harnesses for power and data interfaces to the ISS hosting infrastructure
• Hoses for water cooling loop (in case of EDR2 accommodation)
• Removable mass memory storage devices (e.g. HDDs and USB flash drives)
• Launch bags
3.1.1.2 The harnesses and jumpers (e.g. power cables, LAN/data cables, fluidic hoses) shall
be separate items and shall be connected to the Framework on orbit.
3.1.2 Dimensions
3.1.2.1 The dimensions of the Framework shall be as shown in Figure 2-6 and Figure 2-7.
These figures also provide the layout of the single 1U sized cubes.
3.1.2.2 The dimension of the Case/Drawer and the length of the harnesses shall be finalized
following the definition of the accommodation on board the ISS. The following options
apply:
1) “8PU” drawer for accommodation in Columbus EPM Rack (RD7)
2) “Type 0” insert for accommodation in Columbus EDR2 Rack (RD8)
3) Internal Case dimensions (400 mm x 325 mm x 595 mm) for Columbus cabin
accommodation
4) Dimensions are TBD for accommodation in the Multipurpose Laboratory Module
(MLM) of the Russian Orbital Segment (ROS)
3.1.2.3 The external envelope of the PharmaLab shall not exceed the dimensions of 350 x
120 x 530 mm.
Note: These dimensions are driven by the compatibility with the operation in
Columbus EPM Rack.
3.1.2.4 The external dimensions of the ICE Cubes Hardware, once packed in launch
configuration, shall be minimized and compatible with the inclusion in Cargo Transfer
Bags (CTBs, see AD8).
3.1.2.5 Independently of its dimensions, each Experiment Cube shall allow to be plugged in
and out of the Framework individually without affecting the other Experiment Cubes
mechanically.
3.1.2.6 The hardware code shall be different and unique for each individual Experiment Cube.

Version : 1.0.0
Date : 02-Oct-2015
Page : 13
3.1.3 Mass
3.1.3.1 The mass of the Framework, without removable mass memory storage devices (HDDs
and USB pens) shall not exceed 5 kg (TBC).
Note: As per Figure 1-1, detailed requirements for the mass of the PharmaLab will be
defined in the dedicated PharmaLab Specification.
3.1.3.2 The mass of the Case/Drawer and external harness/hoses shall be minimized
following the definition of the accommodation on board the ISS (see req. 3.1.2.2).
3.2 Functional Requirements

3.2.1.1 The ICF shall support operations of the hosted Experiment Cubes and PharmaLab
autonomously or controlled from ground.
3.2.1.2 The Framework shall be able to provide up to sixteen (16) (TBC) active locations for
Experiment Cubes, equipped with power and data interfaces.
3.2.1.3 The ICF shall provide near real-time telecommand (TC) routing to the various
Experiment Cubes from ground.
3.2.1.4 The ICF shall provide near real-time routing of telemetry (TM) from the various
Experiment Cubes to the ISS and to ground.
3.2.1.5 The ICF shall provide data storage (e.g. NAS) with a capacity of 2TB (TBC) to serve:
- as a data buffer to record the data at a faster rate than it is downlinked, and/or
- as a backup, to be wiped once all data is collected on ground and verified to be
good, and/or
- as a temporary storage, to be wiped once all data is transferred e.g. to a USB key on
board the ISS , the idea being to physically download the USB key in question to
Earth.
3.2.1.6 The Framework shall be able to support the following scenarios of experiment Cubes
running in parallel:
• ten (10) (TBC) Experiment Cubes (without PharmaLab)
• eight (8) (TBC) Experiment Cubes plus the PharmaLab
3.2.1.7 The Framework shall be able to store in real time the data coming for the overall set of
running Experiment Cubes up to a data rate of 5Gbit/s (TBC).
Note: This is the performance offered by the USB 3.0 technology.
3.2.1.8 To fulfil the possible need to physically (rather than electronically via the MPCC)
downlink data from the Framework to ground, the Framework shall feature an easily
accessible external interface USB 3.0 (TBC) type for interfacing drives up to 1TB
(TBC) of capacity.
3.2.1.9 The ICE Cubes shall allow for utilization of removable data storage media with 1TB of
capacity, to be used for physical download of scientific data.
3.2.1.10 The Framework shall provide time service (i.e. on board electronics clock to provide
synchronized time to Experiment Cubes).
3.2.1.11 To allow for on-orbit troubleshooting and in situ debug (e.g. in case the connection
from ground to the ICF is lost), USB and video port shall be available and easy
accessible for connection with a KVM switch (e.g. KVM2USB™ device of RD12) to
allow for connection to an on-board laptop computer and debug in situ.

Version : 1.0.0
Date : 02-Oct-2015
Page : 14
3.3 Control Requirements

3.3.1.1 The ICF shall be operated in all its functions (full monitor and control), from ground by
the defined Mission Control Centre (MCC).
3.3.1.2 The ICF shall allow for intervention of the crew, for control purposes, limited to:
- overall power on/off via a dedicated main switch
- power on/off of single experiment cubes via dedicated switch (TBC)
- direct access to Framework CPU for troubleshooting and in situ debug (see
req. 3.2.1.11).
3.3.1.3 The activation (power on) of the single Experiment Cubes shall be possible by the
MCC only.
3.3.1.4 The full control and power off (TBC) of the experiment, once activated by the MCC,
shall be possible by the experiment responsible, at his User Home Base (UHB), by
using the dedicated experiment control software made available by the ICE Cubes
service.
3.3.1.5 The ICF shall be capable of automatic monitoring and management of off-nominal
situations.
3.3.1.6 Situational awareness data (functional housekeeping) shall be generated for and
downlinked to monitor the health status of the facility and the Experiment Cubes (for
each Experiment Cube, a predefined, limited set of critical parameters will be defined
and monitored by the MCC).
3.3.1.7 Adequate diagnostics shall be implemented for the detection, monitoring and reporting
of any function degradation or failure having occurred.
3.3.1.8 The ICF shall support initialisation and checkout of its system and subsystem
elements.
3.3.1.9 The ICF shall also react by software interface on remote command execution.
3.3.1.10 The period of LOS (Loss of Signal) between ISS and MCC shall be considered part of
standard operation and properly handled. The ICF shall be capable to manage the
periods of LOS (e.g. in order not to endanger the facility) without the crew and ground
support.
3.3.2 Command and Data Handling Requirements

3.3.2.1 Baseline for the design of command, control, data access and data handling aspects
shall be the architecture of the ESA MPCC as defined in RD13.
3.3.2.2 The Framework shall implement a LAN as the link for TM/TC and data transfer to the
ISS hosting facility.
3.3.2.3 For management and administration purposes (copy, transfer to USB removable
device, delete), full access to the data stored in the mass memory storage device(s)
shall be possible from the MCC.
3.3.2.4 Control commands provided from ground by telecommanding shall be transferred to
the appropriate Experiment Cube directly (transparent throughpassing).
3.3.2.5 The ICF shall be responsible for time-tagging its own housekeeping data.
3.3.2.6 The ICF shall be responsible for time-tagging the functional housekeeping data
generated by the Experiment Cubes.
3.3.2.7 The ICF shall be responsible for time-tagging of the scientific data generated by the
Experiment Cubes with a max delay of TBD. (TBC)

Version : 1.0.0
Date : 02-Oct-2015
Page : 15
3.3.2.8 It shall be possible to encrypt scientific data before their downlink or their transfer to
removable mass memory storage device(s) for physical download.
3.3.2.9 The network architecture shall automatically guarantee the possibility to have
experiments spread in multiple Experiment Cubes where one Experiment Cube
directly monitors and controls one or more other Experiment Cubes.
3.3.2.10 Execution/rejection of commands to the ICF, PharmaLab or Experiment Cubes shall
be reported in the dataflow of the subsequent telemetry (TM) downlink.
3.3.2.11 It shall be possible to override the ongoing command execution/rejection function from
the MCC, as long as safety is not affected.
3.3.2.12 The ICF shall start the processing of commands within one second from the receival
from ground.
3.3.2.13 The status of powering of the ICF and of the single Experiment Cubes shall be evident
to the crew via dedicated LEDs present on the front side of the Framework.
3.4 Interfaces Requirements
3.4.1 Launcher Interfaces

3.4.1.1 The ICE Cubes flight hardware shall comply with the launchers common interfaces
requirements defined in AD3.
3.4.1.2 The ICE Cubes flight hardware shall be launched in non-operating, non-powered
condition.
3.4.2 External Interfaces to ISS Infrastructure

3.4.2.1 As far as the mechanical interfaces are concerned, the ICF shall interface with the ISS
infrastructure via the Case/Drawer. The design shall be compliant to the requirements
applicable for the selected accommodation (TBD). For preliminary design purposes,
the envelope of requirements defined by the accommodation scenario of req. 3.1.2.2
shall be considered.
3.4.2.2 The Framework shall provide a connector, on the front side, for power interface to the
ISS infrastructure. The assumed power interface characteristics are 28V @10A,
280W.
Note: The actual interface to the ISS is implemented via an external jumper to be
defined after the finalization of the accommodation on board the ISS.
3.4.2.3 The Framework shall provide a LAN connector on the front side.
Note: The actual interface to the ISS is implemented via an external jumper to be
defined after the finalization of the accommodation on board the ISS.
3.4.2.4 As the interface temperature for the ICF will depend on the actual accommodation on
the ISS, for preliminary design purposes, the envelope of requirements defined by the
accommodation scenario of req. 3.1.2.2 shall be considered.
3.4.3 Crew Interfaces

3.4.3.1 All the switches, connectors, LEDs and removable mass memory storage devices to
be operated/checked by the crew during nominal operations shall be accessible on the
front side of the Framework (or of the Drawer, in case of fluidic connectors for EDR2
accommodation).

Version : 1.0.0
Date : 02-Oct-2015
Page : 16
3.4.4 Internal Interfaces - Framework to Experiment Cubes

3.4.4.1 The Framework shall provide power interface to the active locations for Experiment
Cubes. The following power profiles shall be provided via the same power connector:
(a) 5V @ 2A, 10W; (b) 12V @ 3A, 36W; (c) 20V @ 3A, 60W.
3.4.4.2 The PharmaLab shall provide data interface to active locations of the Experiment
Cubes via USB.
3.4.4.3 The possibility to transmit power and data via one single connector (e.g. USB
connector type-C as per RD9 and RD10) shall be preferred.
Note: The restraint capability offered by the friction of the mated connector could be
considered sufficient up to a certain mass/size of Experiment Cube, if supported by
adequate demonstration.
3.4.4.4 The layout of the interface connectors to the Experiment Cubes shall maximize the
flexibility in accommodating different classes/sizes of Experiment Cubes.
3.4.5 Internal interfaces - Framework to PharmaLab

3.4.5.1 The Framework shall provide mechanical interface and restraint to PharmaLab. The
restraint shall be automatic and shall not require operation of fasteners.
3.4.5.2 The Framework shall provide power and data interface to PharmaLab, as follows:
- Power: TBD
- Data: USB
Note: The interfaces with PharmaLab will be specified following the definition of its
system requirements established in the PharmaLab Specification (see Figure 1-1).
3.4.6 Internal interfaces - Framework to Case/Drawer

3.4.6.1 The Framework shall interface to the Case/Drawer via dedicated sliding guides as
shown in the figures from Figure 2-2 to Figure 2-7.
3.4.6.2 No fasteners shall be used for restraining the Framework into the Case/Drawer.
3.4.6.3 Once closed, the front door of the Case/Drawer shall provide restraint against
longitudinal sliding of the Framework.
3.4.6.4 Once closed, the front door of the Case/Drawer shall let access to the Framework’s
front connectors, switches, and ports for connecting removable mass memory storage
devices.
3.5 Design Requirements

Note: Unless otherwise specified, the following requirement apply to all the elements of the ICF,
Experiment Cubes and PharmaLab.
3.5.1 Mechanical and Structural Design Requirements

3.5.1.1 The ICF shall be designed for a single launch scenario.
3.5.1.2 The PharmaLab shall be designed for a single launch scenario.
3.5.1.3 Design and verification of packaging for launch shall follow the guidelines of RD3.
3.5.1.4 Structural design shall be compliant to requirements of AD22, AD23 and AD26.
3.5.1.5 Pressurised items shall be designed according to AD21.
3.5.1.6 Critical/structural fasteners shall be procured according to AD17.

Version : 1.0.0
Date : 02-Oct-2015
Page : 17
3.5.1.7 Fasteners that are used in parts that will be removed in flight shall be captive.
3.5.1.8 Positive back-off prevention means shall be used for all fasteners. Use of glue (e.g.
Loctite) or stacking compound is subject to prior approval by the Agency and is,
however, forbidden for structural fasteners.
3.5.1.9 Non-Destructive Inspections (NDIs), if any, shall be performed in accordance with
AD24. The etching requirement before penetration inspection is not applicable to
rolled threads.
3.5.1.10 Design of mechanisms shall comply with requirements of AD13.
3.5.1.11 In the event of depressurisation on station and/or during transfer from/to Progress, the
ICF and the Experiments Cubes shall remain safe.
3.5.1.12 The ICF shall be capable of resuming nominal operations on station after re-
pressurisation without any damage due to de-/re-pressurisation.
3.5.1.13 The design of the ICF shall be compatible with the complete scenario of thermally
induced loads including the on-ground testing and transport, pre-launch processing,
and operations on board the ISS.
3.5.1.14 Fracture control plan shall be established according to the requirements of AD10.
3.5.1.15 Intermittent and continuous audible noise generated by the ICF and the Experiment
Cubes shall be compliant to the requirements of the ISS hosting facility. For
preliminary design purposes, the NC-40 profile, as defined in AD2, shall be considered
applicable.
3.5.1.16 Structural finite elements models shall be generated in compliance to AD11.
3.5.2 Thermal Design requirements

3.5.2.1 The Framework, the PharmaLab and the Experiment Cubes shall be thermally
controlled via forced air ventilation (TBC) created inside the Case/Drawer enclosure.
The details and the implementation of this air circulation depend on the final
accommodation and the possibilities offered by the hosting ISS infrastructure. For
preliminary design purposes, the envelope of requirements defined by the
accommodation scenario of req. 3.1.2.2 and the concepts defined in figures from
Figure 2-2 to Figure 2-7 shall be considered.
3.5.2.2 The ICF shall be able to dissipate the heat generated by the Experiment Cubes
assuming, for design purposes, a power density of 10W/dm³ (TBC).
Note: Given the forced air circulation defined in req. 3.5.2.1, the amount of power that
an Experiment Cube can dissipate depends on the exposed external surface and,
hence on its dimensions.
3.5.2.3 The thermal design of the ICE Cubes hardware shall be compliant to AD20.
3.5.2.4 Because of uncertainties in the thermal analysis, a margin of 5°C shall be considered
when specifying interface temperatures for the design.
3.5.2.5 If the ICF is accommodated in EDR2, a dedicated air-to-water heat exchanger (TBC)
shall be introduced inside the Case/Drawer, which shall not modify the architecture
and the design of the Framework and Experiment Cubes.
3.5.2.6 Induction of thermal perturbation and deformation into the diagnostic instrumentation
shall be minimised per design and demonstrated compatible with the functional
requirements of the experiment.
3.5.2.7 Laser diodes, if any, shall be adequately temperature stabilised.
3.5.2.8 Thermal mathematical models to be used for integrated system analysis shall be
compliant to the requirements of the ISS hosting facility. Unless otherwise specified,

Version : 1.0.0
Date : 02-Oct-2015
Page : 18
the guidelines of RD8 shall be followed, even if the ICF is not accommodated in
EDR2.
3.5.3 Electrical Design Requirements

3.5.3.1 The ICF shall be designed to minimize the power requested by its internal subsystems
and to maximize the power distributed to the various Experiment Cubes. The overall
maximum power consumption of the facility, apart from the phase of writing data in the
removable mass memory storage devices, shall not exceed 70W (TBC).
3.5.3.2 The ICF and the Experiment Cubes shall be compliant to the bonding and grounding
requirements specified in AD2.
Note: This is assumed for design purposes, even if the ICF is not accommodated in
the Columbus module.
3.5.3.3 The ICF, including the Experiment Cubes, shall not produce electromagnetic
emissions beyond the limits specified in AD28, AD29 and AD30.
3.5.3.4 For preliminary design purposes, the ICF, including the Experiment Cubes, shall be
compliant with the requirements and definitions of the electromagnetic susceptibility
limits of AD2.
3.5.3.5 For preliminary design purposes, the ICF, including the Experiment Cubes, shall meet
the electrostatic discharge requirements of AD2.
the AC magnetic field emission requirements of AD2.
the DC magnetic field emission requirements of AD2.
the corona requirements of AD2.
3.5.3.9 The ICF shall be compatible with the actual steady state voltage range of 28V +1.5V /
-2.7V DC.
3.5.3.10 Functional/safety critical components shall be derated in the manner outlined in AD25.
Project-specific stresses, such as temperature, radiation, etc., shall be reviewed as a
means of assessing whether additional derating is required.
3.5.3.11 The ICF shall operate and be compatible with the EPS ripple voltage characteristics
applicable for the actual ISS accommodation.
3.5.3.12 The ICF and the PharmaLab shall be designed to operate nominally throughout the
entire life-time, being exposed to the yearly total dose of radiations as a consequence
of the radiation environment.
3.5.3.13 Equipment and subsystems shall be designed not to produce an unsafe condition or
one that could cause damage to equipment external to the integrated rack as a result
to exposure to SEE ionizing radiation assuming exposure levels specified in AD27,
paragraph 3.2.1, with a shielding thickness of 5.4 mm plus the specific shielding of the
ICE Cubes metallic parts.
3.6 Environmental Conditions Requirements
3.6.1 Natural Environment

3.6.1.1 The ICF, including the Experiment Cubes, shall withstand the ISS, HTV, Progress,
Soyuz, SpaceX Dragon, and Orbital Cygnus and depressurization and re-

Version : 1.0.0
Date : 02-Oct-2015
Page : 19
pressurization, humidity, temperature and atmospheric pressure requirements as

defined in AD3.
3.6.1.2 The ICF, including the Experiment Cubes, shall withstand the environmental
requirements given in the following table:
Temperature (°C) Pressure (mbar) Maximum Relative

Humidity (%)
Storage +5 to +35 942 to 1050 85
Transport 0 to +50* 150 to 1060 90
Accommodation into 0 to +50 600 to 1293 85

launcher
Launch / Ascent 0 to +50 0 to 1293 90 (100 depressed)
On Orbit +5 to +45 0 to 1050 70 (100 depressed)

(on board the ISS)
non operational
Descent / Landing 0 to +48,9 0 to 1293 90 (100 depressed)
* In the event of a launch in Progress or Soyuz, the temperature range requirement during transportation by train
to the launch site is actually -50°C to +50°C. However, this temperature range can be narrowed to 0°C to +50°C by
shipping the hardware items from Space Applications Services’ premises to the launch site in such a way that no
transportation in an uncontrolled temperature environment takes place (as it has been done in the past for other
projects). Therefore, it is considered appropriate to verify compliance of the ICF design against the 0°C to +50°C
range.
Note: The table above is an overall enveloping table, but for each transportation vehicle, the applicable
document(s) (as listed in §3.6.1.1) give the details, which cannot all be captured here.
3.6.2 Structural / Mechanical Operational Conditions

3.6.2.1 The ICF, including the Experiment Cubes, shall be compatible with on-orbit static
accelerations of 0.2g in three orthogonal directions at the same time.
3.6.2.2 Once installed on board the ISS, the ICF facility shall be compliant with the
requirements for crew loads defined in AD2.
3.6.2.3 The ICF, including the Experiment Cubes, shall not generate vibratory accelerations
beyond the requirements established for the specific hosting ISS infrastructure. For
preliminary design purposes, the envelope of requirements defined by the
accommodation scenario of req. 3.1.2.2 shall be considered.
3.7 Design and Construction Requirements
3.7.1 Design Requirements

3.7.1.1 For the ICF designs, including the Experiment Cubes designs, SI units shall be used.
3.7.1.2 During the design, conformity to international regulations by ISO and current
standards of aerospace industry shall be provided.
3.7.1.3 According to the design, the ICF, including the Experiment Cubes, shall be producible,
capable of being inspected and tested.

Version : 1.0.0
Date : 02-Oct-2015
Page : 20
3.7.2 Specifications, Norms, Standards

3.7.2.1 All drawings shall be based on the ISO standard and shall use English language.
3.7.3 Materials, Processes and EEE Components

3.7.3.1 The ICF shall use materials and parts that meet the requirements defined in AD12,
AD15 and AD16.
3.7.3.2 The ICF and PharmaLab EEE components quality shall be as defined in AD31
3.7.3.3 The ICF and PharmaLab CAM equipment shall undergo to evaluation process
according to the guidelines of AD9.
3.7.3.4 For adhesive bonding processes, RD11 shall be considered.
3.7.4 Surface Treatments / Protective Coatings

3.7.4.1 Protective coatings shall be applied whenever required by the nature and/or the
application of a material or part. The worst-case atmospheric environment shall be
considered for the selection of the coating process, and the electrical properties of the
coating shall be regarded.
3.7.4.2 Electrical bonding of the ICF, including the Experiment Cubes, shall be achieved via
the mounting surface. For bonding surfaces on aluminium alloys, electroless nickel
coating shall be used.
3.7.5 Human Factors

3.7.5.1 The design of the ICE Cubes hardware shall take into account the special ergonomic
needs of human operation under weightlessness and thus shall comply with the
human factors engineering requirements of AD2 section 3.12 with the exclusion of
3.12.3.3 “Audible noise requirements” (at rack level) and 3.12.10 “Payload in-flight
maintenance”.
3.7.5.2 The proper orientation for the Experiment Cubes to be plugged onto the Framework
shall be obvious by design or marking.
3.7.5.3 The proper orientation for the Framework to be placed in the Case/Drawer shall be
obvious by design or marking.
3.7.5.4 The proper orientation for the Case to be placed in the ISS hosting infrastructure shall
be obvious by design or marking.
3.7.5.5 Latches, handles and opening/closing mechanisms shall be designed to be
latched/unlatched and opened/closed with one hand and without having to use any
operating instructions or tools.
3.7.5.6 In order to give basic feedback to the crew on board the ISS, the Framework shall
have means (e.g. colour LEDs) to indicate the status of the various Experiment Cubes
(e.g. powered, unpowered, transferring data).
3.7.6 Interchangeability and Replaceability

3.7.6.1 The Ground and Flight Models of the Framework shall provide same interfaces to the
Experiment Cubes for installation, check-out and operation.
3.7.6.2 No predefined hard-coded indication of the target location shall be necessary for the
Experiment Cubes. It shall be possible to change the location of the Experiment
Cubes, on ground and in orbit, without need of software modification.

Version : 1.0.0
Date : 02-Oct-2015
Page : 21
3.7.7 Identification and Marking

3.7.7.1 The ICF labels shall satisfy requirements as defined in AD2.
3.7.7.2 In case of accommodation inside the ROS, specific ROS labelling requirements (TBD)
shall apply. In case of launch with Progress but not accommodation inside the ROS,
this requirement is only valid for the launch bags.
3.7.7.3 The various elements of ICE Cubes shall be marked and labeled as defined in AD32.
3.7.7.4 The Experiment Cubes shall include installation position marks.
3.8 Instrumentation and Performance Requirements

3.8.1.1 The ICF shall support the implementation of a smoke sensor in case it is requested by
the stand-alone (CAPL) installation (TBC).
3.9 Safety Requirements

3.9.1.1 The ICF design shall be inherently safe.
3.9.1.2 The ICF shall not produce an unsafe condition or one that could result in damage to
the hosting ISS infrastructure.
3.9.1.3 The ICF design shall be in accordance with AD5.
3.9.1.4 The ICF (including the Experiment Cubes) and associated GSE and ground
operations used at the selected launcher premises shall comply with all applicable
ground safety requirements.
3.9.1.5 ICF internal materials which are in direct contact shall be compatible with each other.
3.9.1.6 The ICF shall comply with the applicable requirements of the hosting ISS
infrastructure for fire detection and suppression.
3.9.1.7 For technical and safety (e.g. fire prevention) reasons, the ICF shall be equipped with
a set of detectors (e.g. thermistors) to be used for monitoring and assessing non-
nominal situations and trigger power shutoff as necessary.
3.10 Lifetime Requirements

3.10.1.1 The Framework and Case/Drawer shall be designed for a 10-year lifetime in orbit, with
the following operational scenario assumed:
- Four (4) launches per year of experiment Cubes (increments).
- Average operational duration of each experiment: 1 month.
3.11 Reliability and Maintainability Requirements
3.11.1 General Requirements

3.11.1.1 The ICF, including the Experiment Cubes, shall be compliant to the requirements of
AD6.
3.11.1.2 The ICF, including the Experiment Cubes, shall be designed for easy handling and
transport.
3.11.1.3 In nominal cases, the ICF (excluding Experiment Cubes) shall not require crew
activities except for:
- Installation/removal of the ICF and relevant jumpers (cables, hoses).
- Installation/removal of the Experiment Cubes.

Version : 1.0.0
Date : 02-Oct-2015
Page : 22
- Manual switch-on/-off of the facility and Cubes when and if requested.

- Installation/removal of the mass memory storage devices in case of physical
download of data.
3.11.1.4 In off-nominal case, the following crew activities may be required:
- Installation/removal of the mass memory storage devices in case of failure.
- Access to the CPU of the Framework (e.g. via a KVM switch, to perform in-situ
troubleshooting in case of failure).
3.11.1.5 Standardisation shall be incorporated in flight hardware, ground hardware, software,
technical data formats, format access and procedures to facilitate replacements and
maintenance.
3.11.2 Failure Considerations

3.11.2.1 The ICF, including the Experiment Cubes, shall be designed such that a failure shall
not propagate outside the ICF itself.
3.11.2.2 Any failure of the Experiment Cubes shall not propagate to the rest of the ICF and the
other Experiment Cubes
3.11.3 Installation and Removal

3.11.3.1 The ICF, including the Experiment Cubes, shall be designed to preclude incorrect
installation.
3.11.4 Transportability
3.11.4.1 The ICF shall be transportable and storable on ground without degradation of its
functions and performances. Mode of transportation shall be by road and/or air.
3.11.4.2 Ground handling and ground transportation loads shall not exceed 80% of the design
loads for unpacked equipment (valid for Ground and Flight Models).
3.11.4.3 The handling and transport of the ICE Cubes hardware shall meet the requirements
given in AD4.
3.12 Logistics
3.12.1 Storage
3.12.1.1 The ICF, shall be compliant to 6 months ground storage after acceptance without
requiring any maintenance.
3.12.2 Packaging for Launch

3.12.2.1 Utilization of standard, well proven packing methods for launch (e.g. as defined in
RD3) shall be maximized, as long it does not impose unacceptable constraints to the
launch configuration of the various launched items.
3.12.3 Maintenance
3.12.3.1 The Framework and the PharmaLab shall be regarded as On-Orbit Replaceable Units
(ORUs).

Version : 1.0.0
Date : 02-Oct-2015
Page : 23
3.12.3.2 The set of fans creating the air circulation in case of EDR2 (see Figure 2-4) or CAPL
(see Figure 2-5) installation, shall be regarded as ORU (TBC).
Note: these fans are the only elements of the Case/Drawer subject to failure.
3.12.4 Ground Refurbishment

3.12.4.1 The ICF design shall allow for an easy and safe maintenance on ground, including
inspection, servicing and replacement of failed part operations.
3.12.4.2 The design of the ICF, including the Experiment Cubes, shall allow easy, economic
refurbishment on ground of those elements which need periodic replacement and are
subject to further reuse, both for maintenance and for scientific reasons.
3.12.4.3 The design of the Experiment Cubes shall maximise the use of elements that can be
reutilised after refurbishment on ground.

Version : 1.0.0
Date : 02-Oct-2015
Page : 24
4 Ground Models Requirements
4.1 General Requirements

4.1.1.1 The ground models shall be designed for a minimum lifetime of 4 years. Given the
extensive use in ground laboratory conditions, preventive and corrective maintenance
is allowed.
4.1.1.2 The design and the operations of the ground models shall be in compliance to the
safety standards of the facilities in which they are used.
4.2 Engineering Model / Ground Model (EM/GM)

4.2.1.1 The EM/GM shall be identical to the Flight Model in terms of Form, Fit and Function.
4.2.1.2 The EM/GM shall support off-nominal operations and troubleshooting as necessary.
4.2.1.3 The EM/GM shall be adequate for supporting procedure and software development
and validation.
4.2.1.4 The EM/GM shall be able to support (along with complimentary Ground Support
Equipment (GSE), the integrated tests in the Ground Model of the ISS hosting
infrastructure.
4.2.1.5 The EM/GM shall be able to support the Experiment Sequence Tests (ESTs).
4.2.1.6 The EM/GM shall support the preparation and validation of operations procedures.
4.3 Training Model (TM)

4.3.1.1 The TM shall be compliant with the general requirements specified in AD19. Proper
tailoring of the requirements shall be produced, based on the specific objectives of the
ICE Cubes Facility and PharmaLab TMs.
4.3.1.2 The TM shall support installation / de-installation, activation/deactivation with the
Ground Model of the ISS hosting infrastructure.
4.3.1.3 The TM shall be capable of representing all crew interfaces and interactions required
during unpacking, integration, operation, de-integration and disposal.
4.3.1.4 The TM shall be identical to the Flight Model in terms of packaging, external
dimensions, interfaces, appearance and labelling.
4.3.1.5 The TM shall include realistic (working) mechanisms, switches, connectors, hosing,
harness and removable parts (e.g. HDDs) operated by the crew. Elements not
operated by the crew shall be reproduced at static mock-up level.
4.3.1.6 The TM control and indicator LEDs shall correspond with, and respond to, the
appropriate functional conditions created by the crew’s operations (mainly switch-
on/off).
4.3.1.7 The TM shall be adequate for supporting studies and testing regarding installation /
de-installation with the upload and disposal vehicles.
4.3.1.8 A TM of the typical Experiment Cube (1U size) shall be provided, which, in addition of
the shape, reproduces all the interfaces with the Framework.

Version : 1.0.0
Date : 02-Oct-2015
Page : 25
4.4 Demo Model (DM)
4.4.1 ICE Cubes Facility DM

4.4.1.1 The DM of the facility shall be composed of:
- one (1) Case/Drawer DM,
- one (1) Framework DM,
- one (1) Experiment Cube (1U size) DM.
Note: External harness or fluidic hoses are not necessary.
4.4.1.2 The functionality of the DM shall be at the same level as that of the TM (e.g. the
Framework can slide inside the Case/Drawer and the Experiment Cube can be mated
to the Framework).
4.4.2 PharmaLab DM
4.4.2.1 The DM shall be composed of mock-ups of the main components of the PharmaLab.
4.4.2.2 The case/cover shall be removable for showing the layout of internal parts.
4.4.2.3 The PharmaLab Card DM shall be reproduced at Ground Model level and shall be
removable.
4.4.2.4 Materials selection and manufacturing processes shall be driven by requirements of
transportability and shall be tailored to the specific use of this model (participations to
fairs/exhibitions).

Version : 1.0.0
Date : 02-Oct-2015
Page : 26
5 GSE Requirements
5.1 General
5.1.1.1 The ICE Cubes GSE shall be The GSE will be composed, as a minimum, by of the
following items necessary to support integration and test at system level:
• 28V DC laboratory power supply (for powering the facility);
• a commercial-grade computer simulating the ISS infrastructure and commanding
/ monitoring the facility + Experiment Cubes + PharmaLab;
• a commercial-grade computer and relevant “Cubes simulator” extensions, to be
used for simulating the Experiment Cubes installed on the facility and running in
parallel;
• a forced-air ventilation system to reproduce the forced-air cooling or the EPM
rack (only for EPM accommodation; in case of cabin accommodation, the fans
creating the forced-air flow will be part of the facility);
• a dummy case to be used for thermal test on the facility EM/GM if the actual
Case/Drawer design and manufacturing is not finalized (pending agreement with
an Agency);
• a water cooling system to reproduce the water cooling interface and resource of
EDR2 (only in case of accommodation in EDR2);
• Line Impedance Stabilization Network (LISN) for EMC/ESD tests;
• test harnesses, including flight connector savers;
• transport/storage containers.
5.1.1.2 The GSE shall support the ICE Cubes facility and PharmaLab testing and calibration
at three levels:
- Assembly levels whenever required for special verification;
- ICE Cubes facility and PharmaLab stand-alone;
- ICE Cubes facility (Ground and Flight Models) integrated in the ISS hosting
infrastructure Ground Model.
5.1.1.3 The GSE design shall be in accordance with the interfaces and the requirements
imposed by those facilities in which it has to operate, including facility’s safety
standards.
5.1.1.4 The number of containers and similar elements necessary for the stowage at ambient
temperature of the ICE Cubes related items shall be minimized.
5.1.1.5 The ground transportation containers shall be capable to withstand the transportation
loads by a safety factor of 4.
5.1.1.6 The ground transportation containers of the flight hardware shall provide a sealed
containment. Humidity entering the container shall be absorbed by desiccants.
5.1.1.7 The ground transportation containers of the Ground and Flight Models shall be
equipped with shock and temperature sensors and recorder.
5.2 GSE to ICE Cubes H/W Interfaces

5.2.1.1 The GSE or parts thereof used in direct contact with flight hardware shall meet the
material requirements specified in this document for flight hardware.
5.2.1.2 The GSE shall not deteriorate or contaminate the flight hardware.

Version : 1.0.0
Date : 02-Oct-2015
Page : 27
5.2.1.3 The design of the GSE shall not impose constraints to the flight hardware.
5.2.1.4 Parts of the GSE, which will not be used in contact with flight hardware shall use parts,
materials, and processes compatible with the usage environment and consistent with
good commercial aircraft practices.
5.2.1.5 The GSE shall be compatible with the interfaces available in the facilities where it will
be operated.
5.3 Detailed Requirements

As per Figure 1-1, the detailed requirements for the Ground Support Equipment will be defined in the
dedicated ICE Cubes GSE Specification.

Version : 1.0.0
Date : 02-Oct-2015
Page : 28
6 Ground Segment Requirements
6.1 General
6.1.1.1 The ICE Cubes Ground Segment shall be composed of a Mission Control Centre
(MCC) and the various User Home Bases (UHBs).
6.1.1.2 The MCC shall support the in-flight operations by allowing for complete command and
control of the ICE Cubes facility and of the PharmaLab.
6.1.1.3 The MCC shall manage the power-on/-off of the facility, the various Experiment Cubes
and the PharmaLab.
6.1.1.4 The MCC shall be able to monitor the complete set of functional parameters of the
facility and the PharmaLab.
6.1.1.5 The MCC shall be able to monitor a (predefined) set of critical parameters for each
Experiment Cube to monitor its health status and decide for possible power-off.
6.1.1.6 Following the approach of section 2.1.4, the Ground Segment shall allow the customer
for commanding/monitoring the single Experiment Cubes and retrieving the
(predefined) scientific data of interest directly at its home base (power–on/-off of the
Experiment Cube is managed by the MCC).
6.2 Detailed Requirements

As per Figure 1-1, detailed requirements for the Ground Segment will be defined in the dedicated ICE
Cubes Ground Segment Specification.

Version : 1.0.0
Date : 02-Oct-2015
Page : 29
Appendix A Terms and Definitions
Automatic Control Control and monitoring activity performed without the need of external
and Monitoring intervention by the crew or ground station
Continuous Noise A significant noise source which exists for a cumulative total of eight hours or
Source more in any 24-hour period is considered a continuous noise source.
Ground Segment It is composed of the Mission Control Centre (MCC) and the various User
Home Bases (UHBs) where the customers of the Experiment Cubes can
operate their experiment and receive scientific data
Integrated System Set of tests the payload undergoes to being integrated in a ground simulator
Tests of the ISS hosting facility.
Intermittent Noise A significant noise source which exists for a cumulative total of less than
Source eight hours in a 24-hour period is considered an intermittent noise source.
Loss-less Data compression techniques in which no data is lost.

Compression
Lossy Wavelet Data compression technique in which some (can be pre-determined) data is
Compression lost, due to smoothing of the data.
Telescience Experiments operated from a (long) distance (e.g. from the ground).
Depending on the characteristics of the communication link, it can allow for
near real time interaction between the operator and the telecommanded
experiment

Attachment 0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Attachment 0

Uploaded by

Copyright:

Available Formats

Reference : Ref.

System Requirements Specification

Title : System Requirements Specification

Grant Agreement N° : 666815

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

DOCUMENT APPROVAL SHEET

Name Company Signature and Date

Prepared by: T. Peignier Space Applications Services

PA Checked by: L. Tazi Space Applications Services

Approved by: M. Ricci Space Applications Services

Space Applications Services NV/SA Tel: +32-(0)2-721.54.84

Leuvensesteenweg 325 Fax: +32-(0)2-721.54.44

1932 Zaventem, Belgium Web: www.spaceapplications.com

This document is the property of

Space Applications Services NV/SA.

All rights reserved.

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

DOCUMENT CHANGE RECORD

Version Date Author Changed Sections Reason for Change / RID No

1.0.0 02-Oct-2015 T. Peignier Initial release

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

1.1 Purpose and Scope

1.2 Specifications Organization

PharmaLab GSE Ground Segment

Procurement Specification (as necessary)

Figure 1-1: Specifications tree

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

1.3 Applicable Documents

AD2 Astrium – Columbus Pressurized Payloads Interface Requirements Document, COL-RIBRE-

AD10 ECSS – Space engineering: Fracture control, ECSS-E-ST-32-01C, Rev. 1, 06-Mar-2009.

AD12 ECSS – Space engineering: Materials, ECSS-E-ST-32-08C, Rev. 1, 15-Oct-2014.

AD13 ECSS – Space engineering: Mechanisms, ECSS-E-ST-33-01C, 06-Mar-2009.

AD14 ECSS – Space engineering: Software engineering, ECSS-E-ST-40C, 06-Mar-2009

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

AD18 ECSS – Space product assurance: Software quality, ECSS-Q-ST-80C, 06-Mar-2009.

AD19 ESA – Training Model Requirements, MSM-AT-CPT-GNL-RQ-001, Issue 1 Rev. 1, 30-Mar-

AD22 ECSS – Space engineering: Structures general requirements standard, ECSS-E-ST-32C,

AD24 NASA – Non-destructive Evaluation Requirements for Fracture-Critical Metallic Components,

AD25 ECSS – Space product assurance: Derating - EEE components, ECSS-Q-ST-30-11C,

1.4 Reference Documents

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

RD10 Wikipedia – USB [cited 2-Oct-2015]. Available from: https://en.wikipedia.org/wiki/USB

RD11 ECSS – Space engineering: Adhesive bonding handbook, ECSS-E-HB-32-21A, 20-Mar-

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

ICE Cubes International Commercial Experiment Cubes

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification

2.1 ICE Cubes System Overview

The ICE Cubes facility is composed of:

• The Framework, accommodating up to 16 or 20 (TBC) Experiment Cubes, and providing power

Figure 2-1: ICE Cubes facility conceptual view

Copyright by Space Applications Services – All Rights Reserved

System Requirements Specification