Search NASA⌕ Search

SEARCH · Search NASA

Results for “Design Safety”

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 343 records · Page 19

Using computer graphics to enhance astronaut and systems safety

The Operator Station Design System (OSDS), a technique of applied computer graphics featuring a flexible interactive software package, is presented in terms of man-machine analyses, flight operations, and systems engineering. In man-machine analyses, the OSDS was used to determine if viewing from the Shuttle Remote Manipulator System was satisfactory and to identify requirements for a pallet-mounted television camera. In another study, extravehicular activity was analyzed using the example of emergency access to latches should they fail in orbit. In terms of flight operations, OSDS can be used to evaluate array monitoring of a solar array power system complex and to provide animated scenarios of mission operations. The most important application of OSDS is in relation to systems engineering, as OSDS can be used to analyze spacecraft and payload design and integration. Payload configurations are included.

Brown, J. W.↗

A Machine Learning Approach to Improve Air Traffic Management Initiatives

Collaborating closely with commercial air carriers and related organizations, the Federal Aviation Administration(FAA) regulates air traffic and ensures the safety and efficiency of air operations. Air traffic controllers make strategic decisions, such as delaying, rerouting, or canceling flights, partly based on guidance provided by the FAA’s Air TrafficControl System Command Center (ATCSCC). The guidance includes, among other things, control measures known asTraffic Management Initiatives (TMIs) designed to enhance safety and improve operational efficiency. TMIs play a crucial role in managing the demand and capacity within the U.S. National Airspace System (NAS). Two major TMIs that are routinely used (primarily to mitigate the adverse effects of bad weather) are Ground Delay Programs (GDPs) andGround Stops (GSs). In a GDP, flights destined for airports facing thunderstorm activity experience delays at their origin airports. This proactive approach minimizes the risk of routing aircraft through hazardous weather conditions and also replaces (fuel burning) airborne delays with ground delays. In a GS, a temporary restriction is imposed on the departure or arrival of aircraft at a specific airport or within a designated airspace. Although other TMIs (e.g., miles-in-trail) are also implemented as part of (air) traffic flow management in the NAS, the focus of this work is on GDPs and GSs. Since TMIs, by design, lead to flight delays or cancellations, it is crucial to put in place the right set of parameters(e.g., scope and duration of the GDP). For example, when the end time of a GDP extends beyond what is necessary, it imposes unnecessary delays on departing flights. This situation could occur as a result of inaccurate prediction of the(required) duration of the GDP based on the weather forecast. On the other hand, if a GDP ends prematurely before the underlying capacity constraints are resolved at the destination airport, it may result in airborne holding. The delicate balance lies in matching the termination of the GDP precisely with the resolution of capacity constraints, avoiding both the imposition of unnecessary ground delays and the need for airborne holding due to premature program termination.Failing to specify the right parameters for TMIs also leads to flight delays, creating a significant obstacle in managing the increasing traffic volumes causing increased work load for the controllers. To address this issue, we propose the integration of Machine Learning (ML) models in the traffic flow management(TFM) pipeline. In current operations, decisions are made by human experts based on extensive training, historical patterns, available traffic and weather data. Since we have an abundance of data from past events that tell us the likely impact of various TMIs, by ingesting historical data, properly trained ML models can offer valuable insights and aid human decision-making. With the FAA increasingly exploring advanced analytics, ML emerges as a focal point for enhancing TFM within the National Airspace System (NAS). As a first step, this study aims to provide traffic controllers with decision-making support for the issuance and adjustment of TMIs. Data analytics and machine learning have been previously employed to address some of the challenges associated with TMIs. Numerous studies have concentrated on various facets of TMI issuance, exploring factors influencing TMI parameters, including arrival rate, airport capacity, and delay prediction. For example, using weather forecasts, several statistical methods were used to produce probabilistic capacity profiles which in conjunction with deterministic models provided insights into the GDP planning process [1–4]. The downside of using deterministic models is that they rely on fixed inputs and predetermined rules, which lack the ability to account for the inherent uncertainty and variability present in real-world scenarios. In a separate series of studies, researchers aimed to predict the occurrences of GDPs and GSs. The majority of these studies utilized various supervised learning methods, including Decision Trees, Naive Bayes, Support VectorMachines, and Random Forests to analyze the influence of weather conditions and arrival demand on TMI incidents[5–8]. However, these studies primarily focused on predicting the incidence of TMIs without explicitly addressing the scope of TMIs, including their duration and their geographical coverage. Furthermore, the emphasis of these studies was largely on GDPs, given their higher frequency and longer duration when compared to GSs. A limited number of studies focused on predicting the parameters of TMIs, specifically addressing their duration and extent. In one such study focusing on optimizing the TMI parameters at San Francisco International Airport (SFO),the authors utilized a probabilistic forecast of fog [9]. They simulated various capacity scenarios based on the (fog)burn-off forecasts, selecting GDP parameters that minimized airborne and overall ground delays. However, this approach exclusively emphasizes stratus (fog) burn-off as the primary determinant of GDP and GS, neglecting other influential factors like severe weather events, runway closures, lower capacity than traffic demand, and other important variables. Given the complexity of predicting the TMI and determining its scope, we seek a more holistic approach. We aim to consider all significant factors that could impact TMIs and their parameters. What sets this research apart is the fusion of all data sources relevant to the issuance and adjustment of TMIs and it represents the first comprehensive attempt to optimize TMIs in this manner. Since this comprehensive solution involves various aspects, we break down the problem into smaller components and input all parameters into a unified model called the “TMI Adjuster”. Figure 1 shows the overall framework and the list of datasets used in each model. The objective of the TMI Adjuster module is to deliver reliable, consistent and expedited recommendations for the progression, adjustment, and termination of TMIs. The ML solution entails developing a pipeline capable of predicting the necessity of a TMI (e.g., GS or GDP) along with its various parameters. For example, in the case of a GS, this includes the scope of the GS either in terms of distance from the destination airport or based on pre-defined airspace sectors. Here, scope refers to those regions and departing airports that are subject to the GS. In this paper, we concentrate on the issuance of GSs in the three major airports in the New York area — LaGuardia(LGA), John F. Kennedy International (JFK), and Newark Liberty International (EWR). We fuse traffic, weather and other relevant aviation data from years 2017 to 2019 to train and validate the ML models. In particular, we use the following datasets: •Terminal Aerodrome Forecast (TAF): meteorological forecasts specific to each airport, issued four times a day, covering predefined time periods. •TMI data: includes all GSs and GDPs along with their respective parameters. •Aviation System Performance Metrics (ASPM): includes traffic related data such as aircraft delays, arrival, and departure rates. •Notices to Airmen (NOTAMs): utilized to extract runway closure data and manage interdependencies between terminals in close proximity. •Flight cancellation data •Airspace Flow Programs (AFP): includes information on flight airborne holdings caused by TMIs. The data preprocessing entails transforming ASPM, TMI, AFP, NOTAMs, and weather data into an hourly format and consolidating all datasets by merging them based on date and time as the primary key. The TMI Adjuster framework comprises two parallel models: one dedicated to GS and a second model focused on GDP. As previously mentioned, our specific focus is on the GS model as a multi-classification problem. In this framework, each data point of the GS model input summarizes ten hours of data. Specifically, the data loader for the GS model generates the input and output of the model as follows: at a given time step, the input includes the actual traffic, weather, and TMI data from the two-hour window before the time step, alongside the weather forecast and scheduled traffic for the next 8 hours starting from the time step. Based on this information, the output of the GS model for each time interval consists of three dimensions. The first dimension represents a binary decision on whether there should be a GS in place for the next hour or not. The second dimension is related to the scope of the GS in the United States, and the third dimension is related to the scope of the GS in Canada (i.e., to determine if the GS impacts airports in Canada).One of the challenges with TMI modeling is the sparsity of TMI events, particularly regarding its scope. To address this challenge in the scope of the GS model output, we implement grouping. The GS scope for the US region is defined based on a list of centers that should be included when the GS is in place. With 20 centers in the US, we utilized historical data to group them into 4 categories. In particular, we summarized our historical data in a graph format where nodes represent centers, and link weights are defined based on the co-occurrence of centers in the scope parameter ofTMIs. By identified strongly connected components in this graph, we were able to partition the centers into four groups. We consider two model structures for the GS Model. Firstly, a hierarchical classification model [10], where the human decision-making for a GS is of hierarchical nature. The decision-maker first decides whether there is a need fora GS, and if the answer is yes, determines the scope. A hierarchical classification model organizes the problem into a class hierarchy, typically a tree or a Directed Acyclic Graph (DAG) structure, and considers the dependency of the decision in the previous step to the next component [10]. Here, we employ the local classifier per level approach, which involves training one multi-class classifier for each level of the class hierarchy. The second structure is the independent structure. In this setting, as the name suggests, we do not consider the dependency of the decisions in the different dimensions of the output of the model. Instead, for each dimension, we train a multi-class classifier independently. Table 1 summarizes GS model statistics for training, validation and testing. The table documents the effect of limiting data to the time steps when there was actually a TMI in place or when a TMI had just terminated. This resulted in a more balanced distribution of the GS class(GS positive class)versus “No GS”(GS negative class), which might help the training process. While JFK and LGA follow very similar distributions, with 40% and 42% GS positive class respectively, EWR has proportionally fewer GS incidents at 28%. Our subsequent phase involves evaluating the performance of both hierarchical structure and independent structure using different state-of-the-art multi-class classifier models such as Random Forest, Decision Trees, K-nearest Neighbors, and Logistic Regression and forecast the duration and scope of the GSs.

