Program Management for Concurrent University Satellite Programs, Including Propellant Feed System Design Elements

Withrow, Shannah Nichole

关键词: AEROSPACE ENGINEERING;    CUBESATS;    DESIGN ANALYSIS;    ENERGY REQUIREMENTS;    FEED SYSTEMS;    LESSONS LEARNED;    PAYLOADS;    PROJECT MANAGEMENT;    RESEARCH AND DEVELOPMENT;    RISK MANAGEMENT;    STANDARDIZATION;    SYSTEMS ENGINEERING;    TECHNOLOGY UTILIZATION;   

RP-ID  :  NASA/TM-2019-220155,ARC-E-DAA-TN66828

美国|英语

来源: NASA Technical Reports Server

【 摘 要 】

Propulsion options for CubeSats are limited but are necessary for the CubeSat industry to continue future growth. Challenges to CubeSat propulsion include volume/mass constraints, availability of sufficiently small and certified hardware, secondary payload status, safe storage of high energy, and power requirements. A multi-mode (chemical and electric) thruster was developed by at the Missouri University of Science and Technology (Missouri S&T) to enable CubeSat propulsion missions. Two satellite buses, a 3U and 6U, are being developed by the M-SAT satellite research team at Missouri S&T to demonstrate the multi-mode thruster's capabilities. Two key challenges related to these missions are the development of the feed system to support the thruster and management of the two programs' personnel, resources, timelines, and budgets. The feed system was designed to support the unique needs of the thruster including material compatibility with the custom ionic liquid, variable flow rate, high pressurization, and high voltage within the constraints and budget of a student-designed propulsion system. The feed system was also designed to minimize risk as a secondary payload. This resulted in the development of a unique method to pressurize propellant stored in the feed system tubing. Within the expected operating pressure range, the method was experimentally shown to provide sufficient pressure and propellant volume to the thruster to meet mission success criteria. The 3U and 6U CubeSat buses were designed concurrently with complimentary payloads, hardware, objectives, and team structures. Resources such as personnel, lab space, and time had to be carefully balanced between the two teams. With proper management, the two programs have been able to support one another, providing valuable insight and collaboration between the two teams. Lessons learned include experience with design, testing, and assembly of hardware, team training/mentoring and motivation, improved documentation practices, and risk management.