Search NASA⌕ Search

SEARCH · Search NASA

Results for “risk requirements architectures”

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 253 records · Page 14

Jupiter Europa Orbiter Architecture Definition Process

The proposed Jupiter Europa Orbiter mission, planned for launch in 2020, is using a new architectural process and framework tool to drive its model-based systems engineering effort. The process focuses on getting the architecture right before writing requirements and developing a point design. A new architecture framework tool provides for the structured entry and retrieval of architecture artifacts based on an emerging architecture meta-model. This paper describes the relationships among these artifacts and how they are used in the systems engineering effort. Some early lessons learned are discussed.

requirements analysis↗

NASA’s Surface Deformation and Change Mission Study

The National Academies of Science, Engineering and Medicine 2017 Decadal Survey of Earth Science and Applications identified geodetic measurements of surface deformation and related change as one of the top five “observables” to be prioritized in NASA’s future program. In response, NASA commissioned a multi-center Surface Deformation and Change(SDC) team to perform a five year study of mission architectures that would support SDC observables and provide the most value to the diverse science and applications communities it serves. The study is being conducted in phases, in which the science and applications capabilities identified in the Decadal Survey are refined, candidate architectures and associated technologies to support these needs are identified, architectures are assessed against a science value framework specific to SDC, and recommendations to NASA are made. Ultimately, NASA will decide which amongst these recommendations will proceed to mission formulation. As synthetic aperture radar (SAR) was identified as the prime sensor technology to satisfy SDC observational needs, a key component of the SDC study is to assess the current state of the art in SAR sensor and supporting technology. The number of SAR systems, both civil and commercial, is growing rapidly, requiring that mission architectures not only consider technology, but availability of data from other missions, possible partnerships or collaborations, and even data purchase. The mechanism for assessment involves development of an end-to-end science performance evaluation tool for multi-satellite con-stellations, which feeds into a science value framework that con-siders science performance, technological programmatic risks, and cost. This paper will present an overview of the ongoing study including the candidate architectures and the technology road map needed to achieve the objectives of the mission.

Stephen Horst↗

An Approach to Automate tools for the Risk Assessment of Digital Instrumentation and Control Systems

Reliable digital instrumentation and control systems (DI&C) are integral for sustaining the continued operation of nuclear power plants. These systems ensure that nuclear reactors operate safely, efficiently, and within regulatory requirements. Yet, the cost of designing and licensing new nuclear DI&C can be prohibitively expensive. Under the U.S. Department of Energy Light Water Reactor Sustainability Program, Idaho National Laboratory has developed a framework for supporting the risk-informed design of DI&C systems by offering methods to support the identification, quantification, and evaluation of risks for various DI&C design architectures. The framework indicates potential software failure modes and provides pathways for quantifying the potential for these software failures, including common cause failures. Using the framework’s systematic approach, challenges for assessing risks within new and existing nuclear DI&C systems can be reduced. Nevertheless, the current framework can be further improved using the convenience of automation. This paper introduces the development of Software for the Hazard Identification and Evaluation of Digital Systems (SHIELDS). SHIELDS is an engineering software package that enables the identification, elimination, and mitigation of potential risks and reduces the burden of deploying reliable DI&C systems. This work introduces plans and techniques to digitize and improve the manual risk assessment modules of the framework. These improvements will save time and increase the repeatability and usability of the framework, making it more accessible to a wider range of users. Ultimately, this introduces SHIELDS and how its modules support efficient development of safe and reliable DI&C systems.

46 - INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AN↗

Duplex Direct Data Distribution System

The NASA Glenn Research Center (GRC) is developing and demonstrating communications and network technologies that are helping to enable the near-Earth space Internet. GRC envisions several service categories. The first of these categories is direct data distribution or D3 (pronounced "D-cubed"). Commercially provided D3 will make it possible to download a data set from a spacecraft, like the International Space Station. as easily as one can extract a file from a remote server today, using a file transfer protocol. In a second category, NASA spacecraft will make use of commercial satellite communication (SATCOM) systems. Some of those services will come from purchasing time on unused transponders that cover landmasses. While it is likely there will be gaps in service coverage, Internet services should be available using these systems. This report addresses alternative methods of implementing a full duplex enhancement of the GRC developed experimental Ka-Band Direct Data Distribution (D3) space-to-ground communication link. The resulting duplex version is called the Duplex Direct Data Distribution (D4) system. The D4 system is intended to provide high-data-rate commercial direct or internet-based communications service between the NASA spacecraft in low earth orbit (LEO) and the respective principal investigators associated with these spacecraft. Candidate commercial services were assessed regarding their near-term potential to meet NASA requirements. Candidates included Ka-band and V-band geostationary orbit and non-geostationary orbit satellite relay services and direct downlink ("LEO teleport") services. End-to-end systems concepts were examined and characterized in terms of alternative link layer architectures. Alternatives included a Direct Link, a Relay Link, a Hybrid Link, and a Dual Mode Link. The direct link assessment examined sample ground terminal placements and antenna angle issues. The SATCOM-based alternatives examined existing or proposed commercial SATCOM services that could be available in the 2005 time frame. The alternatives were evaluated and compared in terms of average daily system throughput and cost per bit. Throughput was estimated based on hypothetical scenarios supporting the International Space Station and polar orbiting missions. The feasibility of using standard TCP and a modified TCP was evaluated and risks were identified. An estimate of the TCP acknowledgment data rate required to support a return channel rate of 622 Mbps was developed using OPNET.

