SEARCH · Engineering Papers

Results for “standard operating procedure”

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.

SourceResearch connectionFrom yearThrough year

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

At least 451 records · Page 25

All sources NASA NTRS DOE OSTI

NASA NTRS2018

Establishing and Monitoring an Aseptic Workspace

When are aseptic operations necessary? In order to meet certain bioburden requirements, some components must undergo dry heat microbial reduction (DHMR) or other sterilizing procedures. If sensitive surfaces must be re-exposed after DHMR, this could compromise the bioburden levels. Recontaminating sterilized surfaces could be costly both in time by requiring repeated DHMR and risk to the hardware, which may not be compatible with repeated high temperature bakes. In order to prevent recontamination of the sensitive surfaces, an aseptic environment and sterile technique must be employed. Aseptic environments mean working in a space with almost no detectable bioburden in the air or on surfaces. Ideally, DHMR happens as late as possible to avoid requiring aseptic operations, as it can be considered a high-risk operations. Preparing the cleanroom for aseptic operations Establishing an ISO (International Organization for Standardization) class 5 space to minimize airborne particles. Maintain low bioburden in the cleanroom by using biocidal cleaners. Using multiple biocidal techniques decreases the likelihood of selecting for resistant microorganisms. 70% Isopropyl Alcohol (IPA) denatures the proteins in a microorganism (note: 70% IPA is better at killing microorganisms than 100% IPA) 7% hydrogen peroxide: damages DNA and proteins through oxygen radical damage. Ultraviolet-C (UV-C) lamps: causes crosslinking in DNA which prevents replication. Monitor cleanroom regularly for bioburden trending: Standard bioassay: Swab or wipe samples of cleanroom surfaces processed for colony forming unity (viable or spore selected); Rapid bioassay: Adenosine triphosphate (ATP) or Limulus amebocyte lysate (LAL) for a bioburden snapshot. High levels can signal an immediate re-cleaning before standard bioassay samples are taken. Airborne monitoring: Active (pulling air through a filter) or passive (particle fallout) for bioburden. Verify bioburden levels just before aseptic operation. Test hardware and cleanroom surfaces and air 3 days before the planned aseptic operation. Rapid bioburden just before aseptic operation to ensure room was not re-contaminated. Preparing personnel and tools: Personnel training. Everyone in the cleanroom: Standard cleanroom certification Everyone on the team: 1 day Planetary Protection overview. Aseptic operators only: Half-day aseptic operations training. Covers sterile garmenting/gloves, Sterile handling with a focus on contact transfer risk, tool/GSE preparation, and two-operator system for opening sterilized tools/components. Tool sterilization: All tools to be used during an aseptic operation need to be identified. Compatible tools are sterilized by DHMR or Autoclave. Double wrapped so that the exterior bag can be handled by a non-sterile operator, and the sterile. Tools that are not compatible with high heat do not come in contact with sensitive surfaces: either substitutes are found, or tools are isolated by wrapping in sterile foil. During an aseptic operation. Pre-task to make sure everyone understands the operations, who is handling what, and when the most critical surfaces will be exposed. Monitoring during the operation. Bioburden: active and passive airborne bioburden sampling, glove-tip dabs onto a plate after completion of operation (3 days for results). Particles: real time particle counter constantly running, with alarm for exceeding ISO 5 conditions.

aseptic processing↗

NASA NTRS2005

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗

NASA NTRS2024

Autonomous Medical Officer Support (AMOS) Software Technology Demonstrations on the International Space Station (ISS)

Performance of medical procedures in spaceflight beyond low Earth orbit (LEO) requires novel solutions to replace real-time ground support because as distance from Earth increases, communication latencies increase, hampering remote guidance. The Autonomous Medical Officer Support Software (AMOS) Technology Demonstrations on the International Space Station (ISS) trialed a novel software tool that shifts the emphasis from preflight training and real-time remote guidance (current ISS paradigm) to a new standard of multi-dimensional in-flight just-in-time (JIT) instruction. The AMOS platform is a skill management tool for all mission phases and currently features comprehensive training and guidance modules for urinary bladder and renal ultrasound examinations. Variability in Subject anatomy, Operator experience, and Operator receptiveness to instruction during autonomous exams are persistent but manageable limitations. Here we report the first successful demonstrations of autonomous imaging activities in the operational setting of spaceflight, validating this autonomous guidance proof of concept.

