Search NASA⌕ Search

SEARCH · Search NASA

Results for “Process Owner”

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 37 records · Page 2

Environmental Remediation Technologies Derived from Space Industry Research

Beginning in the 1950s and 1960s, an abundance of effort and initiative was focused on propelling the space industry outward for planetary exploration and habitation. During these early years, the push to take space science to new levels indirectly contributed to the evolution of another science field that would not fully surface until the early 1980s, environmental remediation. This field is associated with the remediation or cleanup of environmental resources such as groundwater, soil, and sediment. Because the space-exploration initiative began prior to the establishment of the U.S. Environmental Protection Agency (EPA) in December of 1970, many NASA Centers as well as space-related support contractors allowed for the release of spent chemicals into the environment. Subsequently, these land owners have been directed by the EPA to responsibly initiate cleanup of their impacted sites. This paper will focus on the processes and lessons learned with the development, testing, and commercialization initiatives associated with four remediation technologies. The technologies include installation techniques for permeable reactive barriers (PRBs), the use of ultrasound to improve long-term performance of PRBs, emulsified zero-valent iron for product-level solvent degradation, and emulsion technologies for application to metal and polychlorinated biphenyl contaminated media. Details of the paper cover technology research, evaluation, and testing; contracts and grants; and technology transfer strategies including patenting, marketing, and licensing.

Quinn, Jacqueline↗

Surface Enhancement Improves Crack Resistance

The low plasticity burnishing (LPB) process produces a deep layer of surface compression in a quick and affordable manner to produce metal surfaces free of scratches, nicks, and gouges. The process, designed for easy inclusion in the manufacturing environment, can be performed with conventional Computer Numerical Control machine tools. This allows parts to be processed during manufacturing, rather than as a post process in a separate facility. A smooth, free-rolling spherical ball suspended in a fluid allows for single-point contact. The ball comes into mechanical contact only with the surface to be burnished, and can be moved in any direction. LPB can be applied to all types of carbon and alloy steel, stainless steel, cast iron, aluminum, titanium, and nickel- based super alloys. In addition to improving a surface's resistance to fatigue and damage, treatment stops the growth of shallow cracks. The LPB process is used on the leading edges of turbine blades to improve resistance to foreign object damage and crack growth. This means significant savings for aircraft owners, since maintenance requirements to inspect for fatigue damage, replace parts, and remove corrosion damage increase the cost of operation.

Source record↗

Manual Asset Inventory: NASA Kennedy Space Center

The National Aeronautics and Aerospace Administration (NASA) relies in the security and protection of the information and information systems to know the devices that are connected to the Agency networks whether these are business, mission, research, or engineering devices. The Agency uses different Information Technology resources in order to do this process automatically, however, there are some devices that need to be reported manually. As a result of this, every month the Agency distributes among its Information System Owners (ISOs) the Manual Asset Inventory, a document that consists of a Microsoft Excel spreadsheet with twenty field descriptions cells that has to be filled out by the ISO of every Security Plan in the Center [fifty three in total] and uploaded into the IT Security Enterprise Data Warehouse (ITSEC-EDW).

Presentation↗

Remote Sensing from Geostationary Orbit: GEO TROPSAT, A New Concept for Atmospheric Remote Sensing

The Geostationary Tropospheric Pollution Satellite (GEO TROPSAT) mission is a new approach to measuring the critical constituents of tropospheric ozone chemistry: ozone, carbon monoxide, nitrogen dioxide, and aerosols. The GEO TROPSAT mission comprises a constellation of three instruments flying as secondary payloads on geostationary communications satellites around the world. This proposed approach can significantly reduce the cost of getting a science payload to geostationary orbit and also generates revenue for the satellite owners. The geostationary vantage point enables simultaneous high temporal and spatial resolution measurement of tropospheric trace gases, leading to greatly improved atmospheric ozone chemistry knowledge. The science data processing, conducted as a research (not operational) activity, will provide atmospheric trace gas data many times per day over the same region at better than 25 km ground footprint. The high temporal resolution identifies short time scale processes, diurnal variations, seasonal trends, and interannual variation.

Little, Alan D.↗

Safe Grid

