SSP 50200-10-Baseline-DCN 009-Collated Master STATION PROGRAM IMPLEMENTATION PLAN Sustaining Engineering.pdf

SSP 50200-10

Baseline

Station Program Implementation Plan, Volume 10: Sustaining Engineering

International Space Station Program

Baseline

Incorporates DCN 009

December 1997

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

REVISION AND HISTORY PAGE

REV. DESCRIPTION PUB.

DATE

-- Initial Release (Reference per SSCD 000905, EFF. 05/30/98 06/19/98

DCN 001 (not released)

DCN 002 (not released)

DCN 003 (Reference per SSCD 001989, EFF. 07/07/99) 06/16/00

DCN 004 (Reference per SSCD 002700, EFF. 08/21/00) 10/03/00

DCN 005 (Reference per SSCD 001784, EFF. 10/23/00) 12/01/00

(SSCD 001784 authorized DCN 002 to SSP 50200-10; however, since this directive was received after the incorporation of DCNs 003 and 004, it will be identified as DCN 005 in keeping with the progression of DCN numbering for this document.)

DCN 006 (Reference per SSCD 003969, EFF. 01-16-02) 06/28/02

DCN 007 (Reference per SSCD 007108, EFF. 12-10-02) 04/21/03

DCN 008 (Reference per SSCD 010542, EFF. 01/12/09) 06/18/09

DCN 009 (Reference per SSCD 012665, EFF. 03/03/11) 04/20/11 i

INTERNATIONAL SPACE STATION PROGRAM

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

DECEMBER 1997

ii

PREFACE

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

This document is the Station Program Implementation Plan, Volume 10: Sustaining Engineering. The purpose of this document is to define the integrated function that involves all International Partners/Participants (IP/Ps). This document is not intended to invoke requirements upon the processes which are strictly internal to an International Partner (IP) or Participant.

The contents of this document are intended to be consistent with the functions as defined in SSP 50011, Concept of Operation and Utilization. This document is under control of the Space Station Control Board (SSCD).

iii

SPACE STATION CONTROL BOARD APPROVAL NOTICE

INTERNATIONAL SPACE STATION PROGRAM

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

DECEMBER 1997

(see directive 905 signature) R. Brinkley National Aeronautics and Space Administration

Date

B. Ostroumov Russian Space Agency

Date

/s/ A. Poirier 30 May 1998 A. Poirier Canadian Space Agency

Date

/s/ M. Saito 30 May 1998 M. Saito National Space Development Agency of Japan

Date

/s/ G. Rum 30 May 1998 G. Rum Italian Space Agency

Date iv

INTERNATIONAL SPACE STATION PROGRAM

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

CONCURRENCE

DECEMBER 1997

Prepared by: Irene Taylor OX

BOOK MANAGER AND LEAD, ISSP OFFICE

SUSTAINING ENGINEERING, INTERNATIONAL

PARTNER/PARTICIPANT

ORG

/s/ Irene Taylor 01/14/98

SIGNATURE DATE

Supervised by: Jack Bullman OX

TITLE, NAME OF BOARD/DIV/DIRECTORATE ETC. ORG

/s/ Jack Bullman 01/20/98

NASA DQA: Richard Delgado OL

CONFIGURATION MANAGEMENT ORG

/s/ Richard D. Delgado 01-09-98 iv-a

INTERNATIONAL SPACE STATION PROGRAM

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

CONCURRENCE

DECEMBER 1997

Developer Concurrence: Oleg Babkov RSC-E

ROCKET SPACE CORPORATION - ENERGIA ORG

Developer Concurrence: Vladimire Soloviev RSC-E

Developer Concurrence: Yuri Antoshechkin RSC-E

SSP 50200-10 19 April 2011 v

INTERNATIONAL SPACE STATION PROGRAM

STATION PROGRAM IMPLEMENTATION PLAN,

VOLUME 10: SUSTAINING ENGINEERING

LIST OF CHANGES

DECEMBER 1997

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

SSCB Entry Date Change Paragraph(s)

June 1998 Baseline All

June 2000 DCN 003 Appendix F

September 2000 DCN 004 Appendix G

November 2000 DCN 005 Appendix AA

June 2002 DCN 006

April 2003 DCN 007 Appendix D, Appendix G

November 2008 DCN 008 Appendix I

April 2011 DCN 009 Appendix J vi

TABLE OF CONTENTS

PARAGRAPH PAGE

1.0 INTRODUCTION ................................................................................................................... 1-1

1.1 PURPOSE ............................................................................................................................. 1-1

1.2 SCOPE .................................................................................................................................. 1-1

1.3 PRECEDENCE ...................................................................................................................... 1-1

1.4 DELEGATION OF AUTHORITY ............................................................................................ 1-1

1.5 ISSUES AND OPEN WORK.................................................................................................. 1-2

2.0 DOCUMENTS ....................................................................................................................... 2-1

2.1 APPLICABLE DOCUMENTS................................................................................................. 2-1

2.2 REFERENCE DOCUMENTS ................................................................................................ 2-1

2.3 SOURCE DOCUMENTS ....................................................................................................... 2-3

2.4 SPIP DOCUMENTATION TREE ........................................................................................... 2-4

3.0 OVERVIEW OF SUSTAINING ENGINEERING .................................................................... 3-1

3.1 OVERVIEW OF SUSTAINING ENGINEERING TASKS ........................................................ 3-1

3.2 SUSTAINING ENGINEERING SUPPORT TO LAUNCH VEHICLE INTEGRATION

AND DEINTEGRATION ........................................................................................................ 3-2

3.3 SUSTAINING ENGINEERING FOR ON-ORBIT OPERATIONS ........................................... 3-3

3.3.1 REAL-TIME ENGINEERING SUPPORT ............................................................................... 3-3

3.3.2 OFF-LINE ENGINEERING SUPPORT .................................................................................. 3-4

3.3.2.1 PERFORMANCE ASSESSMENTS ....................................................................................... 3-4

3.3.2.2 ANOMALY RESOLUTION ..................................................................................................... 3-4

3.3.2.3 FACILITIES, MODELS, AND ANALYTICAL TOOLS ............................................................. 3-5

3.3.2.4 HARDWARE MODIFICATIONS ............................................................................................ 3-5

3.3.2.5 SOFTWARE MODIFICATIONS ............................................................................................. 3-6

3.3.2.6 SAFETY ................................................................................................................................ 3-6

3.3.2.7 CONFIGURATION MANAGEMENT ...................................................................................... 3-6

4.0 INTERNATIONAL PARTNER AND PARTICIPANT SUSTAINING ENGINEERING

TASKS ................................................................................................................................... 4-1

5.0 INTERNATIONAL PARTNER AND PARTICIPANT BILATERALS ........................................ 5-1

APPENDIX

A ACRONYMS AND ABBREVIATIONS ................................................................................... A-1

B GLOSSARY OF TERMS <RESERVED> .............................................................................. B-1

C MATRIX OF ISSUES TO BE RESOLVED ............................................................................. C-1

D MATRIX OF TO BE DETERMINED ITEMS ........................................................................... D-1

E NASA RSA BILATERAL ........................................................................................................ E-1

F NASA CSA BILATERAL ........................................................................................................ F-1

G NASA ASI BILATERAL .......................................................................................................... G-1

DCN 004

DCN 006

vii

H NASA NASDA BILATERAL ................................................................................................... H-1

I NASA ESA BILATERAL ........................................................................................................ I-1

J NASA/ASI PERMANENT MULTIPURPOSE MODULE (PMM) SUSTAINING

ENGINEERING PLAN ........................................................................................................... J-1

AA SUSTAINING ENGINEERING DATA, SOFTWARE, AND HARDWARE EXCHANGE

PROCESS AND DELIVERABLES ......................................................................................... AA-I

TABLE

4.0-1 INTERNATIONAL PARTNER AND PARTICIPANT SUSTAINING ENGINEERING

TASKS ................................................................................................................................... 4-1

C.1-1 MATRIX OF ISSUES TO BE RESOLVED ............................................................................. C-2

D.1-1 MATRIX OF TO BE DETERMINED ITEMS ........................................................................... D-2

ANNEX A-1 NODE 2 ARCHITECTURE BREAKDOWN VERSUS RESPONSIBILITY .............................. A-1 ANNEX A-2 NODE 3 ARCHITECTURE BREAKDOWN VERSUS RESPONSIBILITY .............................. A-6

ANNEX A-3 CUPOLA ARCHITECTURE BREAKDOWN VERSUS RESPONSIBILITY ............................ A-11

FIGURE

2.4-1 SPIP DOCUMENTATION TREE ........................................................................................... 2-4 DCN 004

DCN 009

DCN 008

DCN 008

SSP 50200-10 20 July 2000

1-1

1.0 INTRODUCTION

This document describes the International Space Station (ISS) Program implementation plan for Sustaining Engineering.

1.1 PURPOSE

The purpose of this volume is to document the tasks, roles, and responsibilities for each of the various Sustaining Engineering tasks.

1.2 SCOPE

This multilateral main Volume applies to all the Partners, which consists of the National Aeronautics and Space Administration (NASA), Russian Space Agency (RSA), Canadian Space Administration (CSA), the European Space Agency (ESA), and the National Space Development Agency of Japan (NASDA). In addition, this volume also applies to the main Participant, the Agenzia Spaziale Italiana (ASI). This volume covers the time period between the start of planning for Sustaining Engineering throughout the life of the On-Orbit Space Station.

Each International Partner/Participant (IP/P) will provide engineering support to their hardware/software, but the time phasing and specific implementation of the Sustaining Engineering functions will vary. Implementation details for each IP/P will be covered in the respective bilateral appendix.

It should be noted that the IPs have organized their programs differently from NASA and that some of the functions grouped by NASA under the term “sustaining engineering” are covered under different organizational categories by the IPs. Such differences, where important, are pointed out in this document.

1.3 PRECEDENCE

Information contained in this document is consistent with ISSP documentation.

In the case of conflict between this document and SSP 50011, Concept of Operation and Utilization, the Concept of Operation and Utilization (COU) shall take precedence. In the case of conflict between this document and SSP 50200- 01, Station Program Implementation Plan, Volume 1: Station Program Management Plan, the Station Program Implementation Plan (SPIP) Volume 1 shall take precedence.

1.4 DELEGATION OF AUTHORITY

This document is approved by, and is subject to, the Space Station Control Board (SSCB) change control process. This document was developed by the ISS Program office’s Sustaining Engineering Office and the IP/Ps.

The ISS Program Sustaining Engineering Office serves as the book manager for this document.

1-2

1.5 ISSUES AND OPEN WORK

Because of the complex and dynamic nature of ISS development and implementation, there can be unresolved issues concerning new or existing processes. These unresolved issues are identified by a <TBR X-X> in the text.

Appendix C, Matrix of Issues To Be Resolved, captures the To Be Resolved (TBR) issues associated with this implementation plan. Processes associated with a TBR issue are not considered baselined operating processes until the issue is resolved and the implementation plan text is updated.

Not all processes have been defined when discussing Partners’ roles and responsibilities. As this document evolves, the processes become better defined and are incorporated into the implementation plan. All open work is identified by a <TBD X-X> in the text. Appendix D, Matrix of To Be Determined Items, captures the To Be Determined items associated with the implementation plan.

Once the To Be Determined (TBD) information is defined, the correct text is inserted in place of the TBD in the document.

2-1

2.0 DOCUMENTS

2.1 APPLICABLE DOCUMENTS

The following documents include specifications, models, standards, guidelines, handbooks, and other special publications. The current issue of the following documents is identified in the Program Automated Library System (PALS) (http://issa-www.jsc.nasa.gov/cgi-bin/dsql+/ORAP?-h+palshome). 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.

SSP 30599 Safety Review Process

SSP 41170 Configuration Management Requirements

SSP 50011 Concept of Operation and Utilization

SSP 50021 Safety Requirements Document

SSP 50123 Configuration Management Handbook

SSP 50200-01 Station Program Implementation Plan, Volume 1: Station Program Management Plan

SSP 50200-06 Station Program Implementation Plan, Volume 6: Cargo Physical Processing

SSP 50234 Sustaining Engineering Implementation Plan

2.2 REFERENCE DOCUMENTS

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

SSP 41170 Configuration Management Requirements

SSP 50010-02 Documentation Requirements, Standards and Guidelines, Volume 2: Guidelines

SSP 50033 NASA/CSA Bilateral Integration and Verification Plan

SSP 50034 NASA/ESA Bilateral Integration and Verification Plan

SSP 50035 NASA/NASDA Bilateral Integration and Verification Plan

SSP 50101 NASA/RSA Bilateral Integration and Verification Plan

SSP 50200-10 01 July 2002

2-2

SSP 50102 NASA/ASI Bilateral Integration and Verification Plan

SSP 50124 NASA/CSA Bilateral Data Exchange Agreements, Lists, and Schedules.

SSP 50125 NASA/ASI Bilateral Data Exchange Agreements, Lists, and Schedules

SSP 50126 NASA/NASDA Bilateral Data Exchange Agreements, Lists, and Schedules

SSP 50127 NASA/ESA Bilateral Data Exchange Agreements, Lists, and Schedules

SSP 50137 NASA/RSA Bilateral Data Exchange Agreements, Lists, and Schedules

SSP 50200-02 Station Program Implementation Plan, Volume 2: Program Planning and Manifesting

SSP 50200-03 Station Program Implementation Plan, Volume 3: Cargo Analytical Integration

SSP 50200-04 Station Program Implementation Plan, Volume 4: Payload Engineering Integration

SSP 50200-05 Station Program Implementation Plan, Volume 5: Logistics and Maintenance

SSP 50200-07 Station Program Implementation Plan, Volume 7: Training

SSP 50200-08 Station Program Implementation Plan, Volume 8: Increment Execution Preparation

SSP 50200-09 Station Program Implementation Plan, Volume 9: Real-Time Operations

SSP 50482 ISSP Software Management Plan

SSP Number

<TBD 2-1>

NASA/RSA Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

SSP Number

<TBD 2-1>

NASA/CSA Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

2-3

SSP Number

<TBD 2-1>

NASA/ESA Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

SSP Number

<TBD 2-1>

NASA/NASDA Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

SSP Number

<TBD 2-1>

NASA/ASI Bilateral Hardware and Software Exchange Agreements, Lists, and Schedules

No number Memorandum of Understanding between the United States National Aeronautics and Space Administration and the European Space Agency on Cooperation in the Detailed Design, Development, Operations, and Utilization of the Permanently Manned Civilian Space Station

No number Memorandum of Understanding between the United States National Aeronautics and Space Administration and the Government of Japan on Cooperation in the Detailed Design, Development, Operations, and Utilization of the Permanently Manned Civilian Space Station

No number Memorandum of Understanding between the United States National Aeronautics and Space Administration and the Ministry of State for Science and Technology of Canada on Cooperation in the Detailed Design, Development, Operations, and Utilization of the Permanently Manned Civilian Space Station

No number Memorandum of Understanding between the United States National Aeronautics and Space Administration and the Russian Space Agency on Cooperation in the Detailed Design, Development, Operations, and Utilization of the Permanently Manned Civilian Space Station

No number Memorandum of Understanding between the United States National Aeronautics and Space Administration and the ASI on Cooperation in the Detailed Design, Development, Operations, and Utilization of the Permanently Manned Civilian Space Station

2.3 SOURCE DOCUMENTS

The following documents were used in the development of this document.

SSP 50011 Concept of Operation and Utilization

SSP 50019 NASA/ESA Joint Management Plan

2-4

SSP 50022 NASA/CSA Joint Management Plan

SSP 50030 NASA/NASDA Joint Management Plan

SSP 50076 NASA/ASI Joint Management Plan

SSP 50107 NASA/RSA Joint Management Protocol

K-CM-05.3.2 Guide to Space Station Processing at KSC

2.4 SPIP DOCUMENTATION TREE

Figure 2.4-1, SPIP Documentation Tree, illustrates the relationship between this document and the parent ISSP office documents.

FIGURE 2.4-1 SPIP DOCUMENTATION TREE

3-1

3.0 OVERVIEW OF SUSTAINING ENGINEERING

The ISS Program Sustaining Engineering Office has the overall responsibility for Sustaining Engineering of the ISS. Although the overall Sustaining Engineering integration responsibility belongs to NASA, each IP/P is responsible for providing Sustaining Engineering for their on-orbit and ground segments of the ISS.

NASA’s responsibility includes planning, scheduling, allocating the technical and administrative resources necessary, and most importantly, working together with all of the IP/Ps to ensure that all are working jointly towards a common goal.

Sustaining Engineering is the essential engineering support that, after the development of the flight hardware and software is completed and the flight hardware/software is turned over to the launch vehicle integrator, is required to maintain the integrity of the design and/or ensure operability of the ISS hardware and software. This typically occurs at the start of launch vehicle Integration.

Specific implementation details for interactions between each IP/P and NASA ISS Sustaining Engineering will be documented in an appendix to this document.

3.1 OVERVIEW OF SUSTAINING ENGINEERING TASKS

As defined in the COU, Sustaining Engineering includes the following functions:

A. Station performance, trend and anomaly analysis;

B. Maintenance of station analytical models;

C. Development of hardware and software modifications;

D. Configuration management of flight hardware and software.

Each of the IPs, including NASA, performs all or part of these tasks.

Whereas NASA and CSA define the support provided by the element engineering team to the launch vehicle integrator as sustaining engineering, ESA, NASDA, and RSA have categorized this support as: a) an element development team responsibility for the launch processing of their respective elements, and b) a ground processing function for launch of subsequent ESA, NASDA, and RSA cargo. In any case, Sustaining Engineering support to launch vehicle integration/deintegration encompasses the same basic activities and disciplines as Sustaining Engineering support to on-orbit operations.