Farzan Masrour Shalmani↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IVV) Program, with Software Assurance Research Program support, extracted FM architectures across the IVV portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IVV projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management.

Fitz, Rhonda↗

Initial Design Guidelines for Onboard Automation of Flight Path Management

Achieving the National Academy of Science’s vision of advanced aerial mobility will depend on significant developments in automation to achieve safe and efficient operations. Flight path management (FPM), a major category of automation functionality needed to achieve this vision, will provide dynamic management of an aircraft’s flight path, ensuring that it remains feasible to fly to mission completion, deconflicted from hazards, coordinated with other traffic, flexible to accommodate future disturbances, and optimized to meet business objectives. While efforts are underway to advance FPM technology for the Urban Air Mobility application, initial design guidelines are presented for FPM automation capabilities to achieve each of these objectives based on 15+ years of prior FPM automation research and development. Methods to efficiently account for uncertainty in the prediction of trajectories are described, as are additional considerations for prioritizing safety in the design of FPM automation capabilities and interactions between aircraft. Recommendations are supported by extensive experience gained via previous work with the FPM reference automation system, Autonomous Operations Planner, developed by NASA. By employing capable FPM automation supported by cooperative operational flight rules and information sharing, future aircraft operators will benefit from an increased ability to plan and execute safe and efficient flights and to achieve mission success in a dynamic airspace.

