The file's text, extracted by GovTribe without its formatting.
NASA/RSA Bilateral Data Exchange Agreement, List, and Schedule
International Space Station Program
Revision A
April 2015
National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract No.: NNJ12GA46C
SSP 50137
Rev A
1-1
REVISION AND HISTORY PAGE
| REV. |
| DESCRIPTION |
| PUB. DATE |
| - |
| Initial Release (Reference per SSCD 000603, EFF. 30-12-97) |
| 02-20-98 |
| A |
| Revision A (Reference per SSCD 15053, EFF. 04-28-15) |
| 09-04-15 |
PREFACE
NASA/RSA Bilateral Data Exchange Agreement, List, and Schedule The Bilateral Data Exchange Agreement, List and Schedules (BDEALS) defines the data that will be exchanged between the National Aeronautics and Space Administration and Russian Space Agency. This Revision A is administrative to add in the already approved Data Item Descriptions (DIDs).
INTERNATIONAL SPACE STATION PROGRAM
NASA/RSA Bilateral Data Exchange Agreement, List, and Schedule
CONCURRENCE
April 2015
INTERNATIONAL SPACE STATION PROGRAM
NASA/RSA Bilateral Data Exchange Agreement, List, and Schedule
CONCURRENCE
april 2015 iii
INTERNATIONAL SPACE STATION PROGRAM
NASA/RSA Bilateral Data Exchange Agreement, List, and Schedule
LIST OF CHANGES
April 2015 All changes to paragraphs, tables, and figures in this document are shown below:
Board Name
Entry Date
Change
Paragraph(s)
November 1996
Baseline
All
April 2015
Rev A
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 | Document Control | 1-2 |
| 1.5 | confidentiality | 1-2 |
| 2.0 | documents | 2-1 |
| 2.1 | applicable documents | 2-1 |
| 2.2 | reference documents | 2-1 |
| 3.0 | IDENTIFICATION OF DATA TO BE EXCHANGED | 3-1 |
| 3.1 | Format Of Documents To Be Exchanged | 3-1 |
| 3.2 | data exchange list development Process | 3-1 |
| 3.3 | Language | 3-2 |
| 4.0 | RESPONSIBILITIES OF THE PROVIDING/RECEIVING ORGANIZATIONS | 4-1 |
| 4.1 | Definitions | 4-1 |
| 4.2 | Responsibilities Of The Providing Organization | 4-1 |
| 4.3 | Responsibilities Of The Receiving Organization | 4-1 |
| 4.4 | Shared Responsibilities | 4-2 |
| 5.0 | REQUIREMENTS, RIGHTS, AND RESPONSIBILITIES FOR USE OF THESE DATA | 5-1 |
| 5.1 | Confidentiality | 5-1 |
| 5.2 | Protection Of Confidential Information | 5-1 |
| 5.3 | Verbal Presentation Of Confidential Information | 5-1 |
| 5.4 | Duration Of Confidentiality Agreements | 5-2 |
| 6.0 | MANAGEMENT PROCESS | 6-1 |
| 6.1 | Data Item Description (DID) | 6-1 |
| 6.2 | data exchange list | 6-1 |
| 6.3 | RSA Integrator | 6-2 |
| 6.4 | Evaluation Process | 6-2 |
| 7.0 | SUPPLEMENTAL AGREEMENTS | 7-1 |
APPENDIX
| a | Acronyms and abbreviations | a-1 |
| b | glossary of terms | b-1 |
| c | open work | c-1 |
| d | data item descriptions (DID) | d-1 |
TABLE
| C-1 | to be determined items | | c-1 |
| C-2 | TO BE RESOLVED ISSUES | | c-1 |
| D-1 | SSP 50137 Approved Notification of Document Changes | | |
| November 1, 1996 | | d-3 | |
| d-2 | SSP 50137 APPROVED DATA ITEM DESCRIPTIONs (DID) 1996-Present | | d-11 |
| d-3 | mrm1 cargo bag hardware | | d-27 |
| D-4 | R4G-01 MRM1 (DCM) (page 1 of 2) | | d-43 |
| D-5 | R4G-02 MRM1 (DCM) | | d-49 |
| D-6 | R4G-02 MRM1 (DCM) | | d-49 |
| D-7 | MRM1 (DCM) Preliminary Design (Eskizniy Proekt) Part II | | d-50 |
| D-8 | mrm1 vents contamination did schedule | | d-137 |
| d-9 | schedules for mrm1 optically sensitive surfaces | | d-139 |
| D-10 | mrm2 vents contamination did schedule | | d-143 |
| d-11 | schedule for mrm2 optically sensitive surfaces | | d-146 |
FIGURE
| D-1 | DID # R4G-04: MRM1 Detailed Design Data | d-57 |
| D-2 | ndc 50137-202 | d-88 |
| D-3 | NDC SSP 50137-203 | d-94 |
| D-4 | mrm1 external contamination did schedule | d-135 |
| D-5 | Preliminary data – DC-1 data/final: L-6 months | d-141 |
INTRODUCTION
This bilateral agreement documents decisions between the National Aeronautics and Space Administration (NASA) and Russian Space Agency (RSA) regarding data to be exchanged between the NASA and RSA in carrying out their respective roles in the International Space Station (ISS). It includes design, performance, and planning information to be used by the partners for integration of the Russian Segment into the International Space Station. This document shall be consistent with the NASA/RSA Memorandum of Understanding (MOU). The MOU shall take precedence over this document and any changes to the MOU shall be reflected in subsequent revisions of this document.
The Joint Management Plan adopted by the NASA and the RSA identified this document as one of a series of bilateral agreements to be accomplished in implementation of the joint United States (U.S.)/Russian development of the International Space Station. This document represents the single authoritative agreement between NASA and RSA on data exchanges in support of the International Space Station Program.
purpose The objectives of this agreement are as follows:
| A. | To identify the data to be formally exchanged between RSA and NASA, including their respective contractors, in development and integration of the ISS. |
| B. | To identify the organization responsible for providing these data. |
| C. | To define the requirements, rights, and responsibilities for the use of these data by both parties. |
| D. | To define the management process for originating, maintaining and tracking this information exchange activity. |
scope This agreement defines data exchanges between the U.S. and the Russian parties, conducted in compliance with the respective responsibilities of the parties, who act as International Partners within the ISS Program. NASA and RSA are responsible for making contracts, and for financing all their contractors’ operations to be performed in order to implement the terms of this agreement.
Additional data exchanges authorized under the Krunichev contract or NAS15-10110 are not subject to this agreement.
Precedence This agreement is subordinate to the IGA, the NASA/RSA MOU and the NASA/RSA JMP. In the event of conflict between this document and any other Bilateral Plan or Bilateral Requirements document, the Bilateral Plan or Requirements document shall take precedence until a mutually agreed resolution can be reached.
Document Control All changes to this document require the approval of the NASA Space Station Program Manager and the RSA Deputy General Director.
confidentiality It is understood, that in the coused of ISS Program implementation process, the exchange of confidential information and data which are the property of RSA or NASA or their contractors, may become necessary.
The parties agreed to the following method and procedures with regard to ensuring confidentiality for the information and data being exchanged.
| A. | The information and data provided in accordance with this agreement are intended for the use exclusively within the ISS Program implementation activities. Consequently, only the personnel of the receiving party directly dealing with the ISS Program activities may have access to such information and data, as well as their publication or dissemination through the media, or in dedicated scientific publications, will require prior written approval by the providing party. |
| B. | The party providing confidential information and data which is the party’s property, will attach the appropriate notification on the use rights restrictions. |
The party receiving such information and data is obligated to use them strictly in compliance with the requirements indicated in the notification on the use rights restrictions, as well as to take the appropriate measures ensuring confidentiality, which includes the appropriate instructing of the user personnel, who has access to such information and data.
| C. | In cases when a deliverable accompanied by the notification on the use rights restrictions will be handed over to contractors or third parties, the requirements indicated in paragraph A and B above shall be applicable to such contractors or thier parties, which shall be documented in writing in the respective agreements or included in the terms of the respective contract. |
| D. | Providing of information and data is not, and may not be interpreted, as ownership rights transfer, or as yielding or copy rights, or as granting of license to use. |
| E. | It is understood, that in the course of on-going ISS Program implementation process, and during presentations, technical discussions, and meetings in particular, an exchange of confidential information may take place in the oral form. In such a case, the party providing confidential information may designate it as such by making a written notification within 15 calendar days after the presentation, and, subsequently, the other party will be obligated to handle such information as confidential complying with all the requirements indicated above in paragraphs A through D. |
| F. | Requirements and conditions of section 1.5 will remain in force until both parties who signed this agreement agree otherwise. |
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.
| SSP 42121 |
| U.S. On-Orbit Segment Pressurized Mating Adapter-1 to Russian Segment FGB Interface Control Document Part 1 |
| SSP 50094 |
| NASA/RSA Joint Specifications Standards Document for the ISS Russian Segment |
| SSP 50107 |
| NASA/RSA Joint Management Plan |
| SSP 50123 |
| Configuration Management Handbook |
| SSP 50227 |
| Russian Segment (SPP, SM and FGB) to PDGF/SSRMS Interface Control Document |
reference documents N/A
3-2
IDENTIFICATION OF DATA TO BE EXCHANGED
Documentation exchanged under this agreement will be of two types:
Type 1 - Standard design documentation - This is documentation or data derived during the normal course of business in developing, designing, manufacturing, and certification (such as technical requirements, specifications, plans, drawings, and layouts) of space hardware. Exchange of these data will permit either side to perform their required overall ISS integration and verification analyses.
Type 2 - Unique documentation - This is documentation or data which is needed by one side, but is not normally generated by the other side. There will be situations where newly developed documentation will need to be generated by either side in order to satisfy the requirements of the other.
It is understood that Type 2 documentation generating and hand-over procedures will be defined in additional agreements between the sides; these agreements will, among other things, define the scope and content of the documentation. It is understood by both sides that neither side is obligated to agree to provide such unique documentation.
Additional data exchanges authorized under the Krunichev contract or NAS15-10110 are not subject to this agreement.
Format Of Documents To Be Exchanged Data exchange will be conducted by means of hardcopy submittals or electronic files transfer (File Transfer Procedure [FTP] or E-mail). Certain data can only be transferred in electronic format; technical teams will identify and define such data. The technical teams will jointly develop and document these data exchanges.
The parties have agreed upon the following file formats to be used for electronic data exchange:
| A. | TEXT -ASCII (standard), Word 6.0 (English or True Type Cyrillic Fonts);Portable Document Format (PDF) |
| B. | TABLES - Excel 5.0; |
| C. | GRAPHICS - Raster; |
| D. | GRAPHICS - AutoCAD 12, IGES 5.1. |
Where it is not feasible to provide electronic data in the above formats, the electronic data may be submitted in the native RSA/NASA electronic formats and will be agreed to on a case-by-case basis.
data exchange list development Process Development of the date exchange list (Table D-2) shall be in accordance with the following procedure:
| A. | Data exchange agreements reached between technical team will be documented in team protocols. Emphasis will be placed on defining the data exchanges in the terminology and numbering system of the providing organization |
| 1. | For example, agreements for Russian standard design documentation (data type 1) should use Russian nomenclature and reference the Russian document number. |
| 2. | Protocol agreements for unique documentation (data type 2) should include a data item description, which describes in sufficient detail the content of the data exchange. These agreements should also contain sufficient justification to warrant the impacts associated with generating additional (new) documentation. |
| 3. | This information will be documented in Appendix D-Data Item Descriptions (DID). |
| B. | Team protocols will be submitted to the management team for approval. When approved, the agreements will be incorporated in the draft Table D-2 “Bilateral Data Exchange List”. Draft of the changed Table D-2 will be submitted for approval to the management of the organization provider and organization receiver. |
| C. | This Table D-2 and any changes to it will be submitted to the NASA Space Station Program Manager and the RSA Deputy General Director for approval. |
Language Unless otherwise specified, all data exchanges defined under this agreement will be submitted in the native language of the providing organization. When translated documents are exchanged, a copy of the document in the native language will also be exchanged as a reference for translation questions.
RESPONSIBILITIES OF THE PROVIDING/RECEIVING ORGANIZATIONS
Data exchanged under this agreement will be formally exchanged between RSA and NASA, including their respective contractors, in development and integration of the ISS. NASA and RSA are responsible for making the necessary contracts, and for financing all their contractors’ operations to be performed in order to implement the terms of this agreement.
Definitions The Providing Organization is the organization that provides information and data in compliance with this agreement. Such organizations can be both RSA and NASA, and RSA contractors and NASA contractors.
The Receiving Organization is the organization that receives information and data in compliance with this agreement. Such organizations can be both RSA and NASA, and RSA contractors and NASA contractors.
Responsibilities Of The Providing Organization The following is a summary of the responsibilities of the Providing Organization under this agreement:
| A. | Coordination with the Receiving Organization to define and document any supplemental agreements needed to accomplish the efficient data exchange. |
| B. | Delivery of data in accordance with the agreed-to schedule and list. |
| C. | Delivery of data in the native language, unless otherwise agreed to and documented in the data exchange list. |
| D. | Technical support of the exchanged data including participation in meetings, telecons, etc. required for the Receiving Organization to properly use the information. |
| E. | Support to the Receiving Organization in the resolution of any discrepancies, omissions, etc. in the data delivery (within the scope of the agreed to data exchange list). |
| F. | Timely delivery of updates of the exchanged data to the Receiving Organization if the Providing Organization judges the change is pertinent to the receiving organization. |
Responsibilities Of The Receiving Organization The following is a summary of the responsibilities of the Receiving Organization under this agreement:
| A. | Coordination with the Providing Organization to define and document any supplemental agreements needed to accomplish the exchange efficiently. |
| B. | Arranging for timely review of delivered items and timely resolution with the Providing Organization of any discrepancies, omissions, etc. in the data. |
| C. | Use of the exchanged data in accordance with the agreements documented herein and agreements negotiated and documented in accordance with this document. |
Shared Responsibilities
In compliance with the aforementioned responsibilities outlined in Sections 3.2 and 3.3, RSA and NASA will each be responsible for issuing direction, negotiating agreements and providing funding as appropriate to their respective contractors or subordinate agencies necessary to meet the requirements of this agreement.
4-2
REQUIREMENTS, RIGHTS, AND RESPONSIBILITIES FOR USE OF THESE DATA
Confidentiality It is understood that in the course of the ISS Program implementation process it may become necessary to exchange confidential information and data that are the property of RSA, NASA, or their contractors. The following sections outline the procedures that shall be taken to protect the confidentiality of such information and data.
Protection Of Confidential Information The parties agreed to the following method and procedures with regard to ensuring confidentiality for the information and data being exchanged.
The information and data provided in accordance with this agreement are intended for the use exclusively within the ISS Program implementation activities. Consequently, only the personnel of the receiving party directly dealing with the ISS Program activities may have access to such information and data. Their publication or dissemination through the media, or in dedicated scientific publications, will require prior written approval by the providing party.
The party providing confidential information and data which is the party’s property, will attach the appropriate notification on the use rights restrictions.
The party receiving such information and data is obligated to use them strictly in compliance with the requirements indicated in the notification on the use rights restrictions, as well as to take the appropriate measures ensuring confidentiality, which includes the appropriate instructing of the user personnel, who has access to such information and data.
In cases when a deliverable accompanied by the notification on the use rights restrictions will be handed over to contractors or third parties, the requirements indicated above shall be applicable to such contractors or third parties, which shall be documented in writing in the respective agreements or included in the terms of the respective contract.
Providing of information and data is not, and may not be interpreted, as ownership rights transfer, or as yielding of copyrights, or as granting of license to use.
Verbal Presentation Of Confidential Information It is understood, that in the course of on-going ISS Program implementation process, and during presentations, technical discussions, and meetings in particular, an exchange of confidential information may take place in the oral form. In such a case, the party providing confidential information may designate it as such by making a written notification within 15 calendar days after the presentation, and, subsequently, the other party will be obligated to handle such information as confidential complying with all the requirements indicated above.
Duration Of Confidentiality Agreements The requirements and conditions of section 4 will remain in force until both parties who signed this agreement agree otherwise.
Upon request of the Providing Organization, the Receiving Organization will provide a written statement confirming its obligation to adhere to the requirements in section 4. This will be submitted in the form of an appropriate certificate.
5-2
MANAGEMENT PROCESS
Data Item Description (DID) Data exchange agreements reached between technical teams shall be documented on DID forms. When data exchange agreements are negotiated at Technical Interchange Meetings (TIM), the DIDs shall be included in the TIM protocols. The data exchanges will be defined in the terminology and numbering system of the providing organization. For example, agreements for Russian standard design documentation should use Russian nomenclature and reference the Russian document number whenever feasible.
Information provided in the DID shall include:
| A. | DID title and DID number, as assigned by the NASA Bilateral Data Exchange Agreements Lists and Schedules (BDEALS) Representative |
| B. | Description of data or task to be provided |
| C. | Schedule of deliveries |
| D. | Justification of the exchange |
| E. | Agreement |
In the Schedule section, efforts should be made to express the deliverable date in “L-“ format whenever feasible. Deliveries may be scheduled at a specific date, at a determined period prior to launch (“L- format”), or periodically throughout the life of the ISS.
Roscosmos delegates its contractors the authority to approve the DIDs in cases when the DIDs concern the exchanges between these contractors and NASA.
Agreement to the DID shall be indicated by the signatures of both the U.S. and Russian technical team lead engineers. Obtaining these signatures is the responsibility of the respective technical team lead. Approval of the DID shall be indicated by the signatures of U.S. and Russian Team 0 management and providing and receiving organization’s management. Obtaining these signatures is the responsibility of the NASA BDEALS Representative.
Agreements for unique documentation (data type 2) should contain sufficient justification to warrant the impacts associated with generating additional, new documentation.
data exchange list Table D-2 identifies agreed-to date exchanges, from 1996 to present. This DID listing will be provided to RSA annualy..
The column headings for Table D-2 are defined as follows:
| A. | DID Number – an identifier for a description of the document |
| B. | DID Title – a title or brief description of the deliverable |
| C. | Responsible Team – organization/team responsible for writing and receiving/send data per a particular DID |
| D. | Approved Date – Date when DID was signed and agreed upon |
RSA Integrator To assist the NASA BDEALS representative in the task of developing and maintaining the BDEALS, RSA will designate a single point of contact, known as the RSA Integrator, to represent RSA and all its contracting companies. These companies include Rocket Space Corporation- Energia (RSC-E), Krunichev, Gagarin Cosmonaut Training Center (GCTC), and any and all other aerospace contractor(s) working under contract to RSA. Upon request by the NASA BDEALS representative, the Integrator will contact the appropriate RSA contractor in order to provide signature status of DIDs, status of documentation requested in approved DIDs, and other information as requested.
Evaluation Process
Both sides will establish internal procedures for technical evaluation of the data provided under this agreement.
6-2
SUPPLEMENTAL AGREEMENTS
It is understood, that supplemental agreements can be made in the course of the on-going activities to simplify exchange procedures and to specify exchange and information and data use regulations described in this document. It is understood, that such agreements can be made both between RSA and NASA, and between RSA contractors and NASA contractors.
These supplemental agreements will be documented in appropriate protocols 7-1
Appendix a - Acronyms and abbreviations
| AR&D |
| Automated Rendezvous and Docking |
| ASTM |
| American Society for Testing and Materials |
| ATM |
| Acceleration Transformation Matrix |
| BDEALS |
| Bilateral Data Exchange Agreements Lists and Schedules |
| BHSEALS |
| Bilateral Hardware and Software Exchange Agreements, Lists and Schedules |
| BIVP |
| Bilateral Integration and Verification Plan |
| C&DH |
| Command and Data Handling |
| C&T |
| Communication and Tracking |
| CAD |
| Computer Aided Design |
| CDS |
| Common Depress Strategy |
| CMC |
| Cargo Mission Contract |
| CoFR |
| Commit to Flight Reviews |
| CSA |
| Canadian Space Agency |
| DAR |
| Design Analysis Report |
| DCLA |
| Design Couple Loads Analysis |
| DDR |
| Detailed Design Review |
| DFMR |
| Design for Minimum Risk |
| DID |
| Data Item Description |
| DTM |
| Displacement Transformation Matrix |
| ECL |
| Equipment Classification Lists |
| ECLSS |
| Environmental Control and Life Support System |
| EEE |
| Electrical, Electronic and Electromechanical |
| EMC |
| Electromagnetic Compatibility |
| EME |
| Electromagnetic Effects |
| EMI |
| Electromagnetic Interference |
| EPS |
| Electrical Power System |
| ESA |
| External Sampling Adapter |
| EVA |
| Extra Vehicular Activity |
| FAR |
| Final Acceptance Review |
| FGB |
| Functional Cargo Block |
| FMEA |
| Failure Modes and Effects Analysis |
| FMSR |
| Flight Mode Summary Report |
| FRGF |
| Flight Releasable Grapple Fixture |
| FTP |
| File Transfer Procedures |
| GCTC |
| Gagarin Cosmonaut Training Center |
| GN&C |
| Guidance, Navigation and Control |
| GSE |
| Ground Support Equipment |
| HRS |
| Heat Rejection System |
| IBMP |
| Institute for Biomedical Problems |
| ICP |
| Integrated Control Panel |
| IDD |
| Interface Definition Document |
| IDR |
| Integrated Design Reviews |
| IGES |
| Initial Graphic Exchange Specification |
| ISS |
| International Space Station |
| IT |
| Information Technology |
| IVA |
| Intravehicular Activity |
| IVVR |
| Interface Verification Visibility Report |
| KhSC |
| Khrunichev Space Center |
| LMMS |
| Lockheed Martin Mission Services |
| M&P |
| Materials and Processes |
| M/OD |
| Meteoroid/ Orbital Debris |
| MCS |
| Motion Control System |
| MDA |
| McDonnel Douglas Aerospace |
| MDM |
| Multiplexer/Demultiplexer |
| MIP |
| Mission Integration Plan |
| MIR |
| Mission Integration Review |
| MIUL |
| Material Identification Usage List |
| MLI |
| Multilayer Insulation |
| MLM |
| Multipurpose Lab Module |
| MOA |
| Memorandum of Agreement |
| MOD |
| Mission Operations Directorate |
| MOU |
| Memorandum of Understanding |
| MSS |
| Mobile Servicing System |
| NASA |
| National Aeronautics and Space Administration |
| NBL |
| Neutral Buoyancy Laboratory |
| NDC |
| Notice of Document Change |
| NDE |
| Nondestructive Evaluation |
| NSTS |
| National Space Transportation System |
| ODA |
| Orbiter Disconnect Assembly |
| ONS |
| Off Nominal Situations |
| PCDM |
| Probe Cone Docking Mechanism |
| PDF |
| Portable Document Format |
| PDGF |
| Power and Data Grapple Fixture |
| PDR |
| Preliminary Design Review |
| PHS&T |
| Packaging, Handling, Storage and Transportation |
| PMA |
| Pressurized Mating Adapter |
| PVGF |
| Power and Video Grapple Fixture |
| PWS |
| Portable Work Station |
| R&M |
| Reliability and Maintainability |
| RODF |
| Russian Operations Data File |
| ROEU |
| Remotely Operated Electrical Umbilical |
| RPC |
| Remote Power Controller |
| RSC-E |
| Rocket Space Corporation-Energia |
| RSS |
| Russian Segment Specialist |
| RST |
| Russian Segment Trainer |
| 6-DOF |
| Six-degrees-of-freedom |
| S&M |
| Structures and Mechanisms |
| S&MA |
| Safety and Mission Assurance |
| SARJ |
| Solar Alpha Rotary Joint |
| SES |
| Systems Engineering Simulator |
| SINDA |
| Simplified Improved Numerical Difference Analyzer |
| SPIP |
| Station Program Implementation Plan |
| SPP |
| Science Power Platform |
| SSCB |
| Space Station Control Board |
| SSP |
| Space Shuttle Program |
| SSTF |
| Space Station Training Facility |
| SSRMS |
| Space Station Remote Manipulator System |
| STS |
| Shuttle Transportation System |
| STRELA |
| Russian crane for ISS |
| SVF |
| Software Verification Facility |
| SWG |
| Structures Working Group |
| T&V |
| Test and Verification |
| TIM |
| Technical Interchange Meeting |
| TPOC |
| Technical Point of Contact |
| TRASYS |
| Thermal Radiation Analyzer System |
| TVIS |
| Treadmill with Vibration Isolation and Stabilization |
| ULF |
| Utilization Logistics Flight |
| USOS |
| Unites States On-Orbit Segment |
| VAC |
| Verification Analysis Cycle |
| VCM |
| Verification Compliance Matrix |
| VIPER |
| Vehicle Integrated Performance Evaluation Team |
| VLA |
| Verification Load Analysis |
| VMDB |
| Vehicle Master Database |
| VSC |
| Video Signal Converter |
A-1
Appendix b - glossary of terms
BMP
Unit for Purification of Micro impurities (Russian Acronym)
EDV
Water Storage and Supply System (Russian Acronym) InPU Integrated Control Panel (Russian Acronym)
SKV
System for the Conditioning of the Air (Russian Acronym)
SRKV
System for the Reconditioning of Condensate Water (Russian Acronym)
ZIP
Spares (Russian Acronym)
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
| A-1 |
| Appendix A |
| Acronym callout for CL |
| A-2 |
| Appendix A |
| Acronym callout for SCM |
| A-3 |
| Appendix A |
| Acronym callout for SPOM |
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
Appendix d – data item descriptions (DID) Attachment A: Data Item Description
DATA ITEM DESCRIPTION (DID)
DID # (number to be assigned by Book Manager) XXX-XX: Title of DID
PURPOSE: [For what will the information be used for? What product will be generated and how will it be used? Is the product returned to the providing organization? Is ther a two-way exchange of information? What ISS event(s) drive the need for the information exchange?]
SCOPE: [What types of data (drawings, parts lists, analysis reports, math models, software code, photographs, test/verification reports, refernce documents, etc.) will be included?]
DESCRIPTION: {Provide a detailed description of what is needed, specifying version and document numbers when known or applicable. Indicate the anticipated source(s) (with individual and organization names if known) of the information. Indicate any protocols, MOAs, risks that are related to the information exchange. Include attachments, if necessary. Identify any information that might be proprietary and specify the process for handling it properly.]
REQUESTING TEAM: [What work group(s) (in each agency) will receive the information?]
PROVIDER: [The data provider]
FEEDBACK REQUIRED: (Optional) [Does the data receiver have to provide any feedback to the data provider? If yes, describe what is needed.]
DELIVERY FORMAT: [What type of file, software application, drawing size, paper product, book, and technical explanation, etc. are specified for the information? List all that apply.]
NEED DATE(S): [What is the reasonable need date, taking into account the time required to obtain management and export control approval and the tim required for abotained the information, for it to support planned organizational tasks? What events, such as Shuttle filghts, design reviews, ISS events, etc. influence the need date? The need date, in most cases, will preced the deliver date. Will there be multiple deliveries made before the full complement is transferred? Will there be periodice deliveries (tied to Shuttle flights, version updates, ISS configuration changes, etc.) made over a long time period?]
| Concurred By: ____________________ | ____________________ | | | | |
| Technical Team Lead | | Technical Team Lead | | |
| NASA TPOC | Date | | Russia TPOC | Date |
| ____________________ | | ____________________ | | |
| Lois Lenox | | | | |
| NASA CM POC | Date | | Russia Technical Manager | Date |
| Approved By: ____________________ | | | ____________________ | |
| Alixei Bideev | | Russian Team 0 | Date |
| | NASA Team 0 | Date | |
Attachment C: Approved NDC List table D-1 SSP 50137 Approved Notification of Document Changes November 1, 1996
Description Approved Data
| NDC-001 |
| Russian Vehicles Team DIDs: R3 -01,2,3,4,13,27 |
U3 -14,15,16,17,18, 19,21,22,23,26
| Approve Team 3 DIDs |
| 3/18/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-002 |
| Technical Management Team DID: R0-02, Russian Segment Equipment Classification Lists |
| Revise DID R0-02, Russian Segment Equipment Classification Lists |
| 3/1/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-003 |
| Safety and Mission Assurance DIDs: R10-S04, Integrated Safety |
U10-S05, Integrated Safety
| Approve Team 10 DIDs for Integrated Safety Data |
| 3/22/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-004 |
| Service Module Team DID: R4A-01, (service module data) |
| Approve Team 4A Data Item Description |
| 6/21/96 (Team 0) |
TIM 15 (Tech Team)
| NDC-005 |
| Propulsion Team DID: R6D-08, (propulsion data) |
| Incorporate approved DID R6D-08 into SSP 50137 |
| 2/29/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-006 |
| Robotics Team DID: R8B-03, Approved RSC Electrical, Electronic, and Electromechanical (EEE) Parts and Suppliers |
| Approve Team 8B (EEE) Data Item Description |
| 3/20/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-007 |
| Safety and Mission Assurance Team DID: R10-R03, Critical Item List (CIL) |
| Approve Revised DID R10-R03, Critical Items List |
| 3/25/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-008 |
| Robotics Team DID: R8B-07,08,09,10,11 (Electromagnetic Effects [EME] Control Plan, Design Analysis Report [DAR], Test Reports and Plans) |
| Approve Team 8B (EME) Data Item Descriptions |
| 4/22/96 (Team 0) |
4/2/96 (Tech Team)
| NDC-009 |
| Guidance, Navigation and Control Team DID: R5D-2,3,4,7 (Guidance Navigation and Control [GN&C] data) |
U5D-08
| Approve Team 5D (GN&C) Data Item Descriptions |
| 4/8/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-010 |
| Guidance, Navigation and Control Team DID: R5C-02 & 03 (Automated Rendezvous and Docking [AR&D] data) |
| Approve Team 5C (AR&D) Data Item Descriptions |
| 4/10/96 (Team 0) |
TIM 17 (Tech Team)
| NDC-011 |
| R5A-03, Command and Measurement List… |
| Approve Team 5A (Command and Data Handling [C&DH]) Data Item Description |
| 4/26/96 (Team) |
TIM 17 (Tech Team)
| NDC-012 |
| Technical Management Team DID: R0-02, Russian Segment (RS) Equipment Classification Lists (ECL) |
| Approve Team 0 (Mgt.) Data Item Description |
| 5/3/96 (Team 0) |
4/26/96 TIM (Tech Team)
| NDC-013 |
| Technical Management Team DID: R0-03, RS Electronic Data Exchange & Vehicle Master Database (VMDB) Data Interface |
| Approve Team 0 (Mgt.) Data Item Description |
| 5/3/96 (Team 0) |
4/26/96 TIM (Tech Team)
| NDC-014 |
| Integration Perform/Resource Management Team DIDs: R1B-08 (Volume Data RS) |
U1B-09
| Approve Team 1B (International Partner [IP]) Data Item Descriptions |
| 5/3/96 (Team 0) |
4/26/96 TIM (Tech Team)
| NDC-015 |
| CheCs Team DIDs: R6B-02, U6B-03, |
U6B-04, U6B-05, R6B-06, U6B-07, U6B-08, U6B-09 (Crew Health DIDs)
| Approve Team 6B Crew Health Data Item Descriptions |
| 6/21/96 (Team 0) |
5/21/96 (Treadmill with Vibration Isolation and Stabilization [TVIS] TIM) 6/20/96 (#18 V. Yain)
| NDC-016 |
| Safety and Mission Assurance Team DIDs: R10-S01, U10-S08 |
R10-S02, R10-S03 U10-S09, R10-S04 (Safety U10-S05, R10-S06 and U10-S07, R10-R01 Risk U10-R05, R10-R02 DIDs) U10-R06, R10-R03
R10-QA01, U10-QA03
| Approve Team 10 Safety & Risk Data Item Descriptions |
| 6/19/96 (Team 0) |
6/17/96 TIM #18 (Tech Team)
| NDC-018 |
| Automated Rendezvous and Docking Team DIDs: R5C-02, AR&D Data Delivery |
R5C-03, AR&D Data Delivery
| Approve Team 5C AR&D Data Item Descriptions |
| 6/21/96 (Team 0) |
6/20/96 (Tech Team)
| NDC-019 |
| Power Team DID: R5E-07, Electrical/Thermal Data Requirements |
| Approved Team 5E Power Data delivery & closed |
| per data delivery TIM #18 |
| NDC-020 |
| Integration Perform/Resource Management Team DID: R1B-10, R1B-11, R1B-12 & U1B-13 - Power DIDs |
| Approved Team 1B Power Data Item Descriptions |
| 6/21/96 (Team 0) |
6/20/96 TIM #18
| NDC-021 |
| Assembly/Configuration Team DIDs: R1A-05, (Config.) Computer Aided Design (CAD) Models |
U1A-06, (Config.) CAD Models
| Approve revisions to R1A-05 and U1A-06 for exchange of CAD models |
| 6/21/96 (Team 0) |
6/18/96 (Tech Team)
| NDC-023 |
| Integration Perform/Resource Management Team DID: R1B-03, (RSA Microgravity) |
Structures and Mechanisms Team DID: R8A-02, (Loads Analysis Models) U8A-08, (Loads United States On-Orbit Segment [USOS]) Guidance, Navigation and Control Team DID: R5D-07, (GN&C Data)
| Revise delivery schedules for the listed DIDs |
| 6/21/96 (Team 0) |
6/20/96 (Tech Team)
| NDC-024 |
| Test and Verification Team DID: R9-01, Russian Segment Specialist (RSS) Verification Compliance Matrix for Russian Modules |
| Revise content & schedule for the RSS Verification Compliance matrix |
| 6/21/96 (Team 0) |
6/18/96 Test and Verification (T&V) Team
| NDC-026 |
| Structures and Mechanisms Team DID: R8A-04-1, Science Power Platform (SPP) Structural Verification Plan |
| Approve structures team DIDs for SPP element |
| 8/1/96 (Team 0) |
6/21/96 (Tech Team)
| NDC-027 |
| SPP Preliminary Design Review (PDR) Data Exchange |
| Science Power Platform Data exchange at SPP PDR |
| 7/25/96 (Team 0) |
7/25/96 (Tech Team)
| NDC-029 |
| Structures and Mechanisms Team DID: R8A-07-1, SPP Flight Element Structural and Mechanisms test reports |
| Approve Team 8A S&M SPP DID |
| 8/2/96 (Team 0) |
8/2/96 (Tech Team)
| NDC-030 |
| MultiDiscipline Team DID: R8B.1-16, Russian Astra II flight experiment data |
| Add approved DID to SSP 50137 approved section |
| 9/10/96 (Team 0) |
9/9/96 (Tech Team)
| NDC-031 |
| Russian Segment Modules Team DID: R4A-03, Service Module Digital Photography |
| Add approved DID to SSP 50137 approved section |
| 11/1/96 (Team 0) |
10/24/96 (Tech Team)
| NDC-032 |
| Russian Vehicles Team DIDs: R3-27, R3-03, R3-08, U3-22 |
| Revise descriptions and drawings for the listed DIDs |
| 4/28/97 (Team 0) |
4/28/97 (Tech Team)
| NDC-033 |
| Guidance, Navigation and Control Team DIDs: R5D-02, U5D-03, R5D-04, U5D-05, R5D-07, U5D-08, R5D-10, U5D-11 |
| Approve Team 5D (GN&C) DIDs |
| 11/1/96 (Team 0) |
11/1/96 (Tech Team)
| NDC-035 |
| Electrical Power Team DID: U5E-01 |
| Approve Team 5E |
| 11/1/96 (Team 0) |
11/1/96 (Tech Team)
| NDC-036 |
| Materials and Processes Team DID: R8B-03, Approved RSC EEE Parts and Suppliers |
| Approve Team 8B3 (Materials and Processes) DID |
| 10/29/96 (Tech Team) |
| NDC-037 |
| External Contamination Team DID: R8B-01, External Contamination |
| Approve Team 8B (Contamination) DID |
| 11/1/96 (Team 0) |
11/1/96 (Tech Team)
| NDC-038 |
| Appendix A Table A-1 DID List |
| Revise Bilateral Data List to include FGB/SPP PDGF data requirements |
| 11/1/96 (Team 0) |
10/31/96 (Tech Team)
| NDC-039 |
| Appendix A Table A-1 DID List |
| Revise Bilateral Data List to include PDGF data requirements |
| 1/16/97 (Team 0) |
1/16/97 (Tech Team)
| NDC-040 |
| Common Depress Strategy Team DIDs: R11B-01, U11B-02, R11B03, U11B-04, R11B-05, U11B-06, R11B-07, R11B-08, R11B-09, R11B-10, R11B-11, R11B-12, R11B-13 |
| Revise Bilateral Data List to include Operations DID |
| 12/13/96 (Team0) |
12/9/96 (Tech Team)
| NDC-041a |
| Integration Perform/Resource Management Team DIDs: R1B-02, R1B-03 |
| Revise Bilateral Data List to include Team 1B Microgravity additions |
| 3/5/97 (Team 0) |
11/4/97 (Tech Team)
| NDC-042 |
| Russian Vehicles Team DIDs: R3-03, R3-04, U3-22 |
| Revise the Bilateral Data to include Team 3A Soyuz/Progress due date revisions |
| 2/4/96 (Team 0) |
1/10/97 (Tech Team)
| NDC-43 |
| Materials and Processes Team DIDs: R8B-17, U8B-18 |
| Add to Bilateral Data List to include Team 8B Materials and Processes DIDs |
| 2/3/97 (Team 0) |
2/3/97 (Tech Team)
| NDC-044 |
| EMI/EMC Team DIDs: R8B-07, R8B-08, R8B-11 |
| Revise Bilateral Data List to include Team 8B2 Electromagnetic Effects Team updates |
| 4/11/92 (Team 0) |
3/21/97 (Tech Team)
| NDC-045 |
| Automated Rendezvous and Docking Team DIDs: R5C-03, R5C-02 |
| Revise Bilateral Data List to include Team 5C, Automatic Rendezvous and Docking (AR&D) |
| 5/16/97 (Team 0) |
5/14/97 (Tech Team)
| NDC-047 |
| Command and Data Handling Team DID: R5A-03-1 |
| Revise Bilateral Data List to include Team 5A1, Command and Data Handling |
| 6/2/97 (Team 0) |
4/28/97 (Tech Team)
| NDC-048 |
| Service Modules Team DID: R4A-01, Russian Vehicles Team DIDs: U3-23, U3-17 |
| Revise Bilateral Data Exchange List |
| 5/12/97 (Team 0) |
6/3/97 (Tech Team)
| NDC-049 |
| Structures Team DID: R8A1-10 |
| Revise Bilateral Data Exchange List |
| 5/12/97 (Team 0) |
5/12/97 (Tech Team)
| NDC-050 |
| Technical Management Team DID: R0-7B-08 |
| Revise Bilateral Data Exchange List |
| 5/14/97 (Team 0) |
5/12/97 (Tech Team)
| NDC-051 |
| Russian Vehicles Team DIDs: U3-17, U3-23 |
| Revise Bilateral Data Exchange List |
| 5/30/97 (Team 0) |
6/3/97 (Tech Team)
| NDC-052 |
| Test and Verification Team DID: R9-01 |
| Revise Bilateral Data Exchange List |
| 6/18/97 (Team 0) |
6/18/97 (Tech Team)
| NDC-053 |
| Automated Rendezvous and Docking Team DID: R5C-03 |
| Revise BDEALS for Team 5C AR&D DID |
| 7/17/97 (Team 0) |
7/16/97 (Tech Team)
| NDC-054 |
| Automated Rendezvous and Docking Team DID: R5C-02 |
| Revise BDEALS for Team 5C AR&D DID RSC-02 |
| 7/17/97 (Team 0) |
7/16/97 (Tech Team)
| NDC-055 |
| Service Modules Team DID: R4D-03 |
| Revise BDEALS for Team 4A, Service Module (SM) DID R4A-03 |
| 7/10/97 (Team 0) |
7/11/97 (Tech Team)
| NDC-056 |
| TIM #20 protocol, Team 4D4-PDGF Integration |
| BDEAL Description: PDGF stand attachment mechanisms (foot mechanism) |
| 7/11/97 (Team 0) |
6/20/97 (Tech Team)
| NDC-057 |
| Propulsion Team DID: R6D-08 |
| Revise due date of BDEALS for Team 6D-08, Propulsion |
| 7/21/97 (Team 0) |
7/21/97 (Tech Team)
| NDC-058 |
| Structures and Mechanisms Team DID: R8A-06 |
| Revise due date of BDEALS for Team 8A-06, Structures and Mechanisms |
| 8/8/97 (Team 0) |
8/8/97 (Tech Team)
| NDC-059 |
| Structures and Mechanisms Team DID: R8A-09 |
| Revise due date of BDEALS for Team 8A-09, Structures and Mechanisms |
| 8/8/97 (Team 0) |
8/8/97 (Tech Team)
| NDC-060 |
| Flight Crew Systems and Integration Team DID: RO-7B-09 |
| Add DID to BDEALS SPP 50137 for Team O-7B, Training Facilities |
| 8/7/97 (Team 0) |
8/7/97 (Tech Team)
| NDC-061 |
| Thermal Team DIDs: R6C-01, R6C-02, R6C-03, R6C-04, R6C-09 |
| Revise BDEALS SPP 50137 for Team 6C, Thermal Control Systems |
| 8/13/97 (Team 0) |
8/13/97 (Tech Team)
| NDC-062 |
| Structures and Mechanisms Team DID: R8A-01 |
| Revise BDEALS SPP 50137 for Team 8A.2 MM/OD Shielding |
| 10/22/97 (Team 0) |
10/15/97 (Tech Team)
| NDC-063 |
| Integration Perform/Resource Management Team DID: R1B-02 |
| Revise BDEALS SPP 50137 for Team 1B.6, Microgravity |
| 11/26/98 (Team 0) |
9/8/97 (Tech Team)
| NDC-065 |
| Integration Perform/Resource Management Team DID: R1B-03 |
| Revise BDEALS SPP 50137 for Team R1B.7, Mass Properties |
| 8/15/97 (Team 0) |
8/15/97 (Tech Team)
| NDC-066 |
| Appendix A Table A-1 DID List |
| Update the contents and delivery schedule of GN&C DIDs |
| 8/19/97 (Team 0) |
8/15/97 (Tech Team)
| NDC-069 |
| Integration Perform/Resource Management Team DID: R1B-08 |
| Revise BDEALS SPP 50137 for Team 1B.2 Altitude Strategy, Prop Resupply |
| 8/24/97 (Team 0) |
8/21/97 (Tech Team)
| NDC-072 |
| Technical Team DIDs: U11B-08, U11B-12 |
| Revise BDEALS SPP 50137 for Team 11B Command Systems (Training Ops) |
| 8/29/97 (Team 0) |
8/22/97 (Tech Team)
| NDC-073 |
| Command and Data Handling Team DID: R5A-01 |
| Revise BDEALS SPP 50137 for Team 5A C&DH |
| 9/3/97 (Team 0) |
8/28/97 (Tech Team)
| NDC-075 |
| Life Support (ECLSS) Team DID: R6A-04 |
| Add new DID R6A-04, MIR Depressurization Airflow Sensor Experiment Results |
| 9/16/97 (Team 0) |
8/28/97 (Tech Team)
| NDC-076 |
| Test and Verification Team DID: U09-02, Interface Verification Visibility Report (IVVR) for PMA-1 |
| Revise BDEALS SPP 50137 for Team 9 Test and Verification (T&V) |
| 10/23/97 (Team 0) |
10/23/97 (Tech Team)
| NDC-078 |
| Flight Crew Systems and Integration Team DID R7B-11, Russian Laptop Configuration for Russian Segment Trainer (RST) at SSTF |
| Add DID to BDEALS SPP 50137 for Team O-7B, Training Facilities |
| 12/18/97 (Team 0) |
11/12/97 (Tech Team)
| NDC-079 |
| Flight Crew Systems and Integration Team DID R7B-12, SM Integrated Control Panel Configuration (ICP) for Russian Segment Trainer (RST) as SSTF |
| Add DID to BDEALS SPP 50137 for Team O-7B, Training Facilities |
| 12/15/97 (Team 0) |
12/15/97 (Tech Team)
| NDC-080 |
| Russian Vehicles R3-04 |
| Revise DID R3-04, Technical description of Progress M vehicle |
| 11/12/97 (Team 0) |
11/12/97 (Tech Team)
| NDC-082 |
| Structures and Mechanisms Team DID: U8A-11 |
| Creation of DID U8A-11 for Team 8A.2 MM/OD Analysis Output |
| 10/8/97 (Team 0) |
10/15/97 (Tech Team)
| NDC-083 |
| Communication and Tracking Team DID: R5B-04 |
| Add DID R5B-04 C&T ONS Hazard Report |
| 12/3/97 (Team 0) |
12/3/97 (Tech Team)
| NDC-084 |
| Integration Perform/Resource Management Team DID: R1B-05 |
| Revise delivery date for R1B-05 for Integrated Performance team |
| 1/14/98 (Team 0) |
1/20/98 (Tech Team)
| NDC-088 |
| Integration Perform/Resource Management Team DID: R1B-06 |
| Revise delivery date for R1B-06 for Integrated Performance team |
| 1/20/98 (Team 0) |
3/2/98 (Tech Team)
| NDC-089 |
| Integration Perform/Resource Management Team DID: U1B-07 |
| Revise delivery date for U1B-07 for Integrated Performance team |
| 2/27/98 (Team 0) |
2/28/98 (Tech Team)
| NDC-090 |
| Appendix A Table A-1 DID List |
| Update contents and delivery schedules of GN&C DIDs |
| 11/26/97 (Team 0) |
11/21/97 (Tech Team)
| NDC-091 |
| Structures and Mechanisms Team DID: R08A-03 |
| Revise BDEALS for Team 8A-03, Structures and Mechanisms |
| 12/21/97 (Team 0) |
12/21/97 (Tech Team)
| NDC-092 |
| Test and Verification Team DID: R9-01 |
| Update the schedule information for VCM deliveries |
| 1/13/98 (Team 0) |
12/17/97 (Tech Team)
| NDC-093 |
| ISS Integration Team DID: R1A-07 |
| Add new DID to BDEALS SSP 50137 |
| 1/13/98 (Team 0) |
1/13/98 (Tech Team)
| NDC-094 |
| Flight Crew Systems and Integration Team DID: R7B-13 |
| Add new DID to BDEALS SSP 50137 |
| 2/4/98 (Team 0) |
1/20/98 (Tech Team)
| NDC-095 |
| Flight Crew Systems and Integration Team DID: R7B-XX |
| Add DID to BDEALS SPP 50137 to reflect SM RST Software Documentation |
| 1/13/98 (Team 0) |
1/14/98 (Tech Team)
| NDC-096 |
| Flight Crew Systems and Integration Team DID: R7B-15 |
| Add DID to BDEALS SPP 50137 to reflect FGB RST Software Documents |
| 3/3/98 (Team 0) |
2/6/98 (Tech Team)
| NDC-097 |
| Flight Crew Systems and Integration Team DID: RO-7B-03 |
| Add DID to BDEALS SPP 50137 to reflect FGB RST Software Documents |
| 8/29/98 (Team 0) |
8/11/98 (Tech Team)
| NDC-099 |
| Safety and Mission Assurance Team DIDs: R10-S06, U10-S07 |
| Delete DIDs from BDEALS SPP 50137 |
| 3/23/98 (Team 0) |
3/27/98 (Tech Team)
| NDC-100 |
| Common Depress Strategy Team DIDs: R11C-01, R11C-02, R11C-03, R11C-04 |
| Add DIDs Team 11C, Integrated Planning Systems |
| 3/10/98 (Team 0) |
3/10/98 (Tech Team)
| NDC-101 |
| Assembly/Configuration Team DID: R1A-08 |
| Add DID for Team 1A Assembly/Configuration |
| 3/24/98 (Team 0) |
3/11/98 (Tech Team)
| NDC-102 |
| Integration Perform/Resource Management Team DIDs: R1B-05, R1B-06, U1B-07, R1B-08, U1B-09 |
| Revise description and summary of named DIDs |
| 3/11/98 (Team 0) |
3/11/98 (Tech Team)
| NDC-103 |
| Automated Rendezvous and Docking Team DIDs: R5C-02, R5C-03 |
| Revise DIDs for Team 5C AR&D |
| 3/12/98 (Team 0) |
3/23/98 (Tech Team)
| NDC-106 |
| Service Modules Team DID R4A-4 |
| Add DID for Team 4A, Service Module (SM) |
| 6/30/98 (Team 0) |
5/26/98 (Tech Team)
| NDC-107 |
| Command and Data Handling Team DID: R5A-03-1 |
| Revise DID for Team 5A.1 C&DH H/W |
| 6/18/98 (Team 0) |
4/10/98 (Tech Team)
| NDC-108 |
| Propulsion Team DID: R6D-08 |
| Revise DID for Team 6D, Propulsion |
| 4/22/98 (Team 0) |
4/21/98 (Tech Team)
| NDC-109 |
| Test and Verification Team DID: U9-02 |
| Revise DID for Team 9, Test and Verification |
| 5/8/98 (Team 0) |
5/8/98 (Tech Team)
| NDC-110 |
| Appendix A Table A-1 DID List |
| Update the contents and delivery schedules of GN&C DIDs |
| 6/1/98 (Team 0) |
6/1/98 (Tech Team)
| NDC-113 |
| Electromagnetic Interface/Electromagnetic Compatibility Team DID: R8B-19 |
| Add DID R8B-19 to BDEALS for team 8B.3 EMI/EMC |
| 3/24/99 (Team 0) |
7/17/98 (Tech Team)
| NDC-115 |
| Environments Team DID: R8B-20, U8B-21 |
| Add DID R8B-20 to BDEALS for team 8B.1 Environments |
| 7/9/98 (Team 0) |
9/15/98 (Tech Team)
| NDC-116 |
| Integration Perform/Resource Management Team DID: R1B-02 |
| Update the contents and delivery schedules of microgravity team (1B) |
| 11/26/98 (Team 0) |
12/14/98 (Tech Team)
| NDC-117 |
| Integration Perform/Resource Management Team DID: R1B-02 |
| Update the contents and delivery schedules of microgravity team (1B) |
| 11/26/98 (Team 0) |
12/23/98 (Tech Team)
| NDC-118 |
| Structures and Mechanisms Team DID: RO8A-06 |
| Description and schedule changes for DID R8A-061 |
| 3/11/99 (Team 0) |
3/11/99 (Tech Team)
| NDC-119 |
| Processes Team DID: R0A.6-01 |
| Add DID for Team 0A.6 Imagery Group R0A.6 to BDEALS |
| 11/12/98 (Team 0) |
11/3/98 (Tech Team)
| NDC-122 |
| Common Depress Strategy Team DID: R11-30 |
| Add DID to BDEALS for Operations Team Critical Failures and Spares Data |
| 12/22/98 (Team 0) |
11/23/98 (Tech Team)
| NDC-123 |
| Automated Rendezvous and Docking Team DID: R5C-03 |
| Revise DIDs for Team 5C AR&D |
| 11/30/98 (Team 0) |
11/30/98 (Tech Team)
| NDC-125 |
| Structures and Mechanisms Team DID: U8A-017 |
| Add DID to BDEALS for Team 8A Structures and Mechanisms |
| 1/4/99 (Team 0) |
1/4/99 (Tech Team)
| NDC-126 |
| Thermal Team DIDs: R6C-01, R6C-02, R6C-03, R6C-04, R6C-09 |
| Revise DIDs to BDEALS for Team 6C Thermal Control Systems |
| 4/30/99 (Team 0) |
2/1/99 (Tech Team)
| NDC-127 |
| Thermal Team DID: R6C-11 |
| Add DIDs to BDEALS for Team 6C Thermal Control Systems |
| 4/30/99 (Team 0) |
2/1/99 (Tech Team)
| NDC-128 |
| Safety and Mission Assurance Team DID: R10-S11 |
| Ass DID R10-S11 to BDEALS, SSP 50137 |
| 2/16/99 (Team 0) |
2/16/99 (Tech Team)
| NDC-129 |
| Science Power Platform Team DID: R4D-12 |
| Add DID R4D-12 to BDEALS, SSP 50137 for SSP Management Team |
| 3/11/98 (Team 0) |
3/11/98 (Tech Team)
| NDC-130 |
| Science Power Platform Team DID: R4D-13 |
| Add to BDEALS, SSP 50137 for SPP Management Team data transferred |
| 3/24/99 (Team 0) |
3/11/99 (Tech Team)
| NDC-131 |
| Science Power Platform Team DID: R4D-15, U4D-14 |
| Add BDEALS, SSP 50137 for SPP Team DIDs R4D-14 and R4D-16 |
| 3/11/99 (Team 0) |
3/11/99 (Tech Team)
| NDC-132 |
| Science Power Platform Team DID: U4D1-16 |
| Add to BDEALS, SSP 50137 for SPP Team DID U4D1-16 |
| 3/11/99 (Team 0) |
3/11/99 (Tech Team)
| NDC-133 |
| Science Power Platform Team DID: R4D1-17 |
| Add to BDEALS , SSP 50137 for SPP 3D-CAD model Subteam |
| 3/24/99 (Team 0) |
3/11/99 (Tech Team)
| NDC-134 |
| Automated Rendezvous and Docking Team DID: R5C-02 |
| Revise BDEALS for Team 5C AR&D DID R5C-02 |
| 3/18/99 (Team 0) |
4/13/99 (Tech Team)
| NDC-138 |
| Science Power Platform Team DID: U4D3-1 |
| Add to BDEALS, SSP 50137 for SSP 4S Docking Subteam |
| 8/4/99 (Team 0) |
7/27/99 (Tech Team)
| NDC-140 |
| Avionics Systems Team DID: RO-5-01, UO-5-01 |
| Add DIDs RO-5-01 and UO-5-01 to BDEALS |
| 9/13/99 (Team 0) |
10/18/99 (Tech Team)
| NDC-144 |
| Electromagnetic Interface/Electromagnetic Compatibility Team DID: R8B-22 |
| Add DID R8B-22 to BDEALS |
| 9/29/99 (Team 0) |
7/26/99 (Tech Team)
| NDC-145 |
| Environments Team DID: R8B-23, Pyrotechnic Devices Test Report and Compliance |
| Add DID R8B-23 to BDEALS |
| 9/29/99 (Team 0) |
3/31/99 (Tech Team)
| NDC-147 |
| Science Power Platform Team DID: R4D-12 |
| Add DID R4D-12 to BDEALS |
| 9/20/99 (Team 0) |
9/29/99 (Tech Team)
| NDC-151 |
| Science Power Platform Team DID: R4D3-2, U4D3-2 |
| Add DID R4D3-2 and U4D3-2 to BDEALS |
| 10/28/99 (Team 0) |
10/27/99 (Tech Team)
| NDC-152 |
| Science Power Platform Team DID: R4D-13 |
| Add DID R4D-13 to BDEALS |
| 11/5/99 (Team 0) |
10/25/99 (Tech Team)
| NDC-154 |
| Science Power Platform Team DID: U04D4-01 |
| Add DID U-4D4-01 to BDEALS |
| 12/3/99 (Team 0) |
11/17/99 (Tech Team)
| NDC-155 |
| Science Power Platform Team DID: U4D3-3, U4D3-4, U4D3-5, R4D3-3, R4D3-4 |
| Add following new DIDs to BDEALS |
| 2/1/00 (Team 0) |
2/2/00 (Tech Team)
| NDC-156 |
| Technical Management Team DID: V-O-01 |
| Add following new DID to BDEALS |
| 3/9/00 (Team 0) |
12/3/99 (Tech Team)
| NDC-159 |
| Portable Computer Systems Team DID: U-5A.5-01 |
| Add following new DID to BDEALs |
| 1/18/00 (Team 0) |
12/20/99 (Tech Team)
| NDC-161 |
| Stress Analysis Fracture Control Team DIDs: R08A.1-22, R08A.1-23 |
| Add new DIDs to BDEALS |
| 6/15/00 (Team 0) |
6/13/00 (Tech Team)
This is the start of the file's text. The full file is on GovTribe.