SSP_50908-Baseline.docx

NASA/ASI Permanent Multipurpose Module (PMM) Project Joint Implementation Plan (JIP)

International Space Station Program

Baseline

June 2010

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract No. NNJ09GA18B

SSP 50908

Baseline

SSP 50698

BASELINE

ii

REVISION AND HISTORY PAGE

PREFACE

NASA/ASI Permanent multipurpose module (PMM) Project Joint implementation plan (JIP)

This document is developed and maintained by the NASA PMM Project Office. This document is under the control of the Space Station Control Board (SSCB), and any changes or revisions will be approved by the ISS Program Manager. The initial baseline release of this document is under the control of the Space Station Control Board [SSCB]. The SSCB delegates control and approval authority for future updates and/or revisions to the Multilateral Vehicle Control Board (MVCB).

INTERNATIONAL SPACE STATION PROGRAM

module (PMM) Project Joint implementation plan (JIP)

CONCURRENCE

jUNE 2010 module (PMM) Project Joint implementation plan (JIP)

CONCURRENCE

JUNE 2010

module (PMM) Project Joint implementation plan (JIP)

LIST OF CHANGES

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

Board Name

Entry Date

Change

Paragraph(s)

SSCB

August 2010

Baseline

All

TABLE OF CONTENTS

APPENDIX

TABLE

FIGURE

1.5-1 NASA/ASI PMM Documentation 1-3

SSP 50908

Baseline vii introduction This NASA/ASI PMM Joint Implementation Plan (JIP) defines the programmatic, technical and contractual coordination processes to be used by the National Aeronautics and Space Administration (NASA) and the Agenzia Spaziale Italiana (ASI) for the implementation of the International Space Station PMM Project.

background NASA and ASI have agreed to convert one of the Multi-Purpose Logistic Modules (MPLM) to a PMM, to be used to provide additional mass to be launched to the International Space Station (ISS) and additional on-orbit stowage volume that could also allow a more effective positioning of experiments throughout ISS.

The MPLMs were provided by ASI to NASA per the “Memorandum Of Understanding between the Italian Space Agency and the United States National Aeronautics and Space Administration for the design, development, operation and utilization of three Mini Pressurized Logistic Modules for the International Space Station” signed in October 1997.

PURPOSE

NASA and ASI have agreed to the management approach outlined in this JIP and will implement all PMM activities in accordance with this approach.

This JIP only deals with the modification phase of one MPLM unit to become PMM.

The mission execution and the related sustaining to be provided by ASI, as per the Memorandum of Understanding (MOU), shall be subject of a dedicated by-lateral Sustaining Engineering Plan.

ASI will manage the responsibilities related with the modifications needed on MPLM to make it a module permanently attached to the International Space Station. NASA will manage the systems engineering, Government Furnished Equipment (GFE) and Space Station common hardware installed on the PMM, and the PMM integration role.

The objectives of the JIP are as follows:

SCOPE

The JIP describes the PMM management and coordination processes and the interfaces between NASA and ASI for the PMM design, development, and post delivery activities. The processes and responsibilities described herein are applicable to all NASA and ASI organizations, including their respective contractors, which are directly involved in the Space Station PMM Project.

CONTROL and Maintenance The JIP is controlled, through approval signatures, by the ASI MPLM/PMM Program Manager and the NASA Space Station Program Manager. Changes to this plan are approved as a result of discussions of proposed changes reviewed at either Space Station Control Board (SSCB) or at NASA/ASI bilateral Program Reviews. All changes require the approval of NASA and ASI. Following initial approval, NASA will maintain this JIP, including the incorporation of approved changes, which NASA will release and distribute.

PRECEDENCE

This JIP is subordinate to the Space Station Intergovernmental Agreement and to the Memorandum of Understanding between ASI and NASA. In the event of a conflict with any of the lower level multilateral or bilateral documentation, this document shall take precedence for the PMM Project.

Figure 1.5-1 NASA/ASI PMM Documentation

4-10 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.

applicable documents

Volume 1: Station Program Management Plan

Volume 10: Sustaining Engineering

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.

Volume 5: Logistics and Maintenance, Part 1: Maintenance

SSP 50869 Prime Item Development Specification for the Permanent Multipurpose Module.

TAS-I PMM-PM-xxx PMM CADM Plan

NASA/ASI PROGRAM INTERFACES

The formal NASA/ASI Program interface is between the NASA Space Station Program Manager and the ASI MPLM/PMM Program Manager. In particular, they are responsible for implementing applicable Program Directives and Partner Program Directives; for establishing, controlling, and updating Program requirements baseline; and for directing Program implementation.

NASA/ASI MANAGEMENT INTERFACES

