Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Audit”

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 487 records · Page 27

Supplier Management System

Supplier Management System (SMS) allows for a consistent, agency-wide performance rating system for suppliers used by NASA. This version (2.0) combines separate databases into one central database that allows for the sharing of supplier data. Information extracted from the NBS/Oracle database can be used to generate ratings. Also, supplier ratings can now be generated in the areas of cost, product quality, delivery, and audit data. Supplier data can be charted based on real-time user input. Based on these individual ratings, an overall rating can be generated. Data that normally would be stored in multiple databases, each requiring its own log-in, is now readily available and easily accessible with only one log-in required. Additionally, the database can accommodate the storage and display of quality-related data that can be analyzed and used in the supplier procurement decision-making process. Moreover, the software allows for a Closed-Loop System (supplier feedback), as well as the capability to communicate with other federal agencies.

Ramirez, Eric↗

JWST OTE Development Status

This slide presentation reviews the status of the optical telescope element (OTE) for the James Webb Space Telescope (JWST). Information about the cryotests that have been performed, and the test of the Primary Mirror Segment Assembly (PMSA) is included. Also views of the progress on the secondary, tertiary Mirror Segment Assembly and the fine steering motor are included. Information is included about the status of other structures. The critical design audit (CDA) of the OTE is scheduled for October of 2009.

Keski-Kuha, Ritva↗

Unified Communications for Space Inventory Management

To help assure mission success for long-duration exploration activities, NASA is actively pursuing wireless technologies that promote situational awareness and autonomy. Wireless technologies are typically extensible, offer freedom from wire tethers, readily support redundancy, offer potential for decreased wire weight, and can represent dissimilar implementation for increased reliability. In addition, wireless technologies can enable additional situational awareness that otherwise would be infeasible. For example, addition of wired sensors, the need for which might not have been apparent at the outset of a program, night be extremely costly due in part to the necessary routing of cables through the vehicle. RFID, or radio frequency identification, is a wireless technology with the potential for significant savings and increased reliability and safety in space operations. Perhaps the most obvious savings relate to the application of inventory management. A fully automated inventory management system is highly desirable for long-term sustaining operations in space environments. This assertion is evidenced by inventory activities on the International Space Station, which represents the most extensive inventory tracking experience base in the history of space operations. In the short tern, handheld RFID readers offer substantial savings owing to reduced crew time for inventory audits. Over the long term, a combination of improved RFID technology and operational concepts modified to fully utilize the technology should result in space based inventory management that is highly reliable and requires very little crew time. In addition to inventory management, RFID is likely to find space applications in real-time location and tracking systems. These could vary from coarse-resolution RFID portals to the high resolution afforded by ultra-wideband (UWB) RFID. Longer range RFID technologies that leverage passive surface acoustic wave (SAW) devices are being investigated to track assets on a lunar or planetary surface.

Gifford, Kevin K.↗

A Reference Model for Software and System Inspections. White Paper

Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level.

He, Lulu↗

A Quality System Database

A quality system database (QSD), and software to administer the database, were developed to support recording of administrative nonconformance activities that involve requirements for documentation of corrective and/or preventive actions, which can include ISO 9000 internal quality audits and customer complaints.

Snell, William H.↗

Adding Hierarchical Objects to Relational Database General-Purpose XML-Based Information Managements

NETMARK is a flexible, high-throughput software system for managing, storing, and rapid searching of unstructured and semi-structured documents. NETMARK transforms such documents from their original highly complex, constantly changing, heterogeneous data formats into well-structured, common data formats in using Hypertext Markup Language (HTML) and/or Extensible Markup Language (XML). The software implements an object-relational database system that combines the best practices of the relational model utilizing Structured Query Language (SQL) with those of the object-oriented, semantic database model for creating complex data. In particular, NETMARK takes advantage of the Oracle 8i object-relational database model using physical-address data types for very efficient keyword searches of records across both context and content. NETMARK also supports multiple international standards such as WEBDAV for drag-and-drop file management and SOAP for integrated information management using Web services. The document-organization and -searching capabilities afforded by NETMARK are likely to make this software attractive for use in disciplines as diverse as science, auditing, and law enforcement.

Lin, Shu-Chun↗

Distinguishing Provenance Equivalence of Earth Science Data