Flight Path Management, FPM, AOP, UAM, deconflicti↗

Initial Design Guidelines for Onboard Automation of Flight Path Management

Achieving the National Academy of Science’s vision of advanced aerial mobility will depend on significant developments in automation to achieve safe and efficient operations. Flight path management (FPM), a major category of automation functionality needed to achieve this vision, will provide dynamic management of an aircraft’s flight path, ensuring that it remains feasible to fly to mission completion, deconflicted from hazards, coordinated with other traffic, flexible to accommodate future disturbances, and optimized to meet business objectives. While efforts are underway to advance FPM technology for the Urban Air Mobility application, initial design guidelines are presented for FPM automation capabilities to achieve each of these objectives based on 15+ years of prior FPM automation research and development. Methods to efficiently account for uncertainty in the prediction of trajectories are described, as are additional considerations for prioritizing safety in the design of FPM automation capabilities and interactions between aircraft. Recommendations are supported by extensive experience gained via previous work with the FPM reference automation system, Autonomous Operations Planner, developed by NASA. By employing capable FPM automation supported by cooperative operational flight rules and information sharing, future aircraft operators will benefit from an increased ability to plan and execute safe and efficient flights and to achieve mission success in a dynamic airspace.

Flight Path Management↗

Off-design temperature effects on nuclear fuel pins for an advanced space-power-reactor concept

An exploratory out-of-reactor investigation was made of the effects of short-time temperature excursions above the nominal operating temperature of 990 C on the compatibility of advanced nuclear space-power reactor fuel pin materials. This information is required for formulating a reliable reactor safety analysis and designing an emergency core cooling system. Simulated uranium mononitride (UN) fuel pins, clad with tungsten-lined T-111 (Ta-8W-2Hf) showed no compatibility problems after heating for 8 hours at 2400 C. At 2520 C and above, reactions occurred in 1 hour or less. Under these conditions free uranium formed, redistributed, and attacked the cladding.

Bowles, K. J.↗

SOFIA: Flying the Telescope

