No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Utilizing virtual missions to achieve real operations savings
Abstract
As part of the Constellation Program, the National Aeronautics and Space Administration (NASA) began preparation for a simulated Ares I/Orion mission to the International Space Station (ISS). Designated as Virtual Mission 1 (VM-1), it simulated the integration milestones and successfully executed a crew rotation mission, culminating with a “launch” on June 19, 2009 and a “splashdown” of the returning Orion capsule a few weeks later. The accomplishments of this activity were significant in that a baseline schedule as well as many of the operations activities and integrated products were identified and developed by a small, focused group across NASA. This group was selected to leverage the operations expertise gained from the Space Shuttle, ISS and other NASA programs. By using legacy systems and processes, the Constellation Program cost-effectively prepared for early missions. A small number of these virtual missions were scheduled prior to the first actual mission in order to improve the mission development process. The theory was as the vehicle design and mission objectives matured the mission operations concept would mature; therefore, the Constellation Program could take advantage of the lessons learned during the virtual missions to reduce life-cycle costs and risks. Concentrating on the Marshall Space Flight Center (MSFC) Ares I launch vehicle tasks, the authors, working in close coordination with design engineers, proposed integration schedules, operations tools, products, and analyses to give: 1) a smart estimate of the operational tasks required to integrate and fly a real mission and 2) ways to achieve real cost savings in the operational phase. This paper describes the virtual mission integration schedule, requirements and deliverables developed for the Ares I vehicle. It also describes several off nominal events simulated as part of VM-1. The paper concludes by assessing the virtual mission concept and suggesting ways to ma ke it even more effective.
Cloud computing solutions are increasingly adopted by companies and government from several sectors of the economy. In this scenario, the choice of cloud solutions can occur either by hiring an external service (public or community cloud) or by creating an own cloud to provide services only for this institution (private cloud). Even though the cloud technology does bring some interesting benefits for its users, the security aspects related to cloud computing solutions are not always fully understood before hiring such service or even during its operation. The goal of this document is, building on theoretical research and practical experience, to present the main security issues related to cloud computing. We review the main concepts of cloud computing, focusing the discussion on the key issues and safety standards specific to this scenario. Finally, aiming to illustrate how this body of knowledge can be used in practice, we present a case study in which we analyze the API communications on the OpenStack Havana solution.
The United States (U.S.) is charting a renewed course for lunar exploration, with the fielding of a new human-rated space transportation system to replace the venerable Space Shuttle, which will be retired after it completes its missions of building the International Space Station (ISS) and servicing the Hubble Space Telescope. Powering the future of space-based scientific exploration will be the Ares I Crew Launch Vehicle, which will transport the Orion Crew Exploration Vehicle to orbit where it will rendezvous with the Altair Lunar Lander, which will be delivered by the Ares V Cargo Launch Vehicle (fig. 1). This configuration will empower rekindled investigation of Earth’s natural satellite in the not too distant future. This new exploration infrastructure, developed by the National Aeronautics and Space Administration (NASA), will allow astronauts to leave low-Earth orbit (LEO) for extended lunar missions and preparation for the first long-distance journeys to Mars. All space-based operations — to LEO and beyond — are controlled from Earth. NASA’s philosophy is to deliver safe, reliable, and cost-effective architecture solutions to sustain this multi-billiondollar program across several decades. Leveraging 50 years of lessons learned, NASA is partnering with private industry and academia, while building on proven hardware experience. This paper outlines a few ways that the Engineering Directorate at NASA’s Marshall Space Flight Center is working with the Constellation Program and its project offices to streamline ground operations concepts by designing for operability, which reduces lifecycle costs and promotes sustainable space exploration.
The Ares I is a shuttle-derived two-stage launch vehicle. The Ares I is comprised of a first stage, which is a five-segment reusable solid rocket booster, and a second stage, or upper stage, which is a liquid oxygen/liquid hydrogen rocket system powered by a single J-2X engine. The operational goal for this launch vehicle is to reduce operating costs and increase system reliability for human missions to the International Space Station and to the Moon. The Ares I will be designed to accommodate efficient operations for the ground and ascent phases of the mission by both the Ground Operations Project and the Mission Operations Project, respectively. This paper provides an overview of the latest Ares I architecture, operations goals, and the operational concepts for both the ground operation and mission operation phases of the launch vehicle. The latest concepts for the Ares I communication and tracking, engineering support, system integration laboratory, operational infrastructure, logistical support, flight and ground operational planning and execution, training, and sustaining engineering are also addressed. The integration of these across the Ares I system, as well as ongoing trades that may impact the design, are examined as well. The operational scenarios for the Ares I element assembly, integration and testing, transportation, prelaunch operations, launch and ascent operations, and post-mission operations are discussed, along with a status of the contingency and off-nominal operations scenarios. Operational concepts drive operations requirements, which drive optimized operations attributes into the design. These operations attributes in the design—‘design for operability’ —ensure that the launch vehicle can be operated in an efficient and cost-effective manner, at minimum risk of loss of crew or mission, and are characterized by high levels of safety, producibility, reliability, maintainability and supportability. The degree to which the design is imbued with the attributes will be manifested in the system readiness, launch availability, and affordability of the integrated vehicle, all of which are governed by Ares I operations requirements.
As part of the Constellation Program, engineers at NASAs Marshall Space Flight Center in Huntsville, Alabama are working to design and build the Ares I, the first of two large launch vehicles to return humans to the Moon and beyond. A deliberate effort was made to ensure a high level of operability in order to significantly increase safety and availability as well as reduce recurring costs of this new launch vehicle. It was the Ares Project's goal to instill operability as part of the requirements development, design and operations of the vehicle. To support this intent, the Constellation Program defined NASA Needs, Goals, and Objectives (NGO) encapsulating project direction to optimize the vehicle design for efficiencies in production, operations, testing and maintenance. The NGOs provided the framework for “Operability” requirements and design guidance for operable influences regarding the vehicle. This paper documents the past and current design phases and the supporting processes, tools, and methodology for designing operability into the Ares I Launch Vehicle. The content addresses the key operability requirements, system readiness activities, international launch vehicle benchmarking activities, operability assessments, and lessons learned. We discuss the interrelationships within the Ares I Project organization as well interdependencies with the Constellation Program. Based on lessons learned, the last section of this paper will describe proposed organizational and process improvements, and tool enhancements for future projects/programs.
Constellation Program Virtual Mission 1 Summary Report
- D Stapleton
Constellation Program Virtual Mission 1 Ares Project Final Report
- C Cruzen
- G Cartee
- J Wade
- J Wittenstein