Reproducibility of scientific research relies on accurate and precise citation of data and the provenance of that data. Earth science data are often the result of applying complex data transformation and analysis workflows to vast quantities of data. Provenance information of data processing is used for a variety of purposes, including understanding the process and auditing as well as reproducibility. Certain provenance information is essential for producing scientifically equivalent data. Capturing and representing that provenance information and assigning identifiers suitable for precisely distinguishing data granules and datasets is needed for accurate comparisons. This paper discusses scientific equivalence and essential provenance for scientific reproducibility. We use the example of an operational earth science data processing system to illustrate the application of the technique of cascading digital signatures or hash chains to precisely identify sets of granules and as provenance equivalence identifiers to distinguish data made in an an equivalent manner.

Tilmes, Curt↗

NASA Tech Briefs, June 2003

Topics covered include: Nulling Infrared Radiometer for Measuring Temperature; The Ames Power Monitoring System; Hot Films on Ceramic Substrates for Measuring Skin Friction; Probe Without Moving Parts Measures Flow Angle; Detecting Conductive Liquid Leaking from Nonconductive Pipe; Adaptive Suppression of Noise in Voice Communications; High-Performance Solid-State W-Band Power Amplifiers; Microbatteries for Combinatorial Studies of Conventional Lithium-Ion Batteries; Correcting for Beam Aberrations in a Beam-Waveguide Antenna; Advanced Rainbow Solar Photovoltaic Arrays; Metal Side Reflectors for Trapping Light in QWIPs; Software for Collaborative Engineering of Launch Rockets; Software Assists in Extensive Environmental Auditing; Software Supports Distributed Operations via the Internet; Software Estimates Costs of Testing Rocket Engines; yourSky: Custom Sky-Image Mosaics via the Internet; Software for Managing Inventory of Flight Hardware; Lower-Conductivity Thermal-Barrier Coatings; Process for Smoothing an Si Substrate after Etching of SiO2; Flexible Composite-Material Pressure Vessel; Treatment to Destroy Chlorohydrocarbon Liquids in the Ground; Noncircular Cross Sections Could Enhance Mixing in Sprays; Small, Untethered, Mobile Roots for Inspecting Gas Pipes; Paint-Overspray Catcher; Preparation of Regular Specimens for Atom Probes; Inverse Tomo-Lithography for Making Microscopic 3D Parts; Predicting and Preventing Incipient Flameout in Combustors; MEMS-Based Piezoelectric/Electrostatic Inchworm Actuator; Metallized Capillaries as Probes for Raman Spectroscopy; Adaptation of Mesoscale Weather Models to Local Forecasting; Aerodynamic Design using Neural Networks; Combining Multiple Gyroscope Outputs for Increased Accuracy; and Improved Collision-Detection Method for Robotic Manipulator.

Source record↗

Reusable Solid Rocket Motor - Accomplishments, Lessons, and a Culture of Success

The Reusable Solid Rocket Motor represents the largest solid rocket motor ever flown and the only human rated solid motor. Each Reusable Solid Rocket Motor (RSRM) provides approximately 3-million lb of thrust to lift the integrated Space Shuttle vehicle from the launch pad. The motors burn out approximately 2 minutes later, separate from the vehicle and are recovered and refurbished. The size of the motor and the need for high reliability were challenges. Thrust shaping, via shaping of the propellant grain, was needed to limit structural loads during ascent. The motor design evolved through several block upgrades to increase performance and to increase safety and reliability. A major redesign occurred after STS-51L with the Redesigned Solid Rocket Motor. Significant improvements in the joint sealing systems were added. Design improvements continued throughout the Program via block changes with a number of innovations including development of low temperature o-ring materials and incorporation of a unique carbon fiber rope thermal barrier material. Recovery of the motors and post flight inspection improved understanding of hardware performance, and led to key design improvements. Because of the multidecade program duration material obsolescence was addressed, and requalification of materials and vendors was sometimes needed. Thermal protection systems and ablatives were used to protect the motor cases and nozzle structures. Significant understanding of design and manufacturing features of the ablatives was developed during the program resulting in optimization of design features and processing parameters. The project advanced technology in eliminating ozone-depleting materials in manufacturing processes and the development of an asbestos-free case insulation. Manufacturing processes for the large motor components were unique and safety in the manufacturing environment was a special concern. Transportation and handling approaches were also needed for the large hardware segments. The reusable solid rocket motor achieved significant reliability via process control, ground test programs, and postflight assessment. Process control is mandatory for a solid rocket motor as an acceptance test of the delivered product is not feasible. Process control included process failure modes and effects analysis, statistical process control, witness panels, and process product integrity audits. Material controls and inspections were maintained throughout the sub tier vendors. Material fingerprinting was employed to assess any drift in delivered material properties. The RSRM maintained both full scale and sub-scale test articles. These enabled continuous improvement of design and evaluation of process control and material behavior. Additionally RSRM reliability was achieved through attention to detail in post flight assessment to observe any shift in performance. The postflight analysis and inspections provided invaluable reliability data as it enables observation of actual flight performance, most of which would not be available if the motors were not recovered. These unique challenges, features of the reusable solid rocket motor, materials and manufacturing issues, and design improvements will be discussed in the paper.

