Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “integrate”

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 685 records · Page 38
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗
NASA NTRS2008

Intelligent Integrated Health Management for a System of Systems

An intelligent integrated health management system (IIHMS) incorporates major improvements over prior such systems. The particular IIHMS is implemented for any system defined as a hierarchical distributed network of intelligent elements (HDNIE), comprising primarily: (1) an architecture (Figure 1), (2) intelligent elements, (3) a conceptual framework and taxonomy (Figure 2), and (4) and ontology that defines standards and protocols. Some definitions of terms are prerequisite to a further brief description of this innovation: A system-of-systems (SoS) is an engineering system that comprises multiple subsystems (e.g., a system of multiple possibly interacting flow subsystems that include pumps, valves, tanks, ducts, sensors, and the like); 'Intelligent' is used here in the sense of artificial intelligence. An intelligent element may be physical or virtual, it is network enabled, and it is able to manage data, information, and knowledge (DIaK) focused on determining its condition in the context of the entire SoS; As used here, 'health' signifies the functionality and/or structural integrity of an engineering system, subsystem, or process (leading to determination of the health of components); 'Process' can signify either a physical process in the usual sense of the word or an element into which functionally related sensors are grouped; 'Element' can signify a component (e.g., an actuator, a valve), a process, a controller, an actuator, a subsystem, or a system; The term Integrated System Health Management (ISHM) is used to describe a capability that focuses on determining the condition (health) of every element in a complex system (detect anomalies, diagnose causes, prognosis of future anomalies), and provide data, information, and knowledge (DIaK) not just data to control systems for safe and effective operation. A major novel aspect of the present development is the concept of intelligent integration. The purpose of intelligent integration, as defined and implemented in the present IIHMS, is to enable automated analysis of physical phenomena in imitation of human reasoning, including the use of qualitative methods. Intelligent integration is said to occur in a system in which all elements are intelligent and can acquire, maintain, and share knowledge and information. In the HDNIE of the present IIHMS, an SoS is represented as being operationally organized in a hierarchical-distributed format. The elements of the SoS are considered to be intelligent in that they determine their own conditions within an integrated scheme that involves consideration of data, information, knowledge bases, and methods that reside in all elements of the system. The conceptual framework of the HDNIE and the methodologies of implementing it enable the flow of information and knowledge among the elements so as to make possible the determination of the condition of each element. The necessary information and knowledge is made available to each affected element at the desired time, satisfying a need to prevent information overload while providing context-sensitive information at the proper level of detail. Provision of high-quality data is a central goal in designing this or any IIHMS. In pursuit of this goal, functionally related sensors are logically assigned to groups denoted processes. An aggregate of processes is considered to form a system. Alternatively or in addition to what has been said thus far, the HDNIE of this IIHMS can be regarded as consisting of a framework containing object models that encapsulate all elements of the system, their individual and relational knowledge bases, generic methods and procedures based on models of the applicable physics, and communication processes (Figure 2). The framework enables implementation of a paradigm inspired by how expert operators monitor the health of systems with the help of (1) DIaK from various sources, (2) software tools that assist in rapid visualization of the condition of the system, (3) analical software tools that assist in reasoning about the condition, (4) sharing of information via network communication hardware and software, and (5) software tools that aid in making decisions to remedy unacceptable conditions or improve performance.

Smith, Harvey↗
NASA NTRS2009

Submillimeter-Wave Amplifier Module with Integrated Waveguide Transitions

