MD_1036_RA_FINAL_PIP_Charter.docx

DOCX document 203 KB Posted

Attached to
Human Space Flight Technical Integration Contract (HSFTIC) Federal contract opportunity
Solicitation number
80JSC019R0023
Issued by
National Aeronautics and Space Administration Johnson Space Center

About this file

This charter establishes the International Space Station Payload Integration Panel. The Panel is responsible for the technical integration of payloads for the ISS Program. It defines integration processes, coordinates schedules and reviews, manages issues, and maintains integration documents like the Integrated Payload List. The Panel reports to the Research Integration Control Board. Members include representatives from payload development, operations, engineering, safety, and research organizations. The charter delegates authority to the Panel to approve changes to documents within its defined scope and resolve issues, with an appeal process to the Board.

The solicitation seeks proposals for the Human Space Flight Technical Integration Contract to provide technical integration support for NASA's Johnson Space Center. It is a total small business set-aside, with a NAICS code of 541715 and size standard of 1,250 employees. The anticipated RFP release is November 1, 2019, with proposals due December 11, 2019. Offerors should monitor the website for the solicitation. Questions must be submitted in writing only.

MD 1036 RA FINAL PIP Charter

View the file

Other files for this federal contract opportunity

Other files attached to Human Space Flight Technical Integration Contract (HSFTIC), newest first.
File Type Posted
FRFP Industry Questions and Responses 120419.pdf PDF
HSFTIC L Instructions 11.22.19 FRFP-2.docx DOCX document
Attachment L-7 Cost Estimating Wookbook 11.21.19 FRFP-2.xlsx XLSX spreadsheet
SF30 - RFP - Amendment 2.pdf PDF
Attachment L-6 EPM Workbook 11.21.19 FRFP-2.xlsx XLSX spreadsheet
Attachment L-6 EPM Workbook MOD FRFP-1.xlsx XLSX spreadsheet
80JSC019R0023 HSFTIC RFP with MOD FRFP-1.docx DOCX document
HSFTIC Pre-Proposal Conference - Posting.pdf PDF
Attachment_L-7_Cost_Estimating_Workbook.xlsx XLSX spreadsheet
80JSC019R0023_Request_for_Proposal.pdf PDF
APA_Style_Website_Ref.pptx PPTX presentation
SSP_50821.doc DOC document
CR_16052_ATTA_SSP_54353_54354_Baseline.docx DOCX document
MD_106_RB_FINAL.docx DOCX document
SSP_50869-Rev_A.docx DOCX document
SSP-57003_Rev_L.docx DOCX document
MD_1054_PSCB_Charter.pdf PDF
SSP_30234-RevH.docx DOCX document
SSP_42007-Part_1-RevK.pdf PDF
SSP_50318_RevJ.docx DOCX document
SSP_41162BA.pdf PDF
SSP41148_IRN.pdf PDF
BASEPLATE-Mobile_Back-1.png PNG image
SSP_50908-Baseline.docx DOCX document
CCT-REQ-1130_Rev_F.docx DOCX document
50104a.pdf PDF
SSP-50136_RevA.doc DOC document
SSP_50420-HTV1-Baseline.docx DOCX document
Applicable_1.zip ZIP file
OrionProgramOrg.pdf PDF
SSP_42004_Part_2-Update_to_Cover.pdf PDF
SSP_50333-RevH.docx DOCX document
SSP_50406_Rev_B_.doc DOC document
MD_1034_RA_FINAL_2__RICB_Charter.docx DOCX document
SSP_42004_Part_1_Revision_L.docx DOCX document
SSP_50128-C3.doc DOC document
GRA_for_Gateway.xlsx XLSX spreadsheet
SSP_41140_P1_RF_final.pdf PDF
SSP_50182.RTF RTF text file
41004P1_H-1.pdf PDF
SSP_50627-RevA.docx DOCX document
SSP-50264.doc DOC document
19AA0613D_MAPI_Abstract_Blue_Book_Rev_EE.pdf PDF
SSP_42000-RevU.docx DOCX document
SSP50251P2.pdf PDF
Applicable_2.zip ZIP file
SSP_57000_Revision_S.docx DOCX document
SSP_50035_Revision_C_Retired.docx DOCX document
DRAFT_HSFTIC_Cover_Letter.pdf PDF
DRAFT_HSFTIC_Work_Load_Indicators.xlsx XLSX spreadsheet
Show all 50

Human Space Flight Technical Integration Contract (HSFTIC) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Management Directive

ISS MD 1036_Rev A

TO: Distribution

SUBJECT: Charter for the Payload Integration Panel (PIP)

OFFICE OF PRIMARY RESPONSIBILITY: ISS Research Integration Office

1.0 PURPOSE

This charter establishes the International Space Station (ISS) Program Payload Integration Panel (PIP). The PIP is the primary forum for the community-wide technical integration of ISS Program payloads.

2.0 SCOPE