Moore, Dennis R.↗

Dryden Flight Research Center Critical Chain Project Management Implementation

In Fiscal Year 2011 Dryden Flight Research Center (DFRC) implemented a new project management system called Critical Chain Project Management (CCPM). Recent NASA audits have found that the Dryden workforce is strained under increasing project demand and that multi-tasking has been carried to a whole new level at Dryden. It is very common to have an individual work on 10 different projects during a single pay period. Employee surveys taken at Dryden have identified work/life balance as the number one issue concerning employees. Further feedback from the employees indicated that project planning is the area needing the most improvement. In addition, employees have been encouraged to become more innovative, improve job skills, and seek ways to improve overall job efficiency. In order to deal with these challenges, DFRC management decided to adopt the CCPM system that is specifically designed to operate in a resource constrained multi-project environment. This paper will discuss in detail the rationale behind the selection of CCPM and the goals that will be achieved through this implementation. The paper will show how DFRC is tailoring the CCPM system to the flight research environment as well as laying out the implementation strategy. Results of the ongoing implementation will be discussed as well as change management challenges and organizational cultural changes. Finally this paper will present some recommendations on how this system could be used by selected NASA projects or centers.

Hines, Dennis O.↗

Security Data Warehouse Application

The Security Data Warehouse (SDW) is used to aggregate and correlate all JSC IT security data. This includes IT asset inventory such as operating systems and patch levels, users, user logins, remote access dial-in and VPN, and vulnerability tracking and reporting. The correlation of this data allows for an integrated understanding of current security issues and systems by providing this data in a format that associates it to an individual host. The cornerstone of the SDW is its unique host-mapping algorithm that has undergone extensive field tests, and provides a high degree of accuracy. The algorithm comprises two parts. The first part employs fuzzy logic to derive a best-guess host assignment using incomplete sensor data. The second part is logic to identify and correct errors in the database, based on subsequent, more complete data. Host records are automatically split or merged, as appropriate. The process had to be refined and thoroughly tested before the SDW deployment was feasible. Complexity was increased by adding the dimension of time. The SDW correlates all data with its relationship to time. This lends support to forensic investigations, audits, and overall situational awareness. Another important feature of the SDW architecture is that all of the underlying complexities of the data model and host-mapping algorithm are encapsulated in an easy-to-use and understandable Perl language Application Programming Interface (API). This allows the SDW to be quickly augmented with additional sensors using minimal coding and testing. It also supports rapid generation of ad hoc reports and integration with other information systems.

Vernon, Lynn R.↗

Multimodal information Management: Evaluation of Auditory and Haptic Cues for NextGen Communication Displays

Auditory communication displays within the NextGen data link system may use multiple synthetic speech messages replacing traditional ATC and company communications. The design of an interface for selecting amongst multiple incoming messages can impact both performance (time to select, audit and release a message) and preference. Two design factors were evaluated: physical pressure-sensitive switches versus flat panel "virtual switches", and the presence or absence of auditory feedback from switch contact. Performance with stimuli using physical switches was 1.2 s faster than virtual switches (2.0 s vs. 3.2 s); auditory feedback provided a 0.54 s performance advantage (2.33 s vs. 2.87 s). There was no interaction between these variables. Preference data were highly correlated with performance.

Begault, Durand R.↗

Configuration Management Process Assessment Strategy

Purpose: To propose a strategy for assessing the development and effectiveness of configuration management systems within Programs, Projects, and Design Activities performed by technical organizations and their supporting development contractors. Scope: Various entities CM Systems will be assessed dependent on Project Scope (DDT&E), Support Services and Acquisition Agreements. Approach: Model based structured against assessing organizations CM requirements including best practices maturity criteria. The model is tailored to the entity being assessed dependent on their CM system. The assessment approach provides objective feedback to Engineering and Project Management of the observed CM system maturity state versus the ideal state of the configuration management processes and outcomes(system). center dot Identifies strengths and risks versus audit gotcha's (findings/observations). center dot Used "recursively and iteratively" throughout program lifecycle at select points of need. (Typical assessments timing is Post PDR/Post CDR) center dot Ideal state criteria and maturity targets are reviewed with the assessed entity prior to an assessment (Tailoring) and is dependent on the assessed phase of the CM system. center dot Supports exit success criteria for Preliminary and Critical Design Reviews. center dot Gives a comprehensive CM system assessment which ultimately supports configuration verification activities.*