This section identifies the NASA/ASI management interfaces necessary to ensure effective planning and coordination during the PMM Project.

NASA/ASI ORGANIZATIONAL INTERFACES

The primary working interface is between the NASA Space Station Vehicle Office, PMM Project Manager at Johnson Space Center (JSC), Houston and the ASI PMM Project Office at ASI Rome.

The respective NASA and ASI PMM Project Managers interface directly with each other and make binding technical, implementation, and programmatic decisions within the framework of the agreements between the respective Program Managers. Each Project Manager can give delegated authority to other members of his team to act on his behalf.

NASA CONTRACTOR-TO-ASI CONTRACTOR INTERFACE

Day-to-day technical interchange between the NASA and ASI counterparts and contractors is encouraged and can take place without specific agency approval. This interchange will be executed from their respective home bases, using electronic mail, documentation/letter exchange, and teleconferences. Such interchange shall be regarded as informal and shall not be binding on the Parties unless subsequently formalized by the authorized ASI and NASA Project Managers.

LIAISONS

ASI and NASA recognise the effectiveness of a liaison office in the partner’s facility, to facilitate the working relationships and to provide support in the resolution of problems encountered.

ASI has liaison offices established for the MPLM Program at JSC and Kennedy Space Center (KSC) that shall work as a liaison office for PMM-related activities as well.

As NASA recently closed its liaison office in Torino, ASI is committed to provide, as a support to NASA and NASA contractors personnel, while in Italy, an office location fully equipped with desktop computers, LAN lines, printers, wireless router and information technology support. The office will be located in the Advanced Logistics Technology Engineering Center (ALTEC) facility.

JOINT MANAGEMENT MECHANISMS

This section describes the joint management mechanisms by which the NASA and ASI organizations will manage their combined activities.

BOARDS

SPACE station Control Board The Space Station Control Board (SSCB) is chaired by the NASA Space Station Program Manager, and establishes and controls the top-level program requirements, schedules, cost and overall configuration, with the participation of all International Partners. The International Partner (IP) oriented SSCB sessions are scheduled with sufficient lead-time to allow change evaluation and participation by all international partners plus ASI, which has the status of “international participant” .

SPACE STATION PROGRAM CONTROL BOARD

The Space Station Program Control Board (SSPCB) is chaired by the NASA Space Station Program Manager and is the highest board for United States (US) Hardware (HW) and Software (SW) on the ISS. The SSPCB establishes and controls the top-level requirements, schedules, cost and overall configuration for the US. On-Orbit Segments and other ISS HW and SW provided by NASA. The SSPCB will have authority on issues regarding PMM that are within the NASA /ASI Agreement. The SSPCB is normally held weekly. ASI shall be represented, for PMM matters, by the ASI Houston Office, and/or shall participate via telecon through the ASI MPLM/PMM Program manager or his nominated delegate when necessary.

MULTILATERAL VEHICLE Control Board The Multilateral Vehicle Control Board (MVCB) is chaired by the NASA Vehicle Office Manager, and, for PMM matters, will review and disposition all formal changes to the PMM baseline with the exception of changes to the avionics and SW baseline that shall be reviewed and dispositioned by the Avionics and Software Control Board (ASCB). In addition, the MVCB will review and disposition any other pertinent business for PMM including unresolved issues from PMM Status and Issues Teleconference (SIT). For changes that are schedule-critical, the MVCB shall have the authority to request out-of-board implementation from the SSPCB after the NASA/ASI respective responsibilities have been agreed and documented in accordance with the process defined in section 4.3.7. In addition, when required for schedule critical changes, Joint MVCB, with representatives from the Multilateral Avionics and Software Control Board (MASCB), Mission Integration and Operations Control Board (MIOCB), and Program Integration Control Board (PICB) will be held. The MVCB will make every attempt to reach all the decisions by consensus. If consensus cannot be reached, and there is a significant cost, schedule or programmatic impact for the dissenting members, the issue will referred to the SSPCB for resolution.

NASA will facilitate the MVCB. NASA will provide minutes for each board meeting within five working days of the meeting. ASI will review and provide redlines and/or concurrence within five working days of receiving them. Agreements and disagreements will be noted in the minutes. Before any change authorization on PMM matters is committed, the appropriate section of the minutes shall have been concurred in writing by the ASI MVCB representative and ASI and NASA Project Managers. The MVCB minutes will be signed in less than fifteen working days from the Board.

For PMM portion of the MVCB, NASA and ASI will agree to the nomination of key personnel for board membership. Any changes to the list will require notification of the other members. At a minimum, PMM portion of the MVCB will consist of:

