Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Integrated Operations”

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 NTRS2004

Remote Operations and Ground Control Centers

The Payload Operations Integration Center (POIC) at the Marshall Space Flight Center supports the International Space Station (ISS) through remote interfaces around the world. The POIC was originally designed as a gateway to space for remote facilities; ranging from an individual user to a full-scale multiuser environment. This achievement was accomplished while meeting program requirements and accommodating the injection of modern technology on an ongoing basis to ensure cost effective operations. This paper will discuss the open POIC architecture developed to support similar and dissimilar remote operations centers. It will include technologies, protocols, and compromises which on a day to day basis support ongoing operations. Additional areas covered include centralized management of shared resources and methods utilized to provide highly available and restricted resources to remote users. Finally, the effort of coordinating the actions of participants will be discussed.

Bryant, Barry S.↗
NASA NTRS2018

Marrying Social Media Approaches and Space Flight Control: Eight Years at SpaceOps

Three previous SpaceOps papers [1-3] - published in 2010, 2012 (honored by the Conference as a "Best Paper"), and 2014 - have discussed paths to using social media concepts and techniques to enhance space flight controller effectiveness by a) reducing clutter of nonverbal communications (e.g., visual flow with minimal headers and shared content instead of multiple copies), b) moving some voice communication to non-verbal transmission (virtually eliminating "say again" requests because non-verbal comm can be re-read), thus making remaining voice comm easier to focus on, and c) reducing short-term and long-term flight stress on flight control personnel. This paper shows how Marshall Space Flight Center's (MSFC) ISS Payload Operations Integration Center (POIC) is realizing the above goals via the Communications Dashboard (CommDash) software suite deployed in 2017 (including enhancements to the Console Log Tool (CoLT) discussed in earlier papers). Two larger-scope benefits spawned by CommDash evolution are also chronicled: a) emergence of an Agile Software Development (ASD) process adapted to the not-always-nimble environment of government projects, and b) the sprouting of a Human Factors Engineering (HF or HFE) community of practice within MSFC's Payload and Mission Operations Division (PMOD).

Scott, David W.↗
NASA NTRS2008

"Built-In" Action/Issues Tracking and Post-Ops Analysis Tool for Realtime Console Operations

Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for the International Space Station (ISS) uses a number of formal databases to manage and track flight plan changes, onboard and ground equipment anomalies, and other events. However, individual console positions encounter many action items and/or occurrences that don't fit neatly into the databases, and while console logs are comprehensive, manual or automated searches do not always yield consistent results. The Payload Communications Manager (PAYCOM) team, whose members speak directly with the ISS onboard crew with respect to NASA payload operations, has found a creative way to reformat a mandatory Daily Report to organize action items, standing reminders, significant events, and other comments. While the report keeps others appraised of PAYCOMs activities and issues of the moment, the format makes it easy to capture very brief summaries of the items in a "Roll Off Matrix", including start and stop dates, resolution, and possible applicability to future ops. The matrix provides accountability for all action items, gives direct insight into the issues surrounding various payloads and methods of dealing with them, yields indirect information on PAYCOM priorities and processes, and provides a roadmap that makes it easier to get back to extensive details if needed. This paper describes how the ISS PAYCOM Daily Report and Roll Off Matrix are organized, used, and inter-related to each other and the PAYCOM operations log. While the application is for a manned vehicle, the concepts could apply in a wide spectrum of operational settings.

Scott, David W.↗
NASA NTRS2016

Assessment of Delivery Accuracy in an Operational-Like Environment

