Search NASA⌕ Search

SEARCH · Search NASA

Results for “task management”

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.

At least 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Exploration Medical System Demonstration

BACKGROUND: Exploration class missions will present significant new challenges and hazards to the health of the astronauts. Regardless of the intended destination, beyond low Earth orbit a greater degree of crew autonomy will be required to diagnose medical conditions, develop treatment plans, and implement procedures due to limited communications with ground-based personnel. SCOPE: The Exploration Medical System Demonstration (EMSD) project will act as a test bed on the International Space Station (ISS) to demonstrate to crew and ground personnel that an end-to-end medical system can assist clinician and non-clinician crew members in optimizing medical care delivery and data management during an exploration mission. Challenges facing exploration mission medical care include limited resources, inability to evacuate to Earth during many mission phases, and potential rendering of medical care by non-clinicians. This system demonstrates the integration of medical devices and informatics tools for managing evidence and decision making and can be designed to assist crewmembers in nominal, non-emergent situations and in emergent situations when they may be suffering from performance decrements due to environmental, physiological or other factors. PROJECT OBJECTIVES: The objectives of the EMSD project are to: a. Reduce or eliminate the time required of an on-orbit crew and ground personnel to access, transfer, and manipulate medical data. b. Demonstrate that the on-orbit crew has the ability to access medical data/information via an intuitive and crew-friendly solution to aid in the treatment of a medical condition. c. Develop a common data management framework that can be ubiquitously used to automate repetitive data collection, management, and communications tasks for all activities pertaining to crew health and life sciences. d. Ensure crew access to medical data during periods of restricted ground communication. e. Develop a common data management framework that allows for scalability, extensibility, and interoperability of data sources and data users. f. Lower total cost of ownership for development and sustainment of peripheral hardware and software that use EMSD for data management. g. Provide a better standard of healthcare for crew members through reductions in the time required by crew and ground personnel to provide medical treatment and the number of crew errors experienced during treatment.

Rubin, D. A.↗
NASA NTRS2006

Advancing the practice of systems engineering at JPL

In FY 2004, JPL launched an initiative to improve the way it practices systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to "significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks." The scope of the SEA Project includes the systems engineering work performed in all three dimensions of a program, project, or task: 1. the full life-cycle, i.e., concept through end of operations 2. the full depth, i.e., Program, Project, System, Subsystem, Element (SE Levels 1 to 5) 3. the full technical scope, e.g., the flight, ground and launch systems, avionics, power, propulsion, telecommunications, thermal, etc. The initial focus of their efforts defined the following basic systems engineering functions at JPL: systems architecture, requirements management, interface definition, technical resource management, system design and analysis, system verification and validation, risk management, technical peer reviews, design process management and systems engineering task management, They also developed a list of highly valued personal behaviors of systems engineers, and are working to inculcate those behaviors into members of their systems engineering community. The SEA Project is developing products, services, and training to support managers and practitioners throughout the entire system lifecycle. As these are developed, each one needs to be systematically deployed. Hence, the SEA Project developed a deployment process that includes four aspects: infrastructure and operations, communication and outreach, education and training, and consulting support. In addition, the SEA Project has taken a proactive approach to organizational change management and customer relationship management - both concepts and approaches not usually invoked in an engineering environment. This paper'3 describes JPL's approach to advancing the practice of systems engineering at the Lab. It describes the general approach used and how they addressed the three key aspects of change: people, process and technology. It highlights a list of highly valued personal behaviors of systems engineers, discusses the various products, services and training that were developed, describes the deployment approach used, and concludes with several lessons learned.

process improvement↗
NASA NTRS2016

Capturing Safety Requirements to Enable Effective Task Allocation Between Humans and Automaton in Increasingly Autonomous Systems

There is a current drive towards enabling the deployment of increasingly autonomous systems in the National Airspace System (NAS). However, shifting the traditional roles and responsibilities between humans and automation for safety critical tasks must be managed carefully, otherwise the current emergent safety properties of the NAS may be disrupted. In this paper, a verification activity to assess the emergent safety properties of a clearly defined, safety critical, operational scenario that possesses tasks that can be fluidly allocated between human and automated agents is conducted. Task allocation role sets were proposed for a human-automation team performing a contingency maneuver in a reduced crew context. A safety critical contingency procedure (engine out on takeoff) was modeled in the Soar cognitive architecture, then translated into the Hybrid Input Output formalism. Verification activities were then performed to determine whether or not the safety properties held over the increasingly autonomous system. The verification activities lead to the development of several key insights regarding the implicit assumptions on agent capability. It subsequently illustrated the usefulness of task annotations associated with specialized requirements (e.g., communication, timing etc.), and demonstrated the feasibility of this approach.