Douglas Ebert↗

NASA NTRS2004

Tool for Insertion of a Fiber-Optic Terminus in a Connector

A tool has been developed for the special purpose of inserting the terminus of an optical fiber in a cable connector that conforms to NASA Specification SSQ- 21635. What prompted the development of the tool was the observation that because of some aspects of the designs of fiber-optic termini and of springs, sealing rings, and a grommet inside the shell of such a connector, there is a tendency for the grommet to become damaged and detached from the sealing rings during installation. It is necessary to ensure the integrity of the grommet for proper sealing and proper functioning of the connector. The special-purpose tool provides the needed protection for the grommet. The grommet-protection tool resembles a funnel into which an axial slit has been cut (see figure). Prior to insertion, the grommet-protection tool is rolled so that one side of the slit overlaps the other side. The rolled-up grommet-protection tool is inserted in one of the connector holes that accommodate the fiber-optic termini and is pushed in until the flange (the wider of the two conical portions) of the tool becomes seated on the connector grommet. Then a special-purpose installation tool is inserted in the flange of the grommet-protection tool and pressed in until it becomes seated in the flange. This operation expands the narrower of the two conical portions of the grommet-protection tool. The installation tool is removed and the grommet-protection tool remains expanded due to the flat surfaces on the axial slit. By use of a standard contact-insertion tool, a fiber-optic terminus is inserted, through the grommet-protection tool, into the connector cavity. By use of a pair of forceps or needle-nose pliers, the grommet-protection tool is then pulled out of the cavity. Finally, the grommet-protection tool is removed from around the installed fiber-optic cable by pulling the cable through the axial slit. Unlike in some prior procedures for installing the fiber-optic termini in the connector, the procedure that involves the use of the present grommet-protection tool does not include the use of lubricants that can contaminate the interior of the connector. The grommet-protection tool is made of a fluoropolymer, taking advantage of the flexibility of such polymers and further taking advantage of the inherent slipperiness of fluoropolymers. Although the tool is designed primarily for insertion of a fiber-optic terminus, it might also be useful for extracting a previously installed fiber-optic terminus.

King, Wes↗

NASA NTRS2008

XTCE and XML Database Evolution and Lessons from JWST, LandSat, and Constellation

The database organizations within three different NASA projects have advanced current practices by creating database synergy between the various spacecraft life cycle stakeholders and educating users in the benefits of the Consultative Committee for Space Data Systems (CCSDS) XML Telemetry and Command Exchange (XTCE) format. The combination of XML for managing program data and CCSDS XTCE for exchange is a robust approach that will meet all user requirements using Standards and Non proprietary tools. COTS tools for XTCEKML are very wide and varied. To combine together various low cost and free tools can be more expensive in the long run than choosing a more expensive COTS tool that meets all the needs. This was especially important when deploying in 32 remote sites with no need for licenses. A common mission XTCEKML format between dissimilar systems is possible and is not difficult. Command XMLKTCE is more complex than telemetry and the use of XTCEKML metadata to describe pages and scripts is needed due to the proprietary nature of most current ground systems. Other mission and science products such as spacecraft loads, science image catalogs, and mission operation procedures can all be described with XML as well to increase there flexibility as systems evolve and change. Figure 10 is an example of a spacecraft table load. The word is out and the XTCE community is growing, The f ~ sXt TCE user group was held in October and in addition to ESAESOC, SC02000, and CNES identified several systems based on XTCE. The second XTCE user group is scheduled for March 10, 2008 with LDMC and others joining. As the experience with XTCE grows and the user community receives the promised benefits of using XTCE and XML the interest is growing fast.

Gal-Edd, Jonathan↗

NASA NTRSDate not supplied

Dynamic Channel Assignments for Efficient Use of Aviation Spectrum Allocations

The demand for voice and data communications continues to rise with the emergence of new aerial vehicles into the airspace and the continued growth of aviation operations throughout the National Airspace System (NAS). Recent studies have shown that the anticipated growing demand for spectrum resources will exceed the capacity of existing aviation spectrum allocations. Further, airspace configurations, via assignment of fixed channel allocations within standard service volumes, do not allow for the dynamic and efficient distribution of spectrum resources based on airspace demand; as a result, a new approach to aviation spectrum management is needed to support the forecasted needs of new airspace users. The National Aeronautics and Space Administration (NASA) is investigating applications of artificial intelligence (AI), machine learning (ML), and other advanced concepts to solve a dynamic constraint satisfaction problem which is analogous to the frequency assignment problem faced by aviation. Procedures and strategies for dynamic channel allocation can be borrowed from other large-scale mobile services (i.e., 4G/5G applications) and can provide a novel spectrum management approach that allows for the intelligent utilization of aviation spectrum throughout the airspace while maintaining the strict quality of service prescribed by aeronautical standards.