Henry, Thad↗

Analysis of Space Station Centrifuge Rotor Bearing Systems: A Case Study

A team of NASA bearing and lubrication experts was assembled to assess the risk for the rolling-element bearings used in the International Space Station (ISS) centrifuge rotor (CR) to seize or otherwise fail to survive for the required 10-year life. The CR was designed by the Japan Aerospace Exploration Agency and their subcontractor, NEC Toshiba Space Systems, Ltd. (NTSpace). The NASA team performed a design audit for the most critical rolling-element bearing systems and reviewed the lubricant selected. There is uncertainty regarding the ability of the Braycote 601 grease (Castrol Limited) to reliably provide the 10-year continuous life required without relubrication of the system. The fatigue life of the Rotor Shaft Assembly (RSA) spring loaded face-to-face mount at a 99-percent probability of survival (L1 life) for the ball bearing set was estimated at 700 million hours and the single ball bearing (Row 3) at 58 million hours. These lives satisfy the mission requirements for fatigue. Rolling-element seizure tests on the RSA and fluid slip joint bearings were found unlikely to stop the centrifuge, which can cause damage to the ISS structure. The spin motor encoder duplex angular-contact ball bearings have a hard preload and a large number of small balls have the highest risk of failure. These bearings were not tested for seizure even though they are less tolerant to debris or internal clearance reductions.

Poplawski, Joseph V.↗

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

Ground System Architecture↗

IT Security Support for the Spaceport Command Control System Development

My job title is IT Security support for the Spaceport Command & Control System Development. As a cyber‐security analyst it is my job to ensure NASA's information stays safe from cyber threats, such as, viruses, malware and denial-of-service attacks by establishing and enforcing system access controls. Security is very important in the world of technology and it is used everywhere from personal computers to giant networks ran by Government agencies worldwide. Without constant monitoring analysis, businesses, public organizations and government agencies are vulnerable to potential harmful infiltration of their computer information system. It is my responsibility to ensure authorized access by examining improper access, reporting violations, revoke access, monitor information request by new programming and recommend improvements. My department oversees the Launch Control System and networks. An audit will be conducted for the LCS based on compliance with the Federal Information Security Management Act (FISMA) and The National Institute of Standards and Technology (NIST). I recently finished analyzing the SANS top 20 critical controls to give cost effective recommendations on various software and hardware products for compliance. Upon my completion of this internship, I will have successfully completed my duties as well as gain knowledge that will be helpful to my career in the future as a Cyber Security Analyst.

IT Security↗

Cassini Mission Sequence Subsystem (MSS)

This paper describes my work with the Cassini Mission Sequence Subsystem (MSS) team during the summer of 2011. It gives some background on the motivation for this project and describes the expected benefit to the Cassini program. It then introduces the two tasks that I worked on - an automatic system auditing tool and a series of corrections to the Cassini Sequence Generator (SEQ_GEN) - and the specific objectives these tasks were to accomplish. Next, it details the approach I took to meet these objectives and the results of this approach, followed by a discussion of how the outcome of the project compares with my initial expectations. The paper concludes with a summary of my experience working on this project, lists what the next steps are, and acknowledges the help of my Cassini colleagues.

solstice mission↗

Technology Infusion Challenges from a Decision Support Perspective

In a restricted science budget environment and increasingly numerous required technology developments, the technology investment decisions within NASA are objectively more and more difficult to make such that the end results are satisfying the technical objectives and all the organizational constraints. Under these conditions it is rationally desirable to build an investment portfolio, which has the highest possible technology infusion rate. Arguably the path to infusion is subject to many influencing factors, but here only the challenges associated with the very initial stages are addressed: defining the needs and the subsequent investment decision-support process. It is conceivable that decision consistency and possibly its quality suffer when the decision-making process has limited or no traceability. This paper presents a structured decision-support framework aiming to provide traceable, auditable, infusion- driven recommendations towards a selection process in which these recommendations are used as reference points in further discussions among stakeholders. In this framework addressing well-defined requirements, different measures of success can be defined based on traceability to specific selection criteria. As a direct result, even by using simplified decision models the likelihood of infusion can be probed and consequently improved.

Adumitroaie, V.↗