SSP_50901.docx

Integrated Stowage Platform (ISP) to Multi-Purpose Logistics Module (MPLM) Interface Control Document (ICD) Part 1

International Space Station Program

Baseline

July 2009

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas

SSP 50901

Baseline

REVISION AND HISTORY PAGE

vi

PREFACE

INTEGRATED STOWAGE PLATFORM (ISP) TO

MULTI-PURPOSE LOGISTICS MODULE (MPLM)

INTERFACE CONTROL DOCUMENT (ICD) PART 1

The contents of this document are intended to be consistent with the tasks and products to be prepared by Program participants. The SSP 50901, Integrated Stowage Platform (ISP) to Multi-Purpose Logistics Module (MPLM) Interface Control Document (ICD) Part 1, shall be implemented on Node 3 and the MPLM. This document is under the control of the Space Station Control Board, and any changes or revisions will be approved by the Program Manager.

INTERNATIONAL SPACE STATION PROGRAM

INTEGRATED STOWAGE PLATFORM (ISP) TO

MULTI-PURPOSE LOGISTICS MODULE (MPLM)

INTERFACE CONTROL DOCUMENT (ICD) PART 1

june 2009

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

INTEGRATED STOWAGE PLATFORM (ISP) TO

MULTI-PURPOSE LOGISTICS MODULE (MPLM)

INTERFACE CONTROL DOCUMENT (ICD) PART 1

june 2009

CONCURRENCE

INTERNATIONAL SPACE STATION PROGRAM

INTEGRATED STOWAGE PLATFORM (ISP) TO

MULTI-PURPOSE LOGISTICS MODULE (MPLM)

INTERFACE CONTROL DOCUMENT (ICD) PART 1

LIST OF CHANGES

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

SSP 41173

Revision D v

TABLE OF CONTENTS

appendix

TABLE

figure

SSP 50901

Baseline

SSP 50901

Baseline

INTRODUCTION

PURPOSE

The purpose of this document is to provide definition of the physical, functional, and environmental requirements between the Multi Purpose Logistics Module (MPLM) and the Integrated Stowage Platform (ISP). Ground requirements are covered by the SSP 50318, Prime Item Development Specification for Node 3.

Scope The scope of this document is limited to the structural/mechanical interfaces between the MPLM and the ISP that support the launch/landing/on−orbit event

PRECEDENCE

In the event of conflict between SSP 41000, Space Station System Specification, and the contents of this Interface Control Document (ICD), only the requirements of SSP 41000 applicable to each International Partner and to the National Aeronautics and Space Administration (NASA) shall take precedence.

responsibility and change authority This document is prepared and maintained in accordance with SSP 30459, International Space Station Interface Control Plan.

SSP 50901

Baseline

SSP 50901

Baseline (Draft – June 2009)

1-1 4-2

DOCUMENTS

APPLICABLE DOCUMENTS

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The documents listed in this paragraph are applicable to the extent specified herein. Inclusion of applicable documents herein does not in any way supersede the order of precedence identified in Paragraph 1.3 of this document.

ASTM E380

Rev. A, 1993 Standard Practice for Use of the International System of Units (SI) (the Modernized Metric System)

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

N/A

SSP 41173

Revision D

2-1 interfaces general interface description isp description The Integrated Stowage Platform (ISP) interfaces to the Multi-Purpose Logistics Module (MPLM) consist of structural/mechanical attachment for the launch/landing/on-orbit event.

module description The MPLM will support ISP structural/mechanical attachment for the launch/landing/on−orbit event.

ISP INTERFACE FUNCTIONS

The ISP will support the following function at the interface with the MPLM: Structural/Mechanical Attachment.

MODULE INTERFACE FUNCTIONS

The MPLM will support the following function at the interface to ISPs: Launch/landing/on−orbit Structural/Mechanical Attachment.

INTERFACE RESPONSIBILITIES

RESPONSIBILITY FOR ISP

The ISP designer will ensure that the ISP conforms to the interface requirements contained within this document.

RESPONSIBILITY FOR MODULE

NASA will ensure the attachment locations in the MPLM conform to the interface requirements contained within this document. The acceptable locations for the ISPs will be determined for each mission based on a structural assessment of the MPLM module.

ENGINEERING UNITS, TOLERANCES, AND CONVERSIONS

ENGINEERING UNITS

