Session
Technical Session II: Advanced Operations Concepts
Abstract
The IPOS approach recognizes that the real problems in achieving schedule, cost, and science return for PI class missions can only be dealt with by re-examining the basic architecture of payload and satellite systems. We must re-evaluate how they are built, integrated and operated. Reducing integration time and risk, lowering operations cost while increasing science return are absolutely necessary for today's new, low cost, fast turn-around missions. IPOS is systems engineered to match an innovative architecture with both an implementation methodology and enabling technologies. These are designed with recognition of the pitfalls that have historically been problems in satellite/payload integration, providing features that enable the PI to focus resources on development of the science instruments. IPOS is scaleable and targeted toward the UNEX, SMEX, MIDEX and Discovery class missions with a single responsible PI. It is designed to make it practical for the PI to integrate their payload with existing S/C or to "buy a ride" on commercial class vehicles. To achieve these objectives, IPOS defines the entire science payload as a single "PI instrument" making integration with the SIC simpler, and giving the PI control of the entire payload both during development and throughout the mission. IPOS achieves low cost and reliability by using an enabling software bundle called the End-to-End Mission Operations System or "EEMOS" and hardware technology already developed by NASA, DoD, and the commercial sector. IPOS provides each of the Co-I instrument developers with power, command/data, and thermal control, plus enhanced centralized science data processing. IPOS is not simply another integrated payload, it is system engineered be an "end-to-end" set of services, and designed to give the user flexibility in its implementation without redesign. It can be configured for a variety of missions from simple to complex, with soft to hard environmental requirements, and with simple to redundant implementations.
An Integrated Payload Development and Operations System (IPOS) for PI Class Missions
The IPOS approach recognizes that the real problems in achieving schedule, cost, and science return for PI class missions can only be dealt with by re-examining the basic architecture of payload and satellite systems. We must re-evaluate how they are built, integrated and operated. Reducing integration time and risk, lowering operations cost while increasing science return are absolutely necessary for today's new, low cost, fast turn-around missions. IPOS is systems engineered to match an innovative architecture with both an implementation methodology and enabling technologies. These are designed with recognition of the pitfalls that have historically been problems in satellite/payload integration, providing features that enable the PI to focus resources on development of the science instruments. IPOS is scaleable and targeted toward the UNEX, SMEX, MIDEX and Discovery class missions with a single responsible PI. It is designed to make it practical for the PI to integrate their payload with existing S/C or to "buy a ride" on commercial class vehicles. To achieve these objectives, IPOS defines the entire science payload as a single "PI instrument" making integration with the SIC simpler, and giving the PI control of the entire payload both during development and throughout the mission. IPOS achieves low cost and reliability by using an enabling software bundle called the End-to-End Mission Operations System or "EEMOS" and hardware technology already developed by NASA, DoD, and the commercial sector. IPOS provides each of the Co-I instrument developers with power, command/data, and thermal control, plus enhanced centralized science data processing. IPOS is not simply another integrated payload, it is system engineered be an "end-to-end" set of services, and designed to give the user flexibility in its implementation without redesign. It can be configured for a variety of missions from simple to complex, with soft to hard environmental requirements, and with simple to redundant implementations.