In order to enable arrival management concepts and solutions in a Next Generation Air Transportation System (NextGen) environment, ground-based sequencing and scheduling functions were developed to support metering operations in the National Airspace System. These sequencing and scheduling tools are designed to assist air traffic controllers in developing an overall arrival strategy, from enroute down to the terminal area boundary. NASA developed a ground system concept and protoype capability called Terminal Sequencing and Spacing (TSAS) to extend metering operations into the terminal area to the runway. To demonstrate the use of these scheduling and spacing tools in an operational-like environment, the FAA, NASA, and MITRE conducted an Operational Integration Assessment (OIA) of a prototype TSAS system at the FAA's William J. Hughes Technical Center (WJHTC). This paper presents an analysis of the arrival management strategies utilized and delivery accuracy achieved during the OIA. The analysis demonstrates how en route preconditioning, in various forms, and schedule disruptions impact delivery accuracy. As the simulation spanned both enroute and terminal airspace, the use of Ground Interval Management - Spacing (GIM-S) enroute speed advisories was investigated. Delivery accuracy was measured as the difference between the Scheduled Time of Arrival (STA) and the Actual Time of Arrival (ATA). The delivery accuracy was computed across all runs conducted during the OIA, which included deviations from nominal operations which are known to commonly occur in real operations, such as schedule changes and missed approaches. Overall, 83% of all flights were delivered into the terminal airspace within +/- 30 seconds of their STA and 94% of flights were delivered within +/- 60 seconds. The meter fix delivery accuracy standard deviation was found to be between 36 and 55 seconds across all arrival procedures. The data also showed when schedule disruptions were excluded, the percentage of aircraft delivered within +/- 30 seconds was between 85 and 90% across the various arrival procedures at the meter fix. This paper illustrates the ability to meet new delivery accuracy requirements in an operational-like environment using operational systems and NATCA controller participants, while also including common events that might cause disruptions to the schedule and overall system.

Air Traffic Scheduling↗
NASA NTRS1973

CVT/PCS phase 1 integrated testing

Five breadboard experiments representing three Sortie Lab experiment disciplines were installed in a payload carrier simulator. A description of the experiments and the payload carrier simulator was provided. An assessment of the experiment interface with the simulator and an assessment of the simulator experiment support systems were presented. The results indicate that a hardware integrator for each experiment is essential; a crew chief, or mission specialist, for systems management and experimenter liaison is a vital function; a payload specialist is a practical concept for experiment integration and operation; an integration fixture for a complex experiment is required to efficiently integrate the experiment and carrier; simultaneous experiment utilization of simulator systems caused unexpected problems in meeting individual experiment requirements; experimenter traffic inside the dual-floor simulator did not hamper experiment operations; and the requirement for zero-g operation will provide a significant design challenge for some experiments.

Mcbrayer, R. O.↗
NASA NTRS2008

Long-Term Characterization of 6H-SiC Transistor Integrated Circuit Technology Operating at 500 C

NASA has been developing very high temperature semiconductor integrated circuits for use in the hot sections of aircraft engines and for Venus exploration. This paper reports on long-term 500 C electrical operation of prototype 6H-SiC integrated circuits based on epitaxial 6H-SiC junction field effect transistors (JFETs). As of this writing, some devices have surpassed 4000 hours of continuous 500 C electrical operation in oxidizing air atmosphere with minimal change in relevant electrical parameters.

Neudeck, Philip G.↗
NASA NTRS2014

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗
NASA NTRS1993

Piloted simulation of an air-ground profile negotiation process in a time-based Air Traffic Control environment

Historically, development of airborne flight management systems (FMS) and ground-based air traffic control (ATC) systems has tended to focus on different objectives with little consideration for operational integration. A joint program, between NASA's Ames Research Center (Ames) and Langley Research Center (Langley), is underway to investigate the issues of, and develop systems for, the integration of ATC and airborne automation systems. A simulation study was conducted to evaluate a profile negotiation process (PNP) between the Center/TRACON Automation System (CTAS) and an aircraft equipped with a four-dimensional flight management system (4D FMS). Prototype procedures were developed to support the functional implementation of this process. The PNP was designed to provide an arrival trajectory solution which satisfies the separation requirements of ATC while remaining as close as possible to the aircraft's preferred trajectory. Results from the experiment indicate the potential for successful incorporation of aircraft-preferred arrival trajectories in the CTAS automation environment. Fuel savings on the order of 2 percent to 8 percent, compared to fuel required for the baseline CTAS arrival speed strategy, were achieved in the test scenarios. The data link procedures and clearances developed for this experiment, while providing the necessary functionality, were found to be operationally unacceptable to the pilots. In particular, additional pilot control and understanding of the proposed aircraft-preferred trajectory, and a simplified clearance procedure were cited as necessary for operational implementation of the concept.

Williams, David H.↗
NASA NTRS2002

Console Log Keeping Made Easier - Tools and Techniques for Improving Quality of Flight Controller Activity Logs

