Space vehicle electrical system Patent
Electrical power system for space flight vehicles operating over extended periods
SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Electrical power system for space flight vehicles operating over extended periods
The functional requirements for the Flight Operations Processor are defined. The Flight Operations Processor is that element of the Consumables Management System providing support during the flight operations.
In September 1975, the Goddard Space Flight Center operated a short pulse radar during ocean wave measuring experiments off the coast of West Germany in the North Sea. The experiment was part of JONSWAP-75. The radar system and operations during the experiment are described along with examples of data.
The fourth Space Shuttle flight is summarized. STS certification as operational, applications experiments, experiments involving crew, the first Getaway Special, a lightning survey. Shuttle environment measurement, prelaunch rain and hail, loss of solid rocket boosters, and modification of the thermal test program are reviewed.
This handbook is intended to assist users of the Spacelab/Space Transportation System by providing contamination environments and effects information that may be of value in planning, designing, manufacturing, and operating a space flight experiment. A summary of available molecular and particulate contamination data on the Space Transportation System and its facilities is presented. Contamination models, contamination effects, and protection methods information are also presented. In addition to contamination, the effects of the space environments at STS altitudes on spacecraft materials are included. Extensive references, bibliographies, and contacts are provided.
This booklet is mainly a recruitment tool for the various NASA Centers. This well illustrated booklet briefly describes NASA's mission and career opportunities on the NASA team. NASA field installations and their missions are briefly noted. NASA's four chief program offices are briefly described. They are: (1) Aeronautics, Exploration, and Space Technology; (2) Space Flight; (3) Space Operations; and (4) Space Science and Applications.
This paper describes a generic, C++ version of the Planning and Resource Reasoning (PARR) shell which has been developed to supersede the C-based versions of PARR that are currently used to support AI planning and scheduling applications in flight operations centers at Goddard Space Flight Center. This new object-oriented version of PARR can be more easily customized to build a variety of planning and scheduling applications, and C++ PARR applications can be more easily ported to different environments. Genetic classes, constraints, strategies, and paradigms are described along with two types of PARR interfaces.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
This paper focuses on new and innovative software for remote, autonomous, space systems flight operation, including distributed autonomous systems, flight test results, and implications and directions for future systems.
A presentation is provided to demonstrate the interoperability between two space flight Mission Operation Centers (MOCs) and to emulate telemetry, actions, and alert flows between the two centers. One framework uses a COTS C31 system that uses CORBA to interface to the local OTF data network. The second framework relies on current Houston MCC frameworks and ad hoc clients. Messaging relies on SM and C MAL, Core and Common Service formats, while the transport layer uses AMS. A centralized SM and C Registry uses HTTP/XML for transport/encoding. The project's status and progress are reviewed.
The exploration of space is one of the most fascinating domains to study from a human factors perspective. Like other complex work domains such as aviation (Pritchett and Kim, 2008), air traffic management (Durso and Manning, 2008), health care (Morrow, North, and Wickens, 2006), homeland security (Cooke and Winner, 2008), and vehicle control (Lee, 2006), space exploration is a large-scale sociotechnical work domain characterized by complexity, dynamism, uncertainty, and risk in real-time operational contexts (Perrow, 1999; Woods et al, 1994). Nearly the entire gamut of human factors issues - for example, human-automation interaction (Sheridan and Parasuraman, 2006), telerobotics, display and control design (Smith, Bennett, and Stone, 2006), usability, anthropometry (Chaffin, 2008), biomechanics (Marras and Radwin, 2006), safety engineering, emergency operations, maintenance human factors, situation awareness (Tenney and Pew, 2006), crew resource management (Salas et al., 2006), methods for cognitive work analysis (Bisantz and Roth, 2008) and the like -- are applicable to astronauts, mission control, operational medicine, Space Shuttle manufacturing and assembly operations, and space suit designers as they are in other work domains (e.g., Bloomberg, 2003; Bos et al, 2006; Brooks and Ince, 1992; Casler and Cook, 1999; Jones, 1994; McCurdy et al, 2006; Neerincx et aI., 2006; Olofinboba and Dorneich, 2005; Patterson, Watts-Perotti and Woods, 1999; Patterson and Woods, 2001; Seagull et ai, 2007; Sierhuis, Clancey and Sims, 2002). The human exploration of space also has unique challenges of particular interest to human factors research and practice. This chapter provides an overview of those issues and reports on some of the latest research results as well as the latest challenges still facing the field.
In the brief span of about six years (2004-2010), social media radically enhanced people's ways of maintaining recreational friendships. Social media's impact on public affairs (PAO) and community engagement is equally striking: NASA has involved millions of non-NASA viewers in its activities via outward-facing social media, often in a very two-way street fashion. Use of social media as an internal working tool by NASA's tens of thousands of civil servants, onsite contractor employees, and external stakeholders is evolving more slowly. This paper examines, from an engineer's perspective, Marshall Space Flight Center s (MSFC) efforts to bring the power of social media to the daily working environment. Primary emphasis is on an internal Social Networking Service called Explornet that could be scaled Agency-wide. Other topics include MSFC use of other social media day-to-day for non-PAO purposes, some specialized uses of social techniques in space flight control operations, and how to help a community open up so it can discover and adopt what works well.
Papers published via IEEE and AIAA conferences have presented an overview of how social media could benefit NASA working environments in general and proposed three specific social applications to benefit space flight control operations. One of them, Communications Dashboard, would help a real time flight controller keep up with both the "big picture" and significant details of operations via a cohesive interface similar to those of social networking services (SNS). Instead of recreational social features, "CommDash" would support functions like console logging, categorized and threaded text chat streams with enhanced accountability and graphics display features, high-level status displays driven by telemetry or other events, and an on-screen hailing function for requesting voice or text stream conversation. Moving certain voice conversations to text streams would reduce confusion and stress in two ways. Within text conversations, there would be far less repetition of content since text conversations have visual persistence and are reviewable instantly, e.g., there s no need to brief new participants to a discussion -- they just read what s already there. Remaining voice traffic would stand out more clearly, and quieter voice loops means fewer "say again" calls and less distraction from visual and mental tasks, thus less stress. (Most flight controllers monitor 4 or 5 voice loops at once.) Links could be created from console log entries to chat selections so that underlying details are readily available yet unobtrusive. This would reduce the confusion that rises from having multiple and sometimes divergent copies of the same information due to cut/copy and paste operations, attachments, and asynchronous editing. This concept could apply to a plethora of real time control environments and to other settings with lots of information juggling. This paper explores the dashboard concept in further detail and chronicles the first phase of a NASA IT Labs (Information Technology) project that could lead to a working system
Progress by the Consultative Committee for Space Data Standards (CCSDS) Navigation Working Group in developing international standards for use in space flight dynamics operations has been regularly presented at the ISSFD. Since the last update in 2012, the status of several standards has changed relative to previous reports: the Conjunction Data Message has been published and is widely used, the Pointing Request Message is in final prototyping, the Navigation Hardware Message may be cancelled, the Spacecraft Maneuver Message has been discontinued, a new Re-Entry Data Message standard has been started, the Events Message is about to start, and the "first generation" standards (Orbit Data Messages, Attitude Data Messages, Tracking Data Message, NDM/XML Specification) are being revised. Future directions have primarily arisen in the context of "second generation" standards that supplement first generation standards. The need to duplicate common data structures (e.g., an orbit state) commonly arises. Two important objectives of CCSDS international standards are interoperability and cross-support, which makes consistency essential. Still, maintaining consistency from one standard to another is challenging. The related concepts of duplication and consistency have led to the still evolving notion of a "universal, modular message". Recent discussion suggests this concept may be the way forward.
Explore the source record for details and available documents.
His presentation will cover, the current and future, technical and organizational opportunities and challenges with virtualizing a multi-mission operations center. The full deployment of Goddard Space Flight Centers (GSFC) Virtualized Multi-Mission Operations Center (vMMOC) is nearly complete. The Space Science Mission Operations (SSMO) organizations spacecraft ACE, Fermi, LRO, MMS(4), OSIRIS-REx, SDO, SOHO, Swift, and Wind are in the process of being fully migrated to the vMMOC. The benefits of the vMMOC will be the normalization and the standardization of IT services, mission operations, maintenance, and development as well as ancillary services and policies such as collaboration tools, change management systems, and IT Security. The vMMOC will also provide operational efficiencies regarding hardware, IT domain expertise, training, maintenance and support.The presentation will also cover SSMO's secure Situational Awareness Dashboard in an integrated, fleet centric, cloud based web services fashion. Additionally the SSMO Telemetry as a Service (TaaS) will be covered, which allows authorized users and processes to access telemetry for the entire SSMO fleet, and for the entirety of each spacecrafts history. Both services leverage cloud services in a secure FISMA High and FedRamp environment, and also leverage distributed object stores in order to house and provide the telemetry. The services are also in the process of leveraging the cloud computing services elasticity and horizontal scalability. In the design phase is the Navigation as a Service (NaaS) which will provide a standardized, efficient, and normalized service for the fleet's space flight dynamics operations. Additional future services that may be considered are Ground Segment as a Service (GSaaS), Telemetry and Command as a Service (TCaaS), Flight Software Simulation as a Service, etc.