All dimensions will be defined in the English system of units followed by the parenthetical SI metric equivalent.

TOLERANCES AND CONVERSIONS

All tolerances and conversions will be in accordance with ASTM E380, Standard Practice for Use of the International System of Units (SI).

INTERFACE REQUIREMENTS

STRUCTURAL INTERFACES

ISPs shall interface to the MPLM at attach points A, B, C1, and E, as shown in Figure 3.2.1-1, ISP Interface Points, corresponding to MPLM attach points A, B, C1, and E as shown in Figure 3.2.1-2, MPLM Interface Points. Figures 3.2.1-3 and 3.2.1-4 provide a details of the ISP/MPLM attach points.

Figure 3.2.1-1 ISP Interface Points

Figure 3.2.1-2 MPLM Interface Points

Figure 3.2.1-3 ISP/MPLM Attach Points C1 & E

Figure 3.2.1-4 ISP/MPLM Attach points A & B

COORDINATE SYSTEMS

The integrated ISP uses the local Coordinate System (CS) shown in Figure 3.2.1-1 referencing the ISS Standard Payload Rack (ISPR) Coordinate System such that xISP=-xISPR, yISP=-zISPR, and zISP=-yISPR. Information, like ISP Interface loads, from MPLM will be provided in the ISPR coordinate system.

ENVELOPE REQUIREMENTS

The integrated ISP shall not exceed the envelope defined in SSP 41017, section 3.2.1.1, Envelope Requirements, in all directions.

These envelope limit values may be superseded by results from flight specific clearance analysis based on Verification Loads Analyses (VLA) and cargo configuration of the MPLM with ISPs.

MASS PROPERTIES

The mass of an integrated ISP shall be less than or equal to 793 pounds (lbs) (360.45 kg) for launch, and landing.

ISP MINIMUM RESONANT FREQUENCY

Cargo loaded ISPs shall have a minimum natural frequency greater than 20 Hertz (Hz) in hard mounted conditions.

INDUCED ENVIRONMENTS

ISP interfaces to the MPLM shall be capable of operation during and after exposure to any feasible combination of the following environments.

ACCELERATION

ISP accelerations, in Local ISP Coordinate System, are defined in Table 3.2.5.1-1, ISP Accelerations (Maximum Predicted Level).

ISPs to be flown in MPLM shall be designed to withstand the applicable acceleration environment when constrained to an infinitely massive and stiff boundary.

These ISP design accelerations were defined for launch in the ISS Node Element. The MPLM design acceleration requirements are higher in all axes. Therefore, these acceleration environment values shall be superseded by results from flight specific CLA of the MPLM with ISPs.

Table 3.2.5.1-1 ISP Accelerations (Maximum Predicted Level) in Local ISP CS

RANDOM VIBRATION

ISP interfaces to the MPLM shall be capable of operation during and after exposure to the random vibration environment defined in SSP 41017, Table 3.2.1.4.1.2-1, MPLM Random Vibration Environment.

INTERFACE LOADS

Interface loads for launch and landing are the static, dynamic, and pressure loads exchanged between the ISP and the module through the attach points A, B, C1 and E. For all flight and ground events excluding MPLM differential pressure, the ISPs shall not exceed the interface loads, in the ISPR coordinate system, defined in Table 3.2.5.3-1, ISP Interface Design Limit Loads. Table 3.2.5.3-2 defines the loads on ISPs due to differential pressure.

The Interface Design Limit Loads identified above were derived for an ISP attached in a Node, not in a MPLM. These Interface load values may be superseded by results from flight specific CLA of the MPLM with ISPs.

Table 3.2.5.3-1 ISP Interface Design Limit Loads, Forces Defined in ISPR CS Limit Load Lbf (N) Attach Point

(+/- 17598)

(+/- 1227) +/- 276 (+/- 1227)

(+/- 11856) +/-2665 (+/- 11856)

(+/- 29519) +/-6636 (+/- 29519)

Table 3.2.5.3-2 ISP Interface Loads Due to Differential Pressure, Forces Defined in ISPR CS.

Limit Load Lbf (N) Attach Point

(+/- 808) +/-419 (+/- 1865) +/- 136 (+/- 603) +/- 102 (+/- 453)

(+/- 224) +/-50 (+/- 223) +/- 54 (+/- 241) +/- 54 (+/- 239)