The remainder of Section 3 defines the tasks associated with Sustaining Engineering. Section 4 focuses on IP roles, responsibilities, and the support needed for the defined tasks.

Section 5 references the appendices used as “Bilateral” documents. Each IP has an appendix (if necessary) that reiterates the task and defines the implementation strategy for each of the IPs.

3-2

Appendix E addresses RSA, Appendix F addresses CSA, Appendix G addresses ASI, Appendix H addresses NASDA, and Appendix I addresses ESA. SSP 50234, Sustaining Engineering Implementation Plan, documents the internal NASA process for implementing the above tasks.

3.2 SUSTAINING ENGINEERING SUPPORT TO LAUNCH VEHICLE INTEGRATION

AND DEINTEGRATION

Engineering support to launch vehicle Integration and Deintegration is that design engineering expertise needed to support the flight hardware and software while it’s being processed during this time frame. In the case of Shuttle Integration for John F. Kennedy Space Center (KSC) launches, engineering support usually begins at Launch minus a 6-8 week period, and ends when the Shuttle is launched. Shuttle Deintegration begins when the Orbiter returns to the landing site. Depending on the landing site and the mission-unique tasks, the Shuttle Deintegration time period varies.

The launch vehicle integrator is responsible for leading the launch vehicle Integration and Deintegration activities while the ISS IP/Ps are responsible for providing engineering support. The engineering support sub-tasks are discussed in the following paragraphs.

