4 - Notional Payload Life Cycle and Examples.pdf

Early Integration

Initial payload resources estimated on CLDS

Initial payload facility throughput estimated

Non‐standard payload needs identified

Initial increment utilization content defined

Design and Analyze

Increment task order placed on contract

Manifest, inflight stowage, and operational volume assessed

Preliminary flight/mission assigned

Applicable safety and engineering requirements and verifications documented and testing scheduled

Operational products identified and drafted based on mature ops concept

Individual payload schedule

Planning for return/disposal

Operations Readiness

Publication of planning, crew/ground procedures, flight rules, provider to user communication protocols, topology, exceptions

Hardware/software testing (engineering and safety), ground configuration testing

Safety and engineering verifications submitted and closed

Crew/ground and in‐flight training published. Pre‐ flight training complete.

Certification of flight readiness (CoFR)

Turnover and Launch

Hardware/software delivered

Hardware/software received, appropriate personnel and processes available for sample handling (e.g. radioactive material, narcotics)

Launch/ascent vehicle

– monitor vehicle environmental data

In‐Flight Operations

Activation checkout operations

Re‐planning that impacts NASA priorities or ability to complete science (Executing Priorities)

Hardware and software logistics, preparing facilities

Anomaly Response and resolution for NASA payloads or facilities /capabilities required by NASA payloads

Science Objective Completion

Payload return prep or In‐flight disposal

Return to Earth – monitor vehicle environmental data

Payload return to

PD/PI

Publish results

Track results, create metrics, communication

DRAFT Payload Lifecycle 1-pager: Notional Stages and Tasks

6/11/2024 3 All content is considered draft and subject to change prior to final RFP release.

Early Integration

Initial payload resources estimated on

CLDS

‐ NASA

Initial payload facility throughput estimate

‐ NASA

Non‐standard payload needs identified

‐ NASA

Initial increment utilization content defined ‐ NASA delivers to

Provider

Design and Analyze

Increment task order placed on contract ‐ Provider and NASA

Manifest, inflight stowage, and operational volume assessed

‐ Provider

Preliminary flight/mission assigned ‐ Provider and NASA

Applicable safety and engineering requirements and verifications documented and testing scheduled

‐ Provider and PD/PI with NASA support

Operational products identified and drafted based on mature ops concept

‐ Provider with PD/PI/NASA support

Individual Payload schedule ‐ Provider and PD/PI

Planning for return/disposal ‐ Provider and NASA

Operations Readiness

Publication of Planning, Crew/Ground procedures, Flight Rules, provider to user communication protocols, topology, exceptions ‐ Provider with NASA support

Hardware/software testing (engineering and safety), ground configuration testing ‐ Provider, PD/PI, and

NASA

Safety and engineering verifications closed

‐ Provider, PD/PI, and NASA

Crew/Ground and in‐flight training published. Pre‐ flight training complete.

‐ Provider and PD/PI with

NASA support

Certification of Flight Readiness (CoFR) ‐ Provider with NASA support

Turnover and Launch

Hardware/software delivered ‐ PD/PI with NASA support

Hardware/software received, appropriate personnel and processes available for sample handling (e.g. radioactive material, narcotics)

‐ Provider with NASA support

Launch/ascent – monitor vehicle environmental data

‐ Provider and PD/PI with NASA support

In‐Flight Operations

Activation checkout operations ‐ Provider and PD/PI with NASA support

Re‐planning that impacts NASA priorities or ability to complete

‐ Provider and NASA

Hardware and software logistics, preparing facilities

‐ Provider with NASA support

Anomaly Response/Resolution for NASA payloads or facilities/capabilities required by NASA payloads ‐ Provider and PD/PI with NASA support

Science Objective Completion

Payload return prep or In‐flight disposal ‐ Provider with PD support

Return to Earth – monitor vehicle environmental data

‐ Provider and PD/PI with NASA support

Payload return to PD ‐ Provider with PD support

Publishing results

‐ PD/PI

Track results, create metrics, communication

‐ NASA

DRAFT Notional Payload Lifecycle 1-pager: NASA Payload in a CLD Payload Facility

Text highlighted in teal denotes NASA safety engagement

6/11/2024 18All content is considered draft and subject to change prior to final RFP release.

Human Research “Early Integration”

Experiment Feasibility Assessment, Definition, IRB approval

• Amount of time depends on study complexity

• This must be done prior to being included in an

ICB.

• PI obtains IRB approval

Pre‐ICB Work: Working Group of all Payload Developers (PDs) requesting Human Research

• All PDs discuss planned research and possible conflicts for upcoming mission

• Potential combinations of experiments (complement scenarios) are developed that do not conflict or exceed resources such as post‐flight duty day and blood volume limits

Initial ICB (At L‐12 to 13 months)

• Crew receives ICB on all human research experiments planned for the increment

• Crewmembers provide interest surveys

Approval of Individual Crew Complements (At L‐12 to 11 months)

• Takes into account both crew interests and priorities

Text highlighted in teal denotes NASA safety engagement

IRB = Institutional Review Board ICB = Informed Consent Briefing

Example additional “Early Integration” considerations for any spacefaring human participating in a human research investigation

DRAFT Human Research Investigation Considerations

6/11/2024 24All content is considered draft and subject to change prior to final RFP release.