The biggest users of GRID technologies came from the science and technology communities. These consist of government, industry and academia (national and international). The NASA GRID is moving into a higher technology readiness level (TRL) today; and as a joint effort among these leaders within government, academia, and industry, the NASA GRID plans to extend availability to enable scientists and engineers across these geographical boundaries collaborate to solve important problems facing the world in the 21 st century. In order to enable NASA programs and missions to use IPG resources for program and mission design, the IPG capabilities needs to be accessible from inside the NASA center networks. However, because different NASA centers maintain different security domains, the GRID penetration across different firewalls is a concern for center security people. This is the reason why some IPG resources are been separated from the NASA center network. Also, because of the center network security and ITAR concerns, the NASA IPG resource owner may not have full control over who can access remotely from outside the NASA center. In order to obtain organizational approval for secured remote access, the IPG infrastructure needs to be adapted to work with the NASA business process. Improvements need to be made before the IPG can be used for NASA program and mission development. The Secured Advanced Federated Environment (SAFE) technology is designed to provide federated security across NASA center and NASA partner's security domains. Instead of one giant center firewall which can be difficult to modify for different GRID applications, the SAFE "micro security domain" provide large number of professionally managed "micro firewalls" that can allow NASA centers to accept remote IPG access without the worry of damaging other center resources. The SAFE policy-driven capability-based federated security mechanism can enable joint organizational and resource owner approved remote access from outside of NASA centers. A SAFE enabled IPG can enable IPG capabilities to be available to NASA mission design teams across different NASA center and partner company firewalls. This paper will first discuss some of the potential security issues for IPG to work across NASA center firewalls. We will then present the SAFE federated security model. Finally we will present the concept of the architecture of a SAFE enabled IPG and how it can benefit NASA mission development.

Chow, Edward T.↗

Documentation: No Substitute for Communication

SO WHAT IS AN RFI? IT WAS ONE OF THE FIRST THINGS I learned about back when I started my project management career with my first large construction firm. I learned how to use these forms as a convenient and effective means of documenting the many legitimate clarifications needed on a major project. However, like most other young engineers, I also learned to use the RFI as a weapon in the ongoing battle between owners. or their designer and the construction contractors. Recently, our project team has done a few simple things to greatly reduce the waste and frustration that comes from this type of battle. The RFI form can be a great tool if used properly, and I certainly don t recommend that they be eliminated entirely. The RFI form was created to document the many clarifications that are commonly required on projects. Typically, the contractor uses the top half of the form to clarify-or request permission to vary from-the contract documents. The bottom half of the form is used to record the answer. But this seemingly simple process is plagued by a number of problems. From the contractor s perspective, RFIs are needed to secure information that should have been in the contract documents in the first place. The missing information keeps their crews from working effectively, and it makes hitting already demanding cost and schedule targets even more difficult. Owners, or their design firms, often view the RFI as a means of harassment. Both sides of the issue have legitimate complaints, and both sides cause most of their own pain.

Strickland, John↗

The measurement of frequency and frequency stability of precision oscillators

The specification and performance of precision oscillators is discussed as a very important topic to the owners and users of these oscillators. This paper presents at the tutorial level some convenient methods of measuring the frequencies of precision oscillators -- giving advantages and disadvantages of these methods. Further it is shown that by processing the data from the frequency measurements in certain ways, one may be able to state more general characteristics of the oscillators being measured. The goal in this regard is to allow the comparisons of different manufacturers' specifications and more importantly to help assess whether these oscillators will meet the standard of performance the user may have in a particular application.

Allan, D. W.↗

An Integrated Approach to Exploration Launch Office Requirements Development

The proposed paper will focus on the Project Management and Systems Engineering approach utilized to develop a set of both integrated and cohesive requirements for the Exploration Launch Office, within the Constellation Program. A summary of the programmatic drivers which influenced the approach along with details of the resulting implementation will be discussed as well as metrics evaluating the efficiency and accuracy of the various requirements development activities. Requirements development activities will focus on the procedures utilized to ensure that technical content was valid and mature in preparation for the Crew Launch Vehicle and Constellation System s Requirements Reviews. This discussion will begin at initial requirements development during the Exploration Systems Architecture Study and progress through formal development of the program structure. Specific emphasis will be given to development and validation of the requirements. This discussion will focus on approaches to garner the appropriate requirement owners (or customers), project infrastructure utilized to emphasize proper integration, and finally the procedure to technically mature, verify and validate the requirements. Examples of requirements being implemented on the Launch Vehicle (systems, interfaces, test & verification) will be utilized to demonstrate the various processes and also provide a top level understanding of the launch vehicle(s) performance goals. Details may also be provided on the approaches for verification, which range from typical aerospace hardware development (qualification/acceptance) through flight certification (flight test, etc.). The primary intent of this paper is to provide a demonstrated procedure for the development of a mature, effective, integrated set of requirements on a complex system, which also has the added intricacies of both heritage and new hardware development integration. Ancillary focus of the paper will include discussion of Test and Verification approaches along with top level systems/elements performance capabilities.