Each IP/P will provide design engineering support for their flight hardware and software during the launch vehicle integration and in the case of the Shuttle, Deintegration timeframe. This support includes, but is not limited to:

A. Providing design engineering expertise for monitoring the hardware and advising the launch processing team during launch site handling, transportation, testing, and servicing operations, including both nominal and contingency operations.

B. Maintaining the hardware and software configuration.

C. Supporting specific tasks related to the final preparation of space station elements for launch (e.g., the NASA/KSC installation and ground survey of Space Vision System (SVS) targets onto the IP/P elements).

D. Performing flight hardware closeouts, servicing the flight hardware (if required), and dispositioning any hardware that returns from orbit.

E. The IP/Ps will provide anomaly resolution for their hardware/software.

Engineering support for anomaly resolution is that design expertise needed to resolve any mechanical, electrical, or avionics/software problem.

F. The IP/P will provide engineering support needed in reviewing plans, processes, procedures, deviations/waivers, schedules, etc.

3-3

For additional details associated with Launch Site Processing, refer to SSP 50200-06, Station Program Implementation Plan, Volume 6: Cargo Physical Processing.

3.3 SUSTAINING ENGINEERING FOR ON-ORBIT OPERATIONS

Each IP/P is responsible for providing Sustaining Engineering for on-orbit operations for its specific element.