Neogi, Natasha A.↗
NASA NTRS2004

Initiating the 2002 Mars Science Laboratory (MSL) Technology Program

The Mars Science Laboratory (MSL) Project is an aggressive mission launching in 2009 to investigate the Martian environment and requires new capabilities that are currently are not available. The MSL Technology Program is developing a wide-range of technologies needed for this Mission and potentially other space missions. The MSL Technology Program reports to both the MSL Project and the Mars Technology Program (MTP). The dual reporting process creates a challenging management situation, but ensures the new technology meets both the specific MSL requirements and the broader Mars Program requirements. MTP is a NASA-wide technology development program managed by JPL and is divided into a Focused Program and a Base Program. The MSL Technology Program is under the focused program and is tightly coupled to MSL's mission milestones and deliverables. The technology budget is separate from the flight Project budget, but the technology's requirements and the development process are tightly coordinated with the Project. The MSL Technology Program combines the proven management techniques of flight projects with the commercial technology management strategies of industry and academia, to create a technology management program that meets the short-term requirements of MSL and the long-term requirements of MTP. This paper examines the initiation of 2002 MSL Technology program. Some of the areas discussed in this paper include technology definition, task selection, technology management, and technology assessment. This paper also provides an update of the 2003 MSL technology program and examines some of the drivers that changed the program from its initiation.

Caffrey, Robert T.↗
NASA NTRS2004

Initiating the 2002 Mars Science Laboratory (MSL) Focused Technology Program

The Mars Science Laboratory (MSL) Project is an aggressive mission launching in 2009 to deliver a new generation of rover safely to the surface of Mars and conduct comprehensive in situ investigations using a new generation of instruments. This system will be designed to land with precision and be capable of operating over a large percentage on the surface of Mars. It will have capabilities that will support NASA's scientific goals into the next decade of exphation. The MSL Technology program is developing a wide-range of technologies needed for this Mission and potentially other space missions. The MSL Technology Program reports to both the MSL Project and the Mars Technology Program (MTP). The dual reporting process creates a challenging management situation, but ensures the new technology meets both the specific MSL requirements and the broader Mars Program requirements. MTP is a NASA-wide technology development program managed by the Jet Propulsion Laboratory (JPL) and is divided into a Focused Program and a Base Program. The Focused Technology Program addresses technologies that are specific and critical to near-term missions, while the Base Technology Program addresses those technologies that are applicable to multiple missions and which can be characterized as longer term, higher risk, and high payoff technologies. The MSL Technology Program is under the Focused Program and is tightly coupled to MSL's mission milestones and deliverables. The technology budget is separate from the flight Project budget, but the technology s requirements and the development process are tightly coordinated with the Project. The Technology Program combines proven management techniques of flight projects with commercial and academic technology management strategies, to create a technology management program that meets the near-term requirements of MSL and the long-term requirements of MTP. This paper examines the initiation of 2002 MSL Technology program. Some of the areas discussed in this paper include technology definition, task selection, technology management, and technology assessment.

Caffrey, Robert T.↗
NASA NTRS2026

AC and DC Fault Management for Megawatt Electrified Aircraft Electrical Powertrains Task 3: Lifetime and Reliability of Electrical Insulators