Communications↗

NASA NTRSDate not supplied

Dynamic Channel Assignments for Efficient Use of Aviation Spectrum Allocations

communications↗

NASA NTRS2016

International Docking Standard (IDSS) Interface Definition Document (IDD) : Revision - E

This International Docking System Standard (IDSS) Interface Definition Document (IDD) is the result of a collaboration by the International Space Station membership to establish a standard docking interface to enable on-orbit crew rescue operations and joint collaborative endeavors utilizing different spacecraft. This IDSS IDD details the physical geometric mating interface and design loads requirements. The physical geometric interface requirements must be strictly followed to ensure physical spacecraft mating compatibility. This includes both defined components and areas that are void of components. The IDD also identifies common design parameters as identified in section 3.0, e.g., docking initial conditions and vehicle mass properties. This information represents a recommended set of design values enveloping a broad set of design reference missions and conditions, which if accommodated in the docking system design, increases the probability of successful docking between different spacecraft. This IDD does not address operational procedures or off-nominal situations, nor does it dictate implementation or design features behind the mating interface. It is the responsibility of the spacecraft developer to perform all hardware verification and validation, and to perform final docking analyses to ensure the needed docking performance and to develop the final certification loads for their application. While there are many other critical requirements needed in the development of a docking system such as fault tolerance, reliability, and environments (e.g. vibration, etc.), it is not the intent of the IDSS IDD to mandate all of these requirements; these requirements must be addressed as part of the specific developer's unique program, spacecraft and mission needs. This approach allows designers the flexibility to design and build docking mechanisms to their unique program needs and requirements. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions. The purpose of the IDSS IDD is to provide basic common design parameters to allow developers to independently design compatible docking systems. The IDSS is intended for uses ranging from crewed to autonomous space vehicles, and from Low Earth Orbit (LEO) to deep-space exploration missions.

docking↗

NASA NTRS1990

OPEX propagation measurements and studies

With the launch of the telecommunications Olympus satellite a new area began for the Olympus Propagation Experiments (OPEX) group. The years of preparations are now paying off - the experiments are underway and the co-operative effort is now turning its attention to the processing and analysis of data and to the interpretation of results. The aim here is to give a short review of the accomplishments made since NAPEX 13 and the work planned for the future. When ESA's Olympus was launched in summer of 1989 it carried a payload producing three unmodulated beacons at 12.5, 19.8, and 29.7 GHz. The main purpose of these beacons is to enable scientists to carry out long term slant path propagation experiments at these frequencies. The OPEX group, which was set up under ESA auspices in 1980, had been preparing for this event very carefully. The specifications for the equipment to be used and the elaboration of standard procedures for data processing and analysis have been worked out jointly. Today the OPEX community includes approximately 30 groups of experimenters. Immediately after achieving platform stability at the orbital location at 341 degrees east, ESA performed the In-Orbit Tests. Most measurements were carried out in Belgium using terminals specially developed for this purpose. A summary of the test results is given.

Arbesser-Rastburg, Bertram↗

NASA NTRSDate not supplied

Strategy for Risk Quantification of Spaceflight Crew Health and Performance Using Dynamic Probabilistic Risk Assessment

At NASA, the Crew Health and Performance (CHP) system represents the span of countermeasures, capabilities, interventions, and tested processes and procedures that in combination work to mitigate the human component of spaceflight mission risk. Across the varying NASA mental models of the CHP system, the different functionalities needed to meet human flight systems standards can be broken down into specific categories (i.e. medical capability, environmental health, behavioral health). These categories can be further broken down into specific subgroups generally associated with the CHP functionalities meant to mitigate or buy down individual human system risks. Taking a similar development approach we seek to leverage dynamic probabilistic risk assessment as a means to quantify and relatively assess the human risk state within the crew health and performance domain. By utilizing existing tools as integrators, we propose a rapid development strategy for incorporating research and operational data that represent the influence of the CHP system functionalities, in order to provide order of magnitudes estimates of the influence on most human system risks outcomes. The model system utilizes a modest cumulative risk approach and that limits the scope to primary paths of influence between the CHP functionalities and human system risks, thus enabling quick prototypes of the integrative effects of CHP functional combinations to solicit valuable feedback from stakeholders and customers on the data, relationship, and structure of the integration.