At the Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for International Space Station (ISS), each flight controller maintains detailed logs of activities and communications at their console position. These logs are critical for accurately controlling flight in real-time as well as providing a historical record and troubleshooting tool. This paper describes logging methods and electronic formats used at the POIC and provides food for thought on their strengths and limitations, plus proposes some innovative extensions. It also describes an inexpensive PC-based scheme for capturing and/or transcribing audio clips from communications consoles. Flight control activity (e.g. interpreting computer displays, entering data/issuing electronic commands, and communicating with others) can become extremely intense. It's essential to document it well, but the effort to do so may conflict with actual activity. This can be more than just annoying, as what's in the logs (or just as importantly not in them) often feeds back directly into the quality of future operations, whether short-term or long-term. In earlier programs, such as Spacelab, log keeping was done on paper, often using position-specific shorthand, and the other reader was at the mercy of the writer's penmanship. Today, user-friendly software solves the legibility problem and can automate date/time entry, but some content may take longer to finish due to individual typing speed and less use of symbols. File layout can be used to great advantage in making types of information easy to find, and creating searchable master logs for a given position is very easy and a real lifesaver in reconstructing events or researching a given topic. We'll examine log formats from several console position, and the types of information that are included and (just as importantly) excluded. We'll also look at when a summary or synopsis is effective, and when extensive detail is needed.

Scott, David W.↗
NASA NTRS2018

Innovative Development of a Cross-Center Timeline Planning Tool

The Payload Operations Integration Center (POIC) at Marshall Space Flight Center (MSFC) supports planning, coordination and scheduling of science activities for the International Space Station (ISS) in coordination with other NASA centers, international partners, and payload developers. The ability to efficiently plan and re-plan in response to change is critical to the flight planning teams. With the achievement of supporting a fourth crew member aboard the ISS and an increasing amount of payload science activities, came the need for a dynamic, more efficient way of building timeline planning reports that could be readily updated as fast as payload science plans could change. This paper addresses software architecture considerations in the successful cross-center development of an automated planning tool with multiple data sources. It also discusses the practical implementation of a time-boxed, hybrid Agile Software Development (ASD) approach to deliver customer-driven value despite changing requirements with respect to low-Earth orbit operational planning activities. The goal of this paper is to open discussion with members of the international community and trade effective strategies for cross-center architectural and customer-developer driven collaborations, to support increasing utilization of planning and conducting science activities in space.

Pedoto, Ramon W.↗
NASA NTRSDate not supplied

NASA's Space Launch System Begins Integration, Stacking in Preparation for Artemis I Launch