Greenfield, Israel↗

Asteroid Redirect Crewed Mission Space Suit and EVA System Architecture Trade Study

The Asteroid Redirect Crewed Mission (ARCM) requires a Launch/Entry/Abort (LEA) suit capability and short duration Extra Vehicular Activity (EVA) capability for Orion. The EVAs will involve a two-person crew for approximately four hours. Currently, two EVAs are planned with one contingency EVA in reserve. Providing this EVA capability is very challenging due to system level constraints and a new and unknown environment. The goal of the EVA architecture for ARCM is one that builds upon previously developed technologies and lessons learned, and that accomplishes the ARCM mission while providing a stepping stone to future missions and destinations. The primary system level constraints are to 1) minimize system mass and volume and 2) minimize the interfacing impacts to the baseline Orion design. In order to minimize the interfacing impacts and to not perturb the baseline Orion schedule, the concept of adding "kits" to the baseline system is proposed. These kits consist of: an EVA kit (converts LEA suit to EVA suit), EVA Servicing and Recharge Kit (provides suit consumables), the EVA Tools, Translation Aids & Sample Container Kit (the tools and mobility aids to complete the tasks), the EVA Communications Kit (interface between the EVA radio and the MPCV), and the Cabin Repress Kit (represses the MPCV between EVAs). This paper will focus on the trade space, analysis, and testing regarding the space suit (pressure garment and life support system). Historical approaches and lessons learned from all past EVA operations were researched. Previous and current, successfully operated EVA hardware and high technology readiness level (TRL) hardware were evaluated, and a trade study was conducted for all possible pressure garment and life support options. Testing and analysis was conducted and a recommended EVA system architecture was proposed. Pressure garment options that were considered for this mission include the currently in-use ISS EVA Mobility Unit (EMU), all variations of the Advanced Crew Escape Suit (ACES), and the Exploration Z-suit. For this mission, the pressure garment that was selected is the Modified ACES (MACES) with EVA enhancements. Life support options that were considered included short closed-loop umbilicals, long open-loop umbilicals, the currently in-use ISS EMU Portable Life Support System (PLSS), and the currently in development Exploration PLSS. For this mission, the life support option that was selected is the Exploration PLSS. The greatest risk in the proposed architecture is viewed to be the comfort and mobility of the baseline MACES and the delicate balance between adding more mobility features while not compromising landing safety. Feasibility testing was accomplished in low fidelity analogs and in the JSC Neutral Buoyancy Laboratory (NBL) to validate the concept before a final recommendation on the architecture was made. The proposed architecture was found to meet the mission constraints, but much more work is required to determine the details of the required suit upgrades, the integration with the PLSS, and the rest of the tools and equipment required to accomplish the mission. This work and further definition of the remaining kits will be conducted in government fiscal year 14.

Blanco, Raul A.↗

Lunar Water ISRU Measurement Study (LWIMS): Establishing a Measurement Plan for Identification and Characterization of a Water Reserve

NASA’s Artemis program aims to achieve a sustainable lunar presence by 2028. To carry out sustained crewed surface operations, In-Situ Resource Utilization (ISRU), which would use lunar resources (e.g., water) to produce mission consumables, will be critical. Water-bearing materials have been identified at both lunar poles, butthe nature and extent of this resource is not well understood. Identification of the presence of water alone is not adequate for ISRU architecture planning and engineering design. The Lunar Water ISRU Measurement Study (LWIMS) assessed and defined the type, amount, and fidelity of the information and measurements needed to select mining locations for lunar water ISRU and to define requirements for ISRU hardware and architecture development. Current ISRU requirements were used to define a water ‘reserve’ in this context. A measurement plan to achieve these goals includes three key elements; a predictive ‘water favorability’ model to identify and map potential deposits, continued assessment of orbital data, and three types of landed missions to make direct ground measurements. Corresponding mission scenarios and instrument suites will depend on risk posture and timelines for ISRU implementation.