Holladay, Jon B.↗

Invention-driven marketing

Suppose you have just created a revolutionary bicycle suspension which allows a bike to be ridden over rough terrain at 60 miles per hour. In addition, suppose that you are deeply concerned about the plight of hungry children. Which should you do: be sure all hungry children have bicycles; transfer the technology for your new suspension to bicycle manufacturers worldwide; or start a company to supply premium sports bicycle based on your patented technology, and donate the profits to a charity which feeds hungry children? Woven through this somewhat trivial example is the paradox of technology transfer - the supplier (owner) may want to transfer technology; but to succeed, he or she must reformulate the problem as a user need for which there is a new and better solution. Successful technology transfer is little more than good marketing applied to an existing invention, process, or capability. You must identify who needs the technology, why they need it, why the new technology is better than alternatives, how much the customers are willing and able to pay for these benefits, and how to distribute products based on the technology tc the target customers. In market-driven development, the term 'technology transfer' is rarely used. The developers focus on studying user needs and designing solution They may have technology needs, but they don't have technology in search of a use.

Carlson, William E.↗

Wireless Self-Acquistion of 12-Lead ECG via Android Smart Phone

Researchers at NASA s Johnson Space Center and at Orbital Research, Inc. (a NASA SBIR grant recipient) have recently developed a dry-electrode harness that allows for self-acquisition of resting 12-lead ECGs by minimally trained laypersons. When used in conjunction with commercial wireless (e.g., Bluetooth(TM) or 802.11-enabled) 12-lead ECG devices and custom smart phone-based software, the collected 12-lead ECG data can also immediately be forwarded from any geographic location within cellular range to the user s physician(s) of choice. The system can also be used to immediately forward to central receiving stations 12-lead ECG data collected during space flight or during activities in any remote terrestrial location supported by an internet or cellular phone infrastructure. The main novel aspects of the system are first, the dry-electrode 12-lead ECG harness itself, and second, an accompanying Android(TM) smart phone-based wireless 12-lead ECG capability. The ECG harness nominally employs dry electrodes manufactured by Orbital Research, Inc, recently cleared through the Food and Drug Administration (FDA). However, other dry electrodes that are not yet FDA cleared, for example those recently developed by Nanosonic, Inc as part of another NASA SBIR grant, can also be used. The various advantageous features of the harness include: 1) laypersons can be quickly instructed on its correct use, remotely if necessary; 2) all tangled "leadwire spaghetti" is eliminated, as is the common clinical problem of "leadwire reversal"; 3) all adhesives and disposables are also eliminated, the harness being fully reusable; if multiple individuals intend to use use the same harness, then standard antimicrobial wipes can be employed to sterilize the dry electrodes (and harness surface if needed) between users; 5) padded cushions at the lateral sides of the torso function to press the left arm (LA) and right arm (RA) dry electrodes mounted on the cushions against sideward or downward-rested arms of the subject; 6) sufficient distal placement of the arm electrodes achieves good electrode abutment to the arms without the need for adhesives, straps, bands, bracelets, or gloves; 7) padding over the sternum avoids "tenting" in the V1 through V3 (and, when present, the V3R) electrode positions; 8) easy-to-don, one-piece design with an adjustable, front-side single point of connection and an adjustable shoulder strap; and 9) Lund or "modified Lund" placement of the dry electrodes, the results of which more effectively reproduce results from "standard" 12-lead ECG placements than do results from Mason-Likar placements. The main limitation of the harness is that "one size does not fit all", meaning that an appropriately sized harness (small, medium, large, etc) must be chosen on the basis of an individual's size. To facilitate the use of the harness with inexpensive, commodity-grade cell phones and tablet devices, 12-lead ECG software is also being developed to accompany the harness for wireless use with Android. For this part of the project, NASA has teamed with TopCoder, Inc and the Harvard-affiliated NASA Tournament Lab in sponsoring java-based software programming contests through TopCoder. While ECG signals from the harness can already be wirelessly received and thoroughly processed (locally or remotely) by commercial-grade conventional (as well as advanced) 12-lead ECG software running on Microsoft Windows(TM), the Android-based software, once completed, will "cast a wider net" by allowing for a greater percentage of cell phone owners to participate in inexpensive, store-and-forward recordings of 12-lead ECGs worldwide, including for example Android cell phone users in many remote, third-world locations. At the time of writing, the Android 12-lead ECG software platform consists of a basic but expanding graphical user interface and accompanying software that: 1) wirelessly receives the 12-lead ECG data stream from a Bluetooth-based, FDA-cleared 12-leaCG device attached to the harness; 2) locally stores the same data in binary format to the SD card on the Android cell phone; and 3) makes the data stream in available in real time, for now to TopCoder's java programming contestants.