The Artemis era of human lunar exploration is nearing take-off as NASA’s new super heavy-lift launch vehicle, the Space Launch System (SLS), begins stack-ing and integration operations in mid-2020 at Kennedy Space Center (KSC) in Florida. With a planned upgrade path to progressively more powerful vehicles and availability in crew and cargo configurations, SLS provides a unique and flexible launch solution to send crew, large-scale infrastructure and robotic probes to deep space. The SLS Block 1 vehicle, the initial variant to fly, is optimized for lunar missions with a proven propulsion system consisting of four liquid hydrogen (LH2)/liquid oxygen (LOX)-fed RS-25 engines and twin five-segment solid rocket boosters (SRBs). The Block 1 vehicle can also be outfitted with an industry-standard 5 m-class payload fairing (the “cargo” configuration) and will launch at least 27 metric tons (t) of mass to trans-lunar injection (TLI). SLS is the backbone of NASA’s Artemis program, which will return the agency’s human spaceflight program to the Moon for the first time since 1972. For the Artemis I mission, SLS will send an uncrewed Orion spacecraft to TLI, where it will enter a distant retrograde lunar orbit and fly 38,000 nmi past the Moon – farther than any spacecraft built for humans has ever traveled. The SLS Block 1 vehicle for Artemis I completed manufacturing in 2019. Several elements, including the upper stage, have been delivered to the Exploration Ground Systems (EGS) program at KSC and are being prepped for integration and stack-ing. The five-segment solid rocket boosters – the largest and most powerful ever built for flight – are also complete. The booster motor segments for the Artemis I flight are scheduled to ship from prime contractor Northrop Grumman’s Utah facilities and begin stacking and integration at KSC in June 2020. The SLS core stage is the largest rocket stage NASA has ever built in terms of volume and height, and includes the avionics and the tanks that feed cryogenic propellant to the four RS-25s (formerly Space Shuttle Main Engines [SSMEs]). They have been modified with an updated controller and nozzle insulation to protect them from the hotter launch environment. The SLS core stage is currently being test-ed at NASA’s Stennis Space Center (SSC) in a series of “green run” tests to verify it meets design and performance requirements. Following the green run test series, which is scheduled to culminate with a full-duration hot-fire of the four RS-25 engines, the core stage will ship to KSC and be stacked between the sol-id rocket boosters in the Vehicle Assembly Building (VAB). Integration of the vehicle will continue with the upper stage, known as the Interim Cryogenic Propulsion Stage (ICPS) and the Launch Vehicle Stage Adapter (LVSA) on the core stage. Another adapter, the Orion Stage Adapter (OSA), connects SLS to Orion and provides housing for 13 6U CubeSat payloads manifested on Artemis I. The CubeSats will be released in deep space after Orion separates from the vehicle, and the flight marks the first ride share opportunity for independent small-sats to deep space. The second major SLS variant to come online, Block 1B, replaces the single-engine ICPS with a four-engine LH2/LOX Exploration Upper Stage (EUS). This more powerful upper stage, along with other vehicle up-grades, will enable the Block 1B vehicle to launch 38-42 t to TLI, depending on crew or cargo configuration. The final evolution of the vehicle, Block 2, will onramp evolved solid rocket boosters to increase mass to TLI to 43-46 t, de-pending on crew or cargo configuration. The Block 1B/Block 2 vehicles can be outfitted with an 8.4 m-diameter payload fairing in 19.1 m or 27.4 m lengths, to provide unprecedented volume for payloads. With the initial Block 1 vehicle completely manufactured and the core stage in final testing before shipping to KSC, the SLS Program and its industry partners have made significant progress manufacturing subsequent vehicles. For the second Block 1 vehicle, the solid rocket motor segments are complete, as are the RS-25 engines with controllers. All five major components of the Artemis II core stage – the forward skirt, LOX and LH2 tanks, intertank and engine section – are manufactured and technicians are installing subsystems at NASA’s rocket factory, Michoud Assembly Facility. The RL-10 engine for the Artemis II ICPS is complete and panels have been machined for its LH2 tank. In addition, panels are machined for the vehicle’s two adapters, with welding scheduled to begin in summer 2020. Flight hard-ware is also in production for the third SLS vehicle, with several booster motor segments cast. The pace of development on the EUS has increased, with the goal to complete Critical Design Review (CDR) in December 2020. Several EUS test rings have been machined at Michoud. The EUS is designed to exe-cute a variety of missions – human spaceflight, deployment of deep-space infra-structure, or high-C3 missions to the outer solar system – with crew and cargo configurations available beginning in the mid-2020s. The near-term goal for the nation’s powerful new space exploration asset, however, is to launch the Arte-mis program, and send the first woman and the next man to the lunar surface. At the Astrodynamics Specialist Conference, the SLS program will update the community on the progress of the initial Block 1 vehicle in final green run test-ing, integration and stacking. In addition, this paper will provide an update to the community on the manufacturing status of subsequent Block 1 and Block 1B vehicles.

Steve Creech↗
NASA NTRS2017

Mars 2020 Model Based Systems Engineering Pilot

The pilot study is led by the Integration Engineering group in NASA's Launch Services Program (LSP). The Integration Engineering (IE) group is responsible for managing the interfaces between the spacecraft and launch vehicle. This pilot investigates the utility of Model-Based Systems Engineering (MBSE) with respect to managing and verifying interface requirements. The main objectives of the pilot are to model several key aspects of the Mars 2020 integrated operations and interface requirements based on the design and verification artifacts from Mars Science Laboratory (MSL) and to demonstrate how MBSE could be used by LSP to gain further insight on the interface between the spacecraft and launch vehicle as well as to enhance how LSP manages the launch service. The method used to accomplish this pilot started through familiarization of SysML, MagicDraw, and the Mars 2020 and MSL systems through books, tutorials, and NASA documentation. MSL was chosen as the focus of the model since its processes and verifications translate easily to the Mars 2020 mission. The study was further focused by modeling specialized systems and processes within MSL in order to demonstrate the utility of MBSE for the rest of the mission. The systems chosen were the In-Flight Disconnect (IFD) system and the Mass Properties process. The IFD was chosen as a system of focus since it is an interface between the spacecraft and launch vehicle which can demonstrate the usefulness of MBSE from a system perspective. The Mass Properties process was chosen as a process of focus since the verifications for mass properties occur throughout the lifecycle and can demonstrate the usefulness of MBSE from a multi-discipline perspective. Several iterations of both perspectives have been modeled and evaluated. While the pilot study will continue for another 2 weeks, pros and cons of using MBSE for LSP IE have been identified. A pro of using MBSE includes an integrated view of the disciplines, requirements, and verifications leading up to launch. The model allows IE to understand the relationships between disciplines throughout test activities and verifications. Additionally, the relationships between disciplines and integration tasks are generally consistent. The model allows for the generic relationships and tasks to be captured and used throughout multiple mission models should LSP further pursue MBSE. A con of MBSE is the amount of time it takes upfront to understand MBSE and create a useful model. The upfront time it takes to create a useful model is heavily discussed in MBSE literature and is a consistent con throughout the known applications of MBSE. The need to understand SysML and the software chosen also poses the possibility of a "bottleneck" or one person being the sole MBSE user for the working group. The utility of MBSE will continue to be evaluated through the remainder of the study. In conclusion, the original objectives of the pilot study were to use artifacts from MSL to model key aspects of Mars 2020 and demonstrate how MBSE could be used by LSP to gain insight into the spacecraft and launch vehicle interfaces. Progress has been made in modeling and identifying the utility of MBSE to LSP IE and will continue to be made until the pilot study's conclusion in mid-August. The results of this study will produce initial models, modeling instructions and examples, and a summary of MBSE's utility for future use by LSP.