Other functional experts will be invited to participate as required. The MVCB will meet on Thursdays as required.

DOCUMENTATION

BILATERAL DOCUMENTATION

The term “bilateral document” refers to all Space Station documents for PMM Project that are developed, approved, and agreed to jointly by NASA and ASI at the Space Station Program Manager level. NASA manages the documentation development process and produces the final document and subsequent updates for approval by NASA and ASI.

PROGRAM DIRECTIVES

The NASA Space Station Program Manager will issue Program Directives that provide direction to the US Program of which PMM form part concerning special requirements, policy, controls, and Program implementation forums (e.g., panels, working groups etc.). Following approval, these Program Directives will be maintained in the Space Station Library. It is the responsibility of the ASI and NASA PMM Project Managers to ensure PMM implementation of these directives, following the formal change process as define in section 4.3.7.

MISSION Integration and OPERATIONS DOCUMENTATION The mission integration and operations documentation, such as Mission Integration Plan (MIP), Increment Definition and Requirements Document (IDRD) and associated annexes, etc. for PMM shall be generated by NASA utilizing inputs provided by ASI as defined in the Bilateral Data Exchange Agreements, Lists, and Schedules (BDEALS) and Station Program Implementation Plan (SPIP).

CONFIGURATION MANAGEMENT

The NASA/ASI requirements and responsibilities for Configuration Management (CM) are defined in SSP 50200-01, Station Program Implementation Plan, Volume l: Station Program Management, Revision C, SSP 50123, the Configuration Management Handbook, Revision C and SSP 41170, Configuration Management Requirements, Revision C.

ASI/TAS-I CM processes that shall be applied for PMM are described in a dedicated PMM CADM Plan.

CONFIGURATION IDENTIFICATION

Configuration identification for the PMM Project shall be accomplished through the development of formal documentation, defined herein.

INTERFACE DEFINITION

The Interface Requirement Documents (IRDs) and Interface Control Document (ICDs) define the physical, functional, and performance interfaces between the Space Station and PMM. The interface process shall be consistent with SSP 30459, International Space Station Interface Control Plan. The IRDs and ICDs are controlled by the Interface Control Working Group (ICWG).

A PMM interface requirements will be defined into a unique “PMM cargo accommodation handbook”. Details of the book will be included on the BDEALS ####.

INTERFACE CONTROL

Interface control documentation shall be scheduled and developed to support program design, schedules and milestones. Traceability to design drawings of interface requirements/parameters explicitly called in the Prime Item Development Specification (PIDS) shall be maintained by ASI until the transfer of responsibility/ownership to NASA of the PMM modified/new HW and SW and verification closure data delivery as per the BDEALS.

SPECIFICATIONS

SSP 50869, Prime Item Development Specification defines the functional and performance requirements for PMM, derived through changes, as needed and agreed between NASA and ASI, to the MPLM Prime Item Development Specification SSP 41164, Italian Mini-Pressurized Logistics Segment.

ACCEPTANCE DATA PACKAGES

Acceptance Data Packages (ADPs) shall be provided by ASI for the modified/new HW and SW for PMM. ADPs shall provide a complete and verified status, including the as-built configuration of each item, and information pertinent to acceptance. They shall also enable the continuation of required activities subsequent to transfer of responsibility/ownership.

ADPs shall be prepared and delivered in accordance with the BDEALS and shall be maintained throughout the life cycle of the configuration item by the custodian.

NASA and ASI shall support the maintenance with complete and accurate updates to the appropriate ADP sections while the item is under custodianship.

ESTABLISHED BASELINES

Configuration baselines, plus approved changes from those baselines, define the established configuration identification by which the item is controlled. Configuration baselines are established following successful completion of requirements and design reviews and configuration audits. PMM overall configuration baselines, as resulting from the modifications to the MPLM, will be transferred from ASI to NASA following the transfer of responsibility/ownership of ASI deliverable items.

After a baseline is established, it is essential that effective control be established to preclude any unauthorized changes to that baseline. To this end, all proposed changes to an established baseline should only be handled via a formal Change Request (CR) process. Proposed changes to the baseline shall be reviewed, authorized, and implemented by the forum (board) which baselined the original requirement.

CHANGE PROCESS, FORMS AND INSTRUCTIONS

The NASA and ASI Configuration Management Offices (CMO) shall process/monitor all CRs, which are written against bilaterally approved documents or NASA accepted configuration baselines impacting PMM. Editorial changes shall not be processed separately through the CMO system, but shall be collected by CMO and processed through the CMO system as a “block update”. Change Process Forms and instructions to be complied with are documented in the SSP 50123, Configuration Management Handbook.

MODIFICATION CHANGES