On-orbit Sustaining Engineering can be divided into two categories:

A. Real-time engineering support.

B. Off-line engineering support.

For the purpose of this document, off-line engineering support for on-orbit operations is defined as that engineering expertise/support relating to, but outside, real-time Mission Operations Integration Room (MOIR) and IP/P-equivalent facility activities/operations. Each IP/P is responsible for providing the required off-line engineering support for on-orbit operations.

An overview of on-orbit Sustaining Engineering support is provided in the following paragraphs.

3.3.1 REAL-TIME ENGINEERING SUPPORT

Real-time engineering support is defined as real-time support to the assembly and initial on-orbit activation and checkout of flight hardware and software, and to the subsequent on-orbit operations throughout the Operational Phase. This support is provided by teams on-site at Lyndon B. Johnson Space Center (JSC) and at IP control centers, and off-site at development contractor and IP/Plocations. The on-site teams will be composed of representatives from NASA, Government Furnished Equipment (GFE), payload, IP, Participant, and Prime personnel. The support will focus on investigation, isolation, and resolution of anomalies encountered during the assembly and on-orbit activation and checkout of each stage of the ISS. IP/P representation will be at JSC for the first launch and activation of their element during the Assembly Phase.

The MOIR provides the engineering interface to the Space Station Flight Control Team (FCT). It is the MOIR’s responsibility to facilitate and coordinate the engineering support to systems/elements hardware and software design modifications, and to provide an integrated (United States (U.S.) and IP/P) engineering response to the FCT.

