Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “operator support”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS1990

Space system operations and support cost analysis using Markov chains

This paper evaluates the use of Markov chain process in probabilistic life cycle cost analysis and suggests further uses of the process as a design aid tool. A methodology is developed for estimating operations and support cost and expected life for reusable space transportation systems. Application of the methodology is demonstrated for the case of a hypothetical space transportation vehicle. A sensitivity analysis is carried out to explore the effects of uncertainty in key model inputs.

Unal, Resit↗
NASA NTRS2008

Mentoring SFRM: A New Approach to International Space Station Flight Controller Training

The Mission Operations Directorate (MOD) of the Johnson Space Center is responsible for providing continuous operations support for the International Space Station (ISS). Operations support requires flight controllers who are skilled in team performance as well as the technical operations of the ISS. Space Flight Resource Management (SFRM), a NASA adapted variant of Crew Resource Management (CRM), is the competency model used in the MOD. ISS flight controller certification has evolved to include a balanced focus on development of SFRM and technical expertise. The latest challenge the MOD faces is how to certify an ISS flight controller (operator) to a basic level of effectiveness in 1 year. SFRM training uses a two-pronged approach to expediting operator certification: 1) imbed SFRM skills training into all operator technical training and 2) use senior flight controllers as mentors. This paper focuses on how the MOD uses senior flight controllers as mentors to train SFRM skills. Methods: A mentor works with an operator throughout the training flow. Inserted into the training flow are guided-discussion sessions and on-the-job observation opportunities focusing on specific SFRM skills, including: situational leadership, conflict management, stress management, cross-cultural awareness, self care and team care while on-console, communication, workload management, and situation awareness. The mentor and operator discuss the science and art behind the skills, cultural effects on skills applications, recognition of good and bad skills applications, recognition of how skills application changes subtly in different situations, and individual goals and techniques for improving skills. Discussion: This mentoring program provides an additional means of transferring SFRM knowledge compared to traditional CRM training programs. Our future endeavors in training SFRM skills (as well as other organization s) may benefit from adding team performance skills mentoring. This paper explains our mentoring approach and discusses its effectiveness and future applicability in promoting SFRM/CRM skills.

Huning, Therese↗
NASA NTRS2009

Mentoring SFRM: A New Approach to International Space Station Flight Control Training

The Mission Operations Directorate (MOD) of the Johnson Space Center is responsible for providing continuous operations support for the International Space Station (ISS). Operations support requires flight controllers who are skilled in team performance as well as the technical operations of the ISS. Space Flight Resource Management (SFRM), a NASA adapted variant of Crew Resource Management (CRM), is the competency model used in the MOD. ISS flight controller certification has evolved to include a balanced focus on development of SFRM and technical expertise. The latest challenge the MOD faces is how to certify an ISS flight controller (Operator) to a basic level of effectiveness in 1 year. SFRM training uses a twopronged approach to expediting operator certification: 1) imbed SFRM skills training into all Operator technical training and 2) use senior flight controllers as mentors. This paper focuses on how the MOD uses senior flight controllers as mentors to train SFRM skills.

Huning, Therese↗
NASA NTRSDate not supplied

NASA Support for Commercial Crew Launch Capabilities

Since the earliest days of U.S. human spaceflight, NASA’s Marshall Space Flight Center in Huntsville, Alabama, has played a key role in American crew launch capability, from engineering support for the first Mercury-Redstone launches, to the Saturn launches to the Moon, through Shuttle and now Artemis. Today, Marshall brings that expertise gained through decades of crewed space launches to NASA’s Commercial Crew Program (CCP), providing launch vehicle engineering and programmatic support. The team’s responsibilities have included human certification of commercial launch systems for the CCP missions, including Atlas V and Falcon 9, and verifying each launch vehicle complies with flight certification. MSFC provides expertise in nearly all aspects of launch vehicle design and performance including solid motors and liquid engines, stage propulsion, thrust vector control, structural and dynamics, safety and mission assurance. During each commercial crew launch, an engineering support team is on console at Marshall’s Huntsville Operations Support Center, which has provided launch operations support since Apollo, providing real-time oversight to safety standards for the vehicle and verifying data. Launch vehicle support for Commercial Crew has come as a paradigm shift for the MSFC team, inspiring new approaches that leverage expertise and best practices from past NASA-developed launch vehicle missions, while at the same time providing new synergies from work with commercial partners on CCP. This paper will explore the role that the Marshall launch vehicle services team plays in the Commercial Crew Program, as well as lessons learned from the program that will continue to benefit a new era of spaceflight partnerships.