Prior to transfer of responsibility/ownership of the provided HW and SW, ASI shall be responsible for the generation of any modification package, of configuration control of the item to be modified, and of the associated ADP. Following transfer of responsibility/ownership and transfer of configuration baselines from ASI, NASA will be responsible for the control of all PMM configuration changes.

DEVIATIONS, EXCEPTIONS, AND WAIVERS

Deviations shall be utilized to depart from the requirements of the specified configuration item prior to manufacture of an item. Exceptions shall be used to tailor a general specification requirement applicable to a specific item in a specific situation. Waivers shall be utilized if an item does not conform to the approved configuration baseline. Exceptions, deviations, and waivers to baseline requirements shall be processed through the same change control system and dispositioned by the same level of authority that controls the requirement addressed by the exception/deviation/waiver. Waivers, deviations, and exceptions to PMM HW and SW baseline will require NASA approval per SSP 50123.

CONFIGURATION STATUS ACCOUNTING

Configuration accounting and verification functions shall maintain complete and accurate records on the configuration status of all HW and SW. These records shall be the responsibility of ASI through its design contractor until transfer of responsibility/ownership of the modified HW and overall configuration baseline hand-over to NASA.

CONFIGURATION VERIFICATION

CM includes activities associated with assuring that requirements are properly implemented and traceable and that the HW and/or SW is certified/verified as having been designed and built to the correct approved configuration baseline.

DESIGN REVIEWS, Technical Interchange Meetings AND AUDITS NASA and ASI, having authority for the development and control of HW/SW elements of PMM Project, shall ensure that all higher-level requirements and interface requirements have been properly allocated and implemented. Requirements reviews, design reviews, Technical Interchange Meetings (TIMs), and configuration audits shall be conducted on all deliverable HW and SW to ensure proper requirements flow down and implementation. These reviews shall establish baselines for further development and to verify the design approach. In order to allow design for PMM to proceed in the most efficient manner, design reviews and audits will be conducted as incremental reviews.

When the design of a particular Configuration Item (CI)/Computer Software Configuration Item (CSCI) is sufficiently mature, the appropriate design review/audit shall be conducted. These reviews shall be progressive in nature, based on successful completion of lower level reviews.

CHANGE REVIEW and APPROVAL PROCESS Change requests and evaluations received shall be presented to the change approving authority for disposition. Changes that have programmatic impact to PMM Project shall be reviewed at the MVCB to assess the proposed technical change, implementation, the industrial impact, and its appropriate financial responsibility. Presentations to the MVCB should include the results of the review. The MVCB recommendations shall be forwarded to the appropriate change authority for approval. Cost bearing changes will be forwarded to the SSPCB for approval. Cost bearing changes that are schedule-critical could be implemented after the NASA/ASI respective responsibilities have been agreed at the MVCB and with written SSPCB NASA and ASI representatives outside board concurrence. In addition, to address schedule-critical changes, the Program will hold joint MVCB, ASCB, MIOCB, and PICB as required. The allowable review time for each change shall not exceed three weeks. Deviating from the allowable review time is possible, but should be coordinated/agreed upon between the NASA and ASI CMOs. Copies of changes shall be made available in Portable Document Format (PDF) and Interleaf format.

DOCUMENTATION Maintenance NASA CMO shall maintain control of all baselined documents. NASA shall maintain all bilateral and multilateral documents and NASA generated documents. After the approved change(s) have been incorporated into the document(s) NASA or delegated ASI CMO shall distribute the revised documents according to an agreed format and a documentation distribution list. Furthermore, NASA CMO shall send documentation alerts to an agreed distribution list via e-mail.

CONFIGURATION MANAGEMENT OFFICE COORDINATION

The NASA and ASI CMO will coordinate on a routine basis to complete PMM CM functions in a timely manner.

SAFETY AND MissION ASSURANCE

GENERAL REQUIREMENTS BASELINE

The cooperation between NASA and ASI on the ISS Program has established that the processes and requirements applied by both Agencies in implementing the S&MA activities are equivalent.

NASA is responsible for the overall safety, reliability, maintainability, and analytical tasks for PMM. ASI provides the safety reliability and maintainability assessments for the items they provide as well as provides the Safety Data Package to the Safety Review Panel for the PMM. NASA and ASI are each responsible for the quality assurance for the items they provide and for the all the integration activities that they perform. NASA will provide an onsite Quality Assurance representative to support the implementation of SSP 50724.

ASI/TAS-I PA processes that shall be applied for PMM are described in a dedicated “PMM PA Plan”.

PMM REVIEWS and management Meetings NASA and ASI will conduct formal reviews and other meetings of PMM project activities, products, and progress as defined below.