ESA and NASDA will have at their respective control centers equivalent engineering support rooms to the MOIR from which their respective real-time engineering support teams provide support to the ESA and NASDA FCTs.

3-4

The MOIR maintains the ISS Systems Anomaly Log for the U.S. and IP/P elements. This log is the official list for systems problems that develop in-flight during an increment or that exist prior to launch. The MOIR updates and maintains the log and distributes the log to other program personnel. As anomalies occur, the U.S. FCT prepare anomaly reports and submits them to the MOIR for inclusion in the anomaly log which is continually updated. IP/Ps are also required to submit anomaly reports to the MOIR when failures in their systems/elements affect other elements or the station as a whole. It is possible that anomalies may remain open across increments. The MOIR is responsible for the closure of these anomaly reports, with integrated IP/P inputs as appropriate. The Systems Anomaly Log is included as part of the input to Increment Operations Review and is distributed to the preincrement tactical planning personnel for their planning processes.

RSA, ESA, and NASDA maintain System Anomaly Logs for their respective elements at their element control centers. Anomalies that have multi-segment impacts will also be reported to MOIR and will appear in the ISS Systems Anomaly Log

As the primary engineering support facility during real-time operations, the MOIR will be staffed by representatives from NASA and the IP/Ps, as required and as agreed.

The manning requirements will be negotiated per increment, flight, or major phase of operations, and is dependent on the level of engineering support needed.

3.3.2 OFF-LINE ENGINEERING SUPPORT

Off-line engineering support is provided at the various IP/P locations to perform the following activities during assembly and throughout the operational phase of the program.

3.3.2.1 PERFORMANCE ASSESSMENTS

Performance assessments are used to characterize anomalies, assess prospective corrective actions, compare predictions, identify trends, determine readiness to accept next assembly stage, update models, and determine actual operational performance. Performance assessments of each ISS subsystem are performed on a regularly scheduled basis. IP/Ps will be responsible for conducting performance assessments on their elements.

3.3.2.2 ANOMALY RESOLUTION

Anomaly resolution is the identification, investigation, and resolution of anomalies. Specifically, these investigations include the characterization of the problem or deficiency, determination of the probable cause or missing