The primary focus of this paper is how the flight test team for the Stratospheric Observatory For Infrared Astronomy (SOFIA) re-cast an extensive developmental test program to meet key milestones while simultaneously ensuring safe certification of the airframe and delivery of an operationally relevant platform, ultimately saving the overall program from financial demise. Following a brief introduction to the observatory and what it is designed to do, SOFIAs planned developmental test program is summarized, including analysis and design philosophy, envelope expansion, model validation and airframe certification. How NASA used lessons learned from other aircraft that employed open cavities in flight is explained as well as how and why the chosen design was selected. The approach to aerodynamic analysis, including bare airframe testing, wind tunnel testing, computational fluid dynamics and finite element modeling proved absolutely critical. Despite a solid analytical foundation, many unknowns remained. History provides several examples of disastrous effects on both systems and flight safety if cavity design is not approached properly. For these reasons, an extensive test plan was developed to ensure a safe and thorough build-up for envelope expansion, airframe certification and early science missions. Unfortunately, as is often the case, because of chronic delays in overall program execution, severe schedule and funding pressures were present. If critical milestones were not met, domestic as well as international funding was in serious jeopardy, and the demise of the entire program loomed large. Concentrating on rigorous model validation, the test team challenged certification requirements, increased test efficiency and streamlined engineering analysis. This resulted in the safe reduction of test point count by 72%, meeting all program milestones and a platform that soundly satisfied all operational science requirements. Results from early science missions are shown and a proof of concept mission for which SOFIA was opportunely positioned is showcased. Success on this time-critical mission to observe a rare astronomical event proved the usefulness of an airborne observatory and the value in waiting for the capability provided by SOFIA. Finally, lessons learned in the test program are presented with emphasis on how lessons from previous aircraft and successful test programs were applied to SOFIA. Effective application of these lessons was crucial to the success of the SOFIA flight test program. SOFIA is an international cooperative program between NASA and the German Space Agency, DLR. It is a 2.5 meter (100-inch) telescope mounted in a Boeing 747SP aircraft used for astronomical observations at altitudes above 35,000 feet. SOFIA will accommodate a host of scientific instruments from the international science community and has a planned operational lifespan of more than 20 years.

Asher, Troy A.↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

Project EGRESS: Earthbound Guaranteed Reentry from Space Station. the Design of an Assured Crew Recovery Vehicle for the Space Station

Unlike previously designed space-based working environments, the shuttle orbiter servicing the space station will not remain docked the entire time the station is occupied. While an Apollo capsule was permanently available on Skylab, plans for Space Station Freedom call for a shuttle orbiter to be docked at the space station for no more than two weeks four times each year. Consideration of crew safety inspired the design of an Assured Crew Recovery Vehicle (ACRV). A conceptual design of an ACRV was developed. The system allows the escape of one or more crew members from Space Station Freedom in case of emergency. The design of the vehicle addresses propulsion, orbital operations, reentry, landing and recovery, power and communication, and life support. In light of recent modifications in space station design, Project EGRESS (Earthbound Guaranteed ReEntry from Space Station) pays particular attention to its impact on space station operations, interfaces and docking facilities, and maintenance needs. A water-landing medium-lift vehicle was found to best satisfy project goals of simplicity and cost efficiency without sacrificing safety and reliability requirements. One or more seriously injured crew members could be returned to an earth-based health facility with minimal pilot involvement. Since the craft is capable of returning up to five crew members, two such permanently docked vehicles would allow a full evacuation of the space station. The craft could be constructed entirely with available 1990 technology, and launched aboard a shuttle orbiter.

Source record↗

The Bunny: A simulated commercial air transportation study

The Bunny is a single-engine, 100 passenger commercial transport designed to serve the high density short-to-medium range markets in AEROWORLD. The aircraft's design range is 10,000 feet at a cruise velocity of 30 ft/s. The aircraft features a low wing which incorporates polyhedral for roll control. Yaw and pitch control are accomplished by a rudder and elevator, respectively. Propulsion is provided by a nose-mounted Astro 15 electric motor powered by thirteen 1.2 V, 1000 mah batteries with a Zinger 12-6 propeller. The aircraft is structurally designed with a safety factor of 1.5 and is constructed primarily of balsa, bass, and birch wood. Passenger seating is arranged on two levels, with three-abreast on the lower level and two-abreast on the upper level. The factors which had the most significant influence on the final design were the direct operating cost and the take-off distance. The primary strength of The Bunny is its ability to compete economically with the HB-40. At full capacity and mid-range fuel costs, the cost per seat per thousand feet (CPSK) of this aircraft is 25% less than the HB-40. Another principal strength is its ability to operate in all airports in AEROWORLD. Also, The Bunny's two-piece removable wing is an advantage from a transportability standpoint.

