Sample records for configuration management-document control

  1. Tank waste remediation system configuration management plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    The configuration management program for the Tank Waste Remediation System (TWRS) Project Mission supports management of the project baseline by providing the mechanisms to identify, document, and control the functional and physical characteristics of the products. This document is one of the tools used to develop and control the mission and work. It is an integrated approach for control of technical, cost, schedule, and administrative information necessary to manage the configurations for the TWRS Project Mission. Configuration management focuses on five principal activities: configuration management system management, configuration identification, configuration status accounting, change control, and configuration management assessments. TWRS Projectmore » personnel must execute work in a controlled fashion. Work must be performed by verbatim use of authorized and released technical information and documentation. Application of configuration management will be consistently applied across all TWRS Project activities and assessed accordingly. The Project Hanford Management Contract (PHMC) configuration management requirements are prescribed in HNF-MP-013, Configuration Management Plan (FDH 1997a). This TWRS Configuration Management Plan (CMP) implements those requirements and supersedes the Tank Waste Remediation System Configuration Management Program Plan described in Vann, 1996. HNF-SD-WM-CM-014, Tank Waste Remediation System Configuration Management Implementation Plan (Vann, 1997) will be revised to implement the requirements of this plan. This plan provides the responsibilities, actions and tools necessary to implement the requirements as defined in the above referenced documents.« less

  2. Configuration Management Plan for the Tank Farm Contractor

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    WEIR, W.R.

    The Configuration Management Plan for the Tank Farm Contractor describes configuration management the contractor uses to manage and integrate its technical baseline with the programmatic and functional operations to perform work. The Configuration Management Plan for the Tank Farm Contractor supports the management of the project baseline by providing the mechanisms to identify, document, and control the technical characteristics of the products, processes, and structures, systems, and components (SSC). This plan is one of the tools used to identify and provide controls for the technical baseline of the Tank Farm Contractor (TFC). The configuration management plan is listed in themore » management process documents for TFC as depicted in Attachment 1, TFC Document Structure. The configuration management plan is an integrated approach for control of technical, schedule, cost, and administrative processes necessary to manage the mission of the TFC. Configuration management encompasses the five functional elements of: (1) configuration management administration, (2) configuration identification, (3) configuration status accounting, (4) change control, and (5 ) configuration management assessments.« less

  3. Configuration management plan for waste tank farms and the 242-A evaporator of tank waste remediation system

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Laney, T.

    The configuration management architecture presented in this Configuration Management Plan is based on the functional model established by DOE-STD-1073-93, ``Guide for Operational Configuration Management Program.`` The DOE Standard defines the configuration management program by the five basic program elements of ``program management,`` ``design requirements,`` ``document control,`` ``change control,`` and ``assessments,`` and the two adjunct recovery programs of ``design reconstitution,`` and ``material condition and aging management.`` The CM model of five elements and two adjunct programs strengthen the necessary technical and administrative control to establish and maintain a consistent technical relationship among the requirements, physical configuration, and documentation. Although the DOEmore » Standard was originally developed for the operational phase of nuclear facilities, this plan has the flexibility to be adapted and applied to all life-cycle phases of both nuclear and non-nuclear facilities. The configuration management criteria presented in this plan endorses the DOE Standard and has been tailored specifically to address the technical relationship of requirements, physical configuration, and documentation during the full life cycle of the Waste Tank Farms and 242-A Evaporator of Tank Waste Remediation System.« less

  4. TWRS authorization basis configuration control summary

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Mendoza, D.P.

    This document was developed to define the Authorization Basis management functional requirements for configuration control, to evaluate the management control systems currently in place, and identify any additional controls that may be required until the TWRS [Tank Waste Remediation System] Configuration Management system is fully in place.

  5. System configuration management plan for 101-SY Hydrogen Mitigation Test Project Mini-Data Acquisition and Control System of Tank Waste Remediation System

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vargo, G.F. Jr.

    1994-10-11

    The DOE Standard defines the configuration management program by the five basic program elements of ``program management,`` ``design requirements,`` ``document control,`` ``change control,`` and ``assessments,`` and the two adjunct recovery programs of ``design reconstitution,`` and ``material condition and aging management. The C-M model of five elements and two adjunct programs strengthen the necessary technical and administrative control to establish and maintain a consistent technical relationship among the requirements, physical configuration, and documentation. Although the DOE Standard was originally developed for the operational phase of nuclear facilities, this plan has the flexibility to be adapted and applied to all life-cycle phasesmore » of both nuclear and non-nuclear facilities. The configuration management criteria presented in this plan endorses the DOE Standard and has been tailored specifically to address the technical relationship of requirements, physical configuration, and documentation during the full life-cycle of the 101-SY Hydrogen Mitigation Test Project Mini-Data Acquisition and Control System of Tank Waste Remediation System.« less

  6. Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

  7. Aeropropulsion facilities configuration control: Procedures manual

    NASA Technical Reports Server (NTRS)

    Lavelle, James J.

    1990-01-01

    Lewis Research Center senior management directed that the aeropropulsion facilities be put under configuration control. A Configuration Management (CM) program was established by the Facilities Management Branch of the Aeropropulsion Facilities and Experiments Division. Under the CM program, a support service contractor was engaged to staff and implement the program. The Aeronautics Directorate has over 30 facilities at Lewis of various sizes and complexities. Under the program, a Facility Baseline List (FBL) was established for each facility, listing which systems and their documents were to be placed under configuration control. A Change Control System (CCS) was established requiring that any proposed changes to FBL systems or their documents were to be processed as per the CCS. Limited access control of the FBL master drawings was implemented and an audit system established to ensure all facility changes are properly processed. This procedures manual sets forth the policy and responsibilities to ensure all key documents constituting a facilities configuration are kept current, modified as needed, and verified to reflect any proposed change. This is the essence of the CM program.

  8. Tank waste remediation system privatization infrastructure program requirements and document management process guide

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    ROOT, R.W.

    1999-05-18

    This guide provides the Tank Waste Remediation System Privatization Infrastructure Program management with processes and requirements to appropriately control information and documents in accordance with the Tank Waste Remediation System Configuration Management Plan (Vann 1998b). This includes documents and information created by the program, as well as non-program generated materials submitted to the project. It provides appropriate approval/control, distribution and filing systems.

  9. Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)

    NASA Technical Reports Server (NTRS)

    Niewoehner, Kevin R.; Carter, John (Technical Monitor)

    2001-01-01

    The research accomplishments for the cooperative agreement 'Online Learning Flight Control for Intelligent Flight Control Systems (IFCS)' include the following: (1) previous IFC program data collection and analysis; (2) IFC program support site (configured IFC systems support network, configured Tornado/VxWorks OS development system, made Configuration and Documentation Management Systems Internet accessible); (3) Airborne Research Test Systems (ARTS) II Hardware (developed hardware requirements specification, developing environmental testing requirements, hardware design, and hardware design development); (4) ARTS II software development laboratory unit (procurement of lab style hardware, configured lab style hardware, and designed interface module equivalent to ARTS II faceplate); (5) program support documentation (developed software development plan, configuration management plan, and software verification and validation plan); (6) LWR algorithm analysis (performed timing and profiling on algorithm); (7) pre-trained neural network analysis; (8) Dynamic Cell Structures (DCS) Neural Network Analysis (performing timing and profiling on algorithm); and (9) conducted technical interchange and quarterly meetings to define IFC research goals.

  10. Software control and system configuration management - A process that works

    NASA Technical Reports Server (NTRS)

    Petersen, K. L.; Flores, C., Jr.

    1983-01-01

    A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

  11. Software control and system configuration management: A systems-wide approach

    NASA Technical Reports Server (NTRS)

    Petersen, K. L.; Flores, C., Jr.

    1984-01-01

    A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

  12. Spent Nuclear Fuel Project Configuration Management Plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Reilly, M.A.

    This document is a rewrite of the draft ``C`` that was agreed to ``in principle`` by SNF Project level 2 managers on EDT 609835, dated March 1995 (not released). The implementation process philosphy was changed in keeping with the ongoing reengineering of the WHC Controlled Manuals to achieve configuration management within the SNF Project.

  13. GSC configuration management plan

    NASA Technical Reports Server (NTRS)

    Withers, B. Edward

    1990-01-01

    The tools and methods used for the configuration management of the artifacts (including software and documentation) associated with the Guidance and Control Software (GCS) project are described. The GCS project is part of a software error studies research program. Three implementations of GCS are being produced in order to study the fundamental characteristics of the software failure process. The Code Management System (CMS) is used to track and retrieve versions of the documentation and software. Application of the CMS for this project is described and the numbering scheme is delineated for the versions of the project artifacts.

  14. Configuration management plan. System definition and project development. Repository Based Software Engineering (RBSE) program

    NASA Technical Reports Server (NTRS)

    Mckay, Charles

    1991-01-01

    This is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.

  15. Waste receiving and processing plant control system; system design description

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    LANE, M.P.

    1999-02-24

    The Plant Control System (PCS) is a heterogeneous computer system composed of numerous sub-systems. The PCS represents every major computer system that is used to support operation of the Waste Receiving and Processing (WRAP) facility. This document, the System Design Description (PCS SDD), includes several chapters and appendices. Each chapter is devoted to a separate PCS sub-system. Typically, each chapter includes an overview description of the system, a list of associated documents related to operation of that system, and a detailed description of relevant system features. Each appendice provides configuration information for selected PCS sub-systems. The appendices are designed asmore » separate sections to assist in maintaining this document due to frequent changes in system configurations. This document is intended to serve as the primary reference for configuration of PCS computer systems. The use of this document is further described in the WRAP System Configuration Management Plan, WMH-350, Section 4.1.« less

  16. Positive train control interoperability and networking research : final report.

    DOT National Transportation Integrated Search

    2015-12-01

    This document describes the initial development of an ITC PTC Shared Network (IPSN), a hosted : environment to support the distribution, configuration management, and IT governance of Interoperable : Train Control (ITC) Positive Train Control (PTC) s...

  17. Managing computer-controlled operations

    NASA Technical Reports Server (NTRS)

    Plowden, J. B.

    1985-01-01

    A detailed discussion of Launch Processing System Ground Software Production is presented to establish the interrelationships of firing room resource utilization, configuration control, system build operations, and Shuttle data bank management. The production of a test configuration identifier is traced from requirement generation to program development. The challenge of the operational era is to implement fully automated utilities to interface with a resident system build requirements document to eliminate all manual intervention in the system build operations. Automatic update/processing of Shuttle data tapes will enhance operations during multi-flow processing.

  18. Guidance and Control Software Project Data - Volume 1: Planning Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

  19. TWRS configuration management requirement source document

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    The TWRS Configuration Management (CM) Requirement Source document prescribes CM as a basic product life-cycle function by which work and activities are conducted or accomplished. This document serves as the requirements basis for the TWRS CM program. The objective of the TWRS CM program is to establish consistency among requirements, physical/functional configuration, information, and documentation for TWRS and TWRS products, and to maintain this consistency throughout the life-cycle of TWRS and the product, particularly as changes are being made.

  20. Software Manages Documentation in a Large Test Facility

    NASA Technical Reports Server (NTRS)

    Gurneck, Joseph M.

    2001-01-01

    The 3MCS computer program assists and instrumentation engineer in performing the 3 essential functions of design, documentation, and configuration management of measurement and control systems in a large test facility. Services provided by 3MCS are acceptance of input from multiple engineers and technicians working at multiple locations;standardization of drawings;automated cross-referencing; identification of errors;listing of components and resources; downloading of test settings; and provision of information to customers.

  1. Configuration Management (CM) Support for KM Processes at NASA/Johnson Space Center (JSC)

    NASA Technical Reports Server (NTRS)

    Cioletti, Louis

    2010-01-01

    Collection and processing of information are critical aspects of every business activity from raw data to information to an executable decision. Configuration Management (CM) supports KM practices through its automated business practices and its integrated operations within the organization. This presentation delivers an overview of JSC/Space Life Sciences Directorate (SLSD) and its methods to encourage innovation through collaboration and participation. Specifically, this presentation will illustrate how SLSD CM creates an embedded KM activity with an established IT platform to control and update baselines, requirements, documents, schedules, budgets, while tracking changes essentially managing critical knowledge elements.

  2. Design and Data Management System

    NASA Technical Reports Server (NTRS)

    Messer, Elizabeth; Messer, Brad; Carter, Judy; Singletary, Todd; Albasini, Colby; Smith, Tammy

    2007-01-01

    The Design and Data Management System (DDMS) was developed to automate the NASA Engineering Order (EO) and Engineering Change Request (ECR) processes at the Propulsion Test Facilities at Stennis Space Center for efficient and effective Configuration Management (CM). Prior to the development of DDMS, the CM system was a manual, paper-based system that required an EO or ECR submitter to walk the changes through the acceptance process to obtain necessary approval signatures. This approval process could take up to two weeks, and was subject to a variety of human errors. The process also requires that the CM office make copies and distribute them to the Configuration Control Board members for review prior to meetings. At any point, there was a potential for an error or loss of the change records, meaning the configuration of record was not accurate. The new Web-based DDMS eliminates unnecessary copies, reduces the time needed to distribute the paperwork, reduces time to gain the necessary signatures, and prevents the variety of errors inherent in the previous manual system. After implementation of the DDMS, all EOs and ECRs can be automatically checked prior to submittal to ensure that the documentation is complete and accurate. Much of the configuration information can be documented in the DDMS through pull-down forms to ensure consistent entries by the engineers and technicians in the field. The software also can electronically route the documents through the signature process to obtain the necessary approvals needed for work authorization. The workflow of the system allows for backups and timestamps that determine the correct routing and completion of all required authorizations in a more timely manner, as well as assuring the quality and accuracy of the configuration documents.

  3. Systems engineering implementation in the preliminary design phase of the Giant Magellan Telescope

    NASA Astrophysics Data System (ADS)

    Maiten, J.; Johns, M.; Trancho, G.; Sawyer, D.; Mady, P.

    2012-09-01

    Like many telescope projects today, the 24.5-meter Giant Magellan Telescope (GMT) is truly a complex system. The primary and secondary mirrors of the GMT are segmented and actuated to support two operating modes: natural seeing and adaptive optics. GMT is a general-purpose telescope supporting multiple science instruments operated in those modes. GMT is a large, diverse collaboration and development includes geographically distributed teams. The need to implement good systems engineering processes for managing the development of systems like GMT becomes imperative. The management of the requirements flow down from the science requirements to the component level requirements is an inherently difficult task in itself. The interfaces must also be negotiated so that the interactions between subsystems and assemblies are well defined and controlled. This paper will provide an overview of the systems engineering processes and tools implemented for the GMT project during the preliminary design phase. This will include requirements management, documentation and configuration control, interface development and technical risk management. Because of the complexity of the GMT system and the distributed team, using web-accessible tools for collaboration is vital. To accomplish this GMTO has selected three tools: Cognition Cockpit, Xerox Docushare, and Solidworks Enterprise Product Data Management (EPDM). Key to this is the use of Cockpit for managing and documenting the product tree, architecture, error budget, requirements, interfaces, and risks. Additionally, drawing management is accomplished using an EPDM vault. Docushare, a documentation and configuration management tool is used to manage workflow of documents and drawings for the GMT project. These tools electronically facilitate collaboration in real time, enabling the GMT team to track, trace and report on key project metrics and design parameters.

  4. Space Transportation System Cargo projects: inertial stage/spacecraft integration plan. Volume 1: Management plan

    NASA Technical Reports Server (NTRS)

    1981-01-01

    The Kennedy Space Center (KSC) Management System for the Inertial Upper Stage (IUS) - spacecraft processing from KSC arrival through launch is described. The roles and responsibilities of the agencies and test team organizations involved in IUS-S/C processing at KSC for non-Department of Defense missions are described. Working relationships are defined with respect to documentation preparation, coordination and approval, schedule development and maintenance, test conduct and control, configuration management, quality control and safety. The policy regarding the use of spacecraft contractor test procedures, IUS contractor detailed operating procedures and KSC operations and maintenance instructions is defined. Review and approval requirements for each documentation system are described.

  5. SAGA: A project to automate the management of software production systems

    NASA Technical Reports Server (NTRS)

    Campbell, Roy H.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.

    1987-01-01

    The Software Automation, Generation and Administration (SAGA) project is investigating the design and construction of practical software engineering environments for developing and maintaining aerospace systems and applications software. The research includes the practical organization of the software lifecycle, configuration management, software requirements specifications, executable specifications, design methodologies, programming, verification, validation and testing, version control, maintenance, the reuse of software, software libraries, documentation, and automated management.

  6. Hanford tanks initiative (HTI) configuration management desk instruction

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Schaus, P.S., Fluor Daniel Hanford

    The purpose of the document is to provide working level directions for submitting requirements, making changes to the requirements database, and entering Project documentation into the HTI Project information and document management system.

  7. Configuration Management Plan for K Basins

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Weir, W.R.; Laney, T.

    This plan describes a configuration management program for K Basins that establishes the systems, processes, and responsibilities necessary for implementation. The K Basins configuration management plan provides the methodology to establish, upgrade, reconstitute, and maintain the technical consistency among the requirements, physical configuration, and documentation. The technical consistency afforded by this plan ensures accurate technical information necessary to achieve the mission objectives that provide for the safe, economic, and environmentally sound management of K Basins and the stored material. The configuration management program architecture presented in this plan is based on the functional model established in the DOE Standard, DOE-STD-1073-93,more » {open_quotes}Guide for Operational Configuration Management Program{close_quotes}.« less

  8. Product Structure, the Heart of Product Definition

    NASA Technical Reports Server (NTRS)

    DeHoog, C., Jr.

    1999-01-01

    This paper describes the LMMSS Product Definition System (PDS) philosophy and approach were the use of each item parts document or software can be traced to a specific end item (EI) serial/tail number of the product. It explains why a part-oriented approach to data organization and configuration management is required. The definition of part-oriented is that all appropriate product definition data products will be collected. Referenced and managed by their linkage/relationship to parts/items, The paper will touch upon how LMMSS store/controls product definition information under each project's top product designator in a two tiered approach. One tier for each product end item and another tier which contain/controls listings of drawings, documents. Specifications and standards that are required for hardware item definition.

  9. Making automated computer program documentation a feature of total system design

    NASA Technical Reports Server (NTRS)

    Wolf, A. W.

    1970-01-01

    It is pointed out that in large-scale computer software systems, program documents are too often fraught with errors, out of date, poorly written, and sometimes nonexistent in whole or in part. The means are described by which many of these typical system documentation problems were overcome in a large and dynamic software project. A systems approach was employed which encompassed such items as: (1) configuration management; (2) standards and conventions; (3) collection of program information into central data banks; (4) interaction among executive, compiler, central data banks, and configuration management; and (5) automatic documentation. A complete description of the overall system is given.

  10. Space station automation of common module power management and distribution, volume 2

    NASA Technical Reports Server (NTRS)

    Ashworth, B.; Riedesel, J.; Myers, C.; Jakstas, L.; Smith, D.

    1990-01-01

    The new Space Station Module Power Management and Distribution System (SSM/PMAD) testbed automation system is described. The subjects discussed include testbed 120 volt dc star bus configuration and operation, SSM/PMAD automation system architecture, fault recovery and management expert system (FRAMES) rules english representation, the SSM/PMAD user interface, and the SSM/PMAD future direction. Several appendices are presented and include the following: SSM/PMAD interface user manual version 1.0, SSM/PMAD lowest level processor (LLP) reference, SSM/PMAD technical reference version 1.0, SSM/PMAD LLP visual control logic representation's (VCLR's), SSM/PMAD LLP/FRAMES interface control document (ICD) , and SSM/PMAD LLP switchgear interface controller (SIC) ICD.

  11. Use of software engineering techniques in the design of the ALEPH data acquisition system

    NASA Astrophysics Data System (ADS)

    Charity, T.; McClatchey, R.; Harvey, J.

    1987-08-01

    The SASD methodology is being used to provide a rigorous design framework for various components of the ALEPH data acquisition system. The Entity-Relationship data model is used to describe the layout and configuration of the control and acquisition systems and detector components. State Transition Diagrams are used to specify control applications such as run control and resource management and Data Flow Diagrams assist in decomposing software tasks and defining interfaces between processes. These techniques encourage rigorous software design leading to enhanced functionality and reliability. Improved documentation and communication ensures continuity over the system life-cycle and simplifies project management.

  12. Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

    NASA Technical Reports Server (NTRS)

    Odegard, Ryan G.; Siliwinski, Tomasz K.; King, Ellis T.; Hart, Jeremy J.

    2010-01-01

    The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

  13. Space Geodesy Project Information and Configuration Management Procedure

    NASA Technical Reports Server (NTRS)

    Merkowitz, Stephen M.

    2016-01-01

    This plan defines the Space Geodesy Project (SGP) policies, procedures, and requirements for Information and Configuration Management (CM). This procedure describes a process that is intended to ensure that all proposed and approved technical and programmatic baselines and changes to the SGP hardware, software, support systems, and equipment are documented.

  14. Controlling changes - lessons learned from waste management facilities

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Johnson, B.M.; Koplow, A.S.; Stoll, F.E.

    This paper discusses lessons learned about change control at the Waste Reduction Operations Complex (WROC) and Waste Experimental Reduction Facility (WERF) of the Idaho National Engineering Laboratory (INEL). WROC and WERF have developed and implemented change control and an as-built drawing process and have identified structures, systems, and components (SSCS) for configuration management. The operations have also formed an Independent Review Committee to minimize costs and resources associated with changing documents. WROC and WERF perform waste management activities at the INEL. WROC activities include storage, treatment, and disposal of hazardous and mixed waste. WERF provides volume reduction of solid low-levelmore » waste through compaction, incineration, and sizing operations. WROC and WERF`s efforts aim to improve change control processes that have worked inefficiently in the past.« less

  15. Tank waste remediation system privatization infrastructure program, configuration management implementation plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Schaus, P.S.

    This Configuration Management Implementation Plan (CMIP) was developed to assist in managing systems, structures, and components (SSCS), to facilitate the effective control and statusing of changes to SSCS, and to ensure technical consistency between design, performance, and operational requirements. Its purpose is to describe the approach Privatization Infrastructure will take in implementing a configuration management program, to identify the Program`s products that need configuration management control, to determine the rigor of control, and to identify the mechanisms for that control.

  16. TWRS Configuration management program plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    The TWRS Configuration Management Program Plan (CMPP) integrates technical and administrative controls to establish and maintain consistency among requirements, product configuration, and product information for TWRS products during all life cycle phases. This CMPP will be used by TWRS management and configuration management personnel to establish and manage the technical and integrated baselines and controls and status changes to those baselines.

  17. Current Practices in Runway Configuration Management (RCM) and Arrival/Departure Runway Balancing (ADRB)

    NASA Technical Reports Server (NTRS)

    Lohr, Gary W.; Williams, Daniel M.

    2008-01-01

    Significant air traffic increases are anticipated for the future of the National Airspace System (NAS). To cope with future traffic increases, fundamental changes are required in many aspects of the air traffic management process including the planning and use of NAS resources. Two critical elements of this process are the selection of airport runway configurations, and the effective management of active runways. Two specific research areas in NASA's Airspace Systems Program (ASP) have been identified to address efficient runway management: Runway Configuration Management (RCM) and Arrival/Departure Runway Balancing (ADRB). This report documents efforts in assessing past as well as current work in these two areas.

  18. SSME Advanced Health Management: Project Overview

    NASA Technical Reports Server (NTRS)

    Plowden, John

    2000-01-01

    This document is the viewgraphs from a presentation concerning the development of the Health Management system for the Space Shuttle Main Engine (SSME). It reviews the historical background of the SSME Advanced Health Management effort through the present final Health management configuration. The document includes reviews of three subsystems to the Advanced Health Management System: (1) the Real-Time Vibration Monitor System, (2) the Linear Engine Model, and (3) the Optical Plume Anomaly Detection system.

  19. Tank waste remediation system immobilized high-level waste storage project configuration management implementation plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Burgard, K.G.

    This Configuration Management Implementation Plan was developed to assist in the management of systems, structures, and components, to facilitate the effective control and statusing of changes to systems, structures, and components; and to ensure technical consistency between design, performance, and operational requirements. Its purpose is to describe the approach Project W-464 will take in implementing a configuration management control, to determine the rigor of control, and to identify the mechanisms for imposing that control.This Configuration Management Implementation Plan was developed to assist in the management of systems, structures, and components, to facilitate the effective control and statusing of changes tomore » systems, structures, and components; and to ensure technical consistency between design, performance, and operational requirements. Its purpose is to describe the approach Project W-464 will take in implementing a configuration management control, to determine the rigor of control, and to identify the mechanisms for imposing that control.« less

  20. Detailed requirements document for Stowage List and Hardware Tracking System (SLAHTS). [computer based information management system in support of space shuttle orbiter stowage configuration

    NASA Technical Reports Server (NTRS)

    Keltner, D. J.

    1975-01-01

    The stowage list and hardware tracking system, a computer based information management system, used in support of the space shuttle orbiter stowage configuration and the Johnson Space Center hardware tracking is described. The input, processing, and output requirements that serve as a baseline for system development are defined.

  1. Guidance and Control Software Project Data - Volume 2: Development Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the development documents from the GCS project. Volume 2 contains three appendices: A. Guidance and Control Software Development Specification; B. Design Description for the Pluto Implementation of the Guidance and Control Software; and C. Source Code for the Pluto Implementation of the Guidance and Control Software

  2. Space Station Freedom (SSF) Data Management System (DMS) performance model data base

    NASA Technical Reports Server (NTRS)

    Stovall, John R.

    1993-01-01

    The purpose of this document was originally to be a working document summarizing Space Station Freedom (SSF) Data Management System (DMS) hardware and software design, configuration, performance and estimated loading data from a myriad of source documents such that the parameters provided could be used to build a dynamic performance model of the DMS. The document is published at this time as a close-out of the DMS performance modeling effort resulting from the Clinton Administration mandated Space Station Redesign. The DMS as documented in this report is no longer a part of the redesigned Space Station. The performance modeling effort was a joint undertaking between the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) Flight Data Systems Division (FDSD) and the NASA Ames Research Center (ARC) Spacecraft Data Systems Research Branch. The scope of this document is limited to the DMS core network through the Man Tended Configuration (MTC) as it existed prior to the 1993 Clinton Administration mandated Space Station Redesign. Data is provided for the Standard Data Processors (SDP's), Multiplexer/Demultiplexers (MDM's) and Mass Storage Units (MSU's). Planned future releases would have added the additional hardware and software descriptions needed to describe the complete DMS. Performance and loading data through the Permanent Manned Configuration (PMC) was to have been included as it became available. No future releases of this document are presently planned pending completion of the present Space Station Redesign activities and task reassessment.

  3. Statistical evaluation of PACSTAT random number generation capabilities

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Piepel, G.F.; Toland, M.R.; Harty, H.

    1988-05-01

    This report summarizes the work performed in verifying the general purpose Monte Carlo driver-program PACSTAT. The main objective of the work was to verify the performance of PACSTAT's random number generation capabilities. Secondary objectives were to document (using controlled configuration management procedures) changes made in PACSTAT at Pacific Northwest Laboratory, and to assure that PACSTAT input and output files satisfy quality assurance traceability constraints. Upon receipt of the PRIME version of the PACSTAT code from the Basalt Waste Isolation Project, Pacific Northwest Laboratory staff converted the code to run on Digital Equipment Corporation (DEC) VAXs. The modifications to PACSTAT weremore » implemented using the WITNESS configuration management system, with the modifications themselves intended to make the code as portable as possible. Certain modifications were made to make the PACSTAT input and output files conform to quality assurance traceability constraints. 10 refs., 17 figs., 6 tabs.« less

  4. Computer software configuration description, 241-AY and 241-AZ tank farm MICON automation system

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Winkelman, W.D.

    This document describes the configuration process, choices and conventions used during the configuration activities, and issues involved in making changes to the configuration. Includes the master listings of the Tag definitions, which should be revised to authorize any changes. Revision 2 incorporates minor changes to ensure the document setpoints accurately reflect limits (including exhaust stack flow of 800 scfm) established in OSD-T-151-00019. The MICON DCS software controls and monitors the instrumentation and equipment associated with plant systems and processes.

  5. SSE software test management STM capability: Using STM in the Ground Systems Development Environment (GSDE)

    NASA Technical Reports Server (NTRS)

    Church, Victor E.; Long, D.; Hartenstein, Ray; Perez-Davila, Alfredo

    1992-01-01

    This report is one of a series discussing configuration management (CM) topics for Space Station ground systems software development. It provides a description of the Software Support Environment (SSE)-developed Software Test Management (STM) capability, and discusses the possible use of this capability for management of developed software during testing performed on target platforms. This is intended to supplement the formal documentation of STM provided by the SEE Project. How STM can be used to integrate contractor CM and formal CM for software before delivery to operations is described. STM provides a level of control that is flexible enough to support integration and debugging, but sufficiently rigorous to insure the integrity of the testing process.

  6. System-Oriented Runway Management Concept of Operations

    NASA Technical Reports Server (NTRS)

    Lohr, Gary W.; Atkins, Stephen

    2015-01-01

    This document describes a concept for runway management that maximizes the overall efficiency of arrival and departure operations at an airport or group of airports. Specifically, by planning airport runway configurations/usage, it focuses on the efficiency with which arrival flights reach their parking gates from their arrival fixes and departure flights exit the terminal airspace from their parking gates. In the future, the concept could be expanded to include the management of other limited airport resources. While most easily described in the context of a single airport, the concept applies equally well to a group of airports that comprise a metroplex (i.e., airports in close proximity that share resources such that operations at the airports are at least partially dependent) by including the coordination of runway usage decisions between the airports. In fact, the potential benefit of the concept is expected to be larger in future metroplex environments due to the increasing need to coordinate the operations at proximate airports to more efficiently share limited airspace resources. This concept, called System-Oriented Runway Management (SORM), is further broken down into a set of airport traffic management functions that share the principle that operational performance must be measured over the complete surface and airborne trajectories of the airport's arrivals and departures. The "system-oriented" term derives from the belief that the traffic management objective must consider the efficiency of operations over a wide range of aircraft movements and National Airspace System (NAS) dynamics. The SORM concept is comprised of three primary elements: strategic airport capacity planning, airport configuration management, and combined arrival/departure runway planning. Some aspects of the SORM concept, such as using airport configuration management1 as a mechanism for improving aircraft efficiency, are novel. Other elements (e.g., runway scheduling, which is a part of combined arrival/departure runway scheduling) have been well studied, but are included in the concept for completeness and to allow the concept to define the necessary relationship among the elements. The goal of this document is to describe the overall SORM concept and how it would apply both within the NAS and potential future Next Generation Air Traffic System (NextGen) environments, including research conducted to date. Note that the concept is based on the belief that runways are the primary constraint and the decision point for controlling efficiency, but the efficiency of runway management must be measured over a wide range of space and time. Implementation of the SORM concept is envisioned through a collection of complementary, necessary capabilities collectively focused on ensuring efficient arrival and departure traffic management, where that efficiency is measured not only in terms of runway efficiency but in terms of the overall trajectories between parking gates and transition fixes. For the more original elements of the concept-airport configuration management-this document proposes specific air traffic management (ATM) decision-support automation for realizing the concept.

  7. Guidance and Control Software Project Data - Volume 3: Verification Documents

    NASA Technical Reports Server (NTRS)

    Hayhurst, Kelly J. (Editor)

    2008-01-01

    The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.

  8. Issues and Techniques of CASE Integration With Configuration Management

    DTIC Science & Technology

    1992-03-01

    all four!) process architecture classes. For example, Frame Technology’s FrameMaker is a client/server tool because it provides server functions for... FrameMaker clients; it is a parent/child tool since a top-level control panel is used to "fork" child FrameMaker sessions; the "forked" FrameMaker ...sessions are persistent tools since they may be reused to create and modify any number of FrameMaker documents. Despite this, however, these process

  9. Survey of piloting factors in V/STOL aircraft with implications for flight control system design

    NASA Technical Reports Server (NTRS)

    Ringland, R. F.; Craig, S. J.

    1977-01-01

    Flight control system design factors involved for pilot workload relief are identified. Major contributors to pilot workload include configuration management and control and aircraft stability and response qualities. A digital fly by wire stability augmentation, configuration management, and configuration control system is suggested for reduction of pilot workload during takeoff, hovering, and approach.

  10. Design document for the MOODS Data Management System (MDMS), version 1.0

    NASA Technical Reports Server (NTRS)

    1994-01-01

    The MOODS Data Management System (MDMS) provides access to the Master Oceanographic Observation Data Set (MOODS) which is maintained by the Naval Oceanographic Office (NAVOCEANO). The MDMS incorporates database technology in providing seamless access to parameter (temperature, salinity, soundspeed) vs. depth observational profile data. The MDMS is an interactive software application with a graphical user interface (GUI) that supports user control of MDMS functional capabilities. The purpose of this document is to define and describe the structural framework and logical design of the software components/units which are integrated into the major computer software configuration item (CSCI) identified as MDMS, Version 1.0. The preliminary design is based on functional specifications and requirements identified in the governing Statement of Work prepared by the Naval Oceanographic Office (NAVOCEANO) and distributed as a request for proposal by the National Aeronautics and Space Administration (NASA).

  11. Design document for the Surface Currents Data Base (SCDB) Management System (SCDBMS), version 1.0

    NASA Technical Reports Server (NTRS)

    Krisnnamagaru, Ramesh; Cesario, Cheryl; Foster, M. S.; Das, Vishnumohan

    1994-01-01

    The Surface Currents Database Management System (SCDBMS) provides access to the Surface Currents Data Base (SCDB) which is maintained by the Naval Oceanographic Office (NAVOCEANO). The SCDBMS incorporates database technology in providing seamless access to surface current data. The SCDBMS is an interactive software application with a graphical user interface (GUI) that supports user control of SCDBMS functional capabilities. The purpose of this document is to define and describe the structural framework and logistical design of the software components/units which are integrated into the major computer software configuration item (CSCI) identified as the SCDBMS, Version 1.0. The preliminary design is based on functional specifications and requirements identified in the governing Statement of Work prepared by the Naval Oceanographic Office (NAVOCEANO) and distributed as a request for proposal by the National Aeronautics and Space Administration (NASA).

  12. Software Configuration Management Plan for the B-Plant Canyon Ventilation Control System

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    MCDANIEL, K.S.

    1999-08-31

    Project W-059 installed a new B Plant Canyon Ventilation System. Monitoring and control of the system is implemented by the Canyon Ventilation Control System (CVCS). This Software Configuration Management Plan provides instructions for change control of the CVCS.

  13. Unified Desktop for Monitoring & Control Applications - The Open Navigator Framework Applied for Control Centre and EGSE Applications

    NASA Astrophysics Data System (ADS)

    Brauer, U.

    2007-08-01

    The Open Navigator Framework (ONF) was developed to provide a unified and scalable platform for user interface integration. The main objective for the framework was to raise usability of monitoring and control consoles and to provide a reuse of software components in different application areas. ONF is currently applied for the Columbus onboard crew interface, the commanding application for the Columbus Control Centre, the Columbus user facilities specialized user interfaces, the Mission Execution Crew Assistant (MECA) study and EADS Astrium internal R&D projects. ONF provides a well documented and proven middleware for GUI components (Java plugin interface, simplified concept similar to Eclipse). The overall application configuration is performed within a graphical user interface for layout and component selection. The end-user does not have to work in the underlying XML configuration files. ONF was optimized to provide harmonized user interfaces for monitoring and command consoles. It provides many convenience functions designed together with flight controllers and onboard crew: user defined workspaces, incl. support for multi screens efficient communication mechanism between the components integrated web browsing and documentation search &viewing consistent and integrated menus and shortcuts common logging and application configuration (properties) supervision interface for remote plugin GUI access (web based) A large number of operationally proven ONF components have been developed: Command Stack & History: Release of commands and follow up the command acknowledges System Message Panel: Browse, filter and search system messages/events Unified Synoptic System: Generic synoptic display system Situational Awareness : Show overall subsystem status based on monitoring of key parameters System Model Browser: Browse mission database defintions (measurements, commands, events) Flight Procedure Executor: Execute checklist and logical flow interactive procedures Web Browser : Integrated browser reference documentation and operations data Timeline Viewer: View master timeline as Gantt chart Search: Local search of operations products (e.g. documentation, procedures, displays) All GUI components access the underlying spacecraft data (commanding, reporting data, events, command history) via a common library providing adaptors for the current deployments (Columbus MCS, Columbus onboard Data Management System, Columbus Trainer raw packet protocol). New Adaptors are easy to develop. Currently an adaptor to SCOS 2000 is developed as part of a study for the ESTEC standardization section ("USS for ESTEC Reference Facility").

  14. Intelligent Hybrid Vehicle Power Control. Part 2. Online Intelligent Energy Management

    DTIC Science & Technology

    2012-06-30

    IEC_HEV for vehicle energy optimization. IEC_HEV, the Figure 1. Power Split HEV configuration into VSC 5 online energy control is a component...in the Vehicle System Controller ( VSC ). The VSC for this configuration must manage the powertrain control in order to maintain a proper level of...charge in the battery. However, since two power sources are available to propel the vehicle, the VSC in this configuration has the additional

  15. Control of a human-powered helicopter in hover

    NASA Technical Reports Server (NTRS)

    Totah, Joseph J.; Patterson, William

    1988-01-01

    The study of a control system for the Da Vinci 2 human-powered helicopter in hovering flight is documented. This helicopter has two very large, slowly rotating rotor blades and is considered to be unstable in hover. The control system is designed to introduce stability in hover by maintaining level rotors through the use of rotor tip mounted control surfaces. A five degree of freedom kinematic model was developed to study this control system and is documented. Results of this study show that the unaugmented configuration is unstable due to the large Lock Number, and the augmented configuration is stable. The role of NASA in this study included the development and analysis of the kinematic model and control laws. Both analytical and numerical techniques were used.

  16. The Large Synoptic Survey Telescope project management control system

    NASA Astrophysics Data System (ADS)

    Kantor, Jeffrey P.

    2012-09-01

    The Large Synoptic Survey Telescope (LSST) program is jointly funded by the NSF, the DOE, and private institutions and donors. From an NSF funding standpoint, the LSST is a Major Research Equipment and Facilities (MREFC) project. The NSF funding process requires proposals and D&D reviews to include activity-based budgets and schedules; documented basis of estimates; risk-based contingency analysis; cost escalation and categorization. "Out-of-the box," the commercial tool Primavera P6 contains approximately 90% of the planning and estimating capability needed to satisfy R&D phase requirements, and it is customizable/configurable for remainder with relatively little effort. We describe the customization/configuration and use of Primavera for the LSST Project Management Control System (PMCS), assess our experience to date, and describe future directions. Examples in this paper are drawn from the LSST Data Management System (DMS), which is one of three main subsystems of the LSST and is funded by the NSF. By astronomy standards the LSST DMS is a large data management project, processing and archiving over 70 petabyes of image data, producing over 20 petabytes of catalogs annually, and generating 2 million transient alerts per night. Over the 6-year construction and commissioning phase, the DM project is estimated to require 600,000 hours of engineering effort. In total, the DMS cost is approximately 60% hardware/system software and 40% labor.

  17. Quality assurance planning for lunar Mars exploration

    NASA Technical Reports Server (NTRS)

    Myers, Kay

    1991-01-01

    A review is presented of the tools and techniques required to meet the challenge of total quality in the goal of traveling to Mars and returning to the moon. One program used by NASA to ensure the integrity of baselined requirements documents is configuration management (CM). CM is defined as an integrated management process that documents and identifies the functional and physical characteristics of a facility's systems, structures, computer software, and components. It also ensures that changes to these characteristics are properly assessed, developed, approved, implemented, verified, recorded, and incorporated into the facility's documentation. Three principal areas are discussed that will realize significant efficiencies and enhanced effectiveness, change assessment, change avoidance, and requirements management.

  18. Site systems engineering fiscal year 1999 multi-year work plan (MYWP) update for WBS 1.8.2.2

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    GRYGIEL, M.L.

    1998-10-08

    Manage the Site Systems Engineering process to provide a traceable integrated requirements-driven, and technically defensible baseline. Through the Site Integration Group(SIG), Systems Engineering ensures integration of technical activities across all site projects. Systems Engineering's primary interfaces are with the RL Project Managers, the Project Direction Office and with the Project Major Subcontractors, as well as with the Site Planning organization. Systems Implementation: (1) Develops, maintains, and controls the site integrated technical baseline, ensures the Systems Engineering interfaces between projects are documented, and maintain the Site Environmental Management Specification. (2) Develops and uses dynamic simulation models for verification of the baselinemore » and analysis of alternatives. (3) Performs and documents fictional and requirements analyses. (4) Works with projects, technology management, and the SIG to identify and resolve technical issues. (5) Supports technical baseline information for the planning and budgeting of the Accelerated Cleanup Plan, Multi-Year Work Plans, Project Baseline Summaries as well as performance measure reporting. (6) Works with projects to ensure the quality of data in the technical baseline. (7) Develops, maintains and implements the site configuration management system.« less

  19. Attaining and maintaining data integrity with configuration management

    NASA Astrophysics Data System (ADS)

    Huffman, Dorothy J.; Jeane, Shirley A.

    1993-08-01

    Managers and scientists are concerned about data integrity because they draw conclusions from data that can have far reaching effects. Projects managers use Configuration Management to insure that hardware, software, and project information are controlled. They have not, as yet, applied its rigorously to data. However, there is ample opportunity in the data collection and production process to jeopardize data integrity. Environmental changes, tampering and production problems can all affect data integrity. There are four functions included in the Configuration Management process: configuration identification, control, auditing and status accounting. These functions provide management the means to attain data integrity and the visibility into engineering processes needed to maintain data integrity. When project managers apply Configuration Management processes to data, the data user can trace back through history to validate data integrity. The user knows that the project allowed only orderly changes to the data. He is assured that project personnel followed procedures to maintain data quality. He also has access to status information about the data. The user receives data products with a known integrity level and a means to assess the impact of past events ont he conclusions derived from the data. To obtain these benefits, project managers should apply the Configuration Management discipline to data.

  20. 77 FR 67820 - Privacy Act of 1974; Report of a New System of Records; Food and Drug Administration User Fee System

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-11-14

    ..., timely account disablement/deletion, configuration management, maintenance, system and information... paper or CD-ROM submissions): Division of Dockets Management (HFA-305), Food and Drug Administration... document, into the ``Search'' box and follow the prompts and/or go to the Division of Dockets Management...

  1. AZ-101 Mixer Pump Demonstration Data Acquisition System and Gamma Cart Data Acquisition Control System Software Configuration Management Plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    WHITE, D.A.

    1999-12-29

    This Software Configuration Management Plan (SCMP) provides the instructions for change control of the AZ1101 Mixer Pump Demonstration Data Acquisition System (DAS) and the Sludge Mobilization Cart (Gamma Cart) Data Acquisition and Control System (DACS).

  2. PIMS-Universal Payload Information Management

    NASA Technical Reports Server (NTRS)

    Elmore, Ralph; McNair, Ann R. (Technical Monitor)

    2002-01-01

    As the overall manager and integrator of International Space Station (ISS) science payloads and experiments, the Payload Operations Integration Center (POIC) at Marshall Space Flight Center had a critical need to provide an information management system for exchange and management of ISS payload files as well as to coordinate ISS payload related operational changes. The POIC's information management system has a fundamental requirement to provide secure operational access not only to users physically located at the POIC, but also to provide collaborative access to remote experimenters and International Partners. The Payload Information Management System (PIMS) is a ground based electronic document configuration management and workflow system that was built to service that need. Functionally, PIMS provides the following document management related capabilities: 1. File access control, storage and retrieval from a central repository vault. 2. Collect supplemental data about files in the vault. 3. File exchange with a PMS GUI client, or any FTP connection. 4. Files placement into an FTP accessible dropbox for pickup by interfacing facilities, included files transmitted for spacecraft uplink. 5. Transmission of email messages to users notifying them of new version availability. 6. Polling of intermediate facility dropboxes for files that will automatically be processed by PIMS. 7. Provide an API that allows other POIC applications to access PIMS information. Functionally, PIMS provides the following Change Request processing capabilities: 1. Ability to create, view, manipulate, and query information about Operations Change Requests (OCRs). 2. Provides an adaptable workflow approval of OCRs with routing through developers, facility leads, POIC leads, reviewers, and implementers. Email messages can be sent to users either involving them in the workflow process or simply notifying them of OCR approval progress. All PIMS document management and OCR workflow controls are coordinated through and routed to individual user's "to do" list tasks. A user is given a task when it is their turn to perform some action relating to the approval of the Document or OCR. The user's available actions are restricted to only functions available for the assigned task. Certain actions, such as review or action implementation by non-PIMS users, can also be coordinated through automated emails.

  3. Software Description for the O’Hare Runway Configuration Management System. Volume I. Technical Description,

    DTIC Science & Technology

    1982-10-01

    spent in preparing this document. 00. EXECUTIVE SUMMARY The O’Hare Runway Configuration Management System (CMS) is an interactive multi-user computer ...MITRE Washington’s Computer Center. Currently, CMS is housed in an IBM 4341 computer with VM/SP operating system. CMS employs the IBM’s Display...iV 0O, o 0 .r4L /~ wA 0U 00 00 0 w vi O’Hare, it will operate on a dedicated mini- computer which permits multi-tasking (that is, multiple users

  4. CM and DM in an ISO R and D Environment

    NASA Technical Reports Server (NTRS)

    Crowley, Sandra L.

    2000-01-01

    ISO 9000 - a common buzz word in industry is making inroads to government agencies. The National Aeronautics and Space Agency (NASA) achieved ISO 9001 certification at each of its nine (9) Centers and Headquarters in 1998-1999. NASA Glenn Research Center (GRC) was recommended for certification in September 1999. Since then, each of the Centers has been going through the semi-annual surveillance audits. Growing out of the manufacturing industry, successful application of the international quality standard to a research and development (R&D) environment has had its challenges. This paper will address how GRC applied Configuration Management (CM) and Data (or Document) Management (DM) to meet challenges to achieve ISO certification. One of the first challenges was to fit the ISO 9001-1994 elements to the GRC environment. Some of the elements fit well-Management Responsibility (4.1), Internal Audits (4.17), Document and Data Control (4.5). Other elements were not suited or applied easily to the R&D environment-Servicing (4.19), Statistical Techniques (4.20). Since GRC "builds" only one or two items at a time, these elements were considered not applicable to the environment.

  5. The CEBAF Element Database

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Theodore Larrieu, Christopher Slominski, Michele Joyce

    2011-03-01

    With the inauguration of the CEBAF Element Database (CED) in Fall 2010, Jefferson Lab computer scientists have taken a step toward the eventual goal of a model-driven accelerator. Once fully populated, the database will be the primary repository of information used for everything from generating lattice decks to booting control computers to building controls screens. A requirement influencing the CED design is that it provide access to not only present, but also future and past configurations of the accelerator. To accomplish this, an introspective database schema was designed that allows new elements, types, and properties to be defined on-the-fly withmore » no changes to table structure. Used in conjunction with Oracle Workspace Manager, it allows users to query data from any time in the database history with the same tools used to query the present configuration. Users can also check-out workspaces to use as staging areas for upcoming machine configurations. All Access to the CED is through a well-documented Application Programming Interface (API) that is translated automatically from original C++ source code into native libraries for scripting languages such as perl, php, and TCL making access to the CED easy and ubiquitous.« less

  6. Supporting Tablet Configuration, Tracking, and Infection Control Practices in Digital Health Interventions: Study Protocol.

    PubMed

    Furberg, Robert D; Ortiz, Alexa M; Zulkiewicz, Brittany A; Hudson, Jordan P; Taylor, Olivia M; Lewis, Megan A

    2016-06-27

    Tablet-based health care interventions have the potential to encourage patient care in a timelier manner, allow physicians convenient access to patient records, and provide an improved method for patient education. However, along with the continued adoption of tablet technologies, there is a concomitant need to develop protocols focusing on the configuration, management, and maintenance of these devices within the health care setting to support the conduct of clinical research. Develop three protocols to support tablet configuration, tablet management, and tablet maintenance. The Configurator software, Tile technology, and current infection control recommendations were employed to develop three distinct protocols for tablet-based digital health interventions. Configurator is a mobile device management software specifically for iPhone operating system (iOS) devices. The capabilities and current applications of Configurator were reviewed and used to develop the protocol to support device configuration. Tile is a tracking tag associated with a free mobile app available for iOS and Android devices. The features associated with Tile were evaluated and used to develop the Tile protocol to support tablet management. Furthermore, current recommendations on preventing health care-related infections were reviewed to develop the infection control protocol to support tablet maintenance. This article provides three protocols: the Configurator protocol, the Tile protocol, and the infection control protocol. These protocols can help to ensure consistent implementation of tablet-based interventions, enhance fidelity when employing tablets for research purposes, and serve as a guide for tablet deployments within clinical settings.

  7. Managing EEE part standardisation and procurement

    NASA Astrophysics Data System (ADS)

    Serieys, C.; Bensoussan, A.; Petitmangin, A.; Rigaud, M.; Barbaresco, P.; Lyan, C.

    2002-12-01

    This paper presents the development activities in space components selection and procurement dealing with a new data base tool implemented at Alcatel Space using TransForm softwaa re configurator developed by Techform S.A. Based on TransForm, Access Ingenierie has devv eloped a software product named OLG@DOS which facilitate the part nomenclatures analyses for new equipment design and manufacturing in term of ACCESS data base implementation. Hi-Rel EEE part type technical, production and quality information are collected and compiled usingproduction data base issued from production tools implemented for equipment definition, description and production based on Manufacturing Resource Planning (MRP II Control Open) and Parametric Design Manager (PDM Work Manager). The analysis of any new equipment nomenclature may be conducted through this means for standardisation purpose, cost containment program and management procurement activities as well as preparation of Component reviews as Part Approval Document and Declared Part List validation.

  8. Space Shuttle wind tunnel testing program

    NASA Technical Reports Server (NTRS)

    Whitnah, A. M.; Hillje, E. R.

    1984-01-01

    A major phase of the Space Shuttle Vehicle (SSV) Development Program was the acquisition of data through the space shuttle wind tunnel testing program. It became obvious that the large number of configuration/environment combinations would necessitate an extremely large wind tunnel testing program. To make the most efficient use of available test facilities and to assist the prime contractor for orbiter design and space shuttle vehicle integration, a unique management plan was devised for the design and development phase. The space shuttle program is reviewed together with the evolutional development of the shuttle configuration. The wind tunnel testing rationale and the associated test program management plan and its overall results is reviewed. Information is given for the various facilities and models used within this program. A unique posttest documentation procedure and a summary of the types of test per disciplines, per facility, and per model are presented with detailed listing of the posttest documentation.

  9. A network architecture for International Business Satellite communications

    NASA Astrophysics Data System (ADS)

    Takahata, Fumio; Nohara, Mitsuo; Takeuchi, Yoshio

    Demand Assignment (DA) control is expected to be introduced in the International Business Satellte communications (IBS) network in order to cope with a growing international business traffic. The paper discusses the DA/IBS network from the viewpoints of network configuration, satellite channel configuration and DA control. The network configuration proposed here consists of one Central Station with network management function and several Network Coordination Stations with user management function. A satellite channel configuration is also presented along with a tradeoff study on transmission bit rate, high power amplifier output power requirement, and service quality. The DA control flow and protocol based on CCITT Signalling System No. 7 are also proposed.

  10. Guide for Operational Configuration Management Program including the adjunct programs of design reconstitution and material condition and aging management. Part 2

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    This standard presents program criteria and implementation guidance for an operational configuration management program for DOE nuclear and non-nuclear facilities. This Part 2 includes chapters on implementation guidance for operational configuration management, implementation guidance for design reconstitution, and implementation guidance for material condition and aging management. Appendices are included on design control, examples of design information, conduct of walkdowns, and content of design information summaries.

  11. Utilisation d'analyse de concepts formels pour la gestion de variabilite d'un logiciel configure dynamiquement

    NASA Astrophysics Data System (ADS)

    Menguy, Theotime

    Because of its critical nature, avionic industry is bound with numerous constraints such as security standards and certifications while having to fulfill the clients' desires for personalization. In this context, variability management is a very important issue for re-engineering projects of avionic softwares. In this thesis, we propose a new approach, based on formal concept analysis and semantic web, to support variability management. The first goal of this research is to identify characteristic behaviors and interactions of configuration variables in a dynamically configured system. To identify such elements, we used formal concept analysis on different levels of abstractions in the system and defined new metrics. Then, we built a classification for the configuration variables and their relations in order to enable a quick identification of a variable's behavior in the system. This classification could help finding a systematic approach to process variables during a re-engineering operation, depending on their category. To have a better understanding of the system, we also studied the shared controls of code between configuration variables. A second objective of this research is to build a knowledge platform to gather the results of all the analysis performed, and to store any additional element relevant in the variability management context, for instance new results helping define re-engineering process for each of the categories. To address this goal, we built a solution based on a semantic web, defining a new ontology, very extensive and enabling to build inferences related to the evolution processes. The approach presented here is, to the best of our knowledge, the first classification of configuration variables of a dynamically configured software and an original use of documentation and variability management techniques using semantic web in the aeronautic field. The analysis performed and the final results show that formal concept analysis is a way to identify specific properties and behaviors and that semantic web is a good solution to store and explore the results. However, the use of formal concept analysis with new boolean relations, such as the link between configuration variables and files, and the definition of new inferences may be a way to draw better conclusions. The use of the same methodology with other systems would enable to validate the approach in other contexts.

  12. PAN AIR: A computer program for predicting subsonic or supersonic linear potential flows about arbitrary configurations using a higher order panel method. Volume 4: Maintenance document (version 1.1)

    NASA Technical Reports Server (NTRS)

    Baruah, P. K.; Bussoletti, J. E.; Chiang, D. T.; Massena, W. A.; Nelson, F. D.; Furdon, D. J.; Tsurusaki, K.

    1981-01-01

    The Maintenance Document is a guide to the PAN AIR software system, a system which computes the subsonic or supersonic linear potential flow about a body of nearly arbitrary shape, using a higher order panel method. The document describes the over-all system and each program module of the system. Sufficient detail is given for program maintenance, updating and modification. It is assumed that the reader is familiar with programming and CDC (Control Data Corporation) computer systems. The PAN AIR system was written in FORTRAN 4 language except for a few COMPASS language subroutines which exist in the PAN AIR library. Structured programming techniques were used to provide code documentation and maintainability. The operating systems accommodated are NOS 1.2, NOS/BE and SCOPE 2.1.3 on the CDC 6600, 7600 and Cyber 175 computing systems. The system is comprised of a data management system, a program library, an execution control module and nine separate FORTRAN technical modules. Each module calculates part of the posed PAN AIR problem. The data base manager is used to communicate between modules and within modules. The technical modules must be run in a prescribed fashion for each PAN AIR problem. In order to ease the problem of supplying the many JCL cards required to execute the modules, a separate module called MEC (Module Execution Control) was created to automatically supply most of the JCL cards. In addition to the MEC generated JCL, there is an additional set of user supplied JCL cards to initiate the JCL sequence stored on the system.

  13. Experiment/facility requirements document for the Space Station Furnace Facility. Section 1: Integrated configuration

    NASA Astrophysics Data System (ADS)

    1992-05-01

    The function of the Space Station Furnace Facility (SSFF) is to support materials research into the crystal growth and solidification processes of electronic and photonic materials, metals and alloys, and glasses and ceramics. To support this broad base of research requirements, the SSFF will employ a variety of furnace modules which will be operated, regulated, and supported by a core of common subsystems. Furnace modules may be reconfigured or specifically developed to provide unique solidification conditions for each set of experiments. The SSFF modular approach permits the addition of new or scaled-up furnace modules to support the evolution of the facility as new science requirements are identified. The SSFF Core is of modular design to permit augmentation for enhanced capabilities. The fully integrated configuration of the SSFF will consist of three racks with the capability of supporting up to two furnace modules per rack. The initial configuration of the SSFF will consist of two of the three racks and one furnace module. This Experiment/Facility Requirements Document (E/FRD) describes the integrated facility requirements for the Space Station Freedom (SSF) Integrated Configuration-1 (IC1) mission. The IC1 SSFF will consist of two racks: the Core Rack, with the centralized subsystem equipment; and the Experiment Rack-1, with Furnace Module-1 and the distributed subsystem equipment to support the furnace. The SSFF support functions are provided by the following Core subsystems: power conditioning and distribution subsystem (SSFF PCDS); data management subsystem (SSFF DMS); thermal control Subsystem (SSFF TCS); gas distribution subsystem (SSFF GDS); and mechanical structures subsystem (SSFF MSS).

  14. Experiment/facility requirements document for the Space Station Furnace Facility. Section 1: Integrated configuration

    NASA Technical Reports Server (NTRS)

    1992-01-01

    The function of the Space Station Furnace Facility (SSFF) is to support materials research into the crystal growth and solidification processes of electronic and photonic materials, metals and alloys, and glasses and ceramics. To support this broad base of research requirements, the SSFF will employ a variety of furnace modules which will be operated, regulated, and supported by a core of common subsystems. Furnace modules may be reconfigured or specifically developed to provide unique solidification conditions for each set of experiments. The SSFF modular approach permits the addition of new or scaled-up furnace modules to support the evolution of the facility as new science requirements are identified. The SSFF Core is of modular design to permit augmentation for enhanced capabilities. The fully integrated configuration of the SSFF will consist of three racks with the capability of supporting up to two furnace modules per rack. The initial configuration of the SSFF will consist of two of the three racks and one furnace module. This Experiment/Facility Requirements Document (E/FRD) describes the integrated facility requirements for the Space Station Freedom (SSF) Integrated Configuration-1 (IC1) mission. The IC1 SSFF will consist of two racks: the Core Rack, with the centralized subsystem equipment; and the Experiment Rack-1, with Furnace Module-1 and the distributed subsystem equipment to support the furnace. The SSFF support functions are provided by the following Core subsystems: power conditioning and distribution subsystem (SSFF PCDS); data management subsystem (SSFF DMS); thermal control Subsystem (SSFF TCS); gas distribution subsystem (SSFF GDS); and mechanical structures subsystem (SSFF MSS).

  15. Flight evaluation of configuration management system concepts during transition to the landing approach for a powered-lift STOL aircraft

    NASA Technical Reports Server (NTRS)

    Franklin, J. A.; Innis, R. C.

    1980-01-01

    Flight experiments were conducted to evaluate two control concepts for configuration management during the transition to landing approach for a powered-lift STOL aircraft. NASA Ames' augmentor wing research aircraft was used in the program. Transitions from nominal level-flight configurations at terminal area pattern speeds were conducted along straight and curved descending flightpaths. Stabilization and command augmentation for attitude and airspeed control were used in conjunction with a three-cue flight director that presented commands for pitch, roll, and throttle controls. A prototype microwave system provided landing guidance. Results of these flight experiments indicate that these configuration management concepts permit the successful performance of transitions and approaches along curved paths by powered-lift STOL aircraft. Flight director guidance was essential to accomplish the task.

  16. Supporting Tablet Configuration, Tracking, and Infection Control Practices in Digital Health Interventions: Study Protocol

    PubMed Central

    Furberg, Robert D; Zulkiewicz, Brittany A; Hudson, Jordan P; Taylor, Olivia M; Lewis, Megan A

    2016-01-01

    Background Tablet-based health care interventions have the potential to encourage patient care in a timelier manner, allow physicians convenient access to patient records, and provide an improved method for patient education. However, along with the continued adoption of tablet technologies, there is a concomitant need to develop protocols focusing on the configuration, management, and maintenance of these devices within the health care setting to support the conduct of clinical research. Objective Develop three protocols to support tablet configuration, tablet management, and tablet maintenance. Methods The Configurator software, Tile technology, and current infection control recommendations were employed to develop three distinct protocols for tablet-based digital health interventions. Configurator is a mobile device management software specifically for iPhone operating system (iOS) devices. The capabilities and current applications of Configurator were reviewed and used to develop the protocol to support device configuration. Tile is a tracking tag associated with a free mobile app available for iOS and Android devices. The features associated with Tile were evaluated and used to develop the Tile protocol to support tablet management. Furthermore, current recommendations on preventing health care–related infections were reviewed to develop the infection control protocol to support tablet maintenance. Results This article provides three protocols: the Configurator protocol, the Tile protocol, and the infection control protocol. Conclusions These protocols can help to ensure consistent implementation of tablet-based interventions, enhance fidelity when employing tablets for research purposes, and serve as a guide for tablet deployments within clinical settings. PMID:27350013

  17. 78 FR 15056 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-03-08

    ... establish, document, and maintain a system of internal risk management controls. The Rule sets forth the..., documenting, and reviewing its internal risk management control system, which are designed to, among other... documenting its risk management control system is 2,000 hours and that, on average, a registered OTC...

  18. Configuration management program plan for Hanford site systems engineering

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Hoffman, A.G.

    This plan establishes the integrated configuration management program for the evolving technical baseline developed through the systems engineering process. This configuration management program aligns with the criteria identified in the DOE Standard, DOE-STD-1073-93. Included are specific requirements for control of the systems engineering RDD-100 database, and electronic data incorporated in the database that establishes the Hanford site technical baseline.

  19. FLORIDA TOWER FOOTPRINT EXPERIMENTS

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    WATSON,T.B.; DIETZ, R.N.; WILKE, R.

    2007-01-01

    The Florida Footprint experiments were a series of field programs in which perfluorocarbon tracers were released in different configurations centered on a flux tower to generate a data set that can be used to test transport and dispersion models. These models are used to determine the sources of the CO{sub 2} that cause the fluxes measured at eddy covariance towers. Experiments were conducted in a managed slash pine forest, 10 km northeast of Gainesville, Florida, in 2002, 2004, and 2006 and in atmospheric conditions that ranged from well mixed, to very stable, including the transition period between convective conditions atmore » midday to stable conditions after sun set. There were a total of 15 experiments. The characteristics of the PFTs, details of sampling and analysis methods, quality control measures, and analytical statistics including confidence limits are presented. Details of the field programs including tracer release rates, tracer source configurations, and configuration of the samplers are discussed. The result of this experiment is a high quality, well documented tracer and meteorological data set that can be used to improve and validate canopy dispersion models.« less

  20. Microgravity Experiments Safety and Integration Requirements Document Tree

    NASA Technical Reports Server (NTRS)

    Hogan, Jean M.

    1995-01-01

    This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

  1. Integrated Application of Active Controls (IAAC) technology to an advanced subsonic transport project: Wing planform study and final configuration selection

    NASA Technical Reports Server (NTRS)

    1981-01-01

    The Wing Planform Study and Final Configuration Selection Task of the Integrated Application of Active Controls (IAAC) Technology Project within the Energy Efficient Transport Program is documented. Application of Active Controls Technology (ACT) in combination with increased wing span resulted in significant improvements over the Conventional Baseline Configuration (Baseline) and the Initial ACT Configuration previously established. The configurations use the same levels of technology, takeoff gross weight, and payload as the Baseline. The Final ACT Configuration (Model 768-107) incorporates pitch-augmented stability (which enabled an approximately 10% aft shift in cruise center of gravity and a 44% reduction in horizontal tail size), lateral/directional-augmented stability, an angle-of-attack limiter, and wing-load alleviation. Flutter-mode control was not beneficial for this configuration. This resulted in an 890 kg (1960 lb) reduction in airplane takeoff gross weight and a 9.8% improvement in cruise lift/drag. At the Baseline mission range (3589 km 1938 nmi), this amounts to 10% block-fuel reduction. Results of this task strongly indicate that the IAAC Project should proceed with the Final ACT evaluation, and begin the required control system development and test.

  2. ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

    NASA Technical Reports Server (NTRS)

    Wilber, George F.

    2017-01-01

    This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

  3. Independent Orbiter Assessment (IOA): FMEA/CIL assessment

    NASA Technical Reports Server (NTRS)

    Hinsdale, L. W.; Swain, L. J.; Barnes, J. E.

    1988-01-01

    The McDonnell Douglas Astronautics Company (MDAC) was selected to perform an Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL). Direction was given by the Orbiter and GFE Projects Office to perform the hardware analysis and assessment using the instructions and ground rules defined in NSTS 22206. The IOA analysis featured a top-down approach to determine hardware failure modes, criticality, and potential critical items. To preserve independence, the analysis was accomplished without reliance upon the results contained within the NASA and Prime Contractor FMEA/CIL documentation. The assessment process compared the independently derived failure modes and criticality assignments to the proposed NASA post 51-L FMEA/CIL documentation. When possible, assessment issues were discussed and resolved with the NASA subsystem managers. Unresolved issues were elevated to the Orbiter and GFE Projects Office manager, Configuration Control Board (CCB), or Program Requirements Control Board (PRCB) for further resolution. The most important Orbiter assessment finding was the previously unknown stuck autopilot push-button criticality 1/1 failure mode. The worst case effect could cause loss of crew/vehicle when the microwave landing system is not active. It is concluded that NASA and Prime Contractor Post 51-L FMEA/CIL documentation assessed by IOA is believed to be technically accurate and complete. All CIL issues were resolved. No FMEA issues remain that have safety implications. Consideration should be given, however, to upgrading NSTS 22206 with definitive ground rules which more clearly spell out the limits of redundancy.

  4. Alarm rationalization: practical experience rationalizing alarm configuration for an accelerator subsystem

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kasemir, Kay; Hartman, Steven M

    2009-01-01

    A new alarm system toolkit has been implemented at SNS. The toolkit handles the Central Control Room (CCR) 'annunciator', or audio alarms. For the new alarm system to be effective, the alarms must be meaningful and properly configured. Along with the implementation of the new alarm toolkit, a thorough documentation and rationalization of the alarm configuration is taking place. Requirements and maintenance of a robust alarm configuration have been gathered from system and operations experts. In this paper we present our practical experience with the vacuum system alarm handling configuration of the alarm toolkit.

  5. Kennedy Space Center network documentation system

    NASA Technical Reports Server (NTRS)

    Lohne, William E.; Schuerger, Charles L.

    1995-01-01

    The Kennedy Space Center Network Documentation System (KSC NDS) is being designed and implemented by NASA and the KSC contractor organizations to provide a means of network tracking, configuration, and control. Currently, a variety of host and client platforms are in use as a result of each organization having established its own network documentation system. The solution is to incorporate as many existing 'systems' as possible in the effort to consolidate and standardize KSC-wide documentation.

  6. Kepler: A Search for Terrestrial Planets - SOC 9.3 DR25 Pipeline Parameter Configuration Reports

    NASA Technical Reports Server (NTRS)

    Campbell, Jennifer R.

    2017-01-01

    This document describes the manner in which the pipeline and algorithm parameters for the Kepler Science Operations Center (SOC) science data processing pipeline were managed. This document is intended for scientists and software developers who wish to better understand the software design for the final Kepler codebase (SOC 9.3) and the effect of the software parameters on the Data Release (DR) 25 archival products.

  7. GCS plan for software aspects of certification

    NASA Technical Reports Server (NTRS)

    Shagnea, Anita M.; Lowman, Douglas S.; Withers, B. Edward

    1990-01-01

    As part of the Guidance and Control Software (GCS) research project being sponsored by NASA to evaluate the failure processes of software, standard industry software development procedures are being employed. To ensure that these procedures are authentic, the guidelines outlined in the Radio Technical Commission for Aeronautics (RTCA/DO-178A document entitled, software considerations in airborne systems and equipment certification, were adopted. A major aspect of these guidelines is proper documentation. As such, this report, the plan for software aspects of certification, was produced in accordance with DO-178A. An overview is given of the GCS research project, including the goals of the project, project organization, and project schedules. It also specifies the plans for all aspects of the project which relate to the certification of the GCS implementations developed under a NASA contract. These plans include decisions made regarding the software specification, accuracy requirements, configuration management, implementation development and verification, and the development of the GCS simulator.

  8. Integrated Advanced Microwave Sounding Unit-A (AMSU-A): Monthly Report for August

    NASA Technical Reports Server (NTRS)

    Nieto, A.

    2000-01-01

    Included in this report are Combined Program Delivery Schedules and Reports; a report from the Product Team Leaders on the status of all major program elements; Contract Data Requirements List (CDRL) 503, the Weight and Power Budgets; CDRL 204, reporting on the activities of Performance Assurance; CDRL 203, the Configuration Management Status Report; and the Documentation/Data Management Status Report.

  9. Space Shuttle aerothermodynamic data report, phase C

    NASA Technical Reports Server (NTRS)

    1985-01-01

    Space shuttle aerothermodynamic data, collected from a continuing series of wind tunnel tests, are permanently stored with the Data Management Services (DMS) system. Information pertaining to current baseline configuration definition is also stored. Documentation of DMS processed data arranged sequentially and by space shuttle configuration are included. An up-to-date record of all applicable aerothermodynamic data collected, processed, or summarized during the space shuttle program is provided. Tables are designed to provide suvery information to the various space shuttle managerial and technical levels.

  10. Aerothermodynamic data base. Data file contents report, phase C

    NASA Technical Reports Server (NTRS)

    Lutz, G. R.

    1983-01-01

    Space shuttle aerothermodynamic data, collected from a continuing series of wind tunnel tests, are permanently stored with the Data Management Services (DMS) system. Information pertaining to current baseline configuration definition is also stored. Documentation of DMS processed data arranged sequentially and by space shuttle configuration is listed to provide an up-to-date record of all applicable aerothermodynamic data collected, processed, or summarized during the space shuttle program. Tables provide survey information to the various space shuttle managerial and technical levels.

  11. Aerothermodynamic Data Base

    NASA Technical Reports Server (NTRS)

    1984-01-01

    Space shuttle aerothermodynamic data, collected from a continuing series of wind tunnel tests, are permanently stored with the Data Management Services (DMS) system. Information pertaining to current baseline configuration definition is also stored. A list of documentation of DMS processed data arranged sequentially and by space shuttle configuration is presented. The listing provides an up to date record of all applicable aerothermodynamic data collected, processed, or summarized during the space shuttle program. Tables are designed to provide survey information to the various space shuttle managerial and technical levels.

  12. Management of infection control in dental practice.

    PubMed

    Smith, A; Creanor, S; Hurrell, D; Bagg, J; McCowan, M

    2009-04-01

    This was an observational study in which the management policies and procedures associated with infection control and instrument decontamination were examined in 179 dental surgeries by a team of trained surveyors. Information relating to the management of a wide range of infection control procedures, in particular the decontamination of dental instruments, was collected by interview and by examination of practice documentation. This study found that although the majority of surgeries (70%) claimed to have a management policy on infection control, only 50% of these were documented. For infection control policies, 79% of surgeries had access to the British Dental Association Advice Sheet A12. Infection control policies were claimed to be present in 89% of surgeries, of which 62% were documented. Seventy-seven per cent of staff claimed to have received specific infection control training, but for instrument decontamination this was provided mainly by demonstration (97%) or observed practice (88%). Many dental nurses (74%) and dental practitioners (57%) did not recognise the symbol used to designate a single-use device. Audit of infection control or decontamination activities was undertaken in 11% of surgeries. The majority of surgeries have policies and procedures for the management of infection control in dental practice, but in many instances these are not documented. The training of staff in infection control and its documentation is poorly managed and consideration should be given to development of quality management systems for use in dental practice.

  13. SGML and HTML: The Merging of Document Management and Electronic Document Publishing.

    ERIC Educational Resources Information Center

    Dixon, Ross

    1996-01-01

    Document control is an issue for organizations that use SGML/HTML. The prevalent approach is to apply the same techniques to document elements that are applied to full documents, a practice that has led to an overlap of electronic publishing and document management. Lists requirements for the management of SGML/HTML documents. (PEN)

  14. Attitude control/momentum management of the Space Station Freedom for large angle torque-equilibrium-attitude configurations

    NASA Technical Reports Server (NTRS)

    Parlos, Alexander G.; Sunkel, John W.

    1990-01-01

    An attitude-control and momentum-management (ACMM) system for the Space Station in a large-angle torque-equilibrium-attitude (TEA) configuration is developed analytically and demonstrated by means of numerical simulations. The equations of motion for a rigid-body Space Station model are outlined; linearized equations for an arbitrary TEA (resulting from misalignment of control and body axes) are derived; the general requirements for an ACMM are summarized; and a pole-placement linear-quadratic regulator solution based on scheduled gains is proposed. Results are presented in graphs for (1) simulations based on configuration MB3 (showing the importance of accounting for the cross-inertia terms in the TEA estimate) and (2) simulations of a stepwise change from configuration MB3 to the 'assembly complete' stage over 130 orbits (indicating that the present ACCM scheme maintains sufficient control over slowly varying Space Station dynamics).

  15. Management control and status reports documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 5

    NASA Technical Reports Server (NTRS)

    Callender, E. David; Steinbacher, Jody

    1989-01-01

    This is the fifth of five volumes on Information System Life-Cycle and Documentation Standards. This volume provides a well organized, easily used standard for management control and status reports used in monitoring and controlling the management, development, and assurance of informations systems and software, hardware, and operational procedures components, and related processes.

  16. A Content Markup Language for Data Services

    NASA Astrophysics Data System (ADS)

    Noviello, C.; Acampa, P.; Mango Furnari, M.

    Network content delivery and documents sharing is possible using a variety of technologies, such as distributed databases, service-oriented applications, and so forth. The development of such systems is a complex job, because document life cycle involves a strong cooperation between domain experts and software developers. Furthermore, the emerging software methodologies, such as the service-oriented architecture and knowledge organization (e.g., semantic web) did not really solve the problems faced in a real distributed and cooperating settlement. In this chapter the authors' efforts to design and deploy a distribute and cooperating content management system are described. The main features of the system are a user configurable document type definition and a management middleware layer. It allows CMS developers to orchestrate the composition of specialized software components around the structure of a document. In this chapter are also reported some of the experiences gained on deploying the developed framework in a cultural heritage dissemination settlement.

  17. NASA ISS Portable Fan Assembly Acoustics

    NASA Technical Reports Server (NTRS)

    Boone, Andrew; Allen, Christopher S.; Hess, Linda F.

    2018-01-01

    The Portable Fan Assembly (PFA) is a variable speed fan that can be used to provide additional ventilation inside International Space Station (ISS) modules as needed for crew comfort or for enhanced mixing of the ISS atmosphere. This fan can also be configured with a Shuttle era lithium hydroxide (LiOH) canister for CO2 removal in confined areas partially of fully isolated from the primary Environmental Control and Life Support System (ECLSS) on ISS which is responsible for CO2 removal. This report documents noise emission levels of the PFA at various speed settings and configurations. It also documents the acoustic attenuation effects realized when circulating air through the PFA inlet and outlet mufflers and when operating in its CO2 removal configuration (CRK) with a LiOH canister (sorbent bed) installed over the fan outlet.

  18. 33 CFR 96.250 - What documents and reports must a safety management system have?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ...) Safety management system document and data maintenance (1) Procedures which establish and maintain control of all documents and data relevant to the safety management system. (2) Documents are available at... safety management system have? 96.250 Section 96.250 Navigation and Navigable Waters COAST GUARD...

  19. [Requirements for the successful installation of an data management system].

    PubMed

    Benson, M; Junger, A; Quinzio, L; Hempelmann, G

    2002-08-01

    Due to increasing requirements on medical documentation, especially with reference to the German Social Law binding towards quality management and introducing a new billing system (DRGs), an increasing number of departments consider to implement a patient data management system (PDMS). The installation should be professionally planned as a project in order to insure and complete a successful installation. The following aspects are essential: composition of the project group, definition of goals, finance, networking, space considerations, hardware, software, configuration, education and support. Project and finance planning must be prepared before beginning the project and the project process must be constantly evaluated. In selecting the software, certain characteristics should be considered: use of standards, configurability, intercommunicability and modularity. Our experience has taught us that vaguely defined goals, insufficient project planning and the existing management culture are responsible for the failure of PDMS installations. The software used tends to play a less important role.

  20. Managing Documents in the Wider Area: Intelligent Document Management.

    ERIC Educational Resources Information Center

    Bittleston, Richard

    1995-01-01

    Discusses techniques for managing documents in wide area networks, reviews technique limitations, and offers recommendations to database designers. Presented techniques include: increasing bandwidth, reducing data traffic, synchronizing documentation, partial synchronization, audit trials, navigation, and distribution control and security. Two…

  1. Unix Security Cookbook

    NASA Astrophysics Data System (ADS)

    Rehan, S. C.

    This document has been written to help Site Managers secure their Unix hosts from being compromised by hackers. I have given brief introductions to the security tools along with downloading, configuring and running information. I have also included a section on my recommendations for installing these security tools starting from an absolute minimum security requirement.

  2. Towards easing the configuration and new team member accommodation for open source software based portals

    NASA Astrophysics Data System (ADS)

    Fu, L.; West, P.; Zednik, S.; Fox, P. A.

    2013-12-01

    For simple portals such as vocabulary based services, which contain small amounts of data and require only hyper-textual representation, it is often an overkill to adopt the whole software stack of database, middleware and front end, or to use a general Web development framework as the starting point of development. Directly combining open source software is a much more favorable approach. However, our experience with the Coastal and Marine Spatial Planning Vocabulary (CMSPV) service portal shows that there are still issues such as system configuration and accommodating a new team member that need to be handled carefully. In this contribution, we share our experience in the context of the CMSPV portal, and focus on the tools and mechanisms we've developed to ease the configuration job and the incorporation process of new project members. We discuss the configuration issues that arise when we don't have complete control over how the software in use is configured and need to follow existing configuration styles that may not be well documented, especially when multiple pieces of such software need to work together as a combined system. As for the CMSPV portal, it is built on two pieces of open source software that are still under rapid development: a Fuseki data server and Epimorphics Linked Data API (ELDA) front end. Both lack mature documentation and tutorials. We developed comparison and labeling tools to ease the problem of system configuration. Another problem that slowed down the project is that project members came and went during the development process, so new members needed to start with a partially configured system and incomplete documentation left by old members. We developed documentation/tutorial maintenance mechanisms based on our comparison and labeling tools to make it easier for the new members to be incorporated into the project. These tools and mechanisms also provided benefit to other projects that reused the software components from the CMSPV system.

  3. 78 FR 23685 - Airworthiness Directives; The Boeing Company

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-22

    ... installing new operational software for the electrical load management system and configuration database. The..., installing a new electrical power control panel, and installing new operational software for the electrical load management system and configuration database. Since the proposed AD was issued, we have received...

  4. 75 FR 1002 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-01-07

    ... derivatives dealers to establish, document, and maintain a system of internal risk management controls. The... establishing, documenting, and reviewing its internal risk management control system, which are designed to... internal risk management control system) + (One new OTC derivatives dealer x 200 hours to maintain an...

  5. Universal Payload Information Management

    NASA Technical Reports Server (NTRS)

    Elmore, Ralph B.

    2003-01-01

    As the overall manager and integrator of International Space Station (ISS) science payloads, the Payload Operations Integration Center (POIC) at Marshall Space Flight Center has a critical need to provide an information management system for exchange and control of ISS payload files as well as to coordinate ISS payload related operational changes. The POIC's information management system has a fundamental requirement to provide secure operational access not only to users physically located at the POIC, but also to remote experimenters and International Partners physically located in different parts of the world. The Payload Information Management System (PIMS) is a ground-based electronic document configuration management and collaborative workflow system that was built to service the POIC's information management needs. This paper discusses the application components that comprise the PIMS system, the challenges that influenced its design and architecture, and the selected technologies it employs. This paper will also touch on the advantages of the architecture, details of the user interface, and lessons learned along the way to a successful deployment. With PIMS, a sophisticated software solution has been built that is not only universally accessible for POIC customer s information management needs, but also universally adaptable in implementation and application as a generalized information management system.

  6. Final definition and preliminary design study for the initial atmospheric cloud physics laboratory, a Spacelab mission payload

    NASA Technical Reports Server (NTRS)

    1976-01-01

    The following areas related to the final definition and preliminary design study of the initial atmospheric cloud physics laboratory (ACPL) were covered: (1) proposal organization, personnel, schedule, and project management, (2) proposed configurations, (3) study objectives, (4) ACPL experiment program listing and description, (5) mission/flight flexibility and modularity/commonality, (6) study plan, and (7) description of following tasks: requirement analysis and definition task flow, systems analysis and trade studies, subsystem analysis and trade studies, specifications and interface control documents, preliminary design task flow, work breakdown structure, programmatic analysis and planning, and project costs. Finally, an overview of the scientific requirements was presented.

  7. GPM Timeline Inhibits For IT Processing

    NASA Technical Reports Server (NTRS)

    Dion, Shirley K.

    2014-01-01

    The Safety Inhibit Timeline Tool was created as one approach to capturing and understanding inhibits and controls from IT through launch. Global Precipitation Measurement (GPM) Mission, which launched from Japan in March 2014, was a joint mission under a partnership between the National Aeronautics and Space Administration (NASA) and the Japan Aerospace Exploration Agency (JAXA). GPM was one of the first NASA Goddard in-house programs that extensively used software controls. Using this tool during the GPM buildup allowed a thorough review of inhibit and safety critical software design for hazardous subsystems such as the high gain antenna boom, solar array, and instrument deployments, transmitter turn-on, propulsion system release, and instrument radar turn-on. The GPM safety team developed a methodology to document software safety as part of the standard hazard report. As a result of this process, a new tool safety inhibit timeline was created for management of inhibits and their controls during spacecraft buildup and testing during IT at GSFC and at the launch range in Japan. The Safety Inhibit Timeline Tool was a pathfinder approach for reviewing software that controls the electrical inhibits. The Safety Inhibit Timeline Tool strengthens the Safety Analysts understanding of the removal of inhibits during the IT process with safety critical software. With this tool, the Safety Analyst can confirm proper safe configuration of a spacecraft during each IT test, track inhibit and software configuration changes, and assess software criticality. In addition to understanding inhibits and controls during IT, the tool allows the Safety Analyst to better communicate to engineers and management the changes in inhibit states with each phase of hardware and software testing and the impact of safety risks. Lessons learned from participating in the GPM campaign at NASA and JAXA will be discussed during this session.

  8. [Recommendations for the control of documents and the establishment of a documentary system].

    PubMed

    Vinner, E

    2013-06-01

    The quality management system that must be implemented in a MBL to meet the requirements of the standard NF EN ISO 15189 is based, among other things, on the creation and use by staff of a documentary system approved and updated. This documentary system is constituted by external documents (standards, suppliers' documents...) and internal documents (quality manual, procedures, instructions, technical and quality recordings...). A procedure of the documentary system control must be formalized. The documentary system should be modeled in order to identify the various procedures to be drafted and the incurred risks in the case a document would be missing in this system. Each document must be indexed in a unique way and document management must be carried out rigorously. The use of document management software is a great help to manage the life cycle of documents.

  9. Impact of configuration management system of computer center on support of scientific projects throughout their lifecycle

    NASA Astrophysics Data System (ADS)

    Bogdanov, A. V.; Iuzhanin, N. V.; Zolotarev, V. I.; Ezhakova, T. R.

    2017-12-01

    In this article the problem of scientific projects support throughout their lifecycle in the computer center is considered in every aspect of support. Configuration Management system plays a connecting role in processes related to the provision and support of services of a computer center. In view of strong integration of IT infrastructure components with the use of virtualization, control of infrastructure becomes even more critical to the support of research projects, which means higher requirements for the Configuration Management system. For every aspect of research projects support, the influence of the Configuration Management system is being reviewed and development of the corresponding elements of the system is being described in the present paper.

  10. Configuration management program plan for Hanford site systems engineering

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kellie, C.L.

    This plan establishes the integrated management program for the evolving technical baseline developed through the systems engineering process. This configuration management program aligns with the criteria identified in the DOE Standard, DOE-STD-1073-93. Included are specific requirements for control of the systems engineering RDD-100 database, and electronic data incorporated in the database that establishes the Hanford Site Technical Baseline.

  11. Orbiter data reduction complex data processing requirements for the OFT mission evaluation team (level C)

    NASA Technical Reports Server (NTRS)

    1979-01-01

    This document addresses requirements for post-test data reduction in support of the Orbital Flight Tests (OFT) mission evaluation team, specifically those which are planned to be implemented in the ODRC (Orbiter Data Reduction Complex). Only those requirements which have been previously baselined by the Data Systems and Analysis Directorate configuration control board are included. This document serves as the control document between Institutional Data Systems Division and the Integration Division for OFT mission evaluation data processing requirements, and shall be the basis for detailed design of ODRC data processing systems.

  12. High resolution microwave spectrometer sounder (HIMSS), volume 1, book 2

    NASA Technical Reports Server (NTRS)

    1990-01-01

    The following topics are presented with respect to the high resolution microwave spectrometer sounder (HIMSS) that is to be used as an instrument for NASA's Earth Observing System (EOS): (1) preliminary program plans; (2) contract end item (CEI) specification; and (3) the instrument interface description document. Under the preliminary program plans section, plans dealing with the following subject areas are discussed: spares, performance assurance, configuration management, software implementation, contamination, calibration management, and verification.

  13. Management Overview of System Technical Support Plan for the FIREFINDER System Support Center.

    DTIC Science & Technology

    1980-08-06

    34.. /b , UNCLASSIFIED SECU ITY CLASSIFICATION OF THIS PAGE (When Data Entered) READ INSTRUCTIONSREPORT DOCUMENTATION PAGE BEFORE COMPLETING FORM I. REPORT...Evaluation Agency USASA U.S. Army Security Agency UTM Universal Transverse Mercator V Volts V&V Verification and Validation VCSA Vice-Chief of Staff, Army VDD... classification , configuration audits, and so forth. INSTR 5010.27 Management of Automatic Data System 9 November 1971 Development Establishes uniform

  14. Using a formal requirements management tool for system engineering: first results at ESO

    NASA Astrophysics Data System (ADS)

    Zamparelli, Michele

    2006-06-01

    The attention to proper requirement analysis and maintenance is growing in modern astronomical undertakings. The increasing degree of complexity that current and future generations of projects have reached requires substantial system engineering efforts and the usage of all available technology to keep project development under control. One such technology is a tool which helps managing relationships between deliverables at various development stages, and across functional subsystems and disciplines as different as software, mechanics, optics and electronics. The immediate benefits are traceability and the possibility to do impact analysis. An industrially proven tool for requirements management is presented together with the first results across some projects at ESO and a cost/benefit analysis of its usage. Experience gathered so far shows that the extensibility and configurability of the tool from one hand, and integration with common documentation formats and standards on the other, make it appear as a promising solution for even small scale system development.

  15. Dynamic Airspace Configuration

    NASA Technical Reports Server (NTRS)

    Bloem, Michael J.

    2014-01-01

    In air traffic management systems, airspace is partitioned into regions in part to distribute the tasks associated with managing air traffic among different systems and people. These regions, as well as the systems and people allocated to each, are changed dynamically so that air traffic can be safely and efficiently managed. It is expected that new air traffic control systems will enable greater flexibility in how airspace is partitioned and how resources are allocated to airspace regions. In this talk, I will begin by providing an overview of some previous work and open questions in Dynamic Airspace Configuration research, which is concerned with how to partition airspace and assign resources to regions of airspace. For example, I will introduce airspace partitioning algorithms based on clustering, integer programming optimization, and computational geometry. I will conclude by discussing the development of a tablet-based tool that is intended to help air traffic controller supervisors configure airspace and controllers in current operations.

  16. Space shuttle configuration accounting functional design specification

    NASA Technical Reports Server (NTRS)

    1974-01-01

    An analysis is presented of the requirements for an on-line automated system which must be capable of tracking the status of requirements and engineering changes and of providing accurate and timely records. The functional design specification provides the definition, description, and character length of the required data elements and the interrelationship of data elements to adequately track, display, and report the status of active configuration changes. As changes to the space shuttle program levels II and III configuration are proposed, evaluated, and dispositioned, it is the function of the configuration management office to maintain records regarding changes to the baseline and to track and report the status of those changes. The configuration accounting system will consist of a combination of computers, computer terminals, software, and procedures, all of which are designed to store, retrieve, display, and process information required to track proposed and proved engineering changes to maintain baseline documentation of the space shuttle program levels II and III.

  17. Integrated Advanced Sounding Unit-A (AMSU-A). Configuration Management Plan

    NASA Technical Reports Server (NTRS)

    Cavanaugh, J.

    1996-01-01

    The purpose of this plan is to identify the baseline to be established during the development life cycle of the integrated AMSU-A, and define the methods and procedures which Aerojet will follow in the implementation of configuration control for each established baseline. Also this plan establishes the Configuration Management process to be used for the deliverable hardware, software, and firmware of the Integrated AMSU-A during development, design, fabrication, test, and delivery.

  18. Intelligent redundant actuation system requirements and preliminary system design

    NASA Technical Reports Server (NTRS)

    Defeo, P.; Geiger, L. J.; Harris, J.

    1985-01-01

    Several redundant actuation system configurations were designed and demonstrated to satisfy the stringent operational requirements of advanced flight control systems. However, this has been accomplished largely through brute force hardware redundancy, resulting in significantly increased computational requirements on the flight control computers which perform the failure analysis and reconfiguration management. Modern technology now provides powerful, low-cost microprocessors which are effective in performing failure isolation and configuration management at the local actuator level. One such concept, called an Intelligent Redundant Actuation System (IRAS), significantly reduces the flight control computer requirements and performs the local tasks more comprehensively than previously feasible. The requirements and preliminary design of an experimental laboratory system capable of demonstrating the concept and sufficiently flexible to explore a variety of configurations are discussed.

  19. Engineering Documentation and Data Control

    NASA Technical Reports Server (NTRS)

    Matteson, Michael J.; Bramley, Craig; Ciaruffoli, Veronica

    2001-01-01

    Mississippi Space Services (MSS) the facility services contractor for NASA's John C. Stennis Space Center (SSC), is utilizing technology to improve engineering documentation and data control. Two identified improvement areas, labor intensive documentation research and outdated drafting standards, were targeted as top priority. MSS selected AutoManager(R) WorkFlow from Cyco software to manage engineering documentation. The software is currently installed on over 150 desctops. The outdated SSC drafting standard was written for pre-CADD drafting methods, in other words, board drafting. Implementation of COTS software solutions to manage engineering documentation and update the drafting standard resulted in significant increases in productivity by reducing the time spent searching for documents.

  20. Environmental control/life support system for Space Station

    NASA Technical Reports Server (NTRS)

    Miller, C. W.; Heppner, D. B.; Schubert, F. H.; Dahlhausen, M. J.

    1986-01-01

    The functional, operational, and design load requirements for the Environmental Control/Life Support System (ECLSS) are described. The ECLSS is divided into two groups: (1) an atmosphere management group and (2) a water and waste management group. The interaction between the ECLSS and the Space Station Habitability System is examined. The cruciform baseline station design, the delta and big T module configuration, and the reference Space Station configuration are evaluated in terms of ECLSS requirements. The distribution of ECLSS equipment in a reference Space Station configuration is studied as a function of initial operating conditions and growth orbit capabilities. The benefits of water electrolysis as a Space Station utility are considered.

  1. Results of investigation on an 0.004-scale 140c modified configuration space shuttle vehicle orbiter model (74-0) in the NASA/Langley Research Center hypersonic nitrogen tunnel (OA89)

    NASA Technical Reports Server (NTRS)

    Hawthorne, P. J.

    1975-01-01

    Wind tunnel test data for the modified space shuttle vehicle orbiter is documented. Tests were made at various elevon settings and additionally in wing off/bodyflap off configuration at angles of attack from -5 to 42.5 degrees at zero yaw. Data obtained on high hypersonic longitudinal and lateral directional stability and control characteristics of the updated SSV configuration in an initially diatomic medium are included.

  2. Cargo Movement Operations System (CMOS). Final Software Design Document Increment III, (PC UNIX - Navy Configuration)

    DTIC Science & Technology

    1991-07-03

    NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED ( ] ORIGINATOR CONTROL NUMBER: SDD-0003 PROGRAM OFFICE CONTROL NUMBER: DATA ITEM DISCREPANCY WORKSHEET CDRL NUMBER: A006-02 DATE: 07/03/91 ORIGINATOR NAME: Vivian L. Martin OFFICE SYMBOL: SAIC TELEPHONE NUMBER: 272-2999 SUBSTANTIVE: X EDITORIAL: PAGE NUMBER: L-1 PARA NUMBER: 10 COMMENT OR RECOMMENDED CHANGE: Explain the effect of "no longer required" or "replaced" CSUs on the Navy configuration Menu hierarchy. RATIONALE: Paragraph 10 states that the CMOS menu heirarchy is

  3. Co-scheduling of network resource provisioning and host-to-host bandwidth reservation on high-performance network and storage systems

    DOEpatents

    Yu, Dantong; Katramatos, Dimitrios; Sim, Alexander; Shoshani, Arie

    2014-04-22

    A cross-domain network resource reservation scheduler configured to schedule a path from at least one end-site includes a management plane device configured to monitor and provide information representing at least one of functionality, performance, faults, and fault recovery associated with a network resource; a control plane device configured to at least one of schedule the network resource, provision local area network quality of service, provision local area network bandwidth, and provision wide area network bandwidth; and a service plane device configured to interface with the control plane device to reserve the network resource based on a reservation request and the information from the management plane device. Corresponding methods and computer-readable medium are also disclosed.

  4. Federal Emergency Management Information System (FEMIS) system administration guide. Version 1.2

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Burford, M.J.; Burnett, R.A.; Curtis, L.M.

    The Federal Emergency Management Information System (FEMIS) is an emergency management planning and analysis tool that is being developed under the direction of the US Army Chemical biological Defense Command. The FEMIS System Administration Guide defines FEMIS hardware and software requirements and gives instructions for installing the FEMIS system package. System administrators, database administrators, and general users can use this guide to install, configure, and maintain the FEMIS client software package. This document provides a description of the FEMIS environment; distribution media; data, communications, and electronic mail servers; user workstations; and system management.

  5. Synchronous meteorological satellite system description document, volume 3

    NASA Technical Reports Server (NTRS)

    Pipkin, F. B.

    1971-01-01

    The structural design, analysis, and mechanical integration of the synchronous meteorological satellite system are presented. The subjects discussed are: (1) spacecraft configuration, (2) structural design, (3) static load tests, (4) fixed base sinusoidal vibration survey, (5) flight configuration sinusoidal vibration tests, (6) spacecraft acoustic test, and (7) separation and shock test. Descriptions of the auxiliary propulsion subsystem, the apogee boost motor, communications system, and thermal control subsystem are included.

  6. Mission Control Center (MCC) System Specification for the Shuttle Orbital Flight Test (OFT) Timeframe

    NASA Technical Reports Server (NTRS)

    1976-01-01

    System specifications to be used by the mission control center (MCC) for the shuttle orbital flight test (OFT) time frame were described. The three support systems discussed are the communication interface system (CIS), the data computation complex (DCC), and the display and control system (DCS), all of which may interfere with, and share processing facilities with other applications processing supporting current MCC programs. The MCC shall provide centralized control of the space shuttle OFT from launch through orbital flight, entry, and landing until the Orbiter comes to a stop on the runway. This control shall include the functions of vehicle management in the area of hardware configuration (verification), flight planning, communication and instrumentation configuration management, trajectory, software and consumables, payloads management, flight safety, and verification of test conditions/environment.

  7. 78 FR 23690 - Airworthiness Directives; The Boeing Company

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-22

    ... management system (CMS) configuration database; and installing new operational program software (OPS) for the CSCP, zone management unit (ZMU), passenger address controller, cabin interphone controller, cabin area... on the Internet at http://www.regulations.gov ; or in person at the Docket Management Facility...

  8. AdaNET prototype library administration manual

    NASA Technical Reports Server (NTRS)

    Hanley, Lionel

    1989-01-01

    The functions of the AdaNET Prototype Library of Reusable Software Parts is described. Adopted from the Navy Research Laboratory's Reusability Guidebook (V.5.0), this is a working document, customized for use the the AdaNET Project. Within this document, the term part is used to denote the smallest unit controlled by a library and retrievable from it. A part may have several constituents, which may not be individually tracked. Presented are the types of parts which may be stored in the library and the relationships among those parts; a concept of trust indicators which provide measures of confidence that a user of a previously developed part may reasonably apply to a part for a new application; search and retrieval, configuration management, and communications among those who interact with the AdaNET Prototype Library; and the AdaNET Prototype, described from the perspective of its three major users: the part reuser and retriever, the part submitter, and the librarian and/or administrator.

  9. Improvements to information management systems simulator

    NASA Technical Reports Server (NTRS)

    Bilek, R. W.

    1972-01-01

    The performance of personnel in the augmentation and improvement of the interactive IMSIM information management simulation model is summarized. With this augmented model, NASA now has even greater capabilities for the simulation of computer system configurations, data processing loads imposed on these configurations, and executive software to control system operations. Through these simulations, NASA has an extremely cost effective capability for the design and analysis of computer-based data management systems.

  10. SHARP pre-release v1.0 - Current Status and Documentation

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Mahadevan, Vijay S.; Rahaman, Ronald O.

    The NEAMS Reactor Product Line effort aims to develop an integrated multiphysics simulation capability for the design and analysis of future generations of nuclear power plants. The Reactor Product Line code suite’s multi-resolution hierarchy is being designed to ultimately span the full range of length and time scales present in relevant reactor design and safety analyses, as well as scale from desktop to petaflop computing platforms. In this report, building on a several previous report issued in September 2014, we describe our continued efforts to integrate thermal/hydraulics, neutronics, and structural mechanics modeling codes to perform coupled analysis of a representativemore » fast sodium-cooled reactor core in preparation for a unified release of the toolkit. The work reported in the current document covers the software engineering aspects of managing the entire stack of components in the SHARP toolkit and the continuous integration efforts ongoing to prepare a release candidate for interested reactor analysis users. Here we report on the continued integration effort of PROTEUS/Nek5000 and Diablo into the NEAMS framework and the software processes that enable users to utilize the capabilities without losing scientific productivity. Due to the complexity of the individual modules and their necessary/optional dependency library chain, we focus on the configuration and build aspects for the SHARP toolkit, which includes capability to autodownload dependencies and configure/install with optimal flags in an architecture-aware fashion. Such complexity is untenable without strong software engineering processes such as source management, source control, change reviews, unit tests, integration tests and continuous test suites. Details on these processes are provided in the report as a building step for a SHARP user guide that will accompany the first release, expected by Mar 2016.« less

  11. SNL Mechanical Computer Aided Design (MCAD) guide 2007.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Moore, Brandon; Pollice, Stephanie L.; Martinez, Jack R.

    2007-12-01

    This document is considered a mechanical design best-practice guide to new and experienced designers alike. The contents consist of topics related to using Computer Aided Design (CAD) software, performing basic analyses, and using configuration management. The details specific to a particular topic have been leveraged against existing Product Realization Standard (PRS) and Technical Business Practice (TBP) requirements while maintaining alignment with sound engineering and design practices. This document is to be considered dynamic in that subsequent updates will be reflected in the main title, and each update will be published on an annual basis.

  12. U.S. Army Human Capital Enterprise (HCE) ARFORGEN Data Management, Correlation, Integration and Synchronization Analysis

    DTIC Science & Technology

    2011-08-15

    system must, at a minimum, include  design and configuration  framework  supporting:  Part 1.   Net  Ready. The system must support  net ‐ centric operations...Analyze, evaluate and incorporate relevant DoD Architecture Framework . 5) Document standards for each task / condition combination. 6) Prepare final FAA...task  Analyze, evaluate and incorporate relevant Army Architecture Framework  Document standards for each task/condition combination forming

  13. Guideline for Software Documentation Management.

    ERIC Educational Resources Information Center

    National Bureau of Standards (DOC), Washington, DC.

    Designed as a basic reference for federal personnel concerned with the development, maintenance, enhancement, control, and management of computer-based systems, this manual provides a general overview of the software development process and software documentation issues so that managers can assess their own documentation requirements. Reference is…

  14. Configuration of management accounting information system for multi-stage manufacturing

    NASA Astrophysics Data System (ADS)

    Mkrtychev, S. V.; Ochepovsky, A. V.; Enik, O. A.

    2018-05-01

    The article presents an approach to configuration of a management accounting information system (MAIS) that provides automated calculations and the registration of normative production losses in multi-stage manufacturing. The use of MAIS with the proposed configuration at the enterprises of textile and woodworking industries made it possible to increase the accuracy of calculations for normative production losses and to organize accounting thereof with the reference to individual stages of the technological process. Thus, high efficiency of multi-stage manufacturing control is achieved.

  15. Software solutions manage the definition, operation, maintenance and configuration control of the National Ignition Facility

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Dobson, D; Churby, A; Krieger, E

    2011-07-25

    The National Ignition Facility (NIF) is the world's largest laser composed of millions of individual parts brought together to form one massive assembly. Maintaining control of the physical definition, status and configuration of this structure is a monumental undertaking yet critical to the validity of the shot experiment data and the safe operation of the facility. The NIF business application suite of software provides the means to effectively manage the definition, build, operation, maintenance and configuration control of all components of the National Ignition Facility. State of the art Computer Aided Design software applications are used to generate a virtualmore » model and assemblies. Engineering bills of material are controlled through the Enterprise Configuration Management System. This data structure is passed to the Enterprise Resource Planning system to create a manufacturing bill of material. Specific parts are serialized then tracked along their entire lifecycle providing visibility to the location and status of optical, target and diagnostic components that are key to assessing pre-shot machine readiness. Nearly forty thousand items requiring preventive, reactive and calibration maintenance are tracked through the System Maintenance & Reliability Tracking application to ensure proper operation. Radiological tracking applications ensure proper stewardship of radiological and hazardous materials and help provide a safe working environment for NIF personnel.« less

  16. Centralized Fabric Management Using Puppet, Git, and GLPI

    NASA Astrophysics Data System (ADS)

    Smith, Jason A.; De Stefano, John S., Jr.; Fetzko, John; Hollowell, Christopher; Ito, Hironori; Karasawa, Mizuki; Pryor, James; Rao, Tejas; Strecker-Kellogg, William

    2012-12-01

    Managing the infrastructure of a large and complex data center can be extremely difficult without taking advantage of recent technological advances in administrative automation. Puppet is a seasoned open-source tool that is designed for enterprise class centralized configuration management. At the RHIC and ATLAS Computing Facility (RACF) at Brookhaven National Laboratory, we use Puppet along with Git, GLPI, and some custom scripts as part of our centralized configuration management system. In this paper, we discuss how we use these tools for centralized configuration management of our servers and services, change management requiring authorized approval of production changes, a complete version controlled history of all changes made, separation of production, testing and development systems using puppet environments, semi-automated server inventory using GLPI, and configuration change monitoring and reporting using the Puppet dashboard. We will also discuss scalability and performance results from using these tools on a 2,000+ node cluster and 400+ infrastructure servers with an administrative staff of approximately 25 full-time employees (FTEs).

  17. Guidelines for the creation and management of geographic data bases within a GIS environment, version 1.0

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Durfee, R.C.; Land, M.L.; McCord, R.A.

    1994-07-01

    A Geographic Information System (GIS) provides the ability to manage and analyze all types of geographic and environmental information. It performs these functions by providing the tools necessary to capture, access, analyze, and display spatially referenced information in graphic and tabular form. Typical data elements that can be visualized in a map might include roads, buildings, topography, streams, waste areas, monitoring wells, groundwater measurements, soil sample results, landcover, and demography. The intent of this document is to provide data management and quality assurance (QA) guidelines that will aid implementors and users of GIS technology and data bases. These guidelines shouldmore » be useful in all, phases of GIS activities, including the following: (1) project planning, (2) data collection and generation, (3) data maintenance and management, (4) QA and standards, (5) project implementation, (6) spatial analysis and data interpretation, (7) data transformation and exchange, and (8) output and reporting. The daily use of desktop GIS technologies within Martin Marietta Energy Systems, Inc. (Energy Systems), is a relatively new phenomenon, but usage is increasing rapidly. Large volumes of GIS-related data are now being collected and analyzed for the U.S. Department of Energy (DOE) Oak Ridge Reservation (ORR) and its facilities. It is very important to establish and follow good data management practices for GIS. In the absence of such practices, data-related problems will overwhelm users for many years. In comparison with traditional data processing and software life-cycle management, there is limited information on GIS QA techniques, data standards and structures, configuration control, and documentation practices. This lack of information partially results from the newness of the technology and the complexity of spatial information and geographic analysis techniques as compared to typical tabular data management.« less

  18. Cargo Movement Operations System (CMOS). Draft Software Design Document for the PC UNIX Prototype (Air Force Configuration), Increment III

    DTIC Science & Technology

    1991-04-21

    COMMENT: YES [ ] NO [ ] ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ I CLOSED [ ] ORIGINATOR CONTROL NUMBER: SDD-0002...ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS! OPEN [ ] CLOSED [ ] ORIGINATOR CONTROL NUMBER: SDD-0003 PROGRAM OFFICE CONTROL...COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED [ ] ORIGINATOR CONTROL NUMBER: SDD-0004 PROGPLAM OFFICE CONTROL NUMBER

  19. Study of orbiter/payload interface communications configuration control board directive from an operational perspective

    NASA Technical Reports Server (NTRS)

    Addis, A. W.; Tatosian, C. G.; Lidsey, J. F.

    1974-01-01

    Orbiter/payload data and communications interface was examined. It was found that the Configuration Control Board Directive (CCBD) greatly increases the capability of the orbiter to communicate with a wide variety of projected shuttle payloads. Rather than being derived from individual payload communication requirements, the CCBD appears to be based on an operational philosophy that requires the orbiter to duplicate or augment the ground network/payload communication links. It is suggested that the implementation of the CCBD be reviewed and compared with the Level 1 Program Requirements Document, differences reconciled, and interface characteristics defined.

  20. Management approach recommendations. Earth Observatory Satellite system definition study (EOS)

    NASA Technical Reports Server (NTRS)

    1974-01-01

    Management analyses and tradeoffs were performed to determine the most cost effective management approach for the Earth Observatory Satellite (EOS) Phase C/D. The basic objectives of the management approach are identified. Some of the subjects considered are as follows: (1) contract startup phase, (2) project management control system, (3) configuration management, (4) quality control and reliability engineering requirements, and (5) the parts procurement program.

  1. The influence of health system organizational structure and culture on integration of health services: the example of HIV service monitoring in South Africa.

    PubMed

    Kawonga, Mary; Blaauw, Duane; Fonn, Sharon

    2016-11-01

    Administrative integration of disease control programmes (DCPs) within the district health system has been a health sector reform priority in South Africa for two decades. The reforms entail district managers assuming authority for the planning and monitoring of DCPs in districts, with DCP managers providing specialist support. There has been little progress in achieving this, and a dearth of research exploring why. Using a case study of HIV programme monitoring and evaluation (M&E), this article explores whether South Africa's health system is configured to support administrative integration. The article draws on data from document reviews and interviews with 54 programme and district managers in two of nine provinces, exploring their respective roles in decision-making regarding HIV M&E system design and in using HIV data for monitoring uptake of HIV interventions in districts. Using Mintzberg's configurations framework, we describe three organizational parameters: (a) extent of centralization (whether district managers play a role in decisions regarding the design of the HIV M&E system); (b) key part of the organization (extent to which sub-national programme managers vs district managers play the central role in HIV monitoring in districts); and (c) coordination mechanisms used (whether highly formalized and rules-based or more output-based to promote agency). We find that the health system can be characterized as Mintzberg's machine bureaucracy. It is centralized and highly formalized with structures, management styles and practices that promote programme managers as lead role players in the monitoring of HIV interventions within districts. This undermines policy objectives of district managers assuming this leadership role. Our study enhances the understanding of organizational factors that may limit the success of administrative integration reforms and suggests interventions that may mitigate this. © The Author 2016. Published by Oxford University Press in association with The London School of Hygiene and Tropical Medicine. All rights reserved. For permissions, please e-mail: journals.permissions@oup.com.

  2. Project W-211, initial tank retrieval systems, retrieval control system software configuration management plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    RIECK, C.A.

    1999-02-23

    This Software Configuration Management Plan (SCMP) provides the instructions for change control of the W-211 Project, Retrieval Control System (RCS) software after initial approval/release but prior to the transfer of custody to the waste tank operations contractor. This plan applies to the W-211 system software developed by the project, consisting of the computer human-machine interface (HMI) and programmable logic controller (PLC) software source and executable code, for production use by the waste tank operations contractor. The plan encompasses that portion of the W-211 RCS software represented on project-specific AUTOCAD drawings that are released as part of the C1 definitive designmore » package (these drawings are identified on the drawing list associated with each C-1 package), and the associated software code. Implementation of the plan is required for formal acceptance testing and production release. The software configuration management plan does not apply to reports and data generated by the software except where specifically identified. Control of information produced by the software once it has been transferred for operation is the responsibility of the receiving organization.« less

  3. Policy environment for prevention, control and management of cardiovascular diseases in primary health care in Kenya.

    PubMed

    Asiki, Gershim; Shao, Shuai; Wainana, Carol; Khayeka-Wandabwa, Christopher; Haregu, Tilahun N; Juma, Pamela A; Mohammed, Shukri; Wambui, David; Gong, Enying; Yan, Lijing L; Kyobutungi, Catherine

    2018-05-09

    In Kenya, cardiovascular diseases (CVDs) accounted for more than 10% of total deaths and 4% of total Disability-Adjusted Life Years (DALYs) in 2015 with a steady increase over the past decade. The main objective of this paper was to review the existing policies and their content in relation to prevention, control and management of CVDs at primary health care (PHC) level in Kenya. A targeted document search in Google engine using keywords "Kenya national policy on cardiovascular diseases" and "Kenya national policy on non-communicable diseases (NCDs)" was conducted in addition to key informant interviews with Kenyan policy makers. Relevant regional and international policy documents were also included. The contents of documents identified were reviewed to assess how well they aligned with global health policies on CVD prevention, control and management. Thematic content analysis of the key informant interviews was also conducted to supplement the document reviews. A total of 17 documents were reviewed and three key informants interviewed. Besides the Tobacco Control Act (2007), all policy documents for CVD prevention, control and management were developed after 2013. The national policies were preceded by global initiatives and guidelines and were similar in content with the global policies. The Kenya health policy (2014-2030), The Kenya Health Sector Strategic and Investment Plan (2014-2018) and the Kenya National Strategy for the Prevention and Control of Non-communicable diseases (2015-2020) had strategies on NCDs including CVDs. Other policy documents for behavioral risk factors (The Tobacco Control Act 2007, Alcoholic Drinks Control (Licensing) Regulations (2010)) were available. The National Nutrition Action Plan (2012-2017) was available as a draft. Although Kenya has a tiered health care system comprising primary healthcare, integration of CVD prevention and control at PHC level was not explicitly mentioned in the policy documents. This review revealed important gaps in the policy environment for prevention, control and management of CVDs in PHC settings in Kenya. There is need to continuously engage the ministry of health and other sectors to prioritize inclusion of CVD services in PHC.

  4. Computer system design description for SY-101 hydrogen mitigation test project data acquisition and control system (DACS-1)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Ermi, A.M.

    1997-05-01

    Description of the Proposed Activity/REPORTABLE OCCURRENCE or PIAB: This ECN changes the computer systems design description support document describing the computers system used to control, monitor and archive the processes and outputs associated with the Hydrogen Mitigation Test Pump installed in SY-101. There is no new activity or procedure associated with the updating of this reference document. The updating of this computer system design description maintains an agreed upon documentation program initiated within the test program and carried into operations at time of turnover to maintain configuration control as outlined by design authority practicing guidelines. There are no new crediblemore » failure modes associated with the updating of information in a support description document. The failure analysis of each change was reviewed at the time of implementation of the Systems Change Request for all the processes changed. This document simply provides a history of implementation and current system status.« less

  5. SAGA: A project to automate the management of software production systems

    NASA Technical Reports Server (NTRS)

    Campbell, Roy H.; Beckman, Carol S.; Benzinger, Leonora; Beshers, George; Hammerslag, David; Kimball, John; Kirslis, Peter A.; Render, Hal; Richards, Paul; Terwilliger, Robert

    1985-01-01

    The SAGA system is a software environment that is designed to support most of the software development activities that occur in a software lifecycle. The system can be configured to support specific software development applications using given programming languages, tools, and methodologies. Meta-tools are provided to ease configuration. The SAGA system consists of a small number of software components that are adapted by the meta-tools into specific tools for use in the software development application. The modules are design so that the meta-tools can construct an environment which is both integrated and flexible. The SAGA project is documented in several papers which are presented.

  6. Actuator digital interface unit (AIU). [control units for space shuttle data system

    NASA Technical Reports Server (NTRS)

    1973-01-01

    Alternate versions of the actuator interface unit are presented. One alternate is a dual-failure immune configuration which feeds a look-and-switch dual-failure immune hydraulic system. The other alternate is a single-failure immune configuration which feeds a majority voting hydraulic system. Both systems communicate with the data bus through data terminals dedicated to each user subsystem. Both operational control data and configuration control information are processed in and out of the subsystem via the data terminal which yields the actuator interface subsystem, self-managing within its failure immunity capability.

  7. Earth Observatory Satellite system definition study. Report no. 3: Design/cost tradeoff studies. Appendix D: EOS configuration design data. Part 2: Data management system configuration

    NASA Technical Reports Server (NTRS)

    1974-01-01

    The Earth Observatory Satellite (EOS) data management system (DMS) is discussed. The DMS is composed of several subsystems or system elements which have basic purposes and are connected together so that the DMS can support the EOS program by providing the following: (1) payload data acquisition and recording, (2) data processing and product generation, (3) spacecraft and processing management and control, and (4) data user services. The configuration and purposes of the primary or high-data rate system and the secondary or local user system are explained. Diagrams of the systems are provided to support the systems analysis.

  8. Multipurpose Controller with EPICS integration and data logging: BPM application for ESS Bilbao

    NASA Astrophysics Data System (ADS)

    Arredondo, I.; del Campo, M.; Echevarria, P.; Jugo, J.; Etxebarria, V.

    2013-10-01

    This work presents a multipurpose configurable control system which can be integrated in an EPICS control network, this functionality being configured through a XML configuration file. The core of the system is the so-called Hardware Controller which is in charge of the control hardware management, the set up and communication with the EPICS network and the data storage. The reconfigurable nature of the controller is based on a single XML file, allowing any final user to easily modify and adjust the control system to any specific requirement. The selected Java development environment ensures a multiplatform operation and large versatility, even regarding the control hardware to be controlled. Specifically, this paper, focused on fast control based on a high performance FPGA, describes also an application approach for the ESS Bilbao's Beam Position Monitoring system. The implementation of the XML configuration file and the satisfactory performance outcome achieved are presented, as well as a general description of the Multipurpose Controller itself.

  9. Electrical, Electronic, and Electromechanical (EEE) parts management and control requirements for NASA space flight programs

    NASA Technical Reports Server (NTRS)

    1989-01-01

    This document establishes electrical, electronic, and electromechanical (EEE) parts management and control requirements for contractors providing and maintaining space flight and mission-essential or critical ground support equipment for NASA space flight programs. Although the text is worded 'the contractor shall,' the requirements are also to be used by NASA Headquarters and field installations for developing program/project parts management and control requirements for in-house and contracted efforts. This document places increased emphasis on parts programs to ensure that reliability and quality are considered through adequate consideration of the selection, control, and application of parts. It is the intent of this document to identify disciplines that can be implemented to obtain reliable parts which meet mission needs. The parts management and control requirements described in this document are to be selectively applied, based on equipment class and mission needs. Individual equipment needs should be evaluated to determine the extent to which each requirement should be implemented on a procurement. Utilization of this document does not preclude the usage of other documents. The entire process of developing and implementing requirements is referred to as 'tailoring' the program for a specific project. Some factors that should be considered in this tailoring process include program phase, equipment category and criticality, equipment complexity, and mission requirements. Parts management and control requirements advocated by this document directly support the concept of 'reliability by design' and are an integral part of system reliability and maintainability. Achieving the required availability and mission success objectives during operation depends on the attention given reliability and maintainability in the design phase. Consequently, it is intended that the requirements described in this document are consistent with those of NASA publications, 'Reliability Program Requirements for Aeronautical and Space System Contractors,' NHB 5300.4(1A-l); 'Maintainability Program Requirements for Space Systems,' NHB 5300.4(1E); and 'Quality Program Provisions for Aeronautical and Space System Contractors,' NHB 5300.4(1B).

  10. Ubiquitous CM and DM

    NASA Technical Reports Server (NTRS)

    Crowley, Sandra L.

    2000-01-01

    Ubiquitous is a real word. I thank a former Total Quality Coach for my first exposure some years ago to its existence. My version of Webster's dictionary defines ubiquitous as "present, or seeming to be present, everywhere at the same time; omnipresent." While I believe that God is omnipresent, I have come to discover that CM and DM are present everywhere. Oh, yes; I define CM as Configuration Management and DM as either Data or Document Management. Ten years ago, I had my first introduction to the CM world. I had an opportunity to do CM for the Space Station effort at the NASA Lewis Research Center. I learned that CM was a discipline that had four areas of focus: identification, control, status accounting, and verification. I was certified as a CMIl graduate and was indoctrinated about clear, concise, and valid. Off I went into a world of entirely new experiences. I was exposed to change requests and change boards first hand. I also learned about implementation of changes, and then of technical and CM requirements.

  11. A new flight control and management system architecture and configuration

    NASA Astrophysics Data System (ADS)

    Kong, Fan-e.; Chen, Zongji

    2006-11-01

    The advanced fighter should possess the performance such as super-sound cruising, stealth, agility, STOVL(Short Take-Off Vertical Landing),powerful communication and information processing. For this purpose, it is not enough only to improve the aerodynamic and propulsion system. More importantly, it is necessary to enhance the control system. A complete flight control system provides not only autopilot, auto-throttle and control augmentation, but also the given mission management. F-22 and JSF possess considerably outstanding flight control system on the basis of pave pillar and pave pace avionics architecture. But their control architecture is not enough integrated. The main purpose of this paper is to build a novel fighter control system architecture. The control system constructed on this architecture should be enough integrated, inexpensive, fault-tolerant, high safe, reliable and effective. And it will take charge of both the flight control and mission management. Starting from this purpose, this paper finishes the work as follows: First, based on the human nervous control, a three-leveled hierarchical control architecture is proposed. At the top of the architecture, decision level is in charge of decision-making works. In the middle, organization & coordination level will schedule resources, monitor the states of the fighter and switch the control modes etc. And the bottom is execution level which holds the concrete drive and measurement; then, according to their function and resources all the tasks involving flight control and mission management are sorted to individual level; at last, in order to validate the three-leveled architecture, a physical configuration is also showed. The configuration is distributed and applies some new advancement in information technology industry such line replaced module and cluster technology.

  12. FRACTAL Systems & Project suite: engineering tools for improving development and operation of the systems

    NASA Astrophysics Data System (ADS)

    Pérez-Calpena, A.; Mujica-Alvarez, E.; Osinde-Lopez, J.; García-Vargas, M.

    2008-07-01

    This paper describes the FRACTAL Systems & Projects suite. This suite is composed by several tools (GECO, DOCMA and SUMO) that provide the capabilities that all organizations need to store and manage the system information generated along the project's lifetime, from the design phase to the operation phase. The amount of information that is generated in a project keeps growing in size and complexity along the project's lifetime, to an extent that it becomes impossible to manage it without the aid of specific computer-based tools. The suite described in this paper is the solution developed by FRACTAL to assist the execution of different scientific projects, mainly related with telescopes and instruments, for astronomical research centres. These tools help the system and project engineers to maintain the technical control of the systems and to ensure an optimal use of the resources. GECO eases the control of the system configuration data; DOCMA provides the means to organise and manage the documents generated in the project; SUMO allows managing and scheduling the operation, the maintenance activities and the resources during the operational phase of a system. These tools improve the project communication making the information available to the authorized users (project team, customers, Consortium's members, etc). Finally and depending on the project needs, these three tools can be used integrated or in an independent manner.

  13. Assessing usage patterns of electronic clinical documentation templates.

    PubMed

    Vawdrey, David K

    2008-11-06

    Many vendors of electronic medical records support structured and free-text entry of clinical documents using configurable templates. At a healthcare institution comprising two large academic medical centers, a documentation management data mart and a custom, Web-accessible business intelligence application were developed to track the availability and usage of electronic documentation templates. For each medical center, template availability and usage trends were measured from November 2007 through February 2008. By February 2008, approximately 65,000 electronic notes were authored per week on the two campuses. One site had 934 available templates, with 313 being used to author at least one note. The other site had 765 templates, of which 480 were used. The most commonly used template at both campuses was a free text note called "Miscellaneous Nursing Note," which accounted for 33.3% of total documents generated at one campus and 15.2% at the other.

  14. An Air Force Guide to the System Specification.

    DTIC Science & Technology

    1981-01-01

    basis for sound management plans and decisions to initiate system full-scale development. Related topics include: current problems and questions...such current documents as AFR 800-2 and AFR 57-1. Key elements of coverage include the following: a. Levels of system engineering studies are...equipment and computer program elements of a system are acquired most directly acainst lower-level (configuration item) specifications. b. Current

  15. Neural networks for data mining electronic text collections

    NASA Astrophysics Data System (ADS)

    Walker, Nicholas; Truman, Gregory

    1997-04-01

    The use of neural networks in information retrieval and text analysis has primarily suffered from the issues of adequate document representation, the ability to scale to very large collections, dynamism in the face of new information and the practical difficulties of basing the design on the use of supervised training sets. Perhaps the most important approach to begin solving these problems is the use of `intermediate entities' which reduce the dimensionality of document representations and the size of documents collections to manageable levels coupled with the use of unsupervised neural network paradigms. This paper describes the issues, a fully configured neural network-based text analysis system--dataHARVEST--aimed at data mining text collections which begins this process, along with the remaining difficulties and potential ways forward.

  16. The centrality of meta-programming in the ES-DOC eco-system

    NASA Astrophysics Data System (ADS)

    Greenslade, Mark

    2017-04-01

    The Earth System Documentation (ES-DOC) project is an international effort aiming to deliver a robust earth system model inter-comparison project documentation infrastructure. Such infrastructure both simplifies & standardizes the process of documenting (in detail) projects, experiments, models, forcings & simulations. In support of CMIP6, ES-DOC has upgraded its eco-system of tools, web-services & web-sites. The upgrade consolidates the existing infrastructure (built for CMIP5) and extends it with the introduction of new capabilities. The strategic focus of the upgrade is improvements in the documentation experience and broadening the range of scientific use-cases that the archived documentation may help deliver. Whether it is highlighting dataset errors, exploring experimental protocols, comparing forcings across ensemble runs, understanding MIP objectives, reviewing citations, exploring component properties of configured models, visualising inter-model relationships, scientists involved in CMIP6 will find the ES-DOC infrastructure helpful. This presentation underlines the centrality of meta-programming within the ES-DOC eco-system. We will demonstrate how agility is greatly enhanced by taking a meta-programming approach to representing data models and controlled vocabularies. Such an approach nicely decouples representations from encodings. Meta-models will be presented along with the associated tooling chain that forward engineers artefacts as diverse as: class hierarchies, IPython notebooks, mindmaps, configuration files, OWL & SKOS documents, spreadsheets …etc.

  17. Closeout of CRADA JSA 2012S004: Chapter 5, Integrated Control System, of the document of the ESS Conceptual Design Report, publicly available at https://europeanspallationsource.se/accelerator-documents

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Satogata, Todd

    2013-04-22

    The integrated control system (ICS) is responsible for the whole ESS machine and facility: accelerator, target, neutron scattering instruments and conventional facilities. This unified approach keeps the costs of development, maintenance and support relatively low. ESS has selected a standardised, field-proven controls framework, the Experimental Physics and Industrial Control System (EPICS), which was originally developed jointly by Argonne and Los Alamos National Laboratories. Complementing this selection are best practices and experience from similar facilities regarding platform standardisation, control system development and device integration and commissioning. The components of ICS include the control system core, the control boxes, the BLED databasemore » management system, and the human machine interface. The control system core is a set of systems and tools that make it possible for the control system to provide required data, information and services to engineers, operators, physicists and the facility itself. The core components are the timing system that makes possible clock synchronisation across the facility, the machine protection system (MPS) and the personnel protection system (PPS) that prevent damage to the machine and personnel, and a set of control system services. Control boxes are servers that control a collection of equipment (for example a radio frequency cavity). The integrated control system will include many control boxes that can be assigned to one supplier, such as an internal team, a collaborating institute or a commercial vendor. This approach facilitates a clear division of responsibilities and makes integration much easier. A control box is composed of a standardised hardware platform, components, development tools and services. On the top level, it interfaces with the core control system components (timing, MPS, PPS) and with the human-machine interface. At the bottom, it interfaces with the equipment and parts of the facility through a set of analog and digital signals, real-time control loops and other communication buses. The ICS central data management system is named BLED (beam line element databases). BLED is a set of databases, tools and services that is used to store, manage and access data. It holds vital control system configuration and physics-related (lattice) information about the accelerator, target and instruments. It facilitates control system configuration by bringing together direct input-output controller (IOC) con guration and real-time data from proton and neutron beam line models. BLED also simplifies development and speeds up the code-test-debug cycle. The set of tools that access BLED will be tailored to the needs of different categories of users, such as ESS staff physicists, engineers, and operators; external partner laboratories; and visiting experimental instrument users. The human-machine interface is vital to providing a high-quality experience to ICS users. It encompasses a wide array of devices and software tools, from control room screens to engineer terminal windows; from beam physics data tools to post-mortem data analysis tools. It serves users with a wide range of skills from widely varied backgrounds. The Controls Group is developing a set of user profiles to accommodate this diverse range of use-cases and users.« less

  18. Graphical User Interface Development and Design to Support Airport Runway Configuration Management

    NASA Technical Reports Server (NTRS)

    Jones, Debra G.; Lenox, Michelle; Onal, Emrah; Latorella, Kara A.; Lohr, Gary W.; Le Vie, Lisa

    2015-01-01

    The objective of this effort was to develop a graphical user interface (GUI) for the National Aeronautics and Space Administration's (NASA) System Oriented Runway Management (SORM) decision support tool to support runway management. This tool is expected to be used by traffic flow managers and supervisors in the Airport Traffic Control Tower (ATCT) and Terminal Radar Approach Control (TRACON) facilities.

  19. Attitude control/momentum management and payload pointing in advanced space vehicles

    NASA Technical Reports Server (NTRS)

    Parlos, Alexander G.; Jayasuriya, Suhada

    1990-01-01

    The design and evaluation of an attitude control/momentum management system for highly asymmetric spacecraft configurations are presented. The preliminary development and application of a nonlinear control system design methodology for tracking control of uncertain systems, such as spacecraft payload pointing systems are also presented. Control issues relevant to both linear and nonlinear rigid-body spacecraft dynamics are addressed, whereas any structural flexibilities are not taken into consideration. Results from the first task indicate that certain commonly used simplifications in the equations of motions result in unstable attitude control systems, when used for highly asymmetric spacecraft configurations. An approach is suggested circumventing this problem. Additionally, even though preliminary results from the second task are encouraging, the proposed nonlinear control system design method requires further investigation prior to its application and use as an effective payload pointing system design technique.

  20. Computer-Aided Systems Engineering for Flight Research Projects Using a Workgroup Database

    NASA Technical Reports Server (NTRS)

    Mizukami, Masahi

    2004-01-01

    An online systems engineering tool for flight research projects has been developed through the use of a workgroup database. Capabilities are implemented for typical flight research systems engineering needs in document library, configuration control, hazard analysis, hardware database, requirements management, action item tracking, project team information, and technical performance metrics. Repetitive tasks are automated to reduce workload and errors. Current data and documents are instantly available online and can be worked on collaboratively. Existing forms and conventional processes are used, rather than inventing or changing processes to fit the tool. An integrated tool set offers advantages by automatically cross-referencing data, minimizing redundant data entry, and reducing the number of programs that must be learned. With a simplified approach, significant improvements are attained over existing capabilities for minimal cost. By using a workgroup-level database platform, personnel most directly involved in the project can develop, modify, and maintain the system, thereby saving time and money. As a pilot project, the system has been used to support an in-house flight experiment. Options are proposed for developing and deploying this type of tool on a more extensive basis.

  1. Router Agent Technology for Policy-Based Network Management

    NASA Technical Reports Server (NTRS)

    Chow, Edward T.; Sudhir, Gurusham; Chang, Hsin-Ping; James, Mark; Liu, Yih-Chiao J.; Chiang, Winston

    2011-01-01

    This innovation can be run as a standalone network application on any computer in a networked environment. This design can be configured to control one or more routers (one instance per router), and can also be configured to listen to a policy server over the network to receive new policies based on the policy- based network management technology. The Router Agent Technology transforms the received policies into suitable Access Control List syntax for the routers it is configured to control. It commits the newly generated access control lists to the routers and provides feedback regarding any errors that were faced. The innovation also automatically generates a time-stamped log file regarding all updates to the router it is configured to control. This technology, once installed on a local network computer and started, is autonomous because it has the capability to keep listening to new policies from the policy server, transforming those policies to router-compliant access lists, and committing those access lists to a specified interface on the specified router on the network with any error feedback regarding commitment process. The stand-alone application is named RouterAgent and is currently realized as a fully functional (version 1) implementation for the Windows operating system and for CISCO routers.

  2. Piloted simulation study of two tilt-wing flap control concepts, phase 2

    NASA Technical Reports Server (NTRS)

    Birckelbaw, Lourdes G.; Corliss, Lloyd D.; Hindson, William S.; Churchill, Gary B.

    1994-01-01

    A two phase piloted simulation study has been conducted in the Ames Vertical Motion Simulator to investigate alternative wing and flap controls for tilt-wing aircraft. This report documents the flying qualities results and findings of the second phase of the piloted simulation study and describes the simulated tilt-wing aircraft, the flap control concepts, the experiment design and the evaluation tasks. The initial phase of the study compared the flying qualities of both a conventional programmed flap and an innovative geared flap. The second phase of the study introduced an alternate method of pilot control for the geared flap and further studied the flying qualities of the programmed flap and two geared flap configurations. In general, the pilot ratings showed little variation between the programmed flap and the geared flap control concepts. Some differences between the two control concepts were noticed and are discussed in this report. The geared flap configurations had very similar results. Although the geared flap concept has the potential to reduce or eliminate the pitch control power requirements from a tail rotor or a tail thruster at low speeds and in hover, the results did not show reduced tail thruster pitch control power usage with the geared flap configurations compared to the programmed flap configuration. The addition of pitch attitude stabilization in the second phase of simulation study greatly enhanced the aircraft flying qualities compared to the first phase.

  3. Microprocessors: Laboratory Simulation of Industrial Control Applications.

    ERIC Educational Resources Information Center

    Gedeon, David V.

    1981-01-01

    Describes a course to make technical managers more aware of computer technology and how data loggers, programmable controllers, and larger computer systems interact in a hierarchical configuration of manufacturing process control. (SK)

  4. Reference H Cycle 3 Stability, Control, and Flying Qualities Batch Assessments

    NASA Technical Reports Server (NTRS)

    Henderson, Dennis K.

    1999-01-01

    This work is an update of the assessment completed in February of 1996, when a preliminary assessment report was issued for the Cycle 2B simulation model. The primary purpose of the final assessment was to re-evaluate each assessment against the flight control system (FCS) requirements document using the updated model. Only a limited number of final assessments were completed due to the close proximity of the release of the Langley model and the assessment deliverable date. The assessment used the nonlinear Cycle 3 simulation model because it combines nonlinear aeroelastic (quasi-static) aerodynamic with hinge moment and rate limited control surface deflections. Both Configuration Aerodynamics (Task 32) and Flight Controls (Task 36) were funded in 1996 to conduct the final stability and control assessments of the unaugmented Reference H configuration in FY96. Because the two tasks had similar output requirements, the work was divided such that Flight Controls would be responsible for the implementation and checkout of the simulation model and Configuration Aerodynamics for writing Madab "script' files, conducting the batch assessments and writing the assessment report. Additionally, Flight Controls was to investigate control surface allocations schemes different from the baseline Reference H in an effort to fulfill flying qualities criteria.

  5. An Air Force Guide to Computer Program Configuration Management

    DTIC Science & Technology

    1977-08-01

    Various other constraints may’also prevent full completion of the Part I specification for a complex missi-on CPCI in all of its typically massive detail...specifications for developmental CPCIs. Relations of documentation to actual computer program modules is often such as to prevent -ready identification and...names and organizational alignments of the contractor activities ;,.ay vary, but the functions should be represented. The prgram office CCB is the

  6. Using EPIC to Find Conflicts, Inconsistencies, and Gaps in Department of Defense Policies

    DTIC Science & Technology

    2013-01-01

    documentation; or deliver preliminary findings. All RAND reports un- dergo rigorous peer review to ensure that they meet high standards for research quality...responsibilities and the products that result from their execution. Once the high -level frame- work was defined, successive lower layers were developed to further...Lead or Chief Engineer Component Acquisition Executive ( CAE ) Managers Configuration Steering Board Materiel developer Contractor Milestone Decision

  7. PIMMS tools for capturing metadata about simulations

    NASA Astrophysics Data System (ADS)

    Pascoe, Charlotte; Devine, Gerard; Tourte, Gregory; Pascoe, Stephen; Lawrence, Bryan; Barjat, Hannah

    2013-04-01

    PIMMS (Portable Infrastructure for the Metafor Metadata System) provides a method for consistent and comprehensive documentation of modelling activities that enables the sharing of simulation data and model configuration information. The aim of PIMMS is to package the metadata infrastructure developed by Metafor for CMIP5 so that it can be used by climate modelling groups in UK Universities. PIMMS tools capture information about simulations from the design of experiments to the implementation of experiments via simulations that run models. PIMMS uses the Metafor methodology which consists of a Common Information Model (CIM), Controlled Vocabularies (CV) and software tools. PIMMS software tools provide for the creation and consumption of CIM content via a web services infrastructure and portal developed by the ES-DOC community. PIMMS metadata integrates with the ESGF data infrastructure via the mapping of vocabularies onto ESGF facets. There are three paradigms of PIMMS metadata collection: Model Intercomparision Projects (MIPs) where a standard set of questions is asked of all models which perform standard sets of experiments. Disciplinary level metadata collection where a standard set of questions is asked of all models but experiments are specified by users. Bespoke metadata creation where the users define questions about both models and experiments. Examples will be shown of how PIMMS has been configured to suit each of these three paradigms. In each case PIMMS allows users to provide additional metadata beyond that which is asked for in an initial deployment. The primary target for PIMMS is the UK climate modelling community where it is common practice to reuse model configurations from other researchers. This culture of collaboration exists in part because climate models are very complex with many variables that can be modified. Therefore it has become common practice to begin a series of experiments by using another climate model configuration as a starting point. Usually this other configuration is provided by a researcher in the same research group or by a previous collaborator with whom there is an existing scientific relationship. Some efforts have been made at the university department level to create documentation but there is a wide diversity in the scope and purpose of this information. The consistent and comprehensive documentation enabled by PIMMS will enable the wider sharing of climate model data and configuration information. The PIMMS methodology assumes an initial effort to document standard model configurations. Once these descriptions have been created users need only describe the specific way in which their model configuration is different from the standard. Thus the documentation burden on the user is specific to the experiment they are performing and fits easily into the workflow of doing their science. PIMMS metadata is independent of data and as such is ideally suited for documenting model development. PIMMS provides a framework for sharing information about failed model configurations for which data are not kept, the negative results that don't appear in scientific literature. PIMMS is a UK project funded by JISC, The University of Reading, The University of Bristol and STFC.

  8. Users guide: The LaRC human-operator-simulator-based pilot model

    NASA Technical Reports Server (NTRS)

    Bogart, E. H.; Waller, M. C.

    1985-01-01

    A Human Operator Simulator (HOS) based pilot model has been developed for use at NASA LaRC for analysis of flight management problems. The model is currently configured to simulate piloted flight of an advanced transport airplane. The generic HOS operator and machine model was originally developed under U.S. Navy sponsorship by Analytics, Inc. and through a contract with LaRC was configured to represent a pilot flying a transport airplane. A version of the HOS program runs in batch mode on LaRC's (60-bit-word) central computer system. This document provides a guide for using the program and describes in some detail the assortment of files used during its operation.

  9. Network configuration management : paving the way to network agility.

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Maestas, Joseph H.

    2007-08-01

    Sandia networks consist of nearly nine hundred routers and switches and nearly one million lines of command code, and each line ideally contributes to the capabilities of the network to convey information from one location to another. Sandia's Cyber Infrastructure Development and Deployment organizations recognize that it is therefore essential to standardize network configurations and enforce conformance to industry best business practices and documented internal configuration standards to provide a network that is agile, adaptable, and highly available. This is especially important in times of constrained budgets as members of the workforce are called upon to improve efficiency, effectiveness, andmore » customer focus. Best business practices recommend using the standardized configurations in the enforcement process so that when root cause analysis results in recommended configuration changes, subsequent configuration auditing will improve compliance to the standard. Ultimately, this minimizes mean time to repair, maintains the network security posture, improves network availability, and enables efficient transition to new technologies. Network standardization brings improved network agility, which in turn enables enterprise agility, because the network touches all facets of corporate business. Improved network agility improves the business enterprise as a whole.« less

  10. Low-G fluid behavior technology summaries

    NASA Technical Reports Server (NTRS)

    Stark, J. A.; Bradshaw, R. D.; Blatt, M. H.

    1974-01-01

    This report presents a summarization and categorization of the pertinent literature associated with low-g fluid behavior technology. Initially a literature search was conducted to obtain pertinent documents for review. Reports determined to be of primary significance are summarized in detail. Each summary, where applicable, consists of; (1) report identification, (2) objective(s) of the work, (3) description of pertinent work performed, (4) major results, and (5) comments of the reviewer (GD/C). Pertinent figures are presented on a single facing page separate from the text. Specific areas covered are; interface configuration, interface stability, natural frequency and damping, liquid reorientation, bubbles and droplets, fluid inflow, fluid outflow, convection, boiling and condensation heat transfer, venting effects, and fluid properties. Reports which were reviewed and not summarized, along with reasons for not summarizing, are also listed. Cryogenic thermal control and fluid management systems technology are presented.

  11. PAN AIR: A computer program for predicting subsonic or supersonic linear potential flows about arbitrary configurations using a higher order panel method. Volume 4: Maintenance document (version 3.0)

    NASA Technical Reports Server (NTRS)

    Purdon, David J.; Baruah, Pranab K.; Bussoletti, John E.; Epton, Michael A.; Massena, William A.; Nelson, Franklin D.; Tsurusaki, Kiyoharu

    1990-01-01

    The Maintenance Document Version 3.0 is a guide to the PAN AIR software system, a system which computes the subsonic or supersonic linear potential flow about a body of nearly arbitrary shape, using a higher order panel method. The document describes the overall system and each program module of the system. Sufficient detail is given for program maintenance, updating, and modification. It is assumed that the reader is familiar with programming and CRAY computer systems. The PAN AIR system was written in FORTRAN 4 language except for a few CAL language subroutines which exist in the PAN AIR library. Structured programming techniques were used to provide code documentation and maintainability. The operating systems accommodated are COS 1.11, COS 1.12, COS 1.13, and COS 1.14 on the CRAY 1S, 1M, and X-MP computing systems. The system is comprised of a data base management system, a program library, an execution control module, and nine separate FORTRAN technical modules. Each module calculates part of the posed PAN AIR problem. The data base manager is used to communicate between modules and within modules. The technical modules must be run in a prescribed fashion for each PAN AIR problem. In order to ease the problem of supplying the many JCL cards required to execute the modules, a set of CRAY procedures (PAPROCS) was created to automatically supply most of the JCL cards. Most of this document has not changed for Version 3.0. It now, however, strictly applies only to PAN AIR version 3.0. The major changes are: (1) additional sections covering the new FDP module (which calculates streamlines and offbody points); (2) a complete rewrite of the section on the MAG module; and (3) strict applicability to CRAY computing systems.

  12. Analysis, testing, and evaluation of faulted and unfaulted Wye, Delta, and open Delta connected electromechanical actuators

    NASA Technical Reports Server (NTRS)

    Nehl, T. W.; Demerdash, N. A.

    1983-01-01

    Mathematical models capable of simulating the transient, steady state, and faulted performance characteristics of various brushless dc machine-PSA (power switching assembly) configurations were developed. These systems are intended for possible future use as primemovers in EMAs (electromechanical actuators) for flight control applications. These machine-PSA configurations include wye, delta, and open-delta connected systems. The research performed under this contract was initially broken down into the following six tasks: development of mathematical models for various machine-PSA configurations; experimental validation of the model for failure modes; experimental validation of the mathematical model for shorted turn-failure modes; tradeoff study; and documentation of results and methodology.

  13. STORMWATER BEST MANAGEMENT PRACTICES DESIGN GUIDE VOLUME 2 - VEGETATIVE BIOFILTERS

    EPA Science Inventory

    This document is Volume 2 of a three volume document that provides guidance on the selection and design of stormwater management Best Management Practices (BMPs). This second volume provides specific design guidance for a group of onsite BMP control practices that are referred t...

  14. Improving documentation of a beta-blocker quality measure through an anesthesia information management system and real-time notification of documentation errors.

    PubMed

    Nair, Bala G; Peterson, Gene N; Newman, Shu-Fang; Wu, Wei-Ying; Kolios-Morris, Vickie; Schwid, Howard A

    2012-06-01

    Continuation of perioperative beta-blockers for surgical patients who are receiving beta-blockers prior to arrival for surgery is an important quality measure (SCIP-Card-2). For this measure to be considered successful, name, date, and time of the perioperative beta-blocker must be documented. Alternately, if the beta-blocker is not given, the medical reason for not administering must be documented. Before the study was conducted, the institution lacked a highly reliable process to document the date and time of self-administration of beta-blockers prior to hospital admission. Because of this, compliance with the beta-blocker quality measure was poor (-65%). To improve this measure, the anesthesia care team was made responsible for documenting perioperative beta-blockade. Clear documentation guidelines were outlined, and an electronic Anesthesia Information Management System (AIMS) was configured to facilitate complete documentation of the beta-blocker quality measure. In addition, real-time electronic alerts were generated using Smart Anesthesia Messenger (SAM), an internally developed decision-support system, to notify users concerning incomplete beta-blocker documentation. Weekly compliance for perioperative beta-blocker documentation before the study was 65.8 +/- 16.6%, which served as the baseline value. When the anesthesia care team started documenting perioperative beta-blocker in AIMS, compliance was 60.5 +/- 8.6% (p = .677 as compared with baseline). Electronic alerts with SAM improved documentation compliance to 94.6 +/- 3.5% (p < .001 as compared with baseline). To achieve high compliance for the beta-blocker measure, it is essential to (1) clearly assign a medical team to perform beta-blocker documentation and (2) enhance features in the electronic medical systems to alert the user concerning incomplete documentation.

  15. Advanced human-machine interface for collaborative building control

    DOEpatents

    Zheng, Xianjun S.; Song, Zhen; Chen, Yanzi; Zhang, Shaopeng; Lu, Yan

    2015-08-11

    A system for collaborative energy management and control in a building, including an energy management controller, one or more occupant HMIs that supports two-way communication between building occupants and a facility manager, and between building occupants and the energy management controller, and a facility manager HMI that supports two-way communication between the facility manager and the building occupants, and between the facility manager and the energy management controller, in which the occupant HMI allows building occupants to provide temperature preferences to the facility manager and the energy management controller, and the facility manager HMI allows the facility manager to configure an energy policy for the building as a set of rules and to view occupants' aggregated temperature preferences, and the energy management controller determines an optimum temperature range that resolves conflicting occupant temperature preferences and occupant temperature preferences that conflict with the facility manager's energy policy for the building.

  16. Computer software configuration description, 241-AY and 241 AZ tank farm MICON automation system

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Winkelman, W.D.

    This document describes the configuration process, choices and conventions used during the Micon DCS configuration activities, and issues involved in making changes to the configuration. Includes the master listings of the Tag definitions, which should be revised to authorize any changes. Revision 3 provides additional information on the software used to provide communications with the W-320 project and incorporates minor changes to ensure the document alarm setpoint priorities correctly match operational expectations.

  17. Earth Observing System (EOS)/Advanced Microwave Sounding Unit A (AMSU-A) configuration management plan

    NASA Technical Reports Server (NTRS)

    Cavanaugh, J.

    1994-01-01

    This plan describes methods and procedures Aerojet will follow in the implementation of configuration control for each established baseline. The plan is written in response to the GSFC EOS CM Plan 420-02-02, dated January 1990, and also meets he requirements specified in DOD-STD-480, DOD-D 1000B, MIL-STD-483A, and MIL-STD-490B. The plan establishes the configuration management process to be used for the deliverable hardware, software, and firmware of the EOS/AMSU-A during development, design, fabrication, test, and delivery. This revision includes minor updates to reflect Aerojet's CM policies.

  18. Development of an integrated configuration management/flight director system for piloted STOL approaches

    NASA Technical Reports Server (NTRS)

    Hoh, R. H.; Klein, R. H.; Johnson, W. A.

    1977-01-01

    A system analysis method for the development of an integrated configuration management/flight director system for IFR STOL approaches is presented. Curved descending decelerating approach trajectories are considered. Considerable emphasis is placed on satisfying the pilot centered requirements (acceptable workload) as well as the usual guidance and control requirements (acceptable performance). The Augmentor Wing Jet STOL Research Aircraft was utilized to allow illustration by example, and to validate the analysis procedure via manned simulation.

  19. Structural Acoustic Prediction and Interior Noise Control Technology

    NASA Technical Reports Server (NTRS)

    Mathur, G. P.; Chin, C. L.; Simpson, M. A.; Lee, J. T.; Palumbo, Daniel L. (Technical Monitor)

    2001-01-01

    This report documents the results of Task 14, "Structural Acoustic Prediction and Interior Noise Control Technology". The task was to evaluate the performance of tuned foam elements (termed Smart Foam) both analytically and experimentally. Results taken from a three-dimensional finite element model of an active, tuned foam element are presented. Measurements of sound absorption and sound transmission loss were taken using the model. These results agree well with published data. Experimental performance data were taken in Boeing's Interior Noise Test Facility where 12 smart foam elements were applied to a 757 sidewall. Several configurations were tested. Noise reductions of 5-10 dB were achieved over the 200-800 Hz bandwidth of the controller. Accelerometers mounted on the panel provided a good reference for the controller. Configurations with far-field error microphones outperformed near-field cases.

  20. Fluid management in the optimization of space construction

    NASA Technical Reports Server (NTRS)

    Snyder, Howard

    1990-01-01

    Fluid management impacts strongly on the optimization of space construction. Large quantities of liquids are needed for propellants and life support. The mass of propellant liquids is comparable to that required for the structures. There may be a strong dynamic interaction between the stored liquids and the space structure unless the design minimizes the interaction. The constraints of cost and time required optimization of the supply/resupply strategy. The proper selection and design of the fluid management methods for: slosh control; stratification control; acquisition; transfer; gauging; venting; dumping; contamination control; selection of tank configuration and size; the storage state and the control system can improve the entire system performance substantially. Our effort consists of building mathematical/computer models of the various fluid management methods and testing them against the available experimental data. The results of the models are used as inputs to the system operations studies. During the past year, the emphasis has been on modeling: the transfer of cryogens; sloshing and the storage configuration. The work has been intermeshed with ongoing NASA design and development studies to leverage the funds provided by the Center.

  1. Postirradiation Testing Laboratory (327 Building)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kammenzind, D.E.

    A Standards/Requirements Identification Document (S/RID) is the total list of the Environment, Safety and Health (ES and H) requirements to be implemented by a site, facility, or activity. These requirements are appropriate to the life cycle phase to achieve an adequate level of protection for worker and public health and safety, and the environment during design, construction, operation, decontamination and decommissioning, and environmental restoration. S/RlDs are living documents, to be revised appropriately based on change in the site`s or facility`s mission or configuration, a change in the facility`s life cycle phase, or a change to the applicable standards/requirements. S/RIDs encompassmore » health and safety, environmental, and safety related safeguards and security (S and S) standards/requirements related to the functional areas listed in the US Department of Energy (DOE) Environment, Safety and Health Configuration Guide. The Fluor Daniel Hanford (FDH) Contract S/RID contains standards/requirements, applicable to FDH and FDH subcontractors, necessary for safe operation of Project Hanford Management Contract (PHMC) facilities, that are not the direct responsibility of the facility manager (e.g., a site-wide fire department). Facility S/RIDs contain standards/requirements applicable to a specific facility that are the direct responsibility of the facility manager. S/RlDs are prepared by those responsible for managing the operation of facilities or the conduct of activities that present a potential threat to the health and safety of workers, public, or the environment, including: Hazard Category 1 and 2 nuclear facilities and activities, as defined in DOE 5480.23. Selected Hazard Category 3 nuclear, and Low Hazard non-nuclear facilities and activities, as agreed upon by RL. The Postirradiation Testing Laboratory (PTL) S/RID contains standards/ requirements that are necessary for safe operation of the PTL facility, and other building/areas that are the direct responsibility of the specific facility manager. The specific DOE Orders, regulations, industry codes/standards, guidance documents and good industry practices that serve as the basis for each element/subelement are identified and aligned with each subelement.« less

  2. Trajectory-Oriented Approach to Managing Traffic Complexity: Operational Concept and Preliminary Metrics Definition

    NASA Technical Reports Server (NTRS)

    Idris, Husni; Vivona, Robert; Garcia-Chico, Jose L.

    2008-01-01

    This document describes preliminary research on a distributed, trajectory-oriented approach for traffic complexity management. The approach is to manage traffic complexity in a distributed control environment, based on preserving trajectory flexibility and minimizing constraints. In particular, the document presents an analytical framework to study trajectory flexibility and the impact of trajectory constraints on it. The document proposes preliminary flexibility metrics that can be interpreted and measured within the framework.

  3. On I/O Virtualization Management

    NASA Astrophysics Data System (ADS)

    Danciu, Vitalian A.; Metzker, Martin G.

    The quick adoption of virtualization technology in general and the advent of the Cloud business model entail new requirements on the structure and the configuration of back-end I/O systems. Several approaches to virtualization of I/O links are being introduced, which aim at implementing a more flexible I/O channel configuration without compromising performance. While previously the management of I/O devices could be limited to basic technical requirments (e.g. the establishment and termination of fixed-point links), the additional flexibility carries in its wake additional management requirements on the representation and control of I/O sub-systems.

  4. Medication order communication using fax and document-imaging technologies.

    PubMed

    Simonian, Armen I

    2008-03-15

    The implementation of fax and document-imaging technology to electronically communicate medication orders from nursing stations to the pharmacy is described. The evaluation of a commercially available pharmacy order imaging system to improve order communication and to make document retrieval more efficient led to the selection and customization of a system already licensed and used in seven affiliated hospitals. The system consisted of existing fax machines and document-imaging software that would capture images of written orders and send them from nursing stations to a central database server. Pharmacists would then retrieve the images and enter the orders in an electronic medical record system. The pharmacy representatives from all seven hospitals agreed on the configuration and functionality of the custom application. A 30-day trial of the order imaging system was successfully conducted at one of the larger institutions. The new system was then implemented at the remaining six hospitals over a period of 60 days. The transition from a paper-order system to electronic communication via a standardized pharmacy document management application tailored to the specific needs of this health system was accomplished. A health system with seven affiliated hospitals successfully implemented electronic communication and the management of inpatient paper-chart orders by using faxes and document-imaging technology. This standardized application eliminated the problems associated with the hand delivery of paper orders, the use of the pneumatic tube system, and the printing of traditional faxes.

  5. Engineering and Design: Control Stations and Control Systems for Navigation Locks and Dams

    DTIC Science & Technology

    1997-05-30

    of human intelli- hypothetical lock and dam configurations. Finally, b. Terminology. (1) PLC system. The computer- based systems utilize special...electrical industry for industrial use. There- fore, for purposes of this document, a computer- based system is referred to as a PLC system. (2) Relay- based ...be custom made, because most of today’s control systems of any complexity are PLC - based , the standard size of a given motor starter cubicle is not

  6. mREST Interface Specification

    NASA Technical Reports Server (NTRS)

    McCartney, Patrick; MacLean, John

    2012-01-01

    mREST is an implementation of the REST architecture specific to the management and sharing of data in a system of logical elements. The purpose of this document is to clearly define the mREST interface protocol. The interface protocol covers all of the interaction between mREST clients and mREST servers. System-level requirements are not specifically addressed. In an mREST system, there are typically some backend interfaces between a Logical System Element (LSE) and the associated hardware/software system. For example, a network camera LSE would have a backend interface to the camera itself. These interfaces are specific to each type of LSE and are not covered in this document. There are also frontend interfaces that may exist in certain mREST manager applications. For example, an electronic procedure execution application may have a specialized interface for configuring the procedures. This interface would be application specific and outside of this document scope. mREST is intended to be a generic protocol which can be used in a wide variety of applications. A few scenarios are discussed to provide additional clarity but, in general, application-specific implementations of mREST are not specifically addressed. In short, this document is intended to provide all of the information necessary for an application developer to create mREST interface agents. This includes both mREST clients (mREST manager applications) and mREST servers (logical system elements, or LSEs).

  7. Disease and disaster: Optimal deployment of epidemic control facilities in a spatially heterogeneous population with changing behaviour.

    PubMed

    Gaythorpe, Katy; Adams, Ben

    2016-05-21

    Epidemics of water-borne infections often follow natural disasters and extreme weather events that disrupt water management processes. The impact of such epidemics may be reduced by deployment of transmission control facilities such as clinics or decontamination plants. Here we use a relatively simple mathematical model to examine how demographic and environmental heterogeneities, population behaviour, and behavioural change in response to the provision of facilities, combine to determine the optimal configurations of limited numbers of facilities to reduce epidemic size, and endemic prevalence. We show that, if the presence of control facilities does not affect behaviour, a good general rule for responsive deployment to minimise epidemic size is to place them in exactly the locations where they will directly benefit the most people. However, if infected people change their behaviour to seek out treatment then the deployment of facilities offering treatment can lead to complex effects that are difficult to foresee. So careful mathematical analysis is the only way to get a handle on the optimal deployment. Behavioural changes in response to control facilities can also lead to critical facility numbers at which there is a radical change in the optimal configuration. So sequential improvement of a control strategy by adding facilities to an existing optimal configuration does not always produce another optimal configuration. We also show that the pre-emptive deployment of control facilities has conflicting effects. The configurations that minimise endemic prevalence are very different to those that minimise epidemic size. So cost-benefit analysis of strategies to manage endemic prevalence must factor in the frequency of extreme weather events and natural disasters. Copyright © 2016 Elsevier Ltd. All rights reserved.

  8. Civilian Radioactive Waste Management System Requirements Document

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    C.A. Kouts

    2006-05-10

    The CRD addresses the requirements of Department of Energy (DOE) Order 413.3-Change 1, ''Program and Project Management for the Acquisition of Capital Assets'', by providing the Secretarial Acquisition Executive (Level 0) scope baseline and the Program-level (Level 1) technical baseline. The Secretarial Acquisition Executive approves the Office of Civilian Radioactive Waste Management's (OCRWM) critical decisions and changes against the Level 0 baseline; and in turn, the OCRWM Director approves all changes against the Level 1 baseline. This baseline establishes the top-level technical scope of the CRMWS and its three system elements, as described in section 1.3.2. The organizations responsible formore » design, development, and operation of system elements described in this document must therefore prepare subordinate project-level documents that are consistent with the CRD. Changes to requirements will be managed in accordance with established change and configuration control procedures. The CRD establishes requirements for the design, development, and operation of the CRWMS. It specifically addresses the top-level governing laws and regulations (e.g., ''Nuclear Waste Policy Act'' (NWPA), 10 Code of Federal Regulations (CFR) Part 63, 10 CFR Part 71, etc.) along with specific policy, performance requirements, interface requirements, and system architecture. The CRD shall be used as a vehicle to incorporate specific changes in technical scope or performance requirements that may have significant program implications. Such may include changes to the program mission, changes to operational capability, and high visibility stakeholder issues. The CRD uses a systems approach to: (1) identify key functions that the CRWMS must perform, (2) allocate top-level requirements derived from statutory, regulatory, and programmatic sources, and (3) define the basic elements of the system architecture and operational concept. Project-level documents address CRD requirements by further defining system element functions, decomposing requirements into significantly greater detail, and developing designs of system components, facilities, and equipment. The CRD addresses the identification and control of functional, physical, and operational boundaries between and within CRWMS elements. The CRD establishes requirements regarding key interfaces between the CRWMS and elements external to the CRWMS. Project elements define interfaces between CRWMS program elements. The Program has developed a change management process consistent with DOE Order 413.3-Change 1. Changes to the Secretarial Acquisition Executive and Program-level baselines must be approved by a Program Baseline Change Control Board. Specific thresholds have been established for identifying technical, cost, and schedule changes that require approval. The CRWMS continually evaluates system design and operational concepts to optimize performance and/or cost. The Program has developed systems analysis tools to assess potential enhancements to the physical system and to determine the impacts from cost saving initiatives, scientific and technological improvements, and engineering developments. The results of systems analyses, if appropriate, are factored into revisions to the CRD as revised Programmatic Requirements.« less

  9. Initial development of the DIII–D snowflake divertor control

    NASA Astrophysics Data System (ADS)

    Kolemen, E.; Vail, P. J.; Makowski, M. A.; Allen, S. L.; Bray, B. D.; Fenstermacher, M. E.; Humphreys, D. A.; Hyatt, A. W.; Lasnier, C. J.; Leonard, A. W.; McLean, A. G.; Maingi, R.; Nazikian, R.; Petrie, T. W.; Soukhanovskii, V. A.; Unterberg, E. A.

    2018-06-01

    Simultaneous control of two proximate magnetic field nulls in the divertor region is demonstrated on DIII–D to enable plasma operations in an advanced magnetic configuration known as the snowflake divertor (SFD). The SFD is characterized by a second-order poloidal field null, created by merging two first-order nulls of the standard divertor configuration. The snowflake configuration has many magnetic properties, such as high poloidal flux expansion, large plasma-wetted area, and additional strike points, that are advantageous for divertor heat flux management in future fusion reactors. However, the magnetic configuration of the SFD is highly-sensitive to changes in currents within the plasma and external coils and therefore requires complex magnetic control. The first real-time snowflake detection and control system on DIII–D has been implemented in order to stabilize the configuration. The control algorithm calculates the position of the two nulls in real-time by locally-expanding the Grad–Shafranov equation in the divertor region. A linear relation between variations in the poloidal field coil currents and changes in the null locations is then analytically derived. This formulation allows for simultaneous control of multiple coils to achieve a desired SFD configuration. It is shown that the control enabled various snowflake configurations on DIII–D in scenarios such as the double-null advanced tokamak. The SFD resulted in a 2.5×  reduction in the peak heat flux for many energy confinement times (2–3 s) without any adverse effects on core plasma performance.

  10. Relation between facial affect recognition and configural face processing in antipsychotic-free schizophrenia.

    PubMed

    Fakra, Eric; Jouve, Elisabeth; Guillaume, Fabrice; Azorin, Jean-Michel; Blin, Olivier

    2015-03-01

    Deficit in facial affect recognition is a well-documented impairment in schizophrenia, closely connected to social outcome. This deficit could be related to psychopathology, but also to a broader dysfunction in processing facial information. In addition, patients with schizophrenia inadequately use configural information-a type of processing that relies on spatial relationships between facial features. To date, no study has specifically examined the link between symptoms and misuse of configural information in the deficit in facial affect recognition. Unmedicated schizophrenia patients (n = 30) and matched healthy controls (n = 30) performed a facial affect recognition task and a face inversion task, which tests aptitude to rely on configural information. In patients, regressions were carried out between facial affect recognition, symptom dimensions and inversion effect. Patients, compared with controls, showed a deficit in facial affect recognition and a lower inversion effect. Negative symptoms and lower inversion effect could account for 41.2% of the variance in facial affect recognition. This study confirms the presence of a deficit in facial affect recognition, and also of dysfunctional manipulation in configural information in antipsychotic-free patients. Negative symptoms and poor processing of configural information explained a substantial part of the deficient recognition of facial affect. We speculate that this deficit may be caused by several factors, among which independently stand psychopathology and failure in correctly manipulating configural information. PsycINFO Database Record (c) 2015 APA, all rights reserved.

  11. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Chen, K.; Tsai, H.; Decision and Information Sciences

    The technical basis for extending the Model 9977 shipping package periodic maintenance beyond the one-year interval to a maximum of five years is based on the performance of the O-ring seals and the environmental conditions. The DOE Packaging Certification Program (PCP) has tasked Argonne National Laboratory to develop a Radio-Frequency Identification (RFID) temperature monitoring system for use by the facility personnel at DAF/NTS. The RFID temperature monitoring system, depicted in the figure below, consists of the Mk-1 RFId tags, a reader, and a control computer mounted on a mobile platform that can operate as a stand-alone system, or it canmore » be connected to the local IT network. As part of the Conditions of Approval of the CoC, the user must complete the prescribed training to become qualified and be certified for operation of the RFID temperature monitoring system. The training course will be administered by Argonne National Laboratory on behalf of the Headquarters Certifying Official. This is a complete documentation package for the RFID temperature monitoring system of the Model 9977 packagings at NTS. The documentation package will be used for training and certification. The table of contents are: Acceptance Testing Procedure of MK-1 RFID Tags for DOE/EM Nuclear Materials Management Applications; Acceptance Testing Result of MK-1 RFID Tags for DOE/EM Nuclear Materials Management Applications; Performance Test of the Single Bolt Seal Sensor for the Model 9977 Packaging; Calibration of Built-in Thermistors in RFID Tags for Nevada Test Site; Results of Calibration of Built-in Thermistors in RFID Tags; Results of Thermal Calibration of Second Batch of MK-I RFID Tags; Procedure for Installing and Removing MK-1 RFID Tag on Model 9977 Drum; User Guide for RFID Reader and Software for Temperature Monitoring of Model 9977 Drums at NTS; Software Quality Assurance Plan (SQAP) for the ARG-US System; Quality Category for the RFID Temperature Monitoring System; The Documentation Package for the RFID Temperature Monitoring System; Software Test Plan and Results for ARG-US OnSite; Configuration Management Plan (CMP) for the ARG-US System; Requirements Management Plan for the ARG-US System; and Design Management Plan for ARG-US.« less

  12. Moisture Control Guidance for Commercial and Public Buildings (EPA 402-F-13053)

    EPA Science Inventory

    This document provides guidance to designers, construction mangers, and building operation/maintenance managers to improve IEQ and reduce risks of encountering IEQ problems due to insufficient moisture control. EPA will be producing a document entitled "Moisture Control Guida...

  13. Network Operations Support Plan for the Spot 2 mission (revision 1)

    NASA Technical Reports Server (NTRS)

    Werbitzky, Victor

    1989-01-01

    The purpose of this Network Operations Support Plan (NOSP) is to indicate operational procedures and ground equipment configurations for the SPOT 2 mission. The provisions in this document take precedence over procedures or configurations in other documents.

  14. Moisture Control Guidance for Commercial and Public ...

    EPA Pesticide Factsheets

    This document provides guidance to designers, construction mangers, and building operation/maintenance managers to improve IEQ and reduce risks of encountering IEQ problems due to insufficient moisture control. EPA will be producing a document entitled

  15. Digital data processing system dynamic loading analysis

    NASA Technical Reports Server (NTRS)

    Lagas, J. J.; Peterka, J. J.; Tucker, A. E.

    1976-01-01

    Simulation and analysis of the Space Shuttle Orbiter Digital Data Processing System (DDPS) are reported. The mated flight and postseparation flight phases of the space shuttle's approach and landing test configuration were modeled utilizing the Information Management System Interpretative Model (IMSIM) in a computerized simulation modeling of the ALT hardware, software, and workload. System requirements simulated for the ALT configuration were defined. Sensitivity analyses determined areas of potential data flow problems in DDPS operation. Based on the defined system requirements and the sensitivity analyses, a test design is described for adapting, parameterizing, and executing the IMSIM. Varying load and stress conditions for the model execution are given. The analyses of the computer simulation runs were documented as results, conclusions, and recommendations for DDPS improvements.

  16. Space shuttle orbiter digital data processing system timing sensitivity analysis OFT ascent phase

    NASA Technical Reports Server (NTRS)

    Lagas, J. J.; Peterka, J. J.; Becker, D. A.

    1977-01-01

    Dynamic loads were investigated to provide simulation and analysis of the space shuttle orbiter digital data processing system (DDPS). Segments of the ascent test (OFT) configuration were modeled utilizing the information management system interpretive model (IMSIM) in a computerized simulation modeling of the OFT hardware and software workload. System requirements for simulation of the OFT configuration were defined, and sensitivity analyses determined areas of potential data flow problems in DDPS operation. Based on the defined system requirements and these sensitivity analyses, a test design was developed for adapting, parameterizing, and executing IMSIM, using varying load and stress conditions for model execution. Analyses of the computer simulation runs are documented, including results, conclusions, and recommendations for DDPS improvements.

  17. MarFS-Requirements-Design-Configuration-Admin

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kettering, Brett Michael; Grider, Gary Alan

    This document will be organized into sections that are defined by the requirements for a file system that presents a near-POSIX (Portable Operating System Interface) interface to the user, but whose data is stored in whatever form is most efficient for the type of data being stored. After defining the requirement the design for meeting the requirement will be explained. Finally there will be sections on configuring and administering this file system. More and more, data dominates the computing world. There is a “sea” of data out there in many different formats that needs to be managed and used. “Mar”more » means “sea” in Spanish. Thus, this product is dubbed MarFS, a file system for a sea of data.« less

  18. Management evolution in the LSST project

    NASA Astrophysics Data System (ADS)

    Sweeney, Donald; Claver, Charles; Jacoby, Suzanne; Kantor, Jeffrey; Krabbendam, Victor; Kurita, Nadine

    2010-07-01

    The Large Synoptic Survey Telescope (LSST) project has evolved from just a few staff members in 2003 to about 100 in 2010; the affiliation of four founding institutions has grown to 32 universities, government laboratories, and industry. The public private collaboration aims to complete the estimated $450 M observatory in the 2017 timeframe. During the design phase of the project from 2003 to the present the management structure has been remarkably stable. At the same time, the funding levels, staffing levels and scientific community participation have grown dramatically. The LSSTC has introduced project controls and tools required to manage the LSST's complex funding model, technical structure and distributed work force. Project controls have been configured to comply with the requirements of federal funding agencies. Some of these tools for risk management, configuration control and resource-loaded schedule have been effective and others have not. Technical tasks associated with building the LSST are distributed into three subsystems: Telescope & Site, Camera, and Data Management. Each sub-system has its own experienced Project Manager and System Scientist. Delegation of authority is enabling and effective; it encourages a strong sense of ownership within the project. At the project level, subsystem management follows the principle that there is one Board of Directors, Director, and Project Manager who have overall authority.

  19. 78 FR 52808 - Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-08-26

    ... access to customers or other persons, to implement risk management controls and supervisory procedures... requires brokers or dealers to establish, document, and maintain certain risk management controls and... of its risk management controls as part of its books and records in a manner consistent with Rule 17a...

  20. Noise levels from a model turbofan engine with simulated noise control measures applied

    NASA Technical Reports Server (NTRS)

    Hall, David G.; Woodward, Richard P.

    1993-01-01

    A study of estimated full-scale noise levels based on measured levels from the Advanced Ducted Propeller (ADP) sub-scale model is presented. Testing of this model was performed in the NASA Lewis Low Speed Anechoic Wind Tunnel at a simulated takeoff condition of Mach 0.2. Effective Perceived Noise Level (EPNL) estimates for the baseline configuration are documented, and also used as the control case in a study of the potential benefits of two categories of noise control. The effect of active noise control is evaluated by artificially removing various rotor-stator interaction tones. Passive noise control is simulated by applying a notch filter to the wind tunnel data. Cases with both techniques are included to evaluate hybrid active-passive noise control. The results for EPNL values are approximate because the original source data was limited in bandwidth and in sideline angular coverage. The main emphasis is on comparisons between the baseline and configurations with simulated noise control measures.

  1. Configuration and Data Management Process and the System Safety Professional

    NASA Technical Reports Server (NTRS)

    Shivers, Charles Herbert; Parker, Nelson C. (Technical Monitor)

    2001-01-01

    This article presents a discussion of the configuration management (CM) and the Data Management (DM) functions and provides a perspective of the importance of configuration and data management processes to the success of system safety activities. The article addresses the basic requirements of configuration and data management generally based on NASA configuration and data management policies and practices, although the concepts are likely to represent processes of any public or private organization's well-designed configuration and data management program.

  2. Correcting Blindness In the Nerve Center: How To Improve Situational Awareness

    DTIC Science & Technology

    2015-12-01

    Civil Defence Emergency Management released the Response Management, Director’s Guideline for CDEM Group and Local Controllers document in October...Defence & Emergency Management, Response Management: Director’s Guideline for CDEM Group and Local Controllers (Wellington, New Zealand: Ministry of...Response Management: Director’s Guideline for CDEM Group and Local Controllers . Wellington, New Zealand: Ministry of Civil Defence & Emergency

  3. Design and Implementation of the CEBAF Element Database

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Theodore Larrieu, Christopher Slominski, Michele Joyce

    2011-10-01

    With inauguration of the CEBAF Element Database (CED) in Fall 2010, Jefferson Lab computer scientists have taken a first step toward the eventual goal of a model-driven accelerator. Once fully populated, the database will be the primary repository of information used for everything from generating lattice decks to booting front-end computers to building controls screens. A particular requirement influencing the CED design is that it must provide consistent access to not only present, but also future, and eventually past, configurations of the CEBAF accelerator. To accomplish this, an introspective database schema was designed that allows new elements, element types, andmore » element properties to be defined on-the-fly without changing table structure. When used in conjunction with the Oracle Workspace Manager, it allows users to seamlessly query data from any time in the database history with the exact same tools as they use for querying the present configuration. Users can also check-out workspaces and use them as staging areas for upcoming machine configurations. All Access to the CED is through a well-documented API that is translated automatically from original C++ into native libraries for script languages such as perl, php, and TCL making access to the CED easy and ubiquitous. Notice: Authored by Jefferson Science Associates, LLC under U.S. DOE Contract No. DE-AC05-06OR23177. The U.S. Government retains a non-exclusive, paid-up, irrevocable, world-wide license to publish or reproduce this manuscript for U.S. Government purposes.« less

  4. Configuration Analysis Tool (CAT). System Description and users guide (revision 1)

    NASA Technical Reports Server (NTRS)

    Decker, W.; Taylor, W.; Mcgarry, F. E.; Merwarth, P.

    1982-01-01

    A system description of, and user's guide for, the Configuration Analysis Tool (CAT) are presented. As a configuration management tool, CAT enhances the control of large software systems by providing a repository for information describing the current status of a project. CAT provides an editing capability to update the information and a reporting capability to present the information. CAT is an interactive program available in versions for the PDP-11/70 and VAX-11/780 computers.

  5. Context based configuration management system

    NASA Technical Reports Server (NTRS)

    Gurram, Mohana M. (Inventor); Maluf, David A. (Inventor); Mederos, Luis A. (Inventor); Gawdiak, Yuri O. (Inventor)

    2010-01-01

    A computer-based system for configuring and displaying information on changes in, and present status of, a collection of events associated with a project. Classes of icons for decision events, configurations and feedback mechanisms, and time lines (sequential and/or simultaneous) for related events are displayed. Metadata for each icon in each class is displayed by choosing and activating the corresponding icon. Access control (viewing, reading, writing, editing, deleting, etc.) is optionally imposed for metadata and other displayed information.

  6. SNS programming environment user's guide

    NASA Technical Reports Server (NTRS)

    Tennille, Geoffrey M.; Howser, Lona M.; Humes, D. Creig; Cronin, Catherine K.; Bowen, John T.; Drozdowski, Joseph M.; Utley, Judith A.; Flynn, Theresa M.; Austin, Brenda A.

    1992-01-01

    The computing environment is briefly described for the Supercomputing Network Subsystem (SNS) of the Central Scientific Computing Complex of NASA Langley. The major SNS computers are a CRAY-2, a CRAY Y-MP, a CONVEX C-210, and a CONVEX C-220. The software is described that is common to all of these computers, including: the UNIX operating system, computer graphics, networking utilities, mass storage, and mathematical libraries. Also described is file management, validation, SNS configuration, documentation, and customer services.

  7. A Document-Based EHR System That Controls the Disclosure of Clinical Documents Using an Access Control List File Based on the HL7 CDA Header.

    PubMed

    Takeda, Toshihiro; Ueda, Kanayo; Nakagawa, Akito; Manabe, Shirou; Okada, Katsuki; Mihara, Naoki; Matsumura, Yasushi

    2017-01-01

    Electronic health record (EHR) systems are necessary for the sharing of medical information between care delivery organizations (CDOs). We developed a document-based EHR system in which all of the PDF documents that are stored in our electronic medical record system can be disclosed to selected target CDOs. An access control list (ACL) file was designed based on the HL7 CDA header to manage the information that is disclosed.

  8. Digital Archive Issues from the Perspective of an Earth Science Data Producer

    NASA Technical Reports Server (NTRS)

    Barkstrom, Bruce R.

    2004-01-01

    Contents include the following: Introduction. A Producer Perspective on Earth Science Data. Data Producers as Members of a Scientific Community. Some Unique Characteristics of Scientific Data. Spatial and Temporal Sampling for Earth (or Space) Science Data. The Influence of the Data Production System Architecture. The Spatial and Temporal Structures Underlying Earth Science Data. Earth Science Data File (or Relation) Schemas. Data Producer Configuration Management Complexities. The Topology of Earth Science Data Inventories. Some Thoughts on the User Perspective. Science Data User Communities. Spatial and Temporal Structure Needs of Different Users. User Spatial Objects. Data Search Services. Inventory Search. Parameter (Keyword) Search. Metadata Searches. Documentation Search. Secondary Index Search. Print Technology and Hypertext. Inter-Data Collection Configuration Management Issues. An Archive View. Producer Data Ingest and Production. User Data Searching and Distribution. Subsetting and Supersetting. Semantic Requirements for Data Interchange. Tentative Conclusions. An Object Oriented View of Archive Information Evolution. Scientific Data Archival Issues. A Perspective on the Future of Digital Archives for Scientific Data. References Index for this paper.

  9. Cost-effective and business-beneficial computer validation for bioanalytical laboratories.

    PubMed

    McDowall, Rd

    2011-07-01

    Computerized system validation is often viewed as a burden and a waste of time to meet regulatory requirements. This article presents a different approach by looking at validation in a bioanalytical laboratory from the business benefits that computer validation can bring. Ask yourself the question, have you ever bought a computerized system that did not meet your initial expectations? This article will look at understanding the process to be automated, the paper to be eliminated and the records to be signed to meet the requirements of the GLP or GCP and Part 11 regulations. This paper will only consider commercial nonconfigurable and configurable software such as plate readers and LC-MS/MS data systems rather than LIMS or custom applications. Two streamlined life cycle models are presented. The first one consists of a single document for validation of nonconfigurable software. The second is for configurable software and is a five-stage model that avoids the need to write functional and design specifications. Both models are aimed at managing the risk each type of software poses whist reducing the amount of documented evidence required for validation.

  10. 78 FR 128 - Proposed Collection; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-01-02

    ... derivatives dealer will spend establishing and documenting its risk management control system is 2,000 hours... to maintain (e.g., reviewing and updating) its risk management control system.\\1\\ Currently, four... registered with the Commission to maintain their risk management control systems,\\2\\ 2,666 hours for the four...

  11. Client Oriented Management Documents.

    ERIC Educational Resources Information Center

    Limaye, Mohan R.; Hightower, Rick

    Noting that accounting reports, including management advisory service (MAS) studies, reports on internal control, and tax memoranda, often appear rather dense and heavy in style--partly because of the legal environment's demand for careful expression and partly because such documents convey very complex information--this paper presents four…

  12. Integrated Advanced Microwave Sounding Unit-A (AMSU-A)

    NASA Technical Reports Server (NTRS)

    Hauerwaas, R.

    1998-01-01

    This is the 69th Monthly Report for the Advanced Microwave Sounding Unit-A (EOS/AMSU-A), Contract NAS5-32314, and covers the period from 01 September through 30 September 1998. Included in this report are Combined Program Delivery Schedules and Reports (Section 2); a report from the Product Team Leaders on the status of all major program elements (Section 3); Contract Data Requirements List (CDRL) 503, the Weight and Power Budgets (Section 5); CDRL 204, reporting on the activities of Performance Assurance (Section 6); CDRL 203, the Configuration Management Status Report (Section 7); and the Document/Data Management Status Report (Section 8).

  13. Initial development of the DIII–D snowflake divertor control

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kolemen, Egemen; Vail, P. J.; Makowski, M. A.

    Simultaneous control of two proximate magnetic field nulls in the divertor region is demonstrated on DIII–D to enable plasma operations in an advanced magnetic configuration known as the snowflake divertor (SFD). The SFD is characterized by a second-order poloidal field null, created by merging two first-order nulls of the standard divertor configuration. The snowflake configuration has many magnetic properties, such as high poloidal flux expansion, large plasma-wetted area, and additional strike points, that are advantageous for divertor heat flux management in future fusion reactors. However, the magnetic configuration of the SFD is highly-sensitive to changes in currents within the plasmamore » and external coils and therefore requires complex magnetic control. The first real-time snowflake detection and control system on DIII–D has been implemented in order to stabilize the configuration. The control algorithm calculates the position of the two nulls in real-time by locally-expanding the Grad–Shafranov equation in the divertor region. A linear relation between variations in the poloidal field coil currents and changes in the null locations is then analytically derived. This formulation allows for simultaneous control of multiple coils to achieve a desired SFD configuration. It is shown that the control enabled various snowflake configurations on DIII–D in scenarios such as the double-null advanced tokamak. In conclusion, the SFD resulted in a 2.5×reduction in the peak heat flux for many energy confinement times (2–3s) without any adverse effects on core plasma performance.« less

  14. Initial development of the DIII–D snowflake divertor control

    DOE PAGES

    Kolemen, Egemen; Vail, P. J.; Makowski, M. A.; ...

    2018-04-11

    Simultaneous control of two proximate magnetic field nulls in the divertor region is demonstrated on DIII–D to enable plasma operations in an advanced magnetic configuration known as the snowflake divertor (SFD). The SFD is characterized by a second-order poloidal field null, created by merging two first-order nulls of the standard divertor configuration. The snowflake configuration has many magnetic properties, such as high poloidal flux expansion, large plasma-wetted area, and additional strike points, that are advantageous for divertor heat flux management in future fusion reactors. However, the magnetic configuration of the SFD is highly-sensitive to changes in currents within the plasmamore » and external coils and therefore requires complex magnetic control. The first real-time snowflake detection and control system on DIII–D has been implemented in order to stabilize the configuration. The control algorithm calculates the position of the two nulls in real-time by locally-expanding the Grad–Shafranov equation in the divertor region. A linear relation between variations in the poloidal field coil currents and changes in the null locations is then analytically derived. This formulation allows for simultaneous control of multiple coils to achieve a desired SFD configuration. It is shown that the control enabled various snowflake configurations on DIII–D in scenarios such as the double-null advanced tokamak. In conclusion, the SFD resulted in a 2.5×reduction in the peak heat flux for many energy confinement times (2–3s) without any adverse effects on core plasma performance.« less

  15. A materials test system for static compression at elevated temperatures

    NASA Astrophysics Data System (ADS)

    Korellis, J. S.; Steinhaus, C. A.; Totten, J. J.

    1992-06-01

    This report documents modifications to our existing computer-controlled compression testing system to allow elevated temperature testing in an evacuated environment. We have adopted an 'inverse' design configuration where the evacuated test volume is located within the induction heating coil, eliminating the expense and minimizing the evacuation time of a much larger traditional vacuum chamber.

  16. Guidelines for Tailoring DOD-STD-2167A for SDS (Strategic Defense System) Software Development

    DTIC Science & Technology

    1988-02-01

    UNCLASSIFIED APPENDIX A LIST OF ACRONYMS ABM Anti-Ballistic Missle AP Advanced Prototypes BM/C3 Battle Management/Command, Control, Communications CDRL...32 5.7.5 Configuration management ................................. 32 5.8 Sytem integration and testing ....... ............................. 34 t

  17. Tank waste remediation system configuration management implementation plan

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Vann, J.M.

    1998-03-31

    The Tank Waste Remediation System (TWRS) Configuration Management Implementation Plan describes the actions that will be taken by Project Hanford Management Contract Team to implement the TWRS Configuration Management program defined in HNF 1900, TWRS Configuration Management Plan. Over the next 25 years, the TWRS Project will transition from a safe storage mission to an aggressive retrieval, storage, and disposal mission in which substantial Engineering, Construction, and Operations activities must be performed. This mission, as defined, will require a consolidated configuration management approach to engineering, design, construction, as-building, and operating in accordance with the technical baselines that emerge from themore » life cycles. This Configuration Management Implementation Plan addresses the actions that will be taken to strengthen the TWRS Configuration Management program.« less

  18. Energy management and multi-layer control of networked microgrids

    NASA Astrophysics Data System (ADS)

    Zamora, Ramon

    Networked microgrids is a group of neighboring microgrids that has ability to interchange power when required in order to increase reliability and resiliency. Networked microgrid can operate in different possible configurations including: islanded microgrid, a grid-connected microgrid without a tie-line converter, a grid-connected microgrid with a tie-line converter, and networked microgrids. These possible configurations and specific characteristics of renewable energy offer challenges in designing control and management algorithms for voltage, frequency and power in all possible operating scenarios. In this work, control algorithm is designed based on large-signal model that enables microgrid to operate in wide range of operating points. A combination between PI controller and feed-forward measured system responses will compensate for the changes in operating points. The control architecture developed in this work has multi-layers and the outer layer is slower than the inner layer in time response. The main responsibility of the designed controls are to regulate voltage magnitude and frequency, as well as output power of the DG(s). These local controls also integrate with a microgrid level energy management system or microgrid central controller (MGCC) for power and energy balance for. the entire microgrid in islanded, grid-connected, or networked microgid mode. The MGCC is responsible to coordinate the lower level controls to have reliable and resilient operation. In case of communication network failure, the decentralized energy management will operate locally and will activate droop control. Simulation results indicate the superiority of designed control algorithms compared to existing ones.

  19. An Action-Based Fine-Grained Access Control Mechanism for Structured Documents and Its Application

    PubMed Central

    Su, Mang; Li, Fenghua; Tang, Zhi; Yu, Yinyan; Zhou, Bo

    2014-01-01

    This paper presents an action-based fine-grained access control mechanism for structured documents. Firstly, we define a describing model for structured documents and analyze the application scenarios. The describing model could support the permission management on chapters, pages, sections, words, and pictures of structured documents. Secondly, based on the action-based access control (ABAC) model, we propose a fine-grained control protocol for structured documents by introducing temporal state and environmental state. The protocol covering different stages from document creation, to permission specification and usage control are given by using the Z-notation. Finally, we give the implementation of our mechanism and make the comparisons between the existing methods and our mechanism. The result shows that our mechanism could provide the better solution of fine-grained access control for structured documents in complicated networks. Moreover, it is more flexible and practical. PMID:25136651

  20. An action-based fine-grained access control mechanism for structured documents and its application.

    PubMed

    Su, Mang; Li, Fenghua; Tang, Zhi; Yu, Yinyan; Zhou, Bo

    2014-01-01

    This paper presents an action-based fine-grained access control mechanism for structured documents. Firstly, we define a describing model for structured documents and analyze the application scenarios. The describing model could support the permission management on chapters, pages, sections, words, and pictures of structured documents. Secondly, based on the action-based access control (ABAC) model, we propose a fine-grained control protocol for structured documents by introducing temporal state and environmental state. The protocol covering different stages from document creation, to permission specification and usage control are given by using the Z-notation. Finally, we give the implementation of our mechanism and make the comparisons between the existing methods and our mechanism. The result shows that our mechanism could provide the better solution of fine-grained access control for structured documents in complicated networks. Moreover, it is more flexible and practical.

  1. Statewide Intelligent Transportation Systems As-Is Agency Reports For Minnesota, Volume 6, City Of St. Paul

    DOT National Transportation Integrated Search

    1996-08-01

    KEYWORDS: : TRAFFIC SIGNAL CONTROL/REAL-TIME ADAPTIVE CONTROL, ADVANCED TRAFFIC MANAGEMENT SYSTEMS OR ATMS : THIS DOCUMENT PRESENTS THE METHODS, ASSUMPTIONS AND PROCEDURES USED TO COLLECT THE BASELINE INFORMATION. THE DOCUMENTATION OF SYSTEMS ...

  2. [Essential guidelines for Quality Management System].

    PubMed

    Daunizeau, A

    2013-06-01

    The guidelines describe the essential parts of the quality management system to fulfil the requirements of the standard EN ISO 15 189. It includes mainly the organisation, the definition of responsibilities, training of personnel, the document control, the quality control, identification and control of nonconformities, corrective actions, preventive actions and evaluation, as audits and the management review.

  3. 77 FR 39300 - Self-Regulatory Organizations; EDGX Exchange, Inc.; Notice of Filing and Immediate Effectiveness...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-07-02

    ... Change Relating to New Market Access Risk Management Service, EdgeRisk Controls SM June 26, 2012... access risk management service, called EdgeRisk Controls SM (the ``Service''). II. Self-Regulatory..., document and maintain a system of risk management controls and supervisory procedures that are reasonably...

  4. A graph based algorithm for adaptable dynamic airspace configuration for NextGen

    NASA Astrophysics Data System (ADS)

    Savai, Mehernaz P.

    The National Airspace System (NAS) is a complicated large-scale aviation network, consisting of many static sectors wherein each sector is controlled by one or more controllers. The main purpose of the NAS is to enable safe and prompt air travel in the U.S. However, such static configuration of sectors will not be able to handle the continued growth of air travel which is projected to be more than double the current traffic by 2025. Under the initiative of the Next Generation of Air Transportation system (NextGen), the main objective of Adaptable Dynamic Airspace Configuration (ADAC) is that the sectors should change to the changing traffic so as to reduce the controller workload variance with time while increasing the throughput. Change in the resectorization should be such that there is a minimal increase in exchange of air traffic among controllers. The benefit of a new design (improvement in workload balance, etc.) should sufficiently exceed the transition cost, in order to deserve a change. This leads to the analysis of the concept of transition workload which is the cost associated with a transition from one sectorization to another. Given two airspace configurations, a transition workload metric which considers the air traffic as well as the geometry of the airspace is proposed. A solution to reduce this transition workload is also discussed. The algorithm is specifically designed to be implemented for the Dynamic Airspace Configuration (DAC) Algorithm. A graph model which accurately represents the air route structure and air traffic in the NAS is used to formulate the airspace configuration problem. In addition, a multilevel graph partitioning algorithm is developed for Dynamic Airspace Configuration which partitions the graph model of airspace with given user defined constraints and hence provides the user more flexibility and control over various partitions. In terms of air traffic management, vertices represent airports and waypoints. Some of the major (busy) airports need to be given more importance and hence treated separately. Thus the algorithm takes into account the air route structure while finding a balance between sector workloads. The performance of the proposed algorithms and performance metrics is validated with the Enhanced Traffic Management System (ETMS) air traffic data.

  5. Space Station needs, attributes and architectural options. Volume 2, book 2, part 1: Mission implementation concepts

    NASA Technical Reports Server (NTRS)

    1983-01-01

    The overall configuration and modules of the initial and evolved space station are described as well as tended industrial and polar platforms. The mass properties that are the basis for costing are summarized. User friendly attributes (interfaces, resources, and facilities) are identified for commercial; science and applications; industrial park; international participation; national security; and the external tank option. Configuration alternates studied to determine a baseline are examined. Commonality for clustered 3-man and 9-man stations are considered as well as the use of tethered platforms. Requirements are indicated for electrical, communication and tracking; data management Subsystem requirements for electrical, data management, communication and tracking, environment control/life support system; and guidance navigation and control subsystems are identified.

  6. Space Station needs, attributes and architectural options. Volume 2, book 2, part 1: Mission implementation concepts

    NASA Astrophysics Data System (ADS)

    1983-04-01

    The overall configuration and modules of the initial and evolved space station are described as well as tended industrial and polar platforms. The mass properties that are the basis for costing are summarized. User friendly attributes (interfaces, resources, and facilities) are identified for commercial; science and applications; industrial park; international participation; national security; and the external tank option. Configuration alternates studied to determine a baseline are examined. Commonality for clustered 3-man and 9-man stations are considered as well as the use of tethered platforms. Requirements are indicated for electrical, communication and tracking; data management Subsystem requirements for electrical, data management, communication and tracking, environment control/life support system; and guidance navigation and control subsystems are identified.

  7. User's Manual for the Naval Interactive Data Analysis System-Climatologies (NIDAS-C), Version 2.0

    NASA Technical Reports Server (NTRS)

    Abbott, Clifton

    1996-01-01

    This technical note provides the user's manual for the NIDAS-C system developed for the naval oceanographic office. NIDAS-C operates using numerous oceanographic data categories stored in an installed version of the Naval Environmental Operational Nowcast System (NEONS), a relational database management system (rdbms) which employs the ORACLE proprietary rdbms engine. Data management, configuration, and control functions for the supporting rdbms are performed externally. NIDAS-C stores and retrieves data to/from the rdbms but exercises no direct internal control over the rdbms or its configuration. Data is also ingested into the rdbms, for use by NIDAS-C, by external data acquisition processes. The data categories employed by NIDAS-C are as follows: Bathymetry - ocean depth at

  8. Data Supporting Creation of Office of Communications Management.

    ERIC Educational Resources Information Center

    Turner, Alan

    Designed to support the formation of a New York State Office of Communications Management, this document contains official recommendations, cost justifications, public hearing testimonies, and government documents which address the need for a statewide control of telecommunications. A year-long, 12-step plan for implementation of a State Office of…

  9. Guidance documents: Continued support to improve operations of fish hatcheries and field sites to reduce the impact or prevent establishment of New Zealand Mudsnails and other invasive mollusks

    USGS Publications Warehouse

    Moffitt, Christine M.

    2017-01-01

    This project tested and revised a risk assessment/management tool authored by Moffitt and Stockton designed to provide hatchery biologists and others a structure to measure risk and provide tools to control, prevent or eliminate invasive New Zealand mudsnails (NZMS) and other invasive mollusks in fish hatcheries and hatchery operations. The document has two parts: the risk assessment tool, and an appendix that summarizes options for control or management.The framework of the guidance document for risk assessment/hatchery tool combines approaches used by the Hazard Analysis and Critical Control Points (HACCP) process with those developed by the Commission for Environmental Cooperation (CEC), of Canada, Mexico, and the United States, in the Tri-National Risk Assessment Guidelines for Aquatic Alien Invasive Species. The framework approach for this attached first document assesses risk potential with two activities: probability of infestation and consequences of infestation. Each activity is treated equally to determine the risk potential. These two activities are divided into seven basic elements that utilize scientific, technical, and other relevant information in the process of the risk assessment. To determine the probability of infestation four steps are used that have scores reported or determined and averaged. This assessment follows a familiar HACCP process to assess pathways of entry, entry potential, colonization potential, spread potential. The economic, environmental and social consequences are considered as economic impact, environmental impact, and social and cultural influences.To test this document, the Principal Investigator worked to identify interested hatchery managers through contacts at regional aquaculture meetings, fish health meetings, and through the network of invasive species managers and scientists participating in the Western Regional Panel on Aquatic Nuisance Species and the 100th Meridian Initiative's Columbia River Basin Team, and the Western New Zealand Mudsnail Conference in Seattle. Targeted hatchery workshops were conducted with staff at Dworshak National Fish Hatchery Complex (ID), Similkameen Pond, Oroville WA, and Ringold Springs State Hatchery (WA).As a result of communications with hatchery staff, invasive species managers, and on site assessments of hatchery facilities, the document was modified and enhanced. Additional resources were added to keep it up to date. The result is a more simplified tool that can lead hatchery or management personnel through the process of risk assessment and provide an introduction to the risk management and communication process.In addition to the typical HACCP processes, this tool adds steps to rate and consider uncertainty and the weight of evidence regarding options and monitoring results . Uncertainty of outcome exists in most tools that can be used to control or prevent NZMS or other invasive mollusks from infesting an area. In additional this document emphasizes that specific control tools and plans must be tailored to each specific setting to consider the economic, environmental and social influences. From the testing and evaluation process, there was a strong recognition that a number of control and prevention tools previously suggested and reported in the literature from laboratory and small scale trials may not be compatible with regional and national regulations, economic constraints, social or cultural constraints, engineering or water chemistry characteristics of each facility.The options for control are summarized in the second document, Review of Control Measures for Hatcheries Infested with NZMS (Appendix A) that provides sources for additional resources and specific tools, and guidance regarding the feasibility and success of each approach. This tool also emphasizes that management plans need to be adaptive and incorporate oversight from professionals familiar with measuring risks of fish diseases, and treatments (e.g. the fish health practitioners and water quality and effluent management teams). Finally, with such a team, the adaptive management approach must be ongoing, and become a regular component of hatchery operations.Although it was the intent that this two part document would be included as part of the revised National Management and Control Plan for the NZMS proposed by the U.S. Fish and Wildlife Service (USFWS) and others, it is provided as a stand-alone document.

  10. Satellite control system nucleus for the Brazilian complete space mission

    NASA Astrophysics Data System (ADS)

    Yamaguti, Wilson; Decarvalhovieira, Anastacio Emanuel; Deoliveira, Julia Leocadia; Cardoso, Paulo Eduardo; Dacosta, Petronio Osorio

    1990-10-01

    The nucleus of the satellite control system for the Brazilian data collecting and remote sensing satellites is described. The system is based on Digital Equipment Computers and the VAX/VMS operating system. The nucleus provides the access control, the system configuration, the event management, history files management, time synchronization, wall display control, and X25 data communication network access facilities. The architecture of the nucleus and its main implementation aspects are described. The implementation experience acquired is considered.

  11. A database for TMT interface control documents

    NASA Astrophysics Data System (ADS)

    Gillies, Kim; Roberts, Scott; Brighton, Allan; Rogers, John

    2016-08-01

    The TMT Software System consists of software components that interact with one another through a software infrastructure called TMT Common Software (CSW). CSW consists of software services and library code that is used by developers to create the subsystems and components that participate in the software system. CSW also defines the types of components that can be constructed and their roles. The use of common component types and shared middleware services allows standardized software interfaces for the components. A software system called the TMT Interface Database System was constructed to support the documentation of the interfaces for components based on CSW. The programmer describes a subsystem and each of its components using JSON-style text files. A command interface file describes each command a component can receive and any commands a component sends. The event interface files describe status, alarms, and events a component publishes and status and events subscribed to by a component. A web application was created to provide a user interface for the required features. Files are ingested into the software system's database. The user interface allows browsing subsystem interfaces, publishing versions of subsystem interfaces, and constructing and publishing interface control documents that consist of the intersection of two subsystem interfaces. All published subsystem interfaces and interface control documents are versioned for configuration control and follow the standard TMT change control processes. Subsystem interfaces and interface control documents can be visualized in the browser or exported as PDF files.

  12. The Propulsive-Only Flight Control Problem

    NASA Technical Reports Server (NTRS)

    Blezad, Daniel J.

    1996-01-01

    Attitude control of aircraft using only the throttles is investigated. The long time constants of both the engines and of the aircraft dynamics, together with the coupling between longitudinal and lateral aircraft modes make piloted flight with failed control surfaces hazardous, especially when attempting to land. This research documents the results of in-flight operation using simulated failed flight controls and ground simulations of piloted propulsive-only control to touchdown. Augmentation control laws to assist the pilot are described using both optimal control and classical feedback methods. Piloted simulation using augmentation shows that simple and effective augmented control can be achieved in a wide variety of failed configurations.

  13. Management: A continuing literature survey with indexes, March 1976

    NASA Technical Reports Server (NTRS)

    1976-01-01

    Management is a compilation of references to selected reports, journal articles, and other documents on the subject of management. This publication lists 368 documents originally announced in the 1975 issues of Scientific and Technical Aerospace Reports (STAR) or International Aerospace Abstracts (IAA). It includes references on the management of research and development, contracts, production, logistics, personnel, safety, reliability and quality control. It also includes references on: program, project and systems management; management policy, philosophy, tools, and techniques; decisionmaking processes for managers; technology assessment; management of urban problems; and information for managers on Federal resources, expenditures, financing, and budgeting.

  14. Transition of Iraq Relief and Reconstruction Fund Projects to the Iraqi Government

    DTIC Science & Technology

    2006-07-28

    over control of capital assets to the responsible Iraqi government entity for its beneficial use, operation , management , control, and protection using...beneficial use, operation , management , control, and protection. Documentation of this turnover will include, where applicable, all designs, drawings

  15. Design of lane merges at rural freeway construction work zones.

    DOT National Transportation Integrated Search

    2012-10-01

    Practices for the design and control of work zone traffic control configurations have evolved over time : to reflect safer and more efficient management practices. However, they are also recognized as areas : of frequent vehicle conflicts that can ca...

  16. Satellite ATM Networks: Architectures and Guidelines Developed

    NASA Technical Reports Server (NTRS)

    vonDeak, Thomas C.; Yegendu, Ferit

    1999-01-01

    An important element of satellite-supported asynchronous transfer mode (ATM) networking will involve support for the routing and rerouting of active connections. Work published under the auspices of the Telecommunications Industry Association (http://www.tiaonline.org), describes basic architectures and routing protocol issues for satellite ATM (SATATM) networks. The architectures and issues identified will serve as a basis for further development of technical specifications for these SATATM networks. Three ATM network architectures for bent pipe satellites and three ATM network architectures for satellites with onboard ATM switches were developed. The architectures differ from one another in terms of required level of mobility, supported data rates, supported terrestrial interfaces, and onboard processing and switching requirements. The documentation addresses low-, middle-, and geosynchronous-Earth-orbit satellite configurations. The satellite environment may require real-time routing to support the mobility of end devices and nodes of the ATM network itself. This requires the network to be able to reroute active circuits in real time. In addition to supporting mobility, rerouting can also be used to (1) optimize network routing, (2) respond to changing quality-of-service requirements, and (3) provide a fault tolerance mechanism. Traffic management and control functions are necessary in ATM to ensure that the quality-of-service requirements associated with each connection are not violated and also to provide flow and congestion control functions. Functions related to traffic management were identified and described. Most of these traffic management functions will be supported by on-ground ATM switches, but in a hybrid terrestrial-satellite ATM network, some of the traffic management functions may have to be supported by the onboard satellite ATM switch. Future work is planned to examine the tradeoffs of placing traffic management functions onboard a satellite as opposed to implementing those functions at the Earth station components.

  17. Ensuring the Quality of Data Packages in the LTER Network Provenance Aware Synthesis Tracking Architecture Data Management System and Archive

    NASA Astrophysics Data System (ADS)

    Servilla, M. S.; O'Brien, M.; Costa, D.

    2013-12-01

    Considerable ecological research performed today occurs through the analysis of data downloaded from various repositories and archives, often resulting in derived or synthetic products generated by automated workflows. These data are only meaningful for research if they are well documented by metadata, lest semantic or data type errors may occur in interpretation or processing. The Long Term Ecological Research (LTER) Network now screens all data packages entering its long-term archive to ensure that each package contains metadata that is complete, of high quality, and accurately describes the structure of its associated data entity and the data are structurally congruent to the metadata. Screening occurs prior to the upload of a data package into the Provenance Aware Synthesis Tracking Architecture (PASTA) data management system through a series of quality checks, thus preventing ambiguously or incorrectly documented data packages from entering the system. The quality checks within PASTA are designed to work specifically with the Ecological Metadata Language (EML), the metadata standard adopted by the LTER Network to describe data generated by their 26 research sites. Each quality check is codified in Java as part of the ecological community-supported Data Manager Library, which is a resource of the EML specification and used as a component of the PASTA software stack. Quality checks test for metadata quality, data integrity, or metadata-data congruence. Quality checks are further classified as either conditional or informational. Conditional checks issue a 'valid', 'warning' or 'error' response. Only an 'error' response blocks the data package from upload into PASTA. Informational checks only provide descriptive content pertaining to a particular facet of the data package. Quality checks are designed by a group of LTER information managers and reviewed by the LTER community before deploying into PASTA. A total of 32 quality checks have been deployed to date. Quality checks can be customized through a configurable template, which includes turning checks 'on' or 'off' and setting the severity of conditional checks. This feature is important to other potential users of the Data Manager Library who wish to configure its quality checks in accordance with the standards of their community. Executing the complete set of quality checks produces a report that describes the result of each check. The report is an XML document that is stored by PASTA for future reference.

  18. Guide for Operational Configuration Management Program including the adjunct programs of design reconstitution and material condition and aging management. Part 1

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Not Available

    This standard presents program criteria and implementation guidance for an operational configuration management program for DOE nuclear and non-nuclear facilities in the operational phase. Portions of this standard are also useful for other DOE processes, activities, and programs. This Part 1 contains foreword, glossary, acronyms, bibliography, and Chapter 1 on operational configuration management program principles. Appendices are included on configuration management program interfaces, and background material and concepts for operational configuration management.

  19. Report: EPA Should Improve Management Practices and Security Controls for Its Network Directory Service System and Related Servers

    EPA Pesticide Factsheets

    Report #12-P-0836, September 20, 2012. EPA's OEI is not managing key system management documentation, system administration functions, the granting and monitoring of privileged accounts, and the application of security controls associated with its DSS.

  20. Virtual Network Configuration Management System for Data Center Operations and Management

    NASA Astrophysics Data System (ADS)

    Okita, Hideki; Yoshizawa, Masahiro; Uehara, Keitaro; Mizuno, Kazuhiko; Tarui, Toshiaki; Naono, Ken

    Virtualization technologies are widely deployed in data centers to improve system utilization. However, they increase the workload for operators, who have to manage the structure of virtual networks in data centers. A virtual-network management system which automates the integration of the configurations of the virtual networks is provided. The proposed system collects the configurations from server virtualization platforms and VLAN-supported switches, and integrates these configurations according to a newly developed XML-based management information model for virtual-network configurations. Preliminary evaluations show that the proposed system helps operators by reducing the time to acquire the configurations from devices and correct the inconsistency of operators' configuration management database by about 40 percent. Further, they also show that the proposed system has excellent scalability; the system takes less than 20 minutes to acquire the virtual-network configurations from a large scale network that includes 300 virtual machines. These results imply that the proposed system is effective for improving the configuration management process for virtual networks in data centers.

  1. Historical Analysis of C-130E Resources

    DTIC Science & Technology

    1977-07-01

    DOCUMENTATION SEARCH AND COLLECTION FLOW 24 DIAGRAM 6. DATA ANALYSIS FLOW DIAGRAM TASK IV 29 7. C-130 INVENTORY BY CONFIGURATION 40 8. C-130 MISSION...RESORCE RESOURCES....EOUCE .’." * ESURE :;. 400 ................... - ., -...... ’.. ... ".......... ... ’... ’" SYSTEM DESIGN PERFORMANCE 4 , OPERATIO ...Force inventory , the control of the human and material resources crosses several functions and commands. Seldom are the initial estimates verified

  2. SSME/side loads analysis for flight configuration, revision A. [structural analysis of space shuttle main engine under side load excitation

    NASA Technical Reports Server (NTRS)

    Holland, W.

    1974-01-01

    This document describes the dynamic loads analysis accomplished for the Space Shuttle Main Engine (SSME) considering the side load excitation associated with transient flow separation on the engine bell during ground ignition. The results contained herein pertain only to the flight configuration. A Monte Carlo procedure was employed to select the input variables describing the side load excitation and the loads were statistically combined. This revision includes an active thrust vector control system representation and updated orbiter thrust structure stiffness characteristics. No future revisions are planned but may be necessary as system definition and input parameters change.

  3. Configuration Management Policy

    EPA Pesticide Factsheets

    This Policy establishes an Agency-wide Configuration Management Program and to provide responsibilities, compliance requirements, and overall principles for Configuration and Change Management processes to support information technology management.

  4. 75 FR 23822 - Notice of Opportunity for Public Comment on the Proposed Models for Plant-Specific Adoption of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2010-05-04

    ... Agencywide Documents Access and Management System (ADAMS) under Accession Number ML092670242. The proposed... and Maintenance Program'' is being proposed for Section [5.5] [``Administrative Controls--Programs and... and Management System (ADAMS): Publicly available documents created or received at the NRC are...

  5. Innovative Approaches for Urban Watershed Wet-Weather Flow Management and Control: State of Technology Review Report

    EPA Science Inventory

    This report documents initial efforts to identify innovative strategies for managing the effects of wet-weather flow in an urban setting. It served as a communication tool and a starting point for discussion with experts. As such, the document is a compilation of literature rev...

  6. TQM (Total Quality Management) SPARC (Special Process Action Review Committees) Handbook

    DTIC Science & Technology

    1989-08-01

    This document describes the techniques used to support and guide the Special Process Action Review Committees for accomplishing their goals for Total Quality Management (TQM). It includes concepts and definitions, checklists, sample formats, and assessment criteria. Keywords: Continuous process improvement; Logistics information; Process analysis; Quality control; Quality assurance; Total Quality Management ; Statistical processes; Management Planning and control; Management training; Management information systems.

  7. Corral Monitoring System assessment results

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Filby, E.E.; Haskel, K.J.

    1998-03-01

    This report describes the results of a functional and operational assessment of the Corral Monitoring Systems (CMS), which was designed to detect and document accountable items entering or leaving a monitored site. Its development was motivated by the possibility that multiple sites in the nuclear weapons states of the former Soviet Union might be opened to such monitoring under the provisions of the Strategic Arms Reduction Treaty. The assessment was performed at three levels. One level evaluated how well the planned approach addressed the target application, and which involved tracking sensitive items moving into and around a site being monitoredmore » as part of an international treaty or other agreement. The second level examined the overall design and development approach, while the third focused on individual subsystems within the total package. Unfortunately, the system was delivered as disassembled parts and pieces, with very poor documentation. Thus, the assessment was based on fragmentary operating data coupled with an analysis of what documents were provided with the system. The system design seemed to be a reasonable match to the requirements of the target application; however, important questions about site manning and top level administrative control were left unanswered. Four weaknesses in the overall design and development approach were detected: (1) poor configuration control and management, (2) inadequate adherence to a well defined architectural standard, (3) no apparent provision for improving top level error tolerance, and (4) weaknesses in the object oriented programming approach. The individual subsystems were found to offer few features or capabilities that were new or unique, even at the conceptual level. The CMS might possibly have offered a unique combination of features, but this level of integration was never realized, and it had no unique capabilities that could be readily extracted for use in another system.« less

  8. Ver-i-Fus: an integrated access control and information monitoring and management system

    NASA Astrophysics Data System (ADS)

    Thomopoulos, Stelios C.; Reisman, James G.; Papelis, Yiannis E.

    1997-01-01

    This paper describes the Ver-i-Fus Integrated Access Control and Information Monitoring and Management (IAC-I2M) system that INTELNET Inc. has developed. The Ver-i-Fus IAC-I2M system has been designed to meet the most stringent security and information monitoring requirements while allowing two- way communication between the user and the system. The systems offers a flexible interface that permits to integrate practically any sensing device, or combination of sensing devices, including a live-scan fingerprint reader, thus providing biometrics verification for enhanced security. Different configurations of the system provide solutions to different sets of access control problems. The re-configurable hardware interface, tied together with biometrics verification and a flexible interface that allows to integrate Ver-i-Fus with an MIS, provide an integrated solution to security, time and attendance, labor monitoring, production monitoring, and payroll applications.

  9. Management Control System Support of Initiatives for Disruptive Students

    ERIC Educational Resources Information Center

    Scott, Colin

    2011-01-01

    Purpose: The purpose of the paper is to investigate the management control system (MCS) support of school initiatives to develop the school climate and to re-engage disruptive students. Design/methodology/approach: The paper adopts an approach of critical action research interviews with management and document reviews informed by Habermasian…

  10. The evaluation of a number of prototypes for the free-tip rotor constant-moment controller

    NASA Technical Reports Server (NTRS)

    Young, L. A.

    1986-01-01

    The development of several prototypes of a constant moment controller, a critical component of the free-tip rotor (FTR) concept, is described. Also presented are the experimental results of a whirl test designed to select a final controller configuration to be included in a future wind-tunnel test of this innovative rotor system. A brief explanation of the FTR concept and its history are included. The paper documents the controller design constraints, each prototype's operating principle, the evaluation test, and the individual prototype test results. A recommended design is identified, along with the selection rationale.

  11. 17 CFR 240.15c3-4 - Internal risk management control systems for OTC derivatives dealers.

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... 17 Commodity and Securities Exchanges 3 2010-04-01 2010-04-01 false Internal risk management...-Counter Markets § 240.15c3-4 Internal risk management control systems for OTC derivatives dealers. (a) An OTC derivatives dealer shall establish, document, and maintain a system of internal risk management...

  12. Automated Data Management Information System (ADMIS)

    NASA Technical Reports Server (NTRS)

    Blackstone, C.; Dunn, D.; Sullivan, E.; Whitlock, J.; Buehler, D.; Pratt, L.; Hoffiditz, T.; Rose, J.; Smithson, M.; Feeley, J.

    1974-01-01

    ADMIS stores and controls data and documents associated with manned space flight effort. System contains all data oriented toward a specific document; it is primary source of reports generated by the system. Each group of records is composed of one document record, one distribution record for each recipient of the document, and one summary record.

  13. Status of Japanese Experiment Module (JEM) activities

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The current status of the JEM activities are presented in graphic form. The JEM spacecraft configuration is presented. The JEM configuration consist of the Pressurized Module, the Exposed Facility, the Experiment Logistics Module which consist of a pressurized section and an exposed section; and the Remote Manipulator System. The master schedule of the space station is given. Also the development tests of the structure and mechanism, the electrical power system, the data management system, the thermal control system, the environment control system, the experiment support system, and the remote manipulator system are listed.

  14. Requirements management and control

    NASA Technical Reports Server (NTRS)

    Robbins, Red

    1993-01-01

    The systems engineering process for thermal nuclear propulsion requirements and configuration definition is described in outline and graphic form. Functional analysis and mission attributes for a Mars exploration mission are also addressed.

  15. Control Law-Control Allocation Interaction: F/A-18 PA Simulation Test - Bed

    NASA Technical Reports Server (NTRS)

    Durham, Wayne; Nelson, Mark

    2001-01-01

    This report documents the first stage of research into Control Law - Control Allocation Interactions. A three-year research effort was originally proposed: 1. Create a desktop flight simulation environment under which experiments related to the open questions may be conducted. 2. Conduct research to determine which aspects of control allocation have impact upon control law design that merits further research. 3. Conduct research into those aspects of control allocation identified above, and their impacts upon control law design. Simulation code was written utilizing the F/A-18 airframe in the power approach (PA) configuration. A dynamic inversion control law was implemented and used to drive a state-of-the-art control allocation subroutine.

  16. Configuration Management File Manager Developed for Numerical Propulsion System Simulation

    NASA Technical Reports Server (NTRS)

    Follen, Gregory J.

    1997-01-01

    One of the objectives of the High Performance Computing and Communication Project's (HPCCP) Numerical Propulsion System Simulation (NPSS) is to provide a common and consistent way to manage applications, data, and engine simulations. The NPSS Configuration Management (CM) File Manager integrated with the Common Desktop Environment (CDE) window management system provides a common look and feel for the configuration management of data, applications, and engine simulations for U.S. engine companies. In addition, CM File Manager provides tools to manage a simulation. Features include managing input files, output files, textual notes, and any other material normally associated with simulation. The CM File Manager includes a generic configuration management Application Program Interface (API) that can be adapted for the configuration management repositories of any U.S. engine company.

  17. Aerodynamic Performance of an Active Flow Control Configuration Using Unstructured-Grid RANS

    NASA Technical Reports Server (NTRS)

    Joslin, Ronald D.; Viken, Sally A.

    2001-01-01

    This research is focused on assessing the value of the Reynolds-Averaged Navier-Stokes (RANS) methodology for active flow control applications. An experimental flow control database exists for a TAU0015 airfoil, which is a modification of a NACA0015 airfoil. The airfoil has discontinuities at the leading edge due to the implementation of a fluidic actuator and aft of mid chord on the upper surface. This paper documents two- and three-dimensional computational results for the baseline wing configuration (no control) with tile experimental results. The two-dimensional results suggest that the mid-chord discontinuity does not effect the aerodynamics of the wing and can be ignored for more efficient computations. The leading-edge discontinuity significantly affects tile lift and drag; hence, the integrity of the leading-edge notch discontinuity must be maintained in the computations to achieve a good match with the experimental data. The three-dimensional integrated performance results are in good agreement with the experiments inspite of some convergence and grid resolution issues.

  18. Metropolitan transportation management center : a case study : Boston Central Artery/Tunnel Integrated Project control system : responding to incidents rapidly and effectively

    DOT National Transportation Integrated Search

    1999-10-01

    The following case study provides a snapshot of the Boston Central Artery/Tunnel Integration Project Control System (IPCS) operations control center. It follows the outline provided in the companion document, Metropolitan Transportation Management Ce...

  19. First NASA/Industry High-Speed Research Configuration Aerodynamics Workshop

    NASA Technical Reports Server (NTRS)

    Wood, Richard M. (Editor)

    1999-01-01

    This publication is a compilation of documents presented at the First NASA/Industry High Speed Research Configuration Aerodynamics Workshop held on February 27-29, 1996 at NASA Langley Research Center. The purpose of the workshop was to bring together the broad spectrum of aerodynamicists, engineers, and scientists working within the Configuration Aerodynamics element of the HSR Program to collectively evaluate the technology status and to define the needs within Computational Fluid Dynamics (CFD) Analysis Methodology, Aerodynamic Shape Design, Propulsion/Airframe Integration (PAI), Aerodynamic Performance, and Stability and Control (S&C) to support the development of an economically viable High Speed Civil Transport (HSCT) aircraft. To meet these objectives, papers were presented by representative from NASA Langley, Ames, and Lewis Research Centers; Boeing, McDonnell Douglas, Northrop-Grumman, Lockheed-Martin, Vigyan, Analytical Services, Dynacs, and RIACS.

  20. First NASA/Industry High-Speed Research Configuration Aerodynamics Workshop. Pt. 2

    NASA Technical Reports Server (NTRS)

    Wood, Richard M. (Editor)

    1999-01-01

    This publication is a compilation of documents presented at the First NASA Industry High Speed Research Configuration Aerodynamics Workshop held on February 27-29, 1996 at NASA Langley Research Center. The purpose of the workshop was to bring together the broad spectrum of aerodynamicists, engineers, and scientists working within the Configuration Aerodynamics element of the HSR Program to collectively evaluate the technology status and to define the needs within Computational Fluid Dynamics (CFD) Analysis Methodology, Aerodynamic Shape Design, Propulsion/Airframe Integration (PAI), Aerodynamic Performance, and Stability and Control (S&C) to support the development of an economically viable High Speed Civil Transport (HSCT) aircraft. To meet these objectives, papers were presented by representatives from NASA Langley, Ames, and Lewis Research Centers; Boeing, McDonnell Douglas, Northrop-Grumman, Lockheed-Martin, Vigyan, Analytical Services, Dynacs, and RIACS.

  1. First NASA/Industry High-Speed Research Configuration Aerodynamics Workshop. Part 1

    NASA Technical Reports Server (NTRS)

    Wood, Richard M. (Editor)

    1999-01-01

    This publication is a compilation of documents presented at the First NASA/Industry High Speed Research Configuration Aerodynamics Workshop held on February 27-29, 1996 at NASA Langley Research Center. The purpose of the workshop was to bring together the broad spectrum of aerodynamicists, engineers, and scientists working within the Configuration Aerodynamics element of the HSR Program to collectively evaluate the technology status and to define the needs within Computational Fluid Dynamics (CFD) Analysis Methodology, Aerodynamic Shape Design, Propulsion/Airframe Integration (PAI), Aerodynamic Performance, and Stability and Control (S&C) to support the development of an economically viable High Speed Civil Transport (HSCT) aircraft. To meet these objectives, papers were presented by representative from NASA Langley, Ames, and Lewis Research Centers; Boeing, McDonnell Douglas, Northrop-Grumman, Lockheed-Martin, Vigyan, Analytical Services, Dynacs, and RIACS.

  2. ISS and STS Commercial Off-the-Shelf Router Testing

    NASA Technical Reports Server (NTRS)

    Ivancie, William D.; Bell, Terry L.; Shell, Dan

    2002-01-01

    This report documents the results of testing performed with commercial off-the-shelf (COTS) routers and Internet Protocols (IPs) to determine if COTS equipment and IP could be utilized to upgrade NASA's current Space Transportation System (STS), the Shuttle, and the International Space Station communication infrastructure. Testing was performed by NASA Glenn Research Center (GRC) personnel within the Electronic Systems Test Laboratory (ESTE) with cooperation from the Mission Operations Directorate (MOD) Qualification and Utilization of Electronic System Technology (QUEST) personnel. The ESTE testing occurred between November 1 and 9, 2000. Additional testing was performed at NASA Glenn Research Center in a laboratory environment with equipment configured to emulate the STS. This report documents those tests and includes detailed test procedures, equipment interface requirements, test configurations and test results. The tests showed that a COTS router and standard Transmission Control Protocols and Internet Protocols (TCP/IP) could be used for both the Shuttle and the Space Station if near-error-free radio links are provided.

  3. A distributed data base management capability for the deep space network

    NASA Technical Reports Server (NTRS)

    Bryan, A. I.

    1976-01-01

    The Configuration Control and Audit Assembly (CCA) is reported that has been designed to provide a distributed data base management capability for the DSN. The CCA utilizes capabilities provided by the DSN standard minicomputer and the DSN standard nonreal time high level management oriented programming language, MBASIC. The characteristics of the CCA for the first phase of implementation are described.

  4. Smashing the Stovepipe: Leveraging the GMSEC Open Architecture and Advanced IT Automation to Rapidly Prototype, Develop and Deploy Next-Generation Multi-Mission Ground Systems

    NASA Technical Reports Server (NTRS)

    Swenson, Paul

    2017-01-01

    Satellite/Payload Ground Systems - Typically highly-customized to a specific mission's use cases - Utilize hundreds (or thousands!) of specialized point-to-point interfaces for data flows / file transfers Documentation and tracking of these complex interfaces requires extensive time to develop and extremely high staffing costs Implementation and testing of these interfaces are even more cost-prohibitive, and documentation often lags behind implementation resulting in inconsistencies down the road With expanding threat vectors, IT Security, Information Assurance and Operational Security have become key Ground System architecture drivers New Federal security-related directives are generated on a daily basis, imposing new requirements on current / existing ground systems - These mandated activities and data calls typically carry little or no additional funding for implementation As a result, Ground System Sustaining Engineering groups and Information Technology staff continually struggle to keep up with the rolling tide of security Advancing security concerns and shrinking budgets are pushing these large stove-piped ground systems to begin sharing resources - I.e. Operational / SysAdmin staff, IT security baselines, architecture decisions or even networks / hosting infrastructure Refactoring these existing ground systems into multi-mission assets proves extremely challenging due to what is typically very tight coupling between legacy components As a result, many "Multi-Mission" ops. environments end up simply sharing compute resources and networks due to the difficulty of refactoring into true multi-mission systems Utilizing continuous integration / rapid system deployment technologies in conjunction with an open architecture messaging approach allows System Engineers and Architects to worry less about the low-level details of interfaces between components and configuration of systems GMSEC messaging is inherently designed to support multi-mission requirements, and allows components to aggregate data across multiple homogeneous or heterogeneous satellites or payloads - The highly-successful Goddard Science and Planetary Operations Control Center (SPOCC) utilizes GMSEC as the hub for it's automation and situational awareness capability Shifts focus towards getting GS to a final configuration-managed baseline, as well as multi-mission / big-picture capabilities that help increase situational awareness, promote cross-mission sharing and establish enhanced fleet management capabilities across all levels of the enterprise.

  5. A PBOM configuration and management method based on templates

    NASA Astrophysics Data System (ADS)

    Guo, Kai; Qiao, Lihong; Qie, Yifan

    2018-03-01

    The design of Process Bill of Materials (PBOM) holds a hinge position in the process of product development. The requirements of PBOM configuration design and management for complex products are analysed in this paper, which include the reuse technique of configuration procedure and urgent management need of huge quantity of product family PBOM data. Based on the analysis, the function framework of PBOM configuration and management has been established. Configuration templates and modules are defined in the framework to support the customization and the reuse of configuration process. The configuration process of a detection sensor PBOM is shown as an illustration case in the end. The rapid and agile PBOM configuration and management can be achieved utilizing template-based method, which has a vital significance to improve the development efficiency for complex products.

  6. Implementation of a configurable laboratory information management system for use in cellular process development and manufacturing.

    PubMed

    Russom, Diana; Ahmed, Amira; Gonzalez, Nancy; Alvarnas, Joseph; DiGiusto, David

    2012-01-01

    Regulatory requirements for the manufacturing of cell products for clinical investigation require a significant level of record-keeping, starting early in process development and continuing through to the execution and requisite follow-up of patients on clinical trials. Central to record-keeping is the management of documentation related to patients, raw materials, processes, assays and facilities. To support these requirements, we evaluated several laboratory information management systems (LIMS), including their cost, flexibility, regulatory compliance, ongoing programming requirements and ability to integrate with laboratory equipment. After selecting a system, we performed a pilot study to develop a user-configurable LIMS for our laboratory in support of our pre-clinical and clinical cell-production activities. We report here on the design and utilization of this system to manage accrual with a healthy blood-donor protocol, as well as manufacturing operations for the production of a master cell bank and several patient-specific stem cell products. The system was used successfully to manage blood donor eligibility, recruiting, appointments, billing and serology, and to provide annual accrual reports. Quality management reporting features of the system were used to capture, report and investigate process and equipment deviations that occurred during the production of a master cell bank and patient products. Overall the system has served to support the compliance requirements of process development and phase I/II clinical trial activities for our laboratory and can be easily modified to meet the needs of similar laboratories.

  7. Model-Driven Configuration of SELinux Policies

    NASA Astrophysics Data System (ADS)

    Agreiter, Berthold; Breu, Ruth

    The need for access control in computer systems is inherent. However, the complexity to configure such systems is constantly increasing which affects the overall security of a system negatively. We think that it is important to define security requirements on a non-technical level while taking the application domain into respect in order to have a clear and separated view on security configuration (i.e. unblurred by technical details). On the other hand, security functionality has to be tightly integrated with the system and its development process in order to provide comprehensive means of enforcement. In this paper, we propose a systematic approach based on model-driven security configuration to leverage existing operating system security mechanisms (SELinux) for realising access control. We use UML models and develop a UML profile to satisfy these needs. Our goal is to exploit a comprehensive protection mechanism while rendering its security policy manageable by a domain specialist.

  8. Aircraft/Air Traffic Management Functional Analysis Model. Version 2.0; User's Guide

    NASA Technical Reports Server (NTRS)

    Etheridge, Melvin; Plugge, Joana; Retina, Nusrat

    1998-01-01

    The Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 (FAM 2.0), is a discrete event simulation model designed to support analysis of alternative concepts in air traffic management and control. FAM 2.0 was developed by the Logistics Management Institute (LMI) a National Aeronautics and Space Administration (NASA) contract. This document provides a guide for using the model in analysis. Those interested in making enhancements or modification to the model should consult the companion document, Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 Technical Description.

  9. TECHNICAL GUIDANCE DOCUMENT: CONSTRUCTION QUALITY MANAGEMENT FOR REMEDIAL ACTION AND REMEDIAL DESIGN WASTE CONTAINMENT SYSTEMS

    EPA Science Inventory

    This Technical Guidance Document is intended to augment the numerous construction quality control and construction quality assurance (CQC and CQA) documents that are available far materials associated with waste containment systems developed for Superfund site remediation. In ge...

  10. Supporting the Federal Emergency Management Agency Rescuers: a variation of critical incident stress management.

    PubMed

    Garcia, Evangeline; Horton, Denise A

    2003-02-01

    The purpose of this article was to document the efforts of two military installations in facilitating Critical Incident Stress Management teams for Federal Emergency Management Agency Rescue and Recovery Units following the attacks on the World Trade Center on September 11, 2001. McGuire Air Force Base accepted the mission to support the rotating task forces with emotional support, and Fort Dix offered temporary lodging while the teams were in-bound and out-bound to the "Ground Zero" site. A team, comprised of staff from both installations due to the configuration of professional and support staffs, does the Critical Incident Stress Management work. Both installations are within commuting distance of New York City and could provide adequate safety, security, and logistics to the teams. The classic crisis management models were not called into play, as that service was not asked for; however, it was clear to the McGuire Air Force Base/Fort Dix Critical Incident Stress Management team members that the rescue and recovery teams needed their physical presence. Many rescue organizations have their own "debriefing teams," yet it is believed that "outside teams" may be helpful as interim measures to demonstrate the universality of the process of coping with traumatic stress and grief management. It is hoped that this article honors the workers who came together to help in a very difficult time for our country. This article documents the interim measures that were taken for a group of people moving through crisis.

  11. AN ADVANCED TOOL FOR APPLIED INTEGRATED SAFETY MANAGEMENT

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Potts, T. Todd; Hylko, James M.; Douglas, Terence A.

    2003-02-27

    WESKEM, LLC's Environmental, Safety and Health (ES&H) Department had previously assessed that a lack of consistency, poor communication and using antiquated communication tools could result in varying operating practices, as well as a failure to capture and disseminate appropriate Integrated Safety Management (ISM) information. To address these issues, the ES&H Department established an Activity Hazard Review (AHR)/Activity Hazard Analysis (AHA) process for systematically identifying, assessing, and controlling hazards associated with project work activities during work planning and execution. Depending on the scope of a project, information from field walkdowns and table-top meetings are collected on an AHR form. The AHAmore » then documents the potential failure and consequence scenarios for a particular hazard. Also, the AHA recommends whether the type of mitigation appears appropriate or whether additional controls should be implemented. Since the application is web based, the information is captured into a single system and organized according to the >200 work activities already recorded in the database. Using the streamlined AHA method improved cycle time from over four hours to an average of one hour, allowing more time to analyze unique hazards and develop appropriate controls. Also, the enhanced configuration control created a readily available AHA library to research and utilize along with standardizing hazard analysis and control selection across four separate work sites located in Kentucky and Tennessee. The AHR/AHA system provides an applied example of how the ISM concept evolved into a standardized field-deployed tool yielding considerable efficiency gains in project planning and resource utilization. Employee safety is preserved through detailed planning that now requires only a portion of the time previously necessary. The available resources can then be applied to implementing appropriate engineering, administrative and personal protective equipment controls in the field.« less

  12. Evaluation of Early Ground Control Station Configurations for Interacting with a UAS Traffic Management (UTM) System

    NASA Technical Reports Server (NTRS)

    Dao, Arik-Quang V.; Martin, Lynne; Mohlenbrink, Christoph; Bienert, Nancy; Wolte, Cynthia; Gomez, Ashley; Claudatos, Lauren; Mercer, Joey

    2017-01-01

    The purpose of this paper is to report on a human factors evaluation of ground control station design concepts for interacting with an unmanned traffic management system. The data collected for this paper comes from recent field tests for NASA's Unmanned Traffic Management (UTM) project, and covers the following topics; workload, situation awareness, as well as flight crew communication, coordination, and procedures. The goal of this evaluation was to determine if the various software implementations for interacting with the UTM system can be described and classified into design concepts to provide guidance for the development of future UTM interfaces. We begin with a brief description of NASA's UTM project, followed by a description of the test range configuration related to a second development phase. We identified (post hoc) two classes in which the ground control stations could be grouped. This grouping was based on level of display integration. The analysis was exploratory and informal. It was conducted to compare ground stations across those two classes and against the aforementioned topics. Herein, we discuss the results.

  13. Gaia DR1 documentation Chapter 6: Variability

    NASA Astrophysics Data System (ADS)

    Eyer, L.; Rimoldini, L.; Guy, L.; Holl, B.; Clementini, G.; Cuypers, J.; Mowlavi, N.; Lecoeur-Taïbi, I.; De Ridder, J.; Charnas, J.; Nienartowicz, K.

    2017-12-01

    This chapter describes the photometric variability processing of the Gaia DR1 data. Coordination Unit 7 is responsible for the variability analysis of over a billion celestial sources. In particular the definition, design, development, validation and provision of a software package for the data processing of photometrically variable objects. Data Processing Centre Geneva (DPCG) responsibilities cover all issues related to the computational part of the CU7 analysis. These span: hardware provisioning, including selection, deployment and optimisation of suitable hardware, choosing and developing software architecture, defining data and scientific workflows as well as operational activities such as configuration management, data import, time series reconstruction, storage and processing handling, visualisation and data export. CU7/DPCG is also responsible for interaction with other DPCs and CUs, software and programming training for the CU7 members, scientific software quality control and management of software and data lifecycle. Details about the specific data treatment steps of the Gaia DR1 data products are found in Eyer et al. (2017) and are not repeated here. The variability content of the Gaia DR1 focusses on a subsample of Cepheids and RR Lyrae stars around the South ecliptic pole, showcasing the performance of the Gaia photometry with respect to variable objects.

  14. Flammability Configuration Analysis for Spacecraft Applications

    NASA Technical Reports Server (NTRS)

    Pedley, Michael D.

    2014-01-01

    Fire is one of the many potentially catastrophic hazards associated with the operation of crewed spacecraft. A major lesson learned by NASA from the Apollo 204 fire in 1966 was that ignition sources in an electrically powered vehicle should and can be minimized, but can never be eliminated completely. For this reason, spacecraft fire control is based on minimizing potential ignition sources and eliminating materials that can propagate fire. Fire extinguishers are always provided on crewed spacecraft, but are not considered as part of the fire control process. "Eliminating materials that can propagate fire" does not mean eliminating all flammable materials - the cost of designing and building spacecraft using only nonflammable materials is extraordinary and unnecessary. It means controlling the quantity and configuration of such materials to eliminate potential fire propagation paths and thus ensure that any fire would be small, localized, and isolated, and would self-extinguish without harm to the crew. Over the years, NASA has developed many solutions for controlling the configuration of flammable materials (and potentially flammable materials in commercial "off-the-shelf" hardware) so that they can be used safely in air and oxygen-enriched environments in crewed spacecraft. This document describes and explains these design solutions so payload customers and other organizations can use them in designing safe and cost-effective flight hardware. Proper application of these guidelines will produce acceptable flammability configurations for hardware located in any compartment of the International Space Station or other program crewed vehicles and habitats. However, use of these guidelines does not exempt hardware organizations of the responsibility for safety of the hardware under their control.

  15. The NASA Air Traffic Management Ontology: Technical Documentation

    NASA Technical Reports Server (NTRS)

    Keller, Richard M.

    2017-01-01

    This document is intended to serve as comprehensive documentation for the NASA Air Traffic Management (ATM) Ontology. The ATM Ontology is a conceptual model that defines key classes of entities and relationships pertaining to the US National Airspace System (NAS) and the management of air traffic through that system. A wide variety of classes are represented in the ATM Ontology, including classes corresponding to flights, aircraft, manufacturers, airports, airlines, air routes, NAS facilities, air traffic control advisories, weather phenomena, and many others. The Ontology can be useful in the context of a variety of information management tasks relevant to NAS, including information exchange, data query and search, information organization, information integration, and terminology standardization.

  16. Adaptive momentum management for large space structures

    NASA Technical Reports Server (NTRS)

    Hahn, E.

    1987-01-01

    Momentum management is discussed for a Large Space Structure (LSS) with the structure selected configuration being the Initial Orbital Configuration (IOC) of the dual keel space station. The external forces considered were gravity gradient and aerodynamic torques. The goal of the momentum management scheme developed is to remove the bias components of the external torques and center the cyclic components of the stored angular momentum. The scheme investigated is adaptive to uncertainties of the inertia tensor and requires only approximate knowledge of principle moments of inertia. Computational requirements are minimal and should present no implementation problem in a flight type computer and the method proposed is shown to be effective in the presence of attitude control bandwidths as low as .01 radian/sec.

  17. Adaptive momentum management for the dual keel Space Station

    NASA Technical Reports Server (NTRS)

    Hopkins, M.; Hahn, E.

    1987-01-01

    The report discusses momentum management for a large space structure with the structure selected configuration being the Initial Orbital Configuration of the dual-keel Space Station. The external torques considered were gravity gradient and aerodynamic torques. The goal of the momentum management scheme developed is to remove the bias components of the external torques and center the cyclic components of the stored angular momentum. The scheme investigated is adaptive to uncertainties of the inertia tensor and requires only approximate knowledge of principal moments of inertia. Computational requirements are minimal and should present no implementation problem in a flight-type computer. The method proposed is shown to be effective in the presence of attitude control bandwidths as low as 0.01 radian/sec.

  18. 76 FR 26746 - Information Collection Requests to Office of Management and Budget; OMB Control Numbers: 1625...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-05-09

    ... Office of Management and Budget; OMB Control Numbers: 1625-0077, 1625-0085 and 1625-0112 AGENCY: Coast...-0085, Streamlined Inspection Program; and 1625-0112, Enhanced Maritime Domain Awareness via Electronic... Information Management, telephone 202-475-3652, or fax 202-475-3929, for questions on these documents. Contact...

  19. The planning and control of NASA programs and resources

    NASA Technical Reports Server (NTRS)

    1983-01-01

    The major management systems used to plan and control NASA programs and resources are described as well as their integration to form the agency's general management approach in carrying out its mission. Documents containing more detailed descriptions of the processes and techniques involved in the agency's major management systems are listed.

  20. Space Telecommunications Radio System (STRS) Compliance Testing

    NASA Technical Reports Server (NTRS)

    Handler, Louis M.

    2011-01-01

    The Space Telecommunications Radio System (STRS) defines an open architecture for software defined radios. This document describes the testing methodology to aid in determining the degree of compliance to the STRS architecture. Non-compliances are reported to the software and hardware developers as well as the NASA project manager so that any non-compliances may be fixed or waivers issued. Since the software developers may be divided into those that provide the operating environment including the operating system and STRS infrastructure (OE) and those that supply the waveform applications, the tests are divided accordingly. The static tests are also divided by the availability of an automated tool that determines whether the source code and configuration files contain the appropriate items. Thus, there are six separate step-by-step test procedures described as well as the corresponding requirements that they test. The six types of STRS compliance tests are: STRS application automated testing, STRS infrastructure automated testing, STRS infrastructure testing by compiling WFCCN with the infrastructure, STRS configuration file testing, STRS application manual code testing, and STRS infrastructure manual code testing. Examples of the input and output of the scripts are shown in the appendices as well as more specific information about what to configure and test in WFCCN for non-compliance. In addition, each STRS requirement is listed and the type of testing briefly described. Attached is also a set of guidelines on what to look for in addition to the requirements to aid in the document review process.

  1. 33 CFR 332.4 - Planning and documentation.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... control invasive plant species; the proposed grading plan, including elevations and slopes of the substrate; soil management; and erosion control measures. For stream compensatory mitigation projects, the... standards and if adaptive management is needed. A schedule for monitoring and reporting on monitoring...

  2. 33 CFR 332.4 - Planning and documentation.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... control invasive plant species; the proposed grading plan, including elevations and slopes of the substrate; soil management; and erosion control measures. For stream compensatory mitigation projects, the... standards and if adaptive management is needed. A schedule for monitoring and reporting on monitoring...

  3. 33 CFR 332.4 - Planning and documentation.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... control invasive plant species; the proposed grading plan, including elevations and slopes of the substrate; soil management; and erosion control measures. For stream compensatory mitigation projects, the... standards and if adaptive management is needed. A schedule for monitoring and reporting on monitoring...

  4. 33 CFR 332.4 - Planning and documentation.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... control invasive plant species; the proposed grading plan, including elevations and slopes of the substrate; soil management; and erosion control measures. For stream compensatory mitigation projects, the... standards and if adaptive management is needed. A schedule for monitoring and reporting on monitoring...

  5. Consolidated Development Objectives Document (CDOD) For MB-60

    NASA Technical Reports Server (NTRS)

    Greene, William D.

    2013-01-01

    This document defines the objectives related to liquid rocket engine system development to be undertaken by JAXA in support of the Space Launch System (SLS) Program managed out of the NASA Marshall Space Flight Center (MSFC). These objectives include furnishing the necessary management, labor, facilities, tools, equipment, and materials required to execute the specified activities. 1.1 Project Scope: The scope of this effort is to develop a rocket engine and associated products per the objectives and technical requirements established in this document. This engine, minus the engine controller, designated here as MB ]60, is to be developed through to a prequalification point of maturity. It is assumed that should JCNE ]1 development proceed beyond this maturity point towards actual flight qualification, the engine controller will be supplied and integrated by NASA. 1.2 Document Structure: The structure of this Consolidated Development Objectives Document (CDOD) includes a traditional description of objectives in a SOO, plus the associated Data Products Document (DPD) in an attached appendix, and then Engine Requirements Document (ERD) as another attached appendix. It is the intent that this document, in conjunction with the cited applicable documents, should constitute a complete programmatic and technical description of the development effort to be pursued.

  6. Waste Technology Engineering Laboratory (324 building)

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Kammenzind, D.E.

    The 324 Facility Standards/Requirements Identification Document (S/RID) is comprised of twenty functional areas. Two of the twenty functional areas (Decontamination and Decommissioning and Environmental Restoration) were determined as nonapplicable functional areas and one functional area (Research and Development and Experimental Activities) was determined applicable, however, requirements are found in other functional areas and will not be duplicated. Each functional area follows as a separate chapter, either containing the S/RID or a justification for nonapplicability. The twenty functional areas listed below follow as chapters: 1. Management Systems; 2. Quality Assurance; 3. Configuration Management; 4. Training and Qualification; 5. Emergency Management; 6.more » Safeguards and Security; 7. Engineering Program; 8. Construction; 9. Operations; 10. Maintenance; 11. Radiation Protection; 12. Fire Protection; 13. Packaging and Transportation; 14. Environmental Restoration; 15. Decontamination and Decommissioning; 16. Waste Management; 17. Research and Development and Experimental Activities; 18. Nuclear Safety; 19. Occupational Safety and Health; 20. Environmental Protection.« less

  7. Quality-assurance plan for the analysis of suspended sediment by the U.S. Geological Survey in Montana

    USGS Publications Warehouse

    Dodge, Kent A.; Lambing, John H.

    2006-01-01

    A quality-assurance plan has been developed for use by the sediment laboratory of the U.S. Geological Survey Montana Water Science Center in conducting activities related to the analysis of suspended sediment. The plan documents quality-assurance policies for sediment-laboratory certification, personnel responsibilities and training, documentation requirements, and laboratory safety. The plan also documents quality-assurance procedures related to laboratory equipment and supplies, sample management, sample analysis, analytical quality control, and data management.

  8. 17 CFR 240.15c3-1e - Deductions for market and credit risk for certain brokers or dealers (Appendix E to 17 CFR 240...

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ... provisions of § 240.15c3-4 with respect to an internal risk management control system for the affiliate group... part of the internal risk management control system for the affiliate group, establish, document, and... risk management control system for the affiliate group that the ultimate holding company has...

  9. 17 CFR 240.15c3-1e - Deductions for market and credit risk for certain brokers or dealers (Appendix E to 17 CFR 240...

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ... provisions of § 240.15c3-4 with respect to an internal risk management control system for the affiliate group... part of the internal risk management control system for the affiliate group, establish, document, and... risk management control system for the affiliate group that the ultimate holding company has...

  10. 17 CFR 240.15c3-1e - Deductions for market and credit risk for certain brokers or dealers (Appendix E to 17 CFR 240...

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... provisions of § 240.15c3-4 with respect to an internal risk management control system for the affiliate group... part of the internal risk management control system for the affiliate group, establish, document, and... risk management control system for the affiliate group that the ultimate holding company has...

  11. 17 CFR 240.15c3-1e - Deductions for market and credit risk for certain brokers or dealers (Appendix E to 17 CFR 240...

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ... provisions of § 240.15c3-4 with respect to an internal risk management control system for the affiliate group... part of the internal risk management control system for the affiliate group, establish, document, and... risk management control system for the affiliate group that the ultimate holding company has...

  12. Recipe for Success: Digital Viewables

    NASA Technical Reports Server (NTRS)

    LaPha, Steven; Gaydos, Frank

    2014-01-01

    The Engineering Services Contract (ESC) and Information Management Communication Support contract (IMCS) at Kennedy Space Center (KSC) provide services to NASA in respect to flight and ground systems design and development. These groups provides the necessary tools, aid, and best practice methodologies required for efficient, optimized design and process development. The team is responsible for configuring and implementing systems, software, along with training, documentation, and administering standards. The team supports over 200 engineers and design specialists with the use of Windchill, Creo Parametric, NX, AutoCAD, and a variety of other design and analysis tools.

  13. Shuttle mission simulator requirements report, volume 1, revision C

    NASA Technical Reports Server (NTRS)

    Burke, J. F.

    1973-01-01

    The contractor tasks required to produce a shuttle mission simulator for training crew members and ground personnel are discussed. The tasks will consist of the design, development, production, installation, checkout, and field support of a simulator with two separate crew stations. The tasks include the following: (1) review of spacecraft changes and incorporation of appropriate changes in simulator hardware and software design, and (2) the generation of documentation of design, configuration management, and training used by maintenance and instructor personnel after acceptance for each of the crew stations.

  14. 76 FR 50276 - STP Nuclear Operating Company, South Texas Project, Units 1 and 2; Notice of Withdrawal of...

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-08-12

    ... revised the application of Risk- Managed Technical Specifications to Technical Specification 3.7.7, ``Control Room Makeup and Cleanup Filtration System.'' The purpose of the change was to correct a misapplication of the Configuration Risk Management Program that is currently allowed by the Technical...

  15. Role of the New South Wales Department of Primary Industries' Laboratory Information Management System (LIMS) in the 2007 equine influenza emergency animal disease response.

    PubMed

    Croft, M G; Fraser, G C; Gaul, W N

    2011-07-01

    A Laboratory Information Management System (LIMS) was used to manage the laboratory data and support planning and field activities as part of the response to the equine influenza outbreak in Australia in 2007. The database structure of the LIMS and the system configurations that were made to best handle the laboratory implications of the disease response are discussed. The operational aspects of the LIMS and the related procedures used at the laboratory to process the increased sample throughput are reviewed, as is the interaction of the LIMS with other corporate systems used in the management of the response. Outcomes from this tailored configuration and operation of the LIMS resulted in effective provision and control of the laboratory and laboratory information aspects of the response. The extent and immediate availability of the information provided from the LIMS was critical to some of the activities of key operatives involved in controlling the response. © 2011 The Authors. Australian Veterinary Journal © 2011 Australian Veterinary Association.

  16. Comparison of DOE and NIRMA approaches to configuration management programs

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Yang, E.Y.; Kulzick, K.C.

    One of the major management programs used for commercial, laboratory, and defense nuclear facilities is configuration management. The safe and efficient operation of a nuclear facility requires constant vigilance in maintaining the facility`s design basis with its as-built condition. Numerous events have occurred that can be attributed to (either directly or indirectly) the extent to which configuration management principles have been applied. The nuclear industry, as a whole, has been addressing this management philosophy with efforts taken on by its constituent professional organizations. The purpose of this paper is to compare and contrast the implementation plans for enhancing a configurationmore » management program as outlined in the U.S. Department of Energy`s (DOE`s) DOE-STD-1073-93, {open_quotes}Guide for Operational Configuration Management Program,{close_quotes} with the following guidelines developed by the Nuclear Information and Records Management Association (NIRMA): 1. PP02-1994, {open_quotes}Position Paper on Configuration Management{close_quotes} 2. PP03-1992, {open_quotes}Position Paper for Implementing a Configuration Management Enhancement Program for a Nuclear Facility{close_quotes} 3. PP04-1994 {open_quotes}Position Paper for Configuration Management Information Systems.{close_quotes}« less

  17. Sub-Network Access Control Technology Demonstrator: Software Design of the Network Management System

    DTIC Science & Technology

    2002-08-01

    Canadian Operational Fleet. Requirements The proposed network management solution must provide the normal monitoring and configuration mechanisms generally...Joint Warrior Inter- operability Demonstrations (JWID) m and the Communication System Network Inter- Operability (CSNI) Navy Network Trials. In short...management functional area normally includes two main functions: fault isolation and diagnosis, and restoration of the system . In short, an operator

  18. Energy management system for a rotary machine and method therefor

    DOEpatents

    Bowman, Michael John; Sinha, Gautam; Sheldon, Karl Edward

    2004-11-09

    In energy management system is provided for a power generating device having a working fluid intake in which the energy management system comprises an electrical dissipation device coupled to the power generating device and a dissipation device cooling system configured to direct a portion of a working fluid to the electrical dissipation device so as to provide thermal control to the electrical dissipation device.

  19. Test results of flight guidance for fuel conservative descents in a time-based metered air traffic environment. [terminal configured vehicle

    NASA Technical Reports Server (NTRS)

    Knox, C. E.; Person, L. H., Jr.

    1981-01-01

    The NASA developed, implemented, and flight tested a flight management algorithm designed to improve the accuracy of delivering an airplane in a fuel-conservative manner to a metering fix at a time designated by air traffic control. This algorithm provides a 3D path with time control (4D) for the TCV B-737 airplane to make an idle-thrust, clean configured (landing gear up, flaps zero, and speed brakes retracted) descent to arrive at the metering fix at a predetermined time, altitude, and airspeed. The descent path is calculated for a constant Mach/airspeed schedule from linear approximations of airplane performance with considerations given for gross weight, wind, and nonstandard pressure and temperature effects. The flight management descent algorithms are described and flight test results are presented.

  20. Managing operational documentation in the ALICE Detector Control System

    NASA Astrophysics Data System (ADS)

    Lechman, M.; Augustinus, A.; Bond, P.; Chochula, P.; Kurepin, A.; Pinazza, O.; Rosinsky, P.

    2012-12-01

    ALICE (A Large Ion Collider Experiment) is one of the big LHC (Large Hadron Collider) experiments at CERN in Geneve, Switzerland. The experiment is composed of 18 sub-detectors controlled by an integrated Detector Control System (DCS) that is implemented using the commercial SCADA package PVSSII. The DCS includes over 1200 network devices, over 1,000,000 monitored parameters and numerous custom made software components that are prepared by over 100 developers from all around the world. This complex system is controlled by a single operator via a central user interface. One of his/her main tasks is the recovery of anomalies and errors that may occur during operation. Therefore, clear, complete and easily accessible documentation is essential to guide the shifter through the expert interfaces of different subsystems. This paper describes the idea of the management of the operational documentation in ALICE using a generic repository that is built on a relational database and is integrated with the control system. The experience gained and the conclusions drawn from the project are also presented.

  1. NASA rotor systems research aircraft: Fixed-wing configuration flight-test results

    NASA Technical Reports Server (NTRS)

    Erickson, R. E.; Cross, J. L.; Kufeld, R. M.; Acree, C. W.; Nguyen, D.; Hodge, R. W.

    1986-01-01

    The fixed-wing, airplane configuration flight-test results of the Rotor System Research Aircraft (RSRA), NASA 740, at Ames/Dryden Flight Research Center are documented. Fourteen taxi and flight tests were performed from December 1983 to October 1984. This was the first time the RSRA was flown with the main rotor removed; the tail rotor was installed. These tests confirmed that the RSRA is operable as a fixed-wing aircraft. Data were obtained for various takeoff and landing distances, control sensitivity, trim and dynamics stability characteristics, performance rotor-hub drag, and acoustics signature. Stability data were obtained with the rotor hub both installed and removed. The speed envelope was developed to 261 knots true airspeed (KTAS), 226 knots calibrated airspeed (KCAS) at 10,000 ft density altitude. The airplane was configured at 5 deg. wing incidence with 5 deg. wing flaps as a normal configuration. Level-flight data were acquired at 167 KCAS for wing incidence from 0 to 10 deg. Step inputs and doublet inputs of various magnitudes were utilized to acquire dynamic stability and control sensitivity data. Sine-wave inputs of constantly increasing frequency were used to generate parameter identification data. The maximum load factor attained was 2.34 g at 206 KCAS.

  2. How to implement security controls for an information security program at CBRN facilities

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Lenaeus, Joseph D.; O'Neil, Lori Ross; Leitch, Rosalyn M.

    This document was prepared by PNNL within the framework of Project 19 of the European Union Chemical Biological Radiological and Nuclear Risk Mitigation Centres of Excellence Initiative entitled, ''Development of procedures and guidelines to create and improve secure information management systems and data exchange mechanisms for CBRN materials under regulatory control.'' It provides management and workers at CBRN facilities, parent organization managers responsible for those facilities, and regulatory agencies (governmental and nongovernmental) with guidance on the best practices for protecting information security. The security mitigation approaches presented in this document were chosen because they present generally accepted guidance in anmore » easy-to-understand manner, making it easier for facility personnel to grasp key concepts and envision how security controls could be implemented by the facility. This guidance is presented from a risk management perspective.« less

  3. Evaluation of automated decisionmaking methodologies and development of an integrated robotic system simulation, volume 2, part 1. Appendix A: Software documentation

    NASA Technical Reports Server (NTRS)

    Lowrie, J. W.; Fermelia, A. J.; Haley, D. C.; Gremban, K. D.; Vanbaalen, J.; Walsh, R. W.

    1982-01-01

    Documentation of the preliminary software developed as a framework for a generalized integrated robotic system simulation is presented. The program structure is composed of three major functions controlled by a program executive. The three major functions are: system definition, analysis tools, and post processing. The system definition function handles user input of system parameters and definition of the manipulator configuration. The analysis tools function handles the computational requirements of the program. The post processing function allows for more detailed study of the results of analysis tool function executions. Also documented is the manipulator joint model software to be used as the basis of the manipulator simulation which will be part of the analysis tools capability.

  4. Results of investigations on a 0.004-scale 140C modified configuration space shuttle vehicle orbiter model (74-0) in the NASA/Langley Research Center hypersonic helium tunnel

    NASA Technical Reports Server (NTRS)

    Hawthorne, P. J.

    1975-01-01

    Data obtained during a wind tunnel test of a 0.004-scale 140C modified configuration SSV orbiter are documented. The test was conducted during August 1974 with 80 occupancy hours charged, and all runs were conducted at a nominal Mach number of 20 and at Reynolds numbers of 0.7, 1.0, 1.8, and 1,100,000 based on body length. The complete -140C modified model was tested with various elevon settings at angles of attack from 10 to 50 degrees at zero yaw and from angles of sideslip of -10 to +10 at 35 deg angle of attack. The purpose of this test was to obtain high hypersonic longitudinal and lateral-directional stability and control characteristics of the updated SSV configuration.

  5. Spaceborne computer executive routine functional design specification. Volume 2: Computer executive design for space station/base

    NASA Technical Reports Server (NTRS)

    Kennedy, J. R.; Fitzpatrick, W. S.

    1971-01-01

    The computer executive functional system design concepts derived from study of the Space Station/Base are presented. Information Management System hardware configuration as directly influencing the executive design is reviewed. The hardware configuration and generic executive design requirements are considered in detail in a previous report (System Configuration and Executive Requirements Specifications for Reusable Shuttle and Space Station/Base, 9/25/70). This report defines basic system primitives and delineates processes and process control. Supervisor states are considered for describing basic multiprogramming and multiprocessing systems. A high-level computer executive including control of scheduling, allocation of resources, system interactions, and real-time supervisory functions is defined. The description is oriented to provide a baseline for a functional simulation of the computer executive system.

  6. 78 FR 72903 - Collection of Information Under Review by Office of Management and Budget

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-12-04

    ... will address them accordingly. Viewing Comments and Documents To view comments, as well as documents.... This information is required to control vessel traffic, develop contingency plans and enforce...

  7. To Meet or Not To Meet Physical vs. Virtual Configuration Control Board

    NASA Technical Reports Server (NTRS)

    Rice, Shelley

    2017-01-01

    This presentation will define the CCB, discuss its functions and members. We will look into traditional processes of managing change control via the CCB meeting and advanced practices utilizing enhanced product tools and technologies. Well step through a summary of the feedback from the community of CM professionals at NASA Goddard Space Flight Center of best practices as well as pros and cons for facilitating both a physical CCB and managing stakeholder approvals in a virtual environment. Attendees will come away with current industry strategies to determine if process for managing change control and approvals can be streamlined within their local work environments.

  8. Development of Evidence-Based Health Policy Documents in Developing Countries: A Case of Iran

    PubMed Central

    Imani-Nasab, Mohammad Hasan; Seyedin, Hesam; Majdzadeh, Reza; Yazdizadeh, Bahareh; Salehi, Masoud

    2014-01-01

    Background: Evidence-based policy documents that are well developed by senior civil servants and are timely available can reduce the barriers to evidence utilization by health policy makers. This study examined the barriers and facilitators in developing evidence-based health policy documents from the perspective of their producers in a developing country. Methods: In a qualitative study with a framework analysis approach, we conducted semi-structured interviews using purposive and snowball sampling. A qualitative analysis software (MAXQDA-10) was used to apply the codes and manage the data. This study was theory-based and the results were compared to exploratory studies about the factors influencing evidence-based health policymaking. Results: 18 codes and three main themes of behavioral, normative, and control beliefs were identified. Factors that influence the development of evidence-based policy documents were identified by the participants: behavioral beliefs included quality of policy documents, use of resources, knowledge and innovation, being time-consuming and contextualization; normative beliefs included policy authorities, policymakers, policy administrators, and co-workers; and control beliefs included recruitment policy, performance management, empowerment, management stability, physical environment, access to evidence, policy making process, and effect of other factors. Conclusion: Most of the cited barriers to the development of evidence-based policy were related to control beliefs, i.e. barriers at the organizational and health system levels. This study identified the factors that influence the development of evidence-based policy documents based on the components of the theory of planned behavior. But in exploratory studies on evidence utilization by health policymakers, the identified factors were only related to control behaviors. This suggests that the theoretical approach may be preferable to the exploratory approach in identifying the barriers and facilitators of a behavior. PMID:24762343

  9. Development of evidence-based health policy documents in developing countries: a case of Iran.

    PubMed

    Imani-Nasab, Mohammad Hasan; Seyedin, Hesam; Majdzadeh, Reza; Yazdizadeh, Bahareh; Salehi, Masoud

    2014-02-07

    Evidence-based policy documents that are well developed by senior civil servants and are timely available can reduce the barriers to evidence utilization by health policy makers. This study examined the barriers and facilitators in developing evidence-based health policy documents from the perspective of their producers in a developing country. In a qualitative study with a framework analysis approach, we conducted semi-structured interviews using purposive and snowball sampling. A qualitative analysis software (MAXQDA-10) was used to apply the codes and manage the data. This study was theory-based and the results were compared to exploratory studies about the factors influencing evidence-based health policy-making. 18 codes and three main themes of behavioral, normative, and control beliefs were identified. Factors that influence the development of evidence-based policy documents were identified by the participants: behavioral beliefs included quality of policy documents, use of resources, knowledge and innovation, being time-consuming and contextualization; normative beliefs included policy authorities, policymakers, policy administrators, and co-workers; and control beliefs included recruitment policy, performance management, empowerment, management stability, physical environment, access to evidence, policy making process, and effect of other factors. Most of the cited barriers to the development of evidence-based policy were related to control beliefs, i.e. barriers at the organizational and health system levels. This study identified the factors that influence the development of evidence-based policy documents based on the components of the theory of planned behavior. But in exploratory studies on evidence utilization by health policymakers, the identified factors were only related to control behaviors. This suggests that the theoretical approach may be preferable to the exploratory approach in identifying the barriers and facilitators of a behavior.

  10. Requirements management for Gemini Observatory: a small organization with big development projects

    NASA Astrophysics Data System (ADS)

    Close, Madeline; Serio, Andrew; Cordova, Martin; Hardie, Kayla

    2016-08-01

    Gemini Observatory is an astronomical observatory operating two premier 8m-class telescopes, one in each hemisphere. As an operational facility, a majority of Gemini's resources are spent on operations however the observatory undertakes major development projects as well. Current projects include new facility science instruments, an operational paradigm shift to full remote operations, and new operations tools for planning, configuration and change control. Three years ago, Gemini determined that a specialized requirements management tool was needed. Over the next year, the Gemini Systems Engineering Group investigated several tools, selected one for a trial period and configured it for use. Configuration activities including definition of systems engineering processes, development of a requirements framework, and assignment of project roles to tool roles. Test projects were implemented in the tool. At the conclusion of the trial, the group determined that the Gemini could meet its requirements management needs without use of a specialized requirements management tool, and the group identified a number of lessons learned which are described in the last major section of this paper. These lessons learned include how to conduct an organizational needs analysis prior to pursuing a tool; caveats concerning tool criteria and the selection process; the prerequisites and sequence of activities necessary to achieve an optimum configuration of the tool; the need for adequate staff resources and staff training; and a special note regarding organizations in transition and archiving of requirements.

  11. Developing freeway and incident management systems using the national ITS architecture

    DOT National Transportation Integrated Search

    1998-08-01

    This is one of a series of documents providing support for deploying Intelligent Transportation Systems (ITS). This series addresses Traffic Signal Control Systems, Freeway and Incident Management Systems, Transit Management Systems, and Traveler Inf...

  12. Geosynchronous Microwave Atmospheric Sounding Radiometer (MASR) feasibility studies. Volume 1: Management summary

    NASA Technical Reports Server (NTRS)

    1978-01-01

    The mission of the microwave atmospheric sounding radiometer (MASR) is to collect data to aid in the observation and prediction of severe storms. The geosynchronous orbit allows the continuous atmospheric measurement needed to resolve mesoscale dynamics. The instrument may operate in conjunction with this document, Volume 1 - Management, which summarizes the highlights of final reports on both the radiometer instrument and antenna studies. The radiometer instrument summary includes a synopsis of Volume 2 - Radiometer Receiver Feasibility, including design, recommended configuration, performance estimates, and weight and power estimates. The summary of the antenna study includes a synopsis of Volume 3 - Antenna Feasibility, including preliminary design tradeoffs, performance of selected design, and details of the mechanical/thermal design.

  13. Establishing a Product Baseline for Global Positioning System Satellites through Functional and Physical Configuration Audits

    DTIC Science & Technology

    2011-09-01

    PBL may see changes as the design is actually implemented . Such changes are typically for practical reasons of adapting to either specific...shall use a configuration management approach to establish and control product attributes and the product baseline across the total system life cycle... practice that helps prevent government interference in subcontracts, holds the prime contractor accountable for their end product (s), limits the potential

  14. STV engine design considerations

    NASA Technical Reports Server (NTRS)

    1991-01-01

    The topics covered include the following: (1) engine design criteria and issues; (2) design requirements for man rating; (3) test requirements for man rating; (4) design requirements for space basing; (5) engine operation requirements; (6) health monitoring; (7) lunar transfer vehicle (LTV) feed system; (8) lunar excursion vehicle (LEV) propellant system; (9) area ratio gimbal angle limits; (10) reaction control system; and (11) engine configuration and characteristics. This document is presented in viewgraph form.

  15. Space shuttle/food system study

    NASA Technical Reports Server (NTRS)

    1974-01-01

    This document establishes the Functional, physical and performance interface requirements are studied between the space shuttle orbiter and the galley water system, the orbiter and the galley electrical system, and the orbiter and the galley structural system. Control of the configuration and design of the applicable interfacing items is intended to maintain compatibility between co-functioning and physically mating items and to assure those performance criteria that are dependent upon the interfacing items.

  16. Improvements and modifications to the NASA microwave signature acquisition system

    NASA Technical Reports Server (NTRS)

    Jean, B. R.; Newton, R. W.; Warren, G. L.; Clark, B. V.; Zajicek, J. L.

    1978-01-01

    A user oriented description of the modified and upgraded Microwave Signature Acquisition System is provided. The present configuration of the sensor system and its operating characteristics are documented and a step-by-step operating procedure provides instruction for mounting the antenna truss assembly, readying the system for data acquisition, and for controlling the system during the data collection sequence. The resulting data products are also identified.

  17. Cargo Movement Operations System (CMOS). Final Software Design Document. Increment III. (PC Unix - Air Force Configuration)

    DTIC Science & Technology

    1991-07-03

    required changes to this matrix. CMOS PMO ACCEPTS COMMENT: YES [ ] NO [ ] ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN...this appendix should be updated to include all necessary changes. CMOS PMO ACCEPTS COMMENT: YES [ ] NO [ ] ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION...ERCI ACCEPTS COMMENT: YES [ ] NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED [ ] ORIGINATOR CONTROL NUMBER: SDD3-0004 PROGRAM OFFICE

  18. The NASA Langley laminar-flow-control experiment on a swept, supercritical airfoil: Evaluation of initial perforated configuration

    NASA Technical Reports Server (NTRS)

    Harris, Charles D.; Brooks, Cuyler W., Jr.; Clukey, Patricia G.; Stack, John P.

    1992-01-01

    The initial evaluation of a large-chord, swept, supercritical airfoil incorporating an active laminar-flow-control (LFC) suction system with a perforated upper surface is documented in a chronological manner, and the deficiencies in the suction capability of the perforated panels as designed are described. The experiment was conducted in the Langley 8-Foot Transonic Pressure Tunnel. Also included is an evaluation of the influence of the proximity of the tunnel liner to the upper surface of the airfoil pressure distribution.

  19. Pairwise Trajectory Management (PTM): Concept Description and Documentation

    NASA Technical Reports Server (NTRS)

    Jones, Kenneth M.; Graff, Thomas J.; Carreno, Victor; Chartrand, Ryan C.; Kibler, Jennifer L.

    2018-01-01

    Pairwise Trajectory Management (PTM) is an Interval Management (IM) concept that utilizes airborne and ground-based capabilities to enable the implementation of airborne pairwise spacing capabilities in oceanic regions. The goal of PTM is to use airborne surveillance and tools to manage an "at or greater than" inter-aircraft spacing. Due to the accuracy of Automatic Dependent Surveillance-Broadcast (ADS-B) information and the use of airborne spacing guidance, the minimum PTM spacing distance will be less than distances a controller can support with current automation systems that support oceanic operations. Ground tools assist the controller in evaluating the traffic picture and determining appropriate PTM clearances to be issued. Avionics systems provide guidance information that allows the flight crew to conform to the PTM clearance issued by the controller. The combination of a reduced minimum distance and airborne spacing management will increase the capacity and efficiency of aircraft operations at a given altitude or volume of airspace. This document provides an overview of the proposed application, a description of several key scenarios, a high level discussion of expected air and ground equipment and procedure changes, a description of a NASA human-machine interface (HMI) prototype for the flight crew that would support PTM operations, and initial benefits analysis results. Additionally, included as appendices, are the following documents: the PTM Operational Services and Environment Definition (OSED) document and a companion "Future Considerations for the Pairwise Trajectory Management (PTM) Concept: Potential Future Updates for the PTM OSED" paper, a detailed description of the PTM algorithm and PTM Limit Mach rules, initial PTM safety requirements and safety assessment documents, a detailed description of the design, development, and initial evaluations of the proposed flight crew HMI, an overview of the methodology and results of PTM pilot training requirements focus group and human-in-the-loop testing activities, and the PTM Pilot Guide.

  20. Launch Vehicle Control Center Architectures

    NASA Technical Reports Server (NTRS)

    Watson, Michael D.; Epps, Amy; Woodruff, Van; Vachon, Michael Jacob; Monreal, Julio; Williams, Randall; McLaughlin, Tom

    2014-01-01

    This analysis is a survey of control center architectures of the NASA Space Launch System (SLS), United Launch Alliance (ULA) Atlas V and Delta IV, and the European Space Agency (ESA) Ariane 5. Each of these control center architectures have similarities in basic structure, and differences in functional distribution of responsibilities for the phases of operations: (a) Launch vehicles in the international community vary greatly in configuration and process; (b) Each launch site has a unique processing flow based on the specific configurations; (c) Launch and flight operations are managed through a set of control centers associated with each launch site, however the flight operations may be a different control center than the launch center; and (d) The engineering support centers are primarily located at the design center with a small engineering support team at the launch site.

  1. Configuration Aerodynamics: Past - Present - Future

    NASA Technical Reports Server (NTRS)

    Wood, Richard M.; Agrawal, Shreekant; Bencze, Daniel P.; Kulfan, Robert M.; Wilson, Douglas L.

    1999-01-01

    The Configuration Aerodynamics (CA) element of the High Speed Research (HSR) program is managed by a joint NASA and Industry team, referred to as the Technology Integration Development (ITD) team. This team is responsible for the development of a broad range of technologies for improved aerodynamic performance and stability and control characteristics at subsonic to supersonic flight conditions. These objectives are pursued through the aggressive use of advanced experimental test techniques and state of the art computational methods. As the HSR program matures and transitions into the next phase the objectives of the Configuration Aerodynamics ITD are being refined to address the drag reduction needs and stability and control requirements of High Speed Civil Transport (HSCT) aircraft. In addition, the experimental and computational tools are being refined and improved to meet these challenges. The presentation will review the work performed within the Configuration Aerodynamics element in 1994 and 1995 and then discuss the plans for the 1996-1998 time period. The final portion of the presentation will review several observations of the HSR program and the design activity within Configuration Aerodynamics.

  2. Managing a Real-Time Embedded Linux Platform with Buildroot

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Diamond, J.; Martin, K.

    2015-01-01

    Developers of real-time embedded software often need to build the operating system, kernel, tools and supporting applications from source to work with the differences in their hardware configuration. The first attempts to introduce Linux-based real-time embedded systems into the Fermilab accelerator controls system used this approach but it was found to be time-consuming, difficult to maintain and difficult to adapt to different hardware configurations. Buildroot is an open source build system with a menu-driven configuration tool (similar to the Linux kernel build system) that automates this process. A customized Buildroot [1] system has been developed for use in the Fermilabmore » accelerator controls system that includes several hardware configuration profiles (including Intel, ARM and PowerPC) and packages for Fermilab support software. A bootable image file is produced containing the Linux kernel, shell and supporting software suite that varies from 3 to 20 megabytes large – ideal for network booting. The result is a platform that is easier to maintain and deploy in diverse hardware configurations« less

  3. Image and information management system

    NASA Technical Reports Server (NTRS)

    Robertson, Tina L. (Inventor); Raney, Michael C. (Inventor); Dougherty, Dennis M. (Inventor); Kent, Peter C. (Inventor); Brucker, Russell X. (Inventor); Lampert, Daryl A. (Inventor)

    2009-01-01

    A system and methods through which pictorial views of an object's configuration, arranged in a hierarchical fashion, are navigated by a person to establish a visual context within the configuration. The visual context is automatically translated by the system into a set of search parameters driving retrieval of structured data and content (images, documents, multimedia, etc.) associated with the specific context. The system places ''hot spots'', or actionable regions, on various portions of the pictorials representing the object. When a user interacts with an actionable region, a more detailed pictorial from the hierarchy is presented representing that portion of the object, along with real-time feedback in the form of a popup pane containing information about that region, and counts-by-type reflecting the number of items that are available within the system associated with the specific context and search filters established at that point in time.

  4. Image and information management system

    NASA Technical Reports Server (NTRS)

    Robertson, Tina L. (Inventor); Kent, Peter C. (Inventor); Raney, Michael C. (Inventor); Dougherty, Dennis M. (Inventor); Brucker, Russell X. (Inventor); Lampert, Daryl A. (Inventor)

    2007-01-01

    A system and methods through which pictorial views of an object's configuration, arranged in a hierarchical fashion, are navigated by a person to establish a visual context within the configuration. The visual context is automatically translated by the system into a set of search parameters driving retrieval of structured data and content (images, documents, multimedia, etc.) associated with the specific context. The system places hot spots, or actionable regions, on various portions of the pictorials representing the object. When a user interacts with an actionable region, a more detailed pictorial from the hierarchy is presented representing that portion of the object, along with real-time feedback in the form of a popup pane containing information about that region, and counts-by-type reflecting the number of items that are available within the system associated with the specific context and search filters established at that point in time.

  5. CAPSULE REPORT - MANAGING CYANIDE IN METAL FINISHING

    EPA Science Inventory

    The purpose of this document is to provide guidance to surface finishing manufacturers, metal finishing decision maker and regulators on management practices and control technologies for managing cyanide in the workplace. This information can benefit key industry stakeholder gro...

  6. Incident management under SCAT adaptive control system : FAST-TRAC phase III deliverable. #11, Final report on incident management under SCATS adaptive control system

    DOT National Transportation Integrated Search

    1998-04-01

    The report documents the results of a study designed to test the effectiveness of ATMS and ATIS strategies to reduce delay resulting from an incident. The study had two main sections: a simulation study to test the effectiveness of several control st...

  7. Engineering Changes in Product Design - A Review

    NASA Astrophysics Data System (ADS)

    Karthik, K.; Janardhan Reddy, K., Dr

    2016-09-01

    Changes are fundamental to product development. Engineering changes are unavoidable and can arise at any phase of the product life cycle. The consideration of market requirements, customer/user feedbacks, manufacturing constraints, design innovations etc., turning them into viable products can be accomplished when product change is managed properly. In the early design cycle, informal changes are accepted. However, changes become formal when its complexity and cost increases, and as product matures. To maximize the market shares, manufacturers have to effectively and efficiently manage engineering changes by means of Configuration Control. The paper gives a broad overview about ‘Engineering Change Management’ (ECM) through configuration management and its implications in product design. The aim is to give an idea and understanding about the engineering changes in product design scenario to the new researchers. This paper elaborates the significant aspect of managing the engineering changes and the importance of ECM in a product life cycle.

  8. A Recipe for Streamlining Mission Management

    NASA Technical Reports Server (NTRS)

    Mitchell, Andrew E.; Semancik, Susan K.

    2004-01-01

    This paper describes a project's design and implementation for streamlining mission management with knowledge capture processes across multiple organizations of a NASA directorate. Thc project's focus is on standardizing processes and reports; enabling secure information access and case of maintenance; automating and tracking appropriate workflow rules through process mapping; and infusing new technologies. This paper will describe a small team's experiences using XML technologies through an enhanced vendor suite of applications integrated on Windows-based platforms called the Wallops Integrated Scheduling and Document Management System (WISDMS). This paper describes our results using this system in a variety of endeavors, including providing range project scheduling and resource management for a Range and Mission Management Office; implementing an automated Customer Feedback system for a directorate; streamlining mission status reporting across a directorate; and initiating a document management, configuration management and portal access system for a Range Safety Office's programs. The end result is a reduction of the knowledge gap through better integration and distribution of information, improved process performance, automated metric gathering, and quicker identification of problem areas and issues. However, the real proof of the pudding comes through overcoming the user's reluctance to replace familiar, seasoned processes with new technology ingredients blended with automated procedures in an untested recipe. This paper shares some of the team's observations that led to better implementation techniques, as well as an IS0 9001 Best Practices citation. This project has provided a unique opportunity to advance NASA's competency in new technologies, as well as to strategically implement them within an organizational structure, while wetting the appetite for continued improvements in mission management.

  9. Analysis and control of the METC fluid bed gasifier. Final report (includes technical progress report for October 1994--January 1995), September 1994--September 1996

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    NONE

    1996-09-01

    This document presents a modeling and control study of the Fluid Bed Gasification (FBG) unit at the Morgantown Energy Technology Center (METC). The work is performed under contract no. DE-FG21-94MC31384. The purpose of this study is to generate a simple FBG model from process data, and then use the model to suggest an improved control scheme which will improve operation of the gasifier. The work first developes a simple linear model of the gasifier, then suggests an improved gasifier pressure and MGCR control configuration, and finally suggests the use of a multivariable control strategy for the gasifier.

  10. Tools to manage the enterprise-wide picture archiving and communications system environment.

    PubMed

    Lannum, L M; Gumpf, S; Piraino, D

    2001-06-01

    The presentation will focus on the implementation and utilization of a central picture archiving and communications system (PACS) network-monitoring tool that allows for enterprise-wide operations management and support of the image distribution network. The MagicWatch (Siemens, Iselin, NJ) PACS/radiology information system (RIS) monitoring station from Siemens has allowed our organization to create a service support structure that has given us proactive control of our environment and has allowed us to meet the service level performance expectations of the users. The Radiology Help Desk has used the MagicWatch PACS monitoring station as an applications support tool that has allowed the group to monitor network activity and individual systems performance at each node. Fast and timely recognition of the effects of single events within the PACS/RIS environment has allowed the group to proactively recognize possible performance issues and resolve problems. The PACS/operations group performs network management control, image storage management, and software distribution management from a single, central point in the enterprise. The MagicWatch station allows for the complete automation of software distribution, installation, and configuration process across all the nodes in the system. The tool has allowed for the standardization of the workstations and provides a central configuration control for the establishment and maintenance of the system standards. This report will describe the PACS management and operation prior to the implementation of the MagicWatch PACS monitoring station and will highlight the operational benefits of a centralized network and system-monitoring tool.

  11. Wiring harnesses documented by punched-card technique

    NASA Technical Reports Server (NTRS)

    Hicks, W. W.; Kloezeman, W. G.

    1970-01-01

    Cards representing a connector are punched, sorted, and then used to printout wiring documentation for that connector. When wiring changes are made, new cards are punched and the wiring documentation is reprinted to reflect the latest configuration.

  12. SNOMED CT's RF2: Is the future bright?

    PubMed

    Ceusters, Werner

    2011-01-01

    SNOMED CT's new RF2 format is said to come with features for better configuration management of the SNOMED vocabulary, thereby accommodating evolving requirements without the need for further fundamental change in the foreseeable future. Although the available documentation is not yet convincing enough to support this claim, the newly introduced Model Component hierarchy and associated reference set mechanism seem to hold real promise of being able to deal successfully with a number of ontological issues that have been discussed in the recent literature. Backed up by a study of the old and new format and of the relevant literature and documentation, three recommendations are presented that would free SNOMED CT from use-mention confusions, unclear referencing of real-world entities and uninformative reasons for change in a way that does not force SNOMED CT to take a specific philosophical or ontological position.

  13. The space shuttle ascent vehicle aerodynamic challenges configuration design and data base development

    NASA Technical Reports Server (NTRS)

    Dill, C. C.; Young, J. C.; Roberts, B. B.; Craig, M. K.; Hamilton, J. T.; Boyle, W. W.

    1985-01-01

    The phase B Space Shuttle systems definition studies resulted in a generic configuration consisting of a delta wing orbiter, and two solid rocket boosters (SRB) attached to an external fuel tank (ET). The initial challenge facing the aerodynamic community was aerodynamically optimizing, within limits, this configuration. As the Shuttle program developed and the sensitivities of the vehicle to aerodynamics were better understood the requirements of the aerodynamic data base grew. Adequately characterizing the vehicle to support the various design studies exploded the size of the data base to proportions that created a data modeling/management challenge for the aerodynamicist. The ascent aerodynamic data base originated primarily from wind tunnel test results. The complexity of the configuration rendered conventional analytic methods of little use. Initial wind tunnel tests provided results which included undesirable effects from model support tructure, inadequate element proximity, and inadequate plume simulation. The challenge to improve the quality of test results by determining the extent of these undesirable effects and subsequently develop testing techniques to eliminate them was imposed on the aerodynamic community. The challenges to the ascent aerodynamics community documented are unique due to the aerodynamic complexity of the Shuttle launch. Never before was such a complex vehicle aerodynamically characterized. The challenges were met with innovative engineering analyses/methodology development and wind tunnel testing techniques.

  14. An integrated power/attitude control system /IPACS/ for space vehicle application

    NASA Technical Reports Server (NTRS)

    Anderson, W. W.; Keckler, C. R.

    1973-01-01

    An integrated power and attitude control system (IPACS) concept with potential application to a broad class of space missions is discussed. The concept involves the storage and supply on demand of electrical energy in rotating flywheels while simultaneously providing control torques by controlled precession of the flywheels. The system is thus an alternative to the storage batteries used on present spacecraft while providing similar capability for attitude control as that represented by a control moment gyroscope (CMG) system. Potential IPACS configurations discussed include single- and double-rotor double-gimbal IPACS units. Typical sets of control laws which would manage the momentum and energy exchange between the IPACS and a typical space vehicle are discussed. Discussion of a simulation of a typical potential IPACS configuration and candidate mission concerned with pointing capability, power supply and demand flow, and discussion of the interactions between stabilization and control requirements and power flow requirements are presented.

  15. 77 FR 50162 - Importer of Controlled Substances; Notice of Application; Clinical Supplies Management, Inc.

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-08-20

    ... DEPARTMENT OF JUSTICE Drug Enforcement Administration Importer of Controlled Substances; Notice of Application; Clinical Supplies Management, Inc. Correction In notice document 2012-19197 appearing on pages 47109-47110 in the issue of Tuesday, August 7, 2012, make the following corrections: 1. On page 47109...

  16. 46 CFR 162.060-30 - Testing requirements for ballast water management system (BWMS) components.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... production configuration: (1) A resonance search vertically up and down, horizontally from side to side, and...) Components that may be installed in enclosed spaces that are environmentally controlled, including an engine...

  17. 46 CFR 162.060-30 - Testing requirements for ballast water management system (BWMS) components.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... production configuration: (1) A resonance search vertically up and down, horizontally from side to side, and...) Components that may be installed in enclosed spaces that are environmentally controlled, including an engine...

  18. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bartoletti, T.

    SPI/U3.1 consists of five tools used to assess and report the security posture of computers running the UNIX operating system. The tools are: Access Control Test: A rule-based system which identifies sequential dependencies in UNIX access controls. Binary Inspector Tool: Evaluates the release status of system binaries by comparing a crypto-checksum to provide table entries. Change Detection Tool: Maintains and applies a snapshot of critical system files and attributes for purposes of change detection. Configuration Query Language: Accepts CQL-based scripts (provided) to evaluate queries over the status of system files, configuration of services and many other elements of UNIX systemmore » security. Password Security Inspector: Tests for weak or aged passwords. The tools are packaged with a forms-based user interface providing on-line context-sensistive help, job scheduling, parameter management and output report management utilities. Tools may be run independent of the UI.« less

  19. DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bartoletti, Tony

    SPI/U3.2 consists of five tools used to assess and report the security posture of computers running the UNIX operating system. The tools are: Access Control Test: A rule-based system which identifies sequential dependencies in UNIX access controls. Binary Authentication Tool: Evaluates the release status of system binaries by comparing a crypto-checksum to provide table entries. Change Detection Tool: Maintains and applies a snapshot of critical system files and attributes for purposes of change detection. Configuration Query Language: Accepts CQL-based scripts (provided) to evaluate queries over the status of system files, configuration of services and many other elements of UNIX systemmore » security. Password Security Inspector: Tests for weak or aged passwords. The tools are packaged with a forms-based user interface providing on-line context-sensistive help, job scheduling, parameter management and output report management utilities. Tools may be run independent of the UI.« less

  20. Control and applications of cooperating disparate robotic manipulators relevant to nuclear waste management

    NASA Technical Reports Server (NTRS)

    Lew, Jae Young; Book, Wayne J.

    1991-01-01

    Remote handling in nuclear waste management requires a robotic system with precise motion as well as a large workspace. The concept of a small arm mounted on the end of a large arm may satisfy such needs. However, the performance of such a serial configuration lacks payload capacity which is a crucial factor for handling a massive object. Also, this configuration induces more flexibility on the structure. To overcome these problems, the topology of bracing the tip of the small arm (not the large arm) and having an end effector in the middle of the chain is proposed in this paper. Also, control of these cooperating disparate manipulators is accomplished in computer simulations. Thus, this robotic system can have the accuracy of the small arm, and at the same time, it can have the payload capacity and large workspace of the large arm.

  1. SPI/U3.2. Security Profile Inspector for UNIX Systems

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Bartoletti, A.

    1994-08-01

    SPI/U3.2 consists of five tools used to assess and report the security posture of computers running the UNIX operating system. The tools are: Access Control Test: A rule-based system which identifies sequential dependencies in UNIX access controls. Binary Authentication Tool: Evaluates the release status of system binaries by comparing a crypto-checksum to provide table entries. Change Detection Tool: Maintains and applies a snapshot of critical system files and attributes for purposes of change detection. Configuration Query Language: Accepts CQL-based scripts (provided) to evaluate queries over the status of system files, configuration of services and many other elements of UNIX systemmore » security. Password Security Inspector: Tests for weak or aged passwords. The tools are packaged with a forms-based user interface providing on-line context-sensistive help, job scheduling, parameter management and output report management utilities. Tools may be run independent of the UI.« less

  2. PIV Logon Configuration Guidance

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Lee, Glen Alan

    This document details the configurations and enhancements implemented to support the usage of federal Personal Identity Verification (PIV) Card for logon on unclassified networks. The guidance is a reference implementation of the configurations and enhancements deployed at the Los Alamos National Laboratory (LANL) by Network and Infrastructure Engineering – Core Services (NIE-CS).

  3. Propulsion/airframe integration issues for waverider aircraft

    NASA Technical Reports Server (NTRS)

    Blankson, Isaiah M.; Hagseth, Paul

    1993-01-01

    While many propulsion concepts and technologies developed for nonwaverider-type hypersonic vehicles may apply to waveriders, some aspects of these configurations require unique technological approaches. An evaluation is made of such distinctive opportunities in the cases of engine cycle selection, inlets, nozzle designs and integration, longitudinal stability, and thermal management. Also discussed are waverider requirements for control surface effectiveness, inlet boundary layer ingestion effects, and structural/configurational optimization, giving attention to trades in volumetric/structural efficiency and vehicle L/D.

  4. LCS Content Document Application

    NASA Technical Reports Server (NTRS)

    Hochstadt, Jake

    2011-01-01

    My project at KSC during my spring 2011 internship was to develop a Ruby on Rails application to manage Content Documents..A Content Document is a collection of documents and information that describes what software is installed on a Launch Control System Computer. It's important for us to make sure the tools we use everyday are secure, up-to-date, and properly licensed. Previously, keeping track of the information was done by Excel and Word files between different personnel. The goal of the new application is to be able to manage and access the Content Documents through a single database backed web application. Our LCS team will benefit greatly with this app. Admin's will be able to login securely to keep track and update the software installed on each computer in a timely manner. We also included exportability such as attaching additional documents that can be downloaded from the web application. The finished application will ease the process of managing Content Documents while streamlining the procedure. Ruby on Rails is a very powerful programming language and I am grateful to have the opportunity to build this application.

  5. SCAILET - An intelligent assistant for satellite ground terminal operations

    NASA Technical Reports Server (NTRS)

    Shahidi, A. K.; Crapo, J. A.; Schlegelmilch, R. F.; Reinhart, R. C.; Petrik, E. J.; Walters, J. L.; Jones, R. E.

    1992-01-01

    Space communication artificial intelligence for the link evaluation terminal (SCAILET) is an experimenter interface to the link evaluation terminal (LET) developed by NASA through the application of artificial intelligence to an advanced ground terminal. The high-burst-rate (HBR) LET provides the required capabilities for wideband communications experiments with the advanced communications technology satellite (ACTS). The HBR-LET terminal consists of seven major subsystems and is controlled and monitored by a minicomputer through an IEEE-488 or RS-232 interface. Programming scripts configure HBR-LET and allow data acquisition but are difficult to use and therefore the full capabilities of the system are not utilized. An intelligent assistant module was developed as part of the SCAILET module and solves problems encountered during configuration of the HBR-LET system. This assistant is a graphical interface with an expert system running in the background and allows users to configure instrumentation, program sequences and reference documentation. The simplicity of use makes SCAILET a superior interface to the ASCII terminal and continuous monitoring allows nearly flawless configuration and execution of HBR-LET experiments.

  6. [Consensus document for the detection and management of chronic kidney disease].

    PubMed

    Martínez-Castelao, Alberto; Górriz, José L; Bover, Jordi; Segura-de la Morena, Julián; Cebollada, Jesús; Escalada, Javier; Esmatjes, Enric; Fácila, Lorenzo; Gamarra, Javier; Gràcia, Silvia; Hernández-Moreno, Julio; Llisterri-Caro, José L; Mazón, Pilar; Montañés, Rosario; Morales-Olivas, Francisco; Muñoz-Torres, Manuel; de Pablos-Velasco, Pedro; de Santiago, Ana; Sánchez-Celaya, Marta; Suárez, Carmen; Tranche, Salvador

    2014-11-01

    Chronic kidney disease (CKD) is an important global health problem, involving to 10% of the Spanish population, promoting high morbidity and mortality for the patient and an elevate consumption of the total health resources for the National Health System. This is a summary of an executive consensus document of ten scientific societies involved in the care of the renal patient, that actualizes the consensus document published in 2007. The central extended document can be consulted in the web page of each society. The aspects included in the document are: Concept, epidemiology and risk factors for CKD. Diagnostic criteria, evaluation and stages of CKD, albuminuria and glomerular filtration rate estimation. Progression factors for renal damage. Patient remission criteria. Follow-up and objectives of each speciality control. Nephrotoxicity prevention. Cardio-vascular damage detection. Diet, life-style and treatment attitudes: hypertension, dyslipidaemia, hyperglycemia, smoking, obesity, hyperuricemia, anemia, mineral and bone disorders. Multidisciplinary management for Primary Care, other specialities and Nephrology. Integrated management of CKD patient in haemodialysis, peritoneal dialysis and renal transplant patients. Management of the uremic patient in palliative care. We hope that this document may be of help for the multidisciplinary management of CKD patients by summarizing the most updated recommendations. Copyright © 2014 Elsevier España, S.L.U. All rights reserved.

  7. [Consensus document for the detection and management of chronic kidney disease].

    PubMed

    Martínez-Castelao, Alberto; Górriz, José L; Bover, Jordi; Segura-de la Morena, Julián; Cebollada, Jesús; Escalada, Javier; Esmatjes, Enric; Fácila, Lorenzo; Gamarra, Javier; Gràcia, Silvia; Hernández-Moreno, Julio; Llisterri-Caro, José L; Mazón, Pilar; Montañés, Rosario; Morales-Olivas, Francisco; Muñoz-Torres, Manuel; de Pablos-Velasco, Pedro; de Santiago, Ana; Sánchez-Celaya, Marta; Suárez, Carmen; Tranche, Salvador

    2014-11-01

    Chronic kidney disease (CKD) is an important global health problem, involving to 10% of the Spanish population, promoting high morbidity and mortality for the patient and an elevate consumption of the total health resources for the National Health System. This is a summary of an executive consensus document of ten scientific societies involved in the care of the renal patient, that actualizes the consensus document published in 2007. The central extended document can be consulted in the web page of each society. The aspects included in the document are: Concept, epidemiology and risk factors for CKD. Diagnostic criteria, evaluation and stages of CKD, albuminuria and glomerular filtration rate estimation. Progression factors for renal damage. Patient remission criteria. Follow-up and objectives of each speciality control. Nephrotoxicity prevention. Cardio-vascular damage detection. Diet, life-style and treatment attitudes: hypertension, dyslipidaemia, hyperglycemia, smoking, obesity, hyperuricemia, anemia, mineral and bone disorders. Multidisciplinary management for Primary Care, other specialities and Nephrology. Integrated management of CKD patient in haemodialysis, peritoneal dialysis and renal transplant patients. Management of the uremic patient in palliative care. We hope that this document may be of help for the multidisciplinary management of CKD patients by summarizing the most updated recommendations. Copyright © 2014. Published by Elsevier Espana.

  8. Human-In-The-Loop Investigation of Interoperability Between Terminal Sequencing and Spacing, Automated Terminal Proximity Alert, and Wake-Separation Recategorization

    NASA Technical Reports Server (NTRS)

    Callantine, Todd J.; Bienert, Nancy; Borade, Abhay; Gabriel, Conrad; Gujral, Vimmy; Jobe, Kim; Martin, Lynne; Omar, Faisal; Prevot, Thomas; Mercer, Joey

    2016-01-01

    A human-in-the-loop simulation study addressed terminal-area controller-workstation interface variations for interoperability between three new capabilities being introduced by the FAA. The capabilities are Terminal Sequencing and Spacing (TSAS), Automated Terminal Proximity Alert (ATPA), and wake-separation recategorization, or 'RECAT.' TSAS provides controllers with Controller-Managed Spacing (CMS) tools, including slot markers, speed advisories, and early/late indications, together with runway assignments and sequence numbers. ATPA provides automatic monitor, warning, and alert cones to inform controllers about spacing between aircraft on approach. ATPA cones are sized according to RECAT, an improved method of specifying wake-separation standards. The objective of the study was to identify potential issues and provide recommendations for integrating TSAS with ATPA and RECAT. Participants controlled arrival traffic under seven different display configurations, then tested an 'exploratory' configuration developed with participant input. All the display conditions were workable and acceptable, but controllers strongly preferred having the CMS tools available on Feeder positions, and both CMS tools and ATPA available on Final positions. Controllers found the integrated systems favorable and liked being able to tailor configurations to individual preferences.

  9. Program and Project Management Framework

    NASA Technical Reports Server (NTRS)

    Butler, Cassandra D.

    2002-01-01

    The primary objective of this project was to develop a framework and system architecture for integrating program and project management tools that may be applied consistently throughout Kennedy Space Center (KSC) to optimize planning, cost estimating, risk management, and project control. Project management methodology used in building interactive systems to accommodate the needs of the project managers is applied as a key component in assessing the usefulness and applicability of the framework and tools developed. Research for the project included investigation and analysis of industrial practices, KSC standards, policies, and techniques, Systems Management Office (SMO) personnel, and other documented experiences of project management experts. In addition, this project documents best practices derived from the literature as well as new or developing project management models, practices, and techniques.

  10. An IEEE 1451.1 Architecture for ISHM Applications

    NASA Technical Reports Server (NTRS)

    Morris, Jon A.; Turowski, Mark; Schmalzel, John L.; Figueroa, Jorge F.

    2007-01-01

    The IEEE 1451.1 Standard for a Smart Transducer Interface defines a common network information model for connecting and managing smart elements in control and data acquisition networks using network-capable application processors (NCAPs). The Standard is a network-neutral design model that is easily ported across operating systems and physical networks for implementing complex acquisition and control applications by simply plugging in the appropriate network level drivers. To simplify configuration and tracking of transducer and actuator details, the family of 1451 standards defines a Transducer Electronic Data Sheet (TEDS) that is associated with each physical element. The TEDS contains all of the pertinent information about the physical operations of a transducer (such as operating regions, calibration tables, and manufacturer information), which the NCAP uses to configure the system to support a specific transducer. The Integrated Systems Health Management (ISHM) group at NASA's John C. Stennis Space Center (SSC) has been developing an ISHM architecture that utilizes IEEE 1451.1 as the primary configuration and data acquisition mechanism for managing and collecting information from a network of distributed intelligent sensing elements. This work has involved collaboration with other NASA centers, universities and aerospace industries to develop IEEE 1451.1 compliant sensors and interfaces tailored to support health assessment of complex systems. This paper and presentation describe the development and implementation of an interface for the configuration, management and communication of data, information and knowledge generated by a distributed system of IEEE 1451.1 intelligent elements monitoring a rocket engine test system. In this context, an intelligent element is defined as one incorporating support for the IEEE 1451.x standards and additional ISHM functions. Our implementation supports real-time collection of both measurement data (raw ADC counts and converted engineering units) and health statistics produced by each intelligent element. The handling of configuration, calibration and health information is automated by using the TEDS in combination with other electronic data sheets extensions to convey health parameters. By integrating the IEEE 1451.1 Standard for a Smart Transducer Interface with ISHM technologies, each element within a complex system becomes a highly flexible computation engine capable of self-validation and performing other measures of the quality of information it is producing.

  11. Space station integrated wall design and penetration damage control. Task 4: Impact detection/location system

    NASA Technical Reports Server (NTRS)

    Nelson, J. M.; Lempriere, B. M.

    1987-01-01

    A program to develop a methodology is documented for detecting and locating meteoroid and debris impacts and penetrations of a wall configuration currently specified for use on space station. Testing consisted of penetrating and non-penetrating hypervelocity impacts on single and dual plate test configurations, including a prototype 1.22 m x 2.44 m x 3.56 mm (4 ft x 8 ft x 0.140 in) aluminum waffle grid backwall with multilayer insulation and a 0.063-in shield. Acoustic data were gathered with transducers and associated data acquisition systems and stored for later analysis with a multichannel digitizer. Preliminary analysis of test data included sensor evaluation, impact repeatability, first waveform arrival, and Fourier spectral analysis.

  12. Langley applications experiments data management system study. [for space shuttles

    NASA Technical Reports Server (NTRS)

    Lanham, C. C., Jr.

    1975-01-01

    A data management system study is presented that defines, in functional terms, the most cost effective ground data management system to support Advanced Technology Laboratory (ATL) flights of the space shuttle. Results from each subtask performed and the recommended system configuration for reformatting the experiment instrumentation tapes to computer compatible tape are examined. Included are cost factors for development of a mini control center for real-time support of the ATL flights.

  13. Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

    NASA Technical Reports Server (NTRS)

    Khan, Ahmed

    2010-01-01

    The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

  14. Multiplexer/Demultiplexer Loading Tool (MDMLT)

    NASA Technical Reports Server (NTRS)

    Brewer, Lenox Allen; Hale, Elizabeth; Martella, Robert; Gyorfi, Ryan

    2012-01-01

    The purpose of the MDMLT is to improve the reliability and speed of loading multiplexers/demultiplexers (MDMs) in the Software Development and Integration Laboratory (SDIL) by automating the configuration management (CM) of the loads in the MDMs, automating the loading procedure, and providing the capability to load multiple or all MDMs concurrently. This loading may be accomplished in parallel, or single MDMs (remote). The MDMLT is a Web-based tool that is capable of loading the entire International Space Station (ISS) MDM configuration in parallel. It is able to load Flight Equivalent Units (FEUs), enhanced, standard, and prototype MDMs as well as both EEPROM (Electrically Erasable Programmable Read-Only Memory) and SSMMU (Solid State Mass Memory Unit) (MASS Memory). This software has extensive configuration management to track loading history, and the performance improvement means of loading the entire ISS MDM configuration of 49 MDMs in approximately 30 minutes, as opposed to 36 hours, which is what it took previously utilizing the flight method of S-Band uplink. The laptop version recently added to the MDMLT suite allows remote lab loading with the CM of information entered into a common database when it is reconnected to the network. This allows the program to reconfigure the test rigs quickly between shifts, allowing the lab to support a variety of onboard configurations during a single day, based on upcoming or current missions. The MDMLT Computer Software Configuration Item (CSCI) supports a Web-based command and control interface to the user. An interface to the SDIL File Transfer Protocol (FTP) server is supported to import Integrated Flight Loads (IFLs) and Internal Product Release Notes (IPRNs) into the database. An interface to the Monitor and Control System (MCS) is supported to control the power state, and to enable or disable the debug port of the MDMs to be loaded. Two direct interfaces to the MDM are supported: a serial interface (debug port) to receive MDM memory dump data and the calculated checksum, and the Small Computer System Interface (SCSI) to transfer load files to MDMs with hard disks. File transfer from the MDM Loading Tool to EEPROM within the MDM is performed via the MILSTD- 1553 bus, making use of the Real- Time Input/Output Processors (RTIOP) when using the rig-based MDMLT, and via a bus box when using the laptop MDMLT. The bus box is a cost-effective alternative to PC-1553 cards for the laptop. It is noted that this system can be modified and adapted to any avionic laboratory for spacecraft computer loading, ship avionics, or aircraft avionics where multiple configurations and strong configuration management of software/firmware loads are required.

  15. Overseas Environmental Baseline Guidance Document

    DTIC Science & Technology

    2007-05-01

    The primary purpose of this Overseas Environmental Baseline Guidance Document (OEBGD) is to provide criteria and management practices to be used by ...establishes standards for environmental compliance at Department of Defense controlled or operated installations in countries for which no FGS have been established.

  16. Integration and Test of Shuttle Small Payloads

    NASA Technical Reports Server (NTRS)

    Wright, Michael R.

    2003-01-01

    Recommended approaches for space shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of shuttle small payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration and interface testing; (7) Postflight operations. This paper is of special interest to those payload projects that have small budgets and few resources: that is, the truly faster, cheaper, better projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.

  17. Advanced information processing system: Local system services

    NASA Technical Reports Server (NTRS)

    Burkhardt, Laura; Alger, Linda; Whittredge, Roy; Stasiowski, Peter

    1989-01-01

    The Advanced Information Processing System (AIPS) is a multi-computer architecture composed of hardware and software building blocks that can be configured to meet a broad range of application requirements. The hardware building blocks are fault-tolerant, general-purpose computers, fault-and damage-tolerant networks (both computer and input/output), and interfaces between the networks and the computers. The software building blocks are the major software functions: local system services, input/output, system services, inter-computer system services, and the system manager. The foundation of the local system services is an operating system with the functions required for a traditional real-time multi-tasking computer, such as task scheduling, inter-task communication, memory management, interrupt handling, and time maintenance. Resting on this foundation are the redundancy management functions necessary in a redundant computer and the status reporting functions required for an operator interface. The functional requirements, functional design and detailed specifications for all the local system services are documented.

  18. System design analyses of a rotating advanced-technology space station for the year 2025

    NASA Technical Reports Server (NTRS)

    Queijo, M. J.; Butterfield, A. J.; Cuddihy, W. F.; Stone, R. W.; Wrobel, J. R.; Garn, P. A.; King, C. B.

    1988-01-01

    Studies of an advanced technology space station configured to implement subsystem technologies projected for availability in the time period 2000 to 2025 is documented. These studies have examined the practical synergies in operational performance available through subsystem technology selection and identified the needs for technology development. Further analyses are performed on power system alternates, momentum management and stabilization, electrothermal propulsion, composite materials and structures, launch vehicle alternates, and lunar and planetary missions. Concluding remarks are made regarding the advanced technology space station concept, its intersubsystem synergies, and its system operational subsystem advanced technology development needs.

  19. Strategies for increasing house staff management of cholesterol with inpatients.

    PubMed

    Boekeloo, B O; Becker, D M; Levine, D M; Belitsos, P C; Pearson, T A

    1990-01-01

    This study tested the effectiveness of two conceptually different chart audit-based approaches to modifying physicians' clinical practices to conform with quality-assurance standards. The objective was to increase intern utilization of cholesterol management opportunities in the inpatient setting. Using a clinical trial study design, 29 internal medicine interns were randomly assigned to four intervention groups identified by the intervention they received: control, reminder checklists (checklists), patient-specific feedback (feedback), or both interventions (combined). Over a nine-month period, intern management of high blood cholesterol levels in internal medicine inpatients (n = 459) was monitored by postdischarge chart audit. During both a baseline and subsequent intervention period, interns documented significantly more cholesterol management for inpatients with coronary artery disease (CAD) than without CAD. During baseline, 27.3%, 24.3%, 21.7%, 12.4%, 5.4%, and 2.7% of all inpatient charts had intern documentation concerning a low-fat hospital diet, cholesterol history, screening blood cholesterol level assessment, follow-up lipid profile, nutritionist consult, and preventive cardiology consult, respectively. The feedback intervention significantly increased overall intern-documented cholesterol management among inpatients with CAD. The checklists significantly decreased overall intern-documented cholesterol management. Feedback appears to be an effective approach to increasing intern cholesterol management in inpatients.

  20. Git Replacement for the

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Robinson, P.

    2014-09-23

    GRAPE is a tool for managing software project workflows for the Git version control system. It provides a suite of tools to simplify and configure branch based development, integration with a project's testing suite, and integration with the Atlassian Stash repository hosting tool.

  1. DBMS as a Tool for Project Management

    NASA Technical Reports Server (NTRS)

    Linder, H.

    1984-01-01

    Scientific objectives of crustal dynamics are listed as well as the contents of the centralized data information system for the crustal dynamics project. The system provides for project observation schedules, gives project configuration control information and project site information.

  2. Facing the Limitations of Electronic Document Handling.

    ERIC Educational Resources Information Center

    Moralee, Dennis

    1985-01-01

    This essay addresses problems associated with technology used in the handling of high-resolution visual images in electronic document delivery. Highlights include visual fidelity, laser-driven optical disk storage, electronics versus micrographics for document storage, videomicrographics, and system configurations and peripherals. (EJS)

  3. NASA information resources management handbook

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This National Aeronautics and Space Administration (NASA) Handbook (NHB) implements recent changes to Federal laws and regulations involving the acquisition, management, and use of Federal Information Processing (FIP) resources. This document defines NASA's Information Resources Management (IRM) practices and procedures and is applicable to all NASA personnel. The dynamic nature of the IRM environment requires that the controlling management practices and procedures for an Agency at the leading edge of technology, such as NASA, must be periodically updated to reflect the changes in this environment. This revision has been undertaken to accommodate changes in the technology and the impact of new laws and regulations dealing with IRM. The contents of this document will be subject to a complete review annually to determine its continued applicability to the acquisition, management, and use of FIP resources by NASA. Updates to this document will be accomplished by page changes. This revision cancels NHB 2410.1D, dated April 1985.

  4. Effects of early focal brain injury on memory for visuospatial patterns: selective deficits of global-local processing.

    PubMed

    Stiles, Joan; Stern, Catherine; Appelbaum, Mark; Nass, Ruth; Trauner, Doris; Hesselink, John

    2008-01-01

    Selective deficits in visuospatial processing are present early in development among children with perinatal focal brain lesions (PL). Children with right hemisphere PL (RPL) are impaired in configural processing, while children with left hemisphere PL (LPL) are impaired in featural processing. Deficits associated with LPL are less pervasive than those observed with RPL, but this difference may reflect the structure of the tasks used for assessment. Many of the tasks used to date may place greater demands on configural processing, thus highlighting this deficit in the RPL group. This study employed a task designed to place comparable demands on configural and featural processing, providing the opportunity to obtain within-task evidence of differential deficit. Sixty-two 5- to 14-year-old children (19 RPL, 19 LPL, and 24 matched controls) reproduced from memory a series of hierarchical forms (large forms composed of small forms). Global- and local-level reproduction accuracy was scored. Controls were equally accurate on global- and local-level reproduction. Children with RPL were selectively impaired on global accuracy, and children with LPL on local accuracy, thus documenting a double dissociation in global-local processing.

  5. Installation package for integrated programmable electronic controller and hydronic subsystem - solar heating and cooling

    NASA Technical Reports Server (NTRS)

    1978-01-01

    A description is given of the Installation, Operation, and Maintenance Manual and information on the power panel and programmable microprocessor, a hydronic solar pump system and a hydronic heating hot water pumping system. These systems are integrated into various configurations for usages in solar energy management, control and monitoring, lighting control, data logging and other solar related applications.

  6. Windows VPN Set Up | High-Performance Computing | NREL

    Science.gov Websites

    it in your My Documents folder Configure the client software using that conf file Start the TEXT NEEDED Configure the Client Software Start the Endian Connect App. You'll configure the connection using the hpcvpn-win.conf file, uncheck the "save password" link, and add your UserID. Start

  7. Method and system for redundancy management of distributed and recoverable digital control system

    NASA Technical Reports Server (NTRS)

    Stange, Kent (Inventor); Hess, Richard (Inventor); Kelley, Gerald B (Inventor); Rogers, Randy (Inventor)

    2012-01-01

    A method and system for redundancy management is provided for a distributed and recoverable digital control system. The method uses unique redundancy management techniques to achieve recovery and restoration of redundant elements to full operation in an asynchronous environment. The system includes a first computing unit comprising a pair of redundant computational lanes for generating redundant control commands. One or more internal monitors detect data errors in the control commands, and provide a recovery trigger to the first computing unit. A second redundant computing unit provides the same features as the first computing unit. A first actuator control unit is configured to provide blending and monitoring of the control commands from the first and second computing units, and to provide a recovery trigger to each of the first and second computing units. A second actuator control unit provides the same features as the first actuator control unit.

  8. Spaceflight Ground Support Equipment Reliability & System Safety Data

    NASA Technical Reports Server (NTRS)

    Fernandez, Rene; Riddlebaugh, Jeffrey; Brinkman, John; Wilkinson, Myron

    2012-01-01

    Presented were Reliability Analysis, consisting primarily of Failure Modes and Effects Analysis (FMEA), and System Safety Analysis, consisting of Preliminary Hazards Analysis (PHA), performed to ensure that the CoNNeCT (Communications, Navigation, and Networking re- Configurable Testbed) Flight System was safely and reliably operated during its Assembly, Integration and Test (AI&T) phase. A tailored approach to the NASA Ground Support Equipment (GSE) standard, NASA-STD-5005C, involving the application of the appropriate Requirements, S&MA discipline expertise, and a Configuration Management system (to retain a record of the analysis and documentation) were presented. Presented were System Block Diagrams of selected GSE and the corresponding FMEA, as well as the PHAs. Also discussed are the specific examples of the FMEAs and PHAs being used during the AI&T phase to drive modifications to the GSE (via "redlining" of test procedures, and the placement of warning stickers to protect the flight hardware) before being interfaced to the Flight System. These modifications were necessary because failure modes and hazards were identified during the analysis that had not been properly mitigated. Strict Configuration Management was applied to changes (whether due to upgrades or expired calibrations) in the GSE by revisiting the FMEAs and PHAs to reflect the latest System Block Diagrams and Bill Of Material. The CoNNeCT flight system has been successfully assembled, integrated, tested, and shipped to the launch site without incident. This demonstrates that the steps taken to safeguard the flight system when it was interfaced to the various GSE were successful.

  9. Earth Observing System (EOS)/Advanced Microwave Sounding Unit-A (AMSU-A)

    NASA Technical Reports Server (NTRS)

    Mullooly, William

    1995-01-01

    This is the thirty-first monthly report for the Earth Observing System (EOS)/Advanced Microwave Sounding Unit- A (AMSU-A), Contract NAS5-32314, and covers the period from 1 July 1995 through 31 July 1995. This period is the nineteenth month of the Implementation Phase which provides for the design, fabrication, assembly, and test of the first EOS/AMSU-A, the Protoflight Model. Included in this report is the Master Program Schedule (Section 2), a report from the Product Team Leaders on the status of all major program elements (Section 3), Drawing status (Section 4), Weight and Power Budgets (CDRL) 503 (Section 5), Performance Assurance (CDRL 204) (Section 6), Configuration Management Status Report (CDRL 203) (Section 7), Documentation/Data Management Status Report (Section 8), and Contract Status (Section 9).

  10. Methods and Apparatus for Deployable Swirl Vanes

    NASA Technical Reports Server (NTRS)

    Shah, Parthiv N. (Inventor)

    2017-01-01

    An aircraft control structure for drag management includes a nozzle structure configured to exhaust a swirling fluid stream. A plurality of swirl vanes are positioned within the nozzle structure, and an actuation subsystem is configured to cause the plurality of swirl vanes to move from a deployed state to a non-deployed state. In the non-deployed state, the plurality of swirl vanes are substantially flush with the inner surface of the nozzle structure. In the deployed state, the plurality of swirl vanes produce the swirling fluid stream.

  11. United States Coast Guard Configuration Management Plan (CMP) for the Ports and Waterways Safety System (PAWSS) Project

    DOT National Transportation Integrated Search

    1997-01-01

    Prepared ca. 1997. The Configuration Management Plan (CMP) provides configuration management instructions and guidance for the Vessel Traffic Service (VTS) system of the Ports and Waterways Safety System (PAWSS) project. The CMP describes in detail t...

  12. 76 FR 57771 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-09-16

    ... Securities and Exchange Commission (``Commission'') has submitted to the Office of Management and Budget... display a valid Office of Management and Budget (OMB) control number. Background documentation for this... Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington...

  13. 76 FR 75921 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2011-12-05

    ... Securities and Exchange Commission (``Commission'') has submitted to the Office of Management and Budget... of Management and Budget (OMB) control number. The public may view the background documentation for... Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington...

  14. Tools for distributed application management

    NASA Technical Reports Server (NTRS)

    Marzullo, Keith; Cooper, Robert; Wood, Mark; Birman, Kenneth P.

    1990-01-01

    Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system (a collection of tools for constructing distributed application management software) is described. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real-time reactive program. The underlying application is instrumented with a variety of built-in and user-defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when preexisting, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.

  15. Tools for distributed application management

    NASA Technical Reports Server (NTRS)

    Marzullo, Keith; Wood, Mark; Cooper, Robert; Birman, Kenneth P.

    1990-01-01

    Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system is described: a collection of tools for constructing distributed application management software. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real time reactive program. The underlying application is instrumented with a variety of built-in and user defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when pre-existing, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.

  16. Operational Overview for UAS Integration in the NAS Project Flight Test Series 3

    NASA Technical Reports Server (NTRS)

    Valkov, Steffi B.; Sternberg, Daniel; Marston, Michael

    2017-01-01

    The National Aeronautics and Space Administration Unmanned Aircraft Systems Integration in the National Airspace System Project has conducted a series of flight tests intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration. The 2015 Flight Test Series 3, supported two separate test configurations. The first configuration investigated the timing of Detect and Avoid alerting thresholds using a radar equipped unmanned vehicle and multiple live intruders flown at varying encounter geometries. The second configuration included a surrogate unmanned vehicle (flown from a ground control station, with a safety pilot on board) flying a mission in a virtual air traffic control airspace sector using research pilot displays and Detect and Avoid advisories to maintain separation from live and virtual aircraft. The test was conducted over an eight-week span within the R-2508 Special Use Airspace. Over 200 encounters were flown for the first configuration, and although the second configuration was cancelled after three data collection flights, Flight Test 3 proved to be invaluable for the purposes of planning, managing, and execution of this type of integrated flight test.

  17. Cargo Movement Operations System (CMOS). Draft Software Design Document for the PC UNIX Prototype (Navy Configuration), Increment III.

    DTIC Science & Technology

    1991-04-21

    NO [ ] COMMENT DISPOSITION: COMMENT STATUS: OPEN [ ] CLOSED ( ] ORIGINATOR CONTROL NUMBER: SDDN-0003 PROGRAM OFFICE CONTROL NUMBER: DATA ITEM DISCREPANCY WORKSHEET CDRL NUMBER: C006-02 DATE: 04/21/91 ORIGINATOR NAME: Ronald J. Lacour OFFICE SYMBOL: SAIC TELEPHONE NUMBER: 272-2999 SUBSTANTIVE: X EDITORIAL: PAGE NUMBER: CUBA0065-1 PARA NUMBER: N/A COMMENT OR RECOMMENDED CHANGE: Change CUVA0065 in Table 6 to CUBA0065 to match the name in Attachment 1. RATIONALE: It appears that this CSU was improperly named in Table 6. CMOS PMO ACCEPTS COMMENT:

  18. A Sample Data Publication: Interactive Access, Analysis and Display of Remotely Stored Datasets From Hurricane Charley

    NASA Astrophysics Data System (ADS)

    Weber, J.; Domenico, B.

    2004-12-01

    This paper is an example of what we call data interactive publications. With a properly configured workstation, the readers can click on "hotspots" in the document that launches an interactive analysis tool called the Unidata Integrated Data Viewer (IDV). The IDV will enable the readers to access, analyze and display datasets on remote servers as well as documents describing them. Beyond the parameters and datasets initially configured into the paper, the analysis tool will have access to all the other dataset parameters as well as to a host of other datasets on remote servers. These data interactive publications are built on top of several data delivery, access, discovery, and visualization tools developed by Unidata and its partner organizations. For purposes of illustrating this integrative technology, we will use data from the event of Hurricane Charley over Florida from August 13-15, 2004. This event illustrates how components of this process fit together. The Local Data Manager (LDM), Open-source Project for a Network Data Access Protocol (OPeNDAP) and Abstract Data Distribution Environment (ADDE) services, Thematic Realtime Environmental Distributed Data Service (THREDDS) cataloging services, and the IDV are highlighted in this example of a publication with embedded pointers for accessing and interacting with remote datasets. An important objective of this paper is to illustrate how these integrated technologies foster the creation of documents that allow the reader to learn the scientific concepts by direct interaction with illustrative datasets, and help build a framework for integrated Earth System science.

  19. Requirements, Resource Planning and Management for Decrewing/Recrewing Scenarios of the International Space Station

    NASA Technical Reports Server (NTRS)

    Bach, David A.; Hasbrook, Peter V.; BBrand, Susan N.

    2012-01-01

    Following the failure of 44P on launch in August 2011, and the subsequent grounding of all Russian Soyuz rocket based launches, the ISS ground teams engaged in an effort to determine how long the ISS could remain crewed, what would be required to safely configure the ISS for decrewing, and what would be required to recrew the ISS upon resumption of Soyuz rocket launches if decrewing became necessary. This White Paper was written to capture the processes and lessons learned from real-time time events and to provide a reference and training document for ISS Program teams in the event decrewing of the ISS is needed. Through coordination meetings and assessments, teams identified six decrewing priorities for ground and crew operations. These priorities were integrated along with preflight priorities through the Increment replanning process. Additionally, the teams reviewed, updated, and implemented changes to the governing documentation for the configuration of the ISS for a contingency decrewing event. Steps were taken to identify critical items for disposal prior to decrewing, as well as identifying the required items to be strategically staged or flown with the astronauts and cosmonauts who would eventually recrew the ISS. After the successful launches and dockings of both 45P and 28S, the decrewing team transitioned to finalizing and publishing the documentation for standardizing the decrewing flight rules. With the continued launching of crews and cargo to the ISS, utilization and science is again a high priority, with the Increment pairs 29 and 30, and 31 and 32 reaching the milestone of at least 35 hours per week average utilization.

  20. An Approach for Implementation of Project Management Information Systems

    NASA Astrophysics Data System (ADS)

    Běrziša, Solvita; Grabis, Jānis

    Project management is governed by project management methodologies, standards, and other regulatory requirements. This chapter proposes an approach for implementing and configuring project management information systems according to requirements defined by these methodologies. The approach uses a project management specification framework to describe project management methodologies in a standardized manner. This specification is used to automatically configure the project management information system by applying appropriate transformation mechanisms. Development of the standardized framework is based on analysis of typical project management concepts and process and existing XML-based representations of project management. A demonstration example of project management information system's configuration is provided.

  1. Water Hyacinth in China: A Sustainability Science-Based Management Framework

    NASA Astrophysics Data System (ADS)

    Lu, Jianbo; Wu, Jianguo; Fu, Zhihui; Zhu, Lei

    2007-12-01

    The invasion of water hyacinth ( Eichhornia crassipes) has resulted in enormous ecological and economic consequences worldwide. Although the spread of this weed in Africa, Australia, and North America has been well documented, its invasion in China is yet to be fully documented. Here we report that since its introduction about seven decades ago, water hyacinth has infested many water bodies across almost half of China’s territory, causing a decline of native biodiversity, alteration of ecosystem services, deterioration of aquatic environments, and spread of diseases affecting human health. Water hyacinth infestations have also led to enormous economic losses in China by impeding water flows, paralyzing navigation, and damaging irrigation and hydroelectricity facilities. To effectively control the rampage of water hyacinth in China, we propose a sustainability science-based management framework that explicitly incorporates principles from landscape ecology and Integrated Pest Management. This framework emphasizes multiple-scale long-term monitoring and research, integration among different control techniques, combination of control with utilization, and landscape-level adaptive management. Sustainability science represents a new, transdisciplinary paradigm that integrates scientific research, technological innovation, and socioeconomic development of particular regions. Our proposed management framework is aimed to broaden the currently dominant biological control-centered view in China and to illustrate how sustainability science can be used to guide the research and management of water hyacinth.

  2. Aircraft/Air Traffic Management Functional Analysis Model: Technical Description. 2.0

    NASA Technical Reports Server (NTRS)

    Etheridge, Melvin; Plugge, Joana; Retina, Nusrat

    1998-01-01

    The Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 (FAM 2.0), is a discrete event simulation model designed to support analysis of alternative concepts in air traffic management and control. FAM 2.0 was developed by the Logistics Management Institute (LMI) under a National Aeronautics and Space Administration (NASA) contract. This document provides a technical description of FAM 2.0 and its computer files to enable the modeler and programmer to make enhancements or modifications to the model. Those interested in a guide for using the model in analysis should consult the companion document, Aircraft/Air Traffic Management Functional Analysis Model, Version 2.0 Users Manual.

  3. Preliminary design package for solar heating and hot water system

    NASA Technical Reports Server (NTRS)

    1977-01-01

    The preliminary design review on the development of two prototype solar heating and hot water systems is presented. The information contained in this report includes system certification, system functional description, system configuration, system specification, system performance and other documents pertaining to the progress and the design of the system. This system, which is intended for use in the normal single-family residence, consists of the following subsystems: collector, storage, control, transport, and Government-furnished Site Data Acquisition.

  4. Lighting system with thermal management system

    DOEpatents

    Arik, Mehmet; Weaver, Stanton Earl; Stecher, Thomas Elliot; Seeley, Charles Erklin; Kuenzler, Glenn Howard; Wolfe, Jr., Charles Franklin; Utturkar, Yogen Vishwas; Sharma, Rajdeep; Prabhakaran, Satish; Icoz, Tunc

    2015-02-24

    Lighting systems having unique configurations are provided. For instance, the lighting system may include a light source, a thermal management system and driver electronics, each contained within a housing structure. The light source is configured to provide illumination visible through an opening in the housing structure. The thermal management system is configured to provide an air flow, such as a unidirectional air flow, through the housing structure in order to cool the light source. The driver electronics are configured to provide power to each of the light source and the thermal management system.

  5. Lighting system with thermal management system

    DOEpatents

    Arik, Mehmet; Weaver, Stanton Earl; Stecher, Thomas Elliot; Seeley, Charles Erklin; Kuenzler, Glenn Howard; Wolfe, Jr., Charles Franklin; Utturkar, Yogen Vishwas; Sharma, Rajdeep; Prabhakaran, Satish; Icoz, Tunc

    2015-08-25

    Lighting systems having unique configurations are provided. For instance, the lighting system may include a light source, a thermal management system and driver electronics, each contained within a housing structure. The light source is configured to provide illumination visible through an opening in the housing structure. The thermal management system is configured to provide an air flow, such as a unidirectional air flow, through the housing structure in order to cool the light source. The driver electronics are configured to provide power to each of the light source and the thermal management system.

  6. Lighting system with thermal management system

    DOEpatents

    Arik, Mehmet; Weaver, Stanton; Stecher, Thomas; Seeley, Charles; Kuenzler, Glenn; Wolfe, Jr., Charles; Utturkar, Yogen; Sharma, Rajdeep; Prabhakaran, Satish; Icoz, Tunc

    2013-05-07

    Lighting systems having unique configurations are provided. For instance, the lighting system may include a light source, a thermal management system and driver electronics, each contained within a housing structure. The light source is configured to provide illumination visible through an opening in the housing structure. The thermal management system is configured to provide an air flow, such as a unidirectional air flow, through the housing structure in order to cool the light source. The driver electronics are configured to provide power to each of the light source and the thermal management system.

  7. Lighting system with thermal management system

    DOEpatents

    Arik, Mehmet; Weaver, Stanton Earl; Stecher, Thomas Elliot; Seeley, Charles Erklin; Kuenzler, Glenn Howard; Wolfe, Jr, Charles Franklin; Utturkar, Yogen Vishwas; Sharma, Rajdeep; Prabhakaran, Satish; Icoz, Tunc

    2016-10-11

    Lighting systems having unique configurations are provided. For instance, the lighting system may include a light source, a thermal management system and driver electronics, each contained within a housing structure. The light source is configured to provide illumination visible through an opening in the housing structure. The thermal management system is configured to provide an air flow, such as a unidirectional air flow, through the housing structure in order to cool the light source. The driver electronics are configured to provide power to each of the light source and the thermal management system.

  8. 77 FR 36019 - Submission for OMB Review; Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2012-06-15

    ... Securities and Exchange Commission (``Commission'') has submitted to the Office of Management and Budget a... Management and Budget (OMB) control number. The public may view the background documentation for this... of Management and Budget, Room 10102, New Executive Office Building, Washington, DC 20503, or by...

  9. Content Documents Management

    NASA Technical Reports Server (NTRS)

    Muniz, R.; Hochstadt, J.; Boelke J.; Dalton, A.

    2011-01-01

    The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NEC3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

  10. Mode Transitions in Glass Cockpit Aircraft: Results of a Field Study

    NASA Technical Reports Server (NTRS)

    Degani, Asaf; Kirlik, Alex; Shafto, Michael (Technical Monitor)

    1995-01-01

    One consequence of increased levels of automation in complex control systems is the presence of modes. A mode is a particular configuration of a control system that defines how human command inputs are interpreted. In complex systems, modes also often determine a specific allocation of control authority between the human and automated systems. Even in simple static devices (e.g., electronic watches, word processors), the presence of modes has been found to cause problems in either-the acquisition or production of skilled performance. Many of these problems arise due to the fact that the selection of a mode causes device behavior to be mediated by hidden internal state information. For these simple systems, many of these interaction problems can be solved by the design of appropriate feedback to communicate internal state information to the human operator. In complex dynamic systems, however, the design issues associated with modes seem to trancend the problem of merely communicating internal state information via displayed feedback. In complex supervisory control systems (e.g., aircraft, spacecraft, military command and control), a key function of modes is the selection of a particular configuration of control authority between the human operator and automated control systems. One mode may result in full manual control, another may result in a mix of manual and automatic control, while a third may result in full automatic control over the entire system. The human operator selects an appropriate mode as a function of current goals, operating conditions, and operating procedures. Thus, the operator is put in a position of essentially trying to control two coupled dynamic systems: the target system itself, and also a highly complex suite of automation controlling the target system. From a historical perspective, it should probably not come as a surprise that very little information is available to guide the design of mode-oriented control systems. The topic of function allocation (i.e., the proper division of control authority among human and computer) has a long history in human-machine systems research. Although this research has produced some relevant guidelines, a design approach capable of defining appropriate allocations of control function between the human and automation is not yet available. As a result, the function allocation decision itself has been allocated to the operator, to be performed in real-time, in the operation of mode-oriented control systems. A variety of documented aircraft accidents and incidents suggest that the real-time selection and monitoring of control modes is a weak link in the effective operation of complex supervisory control systems. Research in human-machine systems and human-computer interaction has barely scraped the surface of the problem of understanding how operators manage this task.The purpose of this paper is to present the results of a field study which examined how operators manage mode selection in a complex supervisory control system. Data on mode engagements using the Boeing B757/767 auto-flight system were collected during approach and descent into four major airports in the East Coast of the United States. Protocols documenting mode selection, automatic mode changes, pilot actions, quantitative records of flight-path variables, and verbal reports during and after mode engagements were collected by an observer from the jumpseat. Observations were conducted on two typical trips between three airports. Each trip was be replicated 11 times, which yielded a total of 22 trips and 66 legs on which data were collected. All data collected concerned the same flight numbers, and therefore, the same time of day, same type of aircraft, and identical operational environments (e.g., ATC facilities, weather patterns, traffic flow etc.)

  11. Report to the administrator by the NASA Aerospace Safety Advisory Panel on the Skylab program. Volume 1: Summary report. [systems management evaluation and design analysis

    NASA Technical Reports Server (NTRS)

    1973-01-01

    Contractor and NASA technical management for the development and manufacture of the Skylab modules is reviewed with emphasis on the following management controls: configuration and interface management; vendor control; and quality control of workmanship. A review of the modified two-stage Saturn V launch vehicle which focused on modifications to accommodate the Skylab payload; resolution of prior flight anomalies; and changes in personnel and management systems is presented along with an evaluation of the possible age-life and storage problems for the Saturn 1-B launch vehicle. The NASA program management's visibility and control of contractor operations, systems engineering and integration, the review process for the evaluation of design and flight hardware, and the planning process for mission operations are investigated. It is concluded that the technical management system for development and fabrication of the modules, spacecraft, and launch vehicles, the process of design and hardware acceptance reviews, and the risk assessment activities are satisfactory. It is indicated that checkout activity, integrated testing, and preparations for and execution of mission operation require management attention.

  12. Data Distribution System (DDS) and Solar Dynamic Observatory Ground Station (SDOGS) Integration Manager

    NASA Technical Reports Server (NTRS)

    Pham, Kim; Bialas, Thomas

    2012-01-01

    The DDS SDOGS Integration Manager (DSIM) provides translation between native control and status formats for systems within DDS and SDOGS, and the ASIST (Advanced Spacecraft Integration and System Test) control environment in the SDO MOC (Solar Dynamics Observatory Mission Operations Center). This system was created in response for a need to centralize remote monitor and control of SDO Ground Station equipments using ASIST control environment in SDO MOC, and to have configurable table definition for equipment. It provides translation of status and monitoring information from the native systems into ASIST-readable format to display on pages in the MOC. The manager is lightweight, user friendly, and efficient. It allows data trending, correlation, and storing. It allows using ASIST as common interface for remote monitor and control of heterogeneous equipments. It also provides failover capability to back up machines.

  13. [Consensus document for the detection and management of chronic kidney disease].

    PubMed

    Martínez-Castelao, Alberto; Górriz, José L; Bover, Jordi; Segura-de la Morena, Julián; Cebollada, Jesús; Escalada, Javier; Esmatjes, Enric; Fácila, Lorenzo; Gamarra, Javier; Gràcia, Silvia; Hernández-Moreno, Julio; Llisterri-Caro, José L; Mazón, Pilar; Montañés, Rosario; Morales-Olivas, Francisco; Muñoz-Torres, Manuel; de Pablos-Velasco, Pedro; de Santiago, Ana; Sánchez-Celaya, Marta; Suárez, Carmen; Tranche, Salvador

    2014-01-01

    Chronic kidney disease (CKD) is an important global health problem, involving to 10% of the Spanish population, promoting high morbidity and mortality for the patient and an elevate consumption of the total health resources for the National Health System. This is a summary of an executive consensus document of ten scientific societies involved in the care of the renal patient, that actualizes the consensus document published in 2007. The central extended document can be consulted in the web page of each society. The aspects included in the document are: Concept, epidemiology and risk factors for CKD. Diagnostic criteria, evaluation and stages of CKD, albuminuria and glomerular filtration rate estimation. Progression factors for renal damage. Patient remission criteria. Follow-up and objectives of each speciality control. Nephrotoxicity prevention. Cardio-vascular damage detection. Diet, life-style and treatment attitudes: hypertension, dyslipidaemia, hyperglycemia, smoking, obesity, hyperuricemia, anemia, mineral and bone disorders. Multidisciplinary management for Primary Care, other specialities and Nephrology. Integrated management of CKD patient in haemodialysis, peritoneal dialysis and renal transplant patients. Management of the uremic patient in palliative care. We hope that this document may be of help for the multidisciplinary management of CKD patients by summarizing the most updated recommendations. Copyright © 2014 Sociedad Española de Médicos de Atención Primaria (SEMERGEN). Publicado por Elsevier España. All rights reserved.

  14. Cloud Migration Experiment Configuration and Results

    DTIC Science & Technology

    2017-12-01

    ARL-TR-8248 ● DEC 2017 US Army Research Laboratory Cloud Migration Experiment Configuration and Results by Michael De Lucia...or reconstruction of the document. ARL-TR-8248 ● DEC 2017 US Army Research Laboratory Cloud Migration Experiment Configuration...and Results by Michael De Lucia Computational and Information Sciences Directorate, ARL Justin Wray and Steven S Collmann ICF International

  15. CINTEX: International Interoperability Extensions to EOSDIS

    NASA Technical Reports Server (NTRS)

    Graves, Sara J.

    1997-01-01

    A large part of the research under this cooperative agreement involved working with representatives of the DLR, NASDA, EDC, and NOAA-SAA data centers to propose a set of enhancements and additions to the EOSDIS Version 0 Information Management System (V0 IMS) Client/Server Message Protocol. Helen Conover of ITSL led this effort to provide for an additional geographic search specification (WRS Path/Row), data set- and data center-specific search criteria, search by granule ID, specification of data granule subsetting requests, data set-based ordering, and the addition of URLs to result messages. The V0 IMS Server Cookbook is an evolving document, providing resources and information to data centers setting up a VO IMS Server. Under this Cooperative Agreement, Helen Conover revised, reorganized, and expanded this document, and converted it to HTML. Ms. Conover has also worked extensively with the IRE RAS data center, CPSSI, in Russia. She served as the primary IMS contact for IRE-CPSSI and as IRE-CPSSI's liaison to other members of IMS and Web Gateway (WG) development teams. Her documentation of IMS problems in the IRE environment (Sun servers and low network bandwidth) led to a general restructuring of the V0 IMS Client message polling system. to the benefit of all IMS participants. In addition to the IMS server software and documentation. which are generally available to CINTEX sites, Ms. Conover also provided database design documentation and consulting, order tracking software, and hands-on testing and debug assistance to IRE. In the final pre-operational phase of IRE-CPSSI development, she also supplied information on configuration management, including ideas and processes in place at the Global Hydrology Resource Center (GHRC), an EOSDIS data center operated by ITSL.

  16. Incorporating Information Value into Navy Tactical Data System: System Configuration Management Through the Delphi Method

    DTIC Science & Technology

    1989-03-01

    e"-s tcc,: -e .- r reverse of necessary an., ice-tfy by bi.-:’ ru-’ce," 5uz"ou configuration management. Delphi method. Command and Control 19 Ac-s:’a...Aos!,ac: 21 Aostraczt Security Classitcator : R uncassf~’! i~e sa-e as renc- E 0orC users Unclassified 22a Na-e of Respon’s :e iro, v c a 22o Te’eo’one...i!r’ciule A’ea coce’ 22: C’" ce . Thomnas 1’. Mitchell (4081 646-2620 155k.11i DD FORI, 1473.6.: VAR 63 A-- R e-.!c- rnay be usec~ unti exhausted se

  17. Using NetMaster to manage IBM networks

    NASA Technical Reports Server (NTRS)

    Ginsburg, Guss

    1991-01-01

    After defining a network and conveying its importance to support the activities at the JSC, the need for network management based on the size and complexity of the IBM SNA network at JSC is demonstrated. Network Management consists of being aware of component status and the ability to control resources to meet the availability and service needs of users. The concerns of the user are addressed as well as those of the staff responsible for managing the network. It is explained how NetMaster (a network management system for managing SNA networks) is used to enhance reliability and maximize service to SNA network users through automated procedures. The following areas are discussed: customization, problem and configuration management, and system measurement applications of NetMaster. Also, several examples are given that demonstrate NetMaster's ability to manage and control the network, integrate various product functions, as well as provide useful management information.

  18. The M68HC11 gripper controller software. Thesis

    NASA Technical Reports Server (NTRS)

    Tsai, Jodi Wei-Duk

    1991-01-01

    This thesis discusses the development of firmware for the 68HC11 gripper controller. A general description of the software and hardware interfaces is given. The C library interface for the gripper is then described and followed by a detailed discussion of the software architecture of the firmware. A procedure to assemble and download 68HC11 programs is presented in the form of a tutorial. The tools used to implement this environment are then described. Finally, the implementation of the configuration management scheme used to manage all CIRSSE software is presented.

  19. Apollo Soyuz Test Project Weights and Mass Properties Operational Management System

    NASA Technical Reports Server (NTRS)

    Collins, M. A., Jr.; Hischke, E. R.

    1975-01-01

    The Apollo Soyuz Test Project (ASTP) Weights and Mass Properties Operational Management System was established to assure a timely and authoritative method of acquiring, controlling, generating, and disseminating an official set of vehicle weights and mass properties data. This paper provides an overview of the system and its interaction with the various aspects of vehicle and component design, mission planning, hardware and software simulations and verification, and real-time mission support activities. The effect of vehicle configuration, design maturity, and consumables updates is discussed in the context of weight control.

  20. Development of a generic GMCC simulator.

    DOT National Transportation Integrated Search

    2001-11-01

    This document describes the development and current status of a high fidelity, human-in-the-loop simulator for Airway Facilities : Maintenance Control Centers and Operations Control Centers. Applications include Event Manager, Maintenance Automation ...

  1. REVEAL: Software Documentation and Platform Migration

    NASA Technical Reports Server (NTRS)

    Wilson, Michael A.; Veibell, Victoir T.; Freudinger, Lawrence C.

    2008-01-01

    The Research Environment for Vehicle Embedded Analysis on Linux (REVEAL) is reconfigurable data acquisition software designed for network-distributed test and measurement applications. In development since 2001, it has been successfully demonstrated in support of a number of actual missions within NASA s Suborbital Science Program. Improvements to software configuration control were needed to properly support both an ongoing transition to operational status and continued evolution of REVEAL capabilities. For this reason the project described in this report targets REVEAL software source documentation and deployment of the software on a small set of hardware platforms different from what is currently used in the baseline system implementation. This report specifically describes the actions taken over a ten week period by two undergraduate student interns and serves as a final report for that internship. The topics discussed include: the documentation of REVEAL source code; the migration of REVEAL to other platforms; and an end-to-end field test that successfully validates the efforts.

  2. An Evaluation Method of Equipment Reliability Configuration Management

    NASA Astrophysics Data System (ADS)

    Wang, Wei; Feng, Weijia; Zhang, Wei; Li, Yuan

    2018-01-01

    At present, many equipment development companies have been aware of the great significance of reliability of the equipment development. But, due to the lack of effective management evaluation method, it is very difficult for the equipment development company to manage its own reliability work. Evaluation method of equipment reliability configuration management is to determine the reliability management capabilities of equipment development company. Reliability is not only designed, but also managed to achieve. This paper evaluates the reliability management capabilities by reliability configuration capability maturity model(RCM-CMM) evaluation method.

  3. Development of integrated programs for Aerospace-vehicle Design (IPAD): Product program management systems

    NASA Technical Reports Server (NTRS)

    Isenberg, J. M.; Southall, J. W.

    1979-01-01

    The Integrated Programs for Aerospace Vehicle Design (IPAD) is a computing system to support company-wide design information processing. This document presents a brief description of the management system used to direct and control a product-oriented program. This document, together with the reference design process (CR 2981) and the manufacture interactions with the design process (CR 2982), comprises the reference information that forms the basis for specifying IPAD system requirements.

  4. Securely and Flexibly Sharing a Biomedical Data Management System

    PubMed Central

    Wang, Fusheng; Hussels, Phillip; Liu, Peiya

    2011-01-01

    Biomedical database systems need not only to address the issues of managing complex data, but also to provide data security and access control to the system. These include not only system level security, but also instance level access control such as access of documents, schemas, or aggregation of information. The latter is becoming more important as multiple users can share a single scientific data management system to conduct their research, while data have to be protected before they are published or IP-protected. This problem is challenging as users’ needs for data security vary dramatically from one application to another, in terms of who to share with, what resources to be shared, and at what access level. We develop a comprehensive data access framework for a biomedical data management system SciPort. SciPort provides fine-grained multi-level space based access control of resources at not only object level (documents and schemas), but also space level (resources set aggregated in a hierarchy way). Furthermore, to simplify the management of users and privileges, customizable role-based user model is developed. The access control is implemented efficiently by integrating access privileges into the backend XML database, thus efficient queries are supported. The secure access approach we take makes it possible for multiple users to share the same biomedical data management system with flexible access management and high data security. PMID:21625285

  5. Development and test results of a flight management algorithm for fuel conservative descents in a time-based metered traffic environment

    NASA Technical Reports Server (NTRS)

    Knox, C. E.; Cannon, D. G.

    1980-01-01

    A simple flight management descent algorithm designed to improve the accuracy of delivering an airplane in a fuel-conservative manner to a metering fix at a time designated by air traffic control was developed and flight tested. This algorithm provides a three dimensional path with terminal area time constraints (four dimensional) for an airplane to make an idle thrust, clean configured (landing gear up, flaps zero, and speed brakes retracted) descent to arrive at the metering fix at a predetermined time, altitude, and airspeed. The descent path was calculated for a constant Mach/airspeed schedule from linear approximations of airplane performance with considerations given for gross weight, wind, and nonstandard pressure and temperature effects. The flight management descent algorithm is described. The results of the flight tests flown with the Terminal Configured Vehicle airplane are presented.

  6. [Document management systems to support quality management systems at university hospitals - an interview-based study].

    PubMed

    Holderried, Martin; Bökel, Ann-Catrin; Ochsmann, Elke

    2018-05-01

    In order to save and control the processes and quality of medical services, a suitable steering system of all relevant documents is essential from the point of view of clinical quality management. Systems supporting an automated steering system of documents are called document management systems (DMS), and they also enter the healthcare sector. The use of DMS in the German healthcare sector has hardly been investigated so far. To close this knowledge gap, interviews were carried out with German university hospitals over a six-month period and subjected to a qualitative content analysis according to Mayring. In total, 25 university hospitals agreed to participate in this study, 19 of which have been working with a digital DMS for about six years on average. There was a great variety among the IT systems used. Document management and usability of the DMS as well as its integration into existing IT structures were key decision-making criteria for the selection of a digital DMS. In general, the long-term usability of the DMS is supported by regular evaluation of one's own requirements for the system, administration and training programs. In addition, DMS have a positive effect on patient safety and the quality of medical care. Copyright © 2018. Published by Elsevier GmbH.

  7. 46 CFR 356.43 - Long-term or exclusive sales contracts.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... the vessel or the vessel's operation, management and harvesting activities. (b) Provisions of a long... control over the operation, management or harvesting activities of the vessel, vessel owner, or bareboat... DOCUMENTATION Charters, Management Agreements and Exclusive or Long-Term Contracts § 356.43 Long-term or...

  8. 25 CFR 542.15 - What are the minimum internal control standards for credit?

    Code of Federal Regulations, 2014 CFR

    2014-04-01

    ...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

  9. 25 CFR 542.15 - What are the minimum internal control standards for credit?

    Code of Federal Regulations, 2013 CFR

    2013-04-01

    ...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

  10. 25 CFR 542.15 - What are the minimum internal control standards for credit?

    Code of Federal Regulations, 2012 CFR

    2012-04-01

    ...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

  11. 25 CFR 542.15 - What are the minimum internal control standards for credit?

    Code of Federal Regulations, 2010 CFR

    2010-04-01

    ...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

  12. 25 CFR 542.15 - What are the minimum internal control standards for credit?

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

  13. The effect of cropping systems and irrigation management on development of potato early blight

    USDA-ARS?s Scientific Manuscript database

    Crop and soil management may modify canopy and belowground microclimate. However, their effects on potential development and control of early blight are not well documented. Crop management systems [Status Quo (SQ), Soil Conserving (SC), Soil Improving (SI), Disease Suppressive (DS), and Continuou...

  14. Proximity Displays for Access Control

    ERIC Educational Resources Information Center

    Vaniea, Kami

    2012-01-01

    Managing access to shared digital information, such as photographs and documents. is difficult for end users who are accumulating an increasingly large and diverse collection of data that they want to share with others. Current policy-management solutions require a user to proactively seek out and open a separate policy-management interface when…

  15. A study of spaceraft technology and design concepts, volume 1

    NASA Technical Reports Server (NTRS)

    Zylius, F. A.

    1985-01-01

    Concepts for advancing the state of the art in the design of unmanned spacecraft, the requirements that gave rise to its configuration, and the programs of technology that are suggested as leading to its eventual development are examined. Particular technology issues discussed include: structures and materials; thermal control; propulsion; electrical power; communications; data management; and guidance, navigation, and control.

  16. Operational Management System for Regulated Water Systems

    NASA Astrophysics Data System (ADS)

    van Loenen, A.; van Dijk, M.; van Verseveld, W.; Berger, H.

    2012-04-01

    Most of the Dutch large rivers, canals and lakes are controlled by the Dutch water authorities. The main reasons concern safety, navigation and fresh water supply. Historically the separate water bodies have been controlled locally. For optimizating management of these water systems an integrated approach was required. Presented is a platform which integrates data from all control objects for monitoring and control purposes. The Operational Management System for Regulated Water Systems (IWP) is an implementation of Delft-FEWS which supports operational control of water systems and actively gives advice. One of the main characteristics of IWP is that is real-time collects, transforms and presents different types of data, which all add to the operational water management. Next to that, hydrodynamic models and intelligent decision support tools are added to support the water managers during their daily control activities. An important advantage of IWP is that it uses the Delft-FEWS framework, therefore processes like central data collection, transformations, data processing and presentation are simply configured. At all control locations the same information is readily available. The operational water management itself gains from this information, but it can also contribute to cost efficiency (no unnecessary pumping), better use of available storage and advise during (water polution) calamities.

  17. Manned Mars mission accommodation: Sprint mission

    NASA Technical Reports Server (NTRS)

    Cirillo, William M.; Kaszubowski, Martin J.; Ayers, J. Kirk; Llewellyn, Charles P.; Weidman, Deene J.; Meredith, Barry D.

    1988-01-01

    The results of a study conducted at the NASA-LaRC to assess the impacts on the Phase 2 Space Station of Accommodating a Manned Mission to Mars are documented. In addition, several candidate transportation node configurations are presented to accommodate the assembly and verification of the Mars Mission vehicles. This study includes an identification of a life science research program that would need to be completed, on-orbit, prior to mission departure and an assessment of the necessary orbital technology development and demonstration program needed to accomplish the mission. Also included is an analysis of the configuration mass properties and a preliminary analysis of the Space Station control system sizing that would be required to control the station. Results of the study indicate the Phase 2 Space Station can support a manned mission to Mars with the addition of a supporting infrastructure that includes a propellant depot, assembly hangar, and a heavy lift launch vehicle to support the large launch requirements.

  18. Coandă configured aircraft: A preliminary analytical assessment

    NASA Astrophysics Data System (ADS)

    Hamid, M. F. Abdul; Gires, E.; Harithuddin, A. S. M.; Abu Talib, A. R.; Rafie, A. S. M.; Romli, F. I.; Harmin, M. Y.

    2017-12-01

    The interest in the use of flow control for enhanced aerodynamic performance has grown, particularly in the use of jets (continuous, synthetic, pulsed, etc.), compliant surface, vortex-cell, and others. It has been widely documented that these active control concepts can dramatically alter the behaviour of aerodynamic components like airfoils, wings and bodies. In this conjunction, with the present demands of low-cost and efficient flights, the use of Coandă effect as a lift enhancer has attracted a lot of interest. Tangential jets that take advantage of the Coandă effect to closely follow the contours of the body have been considered to be simple and particularly effective. For this case, a large mass of surrounding air can be entrained, hence amplifying the circulation. In an effort to optimize the aerodynamic performance of an aircraft, such effect will be critically reviewed by taking advantage of recent progress. For this purpose, in this study, the design of a Coandă-configured aircraft wing will be mathematically idealized and modelled as a two-dimensional flow problem.

  19. The Troll HSE Risk Management System

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Wiig, E.; Berthelsen, I.; Donovan, K.

    1996-12-31

    The Petroleum Act and Internal Control regulations in Norway lay down requirements for how HSE shall be Managed and documented. To comply with the Norwegian legislation the Troll Project has developed an HSE Risk Management System (RMS) structured around Hazards and Effects Management. The resulting quality, technical and operating integrity, and HSE performance are an endorsement of the power of RMS.

  20. US/UK Loan Account Project Status PMOD477

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Stevens, Patrice A.

    2012-07-12

    The viewgraphs describe the status of PMOD477 for LANL. The meeting will occur at DOE-HQ with NA-11 and Military Applications personnel in attendance. Serves to repatriate material with a balance to zero by December 2012. Phase 1 -- Establish formality of operations for War Reserve (WR): Complete surrogate taskings to A90 through a Materials Channel and perform US/UK lessons learned; Complete the US/UK agreed Quality Acceptance Plan, Materials Plan, Shipping procedure, and establish the formal UK/US point of contacts. Phase 2 -- Metal Manufacture (WR): Process material and store material as electrorefined metal (ER) rings, with initial assay and isotopicmore » analysis, prior to manufacturing. Material is cast into accepted configuration and appropriate acceptance document for each aliquot will be generated. Phase 3 -- Intermediate Material Manufacture, Packaging and Shipping (WR): Continue processing of the material in accepted configuration with appropriate acceptance documentation for each aliquot. Provide an initial tasking of the material owed to UK including appropriate quality acceptance documentation. Phase 4 -- Complete Tasking (WR). Phase 5 -- Residue Processing (Non-WR): Complete processing of residue material and waste into accepted configuration with appropriate acceptance document for disposal.« less

  1. Systems and Methods for Collaboratively Controlling at Least One Aircraft

    NASA Technical Reports Server (NTRS)

    Estkowski, Regina I. (Inventor)

    2016-01-01

    An unmanned vehicle management system includes an unmanned aircraft system (UAS) control station controlling one or more unmanned vehicles (UV), a collaborative routing system, and a communication network connecting the UAS and the collaborative routing system. The collaborative routing system being configured to receive flight parameters from an operator of the UAS control station and, based on the received flight parameters, automatically present the UAS control station with flight plan options to enable the operator to operate the UV in a defined airspace.

  2. A feedback linearization approach to spacecraft control using momentum exchange devices. Ph.D. Thesis

    NASA Technical Reports Server (NTRS)

    Dzielski, John Edward

    1988-01-01

    Recent developments in the area of nonlinear control theory have shown how coordiante changes in the state and input spaces can be used with nonlinear feedback to transform certain nonlinear ordinary differential equations into equivalent linear equations. These feedback linearization techniques are applied to resolve two problems arising in the control of spacecraft equipped with control moment gyroscopes (CMGs). The first application involves the computation of rate commands for the gimbals that rotate the individual gyroscopes to produce commanded torques on the spacecraft. The second application is to the long-term management of stored momentum in the system of control moment gyroscopes using environmental torques acting on the vehicle. An approach to distributing control effort among a group of redundant actuators is described that uses feedback linearization techniques to parameterize sets of controls which influence a specified subsystem in a desired way. The approach is adapted for use in spacecraft control with double-gimballed gyroscopes to produce an algorithm that avoids problematic gimbal configurations by approximating sets of gimbal rates that drive CMG rotors into desirable configurations. The momentum management problem is stated as a trajectory optimization problem with a nonlinear dynamical constraint. Feedback linearization and collocation are used to transform this problem into an unconstrainted nonlinear program. The approach to trajectory optimization is fast and robust. A number of examples are presented showing applications to the proposed NASA space station.

  3. EMC system test performance on Spacelab

    NASA Astrophysics Data System (ADS)

    Schwan, F.

    1982-07-01

    Electromagnetic compatibility testing of the Spacelab engineering model is discussed. Documentation, test procedures (including data monitoring and test configuration set up) and performance assessment approach are described. Equipment was assembled into selected representative flight configurations. The physical and functional interfaces between the subsystems were demonstrated within the integration and test sequence which culminated in the flyable configuration Long Module plus one Pallet.

  4. Data management system DIU test system

    NASA Technical Reports Server (NTRS)

    1976-01-01

    An operational and functional description is given of the data management system. Descriptions are included for the test control unit, analog stimulus panel, discrete stimulus panel, and the precision source. The mechanical configuration is defined and illustrated to provide card and component location for modification or repair. The unit level interfaces are mirror images of the DIU interfaces and are described in the Final Technical Report for NASA-MSFC contract NAS8-29155.

  5. A configurable electronics system for the ESS-Bilbao beam position monitors

    NASA Astrophysics Data System (ADS)

    Muguira, L.; Belver, D.; Etxebarria, V.; Varnasseri, S.; Arredondo, I.; del Campo, M.; Echevarria, P.; Garmendia, N.; Feuchtwanger, J.; Jugo, J.; Portilla, J.

    2013-09-01

    A versatile and configurable system has been developed in order to monitorize the beam position and to meet all the requirements of the future ESS-Bilbao Linac. At the same time the design has been conceived to be open and configurable so that it could eventually be used in different kinds of accelerators, independent of the charged particle, with minimal change. The design of the Beam Position Monitors (BPMs) system includes a test bench both for button-type pick-ups (PU) and striplines (SL), the electronic units and the control system. The electronic units consist of two main parts. The first part is an Analog Front-End (AFE) unit where the RF signals are filtered, conditioned and converted to base-band. The second part is a Digital Front-End (DFE) unit which is based on an FPGA board where the base-band signals are sampled in order to calculate the beam position, the amplitude and the phase. To manage the system a Multipurpose Controller (MC) developed at ESSB has been used. It includes the FPGA management, the EPICS integration and Archiver Instances. A description of the system and a comparison between the performance of both PU and SL BPM designs measured with this electronics system are fully described and discussed.

  6. Research on Generating Method of Embedded Software Test Document Based on Dynamic Model

    NASA Astrophysics Data System (ADS)

    Qu, MingCheng; Wu, XiangHu; Tao, YongChao; Liu, Ying

    2018-03-01

    This paper provides a dynamic model-based test document generation method for embedded software that provides automatic generation of two documents: test requirements specification documentation and configuration item test documentation. This method enables dynamic test requirements to be implemented in dynamic models, enabling dynamic test demand tracking to be easily generated; able to automatically generate standardized, standardized test requirements and test documentation, improved document-related content inconsistency and lack of integrity And other issues, improve the efficiency.

  7. TDRSS data handling and management system study. Ground station systems for data handling and relay satellite control

    NASA Technical Reports Server (NTRS)

    1973-01-01

    Results of a two-phase study of the (Data Handling and Management System DHMS) are presented. An original baseline DHMS is described. Its estimated costs are presented in detail. The DHMS automates the Tracking and Data Relay Satellite System (TDRSS) ground station's functions and handles both the forward and return link user and relay satellite data passing through the station. Direction of the DHMS is effected via a TDRSS Operations Control Central (OCC) that is remotely located. A composite ground station system, a modified DHMS (MDHMS), was conceptually developed. The MDHMS performs both the DHMS and OCC functions. Configurations and costs are presented for systems using minicomputers and midicomputers. It is concluded that a MDHMS should be configured with a combination of the two computer types. The midicomputers provide the system's organizational direction and computational power, and the minicomputers (or interface processors) perform repetitive data handling functions that relieve the midicomputers of these burdensome tasks.

  8. Hazard Categorization Reduction via Nature of the Process Argument

    DOE Office of Scientific and Technical Information (OSTI.GOV)

    Chelise A. Van De Graaff; Dr. Chad Pope; J. Todd Taylor

    2012-05-01

    This paper documents the Hazard Categorization (HC) and Critical Safety Evaluation (CSE) for activities performed using an Inspection Object (IO) in excess of the single parameter subcritical limit of 700 g of U-235. By virtue of exceeding the single parameter subcritical limit and the subsequent potential for criticality, the IO HC is initially categorized as HC2. However, a novel application of the nature of the process argument was employed to reduce the IO HC from HC2 to less than HC3 (LTHC3). The IO is composed of five separate uranium metal plates that total no greater than 3.82 kg of U-235more » (U(20)). The IO is planned to be arranged in various configurations. As the IO serves as a standard for experimentation aimed at establishing techniques for detection of fissionable materials, it may be placed in close proximity to various reflectors, moderators, or both. The most reactive configurations of the IO were systematically evaluated and shown that despite the mass of U-235 and potential positioning near various reflectors and moderators, the IO cannot be assembled into a critical configuration. Therefore, the potential for criticality does not exist. With Department of Energy approval, a Hazards Assessment Document with high-level (facility-level) controls on the plates negates the potential for criticality and satisfies the nature of the process argument to reduce the HC from HC2 to LTHC3.« less

  9. An Analysis of Naval Aviation Configuration Status Accounting.

    DTIC Science & Technology

    1983-12-01

    Audit Service Report T30211, Multilocation Audit of Configuration Management of Aeronautical Equipment, 17 August 1982. 18. United States General... Audit and Review .......... 27 III. CONFIGURATION MANAGEMENT STATUS ACCOUNTING WITHIN THE DEPARTMENT OF DEFENSE ........................... 29 A. DOD...included published ar- ticles written by both military and private industry managers, technical papers delivered at symposia and conferences, Naval Audit

  10. Acupuncture for the Management of Postdural Puncture Headache: A Case Report

    PubMed Central

    Chang, Alexandra; Acquah, Joseph; Reddy, Sanjay

    2016-01-01

    Postdural puncture headache (PDPH) is a recognized complication of neuraxial anesthesia. This case report documents 1 patient who developed PDPH following epidural anesthesia for postoperative pain control. The patient declined conventional treatments, including an epidural blood patch and intravenous caffeine. This report documents successful use of adjunct acupuncture for the management of PDPH. Additional research on acupuncture as a potential adjunctive therapy for PDPH is needed, particularly for patients who are reluctant to receive more invasive treatments. PMID:26937320

  11. Advanced Data Acquisition Systems with Self-Healing Circuitry

    NASA Technical Reports Server (NTRS)

    Larson, William E.; Ihlefeld, Curtis M.; Medelius, Pedro J.; Delgado, H. (Technical Monitor)

    2001-01-01

    Kennedy Space Center's Spaceport Engineering & Technology Directorate has developed a data acquisition system that will help drive down the cost of ground launch operations. This system automates both the physical measurement set-up function as well as configuration management documentation. The key element of the system is a self-configuring, self-calibrating, signal-conditioning amplifier that automatically adapts to any sensor to which it is connected. This paper will describe the core technology behind this device and the automated data system in which it has been integrated. The paper will also describe the revolutionary enhancements that are planned for this innovative measurement technology. All measurement electronics devices contain circuitry that, if it fails or degrades, requires the unit to be replaced, adding to the cost of operations. Kennedy Space Center is now developing analog circuits that will be able to detect their own failure and dynamically reconfigure their circuitry to restore themselves to normal operation. This technology will have wide ranging application in all electronic devices used in space and ground systems.

  12. Atypical anatomy of maxillary second premolar with three roots and four canals

    PubMed Central

    Izaz, Shaik; Mandava, Pragna; Bolla, Nagesh; Dasari, Bhargavi

    2017-01-01

    Knowledge and understanding the anatomical configuration of individual tooth play a significant role in success of endodontic treatment, in addition to through debridement and obturation of the canals. The canal anatomy of maxillary second premolar has been studied extensively, and the presence of a significant variety of multirooted canals is relatively rare in it. A 27-year-old female reported with a chief complaint of pain in her upper right posterior region for 10 days. On intraoral hard tissue examination, ill-defined access preparation was seen in maxillary right second premolar with exposed pulp. An intraoral periapical radiograph reveals radiolucency involving the pulp space and varied morphology in the same tooth. The occurrence of three roots with four canals in the maxillary second premolar is rare and not documented in the literature so far. This case report describes the nonsurgical endodontic management of such varied anatomical configuration using cone beam computed tomography as an evaluating diagnostic tool. PMID:29386789

  13. Solar heating and cooling system design and development

    NASA Technical Reports Server (NTRS)

    1978-01-01

    Application surveys and performance studies were conducted to determine a solar heating and hot water configuration that could be used in a variety of applications, and to identify subsystem modules that could be utilized in a building block fashion to adapt hardware items to single and multi-family residential and commercial systems. Topics discussed include: subsystem development for the solar collectors, controls, other components, energy management module, and the heating system configuration test. Operational tests conducted at an Illinois farmhouse, and a YWCA in Spokane, Washington are discussed.

  14. A Model for Effective Systems Engineering Workforce Development at Space and Naval Warfare Systems Center (SSC) Atlantic

    DTIC Science & Technology

    2013-09-01

    Entry  Activity  17.0 CONFIGURAT ION  MANAGEMEN T   Knowledge and basic abilities associated  to perform configuration management  activities  Entry...Activity  17.0 CONFIGURAT ION  MANAGEMEN T   Aware of configuration change control  Entry  Activity  18.0 REQUIREMEN TS MANAGEMENT  Participate in (for...Washington headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202

  15. Optical mass memory system (AMM-13). AMM/DBMS interface control document

    NASA Technical Reports Server (NTRS)

    Bailey, G. A.

    1980-01-01

    The baseline for external interfaces of a 10 to the 13th power bit, optical archival mass memory system (AMM-13) is established. The types of interfaces addressed include data transfer; AMM-13, Data Base Management System, NASA End-to-End Data System computer interconnect; data/control input and output interfaces; test input data source; file management; and facilities interface.

  16. [IMPLEMENTATION OF A QUALITY MANAGEMENT SYSTEM IN A NUTRITION UNIT ACCORDING TO ISO 9001:2008].

    PubMed

    Velasco Gimeno, Cristina; Cuerda Compés, Cristina; Alonso Puerta, Alba; Frías Soriano, Laura; Camblor Álvarez, Miguel; Bretón Lesmes, Irene; Plá Mestre, Rosa; Izquierdo Membrilla, Isabel; García-Peris, Pilar

    2015-09-01

    the implementation of quality management systems (QMS) in the health sector has made great progress in recent years, remains a key tool for the management and improvement of services provides to patients. to describe the process of implementing a quality management system (QMS) according to the standard ISO 9001:2008 in a Nutrition Unit. the implementation began in October 2012. Nutrition Unit was supported by Hospital Preventive Medicine and Quality Management Service (PMQM). Initially training sessions on QMS and ISO standards for staff were held. Quality Committee (QC) was established with representation of the medical and nursing staff. Every week, meeting took place among members of the QC and PMQM to define processes, procedures and quality indicators. We carry on a 2 months follow-up of these documents after their validation. a total of 4 processes were identified and documented (Nutritional status assessment, Nutritional treatment, Monitoring of nutritional treatment and Planning and control of oral feeding) and 13 operating procedures in which all the activity of the Unit were described. The interactions among them were defined in the processes map. Each process has associated specific quality indicators for measuring the state of the QMS, and identifying opportunities for improvement. All the documents associated with requirements of ISO 9001:2008 were developed: quality policy, quality objectives, quality manual, documents and records control, internal audit, nonconformities and corrective and preventive actions. The unit was certified by AENOR in April 2013. the implementation of a QMS causes a reorganization of the activities of the Unit in order to meet customer's expectations. Documenting these activities ensures a better understanding of the organization, defines the responsibilities of all staff and brings a better management of time and resources. QMS also improves the internal communication and is a motivational element. Explore the satisfaction and expectations of patients can include their view in the design of care processes. Copyright AULA MEDICA EDICIONES 2014. Published by AULA MEDICA. All rights reserved.

  17. Media independent interface. Interface control document

    NASA Technical Reports Server (NTRS)

    1987-01-01

    A Media Independent Interface (MII) is specified, using current standards in the industry. The MII is described in hierarchical fashion. At the base are IEEE/International Standards Organization (ISO) documents (standards) which describe the functionality of the software modules or layers and their interconnection. These documents describe primitives which are to transcent the MII. The intent of the MII is to provide a universal interface to one or more Media Access Contols (MACs) for the Logical Link Controller and Station Manager. This interface includes both a standardized electrical and mechanical interface and a standardized functional specification which defines the services expected from the MAC.

  18. Application of Bridge Pier Scour Equations for Large Woody Vegetation

    DTIC Science & Technology

    2016-07-01

    official Department of the Army position unless so designated by other authorized documents. DESTROY THIS REPORT WHEN NO LONGER NEEDED. DO NOT...11 Figure 3. Standing tree test configuration, pretest ...12 Figure 4. Fallen tree test configuration, pretest

  19. Understanding how train dispatchers manage and control trains : results of a cognitive task analysis

    DOT National Transportation Integrated Search

    2001-05-01

    This report documents the results of a Cognitive Task Analysis that examined how experienced railroad dispatchers manage and : schedule trains in todays environment. The objective was to understand the cognitive demands placed on railroad dispatch...

  20. Report on Tick-Borne Disease and Integrated Pest Management Conference

    EPA Pesticide Factsheets

    The US Environmental Protection Agency (EPA) and the Centers for Disease Control and Prevention (CDC) co-hosted a conference on Tick-Borne Disease Integrated Pest Management on March 5-6, 2013, in Arlington, VA. This document summarizes this meeting.

  1. Understanding how train dispatchers manage and control trains : results of a cognitive task analysis

    DOT National Transportation Integrated Search

    2001-05-01

    This report documents the results ofaCognitive Task Analysis that examined how experienced railroad dispatchers manage and : schedule trains in today's environment. The objective was to understand the cognitive demands placed on railroad dispatchers ...

  2. Understanding how train dispatchers manage and control trains : results of a cognitive task analysis.

    DOT National Transportation Integrated Search

    2001-05-01

    This report documents the results of a Cognitive Task Analysis that examined how experienced railroad dispatchers manage and schedule trains in todays environment. The objective was to understand the cognitive demands placed on railroad dispatcher...

  3. Food and Beverage Control. Food and Beverage Management Module. Operational Management Programme. Increasing Opportunities for Supervisors and Managers.

    ERIC Educational Resources Information Center

    Jones, Peter

    This self-instructional unit for supervisors and managers in the British hotel and catering industry is intended to consolidate work covered in a 1-day course. The unit covers the key management functions needed to implement an effective purchasing and supply policy. The document begins with an introduction and advice on how to use the unit. The…

  4. Naver: a PC-cluster-based VR system

    NASA Astrophysics Data System (ADS)

    Park, ChangHoon; Ko, HeeDong; Kim, TaiYun

    2003-04-01

    In this paper, we present a new framework NAVER for virtual reality application. The NAVER is based on a cluster of low-cost personal computers. The goal of NAVER is to provide flexible, extensible, scalable and re-configurable framework for the virtual environments defined as the integration of 3D virtual space and external modules. External modules are various input or output devices and applications on the remote hosts. From the view of system, personal computers are divided into three servers according to its specific functions: Render Server, Device Server and Control Server. While Device Server contains external modules requiring event-based communication for the integration, Control Server contains external modules requiring synchronous communication every frame. And, the Render Server consists of 5 managers: Scenario Manager, Event Manager, Command Manager, Interaction Manager and Sync Manager. These managers support the declaration and operation of virtual environment and the integration with external modules on remote servers.

  5. Marketing: Managing the Marketing Mix. Courseware Evaluation for Vocational and Technical Education.

    ERIC Educational Resources Information Center

    Fleming, Lian; And Others

    This courseware evaluation rates the Marketing: Managing the Marketing Mix program developed by Control Data Limited. (This program--not contained in this document--is designed to introduce decisions made by marketing managers during the implementation phase of marketing.) Part A describes the program in terms of subject area (marketing, decision…

  6. Draft Guidelines for State and Areawide Water Quality Management Program Development.

    ERIC Educational Resources Information Center

    Environmental Protection Agency, Washington, DC.

    This document discusses the draft guidelines formulated by the Environmental Protection Agency (EPA) to assist the states in establishing a management program to integrate water quality and other resource management decisions. These guidelines are pfovided so that the long range goals of the Federal Water Pollution Control Act Amendments of 1972…

  7. Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

    NASA Technical Reports Server (NTRS)

    Bolen, Kenny; Greenlaw, Ronald

    2010-01-01

    A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

  8. Euler Technology Assessment for Preliminary Aircraft Design-Unstructured/Structured Grid NASTD Application for Aerodynamic Analysis of an Advanced Fighter/Tailless Configuration

    NASA Technical Reports Server (NTRS)

    Michal, Todd R.

    1998-01-01

    This study supports the NASA Langley sponsored project aimed at determining the viability of using Euler technology for preliminary design use. The primary objective of this study was to assess the accuracy and efficiency of the Boeing, St. Louis unstructured grid flow field analysis system, consisting of the MACGS grid generation and NASTD flow solver codes. Euler solutions about the Aero Configuration/Weapons Fighter Technology (ACWFT) 1204 aircraft configuration were generated. Several variations of the geometry were investigated including a standard wing, cambered wing, deflected elevon, and deflected body flap. A wide range of flow conditions, most of which were in the non-linear regimes of the flight envelope, including variations in speed (subsonic, transonic, supersonic), angles of attack, and sideslip were investigated. Several flowfield non-linearities were present in these solutions including shock waves, vortical flows and the resulting interactions. The accuracy of this method was evaluated by comparing solutions with test data and Navier-Stokes solutions. The ability to accurately predict lateral-directional characteristics and control effectiveness was investigated by computing solutions with sideslip, and with deflected control surfaces. Problem set up times and computational resource requirements were documented and used to evaluate the efficiency of this approach for use in the fast paced preliminary design environment.

  9. An ontology-based semantic configuration approach to constructing Data as a Service for enterprises

    NASA Astrophysics Data System (ADS)

    Cai, Hongming; Xie, Cheng; Jiang, Lihong; Fang, Lu; Huang, Chenxi

    2016-03-01

    To align business strategies with IT systems, enterprises should rapidly implement new applications based on existing information with complex associations to adapt to the continually changing external business environment. Thus, Data as a Service (DaaS) has become an enabling technology for enterprise through information integration and the configuration of existing distributed enterprise systems and heterogonous data sources. However, business modelling, system configuration and model alignment face challenges at the design and execution stages. To provide a comprehensive solution to facilitate data-centric application design in a highly complex and large-scale situation, a configurable ontology-based service integrated platform (COSIP) is proposed to support business modelling, system configuration and execution management. First, a meta-resource model is constructed and used to describe and encapsulate information resources by way of multi-view business modelling. Then, based on ontologies, three semantic configuration patterns, namely composite resource configuration, business scene configuration and runtime environment configuration, are designed to systematically connect business goals with executable applications. Finally, a software architecture based on model-view-controller (MVC) is provided and used to assemble components for software implementation. The result of the case study demonstrates that the proposed approach provides a flexible method of implementing data-centric applications.

  10. Vortical flow management for improved configuration aerodynamics: Recent experiences

    NASA Technical Reports Server (NTRS)

    Rao, D. M.

    1983-01-01

    Recent progress in vortex-control applications for alleviating the adverse consequences of three dimensional separation and vortical interactions on slender body/swept wing configurations is reported. Examples include helical separation trip to alleviate the side force due to forebody vortex asymmetry; hinged strakes to avoid vortex breakdown effects; compartmentation of swept leading edge separation to delay the pitch-up instability; under wing vortex trip and vortex trip and vortex flaps for drag reduction at high lift; and an apex-flap trimmer to fully utilize the lift capability of trailing-edge flaps for take off and landing of delta wings. Experimental results on generic wind-tunnel models are presented to illustrate the vortex-management concepts involved and to indicate their potential for enhancing the subsonic aerodynamics of supersonic-cruise type vehicles.

  11. Configuration management and software measurement in the Ground Systems Development Environment (GSDE)

    NASA Technical Reports Server (NTRS)

    Church, Victor E.; Long, D.; Hartenstein, Ray; Perez-Davila, Alfredo

    1992-01-01

    A set of functional requirements for software configuration management (CM) and metrics reporting for Space Station Freedom ground systems software are described. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the Space Station Training Facility (SSTF) and the Space Station Control Center (SSCC), and the target systems for SSCC and SSTF. The focus is on the CM of the software following delivery to NASA and on the software metrics that relate to the quality and maintainability of the delivered software. The CM and metrics requirements address specific problems that occur in large-scale software development. Mechanisms to assist in the continuing improvement of mission operations software development are described.

  12. Is Your Biobank Up to Standards? A Review of the National Canadian Tissue Repository Network Required Operational Practice Standards and the Controlled Documents of a Certified Biobank.

    PubMed

    Hartman, Victoria; Castillo-Pelayo, Tania; Babinszky, Sindy; Dee, Simon; Leblanc, Jodi; Matzke, Lise; O'Donoghue, Sheila; Carpenter, Jane; Carter, Candace; Rush, Amanda; Byrne, Jennifer; Barnes, Rebecca; Mes-Messons, Anne-Marie; Watson, Peter

    2018-02-01

    Ongoing quality management is an essential part of biobank operations and the creation of high quality biospecimen resources. Adhering to the standards of a national biobanking network is a way to reduce variability between individual biobank processes, resulting in cross biobank compatibility and more consistent support for health researchers. The Canadian Tissue Repository Network (CTRNet) implemented a set of required operational practices (ROPs) in 2011 and these serve as the standards and basis for the CTRNet biobank certification program. A review of these 13 ROPs covering 314 directives was conducted after 5 years to identify areas for revision and update, leading to changes to 7/314 directives (2.3%). A review of all internal controlled documents (including policies, standard operating procedures and guides, and forms for actions and processes) used by the BC Cancer Agency's Tumor Tissue Repository (BCCA-TTR) to conform to these ROPs was then conducted. Changes were made to 20/106 (19%) of BCCA-TTR documents. We conclude that a substantial fraction of internal controlled documents require updates at regular intervals to accommodate changes in best practices. Reviewing documentation is an essential aspect of keeping up to date with best practices and ensuring the quality of biospecimens and data managed by biobanks.

  13. Advanced Aircraft Electrical System Control Technology Demonstrator. Phase I. Requirements Analysis and Conceptual Design.

    DTIC Science & Technology

    1981-07-01

    System 13 (7) Flight Critical Power 15 (8) Power Bus Configuration 16 b. System Control and Protection 20...includes the main buses, external power receptacles and distribution feeders. The function of the distribution protection system * is mainly to provide...TechnicaI rea Manager Power Systems Branch Power Systems B nch Aerospace Power Division Aerospace Power Division FOR .AKE D . REAMS Chief,

  14. The Intelligent Flight Control Program (IFCS)

    NASA Technical Reports Server (NTRS)

    2004-01-01

    This is the closeout report for the Research Cooperative Agreement NCC4-00130 of accomplishments for the Intelligent Flight Control System (IFCS) Project. It has been a pleasure working with NASA and NASA partners as we strive to meet the goals of this research initiative. ISR was engaged in this Research Cooperative Agreement beginning 01 January 2003 and ending 31 January 2004. During this time ISR conducted efforts towards development of the ARTS II Computer Software Configuration Item (CSCI) version 4.0 by performing or developing the following: 1) Requirements Definition; 2) Software Design and Development; 3) Hardware In the Loop Simulation; 4) Unit Level testing; 5) Documentation.

  15. ControlShell: A real-time software framework

    NASA Technical Reports Server (NTRS)

    Schneider, Stanley A.; Chen, Vincent W.; Pardo-Castellote, Gerardo

    1994-01-01

    The ControlShell system is a programming environment that enables the development and implementation of complex real-time software. It includes many building tools for complex systems, such as a graphical finite state machine (FSM) tool to provide strategic control. ControlShell has a component-based design, providing interface definitions and mechanisms for building real-time code modules along with providing basic data management. Some of the system-building tools incorporated in ControlShell are a graphical data flow editor, a component data requirement editor, and a state-machine editor. It also includes a distributed data flow package, an execution configuration manager, a matrix package, and an object database and dynamic binding facility. This paper presents an overview of ControlShell's architecture and examines the functions of several of its tools.

  16. 9 CFR 318.309 - Finished product inspection.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... microbiological contamination; (2) An FSIS-approved total quality control system; (3) Alternative documented... associated with microbial contamination, where there is no approved total quality control system, or where... Office of Management and Budget under control number 0583-0015) [51 FR 45619, Dec. 19, 1986, as amended...

  17. DPM: Future Proof Storage

    NASA Astrophysics Data System (ADS)

    Alvarez, Alejandro; Beche, Alexandre; Furano, Fabrizio; Hellmich, Martin; Keeble, Oliver; Rocha, Ricardo

    2012-12-01

    The Disk Pool Manager (DPM) is a lightweight solution for grid enabled disk storage management. Operated at more than 240 sites it has the widest distribution of all grid storage solutions in the WLCG infrastructure. It provides an easy way to manage and configure disk pools, and exposes multiple interfaces for data access (rfio, xroot, nfs, gridftp and http/dav) and control (srm). During the last year we have been working on providing stable, high performant data access to our storage system using standard protocols, while extending the storage management functionality and adapting both configuration and deployment procedures to reuse commonly used building blocks. In this contribution we cover in detail the extensive evaluation we have performed of our new HTTP/WebDAV and NFS 4.1 frontends, in terms of functionality and performance. We summarize the issues we faced and the solutions we developed to turn them into valid alternatives to the existing grid protocols - namely the additional work required to provide multi-stream transfers for high performance wide area access, support for third party copies, credential delegation or the required changes in the experiment and fabric management frameworks and tools. We describe new functionality that has been added to ease system administration, such as different filesystem weights and a faster disk drain, and new configuration and monitoring solutions based on the industry standards Puppet and Nagios. Finally, we explain some of the internal changes we had to do in the DPM architecture to better handle the additional load from the analysis use cases.

  18. Liquid Pipeline Operator's Control Room Human Factors Risk Assessment and Management Guide

    DOT National Transportation Integrated Search

    2008-11-26

    The purpose of this guide is to document methodologies, tools, procedures, guidance, and instructions that have been developed to provide liquid pipeline operators with an efficient and effective means of managing the human factors risks in their con...

  19. Understanding how train dispatchers manage and control trains : results of a cognitive task analysis

    DOT National Transportation Integrated Search

    1999-03-01

    This report documents the results of a preliminary Cognitive Task Analysis (CTA) that examined how experienced train dispatchers manage and : schedule trains in today's environment The objective was to understand the cognitive demands placed on train...

  20. NICKEL PLATING: INDUSTRY PRACTICES, CONTROL TECHNOLOGIES, AND ENVIRONMENTAL MANAGEMENT

    EPA Science Inventory

    This report was prepared under the direction of EPA's ORD to assist the metal finishing community with the management of nickel plating environmental issues. This report provides the rationale for developing the document, identifies the intended user audience, and presents the fr...

  1. Requirements, Resource Planning, and Management for Decrewing/Recrewing Scenarios of the International Space Station

    NASA Technical Reports Server (NTRS)

    Bach, David A.; Brand, Susan N.; Hasbrook, Peter V.

    2013-01-01

    Following the failure of 44 Progress (44P) on launch in August 2011, and the subsequent grounding of all Russian Soyuz rocket based launches, the International Space Station (ISS) ground teams engaged in an effort to determine how long the ISS could remain crewed, what would be required to safely configure the ISS for decrewing, and what would be required to recrew the ISS upon resumption of Soyuz rocket launches if decrewing became necessary. This White Paper was written to capture the processes and lessons learned from real-time time events and to provide a reference and training document for ISS Program teams in the event decrewing of the ISS is needed. Through coordination meetings and assessments, teams identified six decrewing priorities for ground and crew operations. These priorities were integrated along with preflight priorities through the Increment re-planning process. Additionally, the teams reviewed, updated, and implemented changes to the governing documentation for the configuration of the ISS for a contingency decrewing event. Steps were taken to identify critical items for disposal prior to decrewing, as well as identifying the required items to be strategically staged or flown with the astronauts and cosmonauts who would eventually recrew the ISS. After the successful launches and dockings of both 45P and 28 Soyuz (28S), the decrewing team transitioned to finalizing and publishing the documentation for standardizing the decrewing flight rules. With the continued launching of crews and cargo to the ISS, utilization and science is again a high priority; both Increment pairs 29 and 30, and Increment 31 and 32 reaching the milestone of at least 35 hours per week average utilization.

  2. Requirements, Resource Planning and Management for Decrewing/Recrewing Scenarios of the International Space Station

    NASA Astrophysics Data System (ADS)

    Bach, David A.; Brand, Susan N.; Hasbrook, Peter V.

    2013-09-01

    Following the failure of 44 Progress (44P) on launch in August 2011, and the subsequent grounding of all Russian Soyuz rocket based launches, the International Space Station (ISS) ground teams engaged in an effort to determine how long the ISS could remain crewed, what would be required to safely configure the ISS for decrewing, and what would be required to recrew the ISS upon resumption of Soyuz rocket launches if decrewing became necessary. This White Paper was written to capture the processes and lessons learned from real-time time events and to provide a reference and training document for ISS Program teams in the event decrewing of the ISS is needed.Through coordination meetings and assessments, teams identified six decrewing priorities for ground and crew operations. These priorities were integrated along with preflight priorities through the Increment re-planning process. Additionally, the teams reviewed, updated, and implemented changes to the governing documentation for the configuration of the ISS for a contingency decrewing event. Steps were taken to identify critical items for disposal prior to decrewing, as well as identifying the required items to be strategically staged or flown with the astronauts and cosmonauts who would eventually recrew the ISS.After the successful launches and dockings of both 45P and 28 Soyuz (28S), the decrewing team transitioned to finalizing and publishing the documentation for standardizing the decrewing flight rules. With the continued launching of crews and cargo to the ISS, utilization and science is again a high priority; both Increment pairs 29 and 30, and Increment 31 and 32 reaching the milestone of at least 35 hours per week average utilization.

  3. Space Station Freedom - Configuration management approach to supporting concurrent engineering and total quality management. [for NASA Space Station Freedom Program

    NASA Technical Reports Server (NTRS)

    Gavert, Raymond B.

    1990-01-01

    Some experiences of NASA configuration management in providing concurrent engineering support to the Space Station Freedom program for the achievement of life cycle benefits and total quality are discussed. Three change decision experiences involving tracing requirements and automated information systems of the electrical power system are described. The potential benefits of concurrent engineering and total quality management include improved operational effectiveness, reduced logistics and support requirements, prevention of schedule slippages, and life cycle cost savings. It is shown how configuration management can influence the benefits attained through disciplined approaches and innovations that compel consideration of all the technical elements of engineering and quality factors that apply to the program development, transition to operations and in operations. Configuration management experiences involving the Space Station program's tiered management structure, the work package contractors, international partners, and the participating NASA centers are discussed.

  4. Large-Scale Operations Management Test of Use of the White Amur for Control of Problem Aquatic Plants. Report 2. First Year Poststocking Results. Volume II. The Fish, Mammals, and Waterfowl of Lake Conway, Florida.

    DTIC Science & Technology

    1982-02-01

    7AD-AI3 853 ’FLORIDA SAME AND FRESH WATER FISH COMMISSION ORLANDO F/ 616 LARGE-SCALE OPERATIONS MANAGEMENT TEST OF USE OF THE WHITE AMUR--ETC(U...of a series of reports documenting a large-scale operations management test of use of the white amur for control of problem aquatic plants in Lake...M. 1982. "Large-Scale Operations Management Test of Use of the White Amur for Control of Problem Aquatic Plants; Report 2, First Year Poststock- ing

  5. Guidance Document on Anaerobic Digester Foaming Prevention and Control Methods (WERF Report INFR1SG10a)

    EPA Science Inventory

    The development of this anaerobic digester (AD) foaming guidance document is based on the need for a specific detailed methodology that water resource recovery facilities (WRRF) personnel can follow and implement to manage or mitigate AD foam incidents. This guidance manual is th...

  6. 29 CFR 2520.102-3 - Contents of summary plan description.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... document that accompanies the plan's SPD, provided that the document satisfies the style and format... descriptive provisions in addition to those prescribed in paragraph (t)(2) of this section. However, the style... Office of Management and Budget under control number 1210-0039) [42 FR 37180, July 19, 1977, as amended...

  7. A dynamically reconfigurable multi-functional PLL for SRAM-based FPGA in 65nm CMOS technology

    NASA Astrophysics Data System (ADS)

    Yang, Mingqian; Chen, Lei; Li, Xuewu; Zhang, Yanlong

    2018-04-01

    Phase-locked loops (PLL) have been widely utilized in FPGA as an important module for clock management. PLL with dynamic reconfiguration capability is always welcomed in FPGA design as it is able to decrease power consumption and simultaneously improve flexibility. In this paper, a multi-functional PLL with dynamic reconfiguration capability for 65nm SRAM-based FPGA is proposed. Firstly, configurable charge pump and loop filter are utilized to optimize the loop bandwidth. Secondly, the PLL incorporates a VCO with dual control voltages to accelerate the adjustment of oscillation frequency. Thirdly, three configurable dividers are presented for flexible frequency synthesis. Lastly, a configuration block with dynamic reconfiguration function is proposed. Simulation results demonstrate that the proposed multi-functional PLL can output clocks with configurable division ratio, phase shift and duty cycle. The PLL can also be dynamically reconfigured without affecting other parts' running or halting the FPGA device.

  8. Configuration management issues and objectives for a real-time research flight test support facility

    NASA Technical Reports Server (NTRS)

    Yergensen, Stephen; Rhea, Donald C.

    1988-01-01

    An account is given of configuration management activities for the Western Aeronautical Test Range (WATR) at NASA-Ames, whose primary function is the conduct of aeronautical research flight testing through real-time processing and display, tracking, and communications systems. The processing of WATR configuration change requests for specific research flight test projects must be conducted in such a way as to refrain from compromising the reliability of WATR support to all project users. Configuration management's scope ranges from mission planning to operations monitoring and performance trend analysis.

  9. Summary of solar cell data from the Long Duration Exposure Facility (LDEF)

    NASA Technical Reports Server (NTRS)

    Hill, David C.; Rose, M. Frank

    1994-01-01

    The contractor has obtained and reviewed data relating solar cells assemblies (SCA's) flown as part of the following LDEF experiments: the Advanced Photovoltaic Experiment (S0014); the Solar Array Materials Passive LDEF Experiment (A0171); the Advanced Solar Cell and Coverglass Analysis Experiment (M0003-4); the LDEF Heat Pipe Experiment (S1001); the Evaluation of Thermal Control Coatings Y Solar Cells Experiment (S1002); and the Space Plasma-High Voltage Drainage Experiment (A0054). Where possible, electrical data have been tabulated and correlated with various environmental effects, including meteoroid and debris impacts, radiation exposure, atomic oxygen exposure, contamination, UV radiation exposure, and thermal cycling. The type, configuration, and location of all SCA's are documented here. By gathering all data and results together, a comparison of the survivability of the various types and configurations can be made.

  10. A Method of Retrospective Computerized System Validation for Drug Manufacturing Software Considering Modifications

    NASA Astrophysics Data System (ADS)

    Takahashi, Masakazu; Fukue, Yoshinori

    This paper proposes a Retrospective Computerized System Validation (RCSV) method for Drug Manufacturing Software (DMSW) that relates to drug production considering software modification. Because DMSW that is used for quality management and facility control affects big impact to quality of drugs, regulatory agency required proofs of adequacy for DMSW's functions and performance based on developed documents and test results. Especially, the work that explains adequacy for previously developed DMSW based on existing documents and operational records is called RCSV. When modifying RCSV conducted DMSW, it was difficult to secure consistency between developed documents and test results for modified DMSW parts and existing documents and operational records for non-modified DMSW parts. This made conducting RCSV difficult. In this paper, we proposed (a) definition of documents architecture, (b) definition of descriptive items and levels in the documents, (c) management of design information using database, (d) exhaustive testing, and (e) integrated RCSV procedure. As a result, we could conduct adequate RCSV securing consistency.

  11. Integration and Test for Small Shuttle Payloads

    NASA Technical Reports Server (NTRS)

    Wright, Michael R.; Day, John H. (Technical Monitor)

    2001-01-01

    Recommended approaches for shuttle small payload integration and test (I&T) are presented. The paper is intended for consideration by developers of small shuttle payloads, including I&T managers, project managers, and system engineers. Examples and lessons learned are presented based on the extensive history of the NASA's Hitchhiker project. All aspects of I&T are presented, including: (1) I&T team responsibilities, coordination, and communication; (2) Flight hardware handling practices; (3) Documentation and configuration management; (4) I&T considerations for payload development; (5) I&T at the development facility; (6) Prelaunch operations, transfer, orbiter integration, and interface testing; and (7) Postflight operations. This paper is of special interest to those payload projects which have small budgets and few resources: That is, the truly 'faster, cheaper, better' projects. All shuttle small payload developers are strongly encouraged to apply these guidelines during I&T planning and ground operations to take full advantage of today's limited resources and to help ensure mission success.

  12. Adaptive mechanism-based congestion control for networked systems

    NASA Astrophysics Data System (ADS)

    Liu, Zhi; Zhang, Yun; Chen, C. L. Philip

    2013-03-01

    In order to assure the communication quality in network systems with heavy traffic and limited bandwidth, a new ATRED (adaptive thresholds random early detection) congestion control algorithm is proposed for the congestion avoidance and resource management of network systems. Different to the traditional AQM (active queue management) algorithms, the control parameters of ATRED are not configured statically, but dynamically adjusted by the adaptive mechanism. By integrating with the adaptive strategy, ATRED alleviates the tuning difficulty of RED (random early detection) and shows a better control on the queue management, and achieve a more robust performance than RED under varying network conditions. Furthermore, a dynamic transmission control protocol-AQM control system using ATRED controller is introduced for the systematic analysis. It is proved that the stability of the network system can be guaranteed when the adaptive mechanism is finely designed. Simulation studies show the proposed ATRED algorithm achieves a good performance in varying network environments, which is superior to the RED and Gentle-RED algorithm, and providing more reliable service under varying network conditions.

  13. Food and Beverage Management: An Introduction. Food and Beverage Management Module. Operational Management Programme. Increasing Opportunities for Supervisors and Managers.

    ERIC Educational Resources Information Center

    Jones, Peter

    This self-instructional unit for supervisors and managers in the British hotel and catering industry is designed to prepare them for the more detailed units in this series, including those on food and beverage control, production, and provision. The document begins with advice on how to use the unit. Three sections cover the following topics: (1)…

  14. LSP Composite Susbtrate Manufacturing Processing Guide

    NASA Technical Reports Server (NTRS)

    Kovach, Daniel J.; Griess, Kenneth H.

    2013-01-01

    This document is intended to define Carbon Fiber Reinforced Plastic (CFRP) test panel configurations that can be employed for the purposes of evaluating the protection capabilities of Lightning Strike Protection (LSP) materials developed by the Aerospace Industry. The configurations are intended to provide consistent behavior in their response to simulated lightning strikes at pre-defined levels when tested by a capable vendor according to a test procedure written to enable consistent results (ref section 2.1.2). In response to an attachment of a simulated lightning strike on a CFRP panel, one can expect to see various levels of ablation and delamination, both through the thickness of the panel and with respect to the amount of panel surface area that exhibits damage. Panel configurations defined in this document include: An "unprotected" configuration 128694-1 (ref section 4.1), consisting of a cured CFRP laminate stackup of tape and fabric prepregs, coated with a typical aerospace primer and paint finishing scheme, attached to aluminum grounding bars intended to draw electrical current from the lightning attachment point to the panel edges and thus to ground. A "protected" configuration 128694-2 (ref section 4.1), wherein a layer of an LSP material form often used in the Aerospace Industry is included in the laminate stackup prior to cure. The CFRP materials, finishes and grounding arrangement for ths configuration are the same as for the "unprotected" configuration.

  15. VERIFICATION TESTING OF AIR POLLUTION CONTROL TECHNOLOGY QUALITY MANAGEMENT PLAN

    EPA Science Inventory

    This document is the basis for quality assurance for the Air Pollution Control Technology Verification Center (APCT Center) operated under the U.S. Environmental Protection Agency (EPA). It describes the policies, organizational structure, responsibilities, procedures, and qualit...

  16. Criteria Underlying the Formation of Alternative IMS Configurations.

    ERIC Educational Resources Information Center

    Dave, Ashok

    To assist the formation of IMS (Instructional Management System) configurations, three categories of characteristics are developed and explained. Categories 1 and 2 emphasize automation, and the necessity of forming workable configurations to carry out instructional management for Southwest Regional Laboratory developed instructional and/or…

  17. 9 CFR 381.309 - Finished product inspection.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ... FSIS-approved total quality control system; or (3) Alternative documented procedures that will ensure... contamination, where there is no approved total quality control system, or where the establishment has no... Office of Management and Budget under control number 0583-0015) [51 FR 45634, Dec. 19, 1986, as amended...

  18. Variable Geometry Aircraft Pylon Structure and Related Operation Techniques

    NASA Technical Reports Server (NTRS)

    Shah, Parthiv N. (Inventor)

    2014-01-01

    An aircraft control structure can be utilized for purposes of drag management, noise control, or aircraft flight maneuvering. The control structure includes a high pressure engine nozzle, such as a bypass nozzle or a core nozzle of a turbofan engine. The nozzle exhausts a high pressure fluid stream, which can be swirled using a deployable swirl vane architecture. The control structure also includes a variable geometry pylon configured to be coupled between the nozzle and the aircraft. The variable geometry pylon has a moveable pylon section that can be deployed into a deflected state to maintain or alter a swirling fluid stream (when the swirl vane architecture is deployed) for drag management purposes, or to assist in the performance of aircraft flight maneuvers.

  19. Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

    NASA Technical Reports Server (NTRS)

    Williams, David E.

    2010-01-01

    Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

  20. Lessons Learned from the Node 1 Atmosphere Control and Storage and Water Recovery and Management Subsystem Design

    NASA Technical Reports Server (NTRS)

    Williams, David E.

    2011-01-01

    Node 1 flew to the International Space Station (ISS) on Flight 2A during December 1998. To date the National Aeronautics and Space Administration (NASA) has learned a lot of lessons from this module based on its history of approximately two years of acceptance testing on the ground and currently its twelve years on-orbit. This paper will provide an overview of the ISS Environmental Control and Life Support (ECLS) design of the Node 1 Atmosphere Control and Storage (ACS) and Water Recovery and Management (WRM) subsystems and it will document some of the lessons that have been learned to date for these subsystems based on problems prelaunch, problems encountered on-orbit, and operational problems/concerns. It is hoped that documenting these lessons learned from ISS will help in preventing them in future Programs.

  1. 78 FR 20324 - Proposed Information Collection Activity: Comment Request

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-04-04

    ..., document the experiences of program participants, examine differences in service receipt and educational experiences between program and control group members, describe the intervention as it was implemented in each... leadership/ managers, instructional staff, case managers/advisors, partners and employers; (d) a brief survey...

  2. [Quality control of laser imagers].

    PubMed

    Winkelbauer, F; Ammann, M; Gerstner, N; Imhof, H

    1992-11-01

    Multiformat imagers based on laser systems are used for documentation in an increasing number of investigations. The specific problems of quality control are explained and the persistence of film processing in these imager systems of different configuration with (Machine 1: 3M-Laser-Imager-Plus M952 with connected 3M Film-Processor, 3M-Film IRB, X-Rax Chemical Mixer 3M-XPM, 3M-Developer and Fixer) or without (Machine 2: 3M-Laser-Imager-Plus M952 with separate DuPont-Cronex Film-processor, Kodak IR-Film, Kodak Automixer, Kodak-Developer and Fixer) connected film processing unit are investigated. In our checking based on DIN 6868 and ONORM S 5240 we found persistence of film processing in the equipment with directly adapted film processing unit according to DIN and ONORM. The checking of film persistence as demanded by DIN 6868 in these equipment could therefore be performed in longer periods. Systems with conventional darkroom processing comparatively show plain increased fluctuation, and hence the demanded daily control is essential to guarantee appropriate reaction and constant quality of documentation.

  3. REVEAL: Software Documentation and Platform Migration

    NASA Technical Reports Server (NTRS)

    Wilson, Michael A.; Veibell, Victoir T.

    2011-01-01

    The Research Environment for Vehicle Embedded Analysis on Linux (REVEAL) is reconfigurable data acquisition software designed for network-distributed test and measurement applications. In development since 2001, it has been successfully demonstrated in support of a number of actual missions within NASA's Suborbital Science Program. Improvements to software configuration control were needed to properly support both an ongoing transition to operational status and continued evolution of REVEAL capabilities. For this reason the project described in this report targets REVEAL software source documentation and deployment of the software on a small set of hardware platforms different from what is currently used in the baseline system implementation. This presentation specifically describes the actions taken over a ten week period by two undergraduate student interns and serves as an overview of the content of the final report for that internship.

  4. Management: A bibliography for NASA managers (supplement 21)

    NASA Technical Reports Server (NTRS)

    1987-01-01

    This bibliography lists 664 reports, articles and other documents introduced into the NASA scientific and technical information system in 1986. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs, and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  5. Management: A bibliography for NASA Managers

    NASA Technical Reports Server (NTRS)

    1986-01-01

    This bibliography lists 707 reports, articles and other documents introduced into the NASA scientific and technology information system in 1985. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs, and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  6. Management: A bibliography for NASA managers

    NASA Technical Reports Server (NTRS)

    1991-01-01

    This bibliography lists 731 reports, articles and other documents introduced into the NASA Scientific and Technical Information System in 1990. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  7. Management: A bibliography for NASA managers

    NASA Technical Reports Server (NTRS)

    1990-01-01

    This bibliography lists 755 reports, articles and other documents introduced into the NASA Scientific and Technical Information System in 1989. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  8. Management: A bibliography for NASA managers

    NASA Technical Reports Server (NTRS)

    1989-01-01

    This bibliography lists 822 reports, articles and other documents introduced into the NASA Scientific and Technical Information System in 1988. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  9. Management: A bibliography for NASA managers

    NASA Technical Reports Server (NTRS)

    1992-01-01

    This bibliography lists 630 reports, articles and other documents introduced into the NASA Scientific and Technical Information System in 1991. Items are selected and grouped according to their usefulness to the manager as manager. Citations are grouped into ten subject categories: human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs and markets; logistics and operations management; reliability and quality control; and legality, legislation, and policy.

  10. Management: A bibliography for NASA managers

    NASA Technical Reports Server (NTRS)

    1988-01-01

    This bibliography lists 653 reports, articles and other documents introduced into the NASA scientific and technical information system in 1987. Items are selected and grouped according to their usefulness to the manager as manager. Citiations are grouped into ten subject categories; human factors and personnel issues; management theory and techniques; industrial management and manufacturing; robotics and expert systems; computers and information management; research and development; economics, costs and markets; logistics and operations management, reliability and quality control; and legality, legislation, and policy.

  11. Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)

    NASA Technical Reports Server (NTRS)

    Vipavetz, Kevin; Shull, Thomas A.; Infeld, Samatha; Price, Jim

    2016-01-01

    The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.

  12. Integrated Autonomous Network Management (IANM) Multi-Topology Route Manager and Analyzer

    DTIC Science & Technology

    2008-02-01

    zebra tmg mtrcli xinetd (tftp) mysql configuration file (mtrrm.conf) configuration file (mtrrmAggregator.properties) tftp files /tftpboot NetFlow PDUs...configuration upload/download snmp, telnet OSPFv2 user interface tmg Figure 6-2. Internal software organization Figure 6-2 illustrates the main

  13. Large angle magnetic suspension test fixture

    NASA Technical Reports Server (NTRS)

    Britcher, Colin P.

    1993-01-01

    Progress made under the subject grant in the period from 1 Nov. 1992 to 31 May 1993 is presented. The research involves the continued development of the Large Angle Magnetic Suspension Test Fixture (LAMSTF) and also the recommissioning of an additional piece of exisiting hardware. During the period in question, the initial configuration of LAMSTF was completed and made routinely and reliably operational. A digital phase advance controller was completed and documented. The goal of a controlled 360 deg rotation was achieved. Work started on the recommissioning of the Annular Suspension and Pointing System (ASPS). Work completed during the report period included: modeling; position sensing; controller; support of the Second International Symposium on Magnetic Suspension Technology; and recommissioning of the Annular Suspension and Pointing System.

  14. Reliability Testing on the CTI-Cryogenic 1 Watt Integral Cooler (HD- 1033C/UA)

    DTIC Science & Technology

    1989-09-01

    SUBJECT TERMS (Continue on reverse if necessary and identify by block numbe) FIELD GROUP SUB- GROUP Cryocooler, Stirling Cycle, Cryogenics 19, ABSTRCT...the Army. C2NVEO also maintains configuration management control of the forward-looking infrared (FLIR) Common Module coolers used in thermal imagers... controlled high/low temperature chamber. * A microprocessor which was programmed to automatically cycle the temperature in the chamber in accordance

  15. Team Software Process (TSP) Body of Knowledge (BOK)

    DTIC Science & Technology

    2010-07-01

    styles that correspond stereotypical extremes of group control and coordination, as shown in Figure 5. closed, random, open, and synchronous group ...and confirming the resolutions • managing the design change process and coordinating changes with the configuration control board • reporting...members. 123 | CMU/SEI-2010-TR-020 4. Coaching – Obtain a lead coach and the coaches for each team. 5. Conceptual design – Form a working group of

  16. Ground Data System Analysis Tools to Track Flight System State Parameters for the Mars Science Laboratory (MSL) and Beyond

    NASA Technical Reports Server (NTRS)

    Allard, Dan; Deforrest, Lloyd

    2014-01-01

    Flight software parameters enable space mission operators fine-tuned control over flight system configurations, enabling rapid and dynamic changes to ongoing science activities in a much more flexible manner than can be accomplished with (otherwise broadly used) configuration file based approaches. The Mars Science Laboratory (MSL), Curiosity, makes extensive use of parameters to support complex, daily activities via commanded changes to said parameters in memory. However, as the loss of Mars Global Surveyor (MGS) in 2006 demonstrated, flight system management by parameters brings with it risks, including the possibility of losing track of the flight system configuration and the threat of invalid command executions. To mitigate this risk a growing number of missions have funded efforts to implement parameter tracking parameter state software tools and services including MSL and the Soil Moisture Active Passive (SMAP) mission. This paper will discuss the engineering challenges and resulting software architecture of MSL's onboard parameter state tracking software and discuss the road forward to make parameter management tools suitable for use on multiple missions.

  17. Generic Airspace Concepts and Research

    NASA Technical Reports Server (NTRS)

    Mogford, Richard H.

    2010-01-01

    The purpose of this study was to evaluate methods for reducing the training and memorization required to manage air traffic in mid-term, Next Generation Air Transportation System (NextGen) airspace. We contrasted the performance of controllers using a sector information display and NextGen automation tools while working with familiar and unfamiliar sectors. The airspace included five sectors from Oakland and Salt Lake City Centers configured as a "generic center" called "West High Center." The Controller Information Tool was used to present essential information for managing these sectors. The Multi Aircraft Control System air traffic control simulator provided data link and conflict detection and resolution. There were five experienced air traffic controller participants. Each was familiar with one or two of the five sectors, but not the others. The participants rotated through all five sectors during the ten data collection runs. The results addressing workload, traffic management, and safety, as well as controller and observer comments, supported the generic sector concept. The unfamiliar sectors were comparable to the familiar sectors on all relevant measures.

  18. Space transportation booster engine configuration study. Volume 2: Design definition document and environmental analysis

    NASA Technical Reports Server (NTRS)

    1989-01-01

    The objective of the Space Transportation Booster Engine (STBE) Configuration Study is to contribute to the Advanced Launch System (ALS) development effort by providing highly reliable, low cost booster engine concepts for both expendable and reusable rocket engines. The objectives of the space Transportation Booster Engine (STBE) Configuration Study were: (1) to identify engine configurations which enhance vehicle performance and provide operational flexibility at low cost, and (2) to explore innovative approaches to the follow-on Full-Scale Development (FSD) phase for the STBE.

  19. Launch Vehicle Control Center Architectures

    NASA Technical Reports Server (NTRS)

    Watson, Michael D.; Epps, Amy; Woodruff, Van; Vachon, Michael Jacob; Monreal, Julio; Levesque, Marl; Williams, Randall; Mclaughlin, Tom

    2014-01-01

    Launch vehicles within the international community vary greatly in their configuration and processing. Each launch site has a unique processing flow based on the specific launch vehicle configuration. Launch and flight operations are managed through a set of control centers associated with each launch site. Each launch site has a control center for launch operations; however flight operations support varies from being co-located with the launch site to being shared with the space vehicle control center. There is also a nuance of some having an engineering support center which may be co-located with either the launch or flight control center, or in a separate geographical location altogether. A survey of control center architectures is presented for various launch vehicles including the NASA Space Launch System (SLS), United Launch Alliance (ULA) Atlas V and Delta IV, and the European Space Agency (ESA) Ariane 5. Each of these control center architectures shares some similarities in basic structure while differences in functional distribution also exist. The driving functions which lead to these factors are considered and a model of control center architectures is proposed which supports these commonalities and variations.

  20. 48 CFR 1816.405-274 - Award fee evaluation factors.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... factor, if used, must include consideration of risk management (including mission success, safety... above the contracting officer, with the concurrence of the project manager. The rationale for any waiver shall be documented in the contract file. When safety, export control, or security are considered under...

Top