In situ resource utilization↗

Neural Architecture and Feature Search for Predicting the Ridership of Public Transportation Routes

Accurately predicting the ridership of public-transit routes provides substantial benefits to both transit agencies, who can dispatch additional vehicles proactively before the vehicles that serve a route become crowded, and to passengers, who can avoid crowded vehicles based on publicly available predictions. The spread of the coronavirus disease has further elevated the importance of ridership prediction as crowded vehicles now present not only an inconvenience but also a public-health risk. At the same time, accurately predicting ridership has become more challenging due to evolving ridership patterns, which may make all data except for the most recent records stale. One promising approach for improving prediction accuracy is to fine-tune the hyper-parameters of machine-learning models for each transit route based on the characteristics of the particular route, such as the number of records. However, manually designing a machine-learning model for each route is a labor-intensive process, which may require experts to spend a significant amount of their valuable time. To help experts with designing machine-learning models, we propose a neural-architecture and feature search approach, which optimizes the architecture and features of a deep neural network for predicting the ridership of a public-transit route. Our approach is based on a randomized local hyper-parameter search, which minimizes both prediction error as well as the complexity of the model. We evaluate our approach on real-world ridership data provided by the public transit agency of Chattanooga, TN, and we demonstrate that training neural networks whose architectures and features are optimized for each route provides significantly better performance than training neural networks whose architectures and features are generic.

Ayman, Afiya↗

A Testbed Demonstration of an Intelligent Archive in a Knowledge Building System

The last decade's influx of raw data and derived geophysical parameters from several Earth observing satellites to NASA data centers has created a data-rich environment for Earth science research and applications. While advances in hardware and information management have made it possible to archive petabytes of data and distribute terabytes of data daily to a broad community of users, further progress is necessary in the transformation of data into information, and information into knowledge that can be used in particular applications in order to realize the full potential of these valuable datasets. In examining what is needed to enable this progress in the data provider environment that exists today and is expected to evolve in the next several years, we arrived at the concept of an Intelligent Archive in context of a Knowledge Building System (IA/KBS). Our prior work and associated papers investigated usage scenarios, required capabilities, system architecture, data volume issues, and supporting technologies. We identified six key capabilities of an IA/KBS: Virtual Product Generation, Significant Event Detection, Automated Data Quality Assessment, Large-Scale Data Mining, Dynamic Feedback Loop, and Data Discovery and Efficient Requesting. Among these capabilities, large-scale data mining is perceived by many in the community to be an area of technical risk. One of the main reasons for this is that standard data mining research and algorithms operate on datasets that are several orders of magnitude smaller than the actual sizes of datasets maintained by realistic earth science data archives. Therefore, we defined a test-bed activity to implement a large-scale data mining algorithm in a pseudo-operational scale environment and to examine any issues involved. The application chosen for applying the data mining algorithm is wildfire prediction over the continental U.S. This paper reports a number of observations based on our experience with this test-bed. While proof-of-concept for data mining scalability and utility has been a major goal for the research reported here, it was not the only one. The other five capabilities of an WKBS named above have been considered as well, and an assessment of the implications of our experience for these other areas will also be presented. The lessons learned through the testbed effort and presented in this paper will benefit technologists, scientists, and system operators as they consider introducing IA/KBS capabilities into production systems.

Ramapriyan, Hampapuram↗

Exploration Blueprint: Data Book