Drayton Munster↗

NASA NTRS1993

Performance of traffic-alert collision avoidance (TCAS) antennas in the presence of scatterers

The performance of two TCAS systems is studied in the presence of electromagnetic scatterers. TCAS is an aircraft mounted angle of arrival (AOA) system, which estimates the bearing of a signal transmitted from a mode-S transponder on another nearby aircraft (intruder). Two systems are studied: (1) Comparison of Relative Amplitude system (CRA), and (2) Spiral Phase Antenna (SPA). The CRA antenna receives the reply via four switched beams. The bearing is estimated by comparing the amplitudes of the received signal. The SPA is based on the phase interferometer, which utilizes the received phase via sum and difference beams. The AOA is computed by comparing the reply with similar values on a calibration table, which is generated by modeling the TCAS antenna on the bare fuselage of a Boeing 727-200. The antenna patterns for the TCAS are found via high frequency methods based on the Uniform Geometric theory of Diffraction (UTD). By minimizing the standard deviation of the bearing error in a specified angular sector, optimal locations for top and bottom mounted TCAS antennas are found on the Boeing 727-200, 737-300 and 747-200 airframes. It will be shown that the overall bearing errors of the amplitude system are consistently smaller than the spiral phase TCAS. The effect of two types of nearby scatterers--antennas, and engine inlets--is studied. The AT741 L-band blade, DMC60-1 VHF Communication antenna were chosen as being representative antenna interference examples. Models are derived for the blades via a moment method analysis followed by a least squares procedure to synthesize the scattering patterns. Studies were conducted to estimate the minimum separation between the two antennas for acceptable operation. It will be shown that the spiral phase TCAS is adversely affected by the presence of a blade antenna. The amplitude system does not suffer from this limitation, especially for the forward look angles which are of most interest here. A model to represent the inlet scattering is based on the multiple scattering method and UTD. The engine on top of the B727-200 fuselage is modeled by a terminated circular waveguide. Then, the effect of moving the antenna forward on the fuselage is studied. It is again shown that the performance of the amplitude system is superior.

Sampath, K. S.↗

NASA NTRS1996

Automation of Command and Data Entry in a Glovebox Work Volume: An Evaluation of Data Entry Devices

The present study was designed to examine the human-computer interface for data entry while performing experimental procedures within a glovebox work volume in order to make a recommendation to the Space Station Biological Research Project for a data entry system to be used within the Life Sciences Glovebox. Test subjects entered data using either a manual keypad, similar to a standard computer numerical keypad located within the glovebox work volume, or a voice input system using a speech recognition program with a microphone headset. Numerical input and commands were programmed in an identical manner between the two systems. With both electronic systems, a small trackball was available within the work volume for cursor control. Data, such as sample vial identification numbers, sample tissue weights, and health check parameters of the specimen, were entered directly into procedures that were electronically displayed on a video monitor within the glovebox. A pen and paper system with a 'flip-chart' format for procedure display, similar to that currently in use on the Space Shuttle, was used as a baseline data entry condition. Procedures were performed by a single operator; eight test subjects were used in the study. The electronic systems were tested under both a 'nominal' or 'anomalous' condition. The anomalous condition was introduced into the experimental procedure to increase the probability of finding limitations or problems with human interactions with the electronic systems. Each subject performed five test runs during a test day: two procedures each with voice and keypad, one with and one without anomalies, and one pen and paper procedure. The data collected were both quantitative (times, errors) and qualitative (subjective ratings of the subjects).

Steele, Marianne K.↗

NASA NTRS1997

Reference Model for an Open Archival Information System

