Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “System Operations”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 217 records · Page 12

From Vehicles to Systems: Understanding Freight Transportation as a Connected Energy, Infrastructure, and Operations System

The U.S. freight system may need to handle 50% more cargo by 2050. Upgrading our freight system requires modernizing capital-intensive, long-lived assets including freight trains, ports, and terminal infrastructure. NLR is advancing freight system solutions spanning ALTRIOS, the first digital twin for the full freight rail system; ALTRIOS-LIFTS, which can create digital twins of freight terminals; INFORMES, the first national model of the intermodal freight system; MARINESim, used to simulate and optimize ocean-going vessel operations; and more. These modeling and simulation tools enable data-driven decision-making across freight modes and systems.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Integration of Utility Distributed Energy Resource Management System and Aggregators for Evolving Distribution System Operators

With the rapid integration of distributed energy resources (DERs), distribution utilities are faced with new and unprecedented issues. New challenges introduced by high penetration of DERs range from poor observability to overload and reverse power flow problems, under-over-voltages, maloperation of legacy protection systems, and requirements for new planning procedures. Distribution utility personnel are not adequately trained, and legacy control centers are not properly equipped to cope with these issues. Fortunately, distribution energy resource management systems (DERMSs) are emerging software technologies aimed to provide distribution system operators (DSOs) with a specialized set of tools to enable them to overcome the issues caused by DERs and to maximize the benefits of the presence of high penetration of these novel resources. However, as DERMS technology is still emerging, its definition is vague and can refer to very different levels of software hierarchies, spanning from decentralized virtual power plants to DER aggregators and fully centralized enterprise systems (called utility DERMS). Although they are all frequently simply called DERMS, these software technologies have different sets of tools and aim to provide different services to different stakeholders. This paper explores how these different software technologies can complement each other, and how they can provide significant benefits to DSOs in enabling them to successfully manage evolving distribution networks with high penetration of DERs when they are integrated together into the control centers of distribution utilities.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Satellite power system operations

A projection of the electrical energy demands over the next 30 to 50 years, coupled with reasonable assessments of known or developable energy sources, indicates that a shortage of electrical energy will occur about the turn of the century. Recognizing the criticality of such a shortage, the Department of Energy is currently evaluating alternative power generation concepts. One of these candidate concepts is the Satellite Power System. The power levels considered during the evaluation of the various satellite systems have ranged from 5 to 10 GW. It is apparent that, with this power level, both the satellite and the rectenna must be very large and encompass a large number of complex operational system activities. Major elements of the Satellite Power System (SPS) consist of a power satellite placed in a geosynchronous equatorial orbit, and a dedicated ground receiving station (GRS) located at a selected site within the continental United States. The nominal power output of the SPS is established at 5 gigawatts (5 million kilowatts) although, because of various system constraints or losses, it may actually produce between 4 and 5 gigawatts.

Pugh, F. L.↗

The elements of a space operations system

The Space Shuttle has completed its flight test program and is entering operational service with its fifth flight in November 1982. With the completion of Shuttle development, its entry to operational service, and delivery of additional units into field service, it is timely to initiate development of the next elements of the system. The elements of a Space Operations System are the Shuttle, a Station in low earth orbit, and upper stages for low and high energy orbit delivery. To design these elements properly will require a substantial operations analysis effort to characterize the most effective performance tradeoffs among the discrete elements. The Shuttle establishes a new context for the design and execution of operations in space. The components of the Shuttle, Space Station, and upper stages will need to share technology and components to minimize the cost and complexity of the logistics of ownership and operation.

Loftus, J. P., Jr.↗

A cost-benefit evaluation of the LANDSAT flow-on operational system

Disciplines to benefit from the LANDSAT Follow-on System include agriculture, petroleum and mineral exploration, hydrologic land use, water resources management, forestry, land use planning and monitoring, and soil management. The annual quantified benefits are in the range of 420 to 970 million (FY 1976 dollars). The operational system sized to achieve the quantified benefits involves a single orbiting satellite with a backup satellite in launch readiness. The ground system includes a basic processing system which feeds information to three user systems - one for agriculture, one for hydrologic land use, and a third for all other users. The resulting present worth benefit cost ratio is at least equal to four with a reasonable likelihood of exceeding nine. This benefit cost ratio is evaluated for an infinite time horizon at the discount rate of 10 percent.

Source record↗

Fault-tolerant software - Experiment with the sift operating system

Results are presented of an experiment conducted in the NASA Avionics Integrated Research Laboratory (AIRLAB) to investigate the implementation of fault-tolerant software techniques on fault-tolerant computer architectures, in particular the Software Implemented Fault Tolerance (SIFT) computer. The N-version programming and recovery block techniques were implemented on a portion of the SIFT operating system. The results indicate that, to effectively implement fault-tolerant software design techniques, system requirements will be impacted and suggest that retrofitting fault-tolerant software on existing designs will be inefficient and may require system modification.