The material contained in this report was compiled to capture the work performed by the National Aeronautics and Space Administration's (NASA's) Exploration study team in the late 2002 timeframe. The "Exploration Blueprint Data Book" documents the analyses and findings of the 90-day Agency-wide study conducted from September - November 2002. During the summer of 2002, the NASA Deputy Administrator requested that a study be performed with the following objectives: - Develop the rationale for exploration beyond low-Earth orbit - Develop roadmaps for how to accomplish the first steps through humans to Mars - Develop design reference missions as a basis for the roadmaps - Make recommendations on what can be done now to effect this future This planning team, termed the Exploration Blueprint, performed architecture analyses to develop roadmaps for how to accomplish the first steps beyond LEO through the human exploration of Mars. The previous NASA Exploration Team activities laid the foundation and framework for development of NASA's Integrated Space Plan. The reference missions resulting from the analysis performed by the Exploration Blueprint team formed the basis for requirement definition, systems development, technology roadmapping, and risk assessments for future human exploration beyond low-Earth orbit. Emphasis was placed on developing recommendations on what could be done now to effect future exploration activities. The Exploration Blueprint team embraced the "Stepping Stone" approach to exploration where human and robotic activities are conducted through progressive expansion outward beyond low-Earth orbit. Results from this study produced a long-term strategy for exploration with near-term implementation plans, program recommendations, and technology investments. Specific results included the development of a common exploration crew vehicle concept, a unified space nuclear strategy, focused bioastronautics research objectives, and an integrated human and robotic exploration strategy. Recommendations from the Exploration Blueprint included the endorsement of the Nuclear Systems Initiative, augmentation of the bioastronautics research, a focused space transportation program including heavy-lift launch and a common exploration vehicle design for ISS and exploration missions, as well as an integrated human and robotic exploration strategy for Mars.

Bret G Drake↗

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗

Survey of Propulsion Technologies Applicable to Cubesats

At present, no Cubesat has flown in space featuring propulsion. This was acceptable as long as CubeSats were flown mostly as university experiments. As CubeSats become of interest to other users in the government and industry communities as well, a larger range of capabilities may be required than exhibited so far, while maintaining the uniqueness of the Cubesat platform. Propulsion capability is crucial in increasing mission capabilities of future CubeSats, such as orbit change and raising, formation flying, proximity operations, fine attitude control, or drag-make-up and de-orbit. While some of these tasks may be accomplished with propellantless devices, their applications are limited, applicable mostly to a single task, and bear their own risks. In this study, a survey was conducted of propulsion technologies applicable to CubeSats. Only few off-the-shelf design solutions exist today. The survey was thus expanded to such devices as well that are under significant development, and are approaching the required design envelope for CubeSats with respect to mass, volume, and power. In some cases, such as electric propulsion devices, CubeSat architectures themselves may need to be adapted, required to feature deployable solar arrays to increase power capabilities. Given the vast scope of this survey, only thruster technologies could be surveyed. However, valves and other feed system components, as well as their integration, are equally important, but have to be left to a future survey. Three major propulsion technology areas applicable to CubeSats emerged when conducting this review: (1) Existing technologies, such as butane systems, pulsed plasma thrusters, and vacuum arc thrusters are applicable to CubeSats today with no or only minor changes, (2) New thruster technologies under significant development, such as hydrazine monopropellant systems, ion engines, or colloid thrusters could be adapted to CubeSats with some further development, especially also in other subsystem areas such as feed systems and power processing units. They will also require increased power capabilities, and (3) emerging technologies, such as micro electrospray arrays and micro cavity discharge arrays that offer even higher flexibility due to scalability for CubeSats, and enable compact integration.

micropropulsion↗

Asteroid Redirect Crewed Mission Space Suit and EVA System Architecture Trade Study

This paper discusses the Asteroid Redirect Crewed Mission (ARCM) space suit and Extravehicular Activity (EVA) architecture trade study and the current state of the work to mature the requirements and products to the mission concept review level. The mission requirements and the resulting concept of operations will be discussed. A historical context will be presented as to present the similarities and differences from previous NASA missions. That will set the stage for the trade study where all options for both pressure garment and life support were considered. The rationale for the architecture decisions will then be presented. Since the trade study did identity risks, the subsequent tests and analyses that mitigated the risks will be discussed. Lastly, the current state of the effort will be provided.

Bowie, Jonathan T.↗

Shuttle-Derived Launch Vehicles' Capablities: An Overview

Shuttle-Derived Launch Vehicle (SDLV) concepts have been developed by a collaborative team comprising the Johnson Space Center, Marshall Space Flight Center, Kennedy Space Center, ATK-Thiokol, Lockheed Martin Space Systems Company, The Boeing Company, and United Space Alliance. The purpose of this study was to provide timely information on a full spectrum of low-risk, cost-effective options for STS-Derived Launch Vehicle concepts to support the definition of crew and cargo launch requirements for the Space Exploration Vision. Since the SDLV options use high-reliability hardware, existing facilities, and proven processes, they can provide relatively low-risk capabilities to launch extremely large payloads to low Earth orbit. This capability to reliably lift very large, high-dollar-value payloads could reduce mission operational risks by minimizing the number of complex on-orbit operations compared to architectures based on multiple smaller launchers. The SDLV options also offer several logical spiral development paths for larger exploration payloads. All of these development paths make practical and cost-effective use of existing Space Shuttle Program (SSP) hardware, infrastructure, and launch and flight operations systems. By utilizing these existing assets, the SDLV project could support the safe and orderly transition of the current SSP through the planned end of life in 2010. The SDLV concept definition work during 2004 focused on three main configuration alternatives: a side-mount heavy lifter (approximately 77 MT payload), an in-line medium lifter (approximately 22 MT Crew Exploration Vehicle payload), and an in-line heavy lifter (greater than 100 MT payload). This paper provides an overview of the configuration, performance capabilities, reliability estimates, concept of operations, and development plans for each of the various SDLV alternatives. While development, production, and operations costs have been estimated for each of the SDLV configuration alternatives, these proprietary data have not been included in this paper.