To increase the usefulness of monolithic millimeter-wave integrated circuit (MMIC) components at submillimeter-wave frequencies, a chip has been designed that incorporates two integrated, radial E-plane probes with an MMIC amplifier in between, thus creating a fully integrated waveguide module. The integrated amplifier chip has been fabricated in 35-nm gate length InP high-electron-mobility-transistor (HEMT) technology. The radial probes were mated to grounded coplanar waveguide input and output lines in the internal amplifier. The total length of the internal HEMT amplifier is 550 m, while the total integrated chip length is 1,085 m. The chip thickness is 50 m with the chip width being 320 m. The internal MMIC amplifier is biased through wire-bond connections to the gates and drains of the chip. The chip has 3 stages, employing 35-nm gate length transistors in each stage. Wire bonds from the DC drain and gate pads are connected to off-chip shunt 51-pF capacitors, and additional off-chip capacitors and resistors are added to the gate and drain bias lines for low-frequency stability of the amplifier. Additionally, bond wires to the grounded coplanar waveguide pads at the RF input and output of the internal amplifier are added to ensure good ground connections to the waveguide package. The S-parameters of the module, not corrected for input or output waveguide loss, are measured at the waveguide flange edges. The amplifier module has over 10 dB of gain from 290 to 330 GHz, with a peak gain of over 14 dB at 307 GHz. The WR2.2 waveguide cutoff is again observed at 268 GHz. The module is biased at a drain current of 27 mA, a drain voltage of 1.24 V, and a gate voltage of +0.21 V. Return loss of the module is very good between 5 to 25 dB. This result illustrates the usefulness of the integrated radial probe transition, and the wide (over 10-percent) bandwidth that one can expect for amplifier modules with integrated radial probes in the submillimeter-regime (>300 GHz).

Samoska, Lorene↗
NASA NTRS2008

Organizational Considerations for Implementing Systems Engineering and Integration in the Ares Projects Office

Systems Engineering and Integration (SE&I) is a critical discipline in developing new space systems. In 2005, NASA performed an internal study of 24 agency and Department of Defense (DoD) programs to evaluate methods of integrating SE&I practices and determine their effectiveness. The goal of the study was to determine the best SE&I implementation strategy for the Ares Projects Office. The study identified six SE&I organizational structures: 1. Lead systems integrator (LSI) with SE&I responsibility and government technical insight. 2a. Integration contractor with government SE&I responsibility (government insight). 2b. Integration contractor with government SE&I responsibility (government oversight). 3a. Prime contractor with SE&I responsibility (government insight). 3b. Prime contractor with SE&I responsibility (government oversight). 3c. Prime contractor with SE&I responsibility (government/industry partnership). 4a.Prime contractor with government SE&I responsibility (government insight). 4b. Prime contractor with government SE&I responsibility (government oversight). 4d.Prime contractors with total system performance responsibility (TSPR). 5. Prime contractor with government SE&I responsibility and integration products through a Federally Funded Research and Development Center (FFRDC). 6. Government/FFRDC in-house development with SE&I responsibility and function. The organizational structure used most often was number 4, using a prime contractor with government SE&I responsibility and government technical insight. However, data analyses did not establish a positive relationship between program development costs and specific SE&I organizational types, nor did it positively determine the relationship between successful programs or projects and their SE&I structure. The SE&I study reached the following conclusions: (1) Large, long-duration, technically complex programs or projects reach their technical goals, but rarely meet schedule or cost goals. NASA's recent successes have been smaller, short-duration development projects using heritage hardware/software, focused technology development, technical oversight and stable external factors. (2) Programs and projects have failed or been terminated due to lack of technical insight, relaxing of SE&I processes, and unstable external factors. (3) The study did not find a single, clear optimum SE&I organization type to fit all projects. However, while any organizational structure can be made to work, the fewer complexities in the program, the better the likelihood of success. (4) The most common successful SE&I organization structure type in the study was type 4b, where the government maintained integration responsibility, with the prime contractor providing SE&I products and the government providing technical oversight. This study was instrumental in helping the APO select organization structure 4, following the same SE&I and oversight process used during humanlund7s last voyages to the Moon.

Thomas, LeAnn↗
NASA NTRS2007

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2012

Human Systems Integration in Practice: Constellation Lessons Learned

NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.

Zumbado, Jennifer Rochlis↗
NASA NTRS2011

Systems Integration Challenges for a National Space Launch System

