Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “scheduling software”

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 1,009 records · Page 56

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a streamlined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to pro-ceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule, development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor downselection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measurements for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jacob↗

MARVEL 90% Final Design Report

This document provides documentation of the Microreactor Applications Research Validation and Evaluation Project’s (MARVEL) 90% Final Design, as required by U.S. Department of Energy (DOE) Standard-1189, “Integration of Safety into the Design Process." Per DOE-STD-1189-2016, the 90% Final Design documentation focuses on design completion, at a level capable of supporting procurement, construction, testing, and operation. At this phase, the design organization finalizes the hazards and accident analyses, Fire Hazard Analysis (FHA), security vulnerability assessments, and other supporting analyses for design completion. The objective of this report is to provide a high-level summary of the design thus far and provide references including, but not limited to, the following design deliverables: • Complete final drawings, specifications and commercial grade dedications that may be released for bid and/or construction. • Clearly defined testing plans for the safety and functionality of all subsystems. • Quality Assurance Program for Design, Testing and Procurement. • Software Quality Assurance Plan. • Code of Record (COR), applicable design requirements including codes and standards. • Final design that meets all the requirements stipulated in the COR. • Final design review, consisting of final validation of comment resolution from previous reviews, and a review of any additional developments since the last review. • Updated Safety Design Strategy. • Hazard Analysis. • Fire Hazard Analysis. • Accident analysis. • Security vulnerability assessment. • Current and detailed cost estimate. • Current construction schedule, and • Risk & Opportunities Assessment.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Locating Biodiversity Data Through The Global Change Master Directory

The Global Change Master Directory (GCMD) presently holds descriptions for almost 7000 data sets held worldwide. The directory's primary purpose is for data discovery. The information provided through the GCMD's Directory Interchange Format (DIF) is the set of information that a researcher would need to determine if a particular data set could be of value. By offering data set descriptions worldwide in many scientific disciplines - including meteorology, oceanography, ecology, geology, hydrology, geophysics, remote sensing, paleoclimate, solar-terrestrial physics, and human dimensions of climate change - the GCMD simplifies the discovery of data sources. Direct linkages to many of the data sets are also provided. In addition, several data set registration tools are offered for populating the directory. To search the directory, one may choose the Guided Search or Free-Text Search. Two experimental interfaces were also made available with the latest software release - one based on a keyword search and another based on a graphical interface. The graphical interface was designed in collaboration with the Human Computer Interaction Laboratory at the University of Maryland. The latest version of the software, Version 6, was released in April, 1998. It features the implementation of a scheme to handle hierarchical data set collections (parent-child relationships); a hierarchical geospatial location search scheme; a Java-based geographic map for conducting geospatial searches; a Related-URL field for project-related data set collections, metadata extensions (such as more detailed inventory information), etc.; a new implementation of the Isite software; a new dataset language field; hyperlinked email addresses, and more. The key to the continued evolution of the GCMD is in the flexibility of the GCMD database, allowing modifications and additions to made relatively easily to maintain currency, thus providing the ability to capitalize on current technology while importing all existing records. Changes are discussed and approved through an online "interoperability" forum. The next major release of the GCMD is scheduled for early 1999 and will include the incorporation of a new matrix-based interface, a rapid valids-based query system; improvement in the operations facility - important for future distributed options; new streamlined code for greater performance and maintainability; improvements in the handling of seven current fields proposed through the interoperability forum (at no expense to the data providers); and the release of DOCmorph, a more robust version of DIFmorph to translate many 'standards' multi-directionally. Issues and actions will also be addressed.

Olsen, Lola M.↗

San Francisco Bar Pilot Fatigue Study