3-5 functionality, evaluation against existing ISS Program requirements, and a recommendation of prospective corrective actions or enhancements. Anomalies that impact multiple IP/Ps will be coordinated and integrated during the anomaly resolution processes. IP/Ps will be responsible for conducting anomaly resolution on their elements. Initially, anomaly resolution will be addressed and in many cases recommended solutions will be developed by the real-time engineering support. However, for more complex anomalies, the off-line support will be tasked to determine the cause and recommend corrective action.

3.3.2.3 FACILITIES, MODELS, AND ANALYTICAL TOOLS

System analytical models generated during the developmental phase of the program elements are delivered to and maintained by Sustaining Engineering for use during the assembly and operations phases to support system performance analysis, operations, and training. The models include both hardware and software models of varying levels of fidelity. Sustaining Engineering updates the models to accurately maintain the on-orbit configuration. Updates may be required based on correlation of the models with actual system performance over time, identification of new training requirements, or modifications to system hardware and software.

Facilities, as used during the development program, are required for developing, validating, or verifying hardware and software modifications. These facilities must be maintained.

Analytical Tools are defined as the operating systems upon which the analyses are conducted. Maintenance of these tools is performed by the IP/P off-line engineering support.

3.3.2.4 HARDWARE MODIFICATIONS

Hardware modifications are changes to hardware design or to the on-orbit configuration that may be required to resolve an anomaly or to enhance the performance. Each IP/P is responsible for providing hardware modifications for its specific hardware and software.

When hardware modifications are required, detailed requirements for the modification are developed. Any modification must be assessed to ensure the modification design is compatible with the Station configuration and meets the actual requirements.

Hardware modifications are verified in accordance with the IP/Ps standard design process. Hardware modifications are integrated across all the affected IP/Ps.

This also involves providing input to the operations planning process regarding impacts of the hardware modification on procedures and operations products (displays, databases, handbooks, and crew procedures), and providing drawing and configuration management changes.

3-6

Each IP/P maintains a hardware facility, as required, to test, checkout, and verify hardware changes, modifications, and enhancements prior to incorporation and integration with the ISS. The IP/P hardware facility is certified per internal IP/P requirements and in accordance with overall Program requirements. These facilities are assumed to be existing facilities that were utilized during the development of the IP/P hardware.

3.3.2.5 SOFTWARE MODIFICATIONS

Software modifications are those modifications that are created to fix a certain anomaly, provide a performance enhancement, or are a total rewrite of the previous software version. Detailed requirement development, verification, integration, and configuration management are required in support of software modifications, along with the usage of appropriate software facilities.

Systems performance analysis may indicate the need for modification to flight software. Sustaining Engineering will define detailed requirements for software modifications; generate, test, and verify the modifications; and, provide them for uplink to the on-orbit Station. Each IP/P is responsible for providing modifications for their specific software. Details of the software modification process are defined in SSP 50482, ISSP Software Management Plan.

3.3.2.6 SAFETY

Each IP/P is accountable to both the ISS Program and internal processes, procedures, and guidelines which define safety requirements and compliances.

All hardware and software related activities, modifications, and enhancements are in accordance with the normal safety process as stated in SSP 30599, Safety Review Process, and SSP 50021, Safety Requirements Document, for NASA or the IP/P bilateral Safety and

Mission Assurance (S&MA) agreements or the IP/P bilateral Safety and Product Assurance (S&PA) requirements, as appropriate, for IP/Ps. IPs/P support all safety related activities and reviews associated with hardware or software modifications of their respective element.

3.3.2.7 CONFIGURATION MANAGEMENT

Each IP/P has the responsibility for maintaining configuration control for all hardware and software modifications associated with its element. Such configuration control is governed by the appropriate procedures and authorizing guidelines as defined in SSP 41170, Configuration Management Requirements, SSP 50123, Configuration Management Handbook, and those documents internal to the IP/Ps.

4-1

4.0 INTERNATIONAL PARTNER AND PARTICIPANT SUSTAINING ENGINEERING

TASKS

Table 4.0-1, summarizes Sustaining Engineering tasks performed by the IP/Ps.

TABLE 4.0-1 INTERNATIONAL PARTNER AND PARTICIPANT SUSTAINING

ENGINEERING TASKS

SUSTAINING ENGINEERING TASKS RSA CSA ESA NASDA ASI NASA

Engineering Support to Launch Vehicle Integration

Maintain hardware and software configuration of equipment at launch site

Y Y Y Y Y Y

Support of launch vehicle Integration Y Y Y Y Y Y Support of launch site Contingency Operations Y Y Y Y Y Y Support of launch site problem resolution Y Y Y Y Y Y Support of launch site plans and procedures development

Y Y Y Y Y Y

Support of launch vehicle Deintegration Y Y Y Y Y Y On-Orbit Operations