System Integration was refined through the complexity and early failures experienced in rocket flight. System Integration encompasses many different viewpoints of the system development. System Integration must ensure consistency in development and operations activities. Human Space Flight tends toward large, complex systems. Understanding the system fs operational and use context is the guiding principle for System Integration: (1) Sizeable costs can be driven into systems by not fully understanding context (2). Adhering to the system context throughout the system fs life cycle is essential to maintaining efficient System Integration. System Integration exists within the System Architecture. Beautiful systems are simple in use and operation -- Block upgrades facilitate manageable steps in functionality evolution. Effective System Integration requires a stable system concept. Communication is essential to system simplicity

May, Todd A.↗
NASA NTRS2015

Reflections on Centaur Upper Stage Integration by the NASA Lewis (Glenn) Research Center

The NASA Glenn (then Lewis) Research Center (GRC) led several expendable launch vehicle (ELV) projects from 1963 to 1998, most notably the Centaur upper stage. These major, comprehensive projects included system management, system development, integration (both payload and stage), and launch operations. The integration role that GRC pioneered was truly unique and highly successful. Its philosophy, scope, and content were not just invaluable to the missions and vehicles it supported, but also had significant Agency-wide benefits. An overview of the NASA Lewis Research Center (now the NASA Glenn Research Center) philosophy on ELV integration is provided, focusing on Atlas/Centaur, Titan/Centaur, and Shuttle/Centaur vehicles and programs. The necessity of having a stable, highly technically competent in-house staff is discussed. Significant depth of technical penetration of contractor work is another critical component. Functioning as a cohesive team was more than a concept: GRC senior management, NASA Headquarters, contractors, payload users, and all staff worked together. The scope, content, and history of launch vehicle integration at GRC are broadly discussed. Payload integration is compared to stage development integration in terms of engineering and organization. Finally, the transition from buying launch vehicles to buying launch services is discussed, and thoughts on future possibilities of employing the successful GRC experience in integrating ELV systems like Centaur are explored.

Centaur↗
NASA NTRS2011

Integrated Arrays on Silicon at Terahertz Frequencies

In this paper we explore various receiver font-end and antenna architecture for use in integrated arrays at terahertz frequencies. Development of wafer-level integrated terahertz receiver front-end by using advanced semiconductor fabrication technologies and use of novel integrated antennas with silicon micromachining are reported. We report novel stacking of micromachined silicon wafers which allows for the 3-dimensional integration of various terahertz receiver components in extremely small packages which easily leads to the development of 2- dimensioanl multi-pixel receiver front-ends in the terahertz frequency range. We also report an integrated micro-lens antenna that goes with the silicon micro-machined front-end. The micro-lens antenna is fed by a waveguide that excites a silicon lens antenna through a leaky-wave or electromagnetic band gap (EBG) resonant cavity. We utilized advanced semiconductor nanofabrication techniques to design, fabricate, and demonstrate a super-compact, low-mass submillimeter-wave heterodyne frontend. When the micro-lens antenna is integrated with the receiver front-end we will be able to assemble integrated heterodyne array receivers for various applications such as multi-pixel high resolution spectrometer and imaging radar at terahertz frequencies.

silicon micromaching↗
NASA NTRSDate not supplied

Distribution of SLS Integrated Load Uncertainty to Surface Pressures and Sectional Loads