The purpose of this study was to evaluate the extent of fatigue among San Francisco Bar Pilots (Maritime Pilots) and its potential impact on safety, and to make recommendations concerning how the risk of fatigue could be managed. Information was gathered via a literature review, observations of Bar Pilots at work, surveys, a task analysis, and an analysis of dispatch records.The work of San Francisco Bar Pilots involves an unusual mix of activities and job demands. Their work calls for situational awareness, reasoning, communication, and perceptual abilities comparable to those required by airline pilots and air traffic controllers. Errors can have severe consequences for public safety and the environment, as well as significant financial costs. Fatigue is increasingly recognized as a hazard that must be managed by the transportation industry. The reduced sleep quality and quantity experienced by personnel who work at night, in conjunction with human circadian rhythms can lead to an operationally significant level of cognitive impairment. The cognitive impact of fatigue includes functions that are critical to safe maritime piloting, such as vigilance, judgment, reaction time and communication. The surveys distributed to Bar Pilots did not uncover evidence of widespread fatigue. The survey results also suggested that fatigue was not a major concern of Bar Pilots. Bar Pilots had overall low scores on the subjective fatigue measures used in the survey, and generally assessed the safety risk due to fatigue as low. Compared to air traffic controllers, Bar Pilots gave significantly lower ratings on questions concerning the prevalence and impact of fatigue. The application of fatigue modeling software to Bar Pilot dispatch records identified that in most cases, pilot's cognitive effectiveness was predicted to be acceptable during their duty periods. However, these results could not be verified with objective data.The study identified a number of fatigue issues that deserve attention. These include Bar Pilot work periods that frequently infringe on the circadian low, consecutive work periods without a significant break, consecutive periods of night work, unpredictable work schedules, start time variability, the potential for sleep inertia, and the number of pilots on the board at any given time.

fatigue↗

Parallel software support for computational structural mechanics

The application of the parallel programming methodology known as the Force was conducted. Two application issues were addressed. The first involves the efficiency of the implementation and its completeness in terms of satisfying the needs of other researchers implementing parallel algorithms. Support for, and interaction with, other Computational Structural Mechanics (CSM) researchers using the Force was the main issue, but some independent investigation of the Barrier construct, which is extremely important to overall performance, was also undertaken. Another efficiency issue which was addressed was that of relaxing the strong synchronization condition imposed on the self-scheduled parallel DO loop. The Force was extended by the addition of logical conditions to the cases of a parallel case construct and by the inclusion of a self-scheduled version of this construct. The second issue involved applying the Force to the parallelization of finite element codes such as those found in the NICE/SPAR testbed system. One of the more difficult problems encountered is the determination of what information in COMMON blocks is actually used outside of a subroutine and when a subroutine uses a COMMON block merely as scratch storage for internal temporary results.

Jordan, Harry F.↗

Commercial Building Energy Baseline Modeling Software: Performance Metrics and Method Testing with Open Source Models and Implications for Proprietary Software Testing

The overarching goal of this work is to advance the capabilities of technology evaluators in evaluating the building-level baseline modeling capabilities of Energy Management and Information System (EMIS) software. Through their customer engagement platforms and products, EMIS software products have the potential to produce whole-building energy savings through multiple strategies: building system operation improvements, equipment efficiency upgrades and replacements, and inducement of behavioral change among the occupants and operations personnel. Some offerings may also automate the quantification of whole-building energy savings, relative to a baseline period, using empirical models that relate energy consumption to key influencing parameters, such as ambient weather conditions and building operation schedule. These automated baseline models can be used to streamline the whole-building measurement and verification (M&V) process, and therefore are of critical importance in the context of multi-measure whole-building focused utility efficiency programs.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

XPRESS: eXascale PRogramming Environment and System Software

This is the final report for UNC activities as its part in the XStack program XPRESS project. A project-wide final report will be submitted by the project as a whole through Sandia National Laboratory when the contracts to the other participating organizations have reached their conclusion(s).

97 MATHEMATICS AND COMPUTING↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements.

Formulation↗

QUEST/Ada: Query utility environment for software testing of Ada

Results of research and development efforts are presented for Task 1, Phase 2 of a general project entitled, The Development of a Program Analysis Environment for Ada. A prototype of the QUEST/Ada system was developed to collect data to determine the effectiveness of the rule-based testing paradigm. The prototype consists of five parts: the test data generator, the parser/scanner, the test coverage analyzer, a symbolic evaluator, and a data management facility, known as the Librarian. These components are discussed at length. Also presented is an experimental design for the evaluations, an overview of the project, and a schedule for its completion.

Brown, David B.↗

BigData Express: Toward Predictable, Schedulable, and High-Performance Data Transfer [Slides]

Big data has emerged as a driving force for scientific discoveries. Large scientific instruments (e.g., colliders, and telescopes) generate exponentially increasing volumes of data. To enable scientific discovery, science data must be collected, indexed, archived, shared, and analyzed, typically in a widely distributed and highly collaborative manner. Data transfer is now an essential function for science discoveries, particularly within big data environments. To support data transfer for big data science, there is a need for predictable, high performance, scalable, end-to-end, programmable networks that enable science applications to use network resources most efficiently. Software-Defined Networking (SDN) is a novel network architecture and technological approach that separates the network control and data planes.