Commercial Crew↗
NASA NTRS2012

Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge of the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments disciplines that will help serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environments and spacecraft effects (SENSE) organization. This SENSE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Engineering effects focuses on the material, component, sub-system and system-level selection and the testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope of the TWGs and their relationship to the functional areas, and discuss an organizational structure for this space environments and spacecraft effects organization.

Edwards, David L.↗
NASA NTRS2012

An Overview of the Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore our Earth, and the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge on the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments fields that will serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environment and spacecraft effects (SESE) organization. This SESE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems, and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Environment effects focuses on the material, component, sub-system, and system-level response to the space environment and include the selection and testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope and purpose of the space environments and spacecraft effects organization and describe the TWG's and their relationship to the functional areas.

Edwards, David L.↗
NASA NTRS2014

CEO Sites Mission Management System (SMMS)

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.

Trenchard, Mike↗
NASA NTRS2010

Design and Testing of the Primary and Secondary Oxygen Regulators for the Flexible Portable Life Support System (FlexPLSS)

The next generation space suit requires additional capabilities for controlling and adjusting internal pressure compared to that of historical designs. Although the general configuration of the oxygen systems for the next generation space suit is similar or derived from the Apollo and Shuttle Extravehicular Mobility Unit (EMU) with Primary closed loop life support operation and Secondary sourced open loop life support operations, nearly everything else has evolved with new available technologies. For the case of the primary and secondary regulators, the design has gone away from purely mechanical systems actuated with pull-cords or "bicycle cables" to electro-mechanical hybrids that provide the best of both worlds with respect to power draw, reliability, and versatility. This paper discusses the development and testing of a Secondary Oxygen Regulator bench-top prototype along with comparisons of operation with the various prototypes for the Primary Oxygen Regulator.

Campbell, Colin↗
NASA NTRS1987

Launch Processing System operations with a future look to Operations Analyst (OPERA)

The Launch Processing System architecture and the ground support operations required to provide Shuttle System engineers with the capability to safely process and launch an Orbiter are described. The described ground operations are the culmination of eleven years of experience and redesign. Some of the 'lessons learned' are examined, and problem areas which ground support operations have identified over the years as the Shuttle and Launch Processing Systems continue to grow in complexity are discussed. The Operational Analyst for Distributed Systems (OPERA), a proposed set of expert systems for the Launch Processing System Operational assistance, is discussed along with its extensions to prospective future configurations and components for the Launch Processing System.

Heard, Astrid E.↗
NASA NTRS2012

HOSC DTN Gateway Test Report

Goals of this activity: Test the Huntsville Operations Support Center (HOSC) Delay/Disruption Tolerant Networking (DTN) Gateway for operational use Current activity includes: (1) Test the Implementation of a new DTN2 gateway at the HOSC (2) Confirm integration of DTN nodes into the S-band uplink and Ku-band downlink of the ISS for limited use (3) Implement Aggregate Custody Signal to ISS platforms (4) Verify operational support for Colorado University (CU) onboard components (5) Verify ability to support Multi-Purpose End-To- End Robotic Operation Network (METERON) OpsCon-2

Pitts, Robert Lee↗
NASA NTRS2014

Usability of Operational Performance Support Tools - Findings from Sea Test II

Sea Test II, aka NASA Extreme Environment Mission Operations 17(NEEMO 17) took place in the Florida Aquarius undersea habitat. This confined underwater environment provides a excellent analog for space habitation providing similarities to space habitation such as hostile environment, difficult logistics, autonomous operations, and remote communications. This study collected subjective feedback on the usability of two performance support tools during the Sea Test II mission, Sept 10‐14, 2013; Google Glass and iPAD. The two main objectives: - Assess the overall functionality and usability of each performance support tool in a mission analog environment. - Assess the advantages and disadvantages of each tool when performing operational procedures and Just‐In‐Time‐Training (JITT).

Byrne, Vicky↗
NASA NTRS2002

Secure Remote Access Issues in a Control Center Environment

The ISS finally reached an operational state and exists for local and remote users. Onboard payload systems are managed by the Huntsville Operations Support Center (HOSC). Users access HOSC systems by internet protocols in support of daily operations, preflight simulation, and test. In support of this diverse user community, a modem security architecture has been implemented. The architecture has evolved over time from an isolated but open system to a system which supports local and remote access to the ISS over broad geographic regions. This has been accomplished through the use of an evolved security strategy, PKI, and custom design. Through this paper, descriptions of the migration process and the lessons learned are presented. This will include product decision criteria, rationale, and the use of commodity products in the end architecture. This paper will also stress the need for interoperability of various products and the effects of seemingly insignificant details.

Pitts, Lee↗
NASA NTRS2002

Secure Payload Access to the International Space Station