Conduct performance assessments Y Y Y Y Y Y Perform anomaly resolution Y Y Y Y Y Y Maintain facilities, models and analytical tools Y Y Y Y Y Y Perform hardware modifications Y Y Y Y Y Y Perform software modifications and verification Y Y Y Y Y Y Conduct safety processes Y Y Y Y Y Y Perform configuration management of hardware and software

Y Y Y Y Y Y

Provide personnel at MOIR as required and as agreed

Y Y Y Y Y Y

Provide software modifications to the SVF and support integrated testing of software load per

SSP 50482

Y Y Y Y Y Y

5-1

5.0 INTERNATIONAL PARTNER AND PARTICIPANT BILATERALS

The individual IP/P interactions with NASA ISS Sustaining Engineering on implementation will be documented in related Appendices to this document.

A-1

APPENDIX A

ACRONYMS AND ABBREVIATIONS DCN 004

A-2

APPENDIX A - ACRONYMS AND ABBREVIATIONS

ASI Agenzia Spaziale Italiana

COU Concept of Operations and Utilization CSA Canadian Space Agency e.g. for example ESA European Space Agency

FCT Flight Control Team

GFE Government Furnished Equipment i.e. that is IGA Inter-Governmental Agreement IP International Partner IP/P International Partner/Participant ISS International Space Station ISSP International Space Station Program

JMP Joint Management Plan JSC Lyndon B. Johnson Space Center

KSC John F. Kennedy Space Center

MOIR Mission Operations Integration Room MOU Memorandum of Understanding

NASA National Aeronautics and Space Administration NASDA National Space Development Agency of Japan

OMP Operations Management Plan

RSA Russian Space Agency

S&MA Safety and Mission Assurance S&PA Safety and Product Assurance SPIP Station Program Implementation Plan SSCB Space Station Control Board SSP Space Station Program SVF Software Verification Facility SVS Space Vision System

TBD To Be Determined TBR To Be Resolved

U.S. United States UMP Utilization Management Plan

B-1

APPENDIX B

GLOSSARY OF TERMS <RESERVED>

B-2

APPENDIX B - GLOSSARY OF TERMS <RESERVED>

C-1

APPENDIX C

MATRIX OF ISSUES TO BE RESOLVED

C-2

APPENDIX C – MATRIX OF ISSUES TO BE RESOLVED

C.1 PURPOSE