This research project was a collaborative investigation between researchers at the RTX Technology Research Center (RTRC) and the University of Texas at Austin and made a significant contribution to enabling electric aircraft. The transport of electric power between the points of generation and use requires power cables. These cables must be smaller, lighter and provide a more predictable life than power cables used in stationary applications. Consequently, this investigation provided heretofore unavailable information supporting the safety and reliability of smaller lighter power cables for electrified aircraft. In addition, the research identified key additional engineering data needed to support quantitative reliability assessments. Important advances included: • Demonstrated that at least one manufacturer can make a novel, smaller, lighter power cable that is free from serious defects. • Developed and published an appropriate analytical construct to describe the life of this novel cable. This is a necessary step for use in aviation where the understanding of remaining life is critical. • Demonstrated thermal-mechanical aging that suggested 1000+ flights before the thermal-mechanical processes produced defects large enough that the defect growth was accelerated electrically. • Showed that electrical aging took place at two rates. The first possibly lasting weeks to months and the second possibly days to weeks. If robust, this provides a good diagnostic for cable replacement. • Demonstrated that the traditional electrical testing of cable materials using manufactured voids can be misleading due to the size of the voids. Emerging laser drilling technology permitted demonstration that the physics of failure in realistically small voids is different from that in the unrealistically large voids used in earlier research, which is very important for high-quality, high-performance, small aircraft cables. Although this project represents a significant contribution to the specifics of cable aging in the aircraft environment, important additional research remains to be completed, including: • Non-uniform thermal cycling by applying the heat from the center conductor to maximize thermal stress next to the core area where the electric gradient is the strongest. This builds on the uniform thermal cycling that has been completed. • The augmentation of the thermal-mechanical failure rate by electrical processes. Better understanding of these time constants strongly affects the ability to predict life. • Termination design: Terminations provide not only electrical reflection potential, but a location for a series arc fault and an area where ozone can diffuse into the center conductor and negatively affect cable insulation. • The abrasion and ozone resistance of the cable jacket. • Pressure cycling as an accelerant of thermal, mechanical, and/or electrical aging. • Possible methods for online PD detection and offline PD localization

model↗
NASA NTRS2005

Towards an Autonomic Cluster Management System (ACMS) with Reflex Autonomicity

Cluster computing, whereby a large number of simple processors or nodes are combined together to apparently function as a single powerful computer, has emerged as a research area in its own right. The approach offers a relatively inexpensive means of providing a fault-tolerant environment and achieving significant computational capabilities for high-performance computing applications. However, the task of manually managing and configuring a cluster quickly becomes daunting as the cluster grows in size. Autonomic computing, with its vision to provide self-management, can potentially solve many of the problems inherent in cluster management. We describe the development of a prototype Autonomic Cluster Management System (ACMS) that exploits autonomic properties in automating cluster management and its evolution to include reflex reactions via pulse monitoring.

Truszkowski, Walt↗
NASA NTRS2007

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗
NASA NTRS2005

Autonomic Cluster Management System (ACMS): A Demonstration of Autonomic Principles at Work

Cluster computing, whereby a large number of simple processors or nodes are combined together to apparently function as a single powerful computer, has emerged as a research area in its own right. The approach offers a relatively inexpensive means of achieving significant computational capabilities for high-performance computing applications, while simultaneously affording the ability to. increase that capability simply by adding more (inexpensive) processors. However, the task of manually managing and con.guring a cluster quickly becomes impossible as the cluster grows in size. Autonomic computing is a relatively new approach to managing complex systems that can potentially solve many of the problems inherent in cluster management. We describe the development of a prototype Automatic Cluster Management System (ACMS) that exploits autonomic properties in automating cluster management.

Baldassari, James D.↗
NASA NTRS1975

Verbal Workload in Distributed Air Traffic Management

The effects of alternative traffic management possibilities on task performance and pilot controller verbal workloads were studied. Two new rule structures - sequencing and advisory - in addition to vectoring were studied in conjunction with CRT pilot displays incorporating traffic situation displays with and without aircraft flight path predictors. The sequencing and advisory systems gave increasing control responsibility to the pilots. It was concluded that distributed management systems could in practice significantly reduce controller verbal workload without reducing system performance. Implications of this conclusion suggest that distributed management would allow controllers to handle a larger volume of traffic safely either as a normal operating procedure or as a failure mode alternative in a highly automated ground centered system.

Kreifeldt, J. G.↗
NASA NTRS1985

Government-to-government cooperation in space station development

A memoranda of understanding was recently signed between the United States (NASA) and three international Space Station partners - Canada, European Space Agency (ESA), and Japan. The international partners are performing parallel Phase B preliminary design studies, concurrent with the U.S., on their proposed elements/systems for possible integration and operation with the U.S. Space Station System complex. During the 21-month Space Station Phase B study, a large amount of technical interface data will have to be transferred between the U.S. and the international partners. Scheduled bilateral technical coordination meetings will also be held. The coordination and large number of interfaces required to integrate the international requirements into the Space Station require a clean interface management organizational structure and operation procedures to accomplish the integration task. The international coordination management organizational structure, management tools, and communications network are discussed including the proposed international elements/systems being studied by the international partners.