The ISS finally reached an operational state and exists for local and remote users. Onboard payload systems are managed by the Huntsville Operations Support Center (HOSC). Users access HOSC systems by internet protocols in support of daily operations, preflight simulation, and test. In support of this diverse user community, a modem security architecture has been implemented. The architecture has evolved over time from an isolated but open system to a system which supports local and remote access to the ISS over broad geographic regions. This has been accomplished through the use of an evolved security strategy, PKI, and custom design. Through this paper, descriptions of the migration process and the lessons learned are presented. This will include product decision criteria, rationale, and the use of commodity products in the end architecture. This paper will also stress the need for interoperability of various products and the effects of seemingly insignificant details.

Pitts, R. Lee↗
NASA NTRS1993

HL-20 operations and support requirements for the Personnel Launch System mission

The processing, mission planning, and support requirements were defined for the HL-20 lifting-body configuration that can serve as a Personnel Launch System. These requirements were based on the assumption of an operating environment that incorporates aircraft and airline support methods and techniques that are applicable to operations. The study covered the complete turnaround process for the HL-20, including landing through launch, and mission operations, but did not address the support requirements of the launch vehicle except for the integrated activities. Support is defined in terms of manpower, staffing levels, facilities, ground support equipment, maintenance/sparing requirements, and turnaround processing time. Support results were drawn from two contracted studies, plus an in-house analysis used to define the maintenance manpower. The results of the contracted studies were used as the basis for a stochastic simulation of the support environment to determine the sufficiency of support and the effect of variance on vehicle processing. Results indicate the levels of support defined for the HL-20 through this process to be sufficient to achieve the desired flight rate of eight flights per year.

Morris, W. D.↗
NASA NTRS1983

Definition of technology development missions for early space stations orbit transfer vehicle serving. Phase 2, task 1: Space station support of operational OTV servicing

Representative space based orbital transfer vehicles (OTV), ground based vehicle turnaround assessment, functional operational requirements and facilities, mission turnaround operations, a comparison of ground based versus space based tasks, activation of servicing facilities prior to IOC, fleet operations requirements, maintenance facilities, OTV servicing facilities, space station support requirements, and packaging for delivery are discussed.

Source record↗
NASA NTRS2014

STK Integrated Message Production List Editor (SIMPLE) for CEO Operations

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade and replace its mission planning and mission operations software systems, which were developed in the Space Shuttle era of the 1980s and 1990s. The impetuses for this change were the planned transition of all workstations to the Windows 7 64-bit operating system and the desire for more efficient and effective use of Satellite Tool Kit (STK) software required for reliable International Space Station (ISS) Earth location tracking. An additional requirement of this new system was the use of the same SQL database of CEO science sites from the SMMS, which was also being developed. STK Integrated Message Production List Editor (SIMPLE) is the essential, all-in-one tool now used by CEO staff to perform daily ISS mission planning to meet its requirement to acquire astronaut photography of specific sites on Earth. The sites are part of a managed, long-term database that has been defined and developed for scientific, educational, and public interest. SIMPLE's end product is a set of basic time and location data computed for an operator-selected set of targets that the ISS crew will be asked to photograph (photography is typically planned 12 to 36 hours out). The CEO operator uses SIMPLE to (a) specify a payload operations planning period; (b) acquire and validate the best available ephemeris data (vectors) for the ISS during the planning period; (c) ingest and display mission-specific site information from the CEO database; (d) identify and display potential current dynamic event targets as map features; (e) compute and display time and location information for each target; (f) screen and select targets based on known crew availability constraints, obliquity constraints, and real-time evaluated constraints to target visibility due to illumination (sun elevation) and atmospheric conditions (weather); and finally (g) incorporate basic, computed time and location information for each selected target into the daily CEO Target List product (message) for submission to ISS payload planning and integration teams for their review and approval prior to uplink. SIMPLE requires and uses the following resources: an ISS mission planning period Greenwich Mean Time start date/time and end date/time), the best available ISS mission ephemeris data (vectors) for that planning period, the STK software package configured for the ISS, and an ISS mission-specific subset of the CEO sites database. The primary advantages realized by the development and implementation of SIMPLE into the CEO payload operations support activity are a smooth transition to the Windows 7 operating system upon scheduled workstation refresh; streamlining of the input and verification of the current ISS ephemeris (vector data); seamless incorporation of selected contents of the SQL database of science sites; the ability to tag and display potential dynamic event opportunities on orbit track maps; simplification of the display and selection of encountered sites based on crew availability, illumination, obliquity, and weather constraints; the incorporation of high-quality mapping of the Earth with various satellite-based datasets for use in describing targets; and the ability to encapsulate and export the essential selected target elements in XML format for use by onboard Earth-location systems, such as Worldmap. SIMPLE is a carefully designed and crafted in-house software package that includes detailed help files for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in May 2012.

Trenchard, Mike↗