Schlegel, Todd T.↗

Between the Rock and a Hard Place: The CCMC as a Transit Station Between Modelers and Forecasters

The Community Coordinated Modeling Center (CCMC) is a US inter-agency activity aiming at research in support of the generation of advanced space weather models. As one of its main functions, the CCMC provides to researchers the use of space science models, even if they are not model owners themselves. The second CCMC activity is to support Space Weather forecasting at national Space Weather Forecasting Centers. This second activity involved model evaluations, model transitions to operations, and the development of draft Space Weather forecasting tools. This presentation will focus on the latter element. Specifically, we will discuss the process of transition research models, or information generated by research models, to Space Weather Forecasting organizations. We will analyze successes as well as obstacles to further progress, and we will suggest avenues for increased transitioning success.

Hesse, Michael↗

The computer simulation of automobile use patterns for defining battery requirements for electric cars

A Monte Carlo simulation process was used to develop the U.S. daily range requirements for an electric vehicle from probability distributions of trip lengths and frequencies and average annual mileage data. The analysis shows that a car in the U.S. with a practical daily range of 82 miles (132 km) can meet the needs of the owner on 95% of the days of the year, or at all times other than his long vacation trips. Increasing the range of the vehicle beyond this point will not make it more useful to the owner because it will still not provide intercity transportation. A daily range of 82 miles can be provided by an intermediate battery technology level characterized by an energy density of 30 to 50 watt-hours per pound (66 to 110 W-hr/kg). Candidate batteries in this class are nickel-zinc, nickel-iron, and iron-air. The implication of these results for the research goals of far-term battery systems suggests a shift in emphasis toward lower cost and greater life and away from high energy density.

Schwartz, H. J.↗

Using Modern Methodologies with Maintenance Software

Jet Propulsion Laboratory uses multi-mission software produced by the Mission Planning and Sequencing (MPS) team to process, simulate, translate, and package the commands that are sent to a spacecraft. MPS works under the auspices of the Multi-Mission Ground Systems and Services (MGSS). This software consists of nineteen applications that are in maintenance. The MPS software is classified as either class B (mission critical) or class C (mission important). The scheduling of tasks is difficult because mission needs must be addressed prior to performing any other tasks and those needs often spring up unexpectedly. Keeping track of the tasks that everyone is working on is also difficult because each person is working on a different software component. Recently the group adopted the Scrum methodology for planning and scheduling tasks. Scrum is one of the newer methodologies typically used in agile development. In the Scrum development environment, teams pick their tasks that are to be completed within a sprint based on priority. The team specifies the sprint length usually a month or less. Scrum is typically used for new development of one application. In the Scrum methodology there is a scrum master who is a facilitator who tries to make sure that everything moves smoothly, a product owner who represents the user(s) of the software and the team. MPS is not the traditional environment for the Scrum methodology. MPS has many software applications in maintenance, team members who are working on disparate applications, many users, and is interruptible based on mission needs, issues and requirements. In order to use scrum, the methodology needed adaptation to MPS. Scrum was chosen because it is adaptable. This paper is about the development of the process for using scrum, a new development methodology, with a team that works on disparate interruptible tasks on multiple software applications.

