1 / 13

MSD Payload Planning Process

MSD Payload Planning Process. MSD Payload Planning Process. The ISS PO has presently defined a need for the RPOs to provide a Multi-Increment Payload Data Set to address the development and review of a Multi-Increment Manifest.

yamka
Download Presentation

MSD Payload Planning Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MSD Payload Planning Process

  2. MSD Payload Planning Process • The ISS PO has presently defined a need for the RPOs to provide a Multi-Increment Payload Data Set to address the development and review of a Multi-Increment Manifest. • GRC MSD will provide the MRPO the data on payloads in the Baselined GRC/MSD ISS Utilization Traffic Model to coincide with the needs of the ISS PO. • This information will be rolled-up to the facility level. • These payloads represent NRA approved science or commercially approved research, and have been adequately funded by the MRPO to meet a proposed flight opportunity. • Presently the Payload Planning Data System (PPDS) is the database system being used by the ISS PO, MRPO, and GRC MSD for payload planning and manifesting. • This allows electronic transfer of data between these organizations. • Due to this commonality, the integration of payload data is accurate and quick. • At a minimum, the MSD PPDS will need to be formally updated, baselined and submitted to the MRPO once per year. • For MSD’s own use, we may actually want to do this more often. • After the final Multi-Increment Data Set drop, data submittals will transition to the IA Addenda and PDL.

  3. GRC MSD Management Team (MMT) GRC MSD Discipline Teams GRC MSD Payload Planning Representative ISS MRPO Payload Developer (PD) Payload Integration Agreement SSP 57117 MSD Resource Allocation derived from available sources Operation Summary Document SSP 50112 START Approved List of Payloads Develop Payload Resource Guidelines Other Sources Yes Yes No Adjust Payload Resource Guidelines DPM Approval of P/L Resource Guidelines DPM Approval of P/L Resource Requests MMT Approval of P/L Resource Guidelines MMT Approval of P/L Resource Requests No Baseline Payload Resource Guidelines A MRPO provides PPDS Structure PD’s Data Input Generate Payload Specific Databases (no data) Approved List of Payloads Integration with MRPO PPDS PPDS placed under Configuration Management Review/Integrate data from Payload Developers Integration with other RPO’s PPDS GRC MSD Integrated PPDS Yes End Yes Planning Data Analysis: - Review PL resource request data; - Compare to PL Resource Guide; - ID areas of concern; - ID possible solutions; - Generate report PL’s Data Adjustment No No Discipline PM Review MSD Payload Planning Process Resource Guideline Process Strategic Planning

  4. MSD Payload Planning Process • Overall Process of Resource Guidelines Estimation Note: There will be NO resource allocation from the MRPO during Strategic Planning!!! • The Payload Planning Team develops a resource “guideline” for GRC payloads. • Using applicable documents, the “Planning Resource Guideline” is calculated for FCF payloads. • When approved, the Planning Resource Guideline information will be provided to Discipline Program Managers (DPM) as guide in payload resource requirement development. • General Assumptions used in Resource Guidelines Estimation • The calculation will be based on the following assumption: • NASA gets 78.9% of the overall utilization resources at Assembly Complete; • per the 30/30/30/10 Assembly Complete resource allocation directive; 30% of NASA utilization resources will be allocated to the Microgravity Research program (MRP). • On a straight allocation basis: • the MRP should receive 30  0.789 = 23.7% of overall ISS utilization resources; • the MSD should expect to receive 2/5th (two disciplines out of five) of the MRP allocation or 9.5%of the overall ISS utilization resources, or 12% of NASA utilization resources.

  5. Note: This information is not the rolled-up result of verified payload data! MSD Payload Planning Process

  6. MSD Payload Planning Process When:

  7. MSD Payload Planning Process When: Rev E. - DCN-04

  8. MSD Payload Planning Process When: CIR Rev E. - DCN-04

  9. MSD Payload Planning Process When: FIR Rev E. - DCN-04

  10. MSD Payload Planning Process What:

  11. Traffic Modeler Provided by the ISS Supporting Files (PL provided) Payload Parameters Station Resources Characterize payload resource requirements • Resource availability per stage*: • Avg. Power, Crew Time, Volume on-orbit, Upmass, etc. *stage is a period from the docking of Flight N to the docking of Flight N+1 MSD Payload Planning Process How: Payload Planning Data System (PPDS) Philosophy

  12. MSD Payload Planning Process • Software Tool Payload Planning Data System (PPDS) in FileMaker Pro • A tool used to quickly develop PL traffic and operation models • Report generation capability • Looks at resource usage • Data fields correspond to PIA/Increment Unique Addendum data fields • Database tool for ISS payload planning • Information can be updated quickly and easily • Currently used by OZ (a.k.a. Mission Integrated Payload Planning System - MIPPS): • OZ4 (N. Penley - RPWG) - Planning and Manifesting • OZ2 (J. Scheib - PMIT) - Manifest change evaluation

  13. MSD Payload Planning Process • Report Layouts generated by the PPDS • RPO resources by stage & Summary • Facility resources by stage & Summary • Facility CY resource Summary (roll-up only per facility) • Planning Period resource Summary • Manifests (P/U, Ascent/Descent, p/l @ risk) • Crew Training Requirements • OFA (Payload on-orbit resource requirements by stage vs availability with margins) • Payload activity Summary • Traffic Models (by year, by Planning Period, by developer) • Payload count

More Related