Dukes, Alexandra Marie↗
NASA NTRS1966

Progress of analog-hybrid computation

Review of fast analog/hybrid computer systems, integrated operational amplifiers, electronic mode-control switches, digital attenuators, and packaging techniques

ELECTRONIC SWITCH↗
NASA NTRS1970

Study of techniques for redundancy verification without disrupting systems, phases 1-3

The problem of verifying the operational integrity of redundant equipment and the impact of a requirement for verification on such equipment are considered. Redundant circuits are examined and the characteristics which determine adaptability to verification are identified. Mutually exclusive and exhaustive categories for verification approaches are established. The range of applicability of these techniques is defined in terms of signal characteristics and redundancy features. Verification approaches are discussed and a methodology for the design of redundancy verification is developed. A case study is presented which involves the design of a verification system for a hypothetical communications system. Design criteria for redundant equipment are presented. Recommendations for the development of technological areas pertinent to the goal of increased verification capabilities are given.

Source record↗
NASA NTRS1973

Steady-state simulation program for attitude control propulsion systems

The formulation and the engineering equations employed in the steady state attitude control propulsion system simulation program are presented. The objective of this program is to aid in the preliminary design and development of propulsion systems used for spacecraft attitude control. The program simulates the integrated operation of the many interdependent components typically comprising an attitude control propulsion system. Flexibility, generality, ease of operation, and speed consistent with adequate accuracy were overriding considerations during the development of this program. Simulation modules were developed representing the various types of fluid components typically encountered in an attitude control propulsion system. These modules are basically self-contained and may be arranged by the program user into desired configuration through the program input data.

Heinmiller, P. J.↗
NASA NTRS1972

Power source considerations for Grand Tour missions.

At the present time, there exists no known power source that will satisfy the power, weight, lifetime, and other stringent requirements of an extended outer-planet mission. Exploratory studies indicate the need for a solar-independent power source capable of supplying approximately 500 W of power over mission lifetimes of up to 12 years. The only known power source which can possibly meet these requirements, in the 1975 to 1979 time period, is a radioisotope thermoelectric generator (RTG). In 1969 a program began to develop a long-life, plutonium-fueled radioisotope thermoelectric power system. Aspects of spacecraft configuration are discussed together with power source requirements, RTG/spacecraft integration, operational details, and problems of safety.

Merrill, O. S.↗
NASA NTRS1973

A rigorous cosmic-ray transport equation with no restrictions on particle energy.

A new transport equation for the cosmic-ray omnidirectional intensity is obtained. This equation follows exactly from the coupled pair of differential moment equations we presented earlier. It can be characterized as a nonlocal convection-diffusion equation in which the usual transport coefficients are replaced by time integral operators. The nonlocal equation is shown to reduce to the standard convection-diffusion form if the adiabatic approximation can be applied. In general, the adiabatic approximation does not apply; however, by going to the limits of infinite and zero gyroradius and, in addition, applying the adiabatic approximation, the large- and small-gyroradius transport theories due originally to Jokipii are regained. The validity of these theories as asymptotic limits and as approximate theories in the interplanetary magnetic field is discussed.

Klimas, A. J.↗