Aerodynamic loads that are important to launch vehicle programs such as NASA’s Space Launch System (SLS) include both integrated loads such as the force & moment on the entire vehicle and distributed loads. In this work two examples of distributed loads are considered: the pressure field on the surface of the vehicle and sectional loads, which are one-dimensional distributions along the axis of the launch vehicle. In some modern flight programs, the integrated loads, such as lift and drag, used to design the guidance and control laws for the vehicle come from wind tunnel testing, while distributed loads are produced using Computational Fluid Dynamics(CFD). The first task that is addressed in this paper, then, is to provide a formal method to adjust the distributed loads so that integrating them matches the prescribed integrated load. In addition, the integrated loads in a launch vehicle typically include an uncertainty estimate. The second task is to distribute this prescribed integrated uncertainty to each point in a distributed load. Both tasks are addressed using the same technique, which is to create distributed load profiles that isolate adjustments to one integrated load while leaving the others unaffected. These adjustments are informed by Proper Orthogonal Decomposition (POD) of the entire CFD-based distributed load database. Once applied, the adjusted distributed loads can be used to evaluate any scalar quantity of interest that might be needed by downstream users such as structural analysis or trajectory modelers.

SLS↗
NASA NTRS2023

The Assembly, Test, and Integration of LOFTID (Low-Earth Orbit Flight Test of an Inflatable Decelera-tor)

R.J. Bodkin Biography Mr. Bodkin worked in industry for a rapid prototype company focusing on UAVs and manned experimental aircraft. Later he served as the Inflation System Lead on IRVE-II and 3 and the Re-Entry Vehicle Lead for LOFTID at NASA Langley Research Center. Introduction: The Low-Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID), developed in partnership with United Launch Alliance (ULA) and flown in conjunction with the National Oceanic and Atmospheric Administration (NOAA) Joint Polar Satellite System-2 (JPSS-2) satellite, demonstrated Hypersonic Inflatable Aerodynamic Decelerator (HIAD) technology has progressed and is ready for mission infusion. LOFTID’s success demonstrates that aeroshells are not limited to the internal diame-ter of the launch vehicle payload fairing, allowing larger payloads to be deployed to the surfaces of planetary bodies with atmospheres. The challenges of assembling, integrating, and testing this revolutionary spacecraft will be dis-cussed as well as issues associated with doing this with a fixed launch date the project did not control. Assembly: Because LOFTID flew as a rideshare partner with JPSS-2, it was constrained with addi-tional schedule, milestone, and technical require-ments that were beyond the project’s control. As-sembly of the LOFTID hardware was challenged with the normal mechanical fit issues while also having to navigate the SARS-COVID-II pandemic. Challenges ranged from availability of team per-sonnel required on-site for vehicle assembly to dif-ficulties associated with team collaboration while working remotely and increased costs and lead times of components due to supply chain con-straints. Numerous additional challenges cascaded from the additional time required. Integration: LOFTID flew as a secondary pay-load to JPSS-2 in a mission-unique configuration, directly under JPSS-2 primary payload, inside the Payload Adapter that integrated JPSS-2 to the Atlas V launch vehicle. A mission unique Payload Adapt-er Separation System (PASS) was required to sepa-rate the Payload Adapter from the Launch Vehicle prior to the start of the LOFTID flight demonstra-tion. Development of this system was challenging due to a shortened development schedule resulting from the iterative nature of Payload Adapter devel-opment with the partners at ULA. Preparations to integrate the main segments of the LOFTID vehicle posed unique challenges of having to accommodate issues with a fixed launch date that led to some cre-ative solutions to the integration. The partnership agreement with ULA and JPSS-2 resulted in a mass simulator designed to be installed late in the inte-gration in the event the LOFTID vehicle was not ready in time.. Test: LOFTID testing was carried out in several phases. Some components were tested at the com-ponent level, others at the sub-system levels and then finally the integrated vehicle level. This culmi-nated with the Complete Systems Test (CST) per-formed in a vacuum chamber as one of the final checkouts prior to disassembly for re-packing of the aeroshell. CST challenges will be discussed as well as obstacles encountered post-CST. After CST, the vehicle was disassembled so the HIAD could be repacked, and the vehicle was reassembled for ac-ceptance vibration testing. Testing concluded with the fully assembled vehicle being shipped to the launch site for final testing and integrations with the Payload Adapter to JPSS-2 for launch and opera-tions. Conclusion: The challenges posed by the AI&T for LOFTID could inform the planetary community of some of the opportunities and challenges of de-veloping technologies on a rideshare with a rela-tively small budget.