This document defines the scope of program authority and document control delegated to the PIP, the Panel membership, and specific operating policies.

3.0 POLICY

The PIP is responsible for reporting issues and resolution plans to the Research Integration Control Board (RICB) when problems associated with technical integration and/or delivery for launch of payloads are identified. The PIP continuously ensures that issues impacting payload technical integration are communicated to the stakeholder organizations and that resolution plans are coordinated across the stakeholder community.

3.1 Meeting Frequency

PIP meetings are normally held weekly with additional meetings scheduled by the Panel Chair, as required.

3.2 Responsibilities

The PIP defines, coordinates, and controls payload technical integration process documents and integrated schedules. Proposed updates to processes and schedule templates will be assessed with the stakeholder community including the affected Payload Developers prior to baselining.

The PIP baselines and manages Payload Integration Manager (PIM) schedules, tracks progress, resolves cross-cutting integration issues, and prepares reports for ISS Program Forums. The PIP will baseline and manage each payload-specific schedule based on the hardware delivery and Certification of Flight Readiness (CoFR) milestones required to fly on the target launch vehicle as specified by the RICB.

The PIP maintains the Integrated Payload List (IPL). The PIP is responsible for ensuring the IPL is maintained in alignment with the RICB direction.

The PIP develops, integrates, and approves Payload Integration Agreements (PIAs). Completed PIAs are submitted to the RICB Chair for final approval to baseline.

The PIP integrates across the payload community to use program-wide resources to meet research integration needs while continuously focusing on maximizing the amount of research being performed on ISS. The PIP assesses technical feasibility and operations concepts early in the lifecycle, conducts trade studies, coordinates ISS Program support for payload technical reviews and technical interchange meetings, identifies programmatic issues and limitations adversely affecting the ability to effectively support the needs of the research community and identifies programmatic strategic investment opportunities.

3.3 Authority

Authority is delegated from the RICB to the PIP as specified in the following paragraphs. Changes to this authority will be reflected in updates to this charter. The PIP has authority to approve all other changes within the scope of this charter.

3.4 Product Control

The PIP has the authority to disposition change requests for documents under ISS baseline control, which are within the authority granted in this charter. The RICB has delegated documentation control to the PIP. The following are the delegated documents and Technical Integration Products from the RICB.

· Integration Payload List (IPL)

· Payload Integration Manager Schedules

· Payload Integration Agreements (PIAs)

· SSP 57057, ISS Science, Technology, and Exploration Integration (ST&E) Flow Website Data. This includes:

· ST&E Integration Flow Swimlane Diagrams [ISS Program and Payload Developer (PD)]

· ST&E Integration Flow Charters

· ST&E Integration Flow Task and Milestone Definitions and Chronology Tables (TMDCTs) (ISS Program and PD)

· ST&E Integration Flow Documentation Update Process

· ST&E Integration Flow Documentation Update Form

· SSP 57072, Standard PIAs for ISS Payloads

· SSP 57061, Standard PIA for Unpressurized Payloads

· SSP 52000-PDS, Payload Data Sets Blank Book

3.5 Member Coordination

The PIP is not a multilateral forum. Payload issues and requirement changes that require formal coordination between NASA and IP/P representative(s) will be addressed at the Multilateral Research Integration Control Board (MRICB).

3.6 Appeal

The PIP shall make every attempt to make decisions by consensus. If consensus cannot be reached, the Chair shall make a decision. Any PIP member can appeal the decision to the RICB. The dissenting member and the PIP Chair will present the tenets of the issue to the RICB. If the decision is time critical, the PIP decision may be implemented at risk while the appeal is proceeding. An appeal must be submitted within 2 weeks following the PIP decision. If a member appeals a decision, that member may elect not to implement the Chair’s decision until the RICB resolves the appeal.

4.0 MEMBERSHIP

Chair:

Manager, Research Integration Management Office, ISS Program

PIP Members:

Representative, Payload Integration Manager Representative, Vehicle Office Representative, Mission Integration and Operations Office Representative, Avionics and Software Office Representative, Systems Engineering and Integration Office Representative, Transportation Integration Office Representative, Human Health and Performance Representative, ISS Chief Engineer Office Representative, Payload Operations Integration Ad Hoc Members :

Ad hoc members will attend the PIP meetings based upon the agenda, to provide information on payload mission integration activities, hardware and software development activities, and schedule milestones.

Representative, Payload Developers Representative, Flight Payload Managers Representative, ISS Research Planning Office Representative, Flight Operations Directorate Representative, Extravehicular Activity Office Representative, External Integration Office Representative, Human Research Program Representative, Safety and Mission Assurance/Program Risk Representative, Payload Support Systems Representative, ISS Technology and Science Research Office Representative, ISS Commercial Space Utilization Office Representative, Center for the Advancement of Science in Space Representative, Commercial Crew Program Representative, Cargo Mission Contract

MD_1036_RA_FINAL

image1.png image2.jpeg

File details come from the government source that posted it. Updated .