Brunelle, J. E.↗

Operating systems in the air transportation environment.

Consideration of the problems facing air transport at present, and to be expected in the future. In the Northeast Corridor these problems involve community acceptance, airway and airport congestion and delays, passenger acceptance, noise reduction, and improvements in low-density short-haul economics. In the development of a superior short-haul operating system, terminal-configured vs cruise-configured vehicles are evaluated. CTOL, STOL, and VTOL aircraft of various types are discussed. In the field of noise abatement, it is shown that flight procedural techniques are capable of supplementing ?quiet engine' technology.

Cherry, G. W.↗

The Anatomy of Software Changes and Bugs in Autonomous Operating System

Cyberphysical systems with autonomous functions are complex pieces of software, consisting of many components, some of which implement autonomous functionality and some may use AI or machine learning algorithms. Software bugs in an autonomous system are of particular concern, as they can have catastrophic consequences. However, detailed studies based on empirical data are rare and therefore these bugs are not well understood. This paper aims to contribute towards filling that gap by investigating the software changes and bugs in Autonomy Operating System (AOS) for Unmanned Aircraft Systems (UAS), which consist of 26 components containing about 103,000 lines of code and having a total of 772 bugfixes. Based on the data extracted from the code repository and semi-structured interviews with the developers of AOS, we explore the differences among autonomous software components, components developed using Model-based Software Engineering, and reuse with respect to change proneness, fault proneness, distribution of bugfixes among AOS components and files of these components, and characteristics of bugs of different AOS components. Our results show that the autonomous components were significantly more change prone (measured in number of commits and code churn) and fault prone (measured in bugfixes per KLoC) than non-autonomous components. The distribution of the locations of bugfixes was skewed, both at component and file level (i.e., a small number of components / files contained the majority of bugs). These evidence-based findings provide important insights to researchers and practitioners alike and can be used to efficiently improve the quality and reliability of autonomous systems.

Katerina Goseva-Popstojanova↗

Space station automation and robotics study. Operator-systems interface

This is the final report of a Space Station Automation and Robotics Planning Study, which was a joint project of the Boeing Aerospace Company, Boeing Commercial Airplane Company, and Boeing Computer Services Company. The study is in support of the Advanced Technology Advisory Committee established by NASA in accordance with a mandate by the U.S. Congress. Boeing support complements that provided to the NASA Contractor study team by four aerospace contractors, the Stanford Research Institute (SRI), and the California Space Institute. This study identifies automation and robotics (A&R) technologies that can be advanced by requirements levied by the Space Station Program. The methodology used in the study is to establish functional requirements for the operator system interface (OSI), establish the technologies needed to meet these requirements, and to forecast the availability of these technologies. The OSI would perform path planning, tracking and control, object recognition, fault detection and correction, and plan modifications in connection with extravehicular (EV) robot operations.

Source record↗

Defining Well Clear Separation for Unmanned Aircraft Systems Operating with Noncooperative Aircraft

Detect-and-Avoid (DAA) systems are essential to the safe operations of Unmanned Aircraft Systems, and have the objectives of mitigating collisions with and remaining Well Clear of manned aircraft. This paper analyzes four candidate DAA Well Clear definitions for non-cooperative aircraft using mitigated performance metrics of DAA systems. These DAA Well Clear definitions were proposed in previous work based on their unmitigated collision risk and maneuver initiation range. In this work they are evaluated using safety and operational suitability metrics computed from a large number of representative encounters. Results suggest that although the four candidate DAA Well Clear definitions provide comparable safety, the alerting characteristics give preference for the DAA Well Clear definition without a temporal parameter.

Well Clear↗

Core Community Specifications for Electron Microprobe Operating Systems: Software, Quality Control, and Data Management Issues

Modem electron microprobe systems have become increasingly sophisticated. These systems utilize either UNIX or PC computer systems for measurement, automation, and data reduction. These systems have undergone major improvements in processing, storage, display, and communications, due to increased capabilities of hardware and software. Instrument specifications are typically utilized at the time of purchase and concentrate on hardware performance. The microanalysis community includes analysts, researchers, software developers, and manufacturers, who could benefit from exchange of ideas and the ultimate development of core community specifications (CCS) for hardware and software components of microprobe instrumentation and operating systems.

Fournelle, John↗

Definition of an auxiliary processor dedicated to real-time operating system kernels