PMM PROJECT REVIEWS

Planned Project reviews and objectives are described below. The schedule for these reviews is described in the integrated program master schedule. In addition, integrated system reviews are conducted, focusing on integrated design or integrated SW readiness matters that are not within the scope of the project reviews.

PMm documentation baseline The purpose of the PMM Documentation baseline is to baseline the configuration of the PMM and the requirements that will be used for the design of the PMM modifications.

Critical Design Review The purpose of the Critical Design Review (CDR) is to determine that the design is in compliance with the requirements as defined in the PIDS and that the design satisfies the operational and safety performance requirements of the International Space Station and Space Shuttle Programs.

Acceptance Review A PMM Acceptance Review (PAR) shall be held at completion of PMM modification tasks under ASI responsibility to allow transfer of responsibility/ownership.

The PAR will occur after completion of the appropriate verification program.

The objectives of this review are to:

F. Confirm that the affected element areas are closed-out as defined in the BDEALS and BIVP. This will be supported by a physical configuration audit and supporting audits of engineering drawings, NCRs and HW anomalies databases. KSC engineering, KSC Quality Assurance (QA), Vehicle Integration Test Team (VITT), ISS QA, and Materials & Processes (M&P), will support these audits.

NASA will provide Certificate of Qualification (CoQ)/COA and ADP for all ISS common HW/SW used by the PMM.

NASA will conduct a similar review for NASA provided Government Furnished Equipment (GFE).

ASI responsibilities:

NASA responsibilities:

1. Participate in the Review 2 Review and assess the ASI-provided documentation, and Review Item Discrepancies (RID’s) 3 Participate in the process of issue disposition.

Incremental PAR Process An Incremental PAR Process is required to ensure updated verification closures, analysis, or configuration baseline are in place and have proper approvals prior to the installation or closeout of new or modified hardware. This incremental process will be scheduled to support the hardware processing activities schedule.

ACCEPTANCE REVIEW BOARD

NASA and ASI will co-chair the board. ASI will organize the review and prepare the review plan for NASA approval.

CERTIFICATION of Flight Readiness Review Following the acceptance of the PMM the PMM integration and certification of flight readiness will follow the Processes established for the MPLM mission. The PMM development Project will provide all data required to support the ULF5 Certification of Flight Readiness (CoFR) process to the PMM processing team.

PMM Project MEETINGS The following meetings shall be conducted in support to PMM project activities. These meetings may be conducted wholly, or in part, using network teleconferences or Video Teleconferencing System (VTS) and will normally be scheduled with at least four (4) weeks advance notice.

RECURRING Meetings and Teleconferences PMM Status and Issues Teleconference To facilitate the communication of the technical status of PMM, a regular teleconference will be held. Participating in the teleconference will be NASA, ASI and the support contractors. Other participants may participate at the concurrence of the teleconference chairpersons. The SIT will be co-chaired by the NASA PMM Project Manager and the ASI PMM Project Manager.

The objectives of the teleconference are:

C. To communicate the status of integration and test activities, D. To address test and verification issues and issues that have not been satisfactorily resolved at the subsystem level and were elevated to the Test & Verification (T&V) level, and E. To request clarification on data received and formally request missing information for closure of requirements.

The SIT will nominally be held on Tuesdays at 8:00 AM (US Central Time) and occur on a weekly basis as required. Agendas for the topics of discussion will be transmitted between ASI and NASA prior to the SIT. Topics outside the agenda may be added as required.

Decisions affecting programmatic issues such as cost and schedule are beyond the scope of the SIT and will be coordinated with ISS Project Managers through the Vehicle Control Board (VCB) as defined in this JIP.

KENNEDY Space Center Planning and Processing Meetings and Teleconferences Teleconference will be held to plan and review implementation of processing and testing requirements for PMM when at KSC. Initially the meetings and teleconferences will be scheduled as required or be part of the SIT teleconference. The KSC PMM Mission Processing Team will lead the meetings. The frequency of these meetings/teleconferences will increase as required to meet Program timelines. An agenda will be distributed prior to all meetings/teleconferences. These meeting will need support from NASA, ASI and support contractors as required by the subjects listed in the agenda.

The objectives of these meetings/teleconferences are:

A. Participation in planning detailed processes and procedures required to actively and successfully accomplish Program requirements.

B. Discuss problems and concerns related to processing and testing PMM at KSC.

C. Review team schedule and action items for PMM processing.

PROJECT SCHEDULING PROCESS