(+/- 2119) +/-511 (+/- 2272) +/- 7 (+/- 31) +/- 41 (+/- 184)

Launch Acoustics ISPs launched in the MPLM shall be capable of operation after exposure to the launch minimum acoustic environment defined in SSP 41017, Table 3.2.1.4.1.1−1, MPLM Internal Acoustic Noise Spectra.

Mplm Interface requirements Envelope requirements Each rack location within the MPLM shall reserve volume for the static and dynamic envelope shown in SSP 41017, section 3.2.2.1 Envelope Requirements, in all directions.

These envelope limit values may be superseded by results from flight specific clearance analysis based on CLA and cargo configuration of the MPLM with ISPs.

MPLM mass properties Each ISP location within the MPLM shall accommodate the maximum integrated ISP mass of 793 lbs (360.4 kg).

Mplm Launch/Landing/On-orbit Attachment The MPLM shall incorporate structural/mechanical provisions for attachment of the ISP for the launch/landing/on–orbit event.

mplm induced environments MPLM interfaces to the ISP shall be capable of operation during and after exposure to any feasible combination of the following environments launch accelerations The MPLM shall impart an acoustic environment no greater than defined in SSP 41017, Table 3.2.1.4.1.1-1, MPLM Internal Acoustic Noise Spectra.

Random vibrations MPLM interfaces to the ISP shall be capable of operation during and after exposure to the random vibration environment defined in SSP 41017, Table 3.2.1.4.1.2-1, MPLM Random Vibration Environment.

interface loads Interface loads for launch and landing are the static, dynamic, and pressure loads exchanged between the module and the rack through the attach points A, B, C1 and E. The MPLM shall be capable of accommodating the interface loads defined in Table 3.3.4.3-1, MPLM Interface Design Limit Loads, Defined in MPLM CS. It is recognized that the ISP Interface loads and MPLM Interface loads tables are different since the ISP was designed for a Node. Therefore, the MPLM will have to perform verification analysis on a mission-by-mission basis as has been identified throughout the document. Table 3.3.4.3-2, MPLM Interface Loads, Due to Differential Pressure in MPLM CS, defines the loads on ISPs due to differential pressure.

SSP 50901

Baseline

SSP 50901

Baseline

3-1 Table 3.3.4.3-1 MPLM Interface Design Limit Loads, Defined in MPLM CS

(14894/-8686) 2292/-2921 (10195/-12995) 6112/-5236 (27187/-23288) 2966/-2270 (13195/-10097)

(11295/-14094)

(16693/-13395) 1953/-2404 (8686/-10694)

Note: Uses A, B, C1, and E points and the forces were divided by 1.4. to get limit values. The values are provided in English and metric units.

Baseline

SSP 41173

Revision D

3-9 Table 3.3.4.3-2 MPLM Interface Loads, Due to Differential Pressure in MPLM CS

SSP 50901

Baseline (Draft – June 2009)

3-10 interface verification There will be no requirements that require joint verification for this interface. Verification of requirements will be performed separately by the rack provider, and the element provider, according with the verification responsibility matrix reported in Table 4.0-1.

TABLE 4.0-1 INTERFACE VERIFICATION (page 1 of 2)

1.0

X

1.1

X

1.2

X

1.3

X

1.4

X

2.0

X

2.1

X

2.2

X

3.0

X

3.1

X

3.1.1

X

3.1.1.1

X

3.1.1.2

X

3.1.1.3

X

3.1.1.4

X

3.1.2

X

3.1.2.1

X

3.1.2.2

X

3.1.3

X

3.1.3.1

X

3.1.3.2

X

3.2

X

3.2.1.1

X

3.3

X

TABLE 4.0-1 INTERFACE VERIFICATION (page 2 of 2)

3.3.1

X

3.3.2

X

3.3.3

X

3.3.4

X

3.3.4.1

X

3.3.4.2

X

3.3.4.3

X

SSP 50901

Baseline

4-1 Appendix A - Acronyms and abbreviations

A-1 4-2 Appendix B – glossary <reserved>

SSP 50901

Baseline

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

Table C-1 to be determined items

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

table C-2 TO BE RESOLVED ISSUES

C-1 C-2 image2.emf image3.emf image4.emf image5.png image6.png image7.jpeg image8.jpeg image1.wmf