Appendix C contains a matrix listing unresolved issues with the document. Each issue is given a TBR number, using the section of the document that contains the issue as the first digit, and a consecutive number for the second digit (i.e., TBR Number 4-1 is the first issue in Section 4 of the document). The issue will be identified in detail. Affected sections will be identified by section number and paragraph (i.e., 5.6.1 (1st paragraph) or 5.3.2 (all).

TBRs will be identified in the document by placing a bold-typed TBR number in brackets immediately after that text. (i.e., <TBR 2-1>).

TABLE C.1-1 MATRIX OF ISSUES TO BE RESOLVED

TBR Number Issue Affected Sections TBR 3-1 Resolved. DCN 006

D-1

APPENDIX D

MATRIX OF TO BE DETERMINED ITEMS

SSP 50200-10 17 April 2003

D-2

APPENDIX D – MATRIX OF TO BE DETERMINED ITEMS

D.1 PURPOSE

Appendix D contains a matrix listing the specific items in the document that are not yet known. Each item is given a TBD number, using the section of the document that contains the item as the first digit, and a consecutive number for the second digit (i.e., TBD 3-1 is in Section 3, and is the first occurrence of this specific item in the document). The item is identified in detail, including the affected section, as well as a description of the TBD item. Each specific TBD item is listed once, with all of its associated affected section numbers. As each TBD item is resolved, the correct text is inserted in place of the “TBD” in the document, and the entry is removed from this matrix.

TABLE D.1-1 MATRIX OF TO BE DETERMINED ITEMS

TBD Number Description Affected Section 2-1 Document numbers 2.0 G-1 Closed.

G-2 SSP 50125 has not been published. Appendix G, Section G.3.6.2 DCN 007

E-1

APPENDIX E

NASA RSA BILATERAL

E-2

APPENDIX E - NASA RSA BILATERAL

E.1 PROCESS REFERENCES

Responsibility for control of the Appendix E changes is delegated to the book manager.

This appendix will be revised as required and changes will be issued as replacement pages or by complete revision of the appendix as appropriate. All requested changes will be directed to the book manager.

F-1

APPENDIX F

NASA CSA BILATERAL

F-2

APPENDIX F - NASA CSA BILATERAL

F.1 PROCESS REFERENCES

Responsibility for control of the Appendix F changes is delegated to the book manager.

This appendix will be revised as required, and changes will be issued as replacement pages or by complete revision of the appendix as appropriate. All requested changes will be directed to the book manager.

Canadian Space Agency Space Station Program

CSA/NASA Bilateral Sustaining Engineering Plan

Initial Release

November 1998

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

DCN 003

REVISION AND HISTORY PAGE

REV. DESCRIPTION PUB.

DATE

-- Initial Release (Reference per SSCD 002700, EFF. 08-21-00) XX-XX-XX

F-i

INTERNATIONAL SPACE STATION PROGRAM

CSA/NASA BILATERAL

SUSTAINING ENGINEERING PLAN

NOVEMBER 1998

SSP 50200-10 13 August 1999

F-ii

PREFACE

CSA/NASA BILATERAL

SUSTAINING ENGINEERING PLAN

Baselining and subsequent changes to this document must be authorized by the signature of the Mobile Servicing System (MSS) Canadian Space Agency (CSA) and National Aeronautics and Space Administration (NASA) Sustaining Engineering Managers. Disagreements which could occur during the implementation of this plan will be referred to the MSS Integration Panel for resolution.

F-iii

TABLE OF CONTENTS

PARAGRAPH PAGE

F.1.0 ...........................................................................................................................................................................INTROD UCTION .................................................................................................................................................................... F.1-

F.1.1 ...........................................................................................................................................................................PURPO SE ............................................................................................................................................................................. F.1-

F.1.2 ...................................................................................................................................................................SCOPE ...........................................................................................................................................................................F.1-1

F.1.3 ...........................................................................................................................................................................BACKG ROUND ..................................................................................................................................................................... F.1-

F.1.4 ...........................................................................................................................................................................PRECE DENCE ..................................................................................................................................................................... F.1-

F.2.0 ...........................................................................................................................................................................DOCUM ENTS ........................................................................................................................................................................ F.2-

F.2.1 ...........................................................................................................................................................................APPLIC ABLE DOCUMENTS ................................................................................................................................................. F.2-

F.2.2 ...........................................................................................................................................................................REFER ENCE DOCUMENTS ................................................................................................................................................ F.2-

F.3.0 ...........................................................................................................................................................................SUSTAI NING ENGINEERING ............................................................................................................................................... F.3-

F.3.1 ...........................................................................................................................................................................SUSTAI NING ENGINEERING OVERVIEW ........................................................................................................................... F.3-

F.3.2 ...................................................................................................................................................................MODES OF OPERATION ....................................................................................................................................................... F.3-

F.3.3 ...........................................................................................................................................................................FACILIT IES ............................................................................................................................................................................ F.3-

F-iv

F.3.3.1 ...........................................................................................................................................................................ENGINE ERING SUPPORT CENTER ..................................................................................................................................... F.3-

F.3.3.2 ................................................................................................................................................................MSS SUSTAINING ENGINEERING FACILITY ................................................................................................................. F.3-

F.3.3.2.1 ...........................................................................................................................................................................MANIPU LATOR DEVELOPMENT AND SIMULATION FACILITY .......................................................................................... F.3-

F.3.3.2.2 .............................................................................................................................................................MSS AVIONICS INTEGRATION FACILITY ....................................................................................................................... F.3-

F.3.3.2.3 ...........................................................................................................................................................................CANADI AN SOFTWARE SUPPORT EQUIPMENT ............................................................................................................... F.3-

F.3.3.2.4 ...........................................................................................................................................................................SPECIA L TEST EQUIPMENT ................................................................................................................................................ F.3-

F.3.4 ...........................................................................................................................................................................RESOU RCES ........................................................................................................................................................................ F.3-

F.3.5 ...........................................................................................................................................................................SCHED ULE ........................................................................................................................................................................... F.3-

F.3.6 ...........................................................................................................................................................................GROUN DRULES AND ASSUMPTIONS ................................................................................................................................ F.3-

F.4.0 ...........................................................................................................................................................................SUSTAI NING ENGINEERING RESPONSIBILITIES ............................................................................................................. F.4-

F.4.1 ...........................................................................................................................................................................FACILIT Y DEVELOPMENT .................................................................................................................................................... F.4-

F.4.1.1 ...........................................................................................................................................................................PERFO RMANCE ANALYTICAL TOOLS............................................................................................................................... F.4-

F.4.1.2 ................................................................................................................................................................MSS SYSTEM HANDBOOK .............................................................................................................................................. F.4-

F-v

F.4.1.3 ................................................................................................................................................................ESC CONSOLES .............................................................................................................................................................. F.4-

F.4.2 ...........................................................................................................................................................................INCREM ENT PLANNING ........................................................................................................................................................ F.4-

F.4.2.1 ...........................................................................................................................................................................OPERA TIONS PROCEDURES ............................................................................................................................................. F.4-

F.4.2.2 ...........................................................................................................................................................................MISCEL LANEOUS PLANNING PRODUCTS ......................................................................................................................... F.4-

F.4.3 ...................................................................................................................................................................MSS PERFORMANCE ANALYSIS .................................................................................................................................... F.4-

F.4.3.1 ................................................................................................................................................................REAL- TIME SUPPORT ....................................................................................................................................................... F.4-

F.4.3.1.1 ...........................................................................................................................................................................SUPPO RT AT THE MSEF ..................................................................................................................................................... F.4-

F.4.3.2 ..........................................................................................................................