In order to increase the efficiency of process control data processing, it is necessary to enhance the productivity of real time high level languages and to automate the task administration, because presently 60 percent or more of the applications are still programmed in assembly languages. This may be achieved by migrating apt functions for the support of process control oriented languages into the hardware, i.e., by new architectures. Whereas numerous high level languages have already been defined or realized, there are no investigations yet on hardware assisted implementation of real time features. The requirements to be fulfilled by languages and operating systems in hard real time environment are summarized. A comparison of the most prominent languages, viz. Ada, HAL/S, LTR, Pearl, as well as the real time extensions of FORTRAN and PL/1, reveals how existing languages meet these demands and which features still need to be incorporated to enable the development of reliable software with predictable program behavior, thus making it possible to carry out a technical safety approval. Accordingly, Pearl proved to be the closest match to the mentioned requirements.

Halang, Wolfgang A.↗

Open Building Operating System: An Open-Source Grid Responsive Control Platform for Buildings

Grid-interactive efficient buildings (GEBs) with flexible loads are a promising method to decarbonize buildings, shift loads during peak hours, and lower energy use and electricity costs. Despite the promising benefits of GEBs, automation systems that manage flexible loads in response to energy prices or other grid signals are still uncommon in small and medium commercial buildings. Recent literature demonstrates such control solutions, but they often rely on custom integrations lacking the tools and drivers needed for scalability. To address these gaps, our team has created a fully open-source software stack capable of integrating heterogeneous flexible building loads and implementing integrated portable control applications called the Open Building Operating System (OpenBOS). The software can be deployed over existing control architecture with a small capital cost. OpenBOS leverages semantic models, which have been the subject of recent investigations to facilitate application portability. The use of semantic data reduces the labor and expense required to deploy and update smart control applications, increasing scalability. In this paper, the semantic modeling schema "Brick" was used, but the proposed approach can also be applied to ASHRAE standard 223P, when released. This paper describes the methodology and software components of OpenBOS and demonstrates its functionality with a rule-based demand flexibility control application configured using a semantic model. This application was tested at a real building in NY that uses a dual-fuel heating system made up of five ductless heat pump mini-splits and a central furnace serving a single zone. The demonstration reduced electricity costs at the site by 27%, demand during a shed event by 49%, and furnace usage by 35%.

24 POWER TRANSMISSION AND DISTRIBUTION↗

An operational system for subject switching between controlled vocabularies

The NASA system of automatically converting sets of terms assigned by Department of Defense indexers to sets of NASA's authorized terms is described. This little-touted system, which has been operating successfully since 1983, matches concepts, rather than words. Subject Switching uses a translation table, known as the Lexical Dictionary, accessed by a program that determines which rules to follow in making the transition from DTIC's to NASA's authorized terms. The authors describe the four phases of development of Subject Switching, changes that have been made, evaluating the system, and benefits. Benefits to NASA include saving indexers' time, the addition of access points for documents indexed, the utilization of other government indexing, and a contribution towards the now-operational NASA, online, interactive, machine aided indexing.

Silvester, June P.↗

Transportability, distributability and rehosting experience with a kernel operating system interface set

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Blumberg, F. C.↗

Calibration Issues and Operating System Requirements for Electron-Probe Microanalysis

Instrument purchase requirements and dialogue with manufacturers have established hardware parameters for alignment, stability, and reproducibility, which have helped improve the precision and accuracy of electron microprobe analysis (EPMA). The development of correction algorithms and the accurate solution to quantitative analysis problems requires the minimization of systematic errors and relies on internally consistent data sets. Improved hardware and computer systems have resulted in better automation of vacuum systems, stage and wavelength-dispersive spectrometer (WDS) mechanisms, and x-ray detector systems which have improved instrument stability and precision. Improved software now allows extended automated runs involving diverse setups and better integrates digital imaging and quantitative analysis. However, instrumental performance is not regularly maintained, as WDS are aligned and calibrated during installation but few laboratories appear to check and maintain this calibration. In particular, detector deadtime (DT) data is typically assumed rather than measured, due primarily to the difficulty and inconvenience of the measurement process. This is a source of fundamental systematic error in many microprobe laboratories and is unknown to the analyst, as the magnitude of DT correction is not listed in output by microprobe operating systems. The analyst must remain vigilant to deviations in instrumental alignment and calibration, and microprobe system software must conveniently verify the necessary parameters. Microanalysis of mission critical materials requires an ongoing demonstration of instrumental calibration. Possible approaches to improvements in instrument calibration, quality control, and accuracy will be discussed. Development of a set of core requirements based on discussions with users, researchers, and manufacturers can yield documents that improve and unify the methods by which instruments can be calibrated. These results can be used to continue improvements of EPMA.

Carpenter, P.↗