Safety_TIM_2_UZ.pdf
PDF 748 KB Posted
- Attached to
- Commercial Low Earth Orbit (LEO) Development Program Phase 2 Requirements and Safety Technical Interchange Meeting Federal contract opportunity
- Solicitation number
- 80JSC025REQ_SAFETY_TIM
About this file
This is a presentation file detailing the Commercial LEO Development Program (CLDP) Utilization team structure, roles, and integration processes. The presentation outlines the CLDP Utilization Integration Plan, which follows a six-phase approach from Early Integration through Utilization Objective Completion, covering payload processing, operations readiness, launch, and on-orbit operations.
The document defines key team roles at both JSC and MSFC locations, including the Payload Process Lead, CLD User Representatives, Interface Leads, and operations positions like PAYCOM and Research Action Manager. It establishes three main governance bodies: the Payload Research and Operations Control Board (PRO-CB) for high-level decisions, the Payload Integration Panel (PIP) for tracking integration status, and the Research Planning Working Group (RPWG) for establishing utilization priorities. The presentation indicates all content is draft and subject to change before final RFP release, with a date reference of 6/11/2024.
View the file
Other files for this federal contract opportunity
Show all 24
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
COMMERCIAL LEO
D E V E L O P M E N T P R O G R A M
CLDP Utilization Current Plans & Expectations
CLDP UZ – J. Curry / J. McMillian / J. Carlson / K.
Neiss / K. Costello
Welcome to the CLDP Utilization Team People to know:
Kirt Costello, Ph.D.
Utilization Manager
Ken Neiss Deputy Mgr
Jessica Curry Payload Process Lead
Jennifer McMillian Payload Ops Lead
Johnathan Carlson Utilization Analyst
P R O G R A M
CLDP Utilization Integration Plan Overview
All content is considered draft and subject to change prior to final RFP release.
P R O G R A M
Key Integration Roles of CLDP Utilization Team
• JSC
• Payload Process Lead – Develops Payload Integration Lifecycle Flow and manages increment payload integration processing to ensure complement is on track. Chairs the Payload Integration Panel (TBC), and oversees CLD User Reps.
• CLD User Rep – Manages payload integration portfolio for a given CLD provider. Acts as the programmatic interface between the payloads team (PD/PI), science sponsor, Institute, CLD provider, and CLDP. Roughly equivalent to the role of an ISS Research Portfolio Manager.
• External Payload Interface Lead – CLDP expert on the CLD provider(s) external payload interfaces and capabilities, and assists both feasibility assessments and integration-related questions/actions.
• Pressurized Payload Interface Lead – CLDP expert on the CLD provider(s) pressurized payload interfaces and capabilities, and assists both feasibility assessments and integration-related questions/actions.
All content is considered draft and subject to change prior to final RFP release. 4
P R O G R A M
Key Integration Roles of CLDP Utilization Team
• MSFC
• Payloads Communicator (PAYCOM) – Payload Communicator present for real-time execution of NASA payloads, to ensure that the proper support and instructions/information is passed up to the crew. performing the investigation, and that the proper onboard information is communicated down to the utilization team.
• Research Action Manager (RAM) – The Research Action Manager is the real-time interface to utilization operations on the CLDs. This position participates in real-time mission planning and replanning, and is the real-time interface between the CLD Program and the Commercial Provider for utilization. This position also is the interface between the CLD Program and the Institute/science sponsors, and reports back to the CLD Program on statuses and actuals.
• Payload Operations & Procedures Specialist (POPS) – Works with the payloads team to develop operations products to support the successful execution of utilization activities, and supports real-time operations to guide the ground teams and crew through the activities as the NASA operations expert.
All content is considered draft and subject to change prior to final RFP release. 5
P R O G R A M
CLDP Utilization Boards/Panels/Working Groups
• Payload Research and Operations Control Board (PRO-CB) – The CLDP PRO-CB is responsible for establishing schedule, mission requirements, and processes related to integration and on-orbit operation of payloads. The board will provide a place for decisions about science and technology issues that arise across all phases of research implementation on CLDs.
• Payload Integration Panel (PIP) – The CLDP PIP is responsible for tracking detailed integration status of individual payloads and the complement of payloads that NASA is sponsoring to a CLD. The PIP will work to ensure appropriate resources and focus are on the payloads as they near key mission milestones. The PIP will also track mission milestones and ensure the community is aware of those dates or any modifications. The topics will be discussed and a recommendation elevated to the PRO-CB for decision.
• Research Planning Working Group (RPWG) – The CLDP Resource Planning Working Group (RPWG) works to identify a consensus on utilization tactical priorities and an implementation plan for the NASA allocation. If consensus cannot be achieved at the CLDP RPWG, the issue will be referred to the CLDP PRO-CB for a decision.
All content is considered draft and subject to change prior to final RFP release. 6
P R O G R A M
Questions?
6/11/2024 All content is considered draft and subject to change prior to final RFP release. 7
| CLDP Utilization Current Plans & Expectations |
| Welcome to the CLDP Utilization Team |
| CLDP Utilization Integration Plan Overview |
| Key Integration Roles of CLDP Utilization Team |
| Key Integration Roles of CLDP Utilization Team |
| CLDP Utilization Boards/Panels/Working Groups |
| Questions? |
File details come from the government source that posted it. Updated .