NASA and ASI will develop and control the integrated PMM system Level I schedule, covering major activities and milestones up to the turnover of the PMM. The NASA/ASI ISS Program Managers will control the Level I schedule via the appropriate board. NASA/ASI will provide an input to the PMM system schedule for integration on a quarterly basis. The inputs will include an assessment of critical path and measurement of progress for all tasks for which NASA and ASI are held accountable. These schedules will be kept until the turnover of the PMM.

NASA and ASI will develop, maintain, and control their respective PMM Level II schedules consistent with the Level I schedule. These schedules will cover the detailed activities and milestones up to the turnover of the PMM. The NASA and ASI Project Managers will monitor the schedules at the System Issues Teleconference and report status and issues to the MVCB. NASA and ASI will provide monthly status to the schedule. The status will include an assessment of the critical path and measurement of progress for all tasks for which NASA and ASI are held accountable so that consistency with the integrated PMM System Level I schedule can be monitored. All tasks owners will provide an informal status at the weekly SIT.

ENGINEERING PROCESSES

The processes described herein identify tasks necessary to perform PMM design and to integrate PMM to the Space Station. This process is interactive, requiring inputs and responses from ASI to NASA and vice-versa.

The data content and exchange required to implement the processes described in the following sections is identified in PMM BDEALS.

PMM DESIGN ENGINEERING PROCESS

NASA is responsible to perform overall systems engineering, integration, and verification of the PMM.

ASI will perform PMM system engineering, physical and analytical integration, test, verification, and acceptance to an optimized degree as determined through negotiations with NASA. ASI will support all remaining NASA responsible integration, analysis, test, verification, and acceptance activities whether performed in Italy or USA Results of these negotiations are documented in the approved BIVP and BDEALS.

NASA and ASI will utilize all the necessary engineering processes and analytical tools to perform the system verification.

SPACE station ENGINEERING integration process NASA is responsible for the overall Space Station performance and design integration. Specific system performance parameters specified for the Station as a whole, can only be satisfied by each of the station elements contributing together to meet these requirements.

NASA, as the Space Station system integrator, performs end-to-end integrated system analyses, which result in an apportionment of these parameters to PMM. ASI is responsible, through its design, development, and verification activities, to implement the ASI applicable requirements and generate associated verification evidence. The implementation activities of subject requirements will be controlled by ASI processes as per ASI documentation listed in the approved BDEALS.

NASA is responsible to integrate the results of PMM distributed requirements implementation to assess the actual overall station performance and propose options for solutions in case of performance shortcomings.

ENGINEERING ANALYSIS

NASA is responsible for the Space Station design integration and overall Space Station performance. As PMM is a segment of the Station, it contributes to the overall configuration in terms of loads, accelerations, thermal exchange, Electromagnetic Compatibility (EMC), data links, and other areas.

Therefore, the PMM functions and performance data as evolving from the design are needed as input for Station-wide engineering analysis. In return, the Station system response is needed to verify PMM, functions, and performance.

The data per discipline to be exchanged, the purpose of its use, the appropriate response, and the need dates are jointly agreed in the approved BDEALS.

SOFTWARE DEVELOPMENT PROCESS

ASI will adapt the MPLM MDM flight SW as needed for PMM purpose. The activities will consist of the modification of the source code in the development environment, of the modification of the simulation models, performing unit test on the development environment, building and loading on the MATE-4, performing the functional verification test (e.g. regression test for the modified capabilities), updating the relevant documentation and delivery to Mission Build Facility (MBF).

After the MBF delivery, the PMM software will be re-tested in the ISS Software Verification Facility (SVF), with TASI/ALTEC support, according to the procedures defined in SSP 50482.

The PMM SW will be loaded on the flight MDM at KSC using the MPLM ETSE.

KSC OPERATIONS/LOGISTICS INTEGRATION PROCESS

OPERATIONS AT KSC

MPLM FM-3 De-intégration (i.e., MLI, Y-Panels, etc.):

1. MPLM FM-3 will remain in KSC CAPPS custodial care during deintegration activities.

2. Element Rotation Stand (ERS) will be DD1149’d to ASI and MPLM FM-3 rotations will be performed by TASI/ALTEC.

3. Removal of selected hardware from MPLM-FM3, including Meteoroids and Debris Protective Shield (MDPS) panels removal, will be performed by TASI/ALTEC. TASI/ALTEC will provide the identification of part number of hardware to be removed one week prior to start of work for KSC Checkout, Assembly and Payload Processing Services (CAPPS) review.

4. Ground Safety Assessment document will be submitted by TASI/ALTEC one week prior to start of work.

5. TASI/ALTEC deintegration procedures will be submitted to NASA KSC one week prior to start of work. This allows time for procedure to be attached to the CAPPS Test Preparation Sheet (TPS), audited by Safety, and released through KSC system (including CM).