97 MATHEMATICS AND COMPUTING↗

Retargeting of existing FORTRAN program and development of parallel compilers

The software models used in implementing the parallelizing compiler for the B-HIVE multiprocessor system are described. The various models and strategies used in the compiler development are: flexible granularity model, which allows a compromise between two extreme granularity models; communication model, which is capable of precisely describing the interprocessor communication timings and patterns; loop type detection strategy, which identifies different types of loops; critical path with coloring scheme, which is a versatile scheduling strategy for any multicomputer with some associated communication costs; and loop allocation strategy, which realizes optimum overlapped operations between computation and communication of the system. Using these models, several sample routines of the AIR3D package are examined and tested. It may be noted that automatically generated codes are highly parallelized to provide the maximized degree of parallelism, obtaining the speedup up to a 28 to 32-processor system. A comparison of parallel codes for both the existing and proposed communication model, is performed and the corresponding expected speedup factors are obtained. The experimentation shows that the B-HIVE compiler produces more efficient codes than existing techniques. Work is progressing well in completing the final phase of the compiler. Numerous enhancements are needed to improve the capabilities of the parallelizing compiler.

Agrawal, Dharma P.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

Future of Work with Robotics - 18599

The DOE Environmental Management mission continues with remaining tasks that are high-hazards to human workers and high-consequences to the nation, resulting in potentially high risks to project costs and schedules. This is the mission pull. At the same time, robotic technologies are hitting a turning point with increased productivity and reliability within society, supporting a technology push. Enabling this push are better computer processing following Moore's Law, breakthroughs in biometric and learning algorithms,and riding a wave of venture funding for intended commercialization of mechatronic and Internet of Thing (IOT) projects. There has been overall improvements in material technologies, algorithms, and software standardization with tools/libraries such as the Robot Operating System (ROS). The internet has made knowledge ubiquitous and the cell phone sector has pushed the boundaries of systems-on-chip technology. This current growth is a race between large global technology companies, and between countries that understand that there is a prize with increased commerce based on being a leader in the field of robotics and automation. This technological advances have placed this technology solidly within the next 4. Industrial Revolution being tracked by the World Economic Council. Policies and law can slow this progression down, but technological changes in adjacent fields will put additional pressure on human workers by being more economical and in saving lives. A fundamental issue is will this change be gradual or disruptive such as with the forecasted singularity. There is also a realization with automation that the transition of human workers to other fields may be temporary, but in the long run, workers may run out of viable work and long-term occupations. The obvious future of human jobs are most assured by those who can embrace the change through the design, development, installment, and maintenance of the technology. Younger workers can be re-educated while older humans can be re-trained. The goal of this paper is to explore all the forces that are enabling this revolution, investigating its many impacts, and speculating on the future of human jobs during nuclear remediation. Automation has made an impact to the manufacturing sector, and has since expanded to the retail and services sectors. The question is will this same automation transition, including robotics and artificial intelligence, occur to the environmental management and cleanup sector, and how should we prepare ourselves for this change. (author)

42 ENGINEERING↗

NREL Energy Models Examine the Potential for Wind and Solar Grid Integration (Fact Sheet)

As renewable energy generating sources, such as wind turbines and solar power systems, reach high levels of penetration in parts of the United States, the National Renewable Energy Laboratory (NREL) is helping the utility industry to peer into the future. Using software modeling tools that the lab developed, NREL is examining the future operation of the electrical grid as renewable energy continues to grow.

14 SOLAR ENERGY↗

A Business Case for Advanced Outage Management

The Department of Energy’s (DOE) Light Water Reactor Sustainability (LWRS) Program develops and validates technologies that will make the U.S. operating nuclear fleet more efficient and competitive. The program has developed a standard methodology for determining the impact of new technologies in order to assist nuclear power plant (NPP) operators in building sound business cases. This paper presents a generic business case for implementation of technology that supports Advanced Outage Management (AOM). The analysis presented demonstrates that advanced communication and networking and analytical technologies will allow NPP to conduct outages with fewer people in management roles and the remaining people can be more effective and more productive. The benefits are quantified with a rough order of magnitude that provides directional guidance to NPPs that are interested in developing a similar business case. Advanced Outage Management is enabled by a suite of technologies, which are described in further detail in the body of this report. They include: • Mobile Work Packages (MWP) • Computer Based Procedures (CBP) • Personal Digital Assistants (PDA) also referred to as smart devices • Barcode readers • High bandwidth wireless networks • Collaboration software (i.e., OneNote) • Advanced digital displays • Advanced data analytics All the hardware necessary to implement AOM as envisioned in this report is readily available today. Configuration to perform within the plant systems and regulatory boundaries would need to be developed by the NPP. 1. The resulting business case demonstrates benefits in two major categories: 2. Reduction in resources required to manage the outage, a. Increased productivity in outage work that reduces the likelihood of schedule overruns: b. reduce likelihood of bulk work resulting in outage delays c. improved management of critical path single issues, d. improved management of emergent work (improve time to collect data and prepare response) It is important to note that in order to realize these benefits at the scale described in this report requires the plant to rethink how technologies can disrupt current processes; how data might be captured, processed, analyzed and presented with little or no human intervention. In many cases, technology be fully utilized in a way that not only aides productivity, but is utilized towards “work destruction” – elimination of work that is currently performed through a human interface.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