Fulton, David↗

The Second Joint NASA/FAA/DoD Conference on Aging Aircraft

The purpose of the Conference was to bring together world leaders in aviation safety research, aircraft design and manufacturing, fleet operation and aviation maintenance to disseminate information on current practices and advanced technologies that will assure the continued airworthiness of the aging aircraft in the military and commercial fleets. The Conference included reviews of current industry practices, assessments of future technology requirements, and status of aviation safety research. The Conference provided an opportunity for interactions among the key personnel in the research and technology development community, the original equipment manufacturers, commercial airline operators, military fleet operators, aviation maintenance, and aircraft certification and regulatory authorities. Conference participation was unrestricted and open to the international aviation community. Appendix B contains the name and addresses of the 623 participants in the Conference.

Harris, Charles E.↗

The Second Joint NASA/FAA/DOD Conference on Aging Aircraft

The purpose of the Conference was to bring together world leaders in aviation safety research, aircraft design and manufacturing, fleet operation and aviation maintenance to disseminate information on current practices and advanced technologies that will assure the continued airworthiness of the aging aircraft in the military and commercial fleets. The Conference included reviews of current industry practices, assessments of future technology requirements, and status of aviation safety research. The Conference provided an opportunity for interactions among the key personnel in the research and technology development community, the original equipment manufacturers, commercial airline operators, military fleet operators, aviation maintenance, and aircraft certification and regulatory authorities. Conference participation was unrestricted and open to the international aviation community.

Harris, Charles E.↗

Sea State and Weather Capability for NASA's Constellation Program

Marine weather and related parameters such as wind, ocean wave height and period, air temperature, sea surface temperature, visibility, and potential for icing are critical to the design, operation, and safety of crewed space vehicles. The National Aeronautics and Space Administration's (NASA's) Constellation Program requires detailed assessment of marine weather related parameters that may be encountered during launch, abort, landing, and crew rescue operations for the crewed Axes/Orion space vehicles. This information is required for both space vehicle design and operational purposes. The space vehicles must be designed such that they cam withstand the environment they are likely to encounter. The crewed Axes/Orion space vehicles will launch from NASA's Kennedy Space Center (KSC), Florida for both International Space Station (ISS) missions with 51.6deg inclination orbits and lunar missions with approximately 280 inclination orbits. Since both missions will fly ever the Atlantic Ocean on ascent to orbit and will fly over the Pacific Ocean on descent from orbit, an unlikely but possible emergency abort could require parachuting the Orion capsule and crew into the ocean. This situation could potentially put the crew in an isolated and hazardous environment for severn hours while they await rescue. Therefore, abort, landing, and crew rescue elements of the Constellation Program must address weather related parameters on a global scale. This paper describes buoy measurement data, sea surface temperature satellite data, and sea state computer model data that are being utilized by the Constellation Program to address these design and operational issues.

Barbre, R. E.↗

Sea State and Weather Assessment Capability for NASA's Constellation Program

Marine weather and related parameters such as wind, ocean wave height and period, air temperature, sea surface temperature, visibility, and potential for icing are critical to the design, operation, and safety of crewed space vehicles. The National Aeronautics and Space Administration's (NASA's) Constellation Program requires detailed assessment of marine weather related parameters that may be encountered during launch, abort, landing, and crew rescue operations for the crewed Ares/Orion space vehicles. This information is required for both space vehicle design and operational purposes. The space vehicles must be designed such that they can withstand the environment they are likely to encounter. The crewed Ares/Orion space vehicles will launch from NASA's Kennedy Space Center (KSC), Florida for both International Space Station (ISS) missions with 51.6 o inclination orbits and lunar missions with approximately 28 inclination orbits. Since both missions will fly over the Atlantic Ocean on ascent to orbit and will fly over the Pacific Ocean on descent from orbit, an unlikely but possible emergency abort could require parachuting the Orion capsule and crew into the ocean. This situation could potentially put the crew in an isolated and hazardous environment for several hours while they await rescue. Therefore, abort, landing, and crew rescue elements of the Constellation Program must address weather related parameters on a global scale. This paper describes buoy measurement data, sea surface temperature satellite data, and sea state computer model data that are being utilized by the Constellation Program to address these design and operational issues.