This document is a technical report for use in developing a consensus on what is required to operate a permanent, or indefinite long-term, archive of digital information. It may be useful as a starting point for a similar document addressing the indefinite long-term preservation of non-digital information. This report establishes a common framework of terms and concepts which comprise an Open Archival Information System (OAIS). It allows existing and future archives to be more meaningfully compared and contrasted. It provides a basis for further standardization of within an archival context and it should promote greater vendor awareness of, and support of , archival requirements. Through the process of normal evolution, it is expected that expansion, deletion, or modification to this document may occur. This report is therefore subject to CCSDS document management and change control procedures.

Source record↗

NASA NTRS2011

NASA's UAS NAS Access Project

The vision of the Unmanned Aircraft System (UAS) Integration in the National Airspace System (NAS) Project is "A global transportation system which allows routine access for all classes of UAS." The goal of the UAS Integration in the NAS Project is to "contribute capabilities that reduce technical barriers related to the safety and operational challenges associated with enabling routine UAS access to the NAS." This goal will be accomplished through a two-phased approach based on development of system-level integration of key concepts, technologies and/or procedures, and demonstrations of integrated capabilities in an operationally relevant environment. Phase 1 will take place the first two years of the Project and Phase 2 will take place the following three years. The Phase 1 and 2 technical objectives are: Phase 1: Developing a gap analysis between current state of the art and the Next Generation Air Transportation System (NextGen) UAS Concept of Operations . Validating the key technical areas identified by this Project . Conducting initial modeling, simulation, and flight testing activities . Completing Sub-project Phase 1 deliverables (spectrum requirements, comparative analysis of certification methodologies, etc.) and continue Phase 2 preparation (infrastructure, tools, etc.) Phase 2: Providing regulators with a methodology for developing airworthiness requirements for UAS, and data to support development of certifications standards and regulatory guidance . Providing systems-level, integrated testing of concepts and/or capabilities that address barriers to routine access to the NAS. Through simulation and flight testing, address issues including separation assurance, communications requirements, and human systems integration in operationally relevant environments. The UAS in the NAS Project will demonstrate solutions in specific technology areas, which will address operational/safety issues related to UAS access to the NAS. Since the resource allocation for this Project is limited ($150M over the five years), the focus is on reducing the technical barriers where NASA has unique capabilities. As a result, technical areas, such as Sense and Avoid (SAA) and beyond line of sight command and control will not be addressed. While these are critical barriers to UAS access, currently, there is a great deal of global effort being exercised to address these challenge areas. Instead, specific technology development in areas where there is certainty that NASA can advance the research to high technology readiness levels will be the Project's focus. Specific sub-projects include Separation Assurance, Human Systems Integration, Communications, Certification, and Integrated Test and Evaluation. Each sub-project will transfer technologies to relevant key stakeholders and decision makers through research transition teams, technology forums, or through other analogous means.

Johnson, Charles W.↗

NASA NTRS1990

An investigation of messy genetic algorithms

Genetic algorithms (GAs) are search procedures based on the mechanics of natural selection and natural genetics. They combine the use of string codings or artificial chromosomes and populations with the selective and juxtapositional power of reproduction and recombination to motivate a surprisingly powerful search heuristic in many problems. Despite their empirical success, there has been a long standing objection to the use of GAs in arbitrarily difficult problems. A new approach was launched. Results to a 30-bit, order-three-deception problem were obtained using a new type of genetic algorithm called a messy genetic algorithm (mGAs). Messy genetic algorithms combine the use of variable-length strings, a two-phase selection scheme, and messy genetic operators to effect a solution to the fixed-coding problem of standard simple GAs. The results of the study of mGAs in problems with nonuniform subfunction scale and size are presented. The mGA approach is summarized, both its operation and the theory of its use. Experiments on problems of varying scale, varying building-block size, and combined varying scale and size are presented.

Goldberg, David E.↗

NASA NTRS1991

Optical studies in the holographic ground station