User modeling techniques for enhanced usability of OPSMODEL operations simulation software

The PC based OPSMODEL operations software for modeling and simulation of space station crew activities supports engineering and cost analyses and operations planning. Using top-down modeling, the level of detail required in the data base can be limited to being commensurate with the results required of any particular analysis. To perform a simulation, a resource environment consisting of locations, crew definition, equipment, and consumables is first defined. Activities to be simulated are then defined as operations and scheduled as desired. These operations are defined within a 1000 level priority structure. The simulation on OPSMODEL, then, consists of the following: user defined, user scheduled operations executing within an environment of user defined resource and priority constraints. Techniques for prioritizing operations to realistically model a representative daily scenario of on-orbit space station crew activities are discussed. The large number of priority levels allows priorities to be assigned commensurate with the detail necessary for a given simulation. Several techniques for realistic modeling of day-to-day work carryover are also addressed.

Davis, William T.↗

Rapid Development of the Seeker Free-Flying Inspector Guidance, Navigation, and Control System

Seeker is an automated extravehicular free-flying inspector CubeSat designed and built in-house at the Johnson Space Center (JSC). As a Class 1E project funded by the International Space Station (ISS) Program, Seeker had a stream-lined process to flight certification, but the vehicle had to be designed, developed, tested, and delivered within approximately one year after authority to proceed (ATP) and within a $1.8 million budget. These constraints necessitated an expedited Guidance, Navigation, and Control (GNC) development schedule. Development began with a navigation sensor trade study using Linear Covariance (LinCov) analysis and a rapid sensor down-selection process, resulting in the use of commercial off-the-shelf (COTS) sensors which could be procured quickly and subjected to in-house environmental testing to qualify them for flight. A neural network was used to enable a COTS camera to provide bearing measure-ments for visual navigation. The GNC flight software (FSW) algorithms utilized lean development practices and leveraged the Core Flight Software (CFS) architecture to rapidly develop the GNC system, tune the system parameters, and verify performance in simulation. This pace was anchored by several Hardware-Software Integration (HSI) milestones, which forced the Seeker GNC team to develop the interfaces both between hardware and software and between the GNC domains early in the project and to enable a timely delivery.

Sullivan, Jake↗

IAEA Domestic Inspections in the US

The Voluntary Offer Agreement between the United States and the IAEA for the implementation of IAEA safeguards in the United States, INFCIRC/288, entered into force in 1980. Under this Agreement, the United States provides to the IAEA an Eligible Facilities List, which lists facilities eligible for IAEA inspection and verification of compliance through either a reporting-only process or for full-scope safeguards (to include inspections). Approximately 300 facilities are currently listed on the Eligible Facilities List. Since 1981, the IAEA has conducted over 700 inspections on ~20 of these facilities. Currently, four NRC-licensed facilities have been selected under the Initial (Reporting) Protocol, and one DOE facility, KAMS at the SRS, has been selected for full-scope safeguards. These IAEA inspections are documented in the ID/288 database managed by staff at ORNL and the Y-12 National Security Complex for the NNSA Office of Nonproliferation and Arms Control. This database also maintains records of US designated inspectors, the status of indices checks, and inspection schedules. The database was most recently updated in FY 2014 to include information related to the IAEA visit to URENCO-USA in New Mexico and will be upgraded again via proposal in FY 2017 to include the Small Quantities Protocol (SQP) inspections in the US Caribbean territories, associated with INFCIRC/366. During the FY 2017 upgrade, the system will also be overhauled to allow for quicker updates and to improve performance using a modern software package.

White-Horton, Jessica↗