6. TASI/ALTEC will take care of properly tagging all the removed parts (including those being shipped to Torino) according to KSC instructions. Blank tags will be provided by KSC.

7. CAPPS will update the FM3 As-built Configuration List (ABCL).

8. KSC quality will not forgo the review of the TASI procedures. Quality assurance will be provided by TASI/ALTEC with NASA Quality Assurance participating as an observer.

a. NASA inspection/monitoring of hardware under the responsibility of TAS-I/ASI

i. Any concerns /observations made will be communicated to TAS-I engineering/quality as appropriate and discussed to determine if TAS-I is in agreement and willing to initiate a NCR/change as appropriate or if documentation supports hardware status and there is no concern/problem.

ii. If no agreement was reached, NASA QA will communicate informally with the local international partner (ASI) representative the concern/finding for potential resolution.

iii. If unsuccessful and determined to be of such significance as to require elevation, the issue/concern will be presented to the NASA ISS Program Representative and the Program will evaluate/pursuit formally with ASI.

iv. Review/approve all NCRs on GFE

b. NASA inspection requirements are implemented fully on TAS-I operations on hardware under the responsibility of NASA/CAPPS.

9. During de-integration, non-conformances discovered by TAS-I/ALTEC will be shared with NASA/CAPPS:

· TAS-I NCRs will be opened for non-conformances against hardware that will be transferred to them (e.g. blankets). ASI/ALTEC/TAS-I will determine if this will be done at the time of discovery or when the hardware (and CAPPS Problem Report [PR]) is turned over (DD1149) to them.

· CAPPS PRs will be opened for all non-conformances against hardware still under CAPPS responsibility, including hardware to be transferred. This may lead to some redundancy but is a contractual requirement. The redundancy is addressed below.

· Note: to avoid confusion CAPPS non-conformances should be referred to as PRs while TAS-I/ALTEC non-conformances should be referred to as NCRs.

10. Following the removal of FM3 hardware by TASI/ALTEC, a DD1149 form will be used for the “transfer of responsibility” from KSC CAPPS to ASI for the hardware required for PMM modifications.

11. As part of the DD1149 process, any open CAPPS PR’s on hardware to be turned over to ASI (e.g. blankets) will be transferred with the hardware per KSC Standard Practices and Procedures (SPP) Q-01 – “Non-Conformances System”. This transfer eliminates the PR/ NCR redundancy noted above.

· The “transfer” involves a paper copy of the PR being provided to TAS-I/ALTEC/ASI. It will have signature page.

· A signed copy of the signature page is scanned and electronically attached to the CAPPS PR. The TAS-I NCR number will be noted on the CAPPS PR, and the PR will be closed.

· TAS-I can proceed with work on the NCR. No additional work on the CAPPS PR is required and the PR does not need to be returned to CAPPS. It would be beneficial if the PR number is noted on the TAS-I NCR for traceability.

12. Hardware will be packaged and shipped by KSC to Italy as required for modifications. KSC CAPPS Logistics will provide shipping containers as required.

MPLM FM-1 Modifications:

13. MPLM FM-1 will remain in KSC CAPPS custodial care during PMM modification activities.

14. TASI/ALTEC will ship FM-3 modified hardware and new hardware from Italy to KSC with TASI/ALTEC as the recipient of the delivery (local TASI/ALTEC address at KSC). Following delivery, an identification and damage receiving inspection will be jointly performed by KSC Quality and TASI/ALTEC.

15. FM-3 modified hardware will remain in TASI/ALTEC custodial care during duration of installation activities. Following completion of installations, the FM-3 modified hardware will be DD1149’d from ASI to KSC CAPPS. New hardware delivered for PMM modifications will not be DD1149’d but will be included in the final hardware acceptance process (DD250).

16. MDPS panels will be removed/installed by KSC CAPPS.

17. Module rotations will be performed by KSC CAPPS.

18. All other MPLM FM-1 modification work, including FM1 blanket removals, will be performed by TASI/ALTEC.

19. Ground Safety Assessment document will be submitted by TASI/ALTEC no later than one week prior to start of work.

20. TASI/ALTEC installation procedures will be submitted to NASA KSC one week prior to start of work. This allows time for procedure to be attached to CAPPS TPS, insert any NASA Quality inspection requirements via pen and ink, audited by Safety, and released through KSC TAIR system (including CM).

21. Proper coordination will be needed between Flight Safety Panel and Ground Safety Panel prior to starting integration activities on the floor. KSC quality will not forgo the review of the TASI procedures. Quality surveillance will be provided by TASI/ALTEC with NASA Quality Assurance participating as an observer. NASA / Boeing CAPPS will close out the area below the MLI per SSPQ-16 and JPD-322 prior to MLI installation on a separate document.