The Holographic Group System (HGS) Facility in rooms 22 & 123, Building 4708 has been developed to provide for ground based research in determining pre-flight parameters and analyzing the results from space experiments. The University of Alabama, Huntsville (UAH) has researched the analysis aspects of the HGS and reports their findings here. Some of the results presented here also occur in the Facility Operating Procedure (FOP), which contains instructions for power up, operation, and powerdown of the Fluid Experiment System (FES) Holographic Ground System (HGS) Test Facility for the purpose of optically recording fluid and/or crystal behavior in a test article during ground based testing through the construction of holograms and recording of videotape. The alignment of the optical bench components, holographic reconstruction and and microscopy alignment sections were also included in the document for continuity even though they are not used until after optical recording of the test article) setup of support subsystems and the Automated Holography System (AHS) computer. The HGS provides optical recording and monitoring during GCEL runs or development testing of potential FES flight hardware or software. This recording/monitoring can be via 70mm holographic film, standard videotape, or digitized images on computer disk. All optical bench functions necessary to construct holograms will be under the control of the AHS personal computer (PC). These include type of exposure, time intervals between exposures, exposure length, film frame identification, film advancement, film platen evacuation and repressurization, light source diffuser introduction, and control of realtime video monitoring. The completed sequence of hologram types (single exposure, diffuse double exposure, etc.) and their time of occurrence can be displayed, printed, or stored on floppy disk posttest for the user.

Workman, Gary L.↗

NASA NTRS2008

Information Requirements for Supervisory Air Traffic Controllers in Support of a Wake Vortex Departure System

Closely Space Parallel Runway (CSPR) configurations are capacity limited for departures due to the requirement to apply wake vortex separation standards from traffic departing on the adjacent parallel runway. To mitigate the effects of this constraint, a concept focusing on wind dependent departure operations has been developed, known as the Wake Turbulence Mitigation for Departures (WTMD). This concept takes advantage of the fact that crosswinds of sufficient velocity blow wakes generated by aircraft departing from the downwind runway away from the upwind runway. Consequently, under certain conditions, wake separations on the upwind runway would not be required based on wakes generated by aircraft on the downwind runway, as is currently the case. It follows that information requirements, and sources for this information, would need to be determined for airport traffic control tower (ATCT) supervisory personnel who would be charged with decisions regarding use of the procedure. To determine the information requirements, data were collected from ATCT supervisors and controller-in-charge qualified individuals at Lambert-St. Louis International Airport (STL) and George Bush Houston Intercontinental Airport (IAH). STL and IAH were chosen as data collection sites based on the implementation of a WTMD prototype system, operating in shadow mode, at these locations. The 17 total subjects (STL: 5, IAH: 12) represented a broad-base of air traffic experience. Results indicated that the following information was required to support the conduct of WTMD operations: current and forecast weather information, current and forecast traffic demand and traffic flow restrictions, and WTMD System status information and alerting. Subjects further indicated that the requisite information is currently available in the tower cab with the exception of the WTMD status and alerting. Subjects were given a demonstration of a display supporting the prototype systems and unanimously stated that the WTMD status information they felt important was represented. Overwhelmingly, subjects felt that approving, monitoring and terminating the WTMD procedure could be integrated into their supervisory workload.

Lohr, Gary W.↗

NASA NTRS1992

Fortran for the nineties

Fortran has largely enjoyed prominence for the past few decades as the computer programming language of choice for numerically intensive scientific, engineering, and process control applications. Fortran's well understood static language syntax has allowed resulting parsers and compiler optimizing technologies to often generate among the most efficient and fastest run-time executables, particularly on high-end scalar and vector supercomputers. Computing architectures and paradigms have changed considerably since the last ANSI/ISO Fortran release in 1978, and while FORTRAN 77 has more than survived, it's aged features provide only partial functionality for today's demanding computing environments. The simple block procedural languages have been necessarily evolving, or giving way, to specialized supercomputing, network resource, and object-oriented paradigms. To address these new computing demands, ANSI has worked for the last 12-years with three international public reviews to deliver Fortran 90. Fortran 90 has superseded and replaced ISO FORTRAN 77 internationally as the sole Fortran standard; while in the US, Fortran 90 is expected to be adopted as the ANSI standard this summer, coexisting with ANSI FORTRAN 77 until at least 1996. The development path and current state of Fortran will be briefly described highlighting the many new Fortran 90 syntactic and semantic additions which support (among others): free form source; array syntax; new control structures; modules and interfaces; pointers; derived data types; dynamic memory; enhanced I/O; operator overloading; data abstraction; user optional arguments; new intrinsics for array, bit manipulation, and system inquiry; and enhanced portability through better generic control of underlying system arithmetic models. Examples from dynamical astronomy, signal and image processing will attempt to illustrate Fortran 90's applicability to today's general scalar, vector, and parallel scientific and engineering requirements and object oriented programming paradigms. Time permitting, current work proceeding on the future development of Fortran 2000 and collateral standards will be introduced.

Himer, J. T.↗