# Presentation: 425532

## 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.
- 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.

## MSD Payload Planning Process

**Resource Guideline Process**

**Strategic Planning**

## 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.

_**	**__**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.

_***MSD Payload Planning Process***_

## MSD Payload Planning Process

## MSD Payload Planning Process

_***MSD Payload Planning Process***_

_***When:***_

## MSD Payload Planning Process

_***When: Rev E. - DCN-04***_

## MSD Payload Planning Process

_***MSD Payload Planning Process***_

_***When: CIR ***__***Rev E. - DCN-04***_

## MSD Payload Planning Process

_***MSD Payload Planning Process***_

_***When: FIR ***__***Rev E. - DCN-04***_

## MSD Payload Planning Process

_***What:***_

## MSD Payload Planning Process

**Payload Planning Data System (PPDS) Philosophy**

_***How:***_

## 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

- 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

_***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  

- 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

_***MSD Payload Planning Process***_