a. NASA inspection/monitoring of hardware under the responsibility of TAS-I

i. Any concerns /observations made will be communicated to TAS-I engineering/quality as appropriate and discussed to determine if TAS-I is in agreement and willing to initiate a NCR/change as appropriate or if documentation supports hardware status and there is no concern/problem.

ii. If no agreement was reached, NASA QA will communicate informally with the local international partner (ASI) representative the concern/finding for potential resolution.

iii. If unsuccessful and determined to be of such significance as to require elevation, the issue/concern will be presented to the NASA ISS Program Representative and the Program will evaluate/pursuit formally with ASI.

iv. Review/approve all NCRs on GFE

b. NASA inspection requirements are implemented fully on TAS-I operations on hardware under the responsibility of NASA/CAPPS.

22. Non-conformances discovered by TASI/ALTEC during MPLM FM-1 hardware removal and installation tasks will be shared with NASA/CAPPS:

· TAS-I will open NCRs and resolve non-conformances for all mod kit hardware.

· CAPPS will open PRs and resolve non-conformances for all “other” module hardware (does not include mod kit hardware). CAPPS PRs are not required on mod kit hardware until after mod kit is installed and transferred (DD1149) to NASA/CAPPS.

SUSTAINING Engineering Sustaining Engineering agreements/understanding will be covered under, SSP 50200-10, the Space Station Program Implementation Plan, Volume 10: Sustaining Engineering Plan. For PMM Sustaining, a dedicated NASA/ASI bilateral Appendix to the SSP 50200-10, Vol.10 shall be developed. NASA Vehicle Office has taken the lead in the development of this Appendix with ASI.

logistics and maintenance operations Logistics and Maintenance Operations integrated processes and agreements/understandings will be covered under SSP 50200-05, the Station Program Implementation Plan, Volume 5: Logistics and Maintenance, Annex for PMM <TBD 2-1>.

This document will include the PMM support concept, NASA and ASI roles and responsibilities, and data exchange consistent with the MOU and other pertinent existing agreements (i.e., BDEALS, BHSEALS); and future agreements, like Common Spares Pool, Integrated Piece Parts Management Plan, etc.

NASA Logistics and Maintenance (L&M) will take the lead in developing along with ASI the SSP 50200-05 <TBD 2-1>.

VERIFICATION

VERIFICATION PLANNING

NASA and ASI will generate a bilaterally controlled BIVP as an appendix to the PMM PIDS. This plan will constitute the top-level verification document applicable between NASA and ASI. It will define the verification approach, management, responsibilities sharing outline per subsystem, reporting requirements for integration and verification testing activities requiring joint participation from NASA and ASI, and as a minimum, the following details for the verification of each requirement:

The PMM is derived from the ISS Multi-Purpose Logistics Module (MPLM) Flight Module which was accepted by and delivered to NASA. The PMM will make use of the previously accepted MPLM verifications to the maximum extent practical. Where necessary the verifications will be modified or new verifications developed to support the PMM Acceptance Review process. Within the PMM PIDS, a matrix will be developed to allocate the PIDS requirements verifications into two categories (A or B)to distinguish the level of PMM verification required.

Category A:

It includes those requirements which are unchanged with respect to MPLM requirements and for which the team has determined that the MPLM verification is not invalidated by the change of mission requirements and/or modifications from the PLM upgrade. Consequently, the PMM verification documentation will be limited to:

• A reference to the MPLM verification documentation.

• The verification that the existing MPLM verification documentation is not affected by the applicable documentation evolution.

In case it is shown that the ADL evolution invalidates the MPLM verification, the requirement will be considered "Category B" and delta verification documentation will be generated.

Category B:

It includes new, modified, and unchanged requirements for which new verification documentation is required. When relevant, the verification can be based, or make reference to existing MPLM verification documentation.

The BIVP will also include test sheets for integration and verification testing activities requiring joint participation from NASA and ASI. The test sheets will define the responsibilities of the parties, test venue and the support/involvement, requested by the party responsible for the requirement to the other parties.

The verification reporting requirements will cover the verification assessment, traceability, closeout, and certification.

The ASI and NASA HW, SW, Ground Support Equipment (GSE), and facilities required from each other for the execution of the respective ASI or NASA verification program are defined in the Bilateral Hardware and Software Exchange Agreements, Lists, and Schedule (BHSEALS). In general, all HW GSE is planned to be provided on a loan basis, with the providing partner maintaining the responsibility for integration, check-out and operation of the provided GSE, unless otherwise stated in the BHSEALS.