R.J. Bodkin↗
NASA NTRS2024

Crew Health and Performance Integrated Data Architecture (CHP-IDA) Project

BACKGROUND: Future Human Exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. A data architecture to support a new generation of technologies, employing advanced analytical and predictive modeling techniques, is needed to enable crew autonomy. OVERVIEW: The Crew Health and Performance Integrated Data Architecture (CHP-IDA) project funded by NASA’s Exploration Medical Integrated Product Team (XMIPT) is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. CHP-IDA provides a platform for common data models and Application Programming Interfaces to access, integrate, process, and display CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.). This will facilitate the increased situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the currently ongoing effort to develop and evaluate a path-to-flight concept of the CHP-IDA software and its core capabilities. Current integrations will be discussed, including analytics for Extravehicular Activity metabolic rate and data ingestion from a multi-functional integrated medical device. The presentation will also provide examples of scenarios used to demonstrate the CHP-IDA through human-in-the-loop test bed activities as well as examples of appropriate system performance metrics. DISCUSSION: Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting exploration medical capabilities. The CHP-IDA is a back-end data system providing core capabilities needed for timely and meaningful data insights across CHP domains to crew and remote personnel to enable increased crew autonomy. Future work includes collaboration with additional CHP domains, new technology integrations, and further demonstrations of the IDA within different vehicle and communication latency contexts. LEARNING OBJECTIVES 1. The audience will understand that the CHP-IDA is a back-end system, providing a platform to facilitate access, promote decision tools, and provide meaningful insights to crew and to remote stakeholders during exploration missions. 2. The audience will gain insight into human-centered research and activities used to discover CHP domain data needs and pain points and how this information is used to guide development of the IDA.

Exploration↗
DOE OSTI2016

Creating an Energy Intelligent Campus: Data Integration Challenges and Solutions at a Large Research Campus

Rich, well-organized building performance and energy consumption data enable a host of analytic capabilities for building owners and operators, from basic energy benchmarking to detailed fault detection and system optimization. Unfortunately, data integration for building control systems is challenging and costly in any setting. Large portfolios of buildings--campuses, cities, and corporate portfolios--experience these integration challenges most acutely. These large portfolios often have a wide array of control systems, including multiple vendors and nonstandard communication protocols. They typically have complex information technology (IT) networks and cybersecurity requirements and may integrate distributed energy resources into their infrastructure. Although the challenges are significant, the integration of control system data has the potential to provide proportionally greater value for these organizations through portfolio-scale analytics, comprehensive demand management, and asset performance visibility. As a large research campus, the National Renewable Energy Laboratory (NREL) experiences significant data integration challenges. To meet them, NREL has developed an architecture for effective data collection, integration, and analysis, providing a comprehensive view of data integration based on functional layers. The architecture is being evaluated on the NREL campus through deployment of three pilot implementations.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2017

Design Considerations for Proposed Fermilab Integrable RCS

Integrable optics is an innovation in particle accelerator design that provides strong nonlinear focusing while avoiding parametric resonances. One promising application of integrable optics is to overcome the traditional limits on accelerator intensity imposed by betatron tune-spread and collective instabilities. The efficacy of high-intensity integrable accelerators will be undergo comprehensive testing over the next several years at the Fermilab Integrable Optics Test Accelerator (IOTA) and the University of Maryland Electron Ring (UMER). We propose an integrable Rapid-Cycling Synchrotron (iRCS) as a replacement for the Fermilab Booster to achieve multi-MW beam power for the Fermilab high-energy neutrino program. We provide a overview of the machine parameters and discuss an approach to lattice optimization. Integrable optics requires arcs with integer-pi phase advance followed by drifts with matched beta functions. We provide an example integrable lattice with features of a modern RCS - long dispersion-free drifts, low momentum compaction, superperiodicity, chromaticity correction, separate-function magnets, and bounded beta functions.