Barbre, B. J.↗

Validating the Autonomous Science Agent

This paper describes the validation process for the Autonomous Science Agent, a software agent that will fly onboard the EO-1 spacecraft from 2003-2004. This agent will recognize science events, retarget the spacecraft to respond to the science events, and reduce data downlink to only the highest value science data. The autonomous science agent has been designed using a layered architectural approach with specific redundant safeguards to reduce the risk of an agent malfunction to the EO-1 spacecraft. This 'safe' design is also in the process of being thoroughly validated by informal validation methods and extensive testing. This paper describes the analysis used to define agent safety, elements of the design that increase the safety of the agent, and the process being used to validate agent safety prior to the agent software controlling the spacecraft.

agent safety↗

Configurable Multi-Purpose Processor

Advancements in technology have allowed the miniaturization of systems used in aerospace vehicles. This technology is driven by the need for next-generation systems that provide reliable, responsive, and cost-effective range operations while providing increased capabilities such as simultaneous mission support, increased launch trajectories, improved launch, and landing opportunities, etc. Leveraging the newest technologies, the command and telemetry processor (CTP) concept provides for a compact, flexible, and integrated solution for flight command and telemetry systems and range systems. The CTP is a relatively small circuit board that serves as a processing platform for high dynamic, high vibration environments. The CTP can be reconfigured and reprogrammed, allowing it to be adapted for many different applications. The design is centered around a configurable field-programmable gate array (FPGA) device that contains numerous logic cells that can be used to implement traditional integrated circuits. The FPGA contains two PowerPC processors running the Vx-Works real-time operating system and are used to execute software programs specific to each application. The CTP was designed and developed specifically to provide telemetry functions; namely, the command processing, telemetry processing, and GPS metric tracking of a flight vehicle. However, it can be used as a general-purpose processor board to perform numerous functions implemented in either hardware or software using the FPGA s processors and/or logic cells. Functionally, the CTP was designed for range safety applications where it would ultimately become part of a vehicle s flight termination system. Consequently, the major functions of the CTP are to perform the forward link command processing, GPS metric tracking, return link telemetry data processing, error detection and correction, data encryption/ decryption, and initiate flight termination action commands. Also, the CTP had to be designed to survive and operate in a launch environment. Additionally, the CTP was designed to interface with the WFF (Wallops Flight Facility) custom-designed transceiver board which is used in the Low Cost TDRSS Transceiver (LCT2) also developed by WFF. The LCT2 s transceiver board demodulates commands received from the ground via the forward link and sends them to the CTP, where they are processed. The CTP inputs and processes data from the inertial measurement unit (IMU) and the GPS receiver board, generates status data, and then sends the data to the transceiver board where it is modulated and sent to the ground via the return link. Overall, the CTP has combined processing with the ability to interface to a GPS receiver, an IMU, and a pulse code modulation (PCM) communication link, while providing the capability to support common interfaces including Ethernet and serial interfaces boarding a relatively small-sized, lightweight package.

Valencia, J. Emilio↗

Some Challenges in the Design of Human-Automation Interaction for Safety-Critical Systems

Increasing amounts of automation are being introduced to safety-critical domains. While the introduction of automation has led to an overall increase in reliability and improved safety, it has also introduced a class of failure modes, and new challenges in risk assessment for the new systems, particularly in the assessment of rare events resulting from complex inter-related factors. Designing successful human-automation systems is challenging, and the challenges go beyond good interface development (e.g., Roth, Malin, & Schreckenghost 1997; Christoffersen & Woods, 2002). Human-automation design is particularly challenging when the underlying automation technology generates behavior that is difficult for the user to anticipate or understand. These challenges have been recognized in several safety-critical domains, and have resulted in increased efforts to develop training, procedures, regulations and guidance material (CAST, 2008, IAEA, 2001, FAA, 2013, ICAO, 2012). This paper points to the continuing need for new methods to describe and characterize the operational environment within which new automation concepts are being presented. We will describe challenges to the successful development and evaluation of human-automation systems in safety-critical domains, and describe some approaches that could be used to address these challenges. We will draw from experience with the aviation, spaceflight and nuclear power domains.

systems engineering↗