Rothschild, William J.↗

Interaction between the space transportation systems and the Space Station architecture and operations and technology requirements

This study, limited to the interaction between the Space Station and an orbital transfer vehicle, illustrates the need to include the space transportation system and the station in a synergistic analysis to determine an overall operationally efficient system that takes full advantage of the potential for the exploration and exploitation of space. Included are examples of the effects of the mission model on the selection of a possible orbit transfer vehicle design and processing procedures at the station; safe, timely, and flexible transfer vehicle trajectories from GEO to the station; mechanical assists on the station for vehicle arrivals and departures that reduce the risk of contamination and collision; and a discussion of the need for efficient procedures for vehicle maintenance and processing at the station.

Eide, Donald G.↗

Attack Surface of Wind Energy Technologies in the United States

Low cost, reliable electrical energy production from wind relies upon automation and control systems, arguably more so than traditional thermal generation. These same systems, however, can serve as the target of adversaries’ cyber-attacks. Idaho National Laboratory (INL), at the request of the Department of Energy’s (DOE’s) Office of Cybersecurity, Energy Security, and Emergency Response (CESER) and Energy Efficiency and Renewable Energy’s (EERE’s) Wind Energy Technologies Office (WETO), evaluated a generalized wind plant architecture to understand the classes of potential threat actors and the vectors that could enable a cyber-attack. This evaluation explores the attack surface of a representative wind plant, identifying potential methods and vectors that an adversary could leverage to conduct a cyber-attack. Included in this assessment are some recommended mitigations and approaches. Each recommendation requires a full security evaluation, cost/benefit analysis, and risk analysis by each owner and operator.

17 WIND ENERGY↗

X-57 Cockpit Interface Control Document (ICD-CEPT-006)

The Cockpit Interface Control Document defines the hardware interfaces between the X-57 cockpit and subsystems. It provides locational and operational information in support of ground and flight operations with details on controls and displays that include Modes of Operation, Start-Up and Shut- Down Sequence diagrams and captures the current state of the MOD II Avionics Power Architecture. There is also preliminary information of the MOD III and MOD IV configurations. Microsoft PowerPoint was chosen for the document as early development required frequent meetings with multiple customers including aircraft operators (pilots), ground operations, support contractors and power, instrumentation, and human systems integration engineers and PowerPoint enabled presentations that could be quickly modified based on customer and developer interaction. One of the driving requirements for the cockpit design was to keep the left side panel as close the stock Tecnam panel as possible to reduce the failure risk of flight critical indicators. The original annunciator panel in the left side panel was modified to alert the pilot to failures in critical X-57 subsystems and an operator audio alert capability was added for these subsystems. Power-Up switches for the aircraft low voltage 13.8 VDC systems are located at the bottom of the left side panel and center panel, the same location as the stock Tecnam 13.8 VDC switches. The switches for energizing the high voltage system were located in the overhead panel to reduce the risk of inadvertently energizing the high voltage system during the low voltage power-up sequence. The Cruise Motor ARM switches were also located in the overhead panel and correspond to the same location as the stock Tecnam ignition switches. The stock Tecnam throttle levers and prop pitch levers were retained for the X-57. The throttle levers were renamed torque levers since they controlled the commanded torque to the cruise motors. The prop pitch levers provide a commanded RPM signal to an electronic prop pitch controller. X-57 specific displays, located in the right-side panel, are driven by dedicated sensors that monitor right and left side cruise motor RPM, right and left high voltage “Traction Bus” A and B (voltage, current and power) and the Avionics Bus DC converters (A and B) voltage and current. An X-57 Multi-Function Display (MFD) located in the center panel displays CAN Bus parameters. CAN Bus architecture is not certified for flight so these displays could not be used for safety critical information but were designed to be used for test point information only.

Laura Kushner↗