43 PARTICLE ACCELERATORS↗
DOE OSTI2016

A whole-path importance-sampling scheme for Feynman path integral calculations of absolute partition functions and free energies

Using Feynman path integrals, a molecular partition function can be written as a double integral with the inner integral involving all closed paths centered at a given molecular configuration, and the outer integral involving all possible molecular configurations. In previous work employing Monte Carlo methods to evaluate such partition functions, we presented schemes for importance sampling and stratification in the molecular configurations that constitute the path centroids, but we relied on free-particle paths for sampling the path integrals. At low temperatures, the path sampling is expensive because the paths can travel far from the centroid configuration. In this paper, we now present a scheme for importance sampling of whole Feynman paths based on harmonic information from an instantaneous normal mode calculation at the centroid configuration, which we refer to as harmonically guided whole-path importance sampling (WPIS). We obtain paths conforming to our chosen importance function by rejection sampling from a distribution of free-particle paths. Sample calculations on CH 4 demonstrate that at a temperature of 200 K, about 99.9% of the free-particle paths can be rejected without integration, and at 300 K, about 98% can be rejected. Finally, we also show that it is typically possible to reduce the overhead associated with the WPIS scheme by sampling the paths using a significantly lower-order path discretization than that which is needed to converge the partition function.

74 ATOMIC AND MOLECULAR PHYSICS↗
DOE OSTI2013

Energy-Efficient and Comfortable Buildings through Multivariate Integrated Control (ECoMIC)