Scrum↗

The Value of Being a Trustworthy Repository

Today, NASA's Earth Observing System Data and Information System (EOSDIS), a system ofactive archives is attaching the CoreTrustSeal to its websites signifying that it merits theconfidence of its user community. But what value does being a trustworthy repository impart to auser? What does it mean to the owners and operators of repositories? What will it mean in thefuture? EOSDIS was started in the 1990s based on a framework of discipline-oriented, geographicallydistributed centers of expertise, named Distributed Active Archive Centers (DAACs). The functionof EOSDIS is to collect Earth Science data sensor measurements (principally those created andneeded by NASA) and manage the data and many derived digital products. EOSDIS providesmany services, including processing, curating, documenting, disseminating, and enabling datadiscovery as well as efficient use of the data. The EOSDIS has been operational over 25 years andmany lessons have been learned relative to the TRUST principles. During the tenure of EOSDIS,many changes have occurred as we have increased the size of the collection from gigabytes totens of petabytes and the distribution of the data to millions of users. We have had severalstages of system evolution that have improved EOSDIS in order to meet both stakeholder andcustomer expectations. This type of evolution is an on-going process to ensure that ourrepositories remain trustworthy. It is also important that our own community of data managersand system engineers add value in being trustworthy. This paper will discuss approaches to change within a large system of Earth Science data and services, while remaining a trustworthyrepository.

Behnke, Jeanne↗

Spatially Characterizing Effective Timber Supply

The structure of a computer-oriented cartographic model for assessing roundwood supply for generation of base load electricity is discussed. The model provides an analytical procedure for coupling spatial information of harvesting economics and owner willingness to sell stumpages. Supply is characterized in terms of standing timber; of accessibility considering various harvesting and hauling factors; and of availability as affected by ownership and residential patterns. Factors governing accessibility to timber include effective harvesting distance to haulic roads as modified by barriers and slopes. Haul distance is expressed in units that take into account the relative ease of travel along various road types to a central processing facility. Areas of accessible timber are grouped into spatial units, termed 'timbersheds', of common access to particular haul road segments that belong to unique 'transport zones'. Timber availability considerations include size of ownership parcels, housing density and excluded areas. The analysis techniques are demonstrated for a cartographic data base in western Massachusetts.

Berry, J. K.↗

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Key Decision Record Creation and Approval Module

Retaining good key decision records is critical to ensuring the success of a project or operation. Having adequately documented decisions with supporting documents and rationale can greatly reduce the amount of rework or reinvention over a project's, vehicle's, or facility's lifecycle. Stennis Space Center developed and uses a software tool that automates the Key Decision Record (KDR) process for its engineering and test projects. It provides the ability for a user to log key decisions that are made during the course of a project. By customizing Parametric Technology Corporation's (PTC) Windchill product, the team was able to log all information about a decision, and electronically route that information for approval. Customizing the Windchill product allowed the team to directly connect these decisions to the engineering data that it might affect and notify data owners of the decision. The user interface was created in JSP and Javascript, within the OOTB (Out of the Box) Windchill product, allowing users to create KDRs. Not only does this interface allow users to create and track KDRs, but it also plugs directly into the OOTB ability to associate these decision records with other relevant engineering data such as drawings, designs, models, requirements, or specifications

Hebert, Barrt↗

The computer simulation of automobile use patterns for defining battery requirements for electric cars

The modeling process of a complex system, based on the calculation and optimization of the system parameters, is complicated in that some parameters can be expressed only as probability distributions. In the present paper, a Monte Carlo technique was used to determine the daily range requirements of an electric road vehicle in the United States from probability distributions of trip lengths, frequencies, and average annual mileage data. The analysis shows that a daily range of 82 miles meets to 95% of the car-owner requirements at all times with the exception of long vacation trips. Further, it is shown that the requirement of a daily range of 82 miles can be met by a (intermediate-level) battery technology characterized by an energy density of 30 to 50 Watt-hours per pound. Candidate batteries in this class are nickel-zinc, nickel-iron, and iron-air. These results imply that long-term research goals for battery systems should be focused on lower cost and longer service life, rather than on higher energy densities

Schwartz, H.-J.↗