Nassiff, S. H.↗
NASA NTRSDate not supplied

Aircraft Classification Using Radar from Small Unmanned Aerial Systems for Scalable Traffic Management Emergency Response Operations

This work investigates two machine learning techniques: Support Vector Machine (SVM) and Autoencoders (AE)with SVM layer for classification of radar trajectories as General Aviation (GA), fixed-wing small Unmanned Aerial System (sUAS), or not-an-aircraft using radar data recorded from sUAS. Onboard identification of intruder aircraft type is useful for planning avoidance maneuvers and is necessary to provide autonomous systems to meet or exceed the avoidance capability of a human pilot. Aircraft classification can identify intruder aircraft that are not part of the team and may be violating a Temporary Flight Restriction. Aircraft classification is needed in monitoring an airspace where multiple aircraft are teaming on a shared task. Scalable Traffic Management for Emergency Response Operations (STEReO) is a NASA project aimed at improving disaster response by enabling large scale aircraft operations through the teaming of manned aircraft with sUAS to maximize emergency response resources. To this end, this work uses trajectories and radar derived features to classify aircraft from a multirotor sUAS. The AE + SVM generated the strongest classification overall accuracy of 93.5% using the first 4 seconds of radar track data for tracks that activated the avoidance system. Subsampling the available track data increased the available training data with the maximum aircraft recall of 0.94 achieved using the SVM with 1 second track data.

Chester V. Dolph↗
NASA NTRSDate not supplied

Effects of Communication Modality on Pilot-Controller Coordination during a Simulated m:N Operation

The last decade or so has seen growing interest in new control paradigms and concepts of operation for uncrewed aircraft systems (UAS) in which multiple aircraft are piloted remotely by a single or relatively small number of people. Referred to as “one-to-many” and “many-to- many” (alternatively, “multi-operator, multi-vehicle”)—and frequently expressed as the corresponding ratios, 1:N and m:N—such novel configurations of aircraft and the people who manage them are seen as critical to the path to future operations involving UAS. Examples of industry domains interested in these control paradigms are small package delivery services utilizing small UAS and passenger-carrying, short-range “Urban Air Mobility” (UAM) operations. Stakeholders in such operations have identified communication and coordination of flight activity with air traffic controllers (ATC) as a barrier to operations. In contrast to present-day flight operations, in which a pilot communicates with one ATC on one radio frequency for one aircraft, multi-vehicle operations potentially entail a significant increase in pilot task load for management of comms. New concepts, such as UAS Service Suppliers (USSs) and Providers of Services to UAM (PSUs), have been proposed to address the known bottleneck for Air Traffic Management (ATM) presented by multi-vehicle operations. While progress has been steadily made over years developing USSs and PSUs, it is generally expected that initial UAM operations will rely on traditional voice-over-radio communication with ATC for purposes of ATM. The current study was a human-in-the-loop simulation that had participants, each possessing a Private Pilot License, act as the ground-based pilot-in- command for multiple vehicles in a hypothetical UAM service in the San Francisco Bay Area. The experiment utilized a 2-by-3, within-subjects design in which the pilot’s Vehicle Load (4 vs. 12) and Comm System (Voice, Datalink, and a Hybrid) were manipulated. The task given to pilots was to use the Comm System to coordinate flight activity for all aircraft with appropriate controllers, having to obtain departure and arrival clearances at “vertiport” facilities and transition clearances for any intermediate airspaces along the route. Pilots were additionally responsible for compliance with vectoring instructions issued by ATC. Subjective workload questionnaires (NASA-TLX) were administered following each experimental trial. Screen recordings of the pilot’s Ground Control Station (GCS) and audio recordings of trials were subsequently coded to obtain performance metrics: response times and error rates. Presented in this paper are results related to pilot responses to vectoring instructions issued by ATC. Workload was found to be significantly higher in the 12-Vehicle condition compared to the 4-Vehicle condition, nearly maxing out the NASA-TLX overall workload scale. There was no significant difference made by the Comm System on workload ratings. Pilots’ response times to communications were fastest in the Voice condition, although overall “service time” for compliance was shorter in Datalink and Hybrid conditions in most cases. Errors by pilots were frequent in both Vehicle Load conditions, most perniciously when using the Voice system. The results of this study suggest tradeoffs in advantages and disadvantages of the three comm systems. Recommendations for communication system design are provided taking the tradeoffs into account.

Garrett G Sadler↗
NASA NTRSDate not supplied

Effects of Communication Modality on Pilot-Controller Coordination during a Simulated m:N Operation

The last decade or so has seen growing interest in new control paradigms and concepts of operation for uncrewed aircraft systems (UAS) in which multiple aircraft are piloted remotely by a single or relatively small number of people. Referred to as “one-to-many” and “many-to- many” (alternatively, “multi-operator, multi-vehicle”)—and frequently expressed as the corresponding ratios, 1:N and m:N—such novel configurations of aircraft and the people who manage them are seen as critical to the path to future operations involving UAS. Examples of industry domains interested in these control paradigms are small package delivery services utilizing small UAS and passenger-carrying, short-range “Urban Air Mobility” (UAM) operations. Stakeholders in such operations have identified communication and coordination of flight activity with air traffic controllers (ATC) as a barrier to operations. In contrast to present-day flight operations, in which a pilot communicates with one ATC on one radio frequency for one aircraft, multi-vehicle operations potentially entail a significant increase in pilot task load for management of comms. New concepts, such as UAS Service Suppliers (USSs) and Providers of Services to UAM (PSUs), have been proposed to address the known bottleneck for Air Traffic Management (ATM) presented by multi-vehicle operations. While progress has been steadily made over years developing USSs and PSUs, it is generally expected that initial UAM operations will rely on traditional voice-over-radio communication with ATC for purposes of ATM. The current study was a human-in-the-loop simulation that had participants, each possessing a Private Pilot License, act as the ground-based pilot-in- command for multiple vehicles in a hypothetical UAM service in the San Francisco Bay Area. The experiment utilized a 2-by-3, within-subjects design in which the pilot’s Vehicle Load (4 vs. 12) and Comm System (Voice, Datalink, and a Hybrid) were manipulated. The task given to pilots was to use the Comm System to coordinate flight activity for all aircraft with appropriate controllers, having to obtain departure and arrival clearances at “vertiport” facilities and transition clearances for any intermediate airspaces along the route. Pilots were additionally responsible for compliance with vectoring instructions issued by ATC. Subjective workload questionnaires (NASA-TLX) were administered following each experimental trial. Screen recordings of the pilot’s Ground Control Station (GCS) and audio recordings of trials were subsequently coded to obtain performance metrics: response times and error rates. Presented in this paper are results related to pilot responses to vectoring instructions issued by ATC. Workload was found to be significantly higher in the 12-Vehicle condition compared to the 4-Vehicle condition, nearly maxing out the NASA-TLX overall workload scale. There was no significant difference made by the Comm System on workload ratings. Pilots’ response times to communications were fastest in the Voice condition, although overall “service time” for compliance was shorter in Datalink and Hybrid conditions in most cases. Errors by pilots were frequent in both Vehicle Load conditions, most perniciously when using the Voice system. The results of this study suggest tradeoffs in advantages and disadvantages of the three comm systems. Recommendations for communication system design are provided taking the tradeoffs into account.

urban air mobility↗
NASA NTRS1991

An enhanced Ada run-time system for real-time embedded processors

An enhanced Ada run-time system has been developed to support real-time embedded processor applications. The primary focus of this development effort has been on the tasking system and the memory management facilities of the run-time system. The tasking system has been extended to support efficient and precise periodic task execution as required for control applications. Event-driven task execution providing a means of task-asynchronous control and communication among Ada tasks is supported in this system. Inter-task control is even provided among tasks distributed on separate physical processors. The memory management system has been enhanced to provide object allocation and protected access support for memory shared between disjoint processors, each of which is executing a distinct Ada program.

Sims, J. T.↗
NASA NTRS2013

Crew Roles and Interactions in Scientific Space Exploration

Future piloted space exploration missions will focus more on science than engineering, a change which will challenge existing concepts for flight crew tasking and demand that participants with contrasting skills, values, and backgrounds learn to cooperate as equals. In terrestrial space flight analogs such as Desert Research And Technology Studies, engineers, pilots, and scientists can practice working together, taking advantage of the full breadth of all team members training to produce harmonious, effective missions that maximize the time and attention the crew can devote to science. This paper presents, in a format usable as a reference by participants in the field, a successfully tested crew interaction model for such missions. The model builds upon the basic framework of a scientific field expedition by adding proven concepts from aviation and human spaceflight, including expeditionary behavior and cockpit resource management, cooperative crew tasking and adaptive leadership and followership, formal techniques for radio communication, and increased attention to operational considerations. The crews of future spaceflight analogs can use this model to demonstrate effective techniques, learn from each other, develop positive working relationships, and make their expeditions more successful, even if they have limited time to train together beforehand. This model can also inform the preparation and execution of actual future spaceflights.

Love, Stanley G.↗
NASA NTRS2007

Biomedical Support of U.S. Extravehicular Activity

The world's first extravehicular activity (EVA) was performed by A. A. Leonov on March 18, 1965 during the Russian Voskhod-2 mission. The first US EVA was executed by Gemini IV astronaut Ed White on June 3, 1965, with an umbilical tether that included communications and an oxygen supply. A hand-held maneuvering unit (HHMU) also was used to test maneuverability during the brief EVA; however the somewhat stiff umbilical limited controlled movement. That constraint, plus difficulty returning through the vehicle hatch, highlighted the need for increased thermal control and improved EVA ergonomics. Clearly, requirements for a useful EVA were interrelated with the vehicle design. The early Gemini EVAs generated requirements for suits providing micro-meteor protection, adequate visual field and eye protection from solar visual and infrared radiation, gloves optimized for dexterity while pressurized, and thermal systems capable of protecting the astronaut while rejecting metabolic heat during high workloads. Subsequent Gemini EVAs built upon this early experience and included development of a portable environmental control and life support systems (ECLSS) and an astronaut maneuvering unit. The ECLSS provided a pressure vessel and controller with functional control over suit pressure, oxygen flow, carbon dioxide removal, humidity, and temperature control. Gemini EVA experience also identified the usefulness of underwater neutral buoyancy and altitude chamber task training, and the importance of developing reliable task timelines. Improved thermal management and carbon dioxide control also were required for high workload tasks. With the Apollo project, EVA activity was primarily on the lunar surface; and suit durability, integrated liquid cooling garments, and low suit operating pressures (3.75 pounds per square inch absolute [psia] or 25.8 kilopascal [kPa],) were required to facilitate longer EVAs with ambulation and significant physical workloads with average metabolic rates of 1000 BTU/hr and peaks of up to 2200 BTU/hr. Mobility was further augmented with the Lunar Roving Vehicle. The Apollo extravehicular mobility unit (EMU) was made up of over 15 components, ranging from a biomedical belt for capturing and transmitting biomedical data, urine and fecal containment systems, a liquid cooling garment, communications cap, a modular portable life support system (PLSS), a boot system, thermal overgloves, and a bubble helmet with eye protection. Apollo lunar astronauts performed successful EVAs on the lunar surface from a 5 psia (34.4 kPa) 100% oxygen environment in the Lunar Lander. A maximum of three EVAs were performed on any mission. For Skylab a modified A7LB suit, used for Apollo 15, was selected. The Skylab astronaut life support assembly (ALSA) provided umbilical support through the life support umbilical (LSU) and used open loop oxygen flow, rather than closed-loop as in Apollo missions. Thermal control was provided by liquid water circulated by spacecraft pumps and electrical power also was provided from the spacecraft via the umbilical. The cabin atmosphere of 5 psia (34.4 kPa), 70% oxygen, provided a normoxic atmosphere and because of the very low nitrogen partial pressures, no special protocols were required to protect against decompression sickness (DCS) as was the case with the Apollo spacecraft with a 5 psi, 100% oxygen environment.

Gernhardt, Michael L.↗
NASA NTRS1982

The OSS-1/STS-3 mission

Integration, test, flight operations, program and science management, and experiment results from the OSS-1/STS-3 flight are reviewed. The experimental pallet, manufactured by ESA members, carried instrumentation for astronomy, space plasma studies, physics, planetology, solar physics, and life sciences. The ability of the equipment to operate in a worst-case Orbiter thermal environment was tested, as was the plasma environment around the Orbiter. The solar UV spectral irradiance monitor microprocessor was found to reset concurrently with start-up of the Shuttle hydraulic pumps. Degradations were also observed in one of the three solar flare X ray polarimeter modules, the thermal cannister experiment microprocessor, and the scientific data recorder no. 2. The Orbiter was determined to perform well during firing of an electron beam. A contamination monitor recorded matter accretion to be dependent on the solar orientation of the Orbiter. Finally, the distribution of the responsibilities and tasks for mission management are reviewed.

Kissin, K.↗