This project aims to develop an integrated control solution for enhanced energy efficiency and user comfort in commercial buildings. The developed technology is a zone-based control framework that minimizes energy usage while maintaining occupants’ visual and thermal comfort through control of electric lights, motorized venetian blinds and thermostats. The control framework is designed following a modular, scalable and flexible architecture to facilitate easy integration with exiting building management systems. The control framework contains two key algorithms: 1) the lighting load balancing algorithm and 2) the thermostat control algorithm. The lighting load balancing algorithm adopts a model-based closed-loop control approach to determine the optimal electric light and venetian blind settings. It is formulated into an optimization problem with minimizing lighting-related energy consumptions as the objective and delivering adequate task light and preventing daylight glare as the constraints. The thermostat control algorithm is based on a well-established thermal comfort model and formulated as a root-finding problem to dynamically determine the optimal thermostat setpoint for both energy savings and improved thermal comfort. To address building-wide scalability, a system architecture was developed for the zone-based control technology. Three levels of services are defined in the architecture: external services, facility level services and zone level services. The zone-level service includes the control algorithms described above as well as the corresponding interfaces, profiles, sensors and actuators to realize the zone controller. The facility level services connect to the zones through a backbone network, handle supervisory level information and controls, and thus facilitate building-wide scalability. The external services provide communication capability to entities outside of the building for grid interaction and remote access. Various aspects of the developed control technology were evaluated and verified through both simulations and testbed implementations. Simulations coupling a DOE medium office reference building in EnergyPlus building simulation software and a prototype controller in Matlab were performed. During summer time in a mixed-humid climate zone, the simulations revealed reductions of 27% and 42% in electric lighting load and cooling load, respectively, when compared to an advanced base case with daylight dimming and blinds automatically tilted to block direct sun. Two single-room testbeds were established. The testbed at Philips Lighting business building (Rosemont, IL) was designed for quantifying energy performance of integrated controls. This particular implementation achieved 40% and 79% savings on lighting and HVAC energy, respectively, compared to a relatively simple base case operated on predefined schedules. While the resulting energy savings was very encouraging, it should be noted that there may be several caveats associated with it. 1) The test was run during late spring and early summer, and the savings numbers might not be directly used to extrapolate the annual energy savings. 2) Due to the needs for separate control and metering of the small-scale demonstrator within a large building, the HVAC system, hence the corresponding savings, did not represent a typical energy code-compliant design. 3) The light level in the control case was regulated at a particular setpoint, which was lower than then the full-on light level in the base case, and the savings resulted from tuning down the light level to the setpoint was not attributable to the contribution of the developed technology. The testbed at the Lawrence Berkeley National Laboratory (Berkeley, CA) specifically focused on glare control integration, and has demonstrated the feasibility and capability of the glare detection and prevention technique. While the short one-month test in this testbed provided a functional indication of the developed technology, and it would require at least a full solstice-to-solstice cycle to ruinously quantify the performance, which was not possible within the project timeframe. There are certain limitations inherited from the operational assumptions, which could potentially affect the effectiveness and applicability of the developed control technologies. The system takes a typical ceiling-mounting approach for the photosensor locations, and therefore, the control performance relies on proper commissioning or the built-in intelligence of the photosensor for pertinent task light level estimations. For spaces where daylight penetration diminishes significantly deeper into the zone, certain modification to the control algorithms is required to accommodate multiple lighting control subzones and the corresponding sensors for providing a more uniform light level across the entire zone. Integrated control of visual and thermal comfort requires the lighting control zone and thermal control zone to coincide with each other. In other words, the area illuminated by a lighting circuit needs to be the same area served by the thermostat. Thus, the original zoning will potentially constrain the applicability of this technology in retrofitting projects. This project demonstrated the technical feasibility of a zone-based integrated control technology. From the simulation results and testbed implementations, up to 60% lighting energy savings in daylit areas relative to a “no-controls” case can easily be achieved. A 20% reduction of whole building energy consumption is also attainable. In the aspect of occupant comfort, the testbed demonstrated the ability to maintain specified light level on the workplane while promptly mitigate daylight glare 90% of the time. The control system also managed to maintain the thermal environment at a comfortable level 90% of the time. The aspect of system scalability was guaranteed by the system architecture design, based on which the testbeds were instantiated. Analysis on the aspect of economic benefit has yielded an about 6-year payback time for a medium-sized building, including the installation of all hardware and software, such as motorized blinds and LED luminaires. The payback time can be significantly reduced if part of the hardware is already in place for retrofitting projects. It needs to be noted that since the payback analysis was partly based on the testbed performance results, it is constrained by the caveats associated with the testbed implementations. The main uncertainty lies in the contribution from the space conditioning energy savings as it was non-trivial to realistically configure a room-size HVAC system for directly extrapolating whole-building HVAC energy savings. It is recommended to further evaluate the developed technology at a larger scale, where the lighting and HVAC energy consumption can be realistically measured at the building level, to more rigorously quantify the performance potentials.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2024

Preliminary Design of Nuclear Reactor Heat Delivery Systems: Integration with Reference Oil Refinery, Methanol Synthesis, and Hydrogen Production

The Department of Energy’s (DOE) Integrated Energy Systems (IES) program is generating comprehensive analyses validating the opportunity for using nuclear energy in a variety of applications including future clean grids, providing heat for direct use, and providing heat to help reduce emissions in chemical commodities. This work focuses on the preliminary designs of thermal delivery systems that can integrate heat produced from a nuclear core to industrial processes. The key research question that needs to be answered is: what is the prospective method for integrating nuclear generated heat energy into non-electric applications that can facilitate combined heat and power operations by advanced nuclear reactor systems? This research is a composition of case studies showing preliminary conceptual designs for thermal delivery systems integrating advanced nuclear systems with a few industrial systems including high temperature steam electrolysis, a reference oil refinery, and potential future methanol systems that supplant some natural gas use with nuclear energy. Piping and instrumentation diagrams have been developed to show the conceptual integration of nuclear systems with representative industrial systems. Different features of the configurations are dependent on the specific integration requirements including energy source conditions, demand quantity, and require energy application conditions. Design concepts are validated using thermodynamic balance calculations to verify system performance including calculating system losses during transport. Key components: pumps and compressors, heat exchangers, and network piping are reported with key design information and sizing.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