Formal Verification of Complex Systems based on SysML Functional Requirements

DTIC Science & Technology

2014-12-23

Formal Verification of Complex Systems based on SysML Functional Requirements Hoda Mehrpouyan1, Irem Y. Tumer2, Chris Hoyle2, Dimitra Giannakopoulou3...requirements for design of complex engineered systems. The proposed ap- proach combines a SysML modeling approach to document and structure safety requirements...methods and tools to support the integration of safety into the design solution. 2.1. SysML for Complex Engineered Systems Traditional methods and tools

Navigating the Requirements Jungle

NASA Astrophysics Data System (ADS)

Langer, Boris; Tautschnig, Michael

Research on validation and verification of requirements specifications has thus far focused on functional properties. Yet, in embedded systems, functional requirements constitute only a small fraction of the properties that must hold to guarantee proper and safe operation of the system under design.

Increasing EHR system usability through standards: Conformance criteria in the HL7 EHR-system functional model.

PubMed

Meehan, Rebecca A; Mon, Donald T; Kelly, Kandace M; Rocca, Mitra; Dickinson, Gary; Ritter, John; Johnson, Constance M

2016-10-01

Though substantial work has been done on the usability of health information technology, improvements in electronic health record system (EHR) usability have been slow, creating frustration, distrust of EHRs and the use of potentially unsafe work-arounds. Usability standards could be part of the solution for improving EHR usability. EHR system functional requirements and standards have been used successfully in the past to specify system behavior, the criteria of which have been gradually implemented in EHR systems through certification programs and other national health IT strategies. Similarly, functional requirements and standards for usability can help address the multitude of sequelae associated with poor usability. This paper describes the evidence-based functional requirements for usability contained in the Health Level Seven (HL7) EHR System Functional Model, and the benefits of open and voluntary EHR system usability standards. Copyright © 2016 Elsevier Inc. All rights reserved.

Identification of emergent off-nominal operational requirements during conceptual architecting of the more electric aircraft

NASA Astrophysics Data System (ADS)

Armstrong, Michael James

Increases in power demands and changes in the design practices of overall equipment manufacturers has led to a new paradigm in vehicle systems definition. The development of unique power systems architectures is of increasing importance to overall platform feasibility and must be pursued early in the aircraft design process. Many vehicle systems architecture trades must be conducted concurrent to platform definition. With an increased complexity introduced during conceptual design, accurate predictions of unit level sizing requirements must be made. Architecture specific emergent requirements must be identified which arise due to the complex integrated effect of unit behaviors. Off-nominal operating scenarios present sizing critical requirements to the aircraft vehicle systems. These requirements are architecture specific and emergent. Standard heuristically defined failure mitigation is sufficient for sizing traditional and evolutionary architectures. However, architecture concepts which vary significantly in terms of structure and composition require that unique failure mitigation strategies be defined for accurate estimations of unit level requirements. Identifying of these off-nominal emergent operational requirements require extensions to traditional safety and reliability tools and the systematic identification of optimal performance degradation strategies. Discrete operational constraints posed by traditional Functional Hazard Assessment (FHA) are replaced by continuous relationships between function loss and operational hazard. These relationships pose the objective function for hazard minimization. Load shedding optimization is performed for all statistically significant failures by varying the allocation of functional capability throughout the vehicle systems architecture. Expressing hazards, and thereby, reliability requirements as continuous relationships with the magnitude and duration of functional failure requires augmentations to the traditional means for system safety assessment (SSA). The traditional two state and discrete system reliability assessment proves insufficient. Reliability is, therefore, handled in an analog fashion: as a function of magnitude of failure and failure duration. A series of metrics are introduced which characterize system performance in terms of analog hazard probabilities. These include analog and cumulative system and functional risk, hazard correlation, and extensions to the traditional component importance metrics. Continuous FHA, load shedding optimization, and analog SSA constitute the SONOMA process (Systematic Off-Nominal Requirements Analysis). Analog system safety metrics inform both architecture optimization (changes in unit level capability and reliability) and architecture augmentation (changes in architecture structure and composition). This process was applied for two vehicle systems concepts (conventional and 'more-electric') in terms of loss/hazard relationships with varying degrees of fidelity. Application of this process shows that the traditional assumptions regarding the structure of the function loss vs. hazard relationship apply undue design bias to functions and components during exploratory design. This bias is illustrated in terms of inaccurate estimations of the system and function level risk and unit level importance. It was also shown that off-nominal emergent requirements must be defined specific to each architecture concept. Quantitative comparisons of architecture specific off-nominal performance were obtained which provide evidence to the need for accurate definition of load shedding strategies during architecture exploratory design. Formally expressing performance degradation strategies in terms of the minimization of a continuous hazard space enhances the system architects ability to accurately predict sizing critical emergent requirements concurrent to architecture definition. Furthermore, the methods and frameworks generated here provide a structured and flexible means for eliciting these architecture specific requirements during the performance of architecture trades.

Operational characterisation of requirements and early validation environment for high demanding space systems

NASA Technical Reports Server (NTRS)

Barro, E.; Delbufalo, A.; Rossi, F.

1993-01-01

The definition of some modern high demanding space systems requires a different approach to system definition and design from that adopted for traditional missions. System functionality is strongly coupled to the operational analysis, aimed at characterizing the dynamic interactions of the flight element with its surrounding environment and its ground control segment. Unambiguous functional, operational and performance requirements are to be defined for the system, thus improving also the successive development stages. This paper proposes a Petri Nets based methodology and two related prototype applications (to ARISTOTELES orbit control and to Hermes telemetry generation) for the operational analysis of space systems through the dynamic modeling of their functions and a related computer aided environment (ISIDE) able to make the dynamic model work, thus enabling an early validation of the system functional representation, and to provide a structured system requirements data base, which is the shared knowledge base interconnecting static and dynamic applications, fully traceable with the models and interfaceable with the external world.

Freight advanced traveler information system : functional requirements.

DOT National Transportation Integrated Search

2012-08-01

This report describes the System Requirement Specifications (SyRS) for a Freight Advanced Traveler Information System (FRATIS). The SyRS is based on user needs described in the FRATIS Concept of Operations (ConOps), which cover the essential function...

Software Dependability and Safety Evaluations ESA's Initiative

NASA Astrophysics Data System (ADS)

Hernek, M.

ESA has allocated funds for an initiative to evaluate Dependability and Safety methods of Software. The objectives of this initiative are; · More extensive validation of Safety and Dependability techniques for Software · Provide valuable results to improve the quality of the Software thus promoting the application of Dependability and Safety methods and techniques. ESA space systems are being developed according to defined PA requirement specifications. These requirements may be implemented through various design concepts, e.g. redundancy, diversity etc. varying from project to project. Analysis methods (FMECA. FTA, HA, etc) are frequently used during requirements analysis and design activities to assure the correct implementation of system PA requirements. The criticality level of failures, functions and systems is determined and by doing that the critical sub-systems are identified, on which dependability and safety techniques are to be applied during development. Proper performance of the software development requires the development of a technical specification for the products at the beginning of the life cycle. Such technical specification comprises both functional and non-functional requirements. These non-functional requirements address characteristics of the product such as quality, dependability, safety and maintainability. Software in space systems is more and more used in critical functions. Also the trend towards more frequent use of COTS and reusable components pose new difficulties in terms of assuring reliable and safe systems. Because of this, its dependability and safety must be carefully analysed. ESA identified and documented techniques, methods and procedures to ensure that software dependability and safety requirements are specified and taken into account during the design and development of a software system and to verify/validate that the implemented software systems comply with these requirements [R1].

Automated Synthesis of Architecture of Avionic Systems

NASA Technical Reports Server (NTRS)

Chau, Savio; Xu, Joseph; Dang, Van; Lu, James F.

2006-01-01

The Architecture Synthesis Tool (AST) is software that automatically synthesizes software and hardware architectures of avionic systems. The AST is expected to be most helpful during initial formulation of an avionic-system design, when system requirements change frequently and manual modification of architecture is time-consuming and susceptible to error. The AST comprises two parts: (1) an architecture generator, which utilizes a genetic algorithm to create a multitude of architectures; and (2) a functionality evaluator, which analyzes the architectures for viability, rejecting most of the non-viable ones. The functionality evaluator generates and uses a viability tree a hierarchy representing functions and components that perform the functions such that the system as a whole performs system-level functions representing the requirements for the system as specified by a user. Architectures that survive the functionality evaluator are further evaluated by the selection process of the genetic algorithm. Architectures found to be most promising to satisfy the user s requirements and to perform optimally are selected as parents to the next generation of architectures. The foregoing process is iterated as many times as the user desires. The final output is one or a few viable architectures that satisfy the user s requirements.

Functional requirements of computer systems for the U.S. Geological Survey, Water Resources Division, 1988-97

USGS Publications Warehouse

Hathaway, R.M.; McNellis, J.M.

1989-01-01

Investigating the occurrence, quantity, quality, distribution, and movement of the Nation 's water resources is the principal mission of the U.S. Geological Survey 's Water Resources Division. Reports of these investigations are published and available to the public. To accomplish this mission, the Division requires substantial computer technology to process, store, and analyze data from more than 57,000 hydrologic sites. The Division 's computer resources are organized through the Distributed Information System Program Office that manages the nationwide network of computers. The contract that provides the major computer components for the Water Resources Division 's Distributed information System expires in 1991. Five work groups were organized to collect the information needed to procure a new generation of computer systems for the U. S. Geological Survey, Water Resources Division. Each group was assigned a major Division activity and asked to describe its functional requirements of computer systems for the next decade. The work groups and major activities are: (1) hydrologic information; (2) hydrologic applications; (3) geographic information systems; (4) reports and electronic publishing; and (5) administrative. The work groups identified 42 functions and described their functional requirements for 1988, 1992, and 1997. A few new functions such as Decision Support Systems and Executive Information Systems, were identified, but most are the same as performed today. Although the number of functions will remain about the same, steady growth in the size, complexity, and frequency of many functions is predicted for the next decade. No compensating increase in the Division 's staff is anticipated during this period. To handle the increased workload and perform these functions, new approaches will be developed that use advanced computer technology. The advanced technology is required in a unified, tightly coupled system that will support all functions simultaneously. The new approaches and expanded use of computers will require substantial increases in the quantity and sophistication of the Division 's computer resources. The requirements presented in this report will be used to develop technical specifications that describe the computer resources needed during the 1990's. (USGS)

An aspect-oriented approach for designing safety-critical systems

NASA Astrophysics Data System (ADS)

Petrov, Z.; Zaykov, P. G.; Cardoso, J. P.; Coutinho, J. G. F.; Diniz, P. C.; Luk, W.

The development of avionics systems is typically a tedious and cumbersome process. In addition to the required functions, developers must consider various and often conflicting non-functional requirements such as safety, performance, and energy efficiency. Certainly, an integrated approach with a seamless design flow that is capable of requirements modelling and supporting refinement down to an actual implementation in a traceable way, may lead to a significant acceleration of development cycles. This paper presents an aspect-oriented approach supported by a tool chain that deals with functional and non-functional requirements in an integrated manner. It also discusses how the approach can be applied to development of safety-critical systems and provides experimental results.

Functional Design of an Automated Instructional Support System for Operational Flight Trainers. Final Report, June 1976 through September 1977.

ERIC Educational Resources Information Center

Semple, Clarence A.; And Others

Functional requirements for a highly automated, flexible, instructional support system for aircrew training simulators are presented. Automated support modes and associated features and capabilities are described, along with hardware and software functional requirements for implementing a baseline system in an operational flight training context.…

Systems Operation Studies for Automated Guideway Transit Systems: Feeder Systems Model Functional Specification

DOT National Transportation Integrated Search

1981-01-01

This document specifies the functional requirements for the AGT-SOS Feeder Systems Model (FSM), the type of hardware required, and the modeling techniques employed by the FSM. The objective of the FSM is to map the zone-to-zone transit patronage dema...

High performance VLSI telemetry data systems

NASA Technical Reports Server (NTRS)

Chesney, J.; Speciale, N.; Horner, W.; Sabia, S.

1990-01-01

NASA's deployment of major space complexes such as Space Station Freedom (SSF) and the Earth Observing System (EOS) will demand increased functionality and performance from ground based telemetry acquisition systems well above current system capabilities. Adaptation of space telemetry data transport and processing standards such as those specified by the Consultative Committee for Space Data Systems (CCSDS) standards and those required for commercial ground distribution of telemetry data, will drive these functional and performance requirements. In addition, budget limitations will force the requirement for higher modularity, flexibility, and interchangeability at lower cost in new ground telemetry data system elements. At NASA's Goddard Space Flight Center (GSFC), the design and development of generic ground telemetry data system elements, over the last five years, has resulted in significant solutions to these problems. This solution, referred to as the functional components approach includes both hardware and software components ready for end user application. The hardware functional components consist of modern data flow architectures utilizing Application Specific Integrated Circuits (ASIC's) developed specifically to support NASA's telemetry data systems needs and designed to meet a range of data rate requirements up to 300 Mbps. Real-time operating system software components support both embedded local software intelligence, and overall system control, status, processing, and interface requirements. These components, hardware and software, form the superstructure upon which project specific elements are added to complete a telemetry ground data system installation. This paper describes the functional components approach, some specific component examples, and a project example of the evolution from VLSI component, to basic board level functional component, to integrated telemetry data system.

TERSSE: Definition of the Total Earth Resources System for the Shuttle Era. Volume 5: Detailed system requirements: Two case studies

NASA Technical Reports Server (NTRS)

1974-01-01

Major resource management missions to be performed by the TERSSE are examined in order to develop an understanding of the form and function of a system designed to perform an operational mission. Factors discussed include: resource manager (user) functions, methods of performing their function, the information flows and information requirements embodied in their function, and the characteristics of the observation system which assists in the management of the resource involved. The missions selected for study are: world crop survey and land resources management. These missions are found to represent opposite ends of the TERSSE spectrum and to support the conclusion that different missions require different systems and must be analyzed in detail to permit proper system development decisions.

Performance monitor system functional simulator, environmental data, orbiter 101(HFT)

NASA Technical Reports Server (NTRS)

Parker, F. W.

1974-01-01

Information concerning the environment component of the space shuttle performance monitor system simulator (PMSS) and those subsystems operational on the shuttle orbiter 101 used for horizontal flight test (HFT) is provided, along with detailed data for the shuttle performance monitor system (PMS) whose software requirements evolve from three basic PMS functions: (1) fault detection and annunciation; (2) subsystem measurement management; and (3) subsystem configuration management. Information relative to the design and operation of Orbiter systems for HFT is also presented, and the functional paths are identified to the lowest level at which the crew can control the system functions. Measurement requirements are given which are necessary to adequately monitor the health status of the system. PMS process requirements, relative to the measurements which are necessary for fault detection and annunciation of a failed functional path, consist of measurement characteristics, tolerance limits, precondition tests, and correlation measurements.

Non-functional Avionics Requirements

NASA Astrophysics Data System (ADS)

Paulitsch, Michael; Ruess, Harald; Sorea, Maria

Embedded systems in aerospace become more and more integrated in order to reduce weight, volume/size, and power of hardware for more fuel-effi ciency. Such integration tendencies change architectural approaches of system ar chi tec tures, which subsequently change non-functional requirements for plat forms. This paper provides some insight into state-of-the-practice of non-func tional requirements for developing ultra-critical embedded systems in the aero space industry, including recent changes and trends. In particular, formal requi re ment capture and formal analysis of non-functional requirements of avionic systems - including hard-real time, fault-tolerance, reliability, and per for mance - are exemplified by means of recent developments in SAL and HiLiTE.

Autonomous Integrated Receive System (AIRS) requirements definition. Volume 4: Functional specification for the prototype Automated Integrated Receive System (AIRS)

NASA Technical Reports Server (NTRS)

Chie, C. M.

1984-01-01

The functional requirements for the performance, design, and testing for the prototype Automated Integrated Receive System (AIRS) to be demonstrated for the TDRSS S-Band Single Access Return Link are presented.

Development of the Functional Flow Block Diagram for the J-2X Rocket Engine System

NASA Technical Reports Server (NTRS)

White, Thomas; Stoller, Sandra L.; Greene, WIlliam D.; Christenson, Rick L.; Bowen, Barry C.

2007-01-01

The J-2X program calls for the upgrade of the Apollo-era Rocketdyne J-2 engine to higher power levels, using new materials and manufacturing techniques, and with more restrictive safety and reliability requirements than prior human-rated engines in NASA history. Such requirements demand a comprehensive systems engineering effort to ensure success. Pratt & Whitney Rocketdyne system engineers performed a functional analysis of the engine to establish the functional architecture. J-2X functions were captured in six major operational blocks. Each block was divided into sub-blocks or states. In each sub-block, functions necessary to perform each state were determined. A functional engine schematic consistent with the fidelity of the system model was defined for this analysis. The blocks, sub-blocks, and functions were sequentially numbered to differentiate the states in which the function were performed and to indicate the sequence of events. The Engine System was functionally partitioned, to provide separate and unique functional operators. Establishing unique functional operators as work output of the System Architecture process is novel in Liquid Propulsion Engine design. Each functional operator was described such that its unique functionality was identified. The decomposed functions were then allocated to the functional operators both of which were the inputs to the subsystem or component performance specifications. PWR also used a novel approach to identify and map the engine functional requirements to customer-specified functions. The final result was a comprehensive Functional Flow Block Diagram (FFBD) for the J-2X Engine System, decomposed to the component level and mapped to all functional requirements. This FFBD greatly facilitates component specification development, providing a well-defined trade space for functional trades at the subsystem and component level. It also provides a framework for function-based failure modes and effects analysis (FMEA), and a rigorous baseline for the functional architecture.

[Definition and specification requirements for PAC-systems (picture archiving and communication system). A performance index with reference to the standard "IEEE Recommended Practice for Software Requirement Specifications"].

PubMed

König, H; Klose, K J

1999-04-01

The formulation of requirements is necessary to control the goals of a PACS project. Furthermore, in this way, the scope of functionality necessary to support radiological working processes becomes clear. Definitions of requirements and specification are formulated independently of systems according to the IEEE standard "Recommended Practice for Software Requirements Specifications". Definitions are given in the Request for Information, specifications in the Request for Proposal. Functional and non-functional requirements are distinguished. The solutions are rated with respect to scope, appropriateness and quality of implementation. A PACS checklist was created according to the methods described above. It is published on the homepage of the "Arbeitsgemeinschaft Informationstechnologie" (AGIT) within the "Deutsche Röntgengesellschaft" (DRG) (http://www.uni-marburg.de/mzr/agit). The checklist provides a discussion forum which should contribute to an agreement on accepted basic PACS functionalities.

47 CFR 80.1081 - Functional requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 5 2010-10-01 2010-10-01 false Functional requirements. 80.1081 Section 80... STATIONS IN THE MARITIME SERVICES Global Maritime Distress and Safety System (GMDSS) Equipment Requirements for Ship Stations § 80.1081 Functional requirements. Ships, while at sea, must be capable: (a) Except...

NASA TSRV essential flight control system requirements via object oriented analysis

NASA Technical Reports Server (NTRS)

Duffy, Keith S.; Hoza, Bradley J.

1992-01-01

The objective was to analyze the baseline flight control system of the Transport Systems Research Vehicle (TSRV) and to develop a system specification that offers high visibility of the essential system requirements in order to facilitate the future development of alternate, more advanced software architectures. The flight control system is defined to be the baseline software for the TSRV research flight deck, including all navigation, guidance, and control functions, and primary pilot displays. The Object Oriented Analysis (OOA) methodology developed is used to develop a system requirement definition. The scope of the requirements definition contained herein is limited to a portion of the Flight Management/Flight Control computer functionality. The development of a partial system requirements definition is documented, and includes a discussion of the tasks required to increase the scope of the requirements definition and recommendations for follow-on research.

Human Systems Integration: Requirements and Functional Decomposition

NASA Technical Reports Server (NTRS)

Berson, Barry; Gershzohn, Gary; Boltz, Laura; Wolf, Russ; Schultz, Mike

2005-01-01

This deliverable was intended as an input to the Access 5 Policy and Simulation Integrated Product Teams. This document contains high-level pilot functionality for operations in the National Airspace System above FL430. Based on the derived pilot functions the associated pilot information and control requirements are given.

Functional Requirements Study

DTIC Science & Technology

2008-07-01

Identification System, AIS, Vessel Traffic Services, VTS, Transmit, Broadcast, Functional Requirements, United States Coast Guard, USCG, Mariner, Electronic ...Chart Systems, ECS, Vessel Operators, National Oceanic Atmospheric Administration, NOAA, US Army Corp of Engineers , USACE, ECDIS 18. Distribution...and River Information Service COPT Captain of the Port DGPS Differential Global Positioning System ECDIS Electronic Chart Display Information System

Identification of high-level functional/system requirements for future civil transports

NASA Technical Reports Server (NTRS)

Swink, Jay R.; Goins, Richard T.

1992-01-01

In order to accommodate the rapid growth in commercial aviation throughout the remainder of this century, the Federal Aviation Administration (FAA) is faced with a formidable challenge to upgrade and/or modernize the National Airspace System (NAS) without compromising safety or efficiency. A recurring theme in both the Aviation System Capital Investment Plan (CIP), which has replaced the NAS Plan, and the new FAA Plan for Research, Engineering, and Development (RE&D) rely on the application of new technologies and a greater use of automation. Identifying the high-level functional and system impacts of such modernization efforts on future civil transport operational requirements, particularly in terms of cockpit functionality and information transfer, was the primary objective of this project. The FAA planning documents for the NAS of the 2005 era and beyond were surveyed; major aircraft functional capabilities and system components required for such an operating environment were identified. A hierarchical structured analysis of the information processing and flows emanating from such functional/system components were conducted and the results documented in graphical form depicting the relationships between functions and systems.

Advanced information processing system: Input/output system services

NASA Technical Reports Server (NTRS)

Masotto, Tom; Alger, Linda

1989-01-01

The functional requirements and detailed specifications for the Input/Output (I/O) Systems Services of the Advanced Information Processing System (AIPS) are discussed. The introductory section is provided to outline the overall architecture and functional requirements of the AIPS system. Section 1.1 gives a brief overview of the AIPS architecture as well as a detailed description of the AIPS fault tolerant network architecture, while section 1.2 provides an introduction to the AIPS systems software. Sections 2 and 3 describe the functional requirements and design and detailed specifications of the I/O User Interface and Communications Management modules of the I/O System Services, respectively. Section 4 illustrates the use of the I/O System Services, while Section 5 concludes with a summary of results and suggestions for future work in this area.

Use of software tools in the development of real time software systems

NASA Technical Reports Server (NTRS)

Garvey, R. C.

1981-01-01

The transformation of a preexisting software system into a larger and more versatile system with different mission requirements is discussed. The history of this transformation is used to illustrate the use of structured real time programming techniques and tools to produce maintainable and somewhat transportable systems. The predecessor system is a single ground diagnostic system; its purpose is to exercise a computer controlled hardware set prior to its deployment in its functional environment, as well as test the equipment set by supplying certain well known stimulas. The successor system (FTE) is required to perform certain testing and control functions while this hardware set is in its functional environment. Both systems must deal with heavy user input/output loads and a new I/O requirement is included in the design of the FTF system. Human factors are enhanced by adding an improved console interface and special function keyboard handler. The additional features require the inclusion of much new software to the original set from which FTF was developed. As a result, it is necessary to split the system into a duel programming configuration with high rates of interground communications. A generalized information routing mechanism is used to support this configuration.

Trade Spaces in Crewed Spacecraft Atmosphere Revitalization System Development

NASA Technical Reports Server (NTRS)

Perry, Jay L.; Bagdigian, Robert M.; Carrasquillo, Robyn L.

2010-01-01

Developing the technological response to realizing an efficient atmosphere revitalization system for future crewed spacecraft and space habitats requires identifying and describing functional trade spaces. Mission concepts and requirements dictate the necessary functions; however, the combination and sequence of those functions possess significant flexibility. Us-ing a closed loop environmental control and life support (ECLS) system architecture as a starting basis, a functional unit operations approach is developed to identify trade spaces. Generalized technological responses to each trade space are discussed. Key performance parameters that apply to functional areas are described.

Detailed requirements document for the integrated structural analysis system, phase B

NASA Technical Reports Server (NTRS)

Rainey, J. A.

1976-01-01

The requirements are defined for a software system entitled integrated Structural Analysis System (ISAS) Phase B which is being developed to provide the user with a tool by which a complete and detailed analysis of a complex structural system can be performed. This software system will allow for automated interface with numerous structural analysis batch programs and for user interaction in the creation, selection, and validation of data. This system will include modifications to the 4 functions developed for ISAS, and the development of 25 new functions. The new functions are described.

The Integrated Mission-Planning Station: Functional Requirements, Aviator-Computer Dialogue, and Human Engineering Design Criteria.

DTIC Science & Technology

1983-08-01

AD- R136 99 THE INTEGRATED MISSION-PLNNING STATION: FUNCTIONAL 1/3 REQUIREMENTS AVIATOR-..(U) RNACAPR SCIENCES INC SANTA BARBARA CA S P ROGERS RUG...Continue on reverse side o necess.ar and identify by btock number) Interactive Systems Aviation Control-Display Functional Require- Plan-Computer...Dialogue Avionics Systems ments Map Display Army Aviation Design Criteria Helicopters M4ission Planning Cartography Digital Map Human Factors Navigation

Functional Requirements for an Electronic Work Package System

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

Oxstrand, Johanna H.

This document provides a set of high level functional requirements for a generic electronic work package (eWP) system. The requirements have been identified by the U.S. nuclear industry as a part of the Nuclear Electronic Work Packages - Enterprise Requirements (NEWPER) initiative. The functional requirements are mainly applied to eWP system supporting Basic and Moderate types of smart documents, i.e., documents that have fields for recording input such as text, dates, numbers, and equipment status, and documents which incorporate additional functionalities such as form field data “type“ validation (e.g. date, text, number, and signature) of data entered and/or self-populate basicmore » document information (usually from existing host application meta data) on the form when the user first opens it. All the requirements are categorized by the roles; Planner, Supervisor, Craft, Work Package Approval Reviewer, Operations, Scheduling/Work Control, and Supporting Functions. The categories Statistics, Records, Information Technology are also included used to group the requirements. All requirements are presented in Section 2 through Section 11. Examples of more detailed requirements are provided for the majority of high level requirements. These examples are meant as an inspiration to be used as each utility goes through the process of identifying their specific requirements. The report’s table of contents provides a summary of the high level requirements.« less

Engineering study for the functional design of a multiprocessor system

NASA Technical Reports Server (NTRS)

Miller, J. S.; Vandever, W. H.; Stanten, S. F.; Avakian, A. E.; Kosmala, A. L.

1972-01-01

The results are presented of a study to generate a functional system design of a multiprocessing computer system capable of satisfying the computational requirements of a space station. These data management system requirements were specified to include: (1) real time control, (2) data processing and storage, (3) data retrieval, and (4) remote terminal servicing.

Functional Requirements Document for HALE UAS Operations in the NAS: Step 1. Version 3

NASA Technical Reports Server (NTRS)

2006-01-01

The purpose of this Functional Requirements Document (FRD) is to compile the functional requirements needed to achieve the Access 5 Vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the national airspace system (NAS)" for Step 1. These functional requirements could support the development of a minimum set of policies, procedures and standards by the Federal Aviation Administration (FAA) and various standards organizations. It is envisioned that this comprehensive body of work will enable the FAA to establish and approve regulations to govern safe operation of UAS in the NAS on a routine or daily "file and fly" basis. The approach used to derive the functional requirements found within this FRD was to decompose the operational requirements and objectives identified within the Access 5 Concept of Operations (CONOPS) into the functions needed to routinely and safely operate a HALE UAS in the NAS. As a result, four major functional areas evolved to enable routine and safe UAS operations for an on-demand basis in the NAS. These four major functions are: Aviate, Navigate, Communicate, and Avoid Hazards. All of the functional requirements within this document can be directly traceable to one of these four major functions. Some functions, however, are traceable to several, or even all, of these four major functions. These cross-cutting functional requirements support the "Command / Control: function as well as the "Manage Contingencies" function. The requirements associated to these high-level functions and all of their supporting low-level functions are addressed in subsequent sections of this document.

Using a Functional Architecture to Identify Human-Automation Trust Needs and Design Requirements

DTIC Science & Technology

2016-12-01

FUNCTIONAL ARCHITECTURE TO IDENTIFY HUMAN-AUTOMATION TRUST NEEDS AND DESIGN REQUIREMENTS by Bradley A. Johnson December 2016 Thesis Advisor...maximum 200 words) This thesis develops and analyzes the functional architecture for an “autonomous” unmanned aerial system performing an...INTENTIONALLY LEFT BLANK v ABSTRACT This thesis develops and analyzes the functional architecture for an “autonomous” unmanned aerial system

The Global Emergency Observation and Warning System

NASA Technical Reports Server (NTRS)

Bukley, Angelia P.; Mulqueen, John A.

1994-01-01

Based on an extensive characterization of natural hazards, and an evaluation of their impacts on humanity, a set of functional technical requirements for a global warning and relief system was developed. Since no technological breakthroughs are required to implement a global system capable of performing the functions required to provide sufficient information for prevention, preparedness, warning, and relief from natural disaster effects, a system is proposed which would combine the elements of remote sensing, data processing, information distribution, and communications support on a global scale for disaster mitigation.

The architecture of the High Performance Storage System (HPSS)

NASA Technical Reports Server (NTRS)

Teaff, Danny; Watson, Dick; Coyne, Bob

1994-01-01

The rapid growth in the size of datasets has caused a serious imbalance in I/O and storage system performance and functionality relative to application requirements and the capabilities of other system components. The High Performance Storage System (HPSS) is a scalable, next-generation storage system that will meet the functionality and performance requirements or large-scale scientific and commercial computing environments. Our goal is to improve the performance and capacity of storage by two orders of magnitude or more over what is available in the general or mass marketplace today. We are also providing corresponding improvements in architecture and functionality. This paper describes the architecture and functionality of HPSS.

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

The functional requirements to be met by the HAL/S-FC compiler, and the hardware and software compatibilities between the compiler system and the environment in which it operates are defined. Associated runtime facilities and the interface with the Software Development Laboratory are specified. The construction of the HAL/S-FC system as functionally separate units and the interfaces between those units is described. An overview of the system's capabilities is presented and the hardware/operating system requirements are specified. The computer-dependent aspects of the HAL/S-FC are also specified. Compiler directives are included.

Candidate Mission from Planet Earth control and data delivery system architecture

NASA Technical Reports Server (NTRS)

Shapiro, Phillip; Weinstein, Frank C.; Hei, Donald J., Jr.; Todd, Jacqueline

1992-01-01

Using a structured, experienced-based approach, Goddard Space Flight Center (GSFC) has assessed the generic functional requirements for a lunar mission control and data delivery (CDD) system. This analysis was based on lunar mission requirements outlined in GSFC-developed user traffic models. The CDD system will facilitate data transportation among user elements, element operations, and user teams by providing functions such as data management, fault isolation, fault correction, and link acquisition. The CDD system for the lunar missions must not only satisfy lunar requirements but also facilitate and provide early development of data system technologies for Mars. Reuse and evolution of existing data systems can help to maximize system reliability and minimize cost. This paper presents a set of existing and currently planned NASA data systems that provide the basic functionality. Reuse of such systems can have an impact on mission design and significantly reduce CDD and other system development costs.

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

NASA Technical Reports Server (NTRS)

2005-01-01

The document provides the Human System Integration(HSI) high-level functional C3 HSI requirements for the interface to the pilot. Description includes (1) the information required by the pilot to have knowledge C3 system status, and (2) the control capability needed by the pilot to obtain C3 information. Fundamentally, these requirements provide the candidate C3 technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how C3 operations and functions should interface with the pilot to provide the necessary C3 functionality to the UA-pilot system. Requirements and guidelines for C3 are partitioned into three categories: (1) Pilot-Air Traffic Control (ATC) Voice Communications (2) Pilot-ATC Data Communications, and (3) command and control of the unmanned aircraft (UA). Each requirement is stated and is supported with a rationale and associated reference(s).

Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

NASA Technical Reports Server (NTRS)

Liebowitz, J.

1986-01-01

The development of an expert system prototype for software functional requirement determination for NASA Goddard's Command Management System, as part of its process of transforming general requests into specific near-earth satellite commands, is described. The present knowledge base was formulated through interactions with domain experts, and was then linked to the existing Knowledge Engineering Systems (KES) expert system application generator. Steps in the knowledge-base development include problem-oriented attribute hierarchy development, knowledge management approach determination, and knowledge base encoding. The KES Parser and Inspector, in addition to backcasting and analogical mapping, were used to validate the expert system-derived requirements for one of the major functions of a spacecraft, the solar Maximum Mission. Knowledge refinement, evaluation, and implementation procedures of the expert system were then accomplished.

Space Tug avionics definition study. Volume 2: Avionics functional requirements

NASA Technical Reports Server (NTRS)

1975-01-01

Flight and ground operational phases of the tug/shuttle system are analyzed to determine the general avionics support functions that are needed during each of the mission phases and sub-phases. Each of these general support functions is then expanded into specific avionics system requirements, which are then allocated to the appropriate avionics subsystems. This process is then repeated at the next lower level of detail where these subsystem requirements are allocated to each of the major components that comprise a subsystem.

Functional requirements for design of the Space Ultrareliable Modular Computer (SUMC) system simulator

NASA Technical Reports Server (NTRS)

Curran, R. T.; Hornfeck, W. A.

1972-01-01

The functional requirements for the design of an interpretive simulator for the space ultrareliable modular computer (SUMC) are presented. A review of applicable existing computer simulations is included along with constraints on the SUMC simulator functional design. Input requirements, output requirements, and language requirements for the simulator are discussed in terms of a SUMC configuration which may vary according to the application.

Modeling traceability information and functionality requirement in export-oriented tilapia chain.

PubMed

Zhang, Xiaoshuan; Feng, Jianying; Xu, Mark; Hu, Jinyou

2011-05-01

Tilapia has been named as the 'food fish of the 21st century' and has become the most important farmed fish. China is the world leader in tilapia production and export. Identifying information and functional requirements is critical in developing an efficient traceability system because traceability has become a fundamental prerequisite for exporting aquaculture products. This paper examines the export-oriented tilapia chains and information flow in the chains, and identifies the key actors, information requirements and information-capturing points. Unified Modeling Language (UML) technology is adopted to describe the information and functionality requirement for chain traceability. The barriers of traceability system adoption are also identified. The results show that the traceability data consist of four categories that must be recorded by each link in the chain. The functionality requirement is classified into four categories from the fundamental information record to decisive quality control; the top three barriers to the traceability system adoption are: high costs of implementing the system, lack of experienced and professional staff; and low level of government involvement and support. Copyright © 2011 Society of Chemical Industry.

A Study on the Deriving Requirements of ARGO Operation System

NASA Astrophysics Data System (ADS)

Seo, Yoon-Kyung; Rew, Dong-Young; Lim, Hyung-Chul; Park, In-Kwan; Yim, Hong-Suh; Jo, Jung Hyun; Park, Jong-Uk

2009-12-01

Korea Astronomy and Space Science Institute (KASI) has been developing one mobile and one stationary SLR system since 2008 named as ARGO-M and ARGO-F, respectively. KASI finished the step of deriving the system requirements of ARGO. The requirements include definitions and scopes of various software and hardware components which are necessary for developing the ARGO-M operation system. And the requirements define function, performance, and interface requirements. The operation system consisting of ARGO-M site, ARGO-F site, and Remote Operation Center (ROC) inside KASI is designed for remote access and the automatic tracking and control system which are the main operation concept of ARGO system. To accomplish remote operation, we are considering remote access to ARGO-F and ARGO-M from ROC. The mobile-phone service allows us to access the ARGO-F remotely and to control the system in an emergency. To implement fully automatic tracking and control function in ARGO-F, we have investigated and described the requirements about the automatic aircraft detection system and the various meteorological sensors. This paper addresses the requirements of ARGO Operation System.

System requirements for a computerised patient record information system at a busy primary health care clinic.

PubMed

Blignaut, P J; McDonald, T; Tolmie, C J

2001-05-01

A prototyping approach was used to determine the essential system requirements of a computerised patient record information system for a typical township primary health care clinic. A pilot clinic was identified and the existing manual system and business processes in this clinic was studied intensively before the first prototype was implemented. Interviews with users, incidental observations and analysis of actual data entered were used as primary techniques to refine the prototype system iteratively until a system with an acceptable data set and adequate functionalities were in place. Several non-functional and user-related requirements were also discovered during the prototyping period.

Transit bus stop pedestrian warning application : requirements document.

DOT National Transportation Integrated Search

2016-08-01

This document describes the System Requirements for the Transit Bus Stop Pedestrian Warning (TSPW) application. The requirements describe the system of interest for the implementation team including the required functions and performance along with t...

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

NASA Technical Reports Server (NTRS)

2005-01-01

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

Light duty utility arm phase 2 qualification test procedure

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

Barnes, G.A.

1997-01-16

This Acceptance Test Procedure (ATP) will test and verify that the Exhauster meets the specified functional requirements, safety requirements, operating requirements, and provide a record of the functional test results. The system/functions that will be tested are listed in the scope section of the Acceptance Test Procedure.

MSFC Skylab instrumentation and communication system mission evaluation

NASA Technical Reports Server (NTRS)

Adair, B. M.

1974-01-01

An evaluation of the in-orbit performance of the instrumentation and communications systems installed on Skylab is presented. Performance is compared with functional requirements and the fidelity of communications. In-orbit performance includes processing engineering, scientific, experiment, and biomedical data, implementing ground-generated commands, audio and video communication, generating rendezvous ranging information, and radio frequency transmission and reception. A history of the system evolution based on the functional requirements and a physical description of the launch configuration is included. The report affirms that the instrumentation and communication system satisfied all imposed requirements.

AN ULTRAVIOLET-VISIBLE SPECTROPHOTOMETER AUTOMATION SYSTEM. PART I: FUNCTIONAL SPECIFICATIONS

EPA Science Inventory

This document contains the project definition, the functional requirements, and the functional design for a proposed computer automation system for scanning spectrophotometers. The system will be implemented on a Data General computer using the BASIC language. The system is a rea...

Monitoring and control requirement definition study for Dispersed Storage and Generation (DSG), volume 1

NASA Technical Reports Server (NTRS)

1980-01-01

Twenty-four functional requirements were prepared under six categories and serve to indicate how to integrate dispersed storage generation (DSG) systems with the distribution and other portions of the electric utility system. Results indicate that there are no fundamental technical obstacles to prevent the connection of dispersed storage and generation to the distribution system. However, a communication system of some sophistication is required to integrate the distribution system and the dispersed generation sources for effective control. The large-size span of generators from 10 KW to 30 MW means that a variety of remote monitoring and control may be required. Increased effort is required to develop demonstration equipment to perform the DSG monitoring and control functions and to acquire experience with this equipment in the utility distribution environment.

I-15 integrated corridor management : system requirements.

DOT National Transportation Integrated Search

2011-07-01

This document is intended as a listing and discussion of the Requirements for the I-15 Integrated Corridor Management System (ICMS) Demonstration Project in San Diego. This document describes what the system is to do (the functional requirements), ho...

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.

Defense Logistics Standard Systems Functional Requirements.

DTIC Science & Technology

1987-03-01

Artificial Intelligence - the development of a machine capability to perform functions normally concerned with human intelligence, such as learning , adapting...Basic Data Base Machine Configurations .... ......... D- 18 xx ~ ?f~~~vX PART I: MODELS - DEFENSE LOGISTICS STANDARD SYSTEMS FUNCTIONAL REQUIREMENTS...On-line, Interactive Access. Integrating user input and machine output in a dynamic, real-time, give-and- take process is considered the optimum mode

ISO 9000 and/or Systems Engineering Capability Maturity Model?

NASA Technical Reports Server (NTRS)

Gholston, Sampson E.

2002-01-01

For businesses and organizations to remain competitive today they must have processes and systems in place that will allow them to first identify customer needs and then develop products/processes that will meet or exceed the customers needs and expectations. Customer needs, once identified, are normally stated as requirements. Designers can then develop products/processes that will meet these requirements. Several functions, such as quality management and systems engineering management are used to assist product development teams in the development process. Both functions exist in all organizations and both have a similar objective, which is to ensure that developed processes will meet customer requirements. Are efforts in these organizations being duplicated? Are both functions needed by organizations? What are the similarities and differences between the functions listed above? ISO 9000 is an international standard of goods and services. It sets broad requirements for the assurance of quality and for management's involvement. It requires organizations to document the processes and to follow these documented processes. ISO 9000 gives customers assurance that the suppliers have control of the process for product development. Systems engineering can broadly be defined as a discipline that seeks to ensure that all requirements for a system are satisfied throughout the life of the system by preserving their interrelationship. The key activities of systems engineering include requirements analysis, functional analysis/allocation, design synthesis and verification, and system analysis and control. The systems engineering process, when followed properly, will lead to higher quality products, lower cost products, and shorter development cycles. The System Engineering Capability Maturity Model (SE-CMM) will allow companies to measure their system engineering capability and continuously improve those capabilities. ISO 9000 and SE-CMM seem to have a similar objective, which is to document the organization's processes and certify to potential customers the capability of a supplier to control the processes that determine the quality of the product or services being produced. The remaining sections of this report examine the differences and similarities between ISO 9000 and SE-CMM and make recommendations for implementation.

45 CFR 307.0 - Scope of this part.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) The requirement for computerized support enforcement systems; (b) The functional requirements that a statewide computerized support enforcement system must meet; (c) Security and confidentiality requirements... to approving an advance planning document (APD); (e) The requirements and procedures for the...

Organizing Performance Requirements For Dynamical Systems

NASA Technical Reports Server (NTRS)

Malchow, Harvey L.; Croopnick, Steven R.

1990-01-01

Paper describes methodology for establishing performance requirements for complicated dynamical systems. Uses top-down approach. In series of steps, makes connections between high-level mission requirements and lower-level functional performance requirements. Provides systematic delineation of elements accommodating design compromises.

14 CFR 25.1705 - Systems and functions: EWIS.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 1 2010-01-01 2010-01-01 false Systems and functions: EWIS. 25.1705 Section 25.1705 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION... (EWIS) § 25.1705 Systems and functions: EWIS. (a) EWIS associated with any system required for type...

On-board Attitude Determination System (OADS). [for advanced spacecraft missions

NASA Technical Reports Server (NTRS)

Carney, P.; Milillo, M.; Tate, V.; Wilson, J.; Yong, K.

1978-01-01

The requirements, capabilities and system design for an on-board attitude determination system (OADS) to be flown on advanced spacecraft missions were determined. Based upon the OADS requirements and system performance evaluation, a preliminary on-board attitude determination system is proposed. The proposed OADS system consists of one NASA Standard IRU (DRIRU-2) as the primary attitude determination sensor, two improved NASA Standard star tracker (SST) for periodic update of attitude information, a GPS receiver to provide on-board space vehicle position and velocity vector information, and a multiple microcomputer system for data processing and attitude determination functions. The functional block diagram of the proposed OADS system is shown. The computational requirements are evaluated based upon this proposed OADS system.

Hypersonic Research Vehicle (HRV) real-time flight test support feasibility and requirements study. Part 2: Remote computation support for flight systems functions

NASA Technical Reports Server (NTRS)

Rediess, Herman A.; Hewett, M. D.

1991-01-01

The requirements are assessed for the use of remote computation to support HRV flight testing. First, remote computational requirements were developed to support functions that will eventually be performed onboard operational vehicles of this type. These functions which either cannot be performed onboard in the time frame of initial HRV flight test programs because the technology of airborne computers will not be sufficiently advanced to support the computational loads required, or it is not desirable to perform the functions onboard in the flight test program for other reasons. Second, remote computational support either required or highly desirable to conduct flight testing itself was addressed. The use is proposed of an Automated Flight Management System which is described in conceptual detail. Third, autonomous operations is discussed and finally, unmanned operations.

47 CFR 80.1081 - Functional requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 5 2014-10-01 2014-10-01 false Functional requirements. 80.1081 Section 80.1081 Telecommunication FEDERAL COMMUNICATIONS COMMISSION (CONTINUED) SAFETY AND SPECIAL RADIO SERVICES STATIONS IN THE MARITIME SERVICES Global Maritime Distress and Safety System (GMDSS) Equipment Requirements...

47 CFR 80.1081 - Functional requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 5 2013-10-01 2013-10-01 false Functional requirements. 80.1081 Section 80.1081 Telecommunication FEDERAL COMMUNICATIONS COMMISSION (CONTINUED) SAFETY AND SPECIAL RADIO SERVICES STATIONS IN THE MARITIME SERVICES Global Maritime Distress and Safety System (GMDSS) Equipment Requirements...

47 CFR 80.1081 - Functional requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 5 2012-10-01 2012-10-01 false Functional requirements. 80.1081 Section 80.1081 Telecommunication FEDERAL COMMUNICATIONS COMMISSION (CONTINUED) SAFETY AND SPECIAL RADIO SERVICES STATIONS IN THE MARITIME SERVICES Global Maritime Distress and Safety System (GMDSS) Equipment Requirements...

47 CFR 80.1081 - Functional requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 47 Telecommunication 5 2011-10-01 2011-10-01 false Functional requirements. 80.1081 Section 80.1081 Telecommunication FEDERAL COMMUNICATIONS COMMISSION (CONTINUED) SAFETY AND SPECIAL RADIO SERVICES STATIONS IN THE MARITIME SERVICES Global Maritime Distress and Safety System (GMDSS) Equipment Requirements...

US-75 ICM system requirements : Dallas Integrated Corridor Management (ICM) demonstration project.

DOT National Transportation Integrated Search

2010-12-01

This document is intended as a listing and discussion of the Requirements for the US-75 Integrated Corridor Management System (ICMS) Demonstration Project in Dallas. This document describes what the system is to do (the functional requirements), how ...

Oak Ridge Environmental Information System (OREIS) functional system design document

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

Birchfield, T.E.; Brown, M.O.; Coleman, P.R.

1994-03-01

The OREIS Functional System Design document provides a detailed functional description of the Oak Ridge Environmental Information System (OREIS). It expands the system requirements defined in the OREIS Phase 1-System Definition Document (ES/ER/TM-34). Documentation of OREIS development is based on the Automated Data Processing System Development Methodology, a Martin Marietta Energy Systems, Inc., procedure written to assist in developing scientific and technical computer systems. This document focuses on the development of the functional design of the user interface, which includes the integration of commercial applications software. The data model and data dictionary are summarized briefly; however, the Data Management Planmore » for OREIS (ES/ER/TM-39), a companion document to the Functional System Design document, provides the complete data dictionary and detailed descriptions of the requirements for the data base structure. The OREIS system will provide the following functions, which are executed from a Menu Manager: (1) preferences, (2) view manager, (3) macro manager, (4) data analysis (assisted analysis and unassisted analysis), and (5) spatial analysis/map generation (assisted ARC/INFO and unassisted ARC/INFO). Additional functionality includes interprocess communications, which handle background operations of OREIS.« less

Requirements Development for the NASA Advanced Engineering Environment (AEE)

NASA Technical Reports Server (NTRS)

Rogers, Eric; Hale, Joseph P.; Zook, Keith; Gowda, Sanjay; Salas, Andrea O.

2003-01-01

The requirements development process for the Advanced Engineering Environment (AEE) is presented. This environment has been developed to allow NASA to perform independent analysis and design of space transportation architectures and technologies. Given the highly collaborative and distributed nature of AEE, a variety of organizations are involved in the development, operations and management of the system. Furthermore, there are additional organizations involved representing external customers and stakeholders. Thorough coordination and effective communication is essential to translate desired expectations of the system into requirements. Functional, verifiable requirements for this (and indeed any) system are necessary to fulfill several roles. Requirements serve as a contractual tool, configuration management tool, and as an engineering tool, sometimes simultaneously. The role of requirements as an engineering tool is particularly important because a stable set of requirements for a system provides a common framework of system scope and characterization among team members. Furthermore, the requirements provide the basis for checking completion of system elements and form the basis for system verification. Requirements are at the core of systems engineering. The AEE Project has undertaken a thorough process to translate the desires and expectations of external customers and stakeholders into functional system-level requirements that are captured with sufficient rigor to allow development planning, resource allocation and system-level design, development, implementation and verification. These requirements are maintained in an integrated, relational database that provides traceability to governing Program requirements and also to verification methods and subsystem-level requirements.

US Search and Rescue Mission Control Center functions

NASA Technical Reports Server (NTRS)

1977-01-01

A satellite aided Search and Rescue (SAR) Mission concept consisting of a local coverage bent pipe system, and a global coverage system is described. The SAR instrument is to consist of a Canadian repeater and a French processor for which Canada and France, respectively are to evaluate health and trends. Performance evaluations of each system were provided. The United States and Canada will each have a Search and Rescue Mission Control Center (MCC) and their functions were also examined. A summary of the interface requirements necessary to perform each function was included as well as the information requirements between the USMCC and each of its interfaces. Physical requirements such as location, manning etc. of the USMCC were discussed.

Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 5: Design of the IPAD system. Part 2: System design. Part 3: General purpose utilities, phase 1, task 2

NASA Technical Reports Server (NTRS)

Garrocq, C. A.; Hurley, M. J.

1973-01-01

Viable designs are presented of various elements of the IPAD framework software, data base management system, and required new languages in relation to the capabilities of operating systems software. A thorough evaluation was made of the basic systems functions to be provide by each software element, its requirements defined in the conceptual design, the operating systems features affecting its design, and the engineering/design functions which it was intended to enhance.

Functions & Requirements for Debris Removal System Project A-2

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

PRECECHTEL, D.R.

1999-12-29

This revision of the Functions and Requirements Document updates the approved Functions and Requirements for Debris Removal Subproject WHC-SD-SNF-FRD-009, Rev. 0. It has been revised in its entirety to reflect the current scope of work for Debris Removal as canisters and lids under the K Basin Projects work breakdown structure (WBS). In this revision the canisters and lids will be consider debris and a new set of Functions and Requirements have been developed to remove the canisters and lids from the basin.

Systems engineering principles for the design of biomedical signal processing systems.

PubMed

Faust, Oliver; Acharya U, Rajendra; Sputh, Bernhard H C; Min, Lim Choo

2011-06-01

Systems engineering aims to produce reliable systems which function according to specification. In this paper we follow a systems engineering approach to design a biomedical signal processing system. We discuss requirements capturing, specification definition, implementation and testing of a classification system. These steps are executed as formal as possible. The requirements, which motivate the system design, are based on diabetes research. The main requirement for the classification system is to be a reliable component of a machine which controls diabetes. Reliability is very important, because uncontrolled diabetes may lead to hyperglycaemia (raised blood sugar) and over a period of time may cause serious damage to many of the body systems, especially the nerves and blood vessels. In a second step, these requirements are refined into a formal CSP‖ B model. The formal model expresses the system functionality in a clear and semantically strong way. Subsequently, the proven system model was translated into an implementation. This implementation was tested with use cases and failure cases. Formal modeling and automated model checking gave us deep insight in the system functionality. This insight enabled us to create a reliable and trustworthy implementation. With extensive tests we established trust in the reliability of the implementation. Copyright © 2010 Elsevier Ireland Ltd. All rights reserved.

Computer Applications Group FY91 final report, February 11, 1991--September 30, 1991

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

Not Available

1992-02-24

This Functional Requirements Document (FRD) defines the functional requirements and general solutions required for design of the Integrated Data System (IDS). The FRD is the primary source of requirements for the designers and all requirements used in the design process shall be part of this or succeeding revisions of the FRD with no exceptions.

C2 Link Security for UAS: Technical Literature Study and Preliminary Functional Requirements. Version 0.9 (Working Draft)

NASA Technical Reports Server (NTRS)

2005-01-01

This document provides a study of the technical literature related to Command and Control (C2) link security for Unmanned Aircraft Systems (UAS) for operation in the National Airspace System (NAS). Included is a preliminary set of functional requirements for C2 link security.

Automated Orbit Determination System (AODS) requirements definition and analysis

NASA Technical Reports Server (NTRS)

Waligora, S. R.; Goorevich, C. E.; Teles, J.; Pajerski, R. S.

1980-01-01

The requirements definition for the prototype version of the automated orbit determination system (AODS) is presented including the AODS requirements at all levels, the functional model as determined through the structured analysis performed during requirements definition, and the results of the requirements analysis. Also specified are the implementation strategy for AODS and the AODS-required external support software system (ADEPT), input and output message formats, and procedures for modifying the requirements.

49 CFR 236.1011 - PTC Implementation Plan content requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... technology embedded in PTC systems that does not employ all of the functionalities required by this subpart... INSTALLATION, INSPECTION, MAINTENANCE, AND REPAIR OF SIGNAL AND TRAIN CONTROL SYSTEMS, DEVICES, AND APPLIANCES Positive Train Control Systems § 236.1011 PTC Implementation Plan content requirements. (a) Contents. A...

49 CFR 236.1011 - PTC Implementation Plan content requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... technology embedded in PTC systems that does not employ all of the functionalities required by this subpart... INSTALLATION, INSPECTION, MAINTENANCE, AND REPAIR OF SIGNAL AND TRAIN CONTROL SYSTEMS, DEVICES, AND APPLIANCES Positive Train Control Systems § 236.1011 PTC Implementation Plan content requirements. (a) Contents. A...

49 CFR 236.1011 - PTC Implementation Plan content requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... technology embedded in PTC systems that does not employ all of the functionalities required by this subpart... INSTALLATION, INSPECTION, MAINTENANCE, AND REPAIR OF SIGNAL AND TRAIN CONTROL SYSTEMS, DEVICES, AND APPLIANCES Positive Train Control Systems § 236.1011 PTC Implementation Plan content requirements. (a) Contents. A...

HALE UAS Concept of Operations. Version 3.0

NASA Technical Reports Server (NTRS)

2006-01-01

This document is a system level Concept of Operations (CONOPS) from the perspective of future High Altitude Long Endurance (HALE) Unmanned Aircraft Systems (UAS) service providers and National Airspace System (NAS) users. It describes current systems (existing UAS), describes HALE UAS functions and operations to be performed (via sample missions), and offers insight into the user s environment (i.e., the UAS as a system of systems). It is intended to be a source document for NAS UAS operational requirements, and provides a construct for government agencies to use in guiding their regulatory decisions, architecture requirements, and investment strategies. Although it does not describe the technical capabilities of a specific HALE UAS system (which do, and will vary widely), it is intended to aid in requirements capture and to be used as input to the functional requirements and analysis process. The document provides a basis for development of functional requirements and operational guidelines to achieve unrestricted access into the NAS. This document is an FY06 update to the FY05 Access 5 Project-approved Concept of Operations document previously published in the Public Domain on the Access 5 open website. This version is recommended to be approved for public release also. The updates are a reorganization of materials from the previous version with the addition of an updated set of operational requirements, inclusion of sample mission scenarios, and identification of roles and responsibilities of interfaces within flight phases.

Quadrature, Interpolation and Observability

NASA Technical Reports Server (NTRS)

Hodges, Lucille McDaniel

1997-01-01

Methods of interpolation and quadrature have been used for over 300 years. Improvements in the techniques have been made by many, most notably by Gauss, whose technique applied to polynomials is referred to as Gaussian Quadrature. Stieltjes extended Gauss's method to certain non-polynomial functions as early as 1884. Conditions that guarantee the existence of quadrature formulas for certain collections of functions were studied by Tchebycheff, and his work was extended by others. Today, a class of functions which satisfies these conditions is called a Tchebycheff System. This thesis contains the definition of a Tchebycheff System, along with the theorems, proofs, and definitions necessary to guarantee the existence of quadrature formulas for such systems. Solutions of discretely observable linear control systems are of particular interest, and observability with respect to a given output function is defined. The output function is written as a linear combination of a collection of orthonormal functions. Orthonormal functions are defined, and their properties are discussed. The technique for evaluating the coefficients in the output function involves evaluating the definite integral of functions which can be shown to form a Tchebycheff system. Therefore, quadrature formulas for these integrals exist, and in many cases are known. The technique given is useful in cases where the method of direct calculation is unstable. The condition number of a matrix is defined and shown to be an indication of the the degree to which perturbations in data affect the accuracy of the solution. In special cases, the number of data points required for direct calculation is the same as the number required by the method presented in this thesis. But the method is shown to require more data points in other cases. A lower bound for the number of data points required is given.

The role of man in flight experiment payload missions. Volume 2: Appendices

NASA Technical Reports Server (NTRS)

Malone, T. B.

1973-01-01

In the study to determine the role of man in Sortie Lab operations, a functional model of a generalized experiment system was developed. The results are presented of a requirements analysis which was conducted to identify performance requirements, information requirements, and interface requirements associated with each function in the model.

Training Records And Information Network UNIX Version

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

Johnston, Michael

1996-12-01

TRAIN-UNIX is used to track training requirements, qualifications, training completion and schedule training, classrooms and instructors. TRAIN-UNIX is a requirements-based system. When the identified training requirements for specific jobs are entered into the system, the employees manager or responsible training person assigns jobs to an employee. TRAIN-UNIX will then assemble an Individual Training Plan (ITP) with all courses required. ITP''s can also be modified to add any special training directed or identified by management, best business practices, procedures, etc. TRAIN-UNIX also schedules and tracks conferences, seminars, and required reading. TRAIN-UNIX is a secure database system on a server accessible viamore » the network. Access to the user functions (scheduling, data entry, ITP modification etc.) within TRAIN-UNIX are granted by function, as needed, by the system administrator. An additional level of security allows those who access TRAIN-UNIX to only add, modify or view information for the organizations to which they belong. TRAIN-UNIX scheduling function allows network access to scheduling of students. As a function of the scheduling process, TRAIN-UNIX checks to insure that the student is a valid employee, not double booked, and the instructor and classroom are not double booked. TRAIN-UNIX will report pending lapse of courses or qualifications. This ability to know the lapse of training along with built in training requesting function allows the training deliverers to forecast training needs.« less

TRAIN-UNIX. Training Records And Information Network UNIX Version

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

Lawrence, M.E.; Crires, J.T.; Johnston, M.

1995-12-01

TRAIN-UNIX is used to track training requirements, qualifications, training completion and schedule training, classrooms and instructors. TRAIN-UNIX is a requirements-based system. When the identified training requirements for specific jobs are entered into the system, the employees manager or responsible training person assigns jobs to an employee. TRAIN-UNIX will then assemble an Individual Training Plan (ITP) with all courses required. ITP`s can also be modified to add any special training directed or identified by management, best business practices, procedures, etc. TRAIN-UNIX also schedules and tracks conferences, seminars, and required reading. TRAIN-UNIX is a secure database system on a server accessible viamore » the network. Access to the user functions (scheduling, data entry, ITP modification etc.) within TRAIN-UNIX are granted by function, as needed, by the system administrator. An additional level of security allows those who access TRAIN-UNIX to only add, modify or view information for the organizations to which they belong. TRAIN-UNIX scheduling function allows network access to scheduling of students. As a function of the scheduling process, TRAIN-UNIX checks to insure that the student is a valid employee, not double booked, and the instructor and classroom are not double booked. TRAIN-UNIX will report pending lapse of courses or qualifications. This ability to know the lapse of training along with built in training requesting function allows the training deliverers to forecast training needs.« less

Advanced information processing system: Inter-computer communication services

NASA Technical Reports Server (NTRS)

Burkhardt, Laura; Masotto, Tom; Sims, J. Terry; Whittredge, Roy; Alger, Linda S.

1991-01-01

The purpose is to document the functional requirements and detailed specifications for the Inter-Computer Communications Services (ICCS) of the Advanced Information Processing System (AIPS). An introductory section is provided to outline the overall architecture and functional requirements of the AIPS and to present an overview of the ICCS. An overview of the AIPS architecture as well as a brief description of the AIPS software is given. The guarantees of the ICCS are provided, and the ICCS is described as a seven-layered International Standards Organization (ISO) Model. The ICCS functional requirements, functional design, and detailed specifications as well as each layer of the ICCS are also described. A summary of results and suggestions for future work are presented.

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

NASA Technical Reports Server (NTRS)

2007-01-01

This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

Surface infrastructure functions, requirements and subsystems for a manned Mars mission

NASA Technical Reports Server (NTRS)

Fairchild, Kyle

1986-01-01

Planning and development for a permanently manned scientific outpost on Mars requires an in-depth understanding and analysis of the functions the outpost is expected to perform. The optimum configuration that accomplishes these functions then arises during the trade studies process. In a project this complex, it becomes necessary to use a formal methodology to document the design and planning process. The method chosen for this study is called top-down functional decomposition. This method is used to determine the functions that are needed to accomplish the overall mission, then determine what requirements and systems are needed to do each of the functions. This method facilitates automation of the trades and options process. In the example, this was done with an off-the shelf software package called TK! olver. The basic functions that a permanently manned outpost on Mars must accomplish are: (1) Establish the Life Critical Systems; (2) Support Planetary Sciences and Exploration; and (3) Develop and Maintain Long-term Support Functions, including those systems needed towards self-sufficiency. The top-down functional decomposition methology, combined with standard spread sheet software, offers a powerful tool to quickly assess various design trades and analyze options. As the specific subsystems, and the relational rule algorithms are further refined, it will be possible to very accurately determine the implications of continually evolving mission requirements.

Collision Avoidance Functional Requirements for Step 1. Revision 6

NASA Technical Reports Server (NTRS)

2006-01-01

This Functional Requirements Document (FRD) describes the flow of requirements from the high level operational objectives down to the functional requirements specific to cooperative collision avoidance for high altitude, long endurance unmanned aircraft systems. These are further decomposed into performance and safety guidelines that are backed up by analysis or references to various documents or research findings. The FRD should be considered when establishing future policies, procedures, and standards pertaining to cooperative collision avoidance.

Functional and performance requirements of the next NOAA-Kasas City computer system

NASA Technical Reports Server (NTRS)

Mosher, F. R.

1985-01-01

The development of the Advanced Weather Interactive Processing System for the 1990's (AWIPS-90) will result in more timely and accurate forecasts with improved cost effectiveness. As part of the AWIPS-90 initiative, the National Meteorological Center (NMC), the National Severe Storms Forecast Center (NSSFC), and the National Hurricane Center (NHC) are to receive upgrades of interactive processing systems. This National Center Upgrade program will support the specialized inter-center communications, data acquisition, and processing needs of these centers. The missions, current capabilities and general functional requirements for the upgrade to the NSSFC are addressed. System capabilities are discussed along with the requirements for the upgraded system.

System Concept Study for a Cargo Data Interchange System (CARDIS)

DOT National Transportation Integrated Search

1975-04-01

The report presents the analysis of functional and operational requirements of CARDIS. From these requirements, system sizing estimates are derived. Three potential CARDIS concepts are introduced for consideration in subsequent analysis. Their charac...

Advanced flight deck/crew station simulator functional requirements

NASA Technical Reports Server (NTRS)

Wall, R. L.; Tate, J. L.; Moss, M. J.

1980-01-01

This report documents a study of flight deck/crew system research facility requirements for investigating issues involved with developing systems, and procedures for interfacing transport aircraft with air traffic control systems planned for 1985 to 2000. Crew system needs of NASA, the U.S. Air Force, and industry were investigated and reported. A matrix of these is included, as are recommended functional requirements and design criteria for simulation facilities in which to conduct this research. Methods of exploiting the commonality and similarity in facilities are identified, and plans for exploiting this in order to reduce implementation costs and allow efficient transfer of experiments from one facility to another are presented.

A Case Study of Non-Functional Requirements and Continuous Improvement at a National Communications System Contractor

ERIC Educational Resources Information Center

Douglas, Volney L. R.

2010-01-01

National communications systems (NCS) are critical elements of a government's infrastructure. Limited improvements to the non-functional requirements (NFR) of NCS have caused issues during national emergencies such as 9/11 and Hurricane Katrina. The literature indicates that these issues result from a deficiency in understanding the roles NFRs and…

The Functional Breakdown Structure (FBS) and Its Relationship to Life Cycle Cost

NASA Technical Reports Server (NTRS)

DeHoff, Bryan; Levack, Danie J. H.; Rhodes, Russell E.

2009-01-01

The Functional Breakdown Structure (FBS) is a structured, modular breakdown of every function that must be addressed to perform a generic mission. It is also usable for any subset of the mission. Unlike a Work Breakdown Structure (WBS), the FBS is a function-oriented tree, not a product-oriented tree. The FBS details not products, but operations or activities that should be performed. The FBS is not tied to any particular architectural implementation because it is a listing of the needed functions, not the elements, of the architecture. The FBS for Space Transportation Systems provides a universal hierarchy of required functions, which include ground and space operations as well as infrastructure - it provides total visibility of the entire mission. By approaching the systems engineering problem from the functional view, instead of the element or hardware view, the SPST has created an exhaustive list of potential requirements which the architecture designers can use to evaluate the completeness of their designs. This is a new approach that will provide full accountability of all functions required to perform the planned mission. It serves as a giant check list to be sure that no functions are omitted, especially in the early architectural design phase. A significant characteristic of a FBS is that if architecture options are compared using this approach, then any missing or redundant elements of each option will be ' identified. Consequently, valid Life Cycle Costs (LCC) comparisons can be made. For example, one architecture option might not need a particular function while another option does. One option may have individual elements to perform each of three functions while another option needs only one element to perform the three functions. Once an architecture has been selected, the FBS will serve as a guide in development of the work breakdown structure, provide visibility of those technologies that need to be further developed to perform required functions, and help identify the personnel skills required to develop and operate the architecture. It also wifi allow the systems engineering activities to totally integrate each discipline to the maximum extent possible and optimize at the total system level, thus avoiding optimizing at the element level (stove-piping). In addition, it furnishes a framework that wifi help prevent over or under specifying requirements because all functions are identified and all elements are aligned to functions.

Functional Mobility Testing: A Novel Method to Create Suit Design Requirements

NASA Technical Reports Server (NTRS)

England, Scott A.; Benson, Elizabeth A.; Rajulu, Sudhakar L.

2008-01-01

This study was performed to aide in the creation of design requirements for the next generation of space suits that more accurately describe the level of mobility necessary for a suited crewmember through the use of an innovative methodology utilizing functional mobility. A novel method was utilized involving the collection of kinematic data while 20 subjects (10 male, 10 female) performed pertinent functional tasks that will be required of a suited crewmember during various phases of a lunar mission. These tasks were selected based on relevance and criticality from a larger list of tasks that may be carried out by the crew. Kinematic data was processed through Vicon BodyBuilder software to calculate joint angles for the ankle, knee, hip, torso, shoulder, elbow, and wrist. Maximum functional mobility was consistently lower than maximum isolated mobility. This study suggests that conventional methods for establishing design requirements for human-systems interfaces based on maximal isolated joint capabilities may overestimate the required mobility. Additionally, this method provides a valuable means of evaluating systems created from these requirements by comparing the mobility available in a new spacesuit, or the mobility required to use a new piece of hardware, to this newly established database of functional mobility.

In-Vehicle Signing Functions and Systems Concepts

DOT National Transportation Integrated Search

1996-01-01

This paper describes functional requirements and system concepts for an In-Vehicle Signing (IVS) system, which will bring information from roadway signs, signals, and pavement markings into the vehicle for presentation to the driver. Information filt...

Requirements as Goals and Commitments Too

NASA Astrophysics Data System (ADS)

Chopra, Amit K.; Mylopoulos, John; Dalpiaz, Fabiano; Giorgini, Paolo; Singh, Munindar P.

In traditional software engineering research and practice, requirements are classified either as functional or non-functional. Functional requirements consist of all functions the system-to-be ought to support, and have been modeled in terms of box-and-arrow diagrams in the spirit of SADT. Non-functional requirements include desired software qualities for the system-to-be and have been described either in natural language or in terms of metrics. This orthodoxy was challenged in the mid-90 s by a host of proposals that had a common theme: all requirements are initially stakeholder goals and ought to be elicited, modeled and analyzed as such. Through systematic processes, these goals can be refined into specifications of functions the system-to-be needs to deliver, while actions assigned to external actors need to be executed. This view is dominating Requirements Engineering (RE) research and is beginning to have an impact on RE practice. We propose a next step along this line of research, by adopting the concept of conditional commitment as companion concept to that of goal. Goals are intentional entities that capture the needs and wants of stakeholders. Commitments, on the other hand, are social concepts that define the willingness and capability of an actor A to fulfill a predicate ϕ for the benefit of actor B, provided B (in return) fulfills predicate ψ for the benefit of actor A. In our conceptualization, goals are mapped to collections of commitments rather than functions, qualities, or actor assignments. We motivate the importance of the concept of commitment for RE through examples and discussion. We also contrast our proposal with state-of-the-art requirements modeling and analysis frameworks, such as KAOS, MAP, i * and Tropos.

A Cross-Functional Systems Project in an IS Capstone Course

ERIC Educational Resources Information Center

Maloni, Michael; Dembla, Pamila; Swaim, J. Anthony

2012-01-01

Information systems (IS) practitioners must regularly work cross-functionally with business users when implementing enterprise systems. However, most IS higher education is not truly cross-functional in nature with students typically relying on instructors or even themselves to represent user requirements. To address this gap, we describe an…

76 FR 8923 - Explosive Siting Requirements

Federal Register 2010, 2011, 2012, 2013, 2014

2011-02-16

....regulations.gov , including any personal information you provide. Using the search function of the docket Web... requirements, but do not impose explicit separation requirements. The employer must guarantee the mechanical... ensure these systems are adequate for their functions and must maintain the components. 29 CFR 1910.119(j...

Step 1: Human System Integration Pilot-Technology Interface Requirements for Weather Management

NASA Technical Reports Server (NTRS)

2005-01-01

This document involves definition of technology interface requirements for Hazardous Weather Avoidance. Technology concepts in use by the Access 5 Weather Management Work Package were considered. Beginning with the Human System Integration (HIS) high-level functional requirement for Hazardous Weather Avoidance, and Hazardous Weather Avoidance technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of hazardous weather, and (2) the control capability needed by the pilot to obtain hazardous weather information. Fundamentally, these requirements provide the candidate Hazardous Weather Avoidance technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Hazardous Weather Avoidance operations and functions should interface with the pilot to provide the necessary Weather Management functionality to the UA-pilot system. Requirements and guidelines for Hazardous Weather Avoidance are partitioned into four categories: (1) Planning En Route (2) Encountering Hazardous Weather En Route, (3) Planning to Destination, and (4) Diversion Planning Alternate Airport. Each requirement is stated and is supported with a rationale and associated reference(s).

Space-based multifunctional end effector systems functional requirements and proposed designs

NASA Technical Reports Server (NTRS)

Mishkin, A. H.; Jau, B. M.

1988-01-01

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested manipulator systems in time for space stations operations in the early 1990s.

Kinematics and constraints associated with swashplate blade pitch control

NASA Technical Reports Server (NTRS)

Leyland, Jane A.

1993-01-01

An important class of techniques to reduce helicopter vibration is based on using a Higher Harmonic controller to optimally define the Higher Harmonic blade pitch. These techniques typically require solution of a general optimization problem requiring the determination of a control vector which minimizes a performance index where functions of the control vector are subject to inequality constraints. Six possible constraint functions associated with swashplate blade pitch control were identified and defined. These functions constrain: (1) blade pitch Fourier Coefficients expressed in the Rotating System, (2) blade pitch Fourier Coefficients expressed in the Nonrotating System, (3) stroke of the individual actuators expressed in the Nonrotating System, (4) blade pitch expressed as a function of blade azimuth and actuator stroke, (5) time rate-of-change of the aforementioned parameters, and (6) required actuator power. The aforementioned constraints and the associated kinematics of swashplate blade pitch control by means of the strokes of the individual actuators are documented.

MODIS. Volume 1: MODIS level 1A software baseline requirements

NASA Technical Reports Server (NTRS)

Masuoka, Edward; Fleig, Albert; Ardanuy, Philip; Goff, Thomas; Carpenter, Lloyd; Solomon, Carl; Storey, James

1994-01-01

This document describes the level 1A software requirements for the moderate resolution imaging spectroradiometer (MODIS) instrument. This includes internal and external requirements. Internal requirements include functional, operational, and data processing as well as performance, quality, safety, and security engineering requirements. External requirements include those imposed by data archive and distribution systems (DADS); scheduling, control, monitoring, and accounting (SCMA); product management (PM) system; MODIS log; and product generation system (PGS). Implementation constraints and requirements for adapting the software to the physical environment are also included.

A system decomposition approach to the design of functional observers

NASA Astrophysics Data System (ADS)

Fernando, Tyrone; Trinh, Hieu

2014-09-01

This paper reports a system decomposition that allows the construction of a minimum-order functional observer using a state observer design approach. The system decomposition translates the functional observer design problem to that of a state observer for a smaller decomposed subsystem. Functional observability indices are introduced, and a closed-form expression for the minimum order required for a functional observer is derived in terms of those functional observability indices.

From Science To Design: Systems Engineering For The Lsst

NASA Astrophysics Data System (ADS)

Claver, Chuck F.; Axelrod, T.; Fouts, K.; Kantor, J.; Nordby, M.; Sebag, J.; LSST Collaboration

2009-01-01

The LSST is a universal-purpose survey telescope that will address scores of scientific missions. To assist the technical teams to convergence to a specific engineering design, the LSST Science Requirements Document (SRD) selects four stressing principle scientific missions: 1) Constraining Dark Matter and Dark Energy; 2) taking an Inventory of the Solar System; 3) Exploring the Transient Optical Sky; and 4) mapping the Milky Way. From these 4 missions the SRD specifies the needed requirements for single images and the full 10 year survey that enables a wide range of science beyond the 4 principle missions. Through optical design and analysis, operations simulation, and throughput modeling the systems engineering effort in the LSST has largely focused on taking the SRD specifications and deriving system functional requirements that define the system design. A Model Based Systems Engineering approach with SysML is used to manage the flow down of requirements from science to system function to sub-system. The rigor of requirements flow and management assists the LSST in keeping the overall scope, hence budget and schedule, under control.

46 CFR 58.30-5 - Design requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Design requirements. 58.30-5 Section 58.30-5 Shipping... AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-5 Design requirements. (a) The.... (b) The system shall be so designed that proper functioning of any unit shall not be affected by the...

46 CFR 58.30-5 - Design requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Design requirements. 58.30-5 Section 58.30-5 Shipping... AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-5 Design requirements. (a) The.... (b) The system shall be so designed that proper functioning of any unit shall not be affected by the...

The Architect's Guide to Mechanical Systems.

ERIC Educational Resources Information Center

Andrews, F. T.

The principles and problems of designing new building mechanical systems are discussed in this reference source in the light of data on the functions and operation of mechanical systems. As a practical guide to understanding mechanical systems it describes system types, functions, space requirements, weights, installation, maintenance and…

Accessing FMS Functionality: The Impact of Design on Learning

NASA Technical Reports Server (NTRS)

Fennell, Karl; Sherry, Lance; Roberts, Ralph, Jr.

2004-01-01

In modern commercial and military aircraft, the Flight Management System (FMS) lies at the heart of the functionality of the airplane. The nature of the FMS has also caused great difficulties learning and accessing this functionality. This study examines actual Air Force pilots who were qualified on the newly introduced advanced FMS and shows that the design of the system itself is a primary source of difficulty learning the system. Twenty representative tasks were selected which the pilots could be expected to accomplish on an ' actual flight. These tasks were analyzed using the RAFIV stage model (Sherry, Polson, et al. 2002). This analysis demonstrates that a great burden is placed on remembering complex reformulation of the task to function mapping. 65% of the tasks required retaining one access steps in memory to accomplish the task, 20% required two memorized access steps, and 15% required zero memorized access steps. The probability that a participant would make an access error on the tasks was: two memorized access steps - 74%, one memorized access step - 13%, and zero memorized access steps - 6%. Other factors were analyzed as well, including experience with the system and frequency of use. This completed the picture of a system with many memorized steps causing difficulty with the new system, especially when trying to fine where to access the correct function.

Client Functional Assessment Data as Management Information: Woodrow Wilson Rehabilitation Center's Management Information System

PubMed Central

Steidle, Ernest F.

1983-01-01

This paper describes the design of a functional assessment system, a component of a management information system (MIS) that supports a comprehensive rehabilitation facility. Products of the subsystem document the functional status of rehabilitation clients through process evaluation reporting and outcomes reporting. The purpose of this paper is to describe the design of this MIS component. The environment supported, the integration requirements and the needed development approach is unique, requiring significant input from health care professionals, medical informatics specialists, statisticians and program evaluators. Strategies for the implementation of the functional assessment system are the major results reported in this paper. They are most useful to the systems designer or management engineer in a human service delivery setting. MIS plan development, computer file structure and access methods, and approaches to scheduling applications is described. Finally, the development of functional status measures is discussed. Application of the methodologies described will facilitate similar efforts towards systems development in other human service delivery settings.

Formal analysis of imprecise system requirements with Event-B.

PubMed

Le, Hong Anh; Nakajima, Shin; Truong, Ninh Thuan

2016-01-01

Formal analysis of functional properties of system requirements needs precise descriptions. However, the stakeholders sometimes describe the system with ambiguous, vague or fuzzy terms, hence formal frameworks for modeling and verifying such requirements are desirable. The Fuzzy If-Then rules have been used for imprecise requirements representation, but verifying their functional properties still needs new methods. In this paper, we propose a refinement-based modeling approach for specification and verification of such requirements. First, we introduce a representation of imprecise requirements in the set theory. Then we make use of Event-B refinement providing a set of translation rules from Fuzzy If-Then rules to Event-B notations. After that, we show how to verify both safety and eventuality properties with RODIN/Event-B. Finally, we illustrate the proposed method on the example of Crane Controller.

NEXT Single String Integration Test Results

NASA Technical Reports Server (NTRS)

Soulas, George C.; Patterson, Michael J.; Pinero, Luis; Herman, Daniel A.; Snyder, Steven John

2010-01-01

As a critical part of NASA's Evolutionary Xenon Thruster (NEXT) test validation process, a single string integration test was performed on the NEXT ion propulsion system. The objectives of this test were to verify that an integrated system of major NEXT ion propulsion system elements meets project requirements, to demonstrate that the integrated system is functional across the entire power processor and xenon propellant management system input ranges, and to demonstrate to potential users that the NEXT propulsion system is ready for transition to flight. Propulsion system elements included in this system integration test were an engineering model ion thruster, an engineering model propellant management system, an engineering model power processor unit, and a digital control interface unit simulator that acted as a test console. Project requirements that were verified during this system integration test included individual element requirements ; integrated system requirements, and fault handling. This paper will present the results of these tests, which include: integrated ion propulsion system demonstrations of performance, functionality and fault handling; a thruster re-performance acceptance test to establish baseline performance: a risk-reduction PMS-thruster integration test: and propellant management system calibration checks.

Section 3: Quality and Value-Based Requirements

NASA Astrophysics Data System (ADS)

Mylopoulos, John

Traditionally, research and practice in software engineering has focused its attention on specific software qualities, such as functionality and performance. According to this perspective, a system is deemed to be of good quality if it delivers all required functionality (“fitness-for-purpose”) and its performance is above required thresholds. Increasingly, primarily in research but also in practice, other qualities are attracting attention. To facilitate evolution, maintainability and adaptability are gaining popularity. Usability, universal accessibility, innovativeness, and enjoyability are being studied as novel types of non-functional requirements that we do not know how to define, let alone accommodate, but which we realize are critical under some contingencies. The growing importance of the business context in the design of software-intensive systems has also thrust economic value, legal compliance, and potential social and ethical implications into the forefront of requirements topics. A focus on the broader user environment and experience, as well as the organizational and societal implications of system use, thus has become more central to the requirements discourse. This section includes three contributions to this broad and increasingly important topic.

Weather Requirements and Procedures for Step 1: High Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS) Flight Operations in the National Air Space (NAS)

NASA Technical Reports Server (NTRS)

2007-01-01

This cover sheet is for version 2 of the weather requirements document along with Appendix A. The purpose of the requirements document was to identify and to list the weather functional requirements needed to achieve the Access 5 vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS) for Step 1." A discussion of the Federal Aviation Administration (FAA) references and related policies, procedures, and standards is provided as basis for the recommendations supported within this document. Additional procedures and reference documentation related to weather functional requirements is also provided for background. The functional requirements and related information are to be proposed to the FAA and various standards organizations for consideration and approval. The appendix was designed to show that sources of flight weather information are readily available to UAS pilots conducting missions in the NAS. All weather information for this presentation was obtained from the public internet.

Goal-Function Tree Modeling for Systems Engineering and Fault Management

NASA Technical Reports Server (NTRS)

Johnson, Stephen B.; Breckenridge, Jonathan T.

2013-01-01

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM).

Earth Observatory Satellite system definition study. Report no. 3: Design/cost tradeoff studies. Appendix C: EOS program requirements document

NASA Technical Reports Server (NTRS)

1974-01-01

An analysis of the requirements for the Earth Observatory Satellite (EOS) system specifications is presented. The analysis consists of requirements obtained from existing documentation and those derived from functional analysis. The requirements follow the hierarchy of program, mission, system, and subsystem. The code for designating specific requirements is explained. Among the subjects considered are the following: (1) the traffic model, (2) space shuttle related performance, (3) booster related performance, (4) the data collection system, (5) spacecraft structural tests, and (6) the ground support requirements.

Discrete shaped strain sensors for intelligent structures

NASA Technical Reports Server (NTRS)

Andersson, Mark S.; Crawley, Edward F.

1992-01-01

Design of discrete, highly distributed sensor systems for intelligent structures has been studied. Data obtained indicate that discrete strain-averaging sensors satisfy the functional requirements for distributed sensing of intelligent structures. Bartlett and Gauss-Hanning sensors, in particular, provide good wavenumber characteristics while meeting the functional requirements. They are characterized by good rolloff rates and positive Fourier transforms for all wavenumbers. For the numerical integration schemes, Simpson's rule is considered to be very simple to implement and consistently provides accurate results for five sensors or more. It is shown that a sensor system that satisfies the functional requirements can be applied to a structure that supports mode shapes with purely sinusoidal curvature.

The new Langley Research Center advanced real-time simulation (ARTS) system

NASA Technical Reports Server (NTRS)

Crawford, D. J.; Cleveland, J. I., II

1986-01-01

Based on a survey of current local area network technology with special attention paid to high bandwidth and very low transport delay requirements, NASA's Langley Research Center designed a new simulation subsystem using the computer automated measurement and control (CAMAC) network. This required significant modifications to the standard CAMAC system and development of a network switch, a clocking system, new conversion equipment, new consoles, supporting software, etc. This system is referred to as the advanced real-time simulation (ARTS) system. It is presently being built at LaRC. This paper provides a functional and physical description of the hardware and a functional description of the software. The requirements which drove the design are presented as well as present performance figures and status.

Lesson 7: From Requirements to Specific Solutions

EPA Pesticide Factsheets

CROMERR requirements set performance goals, they do not dictate specific system functions, operating procedures,system architecture, or technology. The task is to decide on a solution to meet the goals.

47 CFR 10.320 - Provider alert gateway requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 47 Telecommunication 1 2012-10-01 2012-10-01 false Provider alert gateway requirements. 10.320 Section 10.320 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL COMMERCIAL MOBILE ALERT SYSTEM System Architecture § 10.320 Provider alert gateway requirements. This section specifies the functions...

Sharing data between mobile devices, connected vehicles, and infrastructure task 3: system requirements specifications (SyRS) final.

DOT National Transportation Integrated Search

2016-07-14

This report describes the system requirements specifications (SyRS) for the use of mobile devices in a connected vehicle environment. Specifically, it defines the different types of requirements (functional, interface, performance, security, data, an...

EOS image data processing system definition study

NASA Technical Reports Server (NTRS)

Gilbert, J.; Honikman, T.; Mcmahon, E.; Miller, E.; Pietrzak, L.; Yorsz, W.

1973-01-01

The Image Processing System (IPS) requirements and configuration are defined for NASA-sponsored advanced technology Earth Observatory System (EOS). The scope included investigation and definition of IPS operational, functional, and product requirements considering overall system constraints and interfaces (sensor, etc.) The scope also included investigation of the technical feasibility and definition of a point design reflecting system requirements. The design phase required a survey of present and projected technology related to general and special-purpose processors, high-density digital tape recorders, and image recorders.

Space shuttle propulsion systems on-board checkout and monitoring system development study (extension). Volume 1: Summary and technical results

NASA Technical Reports Server (NTRS)

1972-01-01

An analysis was conducted of the space shuttle propulsion systems to define the onboard checkout and monitoring function. A baseline space shuttle vehicle and mission were used to establish the techniques and approach for defining the requirements. The requirements were analyzed to formulate criteria for implementing the functions of preflight checkout, performance monitoring, fault isolation, emergency detection, display, data storage, postflight evaluation, and maintenance retest.

Electrical power systems for Mars

NASA Technical Reports Server (NTRS)

Giudici, Robert J.

1986-01-01

Electrical power system options for Mars Manned Modules and Mars Surface Bases were evaluated for both near-term and advanced performance potential. The power system options investigated for the Mission Modules include photovoltaics, solar thermal, nuclear reactor, and isotope power systems. Options discussed for Mars Bases include the above options with the addition of a brief discussion of open loop energy conversion of Mars resources, including utilization of wind, subsurface thermal gradients, and super oxides. Electrical power requirements for Mission Modules were estimated for three basic approaches: as a function of crew size; as a function of electric propulsion; and as a function of transmission of power from an orbiter to the surface of Mars via laser or radio frequency. Mars Base power requirements were assumed to be determined by production facilities that make resources available for follow-on missions leading to the establishment of a permanently manned Base. Requirements include the production of buffer gas and propellant production plants.

Electrical power systems for Mars

NASA Astrophysics Data System (ADS)

Giudici, Robert J.

1986-05-01

Electrical power system options for Mars Manned Modules and Mars Surface Bases were evaluated for both near-term and advanced performance potential. The power system options investigated for the Mission Modules include photovoltaics, solar thermal, nuclear reactor, and isotope power systems. Options discussed for Mars Bases include the above options with the addition of a brief discussion of open loop energy conversion of Mars resources, including utilization of wind, subsurface thermal gradients, and super oxides. Electrical power requirements for Mission Modules were estimated for three basic approaches: as a function of crew size; as a function of electric propulsion; and as a function of transmission of power from an orbiter to the surface of Mars via laser or radio frequency. Mars Base power requirements were assumed to be determined by production facilities that make resources available for follow-on missions leading to the establishment of a permanently manned Base. Requirements include the production of buffer gas and propellant production plants.

Experimental Test Concept for a Cargo Data Interchange System (CARDIS) : Volume 1. Text.

DOT National Transportation Integrated Search

1976-05-01

This report includes the recommended CARDIS experimental test system functional capabilities. It identifies the CARDIS functions that are inherent to an information exchange capability and optional systems which are required by the transportation rel...

Experimental Test Concept for a Cargo Data Interchange System (CARDIS) : Volume 2. Appendixes.

DOT National Transportation Integrated Search

1976-05-01

This report includes the recommended CARDIS experimental test system functional capabilities. It identifies the CARDIS functions that are inherent to an information exchange capability and optional systems which are required by the transportation rel...

Advanced Software Techniques for Data Management Systems. Volume 2: Space Shuttle Flight Executive System: Functional Design

NASA Technical Reports Server (NTRS)

Pepe, J. T.

1972-01-01

A functional design of software executive system for the space shuttle avionics computer is presented. Three primary functions of the executive are emphasized in the design: task management, I/O management, and configuration management. The executive system organization is based on the applications software and configuration requirements established during the Phase B definition of the Space Shuttle program. Although the primary features of the executive system architecture were derived from Phase B requirements, it was specified for implementation with the IBM 4 Pi EP aerospace computer and is expected to be incorporated into a breadboard data management computer system at NASA Manned Spacecraft Center's Information system division. The executive system was structured for internal operation on the IBM 4 Pi EP system with its external configuration and applications software assumed to the characteristic of the centralized quad-redundant avionics systems defined in Phase B.

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis

PubMed Central

Miller, Matthew James; McGuire, Kerry M.; Feigh, Karen M.

2016-01-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity. The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design. PMID:28491008

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis.

PubMed

Miller, Matthew James; McGuire, Kerry M; Feigh, Karen M

2017-06-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity . The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design.

Parametric Cost Analysis: A Design Function

NASA Technical Reports Server (NTRS)

Dean, Edwin B.

1989-01-01

Parametric cost analysis uses equations to map measurable system attributes into cost. The measures of the system attributes are called metrics. The equations are called cost estimating relationships (CER's), and are obtained by the analysis of cost and technical metric data of products analogous to those to be estimated. Examples of system metrics include mass, power, failure_rate, mean_time_to_repair, energy _consumed, payload_to_orbit, pointing_accuracy, manufacturing_complexity, number_of_fasteners, and percent_of_electronics_weight. The basic assumption is that a measurable relationship exists between system attributes and the cost of the system. If a function exists, the attributes are cost drivers. Candidates for metrics include system requirement metrics and engineering process metrics. Requirements are constraints on the engineering process. From optimization theory we know that any active constraint generates cost by not permitting full optimization of the objective. Thus, requirements are cost drivers. Engineering processes reflect a projection of the requirements onto the corporate culture, engineering technology, and system technology. Engineering processes are an indirect measure of the requirements and, hence, are cost drivers.

Digital Avionics Information System (DAIS): Training Requirements Analysis Model Users Guide. Final Report.

ERIC Educational Resources Information Center

Czuchry, Andrew J.; And Others

This user's guide describes the functions, logical operations and subroutines, input data requirements, and available outputs of the Training Requirements Analysis Model (TRAMOD), a computerized analytical life cycle cost modeling system for use in the early stages of system design. Operable in a stand-alone mode, TRAMOD can be used for the…

High-level requirements for the US-75 integrated corridor in Dallas, Texas

DOT National Transportation Integrated Search

2008-04-30

This document is intended as a listing and discussion of the high-level Requirements for the US-75 Integrated Corridor Management System (ICMS) in Dallas. This document describes what the system is to do (the functional requirements), how well it is ...

System Engineering Analysis For Improved Scout Business Information Systems

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

Van Slyke, D. A.

The project uses system engineering principles to address the need of Boy Scout leaders for an integrated system to facilitate advancement and awards records, leader training and planning for meetings and activities. Existing products to address needs of Scout leaders and relevant stakeholders function to support record keeping and some communication functions but opportunity exists for a better system to fully integrate these functions with training delivery and recording, activity planning along with feedback and information gathering from stakeholders. Key stakeholders for the sytem include Scouts and their families, leaders, training providers, sellers of supplies and awards, content generators andmore » facilities that serve Scout activities. Key performance parameters for the system are protection of personal information, availability of current information, information accuracy and information content that has depth. Implementation concepts considered for the system include (1) owned and operated by Boy Scouts of America, (2) Contracted out to a vendor (3) distributed system that functions with BSA managed interfaces. The selected concept is to contract out to a vendor to maximize the likelihood of successful integration and take advantage of the best technology. Development of requirements considers three key use cases (1) System facilitates planning a hike with training needed satisfied in advance and advancement recording real time (2) Scheduling and documenting in-person training, (3) Family interested in Scouting receives information and can request follow-up. Non-functional requirements are analyzed with the Quality Function Deployment tool. Requirement addressing frequency of backup, compatibility with legacy and new technology, language support, software update are developed to address system reliability and intuitive interface. System functions analyzed include update of activity database, maintenance of advancement status, archive of documents, and monitoring of content that is accessible. The study examines risks associated with information security, technological change and continued popularity of Scouting. Mitigation is based on system functions that are defined. The approach to developing an improved system for facilitating Boy Scout leader functions was iterative with insights into capabilities coming in the course of working through the used cases and sequence diagrams.« less

Requirements Engineering for inter-organizational health information systems with functions for spatial analyses: modeling a WHO safe community applying Use Case Maps.

PubMed

Olvingson, C; Hallberg, N; Timpka, T; Lindqvist, K

2002-01-01

To evaluate Use Case Maps (UCMs) as a technique for Requirements Engineering (RE) in the development of information systems with functions for spatial analyses in inter-organizational public health settings. In this study, Participatory Action Research (PAR) is used to explore the UCM notation for requirements elicitation and to gather the opinions of the users. The Delphi technique is used to reach consensus in the construction of UCMs. The results show that UCMs can provide a visualization of the system's functionality and in combination with PAR provide a sound basis for gathering requirements in inter-organizational settings. UCMs were found to represent a suitable level for describing the organization and the dynamic flux of information including spatial resolution to all stakeholders. Moreover, by using PAR, the voices of the users and their tacit knowledge is intercepted. Further, UCMs are found useful in generating intuitive requirements by the creation of use cases. With UCMs and PAR it is possible to study the effects of design changes in the general information display and the spatial resolution in the same context. Both requirements on the information system in general and the functions for spatial analyses are possible to elicit when identifying the different responsibilities and the demands on spatial resolution associated to the actions of each administrative unit. However, the development process of UCM is not well documented and needs further investigation and formulation of guidelines.

An expert system prototype for aiding in the development of software functional requirements for NASA Goddard's command management system: A case study and lessons learned

NASA Technical Reports Server (NTRS)

Liebowitz, Jay

1986-01-01

At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.

Energy Emergency Management Information System (EEMIS): Functional requirements

NASA Astrophysics Data System (ADS)

1980-10-01

These guidelines state that in order to create the widest practicable competition, the system's requirements, with few exceptions, must be expressed in functional terms without reference to specific hardware or software products, and that wherever exceptions are made a statement of justification must be provided. In addition, these guidelines set forth a recommended maximum threshold limit of annual contract value for schedule contract procurements.

33 CFR 157.12f - Workshop functional test requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... CARRYING OIL IN BULK Design, Equipment, and Installation § 157.12f Workshop functional test requirements. (a) Each oil content meter and each control section of a monitoring system must be subjected to a... protocol must be received with each unit delivered. (b) A functional test conducted on an oil content meter...

33 CFR 157.12f - Workshop functional test requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... CARRYING OIL IN BULK Design, Equipment, and Installation § 157.12f Workshop functional test requirements. (a) Each oil content meter and each control section of a monitoring system must be subjected to a... protocol must be received with each unit delivered. (b) A functional test conducted on an oil content meter...

33 CFR 157.12f - Workshop functional test requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... CARRYING OIL IN BULK Design, Equipment, and Installation § 157.12f Workshop functional test requirements. (a) Each oil content meter and each control section of a monitoring system must be subjected to a... protocol must be received with each unit delivered. (b) A functional test conducted on an oil content meter...

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

Bull, Diana L.; Costello, Ronan; Babarit, Aurelien

Capabilities and functions are hierarchical structures (i.e. taxonomies) that are used in a systems engineering framework to identify complimentary requirements for the system: what the system must do to achieve what it must be. In the case of capabilities, the taxonomy embodies the list of characteristics that are desired, from the perspective of the stakeholders, for the system to be successful. In terms of the functions, the hierarchy represents the solution agnostic (i.e. independent of specific design embodiments) elements that are needed to meet the stakeholder requirements. This paper will focus on the development of the functions. The functions definemore » the fundamental elements of the solution that must be provided in order to achieve the mission and deliver the capabilities. They identify the behaviors the farm must possess, i.e. the farm must be able to generate and deliver electricity from wave power. High-level functions are independent of the technology or design used to implement the function. However, detailed functions may begin to border on specific design choices. Hence a strong effort has been made to maintain functions that are design agnostic.« less

CCA Test Objectives

NASA Technical Reports Server (NTRS)

2005-01-01

Three sources have been considered to provide information allowing the evaluation of the Collision Conflict Avoidance (CCA) functional requirements: existing data, simulation, and flight test. The existing data sources that have been evaluated have been found to be lacking in two areas: The actual data that was recorded and missing elements to the system architecture. Many previous tests addressing collision avoidance were conducted without a remote operator. As such, they are missing critical elements that are required to assess the CCA functional requirements. Tests such as ERAST were conducted with all of the UAS elements. However, ERAST tests were conducted as a demonstration and the data recorded was of end-to-end performance. Many contributing elements of the system were not individually recorded or were recorded at a data rate insufficient for the purposes of evaluating the CCA functional requirements.

High-Throughput Cloning and Expression Library Creation for Functional Proteomics

PubMed Central

Festa, Fernanda; Steel, Jason; Bian, Xiaofang; Labaer, Joshua

2013-01-01

The study of protein function usually requires the use of a cloned version of the gene for protein expression and functional assays. This strategy is particular important when the information available regarding function is limited. The functional characterization of the thousands of newly identified proteins revealed by genomics requires faster methods than traditional single gene experiments, creating the need for fast, flexible and reliable cloning systems. These collections of open reading frame (ORF) clones can be coupled with high-throughput proteomics platforms, such as protein microarrays and cell-based assays, to answer biological questions. In this tutorial we provide the background for DNA cloning, discuss the major high-throughput cloning systems (Gateway® Technology, Flexi® Vector Systems, and Creator™ DNA Cloning System) and compare them side-by-side. We also report an example of high-throughput cloning study and its application in functional proteomics. This Tutorial is part of the International Proteomics Tutorial Programme (IPTP12). Details can be found at http://www.proteomicstutorials.org. PMID:23457047

High-throughput cloning and expression library creation for functional proteomics.

PubMed

Festa, Fernanda; Steel, Jason; Bian, Xiaofang; Labaer, Joshua

2013-05-01

The study of protein function usually requires the use of a cloned version of the gene for protein expression and functional assays. This strategy is particularly important when the information available regarding function is limited. The functional characterization of the thousands of newly identified proteins revealed by genomics requires faster methods than traditional single-gene experiments, creating the need for fast, flexible, and reliable cloning systems. These collections of ORF clones can be coupled with high-throughput proteomics platforms, such as protein microarrays and cell-based assays, to answer biological questions. In this tutorial, we provide the background for DNA cloning, discuss the major high-throughput cloning systems (Gateway® Technology, Flexi® Vector Systems, and Creator(TM) DNA Cloning System) and compare them side-by-side. We also report an example of high-throughput cloning study and its application in functional proteomics. This tutorial is part of the International Proteomics Tutorial Programme (IPTP12). © 2013 WILEY-VCH Verlag GmbH & Co. KGaA, Weinheim.

Functional requirements for the man-vehicle systems research facility. [identifying and correcting human errors during flight simulation

NASA Technical Reports Server (NTRS)

Clement, W. F.; Allen, R. W.; Heffley, R. K.; Jewell, W. F.; Jex, H. R.; Mcruer, D. T.; Schulman, T. M.; Stapleford, R. L.

1980-01-01

The NASA Ames Research Center proposed a man-vehicle systems research facility to support flight simulation studies which are needed for identifying and correcting the sources of human error associated with current and future air carrier operations. The organization of research facility is reviewed and functional requirements and related priorities for the facility are recommended based on a review of potentially critical operational scenarios. Requirements are included for the experimenter's simulation control and data acquisition functions, as well as for the visual field, motion, sound, computation, crew station, and intercommunications subsystems. The related issues of functional fidelity and level of simulation are addressed, and specific criteria for quantitative assessment of various aspects of fidelity are offered. Recommendations for facility integration, checkout, and staffing are included.

An example of requirements for Advanced Subsonic Civil Transport (ASCT) flight control system using structured techniques

NASA Technical Reports Server (NTRS)

Mclees, Robert E.; Cohen, Gerald C.

1991-01-01

The requirements are presented for an Advanced Subsonic Civil Transport (ASCT) flight control system generated using structured techniques. The requirements definition starts from initially performing a mission analysis to identify the high level control system requirements and functions necessary to satisfy the mission flight. The result of the study is an example set of control system requirements partially represented using a derivative of Yourdon's structured techniques. Also provided is a research focus for studying structured design methodologies and in particular design-for-validation philosophies.

Requirements Analysis Study for Master Pump Shutdown System Project Development Specification [SEC 1 and 2

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

BEVINS, R.R.

This document has been updated during the definitive design portion of the first phase of the W-314 Project to capture additional software requirements and is planned to be updated during the second phase of the W-314 Project to cover the second phase of the Project's scope. The objective is to provide requirement traceability by recording the analysis/basis for the functional descriptions of the master pump shutdown system. This document identifies the sources of the requirements and/or how these were derived. Each requirement is validated either by quoting the source or an analysis process involving the required functionality, performance characteristics, operationsmore » input or engineering judgment.« less

Ecology and Biogenesis of Functional Amyloids in Pseudomonas.

PubMed

Rouse, Sarah L; Matthews, Stephen J; Dueholm, Morten S

2018-05-16

Functional amyloids can be found in the extracellular matrix produced by many bacteria during biofilm growth. They mediate the initial attachment of bacteria to surfaces and provide stability and functionality to mature biofilms. Efficient amyloid biogenesis requires a highly coordinated system of amyloid subunits, molecular chaperones and transport systems. The functional amyloid of Pseudomonas (Fap) represents such a system. Here, we review the phylogenetic diversification of the Fap system, its potential ecological role and the dedicated machinery required for Fap biogenesis, with a particular focus on the amyloid exporter FapF, the structure of which has been recently resolved. We also present a sequence covariance-based in silico model of the FapC fiber-forming subunit. Finally, we highlight key questions that remain unanswered and we believe deserve further attention by the scientific community. Copyright © 2018. Published by Elsevier Ltd.

33 CFR 96.240 - What functional requirements must a safety management system meet?

Code of Federal Regulations, 2010 CFR

2010-07-01

... a safety management system meet? 96.240 Section 96.240 Navigation and Navigable Waters COAST GUARD, DEPARTMENT OF HOMELAND SECURITY VESSEL OPERATING REGULATIONS RULES FOR THE SAFE OPERATION OF VESSELS AND SAFETY MANAGEMENT SYSTEMS Company and Vessel Safety Management Systems § 96.240 What functional...

Evaluation of expert systems - An approach and case study. [of determining software functional requirements for command management of satellites

NASA Technical Reports Server (NTRS)

Liebowitz, J.

1985-01-01

Techniques that were applied in defining an expert system prototype for first-cut evaluations of the software functional requirements of NASA satellite command management activities are described. The prototype was developed using the Knowledge Engineering System. Criteria were selected for evaluating the satellite software before defining the expert system prototype. Application of the prototype system is illustrated in terms of the evaluation procedures used with the COBE satellite to be launched in 1988. The limited number of options which can be considered by the program mandates that biases in the system output must be well understood by the users.

Partitioning in Avionics Architectures: Requirements, Mechanisms, and Assurance

NASA Technical Reports Server (NTRS)

Rushby, John

1999-01-01

Automated aircraft control has traditionally been divided into distinct "functions" that are implemented separately (e.g., autopilot, autothrottle, flight management); each function has its own fault-tolerant computer system, and dependencies among different functions are generally limited to the exchange of sensor and control data. A by-product of this "federated" architecture is that faults are strongly contained within the computer system of the function where they occur and cannot readily propagate to affect the operation of other functions. More modern avionics architectures contemplate supporting multiple functions on a single, shared, fault-tolerant computer system where natural fault containment boundaries are less sharply defined. Partitioning uses appropriate hardware and software mechanisms to restore strong fault containment to such integrated architectures. This report examines the requirements for partitioning, mechanisms for their realization, and issues in providing assurance for partitioning. Because partitioning shares some concerns with computer security, security models are reviewed and compared with the concerns of partitioning.

Requirements Analysis Study for Master Pump Shutdown System Project Development Specification [SEC 1 and 2

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

BEVINS, R.R.

This study is a requirements document that presents analysis for the functional description for the master pump shutdown system. This document identifies the sources of the requirements and/or how these were derived. Each requirement is validated either by quoting the source or an analysis process involving the required functionality, performance characteristics, operations input or engineering judgment. The requirements in this study apply to the first phase of the W314 Project. This document has been updated during the definitive design portion of the first phase of the W314 Project to capture additional software requirements and is planned to be updated duringmore » the second phase of the W314 Project to cover the second phase of the project's scope.« less

HSI top-down requirements analysis for ship manpower reduction

NASA Astrophysics Data System (ADS)

Malone, Thomas B.; Bost, J. R.

2000-11-01

U.S. Navy ship acquisition programs such as DD 21 and CVNX are increasingly relying on top down requirements analysis (TDRA) to define and assess design approaches for workload and manpower reduction, and for ensuring required levels of human performance, reliability, safety, and quality of life at sea. The human systems integration (HSI) approach to TDRA begins with a function analysis which identifies the functions derived from the requirements in the Operational Requirements Document (ORD). The function analysis serves as the function baseline for the ship, and also supports the definition of RDT&E and Total Ownership Cost requirements. A mission analysis is then conducted to identify mission scenarios, again based on requirements in the ORD, and the Design Reference Mission (DRM). This is followed by a mission/function analysis which establishes the function requirements to successfully perform the ship's missions. Function requirements of major importance for HSI are information, performance, decision, and support requirements associated with each function. An allocation of functions defines the roles of humans and automation in performing the functions associated with a mission. Alternate design concepts, based on function allocation strategies, are then described, and task networks associated with the concepts are developed. Task network simulations are conducted to assess workloads and human performance capabilities associated with alternate concepts. An assessment of the affordability and risk associated with alternate concepts is performed, and manning estimates are developed for feasible design concepts.

Design requirements and development of an airborne descent path definition algorithm for time navigation

NASA Technical Reports Server (NTRS)

Izumi, K. H.; Thompson, J. L.; Groce, J. L.; Schwab, R. W.

1986-01-01

The design requirements for a 4D path definition algorithm are described. These requirements were developed for the NASA ATOPS as an extension of the Local Flow Management/Profile Descent algorithm. They specify the processing flow, functional and data architectures, and system input requirements, and recommended the addition of a broad path revision (reinitialization) function capability. The document also summarizes algorithm design enhancements and the implementation status of the algorithm on an in-house PDP-11/70 computer. Finally, the requirements for the pilot-computer interfaces, the lateral path processor, and guidance and steering function are described.

Performance prediction evaluation of ceramic materials in point-focusing solar receivers

NASA Technical Reports Server (NTRS)

Ewing, J.; Zwissler, J.

1979-01-01

A performance prediction was adapted to evaluate the use of ceramic materials in solar receivers for point focusing distributed applications. System requirements were determined including the receiver operating environment and system operating parameters for various engine types. Preliminary receiver designs were evolved from these system requirements. Specific receiver designs were then evaluated to determine material functional requirements.

Adaptive structures for precision controlled large space systems

NASA Technical Reports Server (NTRS)

Garba, John A.; Wada, Ben K.; Fanson, James L.

1991-01-01

The stringent accuracy and ground test validation requirements of some of the future space missions will require new approaches in structural design. Adaptive structures, structural systems that can vary their geometric congiguration as well as their physical properties, are primary candidates for meeting the functional requirements for such missions. Research performed in the development of such adaptive structural systems is described.

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.

System analysis study of space platform and station accommodations for life sciences research facilities. Volume 2: Study results. Appendix D: Life sciences research facility requirements

NASA Technical Reports Server (NTRS)

Wiley, Lowell F.

1985-01-01

The purpose of this requirements document is to develop the foundation for concept development for the Life Sciences Research Facility (LSRF) on the Space Station. These requirements are developed from the perspective of a Space Station laboratory module outfitter. Science and mission requirements including those related to specimens are set forth. System requirements, including those for support, are detailed. Functional and design requirements are covered in the areas of structures, mechanisms, electrical power, thermal systems, data management system, life support, and habitability. Finally, interface requirements for the Command Module and Logistics Module are described.

NASA-6 atmospheric measuring station. [calibration, functional checks, and operation of measuring instruments

NASA Technical Reports Server (NTRS)

1973-01-01

Information required to calibrate, functionally check, and operate the Instrumentation Branch equipment on the NASA-6 aircraft is provided. All procedures required for preflight checks and in-flight operation of the NASA-6 atmospheric measuring station are given. The calibration section is intended for only that portion of the system maintained and calibrated by IN-MSD-12 Systems Operation contractor personnel. Maintenance is not included.

Intent inferencing with a model-based operator's associate

NASA Technical Reports Server (NTRS)

Jones, Patricia M.; Mitchell, Christine M.; Rubin, Kenneth S.

1989-01-01

A portion of the Operator Function Model Expert System (OFMspert) research project is described. OFMspert is an architecture for an intelligent operator's associate or assistant that can aid the human operator of a complex, dynamic system. Intelligent aiding requires both understanding and control. The understanding (i.e., intent inferencing) ability of the operator's associate is discussed. Understanding or intent inferencing requires a model of the human operator; the usefulness of an intelligent aid depends directly on the fidelity and completeness of its underlying model. The model chosen for this research is the operator function model (OFM). The OFM represents operator functions, subfunctions, tasks, and actions as a heterarchic-hierarchic network of finite state automata, where the arcs in the network are system triggering events. The OFM provides the structure for intent inferencing in that operator functions and subfunctions correspond to likely operator goals and plans. A blackboard system similar to that of Human Associative Processor (HASP) is proposed as the implementation of intent inferencing function. This system postulates operator intentions based on current system state and attempts to interpret observed operator actions in light of these hypothesized intentions.

Research on Capturing of Customer Requirements Based on Innovation Theory

NASA Astrophysics Data System (ADS)

junwu, Ding; dongtao, Yang; zhenqiang, Bao

To exactly and effectively capture customer requirements information, a new customer requirements capturing modeling method was proposed. Based on the analysis of function requirement models of previous products and the application of technology system evolution laws of the Theory of Innovative Problem Solving (TRIZ), the customer requirements could be evolved from existing product designs, through modifying the functional requirement unit and confirming the direction of evolution design. Finally, a case study was provided to illustrate the feasibility of the proposed approach.

Application of digital computer APU modeling techniques to control system design.

NASA Technical Reports Server (NTRS)

Bailey, D. A.; Burriss, W. L.

1973-01-01

Study of the required controls for a H2-O2 auxiliary power unit (APU) technology program for the Space Shuttle. A steady-state system digital computer program was prepared and used to optimize initial system design. Analytical models of each system component were included. The program was used to solve a nineteen-dimensional problem, and then time-dependent differential equations were added to the computer program to simulate transient APU system and control. Some system parameters were considered quasi-steady-state, and others were treated as differential variables. The dynamic control analysis proceeded from initial ideal control modeling (which considered one control function and assumed the others to be ideal), stepwise through the system (adding control functions), until all of the control functions and their interactions were considered. In this way, the adequacy of the final control design over the required wide range of APU operating conditions was established.

Design of agricultural product quality safety retrospective supervision system of Jiangsu province

NASA Astrophysics Data System (ADS)

Wang, Kun

2017-08-01

In store and supermarkets to consumers can trace back agricultural products through the electronic province card to query their origin, planting, processing, packaging, testing and other important information and found that the problems. Quality and safety issues can identify the responsibility of the problem. This paper designs a retroactive supervision system for the quality and safety of agricultural products in Jiangsu Province. Based on the analysis of agricultural production and business process, the goal of Jiangsu agricultural product quality safety traceability system construction is established, and the specific functional requirements and non-functioning requirements of the retroactive system are analyzed, and the target is specified for the specific construction of the retroactive system. The design of the quality and safety traceability system in Jiangsu province contains the design of the overall design, the trace code design and the system function module.

48 CFR 570.302 - Description of requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... the lease. (2) Functional, performance, or physical requirements. (3) Any special requirements. (4... requirements. 570.302 Section 570.302 Federal Acquisition Regulations System GENERAL SERVICES ADMINISTRATION... Leasehold Interests in Real Property 570.302 Description of requirements. (a) The description of...

18 CFR 301.7 - Average System Cost methodology functionalization.

Code of Federal Regulations, 2010 CFR

2010-04-01

... SYSTEM COST METHODOLOGY FOR SALES FROM UTILITIES TO BONNEVILLE POWER ADMINISTRATION UNDER NORTHWEST POWER... functionalization under its Direct Analysis assigns costs, revenues, debits or credits based upon the actual and/or...) Functionalization methods. (1) Direct analysis, if allowed or required by Table 1, assigns costs, revenues, debits...

10 CFR 50.36 - Technical specifications.

Code of Federal Regulations, 2010 CFR

2010-01-01

..., or component that is part of the primary success path and which functions or actuates to mitigate a... significant safety functions. Where a limiting safety system setting is specified for a variable on which a... the automatic safety system does not function as required, the licensee shall take appropriate action...

Detailed requirements document for the Interactive Financial Management System (IFMS), volume 1

NASA Technical Reports Server (NTRS)

Dodson, D. B.

1975-01-01

The detailed requirements for phase 1 (online fund control, subauthorization accounting, and accounts receivable functional capabilities) of the Interactive Financial Management System (IFMS) are described. This includes information on the following: systems requirements, performance requirements, test requirements, and production implementation. Most of the work is centered on systems requirements, and includes discussions on the following processes: resources authority, allotment, primary work authorization, reimbursable order acceptance, purchase request, obligation, cost accrual, cost distribution, disbursement, subauthorization performance, travel, accounts receivable, payroll, property, edit table maintenance, end-of-year, backup input. Other subjects covered include: external systems interfaces, general inquiries, general report requirements, communication requirements, and miscellaneous. Subjects covered under performance requirements include: response time, processing volumes, system reliability, and accuracy. Under test requirements come test data sources, general test approach, and acceptance criteria. Under production implementation come data base establishment, operational stages, and operational requirements.

Integrated Application of Active Controls (IAAC) technology to an advanced subsonic transport project: Current and advanced act control system definition study

NASA Technical Reports Server (NTRS)

1982-01-01

The Current and Advanced Technology ACT control system definition tasks of the Integrated Application of Active Controls (IAAC) Technology project within the Energy Efficient Transport Program are summarized. The systems mechanize six active control functions: (1) pitch augmented stability; (2) angle of attack limiting; (3) lateral/directional augmented stability; (4) gust load alleviation; (5) maneuver load control; and (6) flutter mode control. The redundant digital control systems meet all function requirements with required reliability and declining weight and cost as advanced technology is introduced.

Exploring the Use of Model-Based Systems Engineering (MBSE) to Develop Systems Architectures in Naval Ship Design

DTIC Science & Technology

2010-06-01

data such as the NSMB B-series, or be based on hydrodynamic (lifting line) predict ions. The power including still air drag and any margin that is...Provide Fuel Function 3.6 Fuel Oil System Component REQ.1.4 Fuel Efficiency Requirement 1.1 Generate Mechanical En... Function 1.1 Prime Mover Component...3.3 Provide Lubrication Function 3.7 Lube Oil System Component 3.4 Provide Cooling Water Function 3.3 Cooling System Component 3.5 Provide Combust ion

General purpose free floating platform for KC-135 flight experimentation

NASA Technical Reports Server (NTRS)

Borchers, Bruce A.; Yendler, Boris S.; Kliss, Mark H.; Gonzales, Andrew A.; Edwards, Mark T.

1994-01-01

The Controlled Ecological Life Support Systems (CELSS) program is evaluating higher plants as a means of providing life support functions aboard space craft. These plant systems will be capable of regenerating air and water while meeting some of the food requirements of the crew. In order to grow plants in space, a series of systems are required to provide the necessary plant support functions. Some of the systems required for CELSS experiments are such that is is likely that existing technologies will require refinement, or novel technologies will need to be developed. To evaluate and test these technologies, a series of KC-135 precursor flights are being proposed. A general purpose free floating experiment platform is being developed to allow the KC-135 flights to be used to their fullest. This paper will outline the basic design for the CELSS Free Floating Test Bed (FFTB), and the requirements for the individual subsystems. Several preliminary experiments suitable for the free floater will also be discussed.

Rotorcraft digital advanced avionics system (RODAAS) functional description

NASA Technical Reports Server (NTRS)

Peterson, E. M.; Bailey, J.; Mcmanus, T. J.

1985-01-01

A functional design of a rotorcraft digital advanced avionics system (RODAAS) to transfer the technology developed for general aviation in the Demonstration Advanced Avionics System (DAAS) program to rotorcraft operation was undertaken. The objective was to develop an integrated avionics system design that enhances rotorcraft single pilot IFR operations without increasing the required pilot training/experience by exploiting advanced technology in computers, busing, displays and integrated systems design. A key element of the avionics system is the functionally distributed architecture that has the potential for high reliability with low weight, power and cost. A functional description of the RODAAS hardware and software functions is presented.

Mark 4A antenna control system data handling architecture study

NASA Technical Reports Server (NTRS)

Briggs, H. C.; Eldred, D. B.

1991-01-01

A high-level review was conducted to provide an analysis of the existing architecture used to handle data and implement control algorithms for NASA's Deep Space Network (DSN) antennas and to make system-level recommendations for improving this architecture so that the DSN antennas can support the ever-tightening requirements of the next decade and beyond. It was found that the existing system is seriously overloaded, with processor utilization approaching 100 percent. A number of factors contribute to this overloading, including dated hardware, inefficient software, and a message-passing strategy that depends on serial connections between machines. At the same time, the system has shortcomings and idiosyncrasies that require extensive human intervention. A custom operating system kernel and an obscure programming language exacerbate the problems and should be modernized. A new architecture is presented that addresses these and other issues. Key features of the new architecture include a simplified message passing hierarchy that utilizes a high-speed local area network, redesign of particular processing function algorithms, consolidation of functions, and implementation of the architecture in modern hardware and software using mainstream computer languages and operating systems. The system would also allow incremental hardware improvements as better and faster hardware for such systems becomes available, and costs could potentially be low enough that redundancy would be provided economically. Such a system could support DSN requirements for the foreseeable future, though thorough consideration must be given to hard computational requirements, porting existing software functionality to the new system, and issues of fault tolerance and recovery.

Earth Observatory Satellite system definition study. Report 5: System design and specifications. Volume 5: Specification for EROS operations control center

NASA Technical Reports Server (NTRS)

1974-01-01

The functional, performance, and design requirements for the Operations Control Center (OCC) of the Earth Observatory Satellite (EOS) system are presented. The OCC controls the operations of the EOS satellite to acquire mission data consisting of: (1) thematic mapper data, (2) multispectral scanner data on EOS-A, or High Resolution Pointable Imager data on EOS-B, and (3) data collection system (DCS) data. The various inputs to the OCC are identified. The functional requirements of the OCC are defined. The specific systems and subsystems of the OCC are described and block diagrams are provided.

Study of solid rocket motor for space shuttle booster, volume 2, book 3, appendix A

NASA Technical Reports Server (NTRS)

1972-01-01

A systems requirements analysis for the solid propellant rocket engine to be used with the space shuttle was conducted. The systems analysis was developed to define the physical and functional requirements for the systems and subsystems. The operations analysis was performed to identify the requirements of the various launch operations, mission operations, ground operations, and logistic and flight support concepts.

The Avian Proghrelin System

USDA-ARS?s Scientific Manuscript database

To understand how the proghrelin system functions in regulating growth hormone release and food intake as well as defining its pleiotropic roles in such diverse physiological processes as energy homeostasis, gastrointestinal tract function and reproduction requires detailed knowledge of the structur...

AESOP- INTERACTIVE DESIGN OF LINEAR QUADRATIC REGULATORS AND KALMAN FILTERS

NASA Technical Reports Server (NTRS)

Lehtinen, B.

1994-01-01

AESOP was developed to solve a number of problems associated with the design of controls and state estimators for linear time-invariant systems. The systems considered are modeled in state-variable form by a set of linear differential and algebraic equations with constant coefficients. Two key problems solved by AESOP are the linear quadratic regulator (LQR) design problem and the steady-state Kalman filter design problem. AESOP is designed to be used in an interactive manner. The user can solve design problems and analyze the solutions in a single interactive session. Both numerical and graphical information are available to the user during the session. The AESOP program is structured around a list of predefined functions. Each function performs a single computation associated with control, estimation, or system response determination. AESOP contains over sixty functions and permits the easy inclusion of user defined functions. The user accesses these functions either by inputting a list of desired functions in the order they are to be performed, or by specifying a single function to be performed. The latter case is used when the choice of function and function order depends on the results of previous functions. The available AESOP functions are divided into several general areas including: 1) program control, 2) matrix input and revision, 3) matrix formation, 4) open-loop system analysis, 5) frequency response, 6) transient response, 7) transient function zeros, 8) LQR and Kalman filter design, 9) eigenvalues and eigenvectors, 10) covariances, and 11) user-defined functions. The most important functions are those that design linear quadratic regulators and Kalman filters. The user interacts with AESOP when using these functions by inputting design weighting parameters and by viewing displays of designed system response. Support functions obtain system transient and frequency responses, transfer functions, and covariance matrices. AESOP can also provide the user with open-loop system information including stability, controllability, and observability. The AESOP program is written in FORTRAN IV for interactive execution and has been implemented on an IBM 3033 computer using TSS 370. As currently configured, AESOP has a central memory requirement of approximately 2 Megs of 8 bit bytes. Memory requirements can be reduced by redimensioning arrays in the AESOP program. Graphical output requires adaptation of the AESOP plot routines to whatever device is available. The AESOP program was developed in 1984.

Design of a recumbent seating system

NASA Technical Reports Server (NTRS)

Croyle, Scott; Delarosa, Jose; George, Daren; Hinkle, Cathy; Karas, Stephen

1993-01-01

Future space shuttle missions presented by NASA might require the shuttle to rendezvous with the Russian space station Mir for the purpose of transporting astronauts back to earth. Due to the atrophied state of these astronauts, a special seating system must be designed for their transportation. The main functions of this seating system are to support and restrain the astronauts during normal reentry flight and to dampen some of the loading that might occur in a crash situation. Through research, the design team developed many concept variants for these functional requirements. By evaluating each variant, the concepts were eliminated until the four most attractive designs remained. The team used a decision matrix to determine the best concept to carry through embodiment. This concept involved using struts for support during reentry flight and a spring damper/shock absorber system to dampen crash landing loads. The embodiment design process consisted of defining the layout of each of the main functional components, specifically, the seat structure and the strut structure. Through the use of MCS/pal two, the design was refined until it could handle all required loads and dampen to the forces specified. The auxiliary function carriers were then considered. Following the design of these components, the complete final layout could be determined. It is concluded that the final design meets all specifications outlined in the conceptual design. The main advantages of this design are its low weight, simplicity, and large amount of function sharing between different components. The disassembly of this design could potentially present a problem because of time and size constraints involved. Overall, this design meets or exceeds all functional requirements.

FBI fingerprint identification automation study. AIDS 3 evaluation report. Volume 3: Operational feasibility

NASA Technical Reports Server (NTRS)

Mulhall, B. D. L.

1980-01-01

An evaluation is presented which is defined as the adequacy of system design with known functional and performance requirements. The proposed Rockwell International AIDS 3 card, document and data flow are presented to summarize the concepts involved and the relationships between functions. The analysis and evaluation includes a study of system capability, processing rates, search requirements and response accuracy as well as a consideration of operational components and hardware integration. Results indicate that the AIDS 3 System concept is operationally feasible if production capacity is slightly enhanced but that operational complexity, hardware integration and a lack of conceptual data pertinent to some of the functions are areas of concern.

Ground Systems Development Environment (GSDE) interface requirements analysis: Operations scenarios

NASA Technical Reports Server (NTRS)

Church, Victor E.; Phillips, John

1991-01-01

This report is a preliminary assessment of the functional and data interface requirements to the link between the GSDE GS/SPF (Amdahl) and the Space Station Control Center (SSCC) and Space Station Training Facility (SSTF) Integration, Verification, and Test Environments (IVTE's). These interfaces will be involved in ground software development of both the control center and the simulation and training systems. Our understanding of the configuration management (CM) interface and the expected functional characteristics of the Amdahl-IVTE interface is described. A set of assumptions and questions that need to be considered and resolved in order to complete the interface functional and data requirements definitions are presented. A listing of information items defined to describe software configuration items in the GSDE CM system is included. It also includes listings of standard reports of CM information and of CM-related tools in the GSDE.

Space shuttle propulsion systems on-board checkout and monitoring system development study (extension). Volume 2: Guidelines for for incorporation of the onboard checkout and monitoring function on the space shuttle

NASA Technical Reports Server (NTRS)

1972-01-01

Guidelines are presented for incorporation of the onboard checkout and monitoring function (OCMF) into the designs of the space shuttle propulsion systems. The guidelines consist of and identify supporting documentation; requirements for formulation, implementation, and integration of OCMF; associated compliance verification techniques and requirements; and OCMF terminology and nomenclature. The guidelines are directly applicable to the incorporation of OCMF into the design of space shuttle propulsion systems and the equipment with which the propulsion systems interface. The techniques and general approach, however, are also generally applicable to OCMF incorporation into the design of other space shuttle systems.

The evaluation and extension of TAE in the development of a user interface management system

NASA Technical Reports Server (NTRS)

Burkhart, Brenda; Sugar, Ross

1986-01-01

The development of a user interface management system (UIMS) for an information gathering and display system is discussed. The system interface requirements are outlined along with the UIMS functional characteristics. Those systems requirements which are supported by the current Transportable Applications Executive (TAE) are listed and necessary modifications to the TAE are described.

Space Transportation System Availability Relationships to Life Cycle Cost

NASA Technical Reports Server (NTRS)

Rhodes, Russel E.; Donahue, Benjamin B.; Chen, Timothy T.

2009-01-01

Future space transportation architectures and designs must be affordable. Consequently, their Life Cycle Cost (LCC) must be controlled. For the LCC to be controlled, it is necessary to identify all the requirements and elements of the architecture at the beginning of the concept phase. Controlling LCC requires the establishment of the major operational cost drivers. Two of these major cost drivers are reliability and maintainability, in other words, the system's availability (responsiveness). Potential reasons that may drive the inherent availability requirement are the need to control the number of unique parts and the spare parts required to support the transportation system's operation. For more typical space transportation systems used to place satellites in space, the productivity of the system will drive the launch cost. This system productivity is the resultant output of the system availability. Availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. Since many operational factors cannot be projected early in the definition phase, the focus will be on inherent availability which is equal to the mean time between a failure (MTBF) divided by the MTBF plus the mean time to repair (MTTR) the system. The MTBF is a function of reliability or the expected frequency of failures. When the system experiences failures the result is added operational flow time, parts consumption, and increased labor with an impact to responsiveness resulting in increased LCC. The other function of availability is the MTTR, or maintainability. In other words, how accessible is the failed hardware that requires replacement and what operational functions are required before and after change-out to make the system operable. This paper will describe how the MTTR can be equated to additional labor, additional operational flow time, and additional structural access capability, all of which drive up the LCC. A methodology will be presented that provides the decision makers with the understanding necessary to place constraints on the design definition. This methodology for the major drivers will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system. This methodology will focus on the achievement of an affordable, responsive space transportation system. It is the intent of this paper to not only provide the visibility of the relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability, but also to provide the capability to bound the variables, thus providing the insight required to control the system's engineering solution. An example of this visibility is the need to provide integration of similar discipline functions to allow control of the total parts count of the space transportation system. Also, selecting a reliability requirement will place a constraint on parts count to achieve a given inherent availability requirement, or require accepting a larger parts count with the resulting higher individual part reliability requirements. This paper will provide an understanding of the relationship of mean repair time (mean downtime) to maintainability (accessibility for repair), and both mean time between failure (reliability of hardware) and the system inherent availability.

Space station functional relationships analysis

NASA Technical Reports Server (NTRS)

Tullis, Thomas S.; Bied, Barbra R.

1988-01-01

A systems engineering process is developed to assist Space Station designers to understand the underlying operational system of the facility so that it can be physically arranged and configured to support crew productivity. The study analyzes the operational system proposed for the Space Station in terms of mission functions, crew activities, and functional relationships in order to develop a quantitative model for evaluation of interior layouts, configuration, and traffic analysis for any Station configuration. Development of the model involved identification of crew functions, required support equipment, criteria of assessing functional relationships, and tools for analyzing functional relationship matrices, as well as analyses of crew transition frequency, sequential dependencies, support equipment requirements, potential for noise interference, need for privacy, and overall compatability of functions. The model can be used for analyzing crew functions for the Initial Operating Capability of the Station and for detecting relationships among these functions. Note: This process (FRA) was used during Phase B design studies to test optional layouts of the Space Station habitat module. The process is now being automated as a computer model for use in layout testing of the Space Station laboratory modules during Phase C.

Orbital transfer vehicle concept definition and system analysis study. Volume 2: OTV concept definition and evaluation. Book 1: Mission and system requirements

NASA Technical Reports Server (NTRS)

Kofal, Allen E.

1987-01-01

The mission and system requirements for the concept definition and system analysis of the Orbital Transfer Vehicle (OTV) are established. The requirements set forth constitute the single authority for the selection, evaluation, and optimization of the technical performance and design of the OTV. This requirements document forms the basis for the Ground and Space Based OTV concept definition analyses and establishes the physical, functional, performance and design relationships to STS, Space Station, Orbital Maneuvering Vehicle (OMV), and payloads.

PDSS/IMC requirements and functional specifications

NASA Technical Reports Server (NTRS)

1983-01-01

The system (software and hardware) requirements for the Payload Development Support System (PDSS)/Image Motion Compensator (IMC) are provided. The PDSS/IMC system provides the capability for performing Image Motion Compensator Electronics (IMCE) flight software test, checkout, and verification and provides the capability for monitoring the IMC flight computer system during qualification testing for fault detection and fault isolation.

Software Safety Risk in Legacy Safety-Critical Computer Systems

NASA Technical Reports Server (NTRS)

Hill, Janice L.; Baggs, Rhoda

2007-01-01

Safety Standards contain technical and process-oriented safety requirements. Technical requirements are those such as "must work" and "must not work" functions in the system. Process-Oriented requirements are software engineering and safety management process requirements. Address the system perspective and some cover just software in the system > NASA-STD-8719.13B Software Safety Standard is the current standard of interest. NASA programs/projects will have their own set of safety requirements derived from the standard. Safety Cases: a) Documented demonstration that a system complies with the specified safety requirements. b) Evidence is gathered on the integrity of the system and put forward as an argued case. [Gardener (ed.)] c) Problems occur when trying to meet safety standards, and thus make retrospective safety cases, in legacy safety-critical computer systems.

Purple L1 Milestone Review Panel GPFS Functionality and Performance

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

Loewe, W E

2006-12-01

The GPFS deliverable for the Purple system requires the functionality and performance necessary for ASC I/O needs. The functionality includes POSIX and MPIIO compatibility, and multi-TB file capability across the entire machine. The bandwidth performance required is 122.15 GB/s, as necessary for productive and defensive I/O requirements, and the metadata performance requirement is 5,000 file stats per second. To determine success for this deliverable, several tools are employed. For functionality testing of POSIX, 10TB-files, and high-node-count capability, the parallel file system bandwidth performance test IOR is used. IOR is an MPI-coordinated application that can write and then read to amore » single shared file or to an individual file per process and check the data integrity of the file(s). The MPIIO functionality is tested with the MPIIO test suite from the MPICH library. Bandwidth performance is tested using IOR for the required 122.15 GB/s sustained write. All IOR tests are performanced with data checking enabled. Metadata performance is tested after ''aging'' the file system with 80% data block usage and 20% inode usage. The fdtree metadata test is expected to create/remove a large directory/file structure in under 20 minutes time, akin to interactive metadata usage. Multiple (10) instances of ''ls -lR'', each performing over 100K stats, are run concurrently in different large directories to demonstrate 5,000 stats/sec.« less

Functions and requirements for tank farm restoration and safe operations, Project W-314. Revision 3

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

Garrison, R.C.

1995-02-01

This Functions and Requirements document (FRD) establishes the basic performance criteria for Project W-314, in accordance with the guidance outlined in the letter from R.W. Brown, RL, to President, WHC, ``Tank Waste Remediation System (TWRS) Project Documentation Methodology,`` 94-PRJ-018, dated 3/18/94. The FRD replaces the Functional Design Criteria (FDC) as the project technical baseline documentation. Project W-314 will improve the reliability of safety related systems, minimize onsite health and safety hazards, and support waste retrieval and disposal activities by restoring and/or upgrading existing Tank Farm facilities and systems. The scope of Project W-314 encompasses the necessary restoration upgrades of themore » Tank Farms` instrumentation, ventilation, electrical distribution, and waste transfer systems.« less

Computer program for design and performance analysis of navigation-aid power systems. Program documentation. Volume 1: Software requirements document

NASA Technical Reports Server (NTRS)

Goltz, G.; Kaiser, L. M.; Weiner, H.

1977-01-01

A computer program has been developed for designing and analyzing the performance of solar array/battery power systems for the U.S. Coast Guard Navigational Aids. This program is called the Design Synthesis/Performance Analysis (DSPA) Computer Program. The basic function of the Design Synthesis portion of the DSPA program is to evaluate functional and economic criteria to provide specifications for viable solar array/battery power systems. The basic function of the Performance Analysis portion of the DSPA program is to simulate the operation of solar array/battery power systems under specific loads and environmental conditions. This document establishes the software requirements for the DSPA computer program, discusses the processing that occurs within the program, and defines the necessary interfaces for operation.

Minimal support technology and in situ resource utilization for risk management of planetary spaceflight missions

NASA Astrophysics Data System (ADS)

Murphy, K. L.; Rygalov, V. Ye.; Johnson, S. B.

2009-04-01

All artificial systems and components in space degrade at higher rates than on Earth, depending in part on environmental conditions, design approach, assembly technologies, and the materials used. This degradation involves not only the hardware and software systems but the humans that interact with those systems. All technological functions and systems can be expressed through functional dependence: [Function]˜[ERU]∗[RUIS]∗[ISR]/[DR];where [ERU]efficiency (rate) of environmental resource utilization[RUIS]resource utilization infrastructure[ISR]in situ resources[DR]degradation rateThe limited resources of spaceflight and open space for autonomous missions require a high reliability (maximum possible, approaching 100%) for system functioning and operation, and must minimize the rate of any system degradation. To date, only a continuous human presence with a system in the spaceflight environment can absolutely mitigate those degradations. This mitigation is based on environmental amelioration for both the technology systems, as repair of data and spare parts, and the humans, as exercise and psychological support. Such maintenance now requires huge infrastructures, including research and development complexes and management agencies, which currently cannot move beyond the Earth. When considering what is required to move manned spaceflight from near Earth stations to remote locations such as Mars, what are the minimal technologies and infrastructures necessary for autonomous restoration of a degrading system in space? In all of the known system factors of a mission to Mars that reduce the mass load, increase the reliability, and reduce the mission’s overall risk, the current common denominator is the use of undeveloped or untested technologies. None of the technologies required to significantly reduce the risk for critical systems are currently available at acceptable readiness levels. Long term interplanetary missions require that space programs produce a craft with all systems integrated so that they are of the highest reliability. Right now, with current technologies, we cannot guarantee this reliability for a crew of six for 1000 days to Mars and back. Investigation of the technologies to answer this need and a focus of resources and research on their advancement would significantly improve chances for a safe and successful mission.

Electrical power systems for Space Station

NASA Technical Reports Server (NTRS)

Simon, W. E.

1984-01-01

Major challenges in power system development are described. Evolutionary growth, operational lifetime, and other design requirements are discussed. A pictorial view of weight-optimized power system applications shows which systems are best for missions of various lengths and required power level. Following definition of the major elements of the electrical power system, an overview of element options and a brief technology assessment are presented. Selected trade-study results show end-to-end system efficiencies, required photovoltaic power capability as a function of energy storage system efficiency, and comparisons with other systems such as a solar dynamic power system.

On a useful functional representation of control system structure

NASA Technical Reports Server (NTRS)

Malchow, Harvey L.

1988-01-01

An alternative structure for control systems is proposed. The structure is represented by a three-element block diagram and three functional definitions. It is argued that the three functional elements form a canonical set. The set includes the functions description, estimation and control. General overlay of the structure on parallel state and nested-state control systems is discussed. Breakdown of two real nested-state control systems into the proposed functional format is displayed. Application of the process to the mapping of complex control systems R and D efforts is explained with the Mars Rover Sample and Return mission as an example. A previous application of this basic functional structure to Space Station performance requirements organization is discussed.

Present, future of automotive hybrid IC applications discussed

NASA Astrophysics Data System (ADS)

Matsuda, Nobuyoshi; Fukuoka, Atuhisa

1987-09-01

Hybrid ICs are presently utilized in various fields such as commercial televisions, VTRs, and audio devices, industrial usage of communication equipment, computers, terminals, and automobiles. Its applications and environments are various and diverse. The functions required for hybrid ICs vary from simple high density mounting for a system to the realization of high mechanisms with the application of function timing. The functions are properly used depending upon the system with its hybrid ICs and its circuit composition. Considering structure and reliability requirements for automotive hybrid ICs, an application example for hybrid ICs which use the package (COMPACT), will be discussed.

Enviromnental Control and Life Support Systems for Mars Missions - Issues and Concerns for Planetary Protection

NASA Technical Reports Server (NTRS)

Barta, Daniel J.; Anderson, Molly S.; Lange, Kevin

2015-01-01

Planetary protection represents an additional set of requirements that generally have not been considered by developers of technologies for Environmental Control and Life Support Systems (ECLSS). Planetary protection guidelines will affect the kind of operations, processes, and functions that can take place during future human planetary exploration missions. Ultimately, there will be an effect on mission costs, including the mission trade space when planetary protection requirements begin to drive vehicle deisgn in a concrete way. Planetary protection requirements need to be considered early in technology development and mission programs in order to estimate these impacts and push back on requirements or find efficient ways to perform necessary functions. It is expected that planetary protection will be a significant factor during technology selection and system architecture design for future missions.

NTP comparison process

NASA Technical Reports Server (NTRS)

Corban, Robert

1993-01-01

The systems engineering process for the concept definition phase of the program involves requirements definition, system definition, and consistent concept definition. The requirements definition process involves obtaining a complete understanding of the system requirements based on customer needs, mission scenarios, and nuclear thermal propulsion (NTP) operating characteristics. A system functional analysis is performed to provide a comprehensive traceability and verification of top-level requirements down to detailed system specifications and provides significant insight into the measures of system effectiveness to be utilized in system evaluation. The second key element in the process is the definition of system concepts to meet the requirements. This part of the process involves engine system and reactor contractor teams to develop alternative NTP system concepts that can be evaluated against specific attributes, as well as a reference configuration against which to compare system benefits and merits. Quality function deployment (QFD), as an excellent tool within Total Quality Management (TQM) techniques, can provide the required structure and provide a link to the voice of the customer in establishing critical system qualities and their relationships. The third element of the process is the consistent performance comparison. The comparison process involves validating developed concept data and quantifying system merits through analysis, computer modeling, simulation, and rapid prototyping of the proposed high risk NTP subsystems. The maximum amount possible of quantitative data will be developed and/or validated to be utilized in the QFD evaluation matrix. If upon evaluation of a new concept or its associated subsystems determine to have substantial merit, those features will be incorporated into the reference configuration for subsequent system definition and comparison efforts.

Procurement Without Problems: Preparing the RFP.

ERIC Educational Resources Information Center

Epstein, Susan Baerg

1983-01-01

Discussion of factors contributing to successful procurement of automated library system focuses on preparation of Request for Proposal (RFP) and elements included in the RFP--administrative requirements, functional requirements, performance requirements, reliability requirements, testing procedures, standardized response language, location table,…

Generic functional requirements for a NASA general-purpose data base management system

NASA Technical Reports Server (NTRS)

Lohman, G. M.

1981-01-01

Generic functional requirements for a general-purpose, multi-mission data base management system (DBMS) for application to remotely sensed scientific data bases are detailed. The motivation for utilizing DBMS technology in this environment is explained. The major requirements include: (1) a DBMS for scientific observational data; (2) a multi-mission capability; (3) user-friendly; (4) extensive and integrated information about data; (5) robust languages for defining data structures and formats; (6) scientific data types and structures; (7) flexible physical access mechanisms; (8) ways of representing spatial relationships; (9) a high level nonprocedural interactive query and data manipulation language; (10) data base maintenance utilities; (11) high rate input/output and large data volume storage; and adaptability to a distributed data base and/or data base machine configuration. Detailed functions are specified in a top-down hierarchic fashion. Implementation, performance, and support requirements are also given.

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.

Analysis and preliminary design of Kunming land use and planning management information system

NASA Astrophysics Data System (ADS)

Li, Li; Chen, Zhenjie

2007-06-01

This article analyzes Kunming land use planning and management information system from the system building objectives and system building requirements aspects, nails down the system's users, functional requirements and construction requirements. On these bases, the three-tier system architecture based on C/S and B/S is defined: the user interface layer, the business logic layer and the data services layer. According to requirements for the construction of land use planning and management information database derived from standards of the Ministry of Land and Resources and the construction program of the Golden Land Project, this paper divides system databases into planning document database, planning implementation database, working map database and system maintenance database. In the design of the system interface, this paper uses various methods and data formats for data transmission and sharing between upper and lower levels. According to the system analysis results, main modules of the system are designed as follows: planning data management, the planning and annual plan preparation and control function, day-to-day planning management, planning revision management, decision-making support, thematic inquiry statistics, planning public participation and so on; besides that, the system realization technologies are discussed from the system operation mode, development platform and other aspects.

Evaluation Methodologies for Information Management Systems; Building Digital Tobacco Industry Document Libraries at the University of California, San Francisco Library/Center for Knowledge Management; Experiments with the IFLA Functional Requirements for Bibliographic Records (FRBR); Coming to Term: Designing the Texas Email Repository Model.

ERIC Educational Resources Information Center

Morse, Emile L.; Schmidt, Heidi; Butter, Karen; Rider, Cynthia; Hickey, Thomas B.; O'Neill, Edward T.; Toves, Jenny; Green, Marlan; Soy, Sue; Gunn, Stan; Galloway, Patricia

2002-01-01

Includes four articles that discuss evaluation methods for information management systems under the Defense Advanced Research Projects Agency; building digital libraries at the University of California San Francisco's Tobacco Control Archives; IFLA's Functional Requirements for Bibliographic Records; and designing the Texas email repository model…

Requirements for implementation of Kuessner and Wagner indicial lift growth functions into the FLEXSTAB computer program system for use in dynamic loads analyses

NASA Technical Reports Server (NTRS)

Miller, R. D.; Rogers, J. T.

1975-01-01

General requirements for dynamic loads analyses are described. The indicial lift growth function unsteady subsonic aerodynamic representation is reviewed, and the FLEXSTAB CPS is evaluated with respect to these general requirements. The effects of residual flexibility techniques on dynamic loads analyses are also evaluated using a simple dynamic model.

Prototype development and demonstration for response, emergency staging, communications, uniform management, and evacuation (R.E.S.C.U.M.E.) : R.E.S.C.U.M.E. final functional and performance requirements.

DOT National Transportation Integrated Search

2014-01-01

This document provides the high-level functional and performance requirements for the Prototype Development and Demonstration of a R.E.S.C.U.M.E. system. The requirements included in this document are based upon those that can be found in previous R....

Multifunction Data Link for an Advanced Air-Traffic Management System

DOT National Transportation Integrated Search

1972-11-01

This report evaluates the requirements relating to a multi-function data link for an advanced Air Traffic Management System. A two-way time ordered data link is postulated to accomplish the communication and control function. Several candidate modula...

A Functional Model of Quality Assurance for Psychiatric Hospitals and Corresponding Staffing Requirements.

ERIC Educational Resources Information Center

Kamis-Gould, Edna; And Others

1991-01-01

A model for quality assurance (QA) in psychiatric hospitals is described. Its functions (general QA, utilization review, clinical records, evaluation, management information systems, risk management, and infection control), subfunctions, and corresponding staffing requirements are reviewed. This model was designed to foster standardization in QA…

Inertial subsystem functional and design requirements for the orbiter (Phase B extension baseline)

NASA Technical Reports Server (NTRS)

Flanders, J. H.; Green, J. P., Jr.

1972-01-01

The design requirements use the Phase B extension baseline system definition. This means that a GNC computer is specified for all command control functions instead of a central computer communicating with the ISS through a databus. Forced air cooling is used instead of cold plate cooling.

Earth Observing System/Advanced Microwave Sounding Unit-A (EOS/AMSU-A): Firmware Requirements

NASA Technical Reports Server (NTRS)

Schwantje, Robert

1995-01-01

This Firmware Requirements Document specifies the functional, performance, and interface requirements of the firmware. It also specifies the major characteristics, implementation constraints, and design goals of the firmware.

Control system and method for a power delivery system having a continuously variable ratio transmission

DOEpatents

Frank, Andrew A.

1984-01-01

A control system and method for a power delivery system, such as in an automotive vehicle, having an engine coupled to a continuously variable ratio transmission (CVT). Totally independent control of engine and transmission enable the engine to precisely follow a desired operating characteristic, such as the ideal operating line for minimum fuel consumption. CVT ratio is controlled as a function of commanded power or torque and measured load, while engine fuel requirements (e.g., throttle position) are strictly a function of measured engine speed. Fuel requirements are therefore precisely adjusted in accordance with the ideal characteristic for any load placed on the engine.

Lasercom system architecture with reduced complexity

NASA Technical Reports Server (NTRS)

Lesh, James R. (Inventor); Chen, Chien-Chung (Inventor); Ansari, Homayoon (Inventor)

1994-01-01

Spatial acquisition and precision beam pointing functions are critical to spaceborne laser communication systems. In the present invention, a single high bandwidth CCD detector is used to perform both spatial acquisition and tracking functions. Compared to previous lasercom hardware design, the array tracking concept offers reduced system complexity by reducing the number of optical elements in the design. Specifically, the design requires only one detector and one beam steering mechanism. It also provides the means to optically close the point-ahead control loop. The technology required for high bandwidth array tracking was examined and shown to be consistent with current state of the art. The single detector design can lead to a significantly reduced system complexity and a lower system cost.

LaserCom System Architecture With Reduced Complexity

NASA Technical Reports Server (NTRS)

Lesh, James R. (Inventor); Chen, Chien-Chung (Inventor); Ansari, Homa-Yoon (Inventor)

1996-01-01

Spatial acquisition and precision beam pointing functions are critical to spaceborne laser communication systems. In the present invention a single high bandwidth CCD detector is used to perform both spatial acquisition and tracking functions. Compared to previous lasercom hardware design, the array tracking concept offers reduced system complexity by reducing the number of optical elements in the design. Specifically, the design requires only one detector and one beam steering mechanism. It also provides means to optically close the point-ahead control loop. The technology required for high bandwidth array tracking was examined and shown to be consistent with current state of the art. The single detector design can lead to a significantly reduced system complexity and a lower system cost.

Integrated command, control, communications and computation system functional architecture

NASA Technical Reports Server (NTRS)

Cooley, C. G.; Gilbert, L. E.

1981-01-01

The functional architecture for an integrated command, control, communications, and computation system applicable to the command and control portion of the NASA End-to-End Data. System is described including the downlink data processing and analysis functions required to support the uplink processes. The functional architecture is composed of four elements: (1) the functional hierarchy which provides the decomposition and allocation of the command and control functions to the system elements; (2) the key system features which summarize the major system capabilities; (3) the operational activity threads which illustrate the interrelationahip between the system elements; and (4) the interfaces which illustrate those elements that originate or generate data and those elements that use the data. The interfaces also provide a description of the data and the data utilization and access techniques.

Specification and testing for power by wire aircraft

NASA Technical Reports Server (NTRS)

Hansen, Irving G.; Kenney, Barbara H.

1993-01-01

A power by wire aircraft is one in which all active functions other than propulsion are implemented electrically. Other nomenclature are 'all electric airplane,' or 'more electric airplane.' What is involved is the task of developing and certifying electrical equipment to replace existing hydraulics and pneumatics. When such functions, however, are primary flight controls which are implemented electrically, new requirements are imposed that were not anticipated by existing power system designs. Standards of particular impact are the requirements of ultra-high reliability, high peak transient bi-directional power flow, and immunity to electromagnetic interference and lightning. Not only must the electromagnetic immunity of the total system be verifiable, but box level tests and meaningful system models must be established to allow system evaluation. This paper discusses some of the problems, the system modifications involved, and early results in establishing wiring harness and interface susceptibility requirements.

Suit study - The impact of VMS in subsystem integration

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

Hill, B.; Watts, R.

1992-02-01

One of the thrusts of the Wright Laboratory/FIVE-sponsored Subsystem Integration Technology (SUIT) study is to investigate the impact of emerging vehicle management system (VMS) concepts on subsystem integration. This paper summarizes the issues relating to VMS/subsystem integration as examined during the Northrop SUIT study. Projected future weapon system requirements are identified and their impact on VMS and subsystem design interpreted. Integrated VMS/subsystem control and management functions are proposed. A candidate system VMS architecture satisfying the aforementioned weapon system requirements and providing the identified control and management functions is proposed. This architecture is used, together with the environmental control system, asmore » an illustrative subsystem example, to address the risks associated with the design, development, procurement, integration and testing of integrated VMS/subsystem concepts. The conclusion is that the development process requires an airframer to adopt the role of subsystem integrator, the consequences of which are discussed. 2 refs.« less

Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 2: Concept document

NASA Technical Reports Server (NTRS)

1989-01-01

The Simulation Computer System (SCS) concept document describes and establishes requirements for the functional performance of the SCS system, including interface, logistic, and qualification requirements. The SCS is the computational communications and display segment of the Marshall Space Flight Center (MSFC) Payload Training Complex (PTC). The PTC is the MSFC facility that will train onboard and ground operations personnel to operate the payloads and experiments on board the international Space Station Freedom. The requirements to be satisfied by the system implementation are identified here. The SCS concept document defines the requirements to be satisfied through the implementation of the system capability. The information provides the operational basis for defining the requirements to be allocated to the system components and enables the system organization to assess whether or not the completed system complies with the requirements of the system.

Architecture for a PACS primary diagnosis workstation

NASA Astrophysics Data System (ADS)

Shastri, Kaushal; Moran, Byron

1990-08-01

A major factor in determining the overall utility of a medical Picture Archiving and Communications (PACS) system is the functionality of the diagnostic workstation. Meyer-Ebrecht and Wendler [1] have proposed a modular picture computer architecture with high throughput and Perry et.al [2] have defined performance requirements for radiology workstations. In order to be clinically useful, a primary diagnosis workstation must not only provide functions of current viewing systems (e.g. mechanical alternators [3,4]) such as acceptable image quality, simultaneous viewing of multiple images, and rapid switching of image banks; but must also provide a diagnostic advantage over the current systems. This includes window-level functions on any image, simultaneous display of multi-modality images, rapid image manipulation, image processing, dynamic image display (cine), electronic image archival, hardcopy generation, image acquisition, network support, and an easy user interface. Implementation of such a workstation requires an underlying hardware architecture which provides high speed image transfer channels, local storage facilities, and image processing functions. This paper describes the hardware architecture of the Siemens Diagnostic Reporting Console (DRC) which meets these requirements.

NAS Requirements Checklist for Job Queuing/Scheduling Software

NASA Technical Reports Server (NTRS)

Jones, James Patton

1996-01-01

The increasing reliability of parallel systems and clusters of computers has resulted in these systems becoming more attractive for true production workloads. Today, the primary obstacle to production use of clusters of computers is the lack of a functional and robust Job Management System for parallel applications. This document provides a checklist of NAS requirements for job queuing and scheduling in order to make most efficient use of parallel systems and clusters for parallel applications. Future requirements are also identified to assist software vendors with design planning.

Space shuttle/food system study. Volume 2, appendix E: Alternate flight systems analysis

NASA Technical Reports Server (NTRS)

1974-01-01

The functional requirements of stowage, preparation, serving, consumption, and cleanup were applied to each of the five food mixes selected for study in terms of the overall design of the space shuttle food system. The analysis led to a definition of performance requirements for each food mix, along with a definition of equipment to meet those requirements. Weight and volume data for all five systems, in terms of food and packaging, support equipment, and galley installation penalties, are presented.

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

NASA Technical Reports Server (NTRS)

Rhodes, Russel E.; Adams, TImothy C.

2008-01-01

It is essential that management and engineering understand the need for an availability requirement for the customer's space transportation system as it enables the meeting of his needs, goal, and objectives. There are three types of availability, e.g., operational availability, achieved availability, or inherent availability. The basic definition of availability is equal to the mean uptime divided by the sum of the mean uptime plus the mean downtime. The major difference is the inclusiveness of the functions within the mean downtime and the mean uptime. This paper will address tIe inherent availability which only addresses the mean downtime as that mean time to repair or the time to determine the failed article, remove it, install a replacement article and verify the functionality of the repaired system. The definitions of operational availability include the replacement hardware supply or maintenance delays and other non-design factors in the mean downtime. Also with inherent availability the mean uptime will only consider the mean time between failures (other availability definitions consider this as mean time between maintenance - preventive and corrective maintenance) that requires the repair of the system to be functional. It is also essential that management and engineering understand all influencing attributes relationships to each other and to the resultant inherent availability requirement. This visibility will provide the decision makers with the understanding necessary to place constraints on the design definition for the major drivers that will determine the inherent availability, safety, reliability, maintainability, and the life cycle cost of the fielded system provided the customer. This inherent availability requirement may be driven by the need to use a multiple launch approach to placing humans on the moon or the desire to control the number of spare parts required to support long stays in either orbit or on the surface of the moon or mars. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability, but also provide the capability to bound the variables providing engineering the insight required to control the system's engineering solution. An example of this visibility will be the need to provide integration of similar discipline functions to allow control of the total parts count of the space transportation system. Also the relationship visibility of selecting a reliability requirement will place a constraint on parts count to achieve a given inherent availability requirement or accepting a larger parts count with the resulting higher reliability requirement. This paper will provide an understanding for the relationship of mean repair time (mean downtime) to maintainability, e.g., accessibility for repair, and both mean time between failure, e.g., reliability of hardware and the system inherent availability. Having an understanding of these relationships and resulting requirements before starting the architectural design concept definition will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Cognitive Functioning in Space Exploration Missions: A Human Requirement

NASA Technical Reports Server (NTRS)

Fiedler, Edan; Woolford, Barbara

2005-01-01

Solving cognitive issues in the exploration missions will require implementing results from both Human Behavior and Performance, and Space Human Factors Engineering. Operational and research cognitive requirements need to reflect a coordinated management approach with appropriate oversight and guidance from NASA headquarters. First, this paper will discuss one proposed management method that would combine the resources of Space Medicine and Space Human Factors Engineering at JSC, other NASA agencies, the National Space Biomedical Research Institute, Wyle Labs, and other academic or industrial partners. The proposed management is based on a Human Centered Design that advocates full acceptance of the human as a system equal to other systems. Like other systems, the human is a system with many subsystems, each of which has strengths and limitations. Second, this paper will suggest ways to inform exploration policy about what is needed for optimal cognitive functioning of the astronaut crew, as well as requirements to ensure necessary assessment and intervention strategies for the human system if human limitations are reached. Assessment strategies will include clinical evaluation and fitness-to-perform evaluations. Clinical intervention tools and procedures will be available to the astronaut and space flight physician. Cognitive performance will be supported through systematic function allocation, task design, training, and scheduling. Human factors requirements and guidelines will lead to well-designed information displays and retrieval systems that reduce crew time and errors. Means of capturing process, design, and operational requirements to ensure crew performance will be discussed. Third, this paper will describe the current plan of action, and future challenges to be resolved before a lunar or Mars expedition. The presentation will include a proposed management plan for research, involvement of various organizations, and a timetable of deliverables.

Space Suit Portable Life Support System (PLSS) 2.0 Pre-Installation Acceptance (PIA) Testing

NASA Technical Reports Server (NTRS)

Watts, Carly; Vogel, Matthew

2016-01-01

Following successful completion of the space suit Portable Life Support System (PLSS) 1.0 development and testing in 2011, the second system-level prototype, PLSS 2.0, was developed in 2012 to continue the maturation of the advanced PLSS design which is intended to reduce consumables, improve reliability and robustness, and incorporate additional sensing and functional capabilities over the current Space Shuttle/International Space Station Extravehicular Mobility Unit (EMU) PLSS. PLSS 2.0 represents the first attempt at a packaged design comprising first generation or later component prototypes and medium fidelity interfaces within a flight-like representative volume. Pre-Installation Acceptance (PIA) is carryover terminology from the Space Shuttle Program referring to the series of test sequences used to verify functionality of the EMU PLSS prior to installation into the Space Shuttle airlock for launch. As applied to the PLSS 2.0 development and testing effort, PIA testing designated the series of 27 independent test sequences devised to verify component and subsystem functionality, perform in situ instrument calibrations, generate mapping data to define set-points for control algorithms, evaluate hardware performance against advanced PLSS design requirements, and provide quantitative and qualitative feedback on evolving design requirements and performance specifications. PLSS 2.0 PIA testing was carried out from 3/20/13 - 3/15/14 using a variety of test configurations to perform test sequences that ranged from stand-alone component testing to system-level testing, with evaluations becoming increasingly integrated as the test series progressed. Each of the 27 test sequences was vetted independently, with verification of basic functionality required before completion. Because PLSS 2.0 design requirements were evolving concurrently with PLSS 2.0 PIA testing, the requirements were used as guidelines to assess performance during the tests; after the completion of PIA testing, test data served to improve the fidelity and maturity of design requirements as well as plans for future advanced PLSS functional testing.

Space Suit Portable Life Support System (PLSS) 2.0 Pre-Installation Acceptance (PIA) Testing

NASA Technical Reports Server (NTRS)

Anchondo, Ian; Cox, Marlon; Meginnis, Carly; Westheimer, David; Vogel, Matt R.

2016-01-01

Following successful completion of the space suit Portable Life Support System (PLSS) 1.0 development and testing in 2011, the second system-level prototype, PLSS 2.0, was developed in 2012 to continue the maturation of the advanced PLSS design. This advanced PLSS is intended to reduce consumables, improve reliability and robustness, and incorporate additional sensing and functional capabilities over the current Space Shuttle/International Space Station Extravehicular Mobility Unit (EMU) PLSS. PLSS 2.0 represents the first attempt at a packaged design comprising first generation or later component prototypes and medium fidelity interfaces within a flight-like representative volume. Pre-Installation Acceptance (PIA) is carryover terminology from the Space Shuttle Program referring to the series of test sequences used to verify functionality of the EMU PLSS prior to installation into the Space Shuttle airlock for launch. As applied to the PLSS 2.0 development and testing effort, PIA testing designated the series of 27 independent test sequences devised to verify component and subsystem functionality, perform in situ instrument calibrations, generate mapping data, define set-points, evaluate control algorithms, evaluate hardware performance against advanced PLSS design requirements, and provide quantitative and qualitative feedback on evolving design requirements and performance specifications. PLSS 2.0 PIA testing was carried out in 2013 and 2014 using a variety of test configurations to perform test sequences that ranged from stand-alone component testing to system-level testing, with evaluations becoming increasingly integrated as the test series progressed. Each of the 27 test sequences was vetted independently, with verification of basic functionality required before completion. Because PLSS 2.0 design requirements were evolving concurrently with PLSS 2.0 PIA testing, the requirements were used as guidelines to assess performance during the tests; after the completion of PIA testing, test data served to improve the fidelity and maturity of design requirements as well as plans for future advanced PLSS functional testing.

Comparison on Human Resource Requirement between Manual and Automated Dispensing Systems.

PubMed

Noparatayaporn, Prapaporn; Sakulbumrungsil, Rungpetch; Thaweethamcharoen, Tanita; Sangseenil, Wunwisa

2017-05-01

This study was conducted to compare human resource requirement among manual, automated, and modified automated dispensing systems. Data were collected from the pharmacy department at the 2100-bed university hospital (Siriraj Hospital, Bangkok, Thailand). Data regarding the duration of the medication distribution process were collected by using self-reported forms for 1 month. The data on the automated dispensing machine (ADM) system were obtained from 1 piloted inpatient ward, whereas those on the manual system were the average of other wards. Data on dispensing, returned unused medication, and stock management processes under the traditional manual system and the ADM system were from actual activities, whereas the modified ADM system was modeled. The full-time equivalent (FTE) of each model was estimated for comparison. The result showed that the manual system required 46.84 FTEs of pharmacists and 132.66 FTEs of pharmacy technicians. By adding pharmacist roles on screening and verification under the ADM system, the ADM system required 117.61 FTEs of pharmacists. Replacing counting and filling medication functions by ADM has decreased the number of pharmacy technicians to 55.38 FTEs. After the modified ADM system canceled the return unused medication process, FTEs requirement for pharmacists and pharmacy technicians decreased to 69.78 and 51.90 FTEs, respectively. The ADM system decreased the workload of pharmacy technicians, whereas it required more time from pharmacists. However, the increased workload of pharmacists was associated with more comprehensive patient care functions, which resulted from the redesigned work process. Copyright © 2017. Published by Elsevier Inc.

Space Generic Open Avionics Architecture (SGOAA) standard specification

NASA Technical Reports Server (NTRS)

Wray, Richard B.; Stovall, John R.

1994-01-01

This standard establishes the Space Generic Open Avionics Architecture (SGOAA). The SGOAA includes a generic functional model, processing structural model, and an architecture interface model. This standard defines the requirements for applying these models to the development of spacecraft core avionics systems. The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture models to the design of a specific avionics hardware/software processing system. This standard defines a generic set of system interface points to facilitate identification of critical services and interfaces. It establishes the requirement for applying appropriate low level detailed implementation standards to those interfaces points. The generic core avionics functions and processing structural models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

Technology readiness assessment of advanced space engine integrated controls and health monitoring

NASA Technical Reports Server (NTRS)

Millis, Marc G.

1991-01-01

An evaluation is given for an integrated control and health monitoring system (ICHM) system that is designed to be used with hydrogen-oxygen rocket engines. The minimum required ICHM functions, system elements, technology readiness, and system cost are assessed for a system which permits the operation of H-O engines that are space-based, reusable, and descent throttleable. Based on the evaluation of the H-O ICHM, it is estimated that the minimum system requirements for demonstration on an engine system testbed will require an investment of 30 to 45 million dollars over six years.

Goal-Function Tree Modeling for Systems Engineering and Fault Management

NASA Technical Reports Server (NTRS)

Patterson, Jonathan D.; Johnson, Stephen B.

2013-01-01

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM). This methodology and corresponding model, known as a Goal-Function Tree (GFT), provides a means to represent, decompose, and elaborate system goals and functions in a rigorous manner that connects directly to design through use of state variables that translate natural language requirements and goals into logical-physical state language. The state variable-based approach also provides the means to directly connect FM to the design, by specifying the range in which state variables must be controlled to achieve goals, and conversely, the failures that exist if system behavior go out-of-range. This in turn allows for the systems engineers and SHM/FM engineers to determine which state variables to monitor, and what action(s) to take should the system fail to achieve that goal. In sum, the GFT representation provides a unified approach to early-phase SE and FM development. This representation and methodology has been successfully developed and implemented using Systems Modeling Language (SysML) on the NASA Space Launch System (SLS) Program. It enabled early design trade studies of failure detection coverage to ensure complete detection coverage of all crew-threatening failures. The representation maps directly both to FM algorithm designs, and to failure scenario definitions needed for design analysis and testing. The GFT representation provided the basis for mapping of abort triggers into scenarios, both needed for initial, and successful quantitative analyses of abort effectiveness (detection and response to crew-threatening events).

Future space transportation systems analysis study. Phase 1 extension: Transportation systems reference data, volume 2

NASA Technical Reports Server (NTRS)

1975-01-01

Transportation mass requirements are developed for various mission and transportation modes based on vehicle systems sized to fit the exact needs of each mission. The parametric data used to derive the mass requirements for each mission and transportation mode are presented to enable accommodation of possible changes in mode options or payload definitions. The vehicle sizing and functional requirements used to derive the parametric data are described.

HALE UAS Command and Control Communications: Step 1 - Functional Requirements Document. Version 4.0

NASA Technical Reports Server (NTRS)

2006-01-01

The High Altitude Long Endurance (HALE) unmanned aircraft system (UAS) communicates with an off-board pilot-in-command in all flight phases via the C2 data link, making it a critical component for the UA to fly in the NAS safely and routinely. This is a new requirement in current FAA communications planning and monitoring processes. This document provides a set of comprehensive C2 communications functional requirements and performance guidelines to help facilitate the future FAA certification process for civil UAS to operate in the NAS. The objective of the guidelines is to provide the ability to validate the functional requirements and in future be used to develop performance-level requirements.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph H.; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2016-01-01

The purpose of this paper is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2015-01-01

The purpose of this presentation is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Turboelectric Aircraft Drive Key Performance Parameters and Functional Requirements

NASA Technical Reports Server (NTRS)

Jansen, Ralph H.; Brown, Gerald V.; Felder, James L.; Duffy, Kirsten P.

2015-01-01

The purpose of this paper is to propose specific power and efficiency as the key performance parameters for a turboelectric aircraft power system and investigate their impact on the overall aircraft. Key functional requirements are identified that impact the power system design. Breguet range equations for a base aircraft and a turboelectric aircraft are found. The benefits and costs that may result from the turboelectric system are enumerated. A break-even analysis is conducted to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Automated personnel data base system specifications, Task V. Final report

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

Bartley, H.J.; Bocast, A.K.; Deppner, F.O.

1978-11-01

The full title of this study is 'Development of Qualification Requirements, Training Programs, Career Plans, and Methodologies for Effective Management and Training of Inspection and Enforcement Personnel.' Task V required the development of an automated personnel data base system for NRC/IE. This system is identified as the NRC/IE Personnel, Assignment, Qualifications, and Training System (PAQTS). This Task V report provides the documentation for PAQTS including the Functional Requirements Document (FRD), the Data Requirements Document (DRD), the Hardware and Software Capabilities Assessment, and the Detailed Implementation Schedule. Specific recommendations to facilitate implementation of PAQTS are also included.

Research and development for Onboard Navigation (ONAV) ground based expert/trainer system: ONAV entry expert system code

NASA Technical Reports Server (NTRS)

Bochsler, Daniel C.

1988-01-01

A complete listing is given of the expert system rules for the Entry phase of the Onboard Navigation (ONAV) Ground Based Expert Trainer System for aircraft/space shuttle navigation. These source listings appear in the same format as utilized and required by the C Language Integrated Production System (CLIPS) expert system shell which is the basis for the ONAV entry system. A schematic overview is given of how the rules are organized. These groups result from a partitioning of the rules according to the overall function which a given set of rules performs. This partitioning was established and maintained according to that established in the knowledge specification document. In addition, four other groups of rules are specified. The four groups (control flow, operator inputs, output management, and data tables) perform functions that affect all the other functional rule groups. As the name implies, control flow ensures that the rule groups are executed in the order required for proper operation; operator input rules control the introduction into the CLIPS fact base of various kinds of data required by the expert system; output management rules control the updating of the ONAV expert system user display screen during execution of the system; and data tables are static information utilized by many different rule sets gathered in one convenient place.

A web-based system for supporting global land cover data production

NASA Astrophysics Data System (ADS)

Han, Gang; Chen, Jun; He, Chaoying; Li, Songnian; Wu, Hao; Liao, Anping; Peng, Shu

2015-05-01

Global land cover (GLC) data production and verification process is very complicated, time consuming and labor intensive, requiring huge amount of imagery data and ancillary data and involving many people, often from different geographic locations. The efficient integration of various kinds of ancillary data and effective collaborative classification in large area land cover mapping requires advanced supporting tools. This paper presents the design and development of a web-based system for supporting 30-m resolution GLC data production by combining geo-spatial web-service and Computer Support Collaborative Work (CSCW) technology. Based on the analysis of the functional and non-functional requirements from GLC mapping, a three tiers system model is proposed with four major parts, i.e., multisource data resources, data and function services, interactive mapping and production management. The prototyping and implementation of the system have been realised by a combination of Open Source Software (OSS) and commercially available off-the-shelf system. This web-based system not only facilitates the integration of heterogeneous data and services required by GLC data production, but also provides online access, visualization and analysis of the images, ancillary data and interim 30 m global land-cover maps. The system further supports online collaborative quality check and verification workflows. It has been successfully applied to China's 30-m resolution GLC mapping project, and has improved significantly the efficiency of GLC data production and verification. The concepts developed through this study should also benefit other GLC or regional land-cover data production efforts.

An investigation of microwave landing guidance system signal requirements for conventionally equipped civilian aircraft.

DOT National Transportation Integrated Search

1971-06-01

The report describes efforts leading to the determination of minimum suitable scan rates for the azimuth and Elevation functions of the microwave Landing Guidance System (LGS) proposed by RTCA SC-117, based on performance requirements of two conventi...

Designing for human presence in space: An introduction to environmental control and life support systems

NASA Technical Reports Server (NTRS)

Wieland, Paul

1994-01-01

Human exploration and utilization of space requires habitats to provide appropriate conditions for working and living. These conditions are provided by environmental control and life support systems (ECLSS) that ensure appropriate atmosphere composition, pressure, and temperature; manage and distribute water, process waste matter, provide fire detection and suppression; and other functions as necessary. The functions that are performed by ECLSS are described and basic information necessary to design an ECLSS is provided. Technical and programmatic aspects of designing and developing ECLSS for space habitats are described including descriptions of technologies, analysis methods, test requirements, program organization, documentation requirements, and the requirements imposed by medical, mission, safety, and system needs. The design and development process is described from initial trade studies through system-level analyses to support operation. ECLSS needs for future space habitats are also described. Extensive listings of references and related works provide sources for more detailed information on each aspect of ECLSS design and development.

Integrated command, control communication and computation system study

NASA Technical Reports Server (NTRS)

1981-01-01

The study was conducted in three phases: a functional requirements phase; a functional architecture phase; and a design plan phase. The major emphasis was on the functional architecture phase and the approaches used for its functional hierarchy, operations concept, and interfaces.

GrDHP: a general utility function representation for dual heuristic dynamic programming.

PubMed

Ni, Zhen; He, Haibo; Zhao, Dongbin; Xu, Xin; Prokhorov, Danil V

2015-03-01

A general utility function representation is proposed to provide the required derivable and adjustable utility function for the dual heuristic dynamic programming (DHP) design. Goal representation DHP (GrDHP) is presented with a goal network being on top of the traditional DHP design. This goal network provides a general mapping between the system states and the derivatives of the utility function. With this proposed architecture, we can obtain the required derivatives of the utility function directly from the goal network. In addition, instead of a fixed predefined utility function in literature, we conduct an online learning process for the goal network so that the derivatives of the utility function can be adaptively tuned over time. We provide the control performance of both the proposed GrDHP and the traditional DHP approaches under the same environment and parameter settings. The statistical simulation results and the snapshot of the system variables are presented to demonstrate the improved learning and controlling performance. We also apply both approaches to a power system example to further demonstrate the control capabilities of the GrDHP approach.

47 CFR 10.500 - General requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 47 Telecommunication 1 2010-10-01 2010-10-01 false General requirements. 10.500 Section 10.500 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL COMMERCIAL MOBILE ALERT SYSTEM Equipment Requirements § 10.500 General requirements. CMAS mobile device functionality is dependent on the capabilities of a...

Representing Operational Modes for Situation Awareness

NASA Astrophysics Data System (ADS)

Kirchhübel, Denis; Lind, Morten; Ravn, Ole

2017-01-01

Operating complex plants is an increasingly demanding task for human operators. Diagnosis of and reaction to on-line events requires the interpretation of real time data. Vast amounts of sensor data as well as operational knowledge about the state and design of the plant are necessary to deduct reasonable reactions to abnormal situations. Intelligent computational support tools can make the operator’s task easier, but they require knowledge about the overall system in form of some model. While tools used for fault-tolerant control design based on physical principles and relations are valuable tools for designing robust systems, the models become too complex when considering the interactions on a plant-wide level. The alarm systems meant to support human operators in the diagnosis of the plant-wide situation on the other hand fail regularly in situations where these interactions of systems lead to many related alarms overloading the operator with alarm floods. Functional modelling can provide a middle way to reduce the complexity of plant-wide models by abstracting from physical details to more general functions and behaviours. Based on functional models the propagation of failures through the interconnected systems can be inferred and alarm floods can potentially be reduced to their root-cause. However, the desired behaviour of a complex system changes due to operating procedures that require more than one physical and functional configuration. In this paper a consistent representation of possible configurations is deduced from the analysis of an exemplary start-up procedure by functional models. The proposed interpretation of the modelling concepts simplifies the functional modelling of distinct modes. The analysis further reveals relevant links between the quantitative sensor data and the qualitative perspective of the diagnostics tool based on functional models. This will form the basis for the ongoing development of a novel real-time diagnostics system based on the on-line adaptation of the underlying MFM model.

Fusing Quantitative Requirements Analysis with Model-based Systems Engineering

NASA Technical Reports Server (NTRS)

Cornford, Steven L.; Feather, Martin S.; Heron, Vance A.; Jenkins, J. Steven

2006-01-01

A vision is presented for fusing quantitative requirements analysis with model-based systems engineering. This vision draws upon and combines emergent themes in the engineering milieu. "Requirements engineering" provides means to explicitly represent requirements (both functional and non-functional) as constraints and preferences on acceptable solutions, and emphasizes early-lifecycle review, analysis and verification of design and development plans. "Design by shopping" emphasizes revealing the space of options available from which to choose (without presuming that all selection criteria have previously been elicited), and provides means to make understandable the range of choices and their ramifications. "Model-based engineering" emphasizes the goal of utilizing a formal representation of all aspects of system design, from development through operations, and provides powerful tool suites that support the practical application of these principles. A first step prototype towards this vision is described, embodying the key capabilities. Illustrations, implications, further challenges and opportunities are outlined.

Performance limitations of bilateral force reflection imposed by operator dynamic characteristics

NASA Technical Reports Server (NTRS)

Chapel, Jim D.

1989-01-01

A linearized, single-axis model is presented for bilateral force reflection which facilitates investigation into the effects of manipulator, operator, and task dynamics, as well as time delay and gain scaling. Structural similarities are noted between this model and impedance control. Stability results based upon this model impose requirements upon operator dynamic characteristics as functions of system time delay and environmental stiffness. An experimental characterization reveals the limited capabilities of the human operator to meet these requirements. A procedure is presented for determining the force reflection gain scaling required to provide stability and acceptable operator workload. This procedure is applied to a system with dynamics typical of a space manipulator, and the required gain scaling is presented as a function of environmental stiffness.

Shuttle payload S-band communications system

NASA Technical Reports Server (NTRS)

Batson, B. H.; Teasdale, W. E.; Pawlowski, J. F.; Schmidt, O. L.

1985-01-01

The Shuttle payload S-band communications system design, operational capabilities, and performance are described in detail. System design requirements, overall system and configuration and operation, and laboratory/flight test results are presented. Payload communications requirements development is discussed in terms of evolvement of requirements as well as the resulting technical challenges encountered in meeting the initial requirements. Initial design approaches are described along with cost-saving initiatives that subsequently had to be made. The resulting system implementation that was finally adopted is presented along with a functional description of the system operation. A description of system test results, problems encountered, how the problems were solved, and the system flight experience to date is presented. Finally, a summary of the advancements made and the lessons learned is discussed.

Security Quality Requirements Engineering (SQUARE) Methodology

DTIC Science & Technology

2005-11-01

such as Joint Application Development and the Accelerated Requirements Method [Wood 89, Hubbard 99] • Soft Systems Methodology [Checkland 89...investigated were misuse cases [Jacobson 92], Soft Systems Methodology (SSM) [Checkland 89], Quality Function Deployment (QFD) [QFD 05], Con- trolled...html (2005). [Checkland 89] Checkland, Peter. Soft Systems Methodology . Rational Analysis for a Problematic World. New York, NY: John Wiley & Sons

Linear Actuator System for the NASA Docking System

NASA Technical Reports Server (NTRS)

Dick, Brandon N.; Oesch, Christopher; Rupp, Timothy W.

2017-01-01

The Linear Actuator System (LAS) is a major sub-system within the NASA Docking System (NDS). The NDS Block 1 will be used on the Boeing Crew Space Transportation (CST-100) system to achieve docking with the International Space Station. Critical functions in the Soft Capture aspect of docking are performed by the LAS. This paper describes the general function of the LAS, the system's key requirements and technical challenges, and the development and qualification approach for the system.

Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.

1993-01-01

This paper analyzes the root causes of safety-related software errors in safety-critical, embedded systems. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than non- safety-related software errors. Safety-related software errors are shown to arise most commonly from (1) discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system and (2) misunderstandings of the software's interface with the rest of the system. The paper uses these results to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.

THE COOLING REQUIREMENTS AND PROCESS SYSTEMS OF THE SOUTH AFRICAN RESEARCH REACTOR, SAFARI 1

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

Colley, J.R.

1962-12-01

The SAFARI 1 research reactor is cooled and moderated by light water. There are three process systems, a primary water system which cools the reactor core and surroundings, a pool water system, and a secondary water system which removes the heat from the primary and pool systems. The cooling requirements for the reactor core and experimental facilities are outlined, and the cooling and purification functions of the three process systems are described. (auth)

Syndecan promotes axon regeneration by stabilizing growth cone migration

PubMed Central

Edwards, Tyson J.; Hammarlund, Marc

2014-01-01

SUMMARY Growth cones facilitate the repair of nervous system damage by providing the driving force for axon regeneration. Using single-neuron laser axotomy and in vivo time-lapse imaging, we show that syndecan, a heparan sulfate (HS) proteoglycan, is required for growth cone function during axon regeneration in C. elegans. In the absence of syndecan, regenerating growth cones form but are unstable and collapse, decreasing the effective growth rate and impeding regrowth to target cells. We provide evidence that syndecan has two distinct functions during axon regeneration: 1) a canonical function in axon guidance that requires expression outside the nervous system and depends on HS chains, and 2) a novel intrinsic function in growth cone stabilization that is mediated by the syndecan core protein, independently of HS. Thus, syndecan is a novel regulator of a critical choke point in nervous system repair. PMID:25001284

Syndecan promotes axon regeneration by stabilizing growth cone migration.

PubMed

Edwards, Tyson J; Hammarlund, Marc

2014-07-10

Growth cones facilitate the repair of nervous system damage by providing the driving force for axon regeneration. Using single-neuron laser axotomy and in vivo time-lapse imaging, we show that syndecan, a heparan sulfate (HS) proteoglycan, is required for growth cone function during axon regeneration in C. elegans. In the absence of syndecan, regenerating growth cones form but are unstable and collapse, decreasing the effective growth rate and impeding regrowth to target cells. We provide evidence that syndecan has two distinct functions during axon regeneration: (1) a canonical function in axon guidance that requires expression outside the nervous system and depends on HS chains and (2) an intrinsic function in growth cone stabilization that is mediated by the syndecan core protein, independently of HS. Thus, syndecan is a regulator of a critical choke point in nervous system repair. Copyright © 2014 The Authors. Published by Elsevier Inc. All rights reserved.

Altair Lander Life Support: Requirement Analysis Cycles 1 and 2

NASA Technical Reports Server (NTRS)

Anderson, Molly; Curley, Su; Rotter, Henry; Yagoda, Evan

2009-01-01

Life support systems are a critical part of human exploration beyond low earth orbit. NASA s Altair Lunar Lander has unique missions to perform and will need a unique life support system to complete them. Initial work demonstrated a feasible minimally-functional Lander design. This work was completed in Design Analysis Cycles (DAC) 1, 2, and 3 were reported in a previous paper. On October 21, 2008, the Altair project completed the Mission Concept Review (MCR), moving the project into Phase A. In Phase A activities, the project is preparing for the System Requirements Review (SRR). Altair has conducted two Requirements Analysis Cycles (RACs) to begin this work. During this time, the life support team must examine the Altair mission concepts, Constellation Program level requirements, and interfaces with other vehicles and spacesuits to derive the right set of requirements for the new vehicle. The minimum functionality design meets some of these requirements already and can be easily adapted to meet others. But Altair must identify which will be more costly in mass, power, or other resources to meet. These especially costly requirements must be analyzed carefully to be sure they are truly necessary, and are the best way of explaining and meeting the true need. If they are necessary and clear, they become important mass threats to track at the vehicle level. If they are not clear or do not seem necessary to all stakeholders, Altair must work to redefine them or push back on the requirements writers. Additionally, the life support team is evaluating new technologies to see if they are more effective than the existing baseline design at performing necessary functions in Altair s life support system.

Altair Lander Life Support: Requirements Analysis Cycles 1 and 2

NASA Technical Reports Server (NTRS)

Anderson, Molly; Curley, Su; Rotter, Henry; Yagoda, Evan

2010-01-01

Life support systems are a critical part of human exploration beyond low earth orbit. NASA's Altair Lunar Lander has unique missions to perform and will need a unique life support system to complete them. Initial work demonstrated a feasible minimally -functional Lander design. This work was completed in Design Analysis Cycles (DAC) 1, 2, and 3 were reported in a previous paper'. On October 21, 2008, the Altair project completed the Mission Concept Review (MCR), moving the project into Phase A. In Phase A activities, the project is preparing for the System Requirements Review (SRR). Altair has conducted two Requirements Analysis Cycles (RACs) to begin this work. During this time, the life support team must examine the Altair mission concepts, Constellation Program level requirements, and interfaces with other vehicles and spacesuits to derive the right set of requirements for the new vehicle. The minimum functionality design meets some of these requirements already and can be easily adapted to meet others. But Altair must identify which will be more costly in mass, power, or other resources to meet. These especially costly requirements must be analyzed carefully to be sure they are truly necessary, and are the best way of explaining and meeting the true need. If they are necessary and clear, they become important mass threats to track at the vehicle level. If they are not clear or do not seem necessary to all stakeholders, Altair must work to redefine them or push back on the requirements writers. Additionally, the life support team is evaluating new technologies to see if they are more effective than the existing baseline design at performing necessary functions in Altair's life support system.

Current Hale ROA Voice and Control Communication Practices and Performance: White Paper

NASA Technical Reports Server (NTRS)

2007-01-01

The objective of this white paper is to help achieve the ACCESS 5 goal by sharing the UNITE members knowledge of current HALE ROA communication systems with other ACCESS 5 participants so that all interested parties start from a common understanding as we begin the clarification of requirements for voice and C2 communication. This white paper is also intended to describe the point of departure for any future developments that need to be realized to achieve the long term ACCESS 5 goal. Although this white paper describes the current systems, the functional and performance requirements that are also being developed under ACCESS 5 may not require the same levels of functionality and performance as currently exist. The paper addresses the following: 1) A description of a typical current HALE ROA communications system, 2) HALE ROA communications systems performance metrics, 3) HALE ROA communications systems performance, and 5) A comparison of current HALE ROA communications systems with current regulations.

Ground Systems Development Environment (GSDE) interface requirements analysis

NASA Technical Reports Server (NTRS)

Church, Victor E.; Philips, John; Hartenstein, Ray; Bassman, Mitchell; Ruskin, Leslie; Perez-Davila, Alfredo

1991-01-01

A set of procedural and functional requirements are presented for the interface between software development environments and software integration and test systems used for space station ground systems software. The requirements focus on the need for centralized configuration management of software as it is transitioned from development to formal, target based testing. This concludes the GSDE Interface Requirements study. A summary is presented of findings concerning the interface itself, possible interface and prototyping directions for further study, and results of the investigation of the Cronus distributed applications environment.

Functional categories for future flight deck designs

NASA Technical Reports Server (NTRS)

Abbott, Terence S.

1993-01-01

With the addition of each new system on the flight deck, the danger of increasing overall operator workload while reducing crew understanding of critical mission information exists. The introduction of more powerful onboard computers, larger databases, and the increased use of electronic display media may lead to a situation of flight deck 'sophistication' at the expense of losses in flight crew capabilities and situational awareness. To counter this potentially negative impact of new technology, research activities are underway to reassess the flight deck design process. The fundamental premise of these activities is that a human-centered, systems-oriented approach to the development of advanced civil aircraft flight decks will be required for future designs to remain ergonomically sound and economically competitive. One of the initial steps in an integrated flight deck process is to define the primary flight deck functions needed to support the mission goals of the vehicle. This would allow the design team to evaluate candidate concepts in relation to their effectiveness in meeting the functional requirements. In addition, this would provide a framework to aid in categorizing and bookkeeping all of the activities that are required to be performed on the flight deck, not just activities of the crew or of a specific system. This could then allow for a better understanding and allocation of activities in the design, an understanding of the impact of a specific system on overall system performance, and an awareness of the total crew performance requirements for the design. One candidate set of functional categories that could be used to guide an advanced flight deck design are described.

UTM TCL2 Software Requirements

NASA Technical Reports Server (NTRS)

Smith, Irene S.; Rios, Joseph L.; McGuirk, Patrick O.; Mulfinger, Daniel G.; Venkatesan, Priya; Smith, David R.; Baskaran, Vijayakumar; Wang, Leo

2017-01-01

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level (TCL) 2 software implements the UTM TCL 2 software requirements described herein. These software requirements are linked to the higher level UTM TCL 2 System Requirements. Each successive TCL implements additional UTM functionality, enabling additional use cases. TCL 2 demonstrated how to enable expanded multiple operations by implementing automation for beyond visual line-of-sight, tracking operations, and operations flying over sparsely populated areas.

Closed-channel culture system for efficient and reproducible differentiation of human pluripotent stem cells into islet cells

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

Hirano, Kunio; Konagaya, Shuhei; Turner, Alexander

Human pluripotent stem cells (hPSCs) are thought to be a promising cell-source solution for regenerative medicine due to their indefinite proliferative potential and ability to differentiate to functional somatic cells. However, issues remain with regard to achieving reproducible differentiation of cells with the required functionality for realizing human transplantation therapies and with regard to reducing the potential for bacterial or fungal contamination. To meet these needs, we have developed a closed-channel culture device and corresponding control system. Uniformly-sized spheroidal hPSCs aggregates were formed inside wells within a closed-channel and maintained continuously throughout the culture process. Functional islet-like endocrine cell aggregatesmore » were reproducibly induced following a 30-day differentiation protocol. Our system shows an easily scalable, novel method for inducing PSC differentiation with both purity and functionality. - Highlights: • A simple, closed-channel-based, semi-automatic culture system is proposed. • Uniform cell aggregate formation and culture is realized in microwell structure. • Functional islet cells are successfully induced following 30-plus-day protocol. • System requires no daily medium replacement and reduces contamination risk.« less

UML Profiles for Design Decisions and Non-Functional Requirements

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

Zhu, Liming; Gorton, Ian

2007-06-30

A software architecture is composed of a collection of design decisions. Each design decision helps or hinders certain Non-Functional Requirements (NFR). Current software architecture views focus on expressing components and connectors in the system. Design decisions and their relationships with non-functional requirements are often captured in separate design documentation, not explicitly expressed in any views. This disassociation makes architecture comprehension and architecture evolution harder. In this paper, we propose a UML profile for modeling design decisions and an associated UML profile for modeling non-functional requirements in a generic way. The two UML profiles treat design decisions and nonfunctional requirements asmore » first-class elements. Modeled design decisions always refer to existing architectural elements and thus maintain traceability between the two. We provide a mechanism for checking consistency over this traceability. An exemplar is given as« less

Requirements for CEC POP Machine Protection System

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

Pinayev, I.

2015-02-18

The requirements of CEC POP machine protection system are meant to prevent damage to a vacuum chamber by a missteered electron beam. In this example, beam energy = 22 MeV, Maximal bunch charge = 5 nC, Maximal repetition rate = 78 kHz, Normalized emittance = 5 mm mrad, Minimal β-function = 1 m. From this information the requirements of the protection system can be calculated by factoring the information into equations to find beam densities and temperature excursions.

Research in image management and access

NASA Technical Reports Server (NTRS)

Vondran, Raymond F.; Barron, Billy J.

1993-01-01

Presently, the problem of over-all library system design has been compounded by the accretion of both function and structure to a basic framework of requirements. While more device power has led to increased functionality, opportunities for reducing system complexity at the user interface level have not always been pursued with equal zeal. The purpose of this book is therefore to set forth and examine these opportunities, within the general framework of human factors research in man-machine interfaces. Human factors may be viewed as a series of trade-off decisions among four polarized objectives: machine resources and user specifications; functionality and user requirements. In the past, a limiting factor was the availability of systems. However, in the last two years, over one hundred libraries supported by many different software configurations have been added to the Internet. This document includes a statistical analysis of human responses to five Internet library systems by key features, development of the ideal online catalog system, and ideal online catalog systems for libraries and information centers.

Natural Resource Information System. Volume 1: Overall description

NASA Technical Reports Server (NTRS)

1972-01-01

A prototype computer-based Natural Resource Information System was designed which could store, process, and display data of maximum usefulness to land management decision making. The system includes graphic input and display, the use of remote sensing as a data source, and it is useful at multiple management levels. A survey established current decision making processes and functions, information requirements, and data collection and processing procedures. The applications of remote sensing data and processing requirements were established. Processing software was constructed and a data base established using high-altitude imagery and map coverage of selected areas of SE Arizona. Finally a demonstration of system processing functions was conducted utilizing material from the data base.

Control system and method for a power delivery system having a continuously variable ratio transmission

DOEpatents

Frank, A.A.

1984-07-10

A control system and method for a power delivery system, such as in an automotive vehicle, having an engine coupled to a continuously variable ratio transmission (CVT). Totally independent control of engine and transmission enable the engine to precisely follow a desired operating characteristic, such as the ideal operating line for minimum fuel consumption. CVT ratio is controlled as a function of commanded power or torque and measured load, while engine fuel requirements (e.g., throttle position) are strictly a function of measured engine speed. Fuel requirements are therefore precisely adjusted in accordance with the ideal characteristic for any load placed on the engine. 4 figs.

Multiconfigurational short-range density-functional theory for open-shell systems

NASA Astrophysics Data System (ADS)

Hedegârd, Erik Donovan; Toulouse, Julien; Jensen, Hans Jørgen Aagaard

2018-06-01

Many chemical systems cannot be described by quantum chemistry methods based on a single-reference wave function. Accurate predictions of energetic and spectroscopic properties require a delicate balance between describing the most important configurations (static correlation) and obtaining dynamical correlation efficiently. The former is most naturally done through a multiconfigurational (MC) wave function, whereas the latter can be done by, e.g., perturbation theory. We have employed a different strategy, namely, a hybrid between multiconfigurational wave functions and density-functional theory (DFT) based on range separation. The method is denoted by MC short-range DFT (MC-srDFT) and is more efficient than perturbative approaches as it capitalizes on the efficient treatment of the (short-range) dynamical correlation by DFT approximations. In turn, the method also improves DFT with standard approximations through the ability of multiconfigurational wave functions to recover large parts of the static correlation. Until now, our implementation was restricted to closed-shell systems, and to lift this restriction, we present here the generalization of MC-srDFT to open-shell cases. The additional terms required to treat open-shell systems are derived and implemented in the DALTON program. This new method for open-shell systems is illustrated on dioxygen and [Fe(H2O)6]3+.

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project: Advanced Collision Avoidance System for UAS (ACAS Xu) Interoperability White Paper Presentation

NASA Technical Reports Server (NTRS)

Fern, Lisa

2017-01-01

The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.

An Approach for Integrating the Prioritization of Functional and Nonfunctional Requirements

PubMed Central

Dabbagh, Mohammad; Lee, Sai Peck

2014-01-01

Due to the budgetary deadlines and time to market constraints, it is essential to prioritize software requirements. The outcome of requirements prioritization is an ordering of requirements which need to be considered first during the software development process. To achieve a high quality software system, both functional and nonfunctional requirements must be taken into consideration during the prioritization process. Although several requirements prioritization methods have been proposed so far, no particular method or approach is presented to consider both functional and nonfunctional requirements during the prioritization stage. In this paper, we propose an approach which aims to integrate the process of prioritizing functional and nonfunctional requirements. The outcome of applying the proposed approach produces two separate prioritized lists of functional and non-functional requirements. The effectiveness of the proposed approach has been evaluated through an empirical experiment aimed at comparing the approach with the two state-of-the-art-based approaches, analytic hierarchy process (AHP) and hybrid assessment method (HAM). Results show that our proposed approach outperforms AHP and HAM in terms of actual time-consumption while preserving the quality of the results obtained by our proposed approach at a high level of agreement in comparison with the results produced by the other two approaches. PMID:24982987

An approach for integrating the prioritization of functional and nonfunctional requirements.

PubMed

Dabbagh, Mohammad; Lee, Sai Peck

2014-01-01

Due to the budgetary deadlines and time to market constraints, it is essential to prioritize software requirements. The outcome of requirements prioritization is an ordering of requirements which need to be considered first during the software development process. To achieve a high quality software system, both functional and nonfunctional requirements must be taken into consideration during the prioritization process. Although several requirements prioritization methods have been proposed so far, no particular method or approach is presented to consider both functional and nonfunctional requirements during the prioritization stage. In this paper, we propose an approach which aims to integrate the process of prioritizing functional and nonfunctional requirements. The outcome of applying the proposed approach produces two separate prioritized lists of functional and non-functional requirements. The effectiveness of the proposed approach has been evaluated through an empirical experiment aimed at comparing the approach with the two state-of-the-art-based approaches, analytic hierarchy process (AHP) and hybrid assessment method (HAM). Results show that our proposed approach outperforms AHP and HAM in terms of actual time-consumption while preserving the quality of the results obtained by our proposed approach at a high level of agreement in comparison with the results produced by the other two approaches.

Space station automation study. Volume 2: Technical report. Autonomous systems and assembly

NASA Technical Reports Server (NTRS)

1984-01-01

The application of automation to space station functions is discussed. A summary is given of the evolutionary functions associated with long range missions and objectives. Mission tasks and requirements are defined. Space station sub-systems, mission models, assembly, and construction are discussed.

Matrix light and pixel light: optical system architecture and requirements to the light source

NASA Astrophysics Data System (ADS)

Spinger, Benno; Timinger, Andreas L.

2015-09-01

Modern Automotive headlamps enable improved functionality for more driving comfort and safety. Matrix or Pixel light headlamps are not restricted to either pure low beam functionality or pure high beam. Light in direction of oncoming traffic is selectively switched of, potential hazard can be marked via an isolated beam and the illumination on the road can even follow a bend. The optical architectures that enable these advanced functionalities are diverse. Electromechanical shutters and lens units moved by electric motors were the first ways to realize these systems. Switching multiple LED light sources is a more elegant and mechanically robust solution. While many basic functionalities can already be realized with a limited number of LEDs, an increasing number of pixels will lead to more driving comfort and better visibility. The required optical system needs not only to generate a desired beam distribution with a high angular dynamic, but also needs to guarantee minimal stray light and cross talk between the different pixels. The direct projection of the LED array via a lens is a simple but not very efficient optical system. We discuss different optical elements for pre-collimating the light with minimal cross talk and improved contrast between neighboring pixels. Depending on the selected optical system, we derive the basic light source requirements: luminance, surface area, contrast, flux and color homogeneity.

Hercules Single-Stage Reusable Vehicle (HSRV) Operating Base

NASA Technical Reports Server (NTRS)

Moon, Michael J.; McCleskey, Carey M.

2017-01-01

Conceptual design for the layout of lunar-planetary surface support systems remains an important area needing further master planning. This paper explores a structured approach to organize the layout of a Mars-based site equipped for routinely flying a human-scale reusable taxi system. The proposed Hercules Transportation System requires a surface support capability to sustain its routine, affordable, and dependable operation. The approach organizes a conceptual Hercules operating base through functional station sets. The station set approach will allow follow-on work to trade design approaches and consider technologies for more efficient flow of material, energy, and information at future Mars bases and settlements. The station set requirements at a Mars site point to specific capabilities needed. By drawing from specific Hercules design characteristics, the technology requirements for surface-based systems will come into greater focus. This paper begins a comprehensive process for documenting functional needs, architectural design methods, and analysis techniques necessary for follow-on concept studies.

Essential use cases for pedagogical patterns

NASA Astrophysics Data System (ADS)

Derntl, Michael; Botturi, Luca

2006-06-01

Coming from architecture, through computer science, pattern-based design spread into other disciplines and is nowadays recognized as a powerful way of capturing and reusing effective design practice. However, current pedagogical pattern approaches lack widespread adoption, both by users and authors, and are still limited to individual initiatives. This paper contributes to creating a shared understanding of what a pattern system is by defining the key terms. Moreover, the paper builds upon and extends a set of existing functional and non-functional requirements for pattern systems, adds structure to these requirements, and derives essential use cases following a goal-based approach for both pattern maintenance and pattern application. Finally, implications concerning the pedagogical use of pattern-based design are drawn, concluding that a stronger focus on the underlying (pedagogical) value system is required in order to make a pattern system a meaningful tool for effective educational design.

Man-machine interface and control of the shuttle digital flight system

NASA Technical Reports Server (NTRS)

Burghduff, R. D.; Lewis, J. L., Jr.

1985-01-01

The space shuttle main engine (SSME) presented new requirements in the design of controls for large pump fed liquid rocket engine systems. These requirements were the need for built in full mission support capability, and complexity and flexibility of function not previously needed in this type of application. An engine mounted programmable digital control system was developed to meet these requirements. The engine system and controller and their function are described. Design challenges encountered during the course of development included accommodation for a very severe engine environment, the implementation of redundancy and redundancy management to provide fail operational/fail safe capability, removal of heat from the package, and significant constraints on computer memory size and processing time. The flexibility offered by programmable control reshaped the approach to engine design and development and set the pattern for future controls development in these types of applications.

Orbit transfer rocket engine integrated control and health monitoring system technology readiness assessment

NASA Technical Reports Server (NTRS)

Bickford, R. L.; Collamore, F. N.; Gage, M. L.; Morgan, D. B.; Thomas, E. R.

1992-01-01

The objectives of this task were to: (1) estimate the technology readiness of an integrated control and health monitoring (ICHM) system for the Aerojet 7500 lbF Orbit Transfer Vehicle engine preliminary design assuming space based operations; and (2) estimate the remaining cost to advance this technology to a NASA defined 'readiness level 6' by 1996 wherein the technology has been demonstrated with a system validation model in a simulated environment. The work was accomplished through the conduct of four subtasks. In subtask 1 the minimally required functions for the control and monitoring system was specified. The elements required to perform these functions were specified in Subtask 2. In Subtask 3, the technology readiness level of each element was assessed. Finally, in Subtask 4, the development cost and schedule requirements were estimated for bringing each element to 'readiness level 6'.

Knowledge-based decision support for Space Station assembly sequence planning

NASA Astrophysics Data System (ADS)

1991-04-01

A complete Personal Analysis Assistant (PAA) for Space Station Freedom (SSF) assembly sequence planning consists of three software components: the system infrastructure, intra-flight value added, and inter-flight value added. The system infrastructure is the substrate on which software elements providing inter-flight and intra-flight value-added functionality are built. It provides the capability for building representations of assembly sequence plans and specification of constraints and analysis options. Intra-flight value-added provides functionality that will, given the manifest for each flight, define cargo elements, place them in the National Space Transportation System (NSTS) cargo bay, compute performance measure values, and identify violated constraints. Inter-flight value-added provides functionality that will, given major milestone dates and capability requirements, determine the number and dates of required flights and develop a manifest for each flight. The current project is Phase 1 of a projected two phase program and delivers the system infrastructure. Intra- and inter-flight value-added were to be developed in Phase 2, which has not been funded. Based on experience derived from hundreds of projects conducted over the past seven years, ISX developed an Intelligent Systems Engineering (ISE) methodology that combines the methods of systems engineering and knowledge engineering to meet the special systems development requirements posed by intelligent systems, systems that blend artificial intelligence and other advanced technologies with more conventional computing technologies. The ISE methodology defines a phased program process that begins with an application assessment designed to provide a preliminary determination of the relative technical risks and payoffs associated with a potential application, and then moves through requirements analysis, system design, and development.

Knowledge-based decision support for Space Station assembly sequence planning

NASA Technical Reports Server (NTRS)

1991-01-01

A complete Personal Analysis Assistant (PAA) for Space Station Freedom (SSF) assembly sequence planning consists of three software components: the system infrastructure, intra-flight value added, and inter-flight value added. The system infrastructure is the substrate on which software elements providing inter-flight and intra-flight value-added functionality are built. It provides the capability for building representations of assembly sequence plans and specification of constraints and analysis options. Intra-flight value-added provides functionality that will, given the manifest for each flight, define cargo elements, place them in the National Space Transportation System (NSTS) cargo bay, compute performance measure values, and identify violated constraints. Inter-flight value-added provides functionality that will, given major milestone dates and capability requirements, determine the number and dates of required flights and develop a manifest for each flight. The current project is Phase 1 of a projected two phase program and delivers the system infrastructure. Intra- and inter-flight value-added were to be developed in Phase 2, which has not been funded. Based on experience derived from hundreds of projects conducted over the past seven years, ISX developed an Intelligent Systems Engineering (ISE) methodology that combines the methods of systems engineering and knowledge engineering to meet the special systems development requirements posed by intelligent systems, systems that blend artificial intelligence and other advanced technologies with more conventional computing technologies. The ISE methodology defines a phased program process that begins with an application assessment designed to provide a preliminary determination of the relative technical risks and payoffs associated with a potential application, and then moves through requirements analysis, system design, and development.

Functional integration of automated system databases by means of artificial intelligence

NASA Astrophysics Data System (ADS)

Dubovoi, Volodymyr M.; Nikitenko, Olena D.; Kalimoldayev, Maksat; Kotyra, Andrzej; Gromaszek, Konrad; Iskakova, Aigul

2017-08-01

The paper presents approaches for functional integration of automated system databases by means of artificial intelligence. The peculiarities of turning to account the database in the systems with the usage of a fuzzy implementation of functions were analyzed. Requirements for the normalization of such databases were defined. The question of data equivalence in conditions of uncertainty and collisions in the presence of the databases functional integration is considered and the model to reveal their possible occurrence is devised. The paper also presents evaluation method of standardization of integrated database normalization.

The Department of Business and Finance in a Public School System.

ERIC Educational Resources Information Center

Educational Service Bureau, Inc., Washington, DC. Administrative Leadership Service.

This booklet describes the business and finance functions of managing public school systems. The role and duties of a school business administrator are discussed and qualifications, educational requirements, and certification requirements are suggested for the position. The organizational structure, operation, and duties of administrators in the…

40 CFR 267.199 - What inspection requirements must I meet?

Code of Federal Regulations, 2011 CFR

2011-07-01

... cathodic protection systems, if present, according to, at a minimum, the following schedule to ensure that they are functioning properly: (1) Confirm that the cathodic protection system is operating properly... 40 Protection of Environment 27 2011-07-01 2011-07-01 false What inspection requirements must I...

40 CFR 267.199 - What inspection requirements must I meet?

Code of Federal Regulations, 2010 CFR

2010-07-01

... cathodic protection systems, if present, according to, at a minimum, the following schedule to ensure that they are functioning properly: (1) Confirm that the cathodic protection system is operating properly... 40 Protection of Environment 26 2010-07-01 2010-07-01 false What inspection requirements must I...

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

Proceedings and findings of the 1976 Workshop on Ride Quality. [passenger acceptance of transportation systems

NASA Technical Reports Server (NTRS)

Kuhlthau, A. R. (Editor)

1976-01-01

The workshop was organized around the study of the three basic transfer functions required to evaluate and/or predict passenger acceptance of transportation systems: These are the vehicle, passenger, and value transfer functions. For the purpose of establishing working groups corresponding to the basic transfer functions, it was decided to split the vehicle transfer function into two distinct groups studying surface vehicles and air/marine vehicles, respectively.

Materials requirements for optical processing and computing devices

NASA Technical Reports Server (NTRS)

Tanguay, A. R., Jr.

1985-01-01

Devices for optical processing and computing systems are discussed, with emphasis on the materials requirements imposed by functional constraints. Generalized optical processing and computing systems are described in order to identify principal categories of requisite components for complete system implementation. Three principal device categories are selected for analysis in some detail: spatial light modulators, volume holographic optical elements, and bistable optical devices. The implications for optical processing and computing systems of the materials requirements identified for these device categories are described, and directions for future research are proposed.

User's manual for the Shuttle Electric Power System analysis computer program (SEPS), volume 2 of program documentation

NASA Technical Reports Server (NTRS)

Bains, R. W.; Herwig, H. A.; Luedeman, J. K.; Torina, E. M.

1974-01-01

The Shuttle Electric Power System Analysis SEPS computer program which performs detailed load analysis including predicting energy demands and consumables requirements of the shuttle electric power system along with parameteric and special case studies on the shuttle electric power system is described. The functional flow diagram of the SEPS program is presented along with data base requirements and formats, procedure and activity definitions, and mission timeline input formats. Distribution circuit input and fixed data requirements are included. Run procedures and deck setups are described.

Design of a clinical notification system.

PubMed

Wagner, M M; Tsui, F C; Pike, J; Pike, L

1999-01-01

We describe the requirements and design of an enterprise-wide notification system. From published descriptions of notification schemes, our own experience, and use cases provided by diverse users in our institution, we developed a set of functional requirements. The resulting design supports multiple communication channels, third party mappings (algorithms) from message to recipient and/or channel of delivery, and escalation algorithms. A requirement for multiple message formats is addressed by a document specification. We implemented this system in Java as a CORBA object. This paper describes the design and current implementation of our notification system.

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.

Expert system for on-board satellite scheduling and control

NASA Technical Reports Server (NTRS)

Barry, John M.; Sary, Charisse

1988-01-01

An Expert System is described which Rockwell Satellite and Space Electronics Division (S&SED) is developing to dynamically schedule the allocation of on-board satellite resources and activities. This expert system is the Satellite Controller. The resources to be scheduled include power, propellant and recording tape. The activities controlled include scheduling satellite functions such as sensor checkout and operation. The scheduling of these resources and activities is presently a labor intensive and time consuming ground operations task. Developing a schedule requires extensive knowledge of the system and subsystems operations, operational constraints, and satellite design and configuration. This scheduling process requires highly trained experts anywhere from several hours to several weeks to accomplish. The process is done through brute force, that is examining cryptic mnemonic data off line to interpret the health and status of the satellite. Then schedules are formulated either as the result of practical operator experience or heuristics - that is rules of thumb. Orbital operations must become more productive in the future to reduce life cycle costs and decrease dependence on ground control. This reduction is required to increase autonomy and survivability of future systems. The design of future satellites require that the scheduling function be transferred from ground to on board systems.

Goal-Function Tree Modeling for Systems Engineering and Fault Management

NASA Technical Reports Server (NTRS)

Johnson, Stephen B.; Breckenridge, Jonathan T.

2013-01-01

This paper describes a new representation that enables rigorous definition and decomposition of both nominal and off-nominal system goals and functions: the Goal-Function Tree (GFT). GFTs extend the concept and process of functional decomposition, utilizing state variables as a key mechanism to ensure physical and logical consistency and completeness of the decomposition of goals (requirements) and functions, and enabling full and complete traceabilitiy to the design. The GFT also provides for means to define and represent off-nominal goals and functions that are activated when the system's nominal goals are not met. The physical accuracy of the GFT, and its ability to represent both nominal and off-nominal goals enable the GFT to be used for various analyses of the system, including assessments of the completeness and traceability of system goals and functions, the coverage of fault management failure detections, and definition of system failure scenarios.

Gravity, the third dimension of life support in space

NASA Technical Reports Server (NTRS)

Burton, Russell R.

1994-01-01

The ascent of the human into high altitudes required a 2-D life support system that supplied: oxygen, and heat. At lower altitudes, increased oxygen concentration in the inhaled gases was useful, but at higher altitudes for longer durations, this 'clever' life support approach was no longer adequate--physiologic requirements had to provide a natural pressure-based environment. In space, the life support system requires a third dimension, gravity. Although substituting for gravity has been successful on a limited number of physiologic functions for short-duration stays in space, long durations will require the effects of the real thing for critical physiologic functions. It has been known for over a hundred years that the forces of acceleration (G) and gravity are equivalent. Therefore, gravitational stimulation in space can be achieved with centrifugation. However, for this stimulation to be effective, the dosage of G required to maintain normal physiologic function must be determined. An approximation of this dosage of G for the human can be determined with 3-day bed-rest studies including periodic centrifuge exposure. Recent research on this topic is reviewed.

The 30/20 GHz communications system functional requirements

NASA Technical Reports Server (NTRS)

Siperko, C. M.; Frankfort, M.; Markham, R.; Wall, M.

1981-01-01

The characteristics of 30/20 GHz usage in satellite systems to be used in support of projected communication requirements of the 1990's are defined. A requirements analysis which develops projected market demand for satellite services by general and specialized carriers and an analysis of the impact of propagation and system constraints on 30/20 GHz operation are included. A set of technical performance characteristics for the 30/20 GHz systems which can serve the resulting market demand and the experimental program necessary to verify technical and operational aspects of the proposed systems is also discussed.

Functional requirements for onboard management of space shuttle consumables, volume 1

NASA Technical Reports Server (NTRS)

Graf, P. J.; Herwig, H. A.; Neel, L. W.

1973-01-01

A study was conducted to determine the functional requirements for onboard management of space shuttle consumables. A generalized consumable management concept was developed for application to advanced spacecraft. The subsystems and related consumables selected for inclusion in the consumables management system are: (1) propulsion, (2) power generation, and (3) environmental and life support.

Principles and core functions of integrated child health information systems.

PubMed

Hinman, Alan R; Atkinson, Delton; Diehn, Tonya Norvell; Eichwald, John; Heberer, Jennifer; Hoyle, Therese; King, Pam; Kossack, Robert E; Williams, Donna C; Zimmerman, Amy

2004-11-01

Infants undergo a series of preventive and therapeutic health interventions and activities. Typically, each activity includes collection and submission of data to a dedicated information system. Subsequently, health care providers, families, and health programs must query each information system to determine the child's status in a given area. Efforts are underway to integrate information in these separate information systems. This requires specifying the core functions that integrated information systems must perform.

Electro-optical rendezvous and docking sensors

NASA Technical Reports Server (NTRS)

Tubbs, David J.; Kesler, Lynn O.; Sirko, Robert J.

1991-01-01

Electro-optical sensors provide unique and critical functionality for space missions requiring rendezvous, docking, and berthing. McDonnell Douglas is developing a complete rendezvous and docking system for both manned and unmanned missions. This paper examines our sensor development and the systems and missions which benefit from rendezvous and docking sensors. Simulation results quantifying system performance improvements in key areas are given, with associated sensor performance requirements. A brief review of NASA-funded development activities and the current performance of electro-optical sensors for space applications is given. We will also describe current activities at McDonnell Douglas for a fully functional demonstration to address specific NASA mission needs.

Aspects, Wrappers and Events

NASA Technical Reports Server (NTRS)

Filman, Robert E.

2003-01-01

This viewgraph presentation provides information on Object Infrastructure Framework (OIF), an Aspect-Oriented Programming (AOP) system. The presentation begins with an introduction to the difficulties and requirements of distributed computing, including functional and non-functional requirements (ilities). The architecture of Distributed Object Technology includes stubs, proxies for implementation objects, and skeletons, proxies for client applications. The key OIF ideas (injecting behavior, annotated communications, thread contexts, and pragma) are discussed. OIF is an AOP mechanism; AOP is centered on: 1) Separate expression of crosscutting concerns; 2) Mechanisms to weave the separate expressions into a unified system. AOP is software engineering technology for separately expressing systematic properties while nevertheless producing running systems that embody these properties.

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.

Design development of the Apollo command and service module thrust vector attitude control systems

NASA Technical Reports Server (NTRS)

Peters, W. H.

1978-01-01

Development of the Apollo thrust vector control digital autopilot (TVC DAP) was summarized. This is the control system that provided pitch and yaw attitude control during velocity change maneuvers using the main rocket engine on the Apollo service module. A list of ten primary functional requirements for this control system are presented, each being subordinate to a more general requirement appearing earlier on the list. Development process functions were then identified and the essential information flow paths were explored. This provided some visibility into the particular NASA/contractor interface, as well as relationships between the many individual activities.

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.

COE loss-of-function analysis reveals a genetic program underlying maintenance and regeneration of the nervous system in planarians.

PubMed

Cowles, Martis W; Omuro, Kerilyn C; Stanley, Brianna N; Quintanilla, Carlo G; Zayas, Ricardo M

2014-10-01

Members of the COE family of transcription factors are required for central nervous system (CNS) development. However, the function of COE in the post-embryonic CNS remains largely unknown. An excellent model for investigating gene function in the adult CNS is the freshwater planarian. This animal is capable of regenerating neurons from an adult pluripotent stem cell population and regaining normal function. We previously showed that planarian coe is expressed in differentiating and mature neurons and that its function is required for proper CNS regeneration. Here, we show that coe is essential to maintain nervous system architecture and patterning in intact (uninjured) planarians. We took advantage of the robust phenotype in intact animals to investigate the genetic programs coe regulates in the CNS. We compared the transcriptional profiles of control and coe RNAi planarians using RNA sequencing and identified approximately 900 differentially expressed genes in coe knockdown animals, including 397 downregulated genes that were enriched for nervous system functional annotations. Next, we validated a subset of the downregulated transcripts by analyzing their expression in coe-deficient planarians and testing if the mRNAs could be detected in coe+ cells. These experiments revealed novel candidate targets of coe in the CNS such as ion channel, neuropeptide, and neurotransmitter genes. Finally, to determine if loss of any of the validated transcripts underscores the coe knockdown phenotype, we knocked down their expression by RNAi and uncovered a set of coe-regulated genes implicated in CNS regeneration and patterning, including orthologs of sodium channel alpha-subunit and pou4. Our study broadens the knowledge of gene expression programs regulated by COE that are required for maintenance of neural subtypes and nervous system architecture in adult animals.

Functional Based Adaptive and Fuzzy Sliding Controller for Non-Autonomous Active Suspension System

NASA Astrophysics Data System (ADS)

Huang, Shiuh-Jer; Chen, Hung-Yi

In this paper, an adaptive sliding controller is developed for controlling a vehicle active suspension system. The functional approximation technique is employed to substitute the unknown non-autonomous functions of the suspension system and release the model-based requirement of sliding mode control algorithm. In order to improve the control performance and reduce the implementation problem, a fuzzy strategy with online learning ability is added to compensate the functional approximation error. The update laws of the functional approximation coefficients and the fuzzy tuning parameters are derived from the Lyapunov theorem to guarantee the system stability. The proposed controller is implemented on a quarter-car hydraulic actuating active suspension system test-rig. The experimental results show that the proposed controller suppresses the oscillation amplitude of the suspension system effectively.

Application of enhanced modern structured analysis techniques to Space Station Freedom electric power system requirements

NASA Technical Reports Server (NTRS)

Biernacki, John; Juhasz, John; Sadler, Gerald

1991-01-01

A team of Space Station Freedom (SSF) system engineers are in the process of extensive analysis of the SSF requirements, particularly those pertaining to the electrical power system (EPS). The objective of this analysis is the development of a comprehensive, computer-based requirements model, using an enhanced modern structured analysis methodology (EMSA). Such a model provides a detailed and consistent representation of the system's requirements. The process outlined in the EMSA methodology is unique in that it allows the graphical modeling of real-time system state transitions, as well as functional requirements and data relationships, to be implemented using modern computer-based tools. These tools permit flexible updating and continuous maintenance of the models. Initial findings resulting from the application of EMSA to the EPS have benefited the space station program by linking requirements to design, providing traceability of requirements, identifying discrepancies, and fostering an understanding of the EPS.

Extended mission life support systems

NASA Technical Reports Server (NTRS)

Quattrone, P. D.

1985-01-01

Extended manned space missions which include interplanetary missions require regenerative life support systems. Manned mission life support considerations are placed in perspective and previous manned space life support system technology, activities and accomplishments in current supporting research and technology (SR&T) programs are reviewed. The life support subsystem/system technologies required for an enhanced duration orbiter (EDO) and a space operations center (SOC), regenerative life support functions and technology required for manned interplanetary flight vehicles, and future development requirements are outlined. The Space Shuttle Orbiters (space transportation system) is space cabin atmosphere is maintained at Earth ambient pressure of 14.7 psia (20% O2 and 80% N2). The early Shuttle flights will be seven-day flights, and the life support system flight hardware will still utilize expendables.

Applying Formal Verification Techniques to Ambient Assisted Living Systems

NASA Astrophysics Data System (ADS)

Benghazi, Kawtar; Visitación Hurtado, María; Rodríguez, María Luisa; Noguera, Manuel

This paper presents a verification approach based on timed traces semantics and MEDISTAM-RT [1] to check the fulfillment of non-functional requirements, such as timeliness and safety, and assure the correct functioning of the Ambient Assisted Living (AAL) systems. We validate this approach by its application to an Emergency Assistance System for monitoring people suffering from cardiac alteration with syncope.

47 CFR 10.320 - Provider alert gateway requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 47 Telecommunication 1 2014-10-01 2014-10-01 false Provider alert gateway requirements. 10.320 Section 10.320 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL WIRELESS EMERGENCY ALERTS System Architecture § 10.320 Provider alert gateway requirements. This section specifies the functions...

47 CFR 10.320 - Provider alert gateway requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 47 Telecommunication 1 2013-10-01 2013-10-01 false Provider alert gateway requirements. 10.320 Section 10.320 Telecommunication FEDERAL COMMUNICATIONS COMMISSION GENERAL WIRELESS EMERGENCY ALERTS System Architecture § 10.320 Provider alert gateway requirements. This section specifies the functions...

Prototype Flight Management Capabilities to Explore Temporal RNP Concepts

NASA Technical Reports Server (NTRS)

Ballin, Mark G.; Williams, David H.; Allen, Bonnie Danette; Palmer, Michael T.

2008-01-01

Next Generation Air Transportation System (NextGen) concepts of operation may require aircraft to fly planned trajectories in four dimensions three spatial dimensions and time. A prototype 4D flight management capability is being developed by NASA to facilitate the development of these concepts. New trajectory generation functions extend today's flight management system (FMS) capabilities that meet a single Required Time of Arrival (RTA) to trajectory solutions that comply with multiple RTA constraints. When a solution is not possible, a constraint management capability relaxes constraints to achieve a trajectory solution that meets the most important constraints as specified by candidate NextGen concepts. New flight guidance functions provide continuous guidance to the aircraft s flight control system to enable it to fly specified 4D trajectories. Guidance options developed for research investigations include a moving time window with varying tolerances that are a function of proximity to imposed constraints, and guidance that recalculates the aircraft s planned trajectory as a function of the estimation of current compliance. Compliance tolerances are related to required navigation performance (RNP) through the extension of existing RNP concepts for lateral containment. A conceptual temporal RNP implementation and prototype display symbology are proposed.

An object oriented extension to CLIPS

NASA Technical Reports Server (NTRS)

Sobkowicz, Clifford

1990-01-01

A presentation of software sub-system developed to augment C Language Production Systems (CLIPS) with facilities for object oriented Knowledge representation. Functions are provided to define classes, instantiate objects, access attributes, and assert object related facts. This extension is implemented via the CLIPS user function interface and does not require modification of any CLIPS code. It does rely on internal CLIPS functions for memory management and symbol representation.

Development of a structured approach for decomposition of complex systems on a functional basis

NASA Astrophysics Data System (ADS)

Yildirim, Unal; Felician Campean, I.

2014-07-01

The purpose of this paper is to present the System State Flow Diagram (SSFD) as a structured and coherent methodology to decompose a complex system on a solution- independent functional basis. The paper starts by reviewing common function modelling frameworks in literature and discusses practical requirements of the SSFD in the context of the current literature and current approaches in industry. The proposed methodology is illustrated through the analysis of a case study: design analysis of a generic Bread Toasting System (BTS).

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.

Optical processing for future computer networks

NASA Technical Reports Server (NTRS)

Husain, A.; Haugen, P. R.; Hutcheson, L. D.; Warrior, J.; Murray, N.; Beatty, M.

1986-01-01

In the development of future data management systems, such as the NASA Space Station, a major problem represents the design and implementation of a high performance communication network which is self-correcting and repairing, flexible, and evolvable. To obtain the goal of designing such a network, it will be essential to incorporate distributed adaptive network control techniques. The present paper provides an outline of the functional and communication network requirements for the Space Station data management system. Attention is given to the mathematical representation of the operations being carried out to provide the required functionality at each layer of communication protocol on the model. The possible implementation of specific communication functions in optics is also considered.

Time Varying Compensator Design for Reconfigurable Structures Using Non-Collocated Feedback

NASA Technical Reports Server (NTRS)

Scott, Michael A.

1996-01-01

Analysis and synthesis tools are developed to improved the dynamic performance of reconfigurable nonminimum phase, nonstrictly positive real-time variant systems. A novel Spline Varying Optimal (SVO) controller is developed for the kinematic nonlinear system. There are several advantages to using the SVO controller, in which the spline function approximates the system model, observer, and controller gain. They are: The spline function approximation is simply connected, thus the SVO controller is more continuous than traditional gain scheduled controllers when implemented on a time varying plant; ft is easier for real-time implementations in storage and computational effort; where system identification is required, the spline function requires fewer experiments, namely four experiments; and initial startup estimator transients are eliminated. The SVO compensator was evaluated on a high fidelity simulation of the Shuttle Remote Manipulator System. The SVO controller demonstrated significant improvement over the present arm performance: (1) Damping level was improved by a factor of 3; and (2) Peak joint torque was reduced by a factor of 2 following Shuttle thruster firings.

Integrated air revitalization system for Space Station

NASA Technical Reports Server (NTRS)

Boyda, R. B.; Miller, C. W.; Schwartz, M. R.

1986-01-01

Fifty-one distinct functions are encompassed by the Space Station's Environmental Control and Life Support System; one exception to this noninteractivity of functions is the regenerative air revitalization system that removes and reduces CO2 and generates O2. The integration of these interdependent functions, and of humidity control, into a single system furnishes opportunities for process simplification as well as for power, weight and volume requirement reductions by comparison with discrete subsystems. Attention is presently given to a system which quantifies these integration-related savings and identifies additional advantages that accrue to this integrating design method.

System engineering study of electrodynamic tether as a spaceborne generator and radiator of electromagnetic waves in the ULF/ELF frequency band

NASA Technical Reports Server (NTRS)

Estes, R. D.; Grossi, M. D.; Lorenzini, E. C.

1986-01-01

The transmission and generation by orbiting tethered satellite systems of information carrying electromagnetic waves in the ULF/ELF frequency band to the Earth at suitably high signal intensities was examined and the system maintaining these intensities in their orbits for long periods of time without excessive onboard power requirements was investigated. The injection quantity power into electromagnetic waves as a function of system parameters such as tether length and orbital height was estimated. The basic equations needed to evaluate alternataing current tethered systems for external energy requirements are presented. The energy equations to tethered systems with various lengths, tether resistances, and radiation resistances, operating at different current values are applied. Radiation resistance as a function of tether length and orbital height is discussed. It is found that ULF/ELF continuously radiating systems could be maintained in orbit with moderate power requirements. The effect of tether length on the power going into electromagnetic waves and whether a single or dual tether system is preferable for the self-driven mode is discussed. It is concluded that the single tether system is preferable over the dual system.

Avian respiratory system disorders

USGS Publications Warehouse

Olsen, Glenn H.

1989-01-01

Diagnosing and treating respiratory diseases in avian species requires a basic knowledge about the anatomy and physiology of this system in birds. Differences between mammalian and avian respiratory system function, diagnosis, and treatment are highlighted.

Fault tolerant computer control for a Maglev transportation system

NASA Technical Reports Server (NTRS)

Lala, Jaynarayan H.; Nagle, Gail A.; Anagnostopoulos, George

1994-01-01

Magnetically levitated (Maglev) vehicles operating on dedicated guideways at speeds of 500 km/hr are an emerging transportation alternative to short-haul air and high-speed rail. They have the potential to offer a service significantly more dependable than air and with less operating cost than both air and high-speed rail. Maglev transportation derives these benefits by using magnetic forces to suspend a vehicle 8 to 200 mm above the guideway. Magnetic forces are also used for propulsion and guidance. The combination of high speed, short headways, stringent ride quality requirements, and a distributed offboard propulsion system necessitates high levels of automation for the Maglev control and operation. Very high levels of safety and availability will be required for the Maglev control system. This paper describes the mission scenario, functional requirements, and dependability and performance requirements of the Maglev command, control, and communications system. A distributed hierarchical architecture consisting of vehicle on-board computers, wayside zone computers, a central computer facility, and communication links between these entities was synthesized to meet the functional and dependability requirements on the maglev. Two variations of the basic architecture are described: the Smart Vehicle Architecture (SVA) and the Zone Control Architecture (ZCA). Preliminary dependability modeling results are also presented.

Axons guided by insulin receptor in Drosophila visual system.

PubMed

Song, Jianbo; Wu, Lingling; Chen, Zun; Kohanski, Ronald A; Pick, Leslie

2003-04-18

Insulin receptors are abundant in the central nervous system, but their roles remain elusive. Here we show that the insulin receptor functions in axon guidance. The Drosophila insulin receptor (DInR) is required for photoreceptor-cell (R-cell) axons to find their way from the retina to the brain during development of the visual system. DInR functions as a guidance receptor for the adapter protein Dock/Nck. This function is independent of Chico, the Drosophila insulin receptor substrate (IRS) homolog.

Telemetry data storage systems technology for the Space Station Freedom era

NASA Technical Reports Server (NTRS)

Dalton, John T.

1989-01-01

This paper examines the requirements and functions of the telemetry-data recording and storage systems, and the data-storage-system technology projected for the Space Station, with particular attention given to the Space Optical Disk Recorder, an on-board storage subsystem based on 160 gigabit erasable optical disk units each capable of operating at 300 M bits per second. Consideration is also given to storage systems for ground transport recording, which include systems for data capture, buffering, processing, and delivery on the ground. These can be categorized as the first in-first out storage, the fast random-access storage, and the slow access with staging. Based on projected mission manifests and data rates, the worst case requirements were developed for these three storage architecture functions. The results of the analysis are presented.

Description of the SSF PMAD DC testbed control system data acquisition function

NASA Technical Reports Server (NTRS)

Baez, Anastacio N.; Mackin, Michael; Wright, Theodore

1992-01-01

The NASA LeRC in Cleveland, Ohio has completed the development and integration of a Power Management and Distribution (PMAD) DC Testbed. This testbed is a reduced scale representation of the end to end, sources to loads, Space Station Freedom Electrical Power System (SSF EPS). This unique facility is being used to demonstrate DC power generation and distribution, power management and control, and system operation techniques considered to be prime candidates for the Space Station Freedom. A key capability of the testbed is its ability to be configured to address system level issues in support of critical SSF program design milestones. Electrical power system control and operation issues like source control, source regulation, system fault protection, end-to-end system stability, health monitoring, resource allocation, and resource management are being evaluated in the testbed. The SSF EPS control functional allocation between on-board computers and ground based systems is evolving. Initially, ground based systems will perform the bulk of power system control and operation. The EPS control system is required to continuously monitor and determine the current state of the power system. The DC Testbed Control System consists of standard controllers arranged in a hierarchical and distributed architecture. These controllers provide all the monitoring and control functions for the DC Testbed Electrical Power System. Higher level controllers include the Power Management Controller, Load Management Controller, Operator Interface System, and a network of computer systems that perform some of the SSF Ground based Control Center Operation. The lower level controllers include Main Bus Switch Controllers and Photovoltaic Controllers. Power system status information is periodically provided to the higher level controllers to perform system control and operation. The data acquisition function of the control system is distributed among the various levels of the hierarchy. Data requirements are dictated by the control system algorithms being implemented at each level. A functional description of the various levels of the testbed control system architecture, the data acquisition function, and the status of its implementationis presented.

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

NASA Technical Reports Server (NTRS)

Patterson, Jonathan D.; Breckenridge, Jonathan T.; Johnson, Stephen B.

2013-01-01

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

The Generic Resolution Advisor and Conflict Evaluator (GRACE) for Detect-And-Avoid Systems

NASA Technical Reports Server (NTRS)

Abramson, Michael; Refai, Mohamad; Santiago, Confesor

2017-01-01

Java Architecture for Detect-And-Avoid (DAA) Extensibility and Modeling (JADEM) was developed at NASA Ames Research Center as a research and modeling tool for Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS). UAS will be required to have DAA systems in order to fulfill the regulatory requirement to remain well clear'' of other traffic. JADEM supports research on technological requirements and Minimum Operational Performance Standards (MOPS) for UAS DAA systems by providing a flexible and extensible software platform that includes models and algorithms for all major DAA functions. This paper describes one of these algorithms, the Generic Resolution Advisor and Conflict Evaluator (GRACE). GRACE supports two core DAA functions: threat evaluation and guidance. GRACE is generic in the sense that it is designed to work with any aircraft or sensor type (both cooperative and non-cooperative), and to be used in various applications and DAA guidance concepts, thus supporting evolving MOPS requirements and research. GRACE combines flexibility, robustness, and computational efficiency. It has modest memory requirements and can handle multiple cooperative and noncooperative intruders. GRACE has been used as a core JADEM component in several real-time and fast-time experiments, including human-in-the-loop simulations and live flight tests.

Minimal-Approximation-Based Decentralized Backstepping Control of Interconnected Time-Delay Systems.

PubMed

Choi, Yun Ho; Yoo, Sung Jin

2016-12-01

A decentralized adaptive backstepping control design using minimal function approximators is proposed for nonlinear large-scale systems with unknown unmatched time-varying delayed interactions and unknown backlash-like hysteresis nonlinearities. Compared with existing decentralized backstepping methods, the contribution of this paper is to design a simple local control law for each subsystem, consisting of an actual control with one adaptive function approximator, without requiring the use of multiple function approximators and regardless of the order of each subsystem. The virtual controllers for each subsystem are used as intermediate signals for designing a local actual control at the last step. For each subsystem, a lumped unknown function including the unknown nonlinear terms and the hysteresis nonlinearities is derived at the last step and is estimated by one function approximator. Thus, the proposed approach only uses one function approximator to implement each local controller, while existing decentralized backstepping control methods require the number of function approximators equal to the order of each subsystem and a calculation of virtual controllers to implement each local actual controller. The stability of the total controlled closed-loop system is analyzed using the Lyapunov stability theorem.

Controlled ecological life support system higher plant flight experiments

NASA Technical Reports Server (NTRS)

Tibbitts, T. W.; Wheeler, R. M.

1984-01-01

Requirements for spaceflight experments which involve higher plants were determined. The plants are studied for use in controlled ecological life support systems (CELSS). Two categories of research requirements are discussed: (1) the physical needs which include nutrient, water and gas exchange requirements; (2) the biological and physiological functions which affect plants in zero gravity environments. Physical problems studies are given the priority since they affect all biological experiments.

Automatic Data Processing Equipment (ADPE) acquisition plan for the medical sciences

NASA Technical Reports Server (NTRS)

1979-01-01

An effective mechanism for meeting the SLSD/MSD data handling/processing requirements for Shuttle is discussed. The ability to meet these requirements depends upon the availability of a general purpose high speed digital computer system. This system is expected to implement those data base management and processing functions required across all SLSD/MSD programs during training, laboratory operations/analysis, simulations, mission operations, and post mission analysis/reporting.

MASTER TELEVISION ANTENNA SYSTEM.

ERIC Educational Resources Information Center

Rhode Island State Dept. of Education, Providence.

SPECIFICATIONS FOR THE FURNISHING AND INSTALLATION OF TELEVISION MASTER ANTENNA SYSTEMS FOR SECONDARY AND ELEMENTARY SCHOOLS ARE GIVEN. CONTRACTOR REQUIREMENTS, EQUIPMENT, PERFORMANCE STANDARDS, AND FUNCTIONS ARE DESCRIBED. (MS)

The Evolvable Advanced Multi-Mission Operations System (AMMOS): Making Systems Interoperable

NASA Technical Reports Server (NTRS)

Ko, Adans Y.; Maldague, Pierre F.; Bui, Tung; Lam, Doris T.; McKinney, John C.

2010-01-01

The Advanced Multi-Mission Operations System (AMMOS) provides a common Mission Operation System (MOS) infrastructure to NASA deep space missions. The evolution of AMMOS has been driven by two factors: increasingly challenging requirements from space missions, and the emergence of new IT technology. The work described in this paper focuses on three key tasks related to IT technology requirements: first, to eliminate duplicate functionality; second, to promote the use of loosely coupled application programming interfaces, text based file interfaces, web-based frameworks and integrated Graphical User Interfaces (GUI) to connect users, data, and core functionality; and third, to build, develop, and deploy AMMOS services that are reusable, agile, adaptive to project MOS configurations, and responsive to industrially endorsed information technology standards.

Nursing Information Systems Requirements: A Milestone for Patient Outcome and Patient Safety Improvement.

PubMed

Farzandipour, Mehrdad; Meidani, Zahra; Riazi, Hossein; Sadeqi Jabali, Monireh

2016-12-01

Considering the integral role of understanding users' requirements in information system success, this research aimed to determine functional requirements of nursing information systems through a national survey. Delphi technique method was applied to conduct this study through three phases: focus group method modified Delphi technique and classic Delphi technique. A cross-sectional study was conducted to evaluate the proposed requirements within 15 general hospitals in Iran. Forty-three of 76 approved requirements were clinical, and 33 were administrative ones. Nurses' mean agreements for clinical requirements were higher than those of administrative requirements; minimum and maximum means of clinical requirements were 3.3 and 3.88, respectively. Minimum and maximum means of administrative requirements were 3.1 and 3.47, respectively. Research findings indicated that those information system requirements that support nurses in doing tasks including direct care, medicine prescription, patient treatment management, and patient safety have been the target of special attention. As nurses' requirements deal directly with patient outcome and patient safety, nursing information systems requirements should not only address automation but also nurses' tasks and work processes based on work analysis.

Data System Implications Derived from User Application Requirements for Satellite Data

NASA Technical Reports Server (NTRS)

Neiers, J.

1979-01-01

An investigation of the data system needs as driven by users of space acquired Earth observation data is documented. Two major categories of users, operational and research, are identified. Limiting data acquisition alleviates some of the delays in processing thus improving timeliness of the delivered product. Trade offs occur between timeliness and data distribution costs, and between data storage and reprocessing. The complexity of the data system requirements to apply space data to users' needs is such that no single analysis suffices to design and implement the optimum system. A series of iterations is required with analyses of the salient problems in a general way, followed by a limited implementation of benefit to some users with a continual upgrade in system capacity, functions, and applications served. The resulting most important requirement for the data system is flexibility to accommodate changing requirements as the system is implemented.

Phase structure rewrite systems in information retrieval

NASA Technical Reports Server (NTRS)

Klingbiel, P. H.

1985-01-01

Operational level automatic indexing requires an efficient means of normalizing natural language phrases. Subject switching requires an efficient means of translating one set of authorized terms to another. A phrase structure rewrite system called a Lexical Dictionary is explained that performs these functions. Background, operational use, other applications and ongoing research are explained.

Definition and means of maintaining the criticality detectors and alarms portion of the PFP safety envelope

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

White, W.F.

The purpose of this document is to provide the definition and means of maintaining the Safety Envelope (SE) related to the Criticality Alarm System (CAS). This document provides amplification of the Limiting Condition for Operation (LCO) described in the Plutonium Finishing Plant (PFP) Operational Safety Requirements (OSR), WHC-SD-CP-OSR-010, Rev. 0, 1994, Section 3.1.2, Criticality Detectors and Alarms. This document, with its appendices, provides the following: (1) System functional requirements for determining system operability (Section 3); (2) A list of annotated system block diagrams which indicate the safety envelope boundaries (Appendix C); (3) A list of the Safety Class 1 andmore » 2 Safety Envelope (SC-1/2 SE) equipment for input into the Master Component Index (Appendix B); (4) Functional requirements for individual SC-1/2 SE components, including appropriate setpoints and process parameters (Section 6 and Appendix A); (5) A list of the operational, maintenance and surveillance procedures necessary to operate and maintain the SC-1/2 SE components as required by the LCO (Section 6 and Appendix A).« less

Representation and matching of knowledge to design digital systems

NASA Technical Reports Server (NTRS)

Jones, J. U.; Shiva, S. G.

1988-01-01

A knowledge-based expert system is described that provides an approach to solve a problem requiring an expert with considerable domain expertise and facts about available digital hardware building blocks. To design digital hardware systems from their high level VHDL (Very High Speed Integrated Circuit Hardware Description Language) representation to their finished form, a special data representation is required. This data representation as well as the functioning of the overall system is described.

Joint Vision 2010: Developing the System of Systems

DTIC Science & Technology

1998-04-01

The system engineering model, as described in Defense Acquisition University Coursebook , consists of five main parts and three feedback loops.4 The... physical architecture is defined and each subsystem developed. In the case of JV2010’s “system of systems” the subsystems would be the items...verify that each requirement can be traced to a system function. The purpose of the design loop is to ensure all the functions can be traced to physical

Magnetohydrodynamics (MHD) Engineering Test Facility (ETF) 200 MWe power plant. Design Requirements Document (DRD)

NASA Technical Reports Server (NTRS)

Rigo, H. S.; Bercaw, R. W.; Burkhart, J. A.; Mroz, T. S.; Bents, D. J.; Hatch, A. M.

1981-01-01

A description and the design requirements for the 200 MWe (nominal) net output MHD Engineering Test Facility (ETF) Conceptual Design, are presented. Performance requirements for the plant are identified and process conditions are indicated at interface stations between the major systems comprising the plant. Also included are the description, functions, interfaces and requirements for each of these major systems. The lastest information (1980-1981) from the MHD technology program are integrated with elements of a conventional steam electric power generating plant.

Integrated Workforce Modeling System

NASA Technical Reports Server (NTRS)

Moynihan, Gary P.

2000-01-01

There are several computer-based systems, currently in various phases of development at KSC, which encompass some component, aspect, or function of workforce modeling. These systems may offer redundant capabilities and/or incompatible interfaces. A systems approach to workforce modeling is necessary in order to identify and better address user requirements. This research has consisted of two primary tasks. Task 1 provided an assessment of existing and proposed KSC workforce modeling systems for their functionality and applicability to the workforce planning function. Task 2 resulted in the development of a proof-of-concept design for a systems approach to workforce modeling. The model incorporates critical aspects of workforce planning, including hires, attrition, and employee development.

A premeiotic function for boule in the planarian Schmidtea mediterranea.

PubMed

Iyer, Harini; Issigonis, Melanie; Sharma, Prashant P; Extavour, Cassandra G; Newmark, Phillip A

2016-06-21

Mutations in Deleted in Azoospermia (DAZ), a Y chromosome gene, are an important cause of human male infertility. DAZ is found exclusively in primates, limiting functional studies of this gene to its homologs: boule, required for meiotic progression of germ cells in invertebrate model systems, and Daz-like (Dazl), required for early germ cell maintenance in vertebrates. Dazl is believed to have acquired its premeiotic role in a vertebrate ancestor following the duplication and functional divergence of the single-copy gene boule. However, multiple homologs of boule have been identified in some invertebrates, raising the possibility that some of these genes may play other roles, including a premeiotic function. Here we identify two boule paralogs in the freshwater planarian Schmidtea mediterranea Smed-boule1 is necessary for meiotic progression of male germ cells, similar to the known function of boule in invertebrates. By contrast, Smed-boule2 is required for the maintenance of early male germ cells, similar to vertebrate Dazl To examine if Boule2 may be functionally similar to vertebrate Dazl, we identify and functionally characterize planarian homologs of human DAZL/DAZ-interacting partners and DAZ family mRNA targets. Finally, our phylogenetic analyses indicate that premeiotic functions of planarian boule2 and vertebrate Dazl evolved independently. Our study uncovers a premeiotic role for an invertebrate boule homolog and offers a tractable invertebrate model system for studying the premeiotic functions of the DAZ protein family.

Proximal—distal pattern formation in Drosophila: cell autonomous requirement for Distal-less gene activity in limb development

PubMed Central

Cohen, Stephen M.; Jürgens, Gerd

1989-01-01

Limb development in the Drosophila embryo requires a pattern-forming system to organize positional information along the proximal–distal axis of the limb. This system must function in the context of the well characterized anterior–posterior and dorsal–ventral pattern-forming systems that are required to organize the body plan of the embryo. By genetic criteria the Distal-less gene appears to play a central role in limb development. Lack-of-function Distal-less mutations cause the deletion of a specific subset of embryonic peripheral sense organs that represent the evolutionary remnants of larval limbs. Distal-less activity is also required in the imaginal discs for the development of adult limbs. This requirement is cell autonomous and region specific within the developing limb primordium. Production of genetically mosaic imaginal discs, in which clones of cells lack Distal-less activity, indicates the existence of an organized proximal–distal positional information in very young imaginal disc primordia. We suggest that this graded positional information may depend on the activity of the Distal-less gene. Images PMID:16453891

Functional and Software Considerations for Bibliographic Data Base Utilization.

ERIC Educational Resources Information Center

Cadwallader, Gouverneur

This is the fourth in a series of eight reports of a research study for the National Agricultural Library (NAL) on the effective utilization of bibliographic data bases in machine-readable form. It describes the general functional and software requirements of an NAL system using external sources of bibliographic data. Various system design…

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

Logistics Reduction and Repurposing Beyond Low Earth Orbit

NASA Technical Reports Server (NTRS)

Ewert, Michael K.; Broyan, James L., Jr.

2012-01-01

All human space missions, regardless of destination, require significant logistical mass and volume that is strongly proportional to mission duration. Anything that can be done to reduce initial mass and volume of supplies or reuse items that have been launched will be very valuable. Often, the logistical items require disposal and represent a trash burden. Logistics contributions to total mission architecture mass can be minimized by considering potential reuse using systems engineering analysis. In NASA's Advanced Exploration Systems "Logistics Reduction and Repurposing Project," various tasks will reduce the intrinsic mass of logistical packaging, enable reuse and repurposing of logistical packaging and carriers for other habitation, life support, crew health, and propulsion functions, and reduce or eliminate the nuisance aspects of trash at the same time. Repurposing reduces the trash burden and eliminates the need for hardware whose function can be provided by use of spent logistical items. However, these reuse functions need to be identified and built into future logical systems to enable them to effectively have a secondary function. These technologies and innovations will help future logistics systems to support multiple exploration missions much more efficiently.

System administrator`s guide to CDPS. Version 1.0

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

Didier, B.T.; Portwood, M.H.

The System Administrator`s Guide to CDPS is intended for those responsible for setting up and maintaining the hardware and software of a Common Mapping Standard (CMS) Date Production System (CDPS) installation. This guide assists the system administrator in performing typical administrative functions. It is not intended to replace the Ultrix Documentation Set that should be available for a DCPS installation. The Ultrix Documentation Set will be required to provide details on referenced Ultrix commands as well as procedures for performing Ultrix maintenance functions. There are six major sections in this guide. Section 1 introduces the system administrator to CDPS andmore » describes the assumptions that are made by this guide. Section 2 describes the CDPS platform configuration. Section 3 describes the platform preparation that is required to install the CDPS software. Section 4 describes the CPS software and its installation procedures. Section 5 describes the CDS software and its installation procedures. Section 6 describes various operation and maintenance procedures. Four appendices are also provided. Appendix A contains a list of used acronyms. Appendix B provides a terse description of common Ultrix commands that are used in administrative functions. Appendix C provides sample CPS and CDS configuration files. Appendix D provides a required list and a recommended list of Ultrix software subsets for installation on a CDPS platform.« less

Pseudosatellite technologies based on the use of functionally stable complexes of remote-piloted aircrafts

NASA Astrophysics Data System (ADS)

Mashkov, O. A.; Samborskiy, I. I.

2009-10-01

A bundle of papers dealing with functionally stable systems requires the necessity of analyzing of obtained results and their understanding in a general context of cybernetic's development and applications. Description of this field of science, main results and perspectives of the new theory of functionally stability of dynamical systems concerning the problem of remote-piloted aircrafts engineering using pseudosatellite technologies are proposed in the paper.

Tracking and data relay satellite system configuration and tradeoff study. Volume 4: TDRS system operation and control and telecommunications service system, part 1

NASA Technical Reports Server (NTRS)

1972-01-01

Major study areas treated in this volume are: 1) operations and control and 2) the telecommunication service system. The TDRS orbit selection, orbital deployment, ground station visibility, sequence of events from launch to final orbit position, and TDRS control center functions required for stationkeeping, repositioning, attitude control, and antenna pointing are briefly treated as part of the operations and control section. The last topic of this section concerns the operations required for efficiently providing the TDRSS user telecommunication services. The discussion treats functions of the GSFC control and data processing facility, ground station, and TDRS control center. The second major portion of this volume deals with the Telecommunication Service System (TSS) which consists of the ground station, TDRS communication equipment and the user transceiver. A summary of the requirements and objectives for the telecommunication services and a brief summary of the TSS capabilities is followed by communication system analysis, signal design, and equipment design. Finally, descriptions of the three TSS elements are presented.

Linear Actuator System for the NASA Docking System

NASA Technical Reports Server (NTRS)

Dick, Brandon; Oesch, Chris

2017-01-01

The Linear Actuator System (LAS) is a major sub-system within the NASA Docking System (NDS). The NDS Block 1 will be used on the Boeing Crew Space Transportation (CST-100) system to achieve docking with the International Space Station. Critical functions in the Soft Capture aspect of docking are performed by the LAS, which implements the Soft Impact Mating and Attenuation Concept (SIMAC). This paper describes the general function of the LAS, the system's key requirements and technical challenges, and the development and qualification approach for the system.

Failure Modes Effects and Criticality Analysis, an Underutilized Safety, Reliability, Project Management and Systems Engineering Tool

NASA Astrophysics Data System (ADS)

Mullin, Daniel Richard

2013-09-01

The majority of space programs whether manned or unmanned for science or exploration require that a Failure Modes Effects and Criticality Analysis (FMECA) be performed as part of their safety and reliability activities. This comes as no surprise given that FMECAs have been an integral part of the reliability engineer's toolkit since the 1950s. The reasons for performing a FMECA are well known including fleshing out system single point failures, system hazards and critical components and functions. However, in the author's ten years' experience as a space systems safety and reliability engineer, findings demonstrate that the FMECA is often performed as an afterthought, simply to meet contract deliverable requirements and is often started long after the system requirements allocation and preliminary design have been completed. There are also important qualitative and quantitative components often missing which can provide useful data to all of project stakeholders. These include; probability of occurrence, probability of detection, time to effect and time to detect and, finally, the Risk Priority Number. This is unfortunate as the FMECA is a powerful system design tool that when used effectively, can help optimize system function while minimizing the risk of failure. When performed as early as possible in conjunction with writing the top level system requirements, the FMECA can provide instant feedback on the viability of the requirements while providing a valuable sanity check early in the design process. It can indicate which areas of the system will require redundancy and which areas are inherently the most risky from the onset. Based on historical and practical examples, it is this author's contention that FMECAs are an immense source of important information for all involved stakeholders in a given project and can provide several benefits including, efficient project management with respect to cost and schedule, system engineering and requirements management, assembly integration and test (AI&T) and operations if applied early, performed to completion and updated along with system design.

Power processing systems for ion thrusters.

NASA Technical Reports Server (NTRS)

Herron, B. G.; Garth, D. R.; Finke, R. C.; Shumaker, H. A.

1972-01-01

The proposed use of ion thrusters to fulfill various communication satellite propulsion functions such as east-west and north-south stationkeeping, attitude control, station relocation and orbit raising, naturally leads to the requirement for lightweight, efficient and reliable thruster power processing systems. Collectively, the propulsion requirements dictate a wide range of thruster power levels and operational lifetimes, which must be matched by the power processing. This paper will discuss the status of such power processing systems, present system design alternatives and project expected near future power system performance.

49 CFR 229.139 - Sanitation, servicing requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 49 Transportation 4 2010-10-01 2010-10-01 false Sanitation, servicing requirements. 229.139... Cab Equipment § 229.139 Sanitation, servicing requirements. (a) The sanitation compartment of each... intended such that: (1) All mechanical systems shall function; (2) Water shall be present in sufficient...

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

Gledhill, Jonathan D.; Tozer, David J., E-mail: d.j.tozer@durham.ac.uk

Density scaling considerations are used to derive an exchange–correlation explicit density functional that is appropriate for the electron deficient side of the integer and which recovers the exact r → ∞ asymptotic behaviour of the exchange–correlation potential. The functional has an unconventional mathematical form with parameters that are system-dependent; the parameters for an N-electron system are determined in advance from generalised gradient approximation (GGA) calculations on the N- and (N − 1)-electron systems. Compared to GGA results, the functional yields similar exchange–correlation energies, but HOMO energies that are an order of magnitude closer to the negative of the vertical ionisationmore » potential; for anions, the HOMO energies are negative, as required. Rydberg excitation energies are also notably improved and the exchange–correlation potential is visibly lowered towards the near-exact potential. Further development is required to improve valence excitations, static isotropic polarisabilities, and the shape of the potential in non-asymptotic regions. The functional is fundamentally different to conventional approximations.« less

Mirror neurons and imitation: a computationally guided review.

PubMed

Oztop, Erhan; Kawato, Mitsuo; Arbib, Michael

2006-04-01

Neurophysiology reveals the properties of individual mirror neurons in the macaque while brain imaging reveals the presence of 'mirror systems' (not individual neurons) in the human. Current conceptual models attribute high level functions such as action understanding, imitation, and language to mirror neurons. However, only the first of these three functions is well-developed in monkeys. We thus distinguish current opinions (conceptual models) on mirror neuron function from more detailed computational models. We assess the strengths and weaknesses of current computational models in addressing the data and speculations on mirror neurons (macaque) and mirror systems (human). In particular, our mirror neuron system (MNS), mental state inference (MSI) and modular selection and identification for control (MOSAIC) models are analyzed in more detail. Conceptual models often overlook the computational requirements for posited functions, while too many computational models adopt the erroneous hypothesis that mirror neurons are interchangeable with imitation ability. Our meta-analysis underlines the gap between conceptual and computational models and points out the research effort required from both sides to reduce this gap.

Hypotonia

MedlinePlus

... will include a detailed examination of the nervous system and muscle function. In most cases, a neurologist (specialist in ... require ongoing care and support. Alternative Names Decreased muscle tone; Floppy infant ... Central nervous system and peripheral nervous system References Burnette WB. Hypotonic ( ...

Telerobotic on-orbit remote fluid resupply system

NASA Technical Reports Server (NTRS)

1990-01-01

The development of a telerobotic on-orbit fluid resupply demonstration system is described. A fluid transfer demonstration system was developed which functionally simulates operations required to remotely transfer fluids (liquids or gases) from a servicing spacecraft to a receiving spacecraft through the use of telerobotic manipulations. The fluid system is representative of systems used by current or planned spacecraft and propulsion stages requiring on-orbit remote resupply. The system was integrated with an existing MSFC remotely controlled manipulator arm to mate/demate couplings for demonstration and evaluation of a complete remotely operated fluid transfer system.

State analysis requirements database for engineering complex embedded systems

NASA Technical Reports Server (NTRS)

Bennett, Matthew B.; Rasmussen, Robert D.; Ingham, Michel D.

2004-01-01

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

Ageing and the immune system: focus on macrophages.

PubMed

Linehan, E; Fitzgerald, D C

2015-03-01

A fully functioning immune system is essential in order to maintain good health. However, the immune system deteriorates with advancing age, and this contributes to increased susceptibility to infection, autoimmunity, and cancer in the older population. Progress has been made in identifying age-related defects in the adaptive immune system. In contrast, relatively little research has been carried out on the impact of ageing on the innate immune response. This area requires further research as the innate immune system plays a crucial role in protection against infection and represents a first line of defence. Macrophages are central effector cells of the innate immune system and have many diverse functions. As a result, age-related impairments in macrophage function are likely to have important consequences for the health of the older population. It has been reported that ageing in macrophages impacts on many processes including toll-like receptor signalling, polarisation, phagocytosis, and wound repair. A detailed understanding of the impact of ageing on macrophages is required in order to develop therapeutics that will boost immune responses in the older population.

Composing, Analyzing and Validating Software Models

NASA Astrophysics Data System (ADS)

Sheldon, Frederick T.

1998-10-01

This research has been conducted at the Computational Sciences Division of the Information Sciences Directorate at Ames Research Center (Automated Software Engineering Grp). The principle work this summer has been to review and refine the agenda that were carried forward from last summer. Formal specifications provide good support for designing a functionally correct system, however they are weak at incorporating non-functional performance requirements (like reliability). Techniques which utilize stochastic Petri nets (SPNs) are good for evaluating the performance and reliability for a system, but they may be too abstract and cumbersome from the stand point of specifying and evaluating functional behavior. Therefore, one major objective of this research is to provide an integrated approach to assist the user in specifying both functionality (qualitative: mutual exclusion and synchronization) and performance requirements (quantitative: reliability and execution deadlines). In this way, the merits of a powerful modeling technique for performability analysis (using SPNs) can be combined with a well-defined formal specification language. In doing so, we can come closer to providing a formal approach to designing a functionally correct system that meets reliability and performance goals.

Composing, Analyzing and Validating Software Models

NASA Technical Reports Server (NTRS)

Sheldon, Frederick T.

1998-01-01

This research has been conducted at the Computational Sciences Division of the Information Sciences Directorate at Ames Research Center (Automated Software Engineering Grp). The principle work this summer has been to review and refine the agenda that were carried forward from last summer. Formal specifications provide good support for designing a functionally correct system, however they are weak at incorporating non-functional performance requirements (like reliability). Techniques which utilize stochastic Petri nets (SPNs) are good for evaluating the performance and reliability for a system, but they may be too abstract and cumbersome from the stand point of specifying and evaluating functional behavior. Therefore, one major objective of this research is to provide an integrated approach to assist the user in specifying both functionality (qualitative: mutual exclusion and synchronization) and performance requirements (quantitative: reliability and execution deadlines). In this way, the merits of a powerful modeling technique for performability analysis (using SPNs) can be combined with a well-defined formal specification language. In doing so, we can come closer to providing a formal approach to designing a functionally correct system that meets reliability and performance goals.

Definition study of land/sea civil user navigational location monitoring systems for NAVSTAR GPS: User requirements and systems concepts

NASA Technical Reports Server (NTRS)

Devito, D. M.

1981-01-01

A low-cost GPS civil-user mobile terminal whose purchase cost is substantially an order of magnitude less than estimates for the military counterpart is considered with focus on ground station requirements for position monitoring of civil users requiring this capability and the civil user navigation and location-monitoring requirements. Existing survey literature was examined to ascertain the potential users of a low-cost NAVSTAR receiver and to estimate their number, function, and accuracy requirements. System concepts are defined for low cost user equipments for in-situ navigation and the retransmission of low data rate positioning data via a geostationary satellite to a central computing facility.

A system architecture for a planetary rover

NASA Technical Reports Server (NTRS)

Smith, D. B.; Matijevic, J. R.

1989-01-01

Each planetary mission requires a complex space vehicle which integrates several functions to accomplish the mission and science objectives. A Mars Rover is one of these vehicles, and extends the normal spacecraft functionality with two additional functions: surface mobility and sample acquisition. All functions are assembled into a hierarchical and structured format to understand the complexities of interactions between functions during different mission times. It can graphically show data flow between functions, and most importantly, the necessary control flow to avoid unambiguous results. Diagrams are presented organizing the functions into a structured, block format where each block represents a major function at the system level. As such, there are six blocks representing telecomm, power, thermal, science, mobility and sampling under a supervisory block called Data Management/Executive. Each block is a simple collection of state machines arranged into a hierarchical order very close to the NASREM model for Telerobotics. Each layer within a block represents a level of control for a set of state machines that do the three primary interface functions: command, telemetry, and fault protection. This latter function is expanded to include automatic reactions to the environment as well as internal faults. Lastly, diagrams are presented that trace the system operations involved in moving from site to site after site selection. The diagrams clearly illustrate both the data and control flows. They also illustrate inter-block data transfers and a hierarchical approach to fault protection. This systems architecture can be used to determine functional requirements, interface specifications and be used as a mechanism for grouping subsystems (i.e., collecting groups of machines, or blocks consistent with good and testable implementations).

Functional Foods Baseline and Requirements Analysis

NASA Technical Reports Server (NTRS)

Cooper, M. R.; Bermudez-Aguirre, L. D.; Douglas, G.

2015-01-01

Current spaceflight foods were evaluated to determine if their nutrient profile supports positioning as a functional food and if the stability of the bioactive compound within the food matrix over an extended shelf-life correlated with the expected storage duration during the mission. Specifically, the research aims were: Aim A. To determine the amount of each nutrient in representative spaceflight foods immediately after processing and at predetermined storage time to establish the current nutritional state. Aim B. To identify the requirements to develop foods that stabilize these nutrients such that required concentrations are maintained in the space food system throughout long duration missions (up to five years). Aim C. To coordinate collaborations with health and performance groups that may require functional foods as a countermeasure.

A Cognitive System Model for Human/Automation Dynamics in Airspace Management

NASA Technical Reports Server (NTRS)

Corker, Kevin M.; Pisanich, Gregory; Lebacqz, J. Victor (Technical Monitor)

1997-01-01

NASA has initiated a significant thrust of research and development focused on providing the flight crew and air traffic managers automation aids to increase capacity in en route and terminal area operations through the use of flexible, more fuel-efficient routing, while improving the level of safety in commercial carrier operations. In that system development, definition of cognitive requirements for integrated multi-operator dynamic aiding systems is fundamental. In order to support that cognitive function definition, we have extended the Man Machine Integrated Design and Analysis System (MIDAS) to include representation of multiple cognitive agents (both human operators and intelligent aiding systems) operating aircraft, airline operations centers and air traffic control centers in the evolving airspace. The demands of this application require representation of many intelligent agents sharing world-models, and coordinating action/intention with cooperative scheduling of goals and actions in a potentially unpredictable world of operations. The MIDAS operator models have undergone significant development in order to understand the requirements for operator aiding and the impact of that aiding in the complex nondeterminate system of national airspace operations. The operator model's structure has been modified to include attention functions, action priority, and situation assessment. The cognitive function model has been expanded to include working memory operations including retrieval from long-term store, interference, visual-motor and verbal articulatory loop functions, and time-based losses. The operator's activity structures have been developed to include prioritization and interruption of multiple parallel activities among multiple operators, to provide for anticipation (knowledge of the intention and action of remote operators), and to respond to failures of the system and other operators in the system in situation-specific paradigms. The model's internal representation has been be modified so that multiple, autonomous sets of equipment will function in a scenario as the single equipment sets do now. In order to support the analysis requirements with multiple items of equipment, it is necessary for equipment to access the state of other equipment objects at initialization time (a radar object may need to access the position and speed of aircraft in its area, for example), and as a function of perception and sensor system interaction. The model has been improved to include multiple world-states as a function of equipment am operator interaction. The model has been used -1o predict the impact of warning and alert zones in aircraft operation, and, more critic-ally, the interaction of flight-deck based warning mechanisms and air traffic controller action in response to ground-based conflict prediction and alerting systems. In this operation, two operating systems provide alerting to two autonomous, but linked sets of operators, whose view of the system and whose dynamics in response are radically different. System stability and operator action was predicted using the MIDAS model.

14 CFR 25.1705 - Systems and functions: EWIS.

Code of Federal Regulations, 2011 CFR

2011-01-01

... showing compliance with the applicable requirements for that system. (b) For systems to which the following rules apply, the components of EWIS associated with those systems must be considered an integral part of that system or systems and must be considered in showing compliance with the applicable...

14 CFR 25.1705 - Systems and functions: EWIS.

Code of Federal Regulations, 2014 CFR

2014-01-01

... showing compliance with the applicable requirements for that system. (b) For systems to which the following rules apply, the components of EWIS associated with those systems must be considered an integral part of that system or systems and must be considered in showing compliance with the applicable...

14 CFR 25.1705 - Systems and functions: EWIS.

Code of Federal Regulations, 2012 CFR

2012-01-01

... showing compliance with the applicable requirements for that system. (b) For systems to which the following rules apply, the components of EWIS associated with those systems must be considered an integral part of that system or systems and must be considered in showing compliance with the applicable...

14 CFR 25.1705 - Systems and functions: EWIS.

Code of Federal Regulations, 2013 CFR

2013-01-01

... showing compliance with the applicable requirements for that system. (b) For systems to which the following rules apply, the components of EWIS associated with those systems must be considered an integral part of that system or systems and must be considered in showing compliance with the applicable...

14 CFR 417.303 - Command control system requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... flight termination system used for each launch. (f) Electromagnetic interference. Each command control system component must function within the electromagnetic environment to which it is exposed. A command... must prevent electromagnetic interference. (g) Command transmitter failover. A command control system...

14 CFR 417.303 - Command control system requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... flight termination system used for each launch. (f) Electromagnetic interference. Each command control system component must function within the electromagnetic environment to which it is exposed. A command... must prevent electromagnetic interference. (g) Command transmitter failover. A command control system...

14 CFR 417.303 - Command control system requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... flight termination system used for each launch. (f) Electromagnetic interference. Each command control system component must function within the electromagnetic environment to which it is exposed. A command... must prevent electromagnetic interference. (g) Command transmitter failover. A command control system...

14 CFR 417.303 - Command control system requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... flight termination system used for each launch. (f) Electromagnetic interference. Each command control system component must function within the electromagnetic environment to which it is exposed. A command... must prevent electromagnetic interference. (g) Command transmitter failover. A command control system...

14 CFR 417.303 - Command control system requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... flight termination system used for each launch. (f) Electromagnetic interference. Each command control system component must function within the electromagnetic environment to which it is exposed. A command... must prevent electromagnetic interference. (g) Command transmitter failover. A command control system...

SCOS 2: ESA's new generation of mission control system

NASA Technical Reports Server (NTRS)

Jones, M.; Head, N. C.; Keyte, K.; Howard, P.; Lynenskjold, S.

1994-01-01

New mission-control infrastructure is currently being developed by ESOC, which will constitute the second generation of the Spacecraft Control Operations system (SCOS 2). The financial, functional and strategic requirements lying behind the new development are explained. The SCOS 2 approach is described. The technological implications of these approaches is described: in particular it is explained how this leads to the use of object oriented techniques to provide the required 'building block' approach. The paper summarizes the way in which the financial, functional and strategic requirements have been met through this combination of solutions. Finally, the paper outlines the development process to date, noting how risk reduction was achieved in the approach to new technologies and summarizes the current status future plans.

Network operating system focus technology

NASA Technical Reports Server (NTRS)

1985-01-01

An activity structured to provide specific design requirements and specifications for the Space Station Data Management System (DMS) Network Operating System (NOS) is outlined. Examples are given of the types of supporting studies and implementation tasks presently underway to realize a DMS test bed capability to develop hands-on understanding of NOS requirements as driven by actual subsystem test beds participating in the overall Johnson Space Center test bed program. Classical operating system elements and principal NOS functions are listed.

Use of heat-pressed leucite reinforced porcelain in "difficult" veneer cases: a clinical report.

PubMed

Rouse, J S

1996-11-01

Two clinical situations are presented where a heat-pressed leucite reinforced ceramic veneer system was used. For these situations the system was advantageous when veneers (1) required bulk or variable thicknesses or (2) were under load from function and parafunctional activity. This porcelain veneer system addressed some of the concerns associated with standard feldspathic porcelain and castglass systems. Practitioners should consider its use for situations that require a stronger veneer material.

System Analysis Applied to Autonomy: Application to Human-Rated Lunar/Mars Landers

NASA Technical Reports Server (NTRS)

Young, Larry A.

2006-01-01

System analysis is an essential technical discipline for the modern design of spacecraft and their associated missions. Specifically, system analysis is a powerful aid in identifying and prioritizing the required technologies needed for mission and/or vehicle development efforts. Maturation of intelligent systems technologies, and their incorporation into spacecraft systems, are dictating the development of new analysis tools, and incorporation of such tools into existing system analysis methodologies, in order to fully capture the trade-offs of autonomy on vehicle and mission success. A "system analysis of autonomy" methodology will be outlined and applied to a set of notional human-rated lunar/Mars lander missions toward answering these questions: 1. what is the optimum level of vehicle autonomy and intelligence required? and 2. what are the specific attributes of an autonomous system implementation essential for a given surface lander mission/application in order to maximize mission success? Future human-rated lunar/Mars landers, though nominally under the control of their crew, will, nonetheless, be highly automated systems. These automated systems will range from mission/flight control functions, to vehicle health monitoring and prognostication, to life-support and other "housekeeping" functions. The optimum degree of autonomy afforded to these spacecraft systems/functions has profound implications from an exploration system architecture standpoint.

Toward a Dynamically Reconfigurable Computing and Communication System for Small Spacecraft

NASA Technical Reports Server (NTRS)

Kifle, Muli; Andro, Monty; Tran, Quang K.; Fujikawa, Gene; Chu, Pong P.

2003-01-01

Future science missions will require the use of multiple spacecraft with multiple sensor nodes autonomously responding and adapting to a dynamically changing space environment. The acquisition of random scientific events will require rapidly changing network topologies, distributed processing power, and a dynamic resource management strategy. Optimum utilization and configuration of spacecraft communications and navigation resources will be critical in meeting the demand of these stringent mission requirements. There are two important trends to follow with respect to NASA's (National Aeronautics and Space Administration) future scientific missions: the use of multiple satellite systems and the development of an integrated space communications network. Reconfigurable computing and communication systems may enable versatile adaptation of a spacecraft system's resources by dynamic allocation of the processor hardware to perform new operations or to maintain functionality due to malfunctions or hardware faults. Advancements in FPGA (Field Programmable Gate Array) technology make it possible to incorporate major communication and network functionalities in FPGA chips and provide the basis for a dynamically reconfigurable communication system. Advantages of higher computation speeds and accuracy are envisioned with tremendous hardware flexibility to ensure maximum survivability of future science mission spacecraft. This paper discusses the requirements, enabling technologies, and challenges associated with dynamically reconfigurable space communications systems.

Space Station Food System

NASA Technical Reports Server (NTRS)

Thurmond, Beverly A.; Gillan, Douglas J.; Perchonok, Michele G.; Marcus, Beth A.; Bourland, Charles T.

1986-01-01

A team of engineers and food scientists from NASA, the aerospace industry, food companies, and academia are defining the Space Station Food System. The team identified the system requirements based on an analysis of past and current space food systems, food systems from isolated environment communities that resemble Space Station, and the projected Space Station parameters. The team is resolving conflicts among requirements through the use of trade-off analyses. The requirements will give rise to a set of specifications which, in turn, will be used to produce concepts. Concept verification will include testing of prototypes, both in 1-g and microgravity. The end-item specification provides an overall guide for assembling a functional food system for Space Station.

Tank Monitoring and Document control System (TMACS) As Built Software Design Document

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

GLASSCOCK, J.A.

This document describes the software design for the Tank Monitor and Control System (TMACS). This document captures the existing as-built design of TMACS as of November 1999. It will be used as a reference document to the system maintainers who will be maintaining and modifying the TMACS functions as necessary. The heart of the TMACS system is the ''point-processing'' functionality where a sample value is received from the field sensors and the value is analyzed, logged, or alarmed as required. This Software Design Document focuses on the point-processing functions.

Parameter Transient Behavior Analysis on Fault Tolerant Control System

NASA Technical Reports Server (NTRS)

Belcastro, Christine (Technical Monitor); Shin, Jong-Yeob

2003-01-01

In a fault tolerant control (FTC) system, a parameter varying FTC law is reconfigured based on fault parameters estimated by fault detection and isolation (FDI) modules. FDI modules require some time to detect fault occurrences in aero-vehicle dynamics. This paper illustrates analysis of a FTC system based on estimated fault parameter transient behavior which may include false fault detections during a short time interval. Using Lyapunov function analysis, the upper bound of an induced-L2 norm of the FTC system performance is calculated as a function of a fault detection time and the exponential decay rate of the Lyapunov function.

A requirements index for information processing in hospitals.

PubMed

Ammenwerth, E; Buchauer, A; Haux, R

2002-01-01

Reference models describing typical information processing requirements in hospitals do not currently exist. This leads to high hospital information system (HIS) management expenses, for example, during tender processes for the acquisition of software application programs. Our aim was, therefore, to develop a comprehensive, lasting, technology-independent, and sufficiently detailed index of requirements for information processing in hospitals in order to reduce respective expenses. Two-dozen German experts established an index of requirements for information processing in university hospitals. This was done in a consensus-based, top-down, cyclic manner. Each functional requirement was derived from information processing functions and sub-functions of a hospital. The result is the first official German version of a requirements index, containing 233 functional requirements and 102 function-independent requirements, focusing on German needs. The functional requirements are structured according to the primary care process from admission to discharge and supplemented by requirements for handling patient records, work organization and resource planning, hospital management, research and education. Both the German version and its English translation are available in the Internet. The index of requirements contains general information processing requirements in hospitals which are formulated independent of information processing tools, or of HIS architectures. It aims at supporting HIS management, especially HIS strategic planning, HIS evaluation, and tender processes. The index can be regarded as a draft, which must, however, be refined according to the specific aims of a particular project. Although focused on German needs, we expect that it can also be useful in other countries. The high amount of interest shown for the index supports its usefulness.

Degree Audit Systems: Are They Worth It?

ERIC Educational Resources Information Center

Johns, Virginia

2006-01-01

A lot of various degree audit systems are available on the market and most often they have similar features such as the functionality they each provide, the technical platforms upon which they operate, their requirements for interfacing with the local SIS, the ease of use, and the level of effort required to implement and operate. However, the…

Planarian homologs of netrin and netrin receptor are required for proper regeneration of the central nervous system and the maintenance of nervous system architecture.

PubMed

Cebrià, Francesc; Newmark, Phillip A

2005-08-01

Conserved axon guidance mechanisms are essential for proper wiring of the nervous system during embryogenesis; however, the functions of these cues in adults and during regeneration remain poorly understood. Because freshwater planarians can regenerate a functional central nervous system (CNS) from almost any portion of their body, they are useful models in which to study the roles of guidance cues during neural regeneration. Here, we characterize two netrin homologs and one netrin receptor family member from Schmidtea mediterranea. RNAi analyses indicate that Smed-netR (netrin receptor) and Smed-netrin2 are required for proper CNS regeneration and that Smed-netR may mediate the response to Smed-netrin2. Remarkably, Smed-netR and Smed-netrin2 are also required in intact planarians to maintain the proper patterning of the CNS. These results suggest a crucial role for guidance cues, not only in CNS regeneration but also in maintenance of neural architecture.

On reliable control system designs. Ph.D. Thesis; [actuators

NASA Technical Reports Server (NTRS)

Birdwell, J. D.

1978-01-01

A mathematical model for use in the design of reliable multivariable control systems is discussed with special emphasis on actuator failures and necessary actuator redundancy levels. The model consists of a linear time invariant discrete time dynamical system. Configuration changes in the system dynamics are governed by a Markov chain that includes transition probabilities from one configuration state to another. The performance index is a standard quadratic cost functional, over an infinite time interval. The actual system configuration can be deduced with a one step delay. The calculation of the optimal control law requires the solution of a set of highly coupled Riccati-like matrix difference equations. Results can be used for off-line studies relating the open loop dynamics, required performance, actuator mean time to failure, and functional or identical actuator redundancy, with and without feedback gain reconfiguration strategies.

On-board multispectral classification study

NASA Technical Reports Server (NTRS)

Ewalt, D.

1979-01-01

The factors relating to onboard multispectral classification were investigated. The functions implemented in ground-based processing systems for current Earth observation sensors were reviewed. The Multispectral Scanner, Thematic Mapper, Return Beam Vidicon, and Heat Capacity Mapper were studied. The concept of classification was reviewed and extended from the ground-based image processing functions to an onboard system capable of multispectral classification. Eight different onboard configurations, each with varying amounts of ground-spacecraft interaction, were evaluated. Each configuration was evaluated in terms of turnaround time, onboard processing and storage requirements, geometric and classification accuracy, onboard complexity, and ancillary data required from the ground.

A real time spectrum to dose conversion system

NASA Technical Reports Server (NTRS)

Farmer, B. J.; Johnson, J. H.; Bagwell, R. G.

1972-01-01

A system has been developed which permits the determination of dose in real time or near real time directly from the pulse-height output of a radiation spectrometer. The technique involves the use of the resolution matrix of a spectrometer, the radiation energy-to-dose conversion function, and the geometrical factors, although the order of matrix operations is reversed. The new technique yields a result which is mathematically identical to the standard method while requiring no matrix manipulations or resolution matrix storage in the remote computer. It utilizes only a single function for each type dose required and each geometric factor involved.

Improving Patient Safety with X-Ray and Anesthesia Machine Ventilator Synchronization: A Medical Device Interoperability Case Study

NASA Astrophysics Data System (ADS)

Arney, David; Goldman, Julian M.; Whitehead, Susan F.; Lee, Insup

When a x-ray image is needed during surgery, clinicians may stop the anesthesia machine ventilator while the exposure is made. If the ventilator is not restarted promptly, the patient may experience severe complications. This paper explores the interconnection of a ventilator and simulated x-ray into a prototype plug-and-play medical device system. This work assists ongoing interoperability framework development standards efforts to develop functional and non-functional requirements and illustrates the potential patient safety benefits of interoperable medical device systems by implementing a solution to a clinical use case requiring interoperability.

46 CFR 62.50-20 - Additional requirements for minimally attended machinery plants.

Code of Federal Regulations, 2014 CFR

2014-10-01

...) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Automated Self-propelled Vessel Manning § 62.50-20 Additional... program must be functioning prior to the completion of the evaluation period for reduced manning required...

46 CFR 62.50-20 - Additional requirements for minimally attended machinery plants.

Code of Federal Regulations, 2012 CFR

2012-10-01

...) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Automated Self-propelled Vessel Manning § 62.50-20 Additional... program must be functioning prior to the completion of the evaluation period for reduced manning required...

46 CFR 62.50-20 - Additional requirements for minimally attended machinery plants.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Automated Self-propelled Vessel Manning § 62.50-20 Additional... program must be functioning prior to the completion of the evaluation period for reduced manning required...

46 CFR 62.50-20 - Additional requirements for minimally attended machinery plants.

Code of Federal Regulations, 2013 CFR

2013-10-01

...) MARINE ENGINEERING VITAL SYSTEM AUTOMATION Automated Self-propelled Vessel Manning § 62.50-20 Additional... program must be functioning prior to the completion of the evaluation period for reduced manning required...

Multi-Modal Traveler Information System - Gateway Functional Requirements

DOT National Transportation Integrated Search

1997-11-17

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

An optimal diagnostic strategy for finding malfunctioning components in systems

NASA Technical Reports Server (NTRS)

Wong, J. T.

1983-01-01

A solution to the following problem is presented: Given that an n-component functional system is down, it is required to find a malfunctioning component of the system such that the expected expenditure is minimum.

Architectural development of an advanced EVA Electronic System

NASA Technical Reports Server (NTRS)

Lavelle, Joseph

1992-01-01

An advanced electronic system for future EVA missions (including zero gravity, the lunar surface, and the surface of Mars) is under research and development within the Advanced Life Support Division at NASA Ames Research Center. As a first step in the development, an optimum system architecture has been derived from an analysis of the projected requirements for these missions. The open, modular architecture centers around a distributed multiprocessing concept where the major subsystems independently process their own I/O functions and communicate over a common bus. Supervision and coordination of the subsystems is handled by an embedded real-time operating system kernel employing multitasking software techniques. A discussion of how the architecture most efficiently meets the electronic system functional requirements, maximizes flexibility for future development and mission applications, and enhances the reliability and serviceability of the system in these remote, hostile environments is included.

What is system control?

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

Hirst, E.; Kirby, B.

1999-11-01

Just as the aviation industry needs air-traffic controllers to manage the movement of airplanes for safety and commerce, so too, the electricity industry requires system operators. The electrical-system-control functions encompass a range of activities that support commercial transactions and maintain bulk-power reliability. As part of a project for the Edison Electric Institute, the authors examined the functions and costs of system control and the issues that need to be resolved in a restructured electricity industry (Hirst and Kirby 1998).

Formal Verification at System Level

NASA Astrophysics Data System (ADS)

Mazzini, S.; Puri, S.; Mari, F.; Melatti, I.; Tronci, E.

2009-05-01

System Level Analysis calls for a language comprehensible to experts with different background and yet precise enough to support meaningful analyses. SysML is emerging as an effective balance between such conflicting goals. In this paper we outline some the results obtained as for SysML based system level functional formal verification by an ESA/ESTEC study, with a collaboration among INTECS and La Sapienza University of Roma. The study focuses on SysML based system level functional requirements techniques.

FPGA implementation of neuro-fuzzy system with improved PSO learning.

PubMed

Karakuzu, Cihan; Karakaya, Fuat; Çavuşlu, Mehmet Ali

2016-07-01

This paper presents the first hardware implementation of neuro-fuzzy system (NFS) with its metaheuristic learning ability on field programmable gate array (FPGA). Metaheuristic learning of NFS for all of its parameters is accomplished by using the improved particle swarm optimization (iPSO). As a second novelty, a new functional approach, which does not require any memory and multiplier usage, is proposed for the Gaussian membership functions of NFS. NFS and its learning using iPSO are implemented on Xilinx Virtex5 xc5vlx110-3ff1153 and efficiency of the proposed implementation tested on two dynamic system identification problems and licence plate detection problem as a practical application. Results indicate that proposed NFS implementation and membership function approximation is as effective as the other approaches available in the literature but requires less hardware resources. Copyright © 2016 Elsevier Ltd. All rights reserved.

MITOCHONDRIAL DISEASES PART II: MOUSE MODELS OF OXPHOS DEFICIENCIES CAUSED BY DEFECTS IN REGULATORY FACTORS AND OTHER COMPONENTS REQUIRED FOR MITOCHONDRIAL FUNCTION

PubMed Central

Iommarini, Luisa; Peralta, Susana; Torraco, Alessandra; Diaz, Francisca

2015-01-01

Mitochondrial disorders are defined as defects that affect the oxidative phosphorylation system (OXPHOS). They are characterized by a heterogeneous array of clinical presentations due in part to a wide variety of factors required for proper function of the components of the OXPHOS system. There is no cure for these disorders owing our poor knowledge of the pathogenic mechanisms of disease. To understand the mechanisms of human disease numerous mouse models have been developed in recent years. Here we summarize the features of several mouse models of mitochondrial diseases directly related to those factors affecting mtDNA maintenance, replication, transcription, translation as well to other proteins that are involved in mitochondrial dynamics and quality control which affect mitochondrial OXPHOS function without been intrinsic components of the system. We discuss how these models have contributed to our understanding of mitochondrial diseases and their pathogenic mechanisms. PMID:25640959

Restricted Authentication and Encryption for Cyber-physical Systems

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

Kirkpatrick, Michael S; Bertino, Elisa; Sheldon, Frederick T

2009-01-01

Cyber-physical systems (CPS) are characterized by the close linkage of computational resources and physical devices. These systems can be deployed in a number of critical infrastructure settings. As a result, the security requirements of CPS are different than traditional computing architectures. For example, critical functions must be identified and isolated from interference by other functions. Similarly, lightweight schemes may be required, as CPS can include devices with limited computing power. One approach that offers promise for CPS security is the use of lightweight, hardware-based authentication. Specifically, we consider the use of Physically Unclonable Functions (PUFs) to bind an access requestmore » to specific hardware with device-specific keys. PUFs are implemented in hardware, such as SRAM, and can be used to uniquely identify the device. This technology could be used in CPS to ensure location-based access control and encryption, both of which would be desirable for CPS implementations.« less

Efficiency Management in Spaceflight Systems

NASA Technical Reports Server (NTRS)

Murphy, Karen

2016-01-01

Efficiency in spaceflight is often approached as “faster, better, cheaper – pick two”. The high levels of performance and reliability required for each mission suggest that planners can only control for two of the three. True efficiency comes by optimizing a system across all three parameters. The functional processes of spaceflight become technical requirements on three operational groups during mission planning: payload, vehicle, and launch operations. Given the interrelationships among the functions performed by the operational groups, optimizing function resources from one operational group to the others affects the efficiency of those groups and therefore the mission overall. This paper helps outline this framework and creates a context in which to understand the effects of resource trades on the overall system, improving the efficiency of the operational groups and the mission as a whole. This allows insight into and optimization of the controlling factors earlier in the mission planning stage.

Forms Of Memory For Representation Of Visual Objects

DTIC Science & Technology

1991-02-14

description system that functions independently of the episodic memory system that is damaged in amnesia and supports explicit remembering. Miscellaneous...well as semantic and functional information about an object, are preserved in the episodic system. 4. Priming and recognition of depth-cued, 3D objects A...requirement should serve to enhance an object’s distinctiveness in episodic memory . We also predicted robust priming for symmetric objects; this is because

Development of a battery status monitor

NASA Technical Reports Server (NTRS)

Zimmerman, R. I.

1974-01-01

A prototype battery status monitor system has been developed. The functions of the system are: (1) to provide the energy status of the battery, (2) to measure and transmit basic battery parameters, (3) to process these measurements required to determine abnormal functioning of the battery, and (4) to transmit warning signals of the abnormal condition along with a go/no go signal. The system was developed for use with the space shuttle.

A concept for fault tolerant design and improved availability of active composite elastic structures

NASA Astrophysics Data System (ADS)

Soeffker, D.; Wolters, K.; Krajcin, I.

2005-05-01

New functionalities, higher comfort and increasing performance requirements are often be solved by adding new technologies to existing (passive) solutions. Monitoring and control approaches uses additional sensors and actuators, new materials, microprocessors and new devices realizing new and improved functionalities. Two effects are becoming more and more interesting: (1) the lifetime of new actuators/materials strongly depends on the usage-history, (2) the functionality of the new composed systems depends on the fully functionality of all elements. In the consequence, the availability of such new systems is decreased by the number of elements and depends strongly on the use. These effects are known and act against new developments improving performance behavior also in mechanical engineering, automotive systems etc. This will be also the case for multifunctional composite or compound systems such as piezomaterials, magnetostrictive alloys or smart memory alloys (SMA) and is actually within the focus of the Structural-Health-Monitoring (SHM)-community. This contribution explains a new and systematically structured methodological approach to avoid and eliminate failures in mechatronical systems in an integrated and intelligent way to achieve a desirable or required amount of utilization in compliance with a defined failure rate. The result is an enhancement of the dependability of such a system.

Space shuttle/food system study. Volume 2, Appendix G: Ground support system analysis. Appendix H: Galley functional details analysis

NASA Technical Reports Server (NTRS)

1974-01-01

The capabilities for preflight feeding of flight personnel and the supply and control of the space shuttle flight food system were investigated to determine ground support requirements; and the functional details of an onboard food system galley are shown in photographic mockups. The elements which were identified as necessary to the efficient accomplishment of ground support functions include the following: (1) administration; (2) dietetics; (3) analytical laboratories; (4) flight food warehouse; (5) stowage module assembly area; (6) launch site module storage area; (7) alert crew restaurant and disperse crew galleys; (8) ground food warehouse; (9) manufacturing facilities; (10) transport; and (11) computer support. Each element is discussed according to the design criteria of minimum cost, maximum flexibility, reliability, and efficiency consistent with space shuttle requirements. The galley mockup overview illustrates the initial operation configuration, food stowage locations, meal assembly and serving trays, meal preparation configuration, serving, trash management, and the logistics of handling and cleanup equipment.

Development of a graphical user interface for the global land information system (GLIS)

USGS Publications Warehouse

Alstad, Susan R.; Jackson, David A.

1993-01-01

The process of developing a Motif Graphical User Interface for the Global Land Information System (GLIS) involved incorporating user requirements, in-house visual and functional design requirements, and Open Software Foundation (OSF) Motif style guide standards. Motif user interface windows have been developed using the software to support Motif window functions war written using the C programming language. The GLIS architecture was modified to support multiple servers and remote handlers running the X Window System by forming a network of servers and handlers connected by TCP/IP communications. In April 1993, prior to release the GLIS graphical user interface and system architecture modifications were test by developers and users located at the EROS Data Center and 11 beta test sites across the country.

Systemic lipopolysaccharide administration impairs retrieval of context-object discrimination, but not spatial, memory: Evidence for selective disruption of specific hippocampus-dependent memory functions during acute neuroinflammation

PubMed Central

Czerniawski, Jennifer; Miyashita, Teiko; Lewandowski, Gail; Guzowski, John F.

2014-01-01

Neuroinflammation is implicated in impairments in neuronal function and cognition that arise with aging, trauma, and/or disease. Therefore, understanding the underlying basis of the effect of immune system activation on neural function could lead to therapies for treating cognitive decline. Although neuroinflammation is widely thought to preferentially impair hippocampus-dependent memory, data on the effects of cytokines on cognition are mixed. One possible explanation for these inconsistent results is that cytokines may disrupt specific neural processes underlying some forms of memory but not others. In an earlier study, we tested the effect of systemic administration of bacterial lipopolysaccharide (LPS) on retrieval of hippocampus-dependent context memory and neural circuit function in CA3 and CA1 (Czerniawski and Guzowski, 2014). Paralleling impairment in context discrimination memory, we observed changes in neural circuit function consistent with disrupted pattern separation function. In the current study we tested the hypothesis that acute neuroinflammation selectively disrupts memory retrieval in tasks requiring hippocampal pattern separation processes. Male Sprague-Dawley rats given LPS systemically prior to testing exhibited intact performance in tasks that do not require hippocampal pattern separation processes: novel object recognition and spatial memory in the water maze. By contrast, memory retrieval in a task thought to require hippocampal pattern separation, context-object discrimination, was strongly impaired in LPS-treated rats in the absence of any gross effects on exploratory activity or motivation. These data show that LPS administration does not impair memory retrieval in all hippocampus-dependent tasks, and support the hypothesis that acute neuroinflammation impairs context discrimination memory via disruption of pattern separation processes in hippocampus. PMID:25451612

Systemic lipopolysaccharide administration impairs retrieval of context-object discrimination, but not spatial, memory: Evidence for selective disruption of specific hippocampus-dependent memory functions during acute neuroinflammation.

PubMed

Czerniawski, Jennifer; Miyashita, Teiko; Lewandowski, Gail; Guzowski, John F

2015-02-01

Neuroinflammation is implicated in impairments in neuronal function and cognition that arise with aging, trauma, and/or disease. Therefore, understanding the underlying basis of the effect of immune system activation on neural function could lead to therapies for treating cognitive decline. Although neuroinflammation is widely thought to preferentially impair hippocampus-dependent memory, data on the effects of cytokines on cognition are mixed. One possible explanation for these inconsistent results is that cytokines may disrupt specific neural processes underlying some forms of memory but not others. In an earlier study, we tested the effect of systemic administration of bacterial lipopolysaccharide (LPS) on retrieval of hippocampus-dependent context memory and neural circuit function in CA3 and CA1 (Czerniawski and Guzowski, 2014). Paralleling impairment in context discrimination memory, we observed changes in neural circuit function consistent with disrupted pattern separation function. In the current study we tested the hypothesis that acute neuroinflammation selectively disrupts memory retrieval in tasks requiring hippocampal pattern separation processes. Male Sprague-Dawley rats given LPS systemically prior to testing exhibited intact performance in tasks that do not require hippocampal pattern separation processes: novel object recognition and spatial memory in the water maze. By contrast, memory retrieval in a task thought to require hippocampal pattern separation, context-object discrimination, was strongly impaired in LPS-treated rats in the absence of any gross effects on exploratory activity or motivation. These data show that LPS administration does not impair memory retrieval in all hippocampus-dependent tasks, and support the hypothesis that acute neuroinflammation impairs context discrimination memory via disruption of pattern separation processes in hippocampus. Copyright © 2014 Elsevier Inc. All rights reserved.

Development of Human Factors Guidlines for Advanced Traveler Information Systems and Commercial Vehicle Operations: Investigation of ATIS Function Transition and the Effects of an In-Vehicle ATIS on Driver Performance

DOT National Transportation Integrated Search

1999-12-01

The objective of the first experiment reported here was to measure the cognitive demands associated with transitioning across Advanced Traveler Information System (ATIS) functions. This required the development of both objective and subjective indice...

Parameter and Structure Inference for Nonlinear Dynamical Systems

NASA Technical Reports Server (NTRS)

Morris, Robin D.; Smelyanskiy, Vadim N.; Millonas, Mark

2006-01-01

A great many systems can be modeled in the non-linear dynamical systems framework, as x = f(x) + xi(t), where f() is the potential function for the system, and xi is the excitation noise. Modeling the potential using a set of basis functions, we derive the posterior for the basis coefficients. A more challenging problem is to determine the set of basis functions that are required to model a particular system. We show that using the Bayesian Information Criteria (BIC) to rank models, and the beam search technique, that we can accurately determine the structure of simple non-linear dynamical system models, and the structure of the coupling between non-linear dynamical systems where the individual systems are known. This last case has important ecological applications.

Conceptual design of a connected vehicle wrong-way driving detection and management system.

DOT National Transportation Integrated Search

2016-04-01

This report describes the tasks completed to develop a concept of operations, functional requirements, and : high-level system design for a Connected Vehicle (CV) Wrong-Way Driving (WWD) Detection and Management : System. This system was designed to ...

An integrated dexterous robotic testbed for space applications

NASA Technical Reports Server (NTRS)

Li, Larry C.; Nguyen, Hai; Sauer, Edward

1992-01-01

An integrated dexterous robotic system was developed as a testbed to evaluate various robotics technologies for advanced space applications. The system configuration consisted of a Utah/MIT Dexterous Hand, a PUMA 562 arm, a stereo vision system, and a multiprocessing computer control system. In addition to these major subsystems, a proximity sensing system was integrated with the Utah/MIT Hand to provide capability for non-contact sensing of a nearby object. A high-speed fiber-optic link was used to transmit digitized proximity sensor signals back to the multiprocessing control system. The hardware system was designed to satisfy the requirements for both teleoperated and autonomous operations. The software system was designed to exploit parallel processing capability, pursue functional modularity, incorporate artificial intelligence for robot control, allow high-level symbolic robot commands, maximize reusable code, minimize compilation requirements, and provide an interactive application development and debugging environment for the end users. An overview is presented of the system hardware and software configurations, and implementation is discussed of subsystem functions.

Using Quality Attributes to Bridge Systems Engineering Gaps : A Juno Ground Data Systems Case Study

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.; Jackson, Maddalena M.; Thornton, Marla S.

2012-01-01

The Juno Mission to Jupiter is the second mission selected by the NASA New Frontiers Program. Juno launched August 2011 and will reach Jupiter July 2016. Juno's payload system is composed of nine instruments plus a gravity science experiment. One of the primary functions of the Juno Ground Data System (GDS) is the assembly and distribution of the CFDP (CCSDS File Delivery Protocol) product telemetry, also referred to as raw science data, for eight out of the nine instruments. The GDS accomplishes this with the Instrument Data Pipeline (IDP). During payload integration, the first attempt to exercise the IDP in a flight like manner revealed that although the functional requirements were well understood, the system was unable to meet latency requirements with the as-is heritage design. A systems engineering gap emerged between Juno instrument data delivery requirements and the assumptions behind the heritage flight-ground interactions. This paper describes the use of quality attributes to measure and overcome this gap by introducing a new systems engineering activity, and a new monitoring service architecture that successfully delivered the performance metrics needed to validate Juno IDP.

32 CFR 352a.4 - Responsibilities and functions.

Code of Federal Regulations, 2010 CFR

2010-07-01

...) ORGANIZATIONAL CHARTERS DEFENSE FINANCE AND ACCOUNTING SERVICE (DFAS) § 352a.4 Responsibilities and functions. (a) The Director, Defense Finance and Accounting Service (DFAS), is the principal DoD executive for finance and accounting requirements, systems, and functions identified in DoD Directive 5118.3, 1 and...

32 CFR 352a.4 - Responsibilities and functions.

Code of Federal Regulations, 2013 CFR

2013-07-01

...) ORGANIZATIONAL CHARTERS DEFENSE FINANCE AND ACCOUNTING SERVICE (DFAS) § 352a.4 Responsibilities and functions. (a) The Director, Defense Finance and Accounting Service (DFAS), is the principal DoD executive for finance and accounting requirements, systems, and functions identified in DoD Directive 5118.3, 1 and...

32 CFR 352a.4 - Responsibilities and functions.

Code of Federal Regulations, 2014 CFR

2014-07-01

...) ORGANIZATIONAL CHARTERS DEFENSE FINANCE AND ACCOUNTING SERVICE (DFAS) § 352a.4 Responsibilities and functions. (a) The Director, Defense Finance and Accounting Service (DFAS), is the principal DoD executive for finance and accounting requirements, systems, and functions identified in DoD Directive 5118.3, 1 and...

32 CFR 352a.4 - Responsibilities and functions.

Code of Federal Regulations, 2011 CFR

2011-07-01

...) ORGANIZATIONAL CHARTERS DEFENSE FINANCE AND ACCOUNTING SERVICE (DFAS) § 352a.4 Responsibilities and functions. (a) The Director, Defense Finance and Accounting Service (DFAS), is the principal DoD executive for finance and accounting requirements, systems, and functions identified in DoD Directive 5118.3, 1 and...

32 CFR 352a.4 - Responsibilities and functions.

Code of Federal Regulations, 2012 CFR

2012-07-01

...) ORGANIZATIONAL CHARTERS DEFENSE FINANCE AND ACCOUNTING SERVICE (DFAS) § 352a.4 Responsibilities and functions. (a) The Director, Defense Finance and Accounting Service (DFAS), is the principal DoD executive for finance and accounting requirements, systems, and functions identified in DoD Directive 5118.3, 1 and...

Introduction: The challenge of optimum integration of propulsion systems and large space structures

NASA Technical Reports Server (NTRS)

Carlisle, R. F.

1980-01-01

A functional matrix of possible propulsion system characteristics for a spacecraft for deployable and assembled spacecraft structures shows that either electric propulsion or low thrust chemical propulsion systems could provide the propulsion required. The trade-off considerations of a single propulsion engine or multiengines are outlined and it is shown that a single point engine is bounded by some upper limit of thrust for assembled spacecraft. The matrix also shows several additional functions that can be provided to the spacecraft if a propulsion system is an integral part of the spacecraft. A review of all of the functions that can be provided for a spacecraft by an integral propulsion system may result in the inclusion of the propulsion for several functions even if no single function were mandatory. Propulsion interface issues for each combination of engines are identified.

Design of a structural and functional hierarchy for planning and control of telerobotic systems

NASA Technical Reports Server (NTRS)

Acar, Levent; Ozguner, Umit

1989-01-01

Hierarchical structures offer numerous advantages over conventional structures for the control of telerobotic systems. A hierarchically organized system can be controlled via undetailed task assignments and can easily adapt to changing circumstances. The distributed and modular structure of these systems also enables fast response needed in most telerobotic applications. On the other hand, most of the hierarchical structures proposed in the literature are based on functional properties of a system. These structures work best for a few given functions of a large class of systems. In telerobotic applications, all functions of a single system needed to be explored. This approach requires a hierarchical organization based on physical properties of a system and such a hierarchical organization is introduced. The decomposition, organization, and control of the hierarchical structure are considered, and a system with two robot arms and a camera is presented.

76 FR 66057 - North American Electric Reliability Corporation; Order Approving Regional Reliability Standard

Federal Register 2010, 2011, 2012, 2013, 2014

2011-10-25

... system conditions when the system experiences dynamic events such as low frequency oscillations, or... R8 requires that dynamic disturbance recorders function continuously. To capture system disturbance... recording capability necessary to monitor the response of the Bulk-Power System to system disturbances...

From Process Understanding Via Soil Functions to Sustainable Soil Management - A Systemic Approach

NASA Astrophysics Data System (ADS)

Wollschlaeger, U.; Bartke, S.; Bartkowski, B.; Daedlow, K.; Helming, K.; Kogel-Knabner, I.; Lang, B.; Rabot, E.; Russell, D.; Stößel, B.; Weller, U.; Wiesmeier, M.; Rabot, E.; Vogel, H. J.

2017-12-01

Fertile soils are central resources for the production of biomass and the provision of food and energy. A growing world population and latest climate targets lead to an increasing demand for both, food and bio-energy, which requires preserving and improving the long-term productivity of soils as a bio-economic resource. At the same time, other soil functions and ecosystem services need to be maintained: filter for clean water, carbon sequestration, provision and recycling of nutrients, and habitat for biological activity. All these soil functions result from the interaction of a multitude of physical, chemical and biological processes that are not yet sufficiently understood. In addition, we lack understanding about the interplay between the socio-economic system and the soil system and how soil functions benefit human wellbeing. Hence, a solid and integrated assessment of soil quality requires the consideration of the ensemble of soil functions and its relation to soil management to finally be able to develop site-specific options for sustainable soil management. We present an integrated modeling approach that investigates the influence of soil management on the ensemble of soil functions. It is based on the mechanistic relationships between soil functional attributes, each explained by a network of interacting processes as derived from scientific evidence. As the evidence base required for feeding the model is for the most part stored in the existing scientific literature, another central component of our work is to set up a public "knowledge-portal" providing the infrastructure for a community effort towards a comprehensive knowledge base on soil processes as a basis for model developments. The connection to the socio-economic system is established using the Drivers-Pressures-Impacts-States-Responses (DPSIR) framework where our improved understanding about soil ecosystem processes is linked to ecosystem services and resource efficiency via the soil functions.

Engineering Complex Embedded Systems with State Analysis and the Mission Data System

NASA Technical Reports Server (NTRS)

Ingham, Michel D.; Rasmussen, Robert D.; Bennett, Matthew B.; Moncada, Alex C.

2004-01-01

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer s intent, potentially leading to software errors. This problem is addressed by a systems engineering methodology called State Analysis, which provides a process for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using State Analysis and how these requirements inform the design of the system software, using representative spacecraft examples.

Development of utility generic functional requirements for electronic work packages and computer-based procedures

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

Oxstrand, Johanna

The Nuclear Electronic Work Packages - Enterprise Requirements (NEWPER) initiative is a step toward a vision of implementing an eWP framework that includes many types of eWPs. This will enable immediate paper-related cost savings in work management and provide a path to future labor efficiency gains through enhanced integration and process improvement in support of the Nuclear Promise (Nuclear Energy Institute 2016). The NEWPER initiative was organized by the Nuclear Information Technology Strategic Leadership (NITSL) group, which is an organization that brings together leaders from the nuclear utility industry and regulatory agencies to address issues involved with information technology usedmore » in nuclear-power utilities. NITSL strives to maintain awareness of industry information technology-related initiatives and events and communicates those events to its membership. NITSL and LWRS Program researchers have been coordinating activities, including joint organization of NEWPER-related meetings and report development. The main goal of the NEWPER initiative was to develop a set of utility generic functional requirements for eWP systems. This set of requirements will support each utility in their process of identifying plant-specific functional and non-functional requirements. The NEWPER initiative has 140 members where the largest group of members consists of 19 commercial U.S. nuclear utilities and eleven of the most prominent vendors of eWP solutions. Through the NEWPER initiative two sets of functional requirements were developed; functional requirements for electronic work packages and functional requirements for computer-based procedures. This paper will describe the development process as well as a summary of the requirements.« less

Urban Planning and Management Information Systems Analysis and Design Based on GIS

NASA Astrophysics Data System (ADS)

Xin, Wang

Based on the analysis of existing relevant systems on the basis of inadequate, after a detailed investigation and research, urban planning and management information system will be designed for three-tier structure system, under the LAN using C/S mode architecture. Related functions for the system designed in accordance with the requirements of the architecture design of the functional relationships between the modules. Analysis of the relevant interface and design, data storage solutions proposed. The design for small and medium urban planning information system provides a viable building program.

Recommended System Design for the Occupational Health Management Information System (OHMIS). Volume 1.

DTIC Science & Technology

1983-04-01

Management Information System (OHMIS). The system design includes: detailed function data flows for each of the core data processing functions of OHMIS, in the form of input/processing/output algorithms; detailed descriptions of the inputs and outputs; performance specifications of OHMIS; resources required to develop and operate OHMIS (Vol II). In addition, the report provides a summary of the rationale used to develop the recommended system design, a description of the methodology used to develop the recommended system design, and a review of existing

Airport Surface Network Architecture Definition

NASA Technical Reports Server (NTRS)

Nguyen, Thanh C.; Eddy, Wesley M.; Bretmersky, Steven C.; Lawas-Grodek, Fran; Ellis, Brenda L.

2006-01-01

Currently, airport surface communications are fragmented across multiple types of systems. These communication systems for airport operations at most airports today are based dedicated and separate architectures that cannot support system-wide interoperability and information sharing. The requirements placed upon the Communications, Navigation, and Surveillance (CNS) systems in airports are rapidly growing and integration is urgently needed if the future vision of the National Airspace System (NAS) and the Next Generation Air Transportation System (NGATS) 2025 concept are to be realized. To address this and other problems such as airport surface congestion, the Space Based Technologies Project s Surface ICNS Network Architecture team at NASA Glenn Research Center has assessed airport surface communications requirements, analyzed existing and future surface applications, and defined a set of architecture functions that will help design a scalable, reliable and flexible surface network architecture to meet the current and future needs of airport operations. This paper describes the systems approach or methodology to networking that was employed to assess airport surface communications requirements, analyze applications, and to define the surface network architecture functions as the building blocks or components of the network. The systems approach used for defining these functions is relatively new to networking. It is viewing the surface network, along with its environment (everything that the surface network interacts with or impacts), as a system. Associated with this system are sets of services that are offered by the network to the rest of the system. Therefore, the surface network is considered as part of the larger system (such as the NAS), with interactions and dependencies between the surface network and its users, applications, and devices. The surface network architecture includes components such as addressing/routing, network management, network performance and security.

Technical support for digital systems technology development. Task order 1: ISP contention analysis and control

NASA Technical Reports Server (NTRS)

Stehle, Roy H.; Ogier, Richard G.

1993-01-01

Alternatives for realizing a packet-based network switch for use on a frequency division multiple access/time division multiplexed (FDMA/TDM) geostationary communication satellite were investigated. Each of the eight downlink beams supports eight directed dwells. The design needed to accommodate multicast packets with very low probability of loss due to contention. Three switch architectures were designed and analyzed. An output-queued, shared bus system yielded a functionally simple system, utilizing a first-in, first-out (FIFO) memory per downlink dwell, but at the expense of a large total memory requirement. A shared memory architecture offered the most efficiency in memory requirements, requiring about half the memory of the shared bus design. The processing requirement for the shared-memory system adds system complexity that may offset the benefits of the smaller memory. An alternative design using a shared memory buffer per downlink beam decreases circuit complexity through a distributed design, and requires at most 1000 packets of memory more than the completely shared memory design. Modifications to the basic packet switch designs were proposed to accommodate circuit-switched traffic, which must be served on a periodic basis with minimal delay. Methods for dynamically controlling the downlink dwell lengths were developed and analyzed. These methods adapt quickly to changing traffic demands, and do not add significant complexity or cost to the satellite and ground station designs. Methods for reducing the memory requirement by not requiring the satellite to store full packets were also proposed and analyzed. In addition, optimal packet and dwell lengths were computed as functions of memory size for the three switch architectures.

Influence of acoustic impedance of multilayer acoustic systems on the transfer function of ultrasonic airborne transducers.

PubMed

Gudra, Tadeusz; Opieliński, Krzysztof J

2002-05-01

In different solutions of ultrasonic transducers radiating acoustic energy into the air there occurs the problem of the proper selection of the acoustic impedance of one or more matching layers. The goal of this work was a computer analysis of the influence of acoustic impedance on the transfer function of piezoceramic transducers equipped with matching layers. Cases of resonance and non-resonance matching impedance in relation to the transfer function and the energy transmission coefficient for solid state-air systems were analysed. With stable thickness of matching layers the required shape of the transfer function can be obtained through proper choice of acoustic impedance were built (e.g. maximal flat function). The proper choice of acoustic impedance requires an elaboration of precise methods of synthesis of matching systems. Using the known matching criteria (Chebyshev's, DeSilets', Souquet's), the transfer function characteristics of transducers equipped with one, two, and three matching layers as well as the optimisation methods of the energy transmission coefficient were presented. The influence of the backside load of the transducer on the shape of transfer function was also analysed. The calculation results of this function for different loads of the transducer backside without and with the different matching layers were presented. The proper load selection allows us to obtain the desired shape of the transfer function, which determines the pulse shape generated by the transducer.

Development of vendor evaluation criteria and post-implementation considerations for MSFC center-wide executive information system

NASA Technical Reports Server (NTRS)

Moynihan, Gary P.

1992-01-01

In June 1991, the MITRE Corporation submitted a series of recommendations as part of a Marshall Space Flight Center (MSFC) Management Information System Requirements Study, initiated by the Information Systems Office (ISO). A major recommendation of the study was to develop an Executive Information System (EIS) for MSFC executives. ISO was directed, by center management, to proceed with the development of a Center-Wide Executive Information System. Existing EIS prototypes, developed by the Space Shuttle Projects Office and the Payload Projects Office, were reviewed. These existing MSFC prototypes were considered not to encompass the required functionality needed on a center-wide basis. A follow-up study by MITRE provided top-level system requirements. These were later incorporated into a final requirements specification document by Boeing Computer Support Services.

Multiple IMU system hardware interface design, volume 2

NASA Technical Reports Server (NTRS)

Landey, M.; Brown, D.

1975-01-01

The design of each system component is described. Emphasis is placed on functional requirements unique in this system, including data bus communication, data bus transmitters and receivers, and ternary-to-binary torquing decision logic. Mechanization drawings are presented.

Orbiter active thermal control system description

NASA Technical Reports Server (NTRS)

Laubach, G. E.

1975-01-01

A brief description of the Orbiter Active Thermal Control System (ATCS) including (1) major functional requirements of heat load, temperature control and heat sink utilization, (2) the overall system arrangement, and (3) detailed description of the elements of the ATCS.

Multi-Modal Traveler Information System - GCM Corridor Architecture Functional Requirements

DOT National Transportation Integrated Search

1997-11-17

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

The Importance of Information Requirements in Designing Acquisition to Information Systems

NASA Technical Reports Server (NTRS)

Davis, Bruce A.; Hill, Chuck; Maughan, Paul M.

1998-01-01

The partnership model used by NASA's Commercial Remote Sensing Program has been successful in better defining remote sensing functional requirements and translation to technical specifications to address environmental needs of the 21st century.

Report of the facility definition team spacelab UV-Optical Telescope Facility

NASA Technical Reports Server (NTRS)

1975-01-01

Scientific requirements for the Spacelab Ultraviolet-Optical Telescope (SUOT) facility are presented. Specific programs involving high angular resolution imagery over wide fields, far ultraviolet spectroscopy, precisely calibrated spectrophotometry and spectropolarimetry over a wide wavelength range, and planetary studies, including high resolution synoptic imagery, are recommended. Specifications for the mounting configuration, instruments for the mounting configuration, instrument mounting system, optical parameters, and the pointing and stabilization system are presented. Concepts for the focal plane instruments are defined. The functional requirements of the direct imaging camera, far ultraviolet spectrograph, and the precisely calibrated spectrophotometer are detailed, and the planetary camera concept is outlined. Operational concepts described in detail are: the makeup and functions of shuttle payload crew, extravehicular activity requirements, telescope control and data management, payload operations control room, orbital constraints, and orbital interfaces (stabilization, maneuvering requirements and attitude control, contamination, utilities, and payload weight considerations).

Standard module approach to scanning requirements for second-generation airborne FLIRs

NASA Astrophysics Data System (ADS)

Ludwiszewski, Alan P.

1995-05-01

This paper examines the specification requirements for the development of standard module scanning components to be used in conjunction with SADA I and SADA II sensor arrays. System-level design considerations are presented to identify a selection of components that is consistent with optimum use of the SADA technology. A limited-rotation electromagnetic actuator, used in conjunction with an angular position sensor and a digital controller, is shown to have the necessary performance and flexibility to perform the frame scan function for a wide range of airborne systems. System level requirements and specifications for an optional interlace scan system are also provided.

Key Performance Parameter Driven Technology Goals for Electric Machines and Power Systems

NASA Technical Reports Server (NTRS)

Bowman, Cheryl; Jansen, Ralph; Brown, Gerald; Duffy, Kirsten; Trudell, Jeffrey

2015-01-01

Transitioning aviation to low carbon propulsion is one of the crucial strategic research thrust and is a driver in the search for alternative propulsion system for advanced aircraft configurations. This work requires multidisciplinary skills coming from multiple entities. The feasibility of scaling up various electric drive system technologies to meet the requirements of a large commercial transport is discussed in terms of key parameters. Functional requirements are identified that impact the power system design. A breakeven analysis is presented to find the minimum allowable electric drive specific power and efficiency that can preserve the range, initial weight, operating empty weight, and payload weight of the base aircraft.

Instrument Pointing Control System for the Stellar Interferometry Mission - Planet Quest

NASA Technical Reports Server (NTRS)

Brugarolas, Paul B.; Kang, Bryan

2006-01-01

This paper describes the high precision Instrument Pointing Control System (PCS) for the Stellar Interferometry Mission (SIM) - Planet Quest. The PCS system provides front-end pointing, compensation for spacecraft motion, and feedforward stabilization, which are needed for proper interference. Optical interferometric measurements require very precise pointing (0.03 as, 1-(sigma) radial) for maximizing the interference pattern visibility. This requirement is achieved by fine pointing control of articulating pointing mirrors with feedback from angle tracking cameras. The overall pointing system design concept is presentcd. Functional requirements and an acquisition concept are given. Guide and Science pointing control loops are discussed. Simulation analyses demonstrate the feasibility of the design.

A premeiotic function for boule in the planarian Schmidtea mediterranea

PubMed Central

Iyer, Harini; Issigonis, Melanie; Sharma, Prashant P.; Extavour, Cassandra G.; Newmark, Phillip A.

2016-01-01

Mutations in Deleted in Azoospermia (DAZ), a Y chromosome gene, are an important cause of human male infertility. DAZ is found exclusively in primates, limiting functional studies of this gene to its homologs: boule, required for meiotic progression of germ cells in invertebrate model systems, and Daz-like (Dazl), required for early germ cell maintenance in vertebrates. Dazl is believed to have acquired its premeiotic role in a vertebrate ancestor following the duplication and functional divergence of the single-copy gene boule. However, multiple homologs of boule have been identified in some invertebrates, raising the possibility that some of these genes may play other roles, including a premeiotic function. Here we identify two boule paralogs in the freshwater planarian Schmidtea mediterranea. Smed-boule1 is necessary for meiotic progression of male germ cells, similar to the known function of boule in invertebrates. By contrast, Smed-boule2 is required for the maintenance of early male germ cells, similar to vertebrate Dazl. To examine if Boule2 may be functionally similar to vertebrate Dazl, we identify and functionally characterize planarian homologs of human DAZL/DAZ-interacting partners and DAZ family mRNA targets. Finally, our phylogenetic analyses indicate that premeiotic functions of planarian boule2 and vertebrate Dazl evolved independently. Our study uncovers a premeiotic role for an invertebrate boule homolog and offers a tractable invertebrate model system for studying the premeiotic functions of the DAZ protein family. PMID:27330085

Functional Performance of Pyrovalves

NASA Technical Reports Server (NTRS)

Bement, Laurence J.

1996-01-01

Following several flight and ground test failures of spacecraft systems using single-shot, 'normally closed' pyrotechnically actuated valves (pyrovalves), a government/industry cooperative program was initiated to assess the functional performance of five qualified designs. The goal of the program was to improve performance-based requirements for the procurement of pyrovalves. Specific objectives included the demonstration of performance test methods, the measurement of 'blowby' (the passage of gases from the pyrotechnic energy source around the activating piston into the valve's fluid path), and the quantification of functional margins for each design. Experiments were conducted in-house at NASA on several units each of the five valve designs. The test methods used for this program measured the forces and energies required to actuate the valves, as well as the energies and the pressures (where possible) delivered by the pyrotechnic sources. Functional performance ranged widely among the designs. Blowby cannot be prevented by o-ring seals; metal-to-metal seals were effective. Functional margin was determined by dividing the energy delivered by the pyrotechnic sources in excess to that required to accomplish the function by the energy required for that function. All but two designs had adequate functional margins with the pyrotechnic cartridges evaluated.

Open-source point-of-care electronic medical records for use in resource-limited settings: systematic review and questionnaire surveys

PubMed Central

Bru, Juan; Berger, Christopher A

2012-01-01

Background Point-of-care electronic medical records (EMRs) are a key tool to manage chronic illness. Several EMRs have been developed for use in treating HIV and tuberculosis, but their applicability to primary care, technical requirements and clinical functionalities are largely unknown. Objectives This study aimed to address the needs of clinicians from resource-limited settings without reliable internet access who are considering adopting an open-source EMR. Study eligibility criteria Open-source point-of-care EMRs suitable for use in areas without reliable internet access. Study appraisal and synthesis methods The authors conducted a comprehensive search of all open-source EMRs suitable for sites without reliable internet access. The authors surveyed clinician users and technical implementers from a single site and technical developers of each software product. The authors evaluated availability, cost and technical requirements. Results The hardware and software for all six systems is easily available, but they vary considerably in proprietary components, installation requirements and customisability. Limitations This study relied solely on self-report from informants who developed and who actively use the included products. Conclusions and implications of key findings Clinical functionalities vary greatly among the systems, and none of the systems yet meet minimum requirements for effective implementation in a primary care resource-limited setting. The safe prescribing of medications is a particular concern with current tools. The dearth of fully functional EMR systems indicates a need for a greater emphasis by global funding agencies to move beyond disease-specific EMR systems and develop a universal open-source health informatics platform. PMID:22763661

Multimission airborne radar for the 1990s

NASA Astrophysics Data System (ADS)

Robinson, Thomas H.

1986-07-01

The continuing trend towards the development and production of aircraft capable of multiple missions indicates that future airborne radars must provide a broad spectrum of air-to-air and air-to-ground modes. This paper investigates the modal and functional requirements of a multimode radar projected for the mid-1990s period. The paper is divided into two sections. In the first, the multimission capabilities of current radars are presented to establish trends and capabilities. In the second, the requirements of the next generation system are established. Current multimode radars lay the basis for future systems. The experience gained on the APG-65 and APG-63/70 radars is presented and conclusions are drawn regarding their impact on future system requirements. Not only are modes and performance reviewed for these radars but also their system architecture. The discussion starts with the APG-65 radar which is the first true multimission radar with programmable signal and data processing. Following this, the evolution of the APG-63 radar, culminating with the most recent upgrading resulting in redesignation of APG-70, is presented. The incorporation of air-to-ground capabilities in the APG-70, resulting from the Dual Role Fighter program, is reviewed. Results from the Advanced Fighter Capabilities Demonstration program are presented showing how high resolution SAR was incorporated into a full weapon delivery solution. The specific radar requirements for the next decade radar system are developed. This development is done in two parts. First, mode requirements are synthesized for air superiority, navigation and strike/interdiction operation. This includes low altitude penetration requirements and a review of radar timeline constraints which arise. Second, the fundamental functional requirements needed to implement the mode requirements are explored. Architectural issues and their impact on reliability and sustainability are also considered.

14 CFR 27.1309 - Equipment, systems, and installations.

Code of Federal Regulations, 2010 CFR

2010-01-01

... showing compliance with paragraph (a), (b), or (c) of this section, the effects of lightning strikes on..., systems, and installations. (a) The equipment, systems, and installations whose functioning is required by... under any foreseeable operating condition. (b) The equipment, systems, and installations of a...

14 CFR 27.1309 - Equipment, systems, and installations.

Code of Federal Regulations, 2011 CFR

2011-01-01

... showing compliance with paragraph (a), (b), or (c) of this section, the effects of lightning strikes on..., systems, and installations. (a) The equipment, systems, and installations whose functioning is required by... under any foreseeable operating condition. (b) The equipment, systems, and installations of a...

Development Requirements for Spacesuit Elbow Joint

NASA Technical Reports Server (NTRS)

Peters, Benjamin

2017-01-01

Functional Requirements for spacesuit elbow joint:1) The system is a conformal, single-axis spacesuit pressurized joint that encloses the elbow joint of the suited user and uses a defined interface to connect to the suit systems on either side of the joint.2) The system shall be designed to bear the loads incurred from the internal pressure of the system, as well as the expected loads induced by the user while enabling the user move the joint through the required range of motion. The joint torque of the system experienced by the user shall remain at or below the required specification for the entire range of motion.3) The design shall be constructed, at a minimum, as a two-layer system. The internal, air-tight layer shall be referred to as the bladder, and the layer on the unpressurized side of the bladder shall be referred to as the restraint. The design of the system may include additional features or layers, such as axial webbing, to meet the overall requirements of the design.

Implementation of a low-cost, commercial orbit determination system

NASA Astrophysics Data System (ADS)

Corrigan, Jim

1994-11-01

Traditional satellite and launch control systems have consisted of custom solutions requiring significant development and maintenance costs. These systems have typically been designed to support specific program requirements and are expensive to modify and augment after delivery. The expanding role of space in today's marketplace combined with the increased sophistication and capabilities of modern satellites has created a need for more efficient, lower cost solutions to complete command and control systems. Recent technical advances have resulted in commercial-off-the-shelf products which greatly reduce the complete life-cycle costs associated with satellite launch and control system procurements. System integrators and spacecraft operators have, however, been slow to integrate these commercial based solutions into a comprehensive command and control system. This is due, in part, to a resistance to change and the fact that many available products are unable to effectively communicate with other commercial products. The United States Air Force, responsible for the health and safety of over 84 satellites via its Air Force Satellite Control Network (AFSCN), has embarked on an initiative to prove that commercial products can be used effectively to form a comprehensive command and control system. The initial version of this system is being installed at the Air Force's Center for Research Support (CERES) located at the National Test Facility in Colorado Springs, Colorado. The first stage of this initiative involved the identification of commercial products capable of satisfying each functional element of a command and control system. A significant requirement in this product selection criteria was flexibility and ability to integrate with other available commercial products. This paper discusses the functions and capabilities of the product selected to provide orbit determination functions for this comprehensive command and control system.

Implementation of a low-cost, commercial orbit determination system

NASA Technical Reports Server (NTRS)

Corrigan, Jim

1994-01-01

Traditional satellite and launch control systems have consisted of custom solutions requiring significant development and maintenance costs. These systems have typically been designed to support specific program requirements and are expensive to modify and augment after delivery. The expanding role of space in today's marketplace combined with the increased sophistication and capabilities of modern satellites has created a need for more efficient, lower cost solutions to complete command and control systems. Recent technical advances have resulted in commercial-off-the-shelf products which greatly reduce the complete life-cycle costs associated with satellite launch and control system procurements. System integrators and spacecraft operators have, however, been slow to integrate these commercial based solutions into a comprehensive command and control system. This is due, in part, to a resistance to change and the fact that many available products are unable to effectively communicate with other commercial products. The United States Air Force, responsible for the health and safety of over 84 satellites via its Air Force Satellite Control Network (AFSCN), has embarked on an initiative to prove that commercial products can be used effectively to form a comprehensive command and control system. The initial version of this system is being installed at the Air Force's Center for Research Support (CERES) located at the National Test Facility in Colorado Springs, Colorado. The first stage of this initiative involved the identification of commercial products capable of satisfying each functional element of a command and control system. A significant requirement in this product selection criteria was flexibility and ability to integrate with other available commercial products. This paper discusses the functions and capabilities of the product selected to provide orbit determination functions for this comprehensive command and control system.

Automated Bilingual Circulation System Using PC Local Area Networks.

ERIC Educational Resources Information Center

Iskanderani, A. I.; Anwar, M. A.

1992-01-01

Describes a personal computer and LAN-based automated circulation system capable of handling both Arabic and Latin characters that was developed for use at King Abdullaziz University (Jeddah, Saudi Arabia). Outlines system requirements, system structure, hardware needs, and individual functional modules of the system. Numerous examples and flow…

System and method of active vibration control for an electro-mechanically cooled device

DOEpatents

Lavietes, Anthony D.; Mauger, Joseph; Anderson, Eric H.

2000-01-01

A system and method of active vibration control of an electro-mechanically cooled device is disclosed. A cryogenic cooling system is located within an environment. The cooling system is characterized by a vibration transfer function, which requires vibration transfer function coefficients. A vibration controller generates the vibration transfer function coefficients in response to various triggering events. The environments may differ by mounting apparatus, by proximity to vibration generating devices, or by temperature. The triggering event may be powering on the cooling system, reaching an operating temperature, or a reset action. A counterbalance responds to a drive signal generated by the vibration controller, based on the vibration signal and the vibration transfer function, which adjusts vibrations. The method first places a cryogenic cooling system within a first environment and then generates a first set of vibration transfer function coefficients, for a vibration transfer function of the cooling system. Next, the cryogenic cooling system is placed within a second environment and a second set of vibration transfer function coefficients are generated. Then, a counterbalance is driven, based on the vibration transfer function, to reduce vibrations received by a vibration sensitive element.

Modern control techniques in active flutter suppression using a control moment gyro

NASA Technical Reports Server (NTRS)

Buchek, P. M.

1974-01-01

Development of organized synthesis techniques, using concepts of modern control theory was studied for the design of active flutter suppression systems for two and three-dimensional lifting surfaces, utilizing a control moment gyro (CMG) to generate the required control torques. Incompressible flow theory is assumed, with the unsteady aerodynamic forces and moments for arbitrary airfoil motion obtained by using the convolution integral based on Wagner's indicial lift function. Linear optimal control theory is applied to find particular optimal sets of gain values which minimize a quadratic performance function. The closed loop system's response to impulsive gust disturbances and the resulting control power requirements are investigated, and the system eigenvalues necessary to minimize the maximum value of control power are determined.

Homeobox gene distal-less is required for neuronal differentiation and neurite outgrowth in the Drosophila olfactory system

PubMed Central

Plavicki, Jessica; Mader, Sara; Pueschel, Eric; Peebles, Patrick; Boekhoff-Falk, Grace

2012-01-01

Vertebrate Dlx genes have been implicated in the differentiation of multiple neuronal subtypes, including cortical GABAergic interneurons, and mutations in Dlx genes have been linked to clinical conditions such as epilepsy and autism. Here we show that the single Drosophila Dlx homolog, distal-less, is required both to specify chemosensory neurons and to regulate the morphologies of their axons and dendrites. We establish that distal-less is necessary for development of the mushroom body, a brain region that processes olfactory information. These are important examples of distal-less function in an invertebrate nervous system and demonstrate that the Drosophila larval olfactory system is a powerful model in which to understand distal-less functions during neurogenesis. PMID:22307614

Thematic mapper flight model preshipment review data package. Volume 4: Appendix. Part G: Miscellaneous system data

NASA Technical Reports Server (NTRS)

1982-01-01

Functional and design data from various thematic mapper subsystems are presented. Coarse focus, modulation transfer function, and shim requirements are addressed along with spectral matching and spatial coverage tests.

Survey on multisensory feedback virtual reality dental training systems.

PubMed

Wang, D; Li, T; Zhang, Y; Hou, J

2016-11-01

Compared with traditional dental training methods, virtual reality training systems integrated with multisensory feedback possess potentials advantages. However, there exist many technical challenges in developing a satisfactory simulator. In this manuscript, we systematically survey several current dental training systems to identify the gaps between the capabilities of these systems and the clinical training requirements. After briefly summarising the components, functions and unique features of each system, we discuss the technical challenges behind these systems including the software, hardware and user evaluation methods. Finally, the clinical requirements of an ideal dental training system are proposed. Future research/development areas are identified based on an analysis of the gaps between current systems and clinical training requirements. © 2015 John Wiley & Sons A/S. Published by John Wiley & Sons Ltd.

Functional and real-time requirements of a multisensor data fusion (MSDF) situation and threat assessment (STA) resource management (RM) system

NASA Astrophysics Data System (ADS)

Duquet, Jean Remi; Bergeron, Pierre; Blodgett, Dale E.; Couture, Jean; Macieszczak, Maciej; Mayrand, Michel; Chalmers, Bruce A.; Paradis, Stephane

1998-03-01

The Research and Development group at Lockheed Martin Canada, in collaboration with the Defence Research Establishment Valcartier, has undertaken a research project in order to capture and analyze the real-time and functional requirements of a next generation Command and Control System (CCS) for the Canadian Patrol Frigates, integrating Multi- Sensor Data Fusion (MSDF), Situation and Threat Assessment (STA) and Resource Management (RM). One important aspect of the project is to define how the use of Artificial Intelligence may optimize the performance of an integrated, real-time MSDF/STA/RM system. A closed-loop simulation environment is being developed to facilitate the evaluation of MSDF/STA/RM concepts, algorithms and architectures. This environment comprises (1) a scenario generator, (2) complex sensor, hardkill and softkill weapon models, (3) a real-time monitoring tool, (4) a distributed Knowledge-Base System (KBS) shell. The latter is being completely redesigned and implemented in-house since no commercial KBS shell could adequately satisfy all the project requirements. The closed- loop capability of the simulation environment, together with its `simulated real-time' capability, allows the interaction between the MSDF/STA/RM system and the environment targets during the execution of a scenario. This capability is essential to measure the performance of many STA and RM functionalities. Some benchmark scenarios have been selected to demonstrate quantitatively the capabilities of the selected MSDF/STA/RM algorithms. The paper describes the simulation environment and discusses the MSDF/STA/RM functionalities currently implemented and their performance as an automatic CCS.

High Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS): Pilot Knowledge, Skills and Abilities

NASA Technical Reports Server (NTRS)

2005-01-01

This report summarizes the initial work accomplished by the ACCESS 5 Human System Integration (HSI) team to identify Unmanned Aircraft System (UAS) Pilot Knowledge, Skill and Ability (KSA), Training and Medical requirements. To derive this information the following tasks were accomplished: a) Mission and Function analyses were performed; b) Applicable FARs and FAA Advisory Circulars (ACs) were reviewed; c) Meetings were conducted with NASA and FAA Human Factors personnel; d) Surveys were completed by ACCESS 5 HSI Working group UA Pilots; e) Coordination meetings were conducted with the ACCESS 5 Policy IPT. The results of these efforts were used to develop a summary of the current qualifications. for an individual to function as a Pilot In Command (PIC) for UAs currently flown by UNITE companies, to develop preliminary Pilot KSAs for each phase of flight, and to delineate preliminary Pilot Training and Medical requirements. These results are to be provided to the Policy IPT to support their development of recommendations for UA Pilot Rating Criteria, training and medical qualifications. It is expected that the initially an instrument rated pilot will be required to serve as the PIC. However, as operational experience is gained, and automation is applied to accomplish various system functions, it is expected that pilot rating criteria could be lessened.

Spacecraft systems engineering: An introduction to the process at GSFC

NASA Technical Reports Server (NTRS)

Fragomeni, Tony; Ryschkewitsch, Michael G.

1993-01-01

The main objective in systems engineering is to devise a coherent total system design capable of achieving the stated requirements. Requirements should be rigid. However, they should be continuously challenged, rechallenged and/or validated. The systems engineer must specify every requirement in order to design, document, implement and conduct the mission. Each and every requirement must be logically considered, traceable and evaluated through various analysis and trade studies in a total systems design. Margins must be determined to be realistic as well as adequate. The systems engineer must also continuously close the loop and verify system performance against the requirements. The fundamental role of the systems engineer, however, is to engineer, not manage. Yet, in large, complex missions, where more than one systems engineer is required, someone needs to manage the systems engineers, and we call them 'systems managers.' Systems engineering management is an overview function which plans, guides, monitors and controls the technical execution of a project as implemented by the systems engineers. As the project moves on through Phases A and B into Phase C/D, the systems engineering tasks become a small portion of the total effort. The systems management role increases since discipline subsystem engineers are conducting analyses and reviewing test data for final review and acceptance by the systems managers.

Propulsion System Choices and Their Implications

NASA Technical Reports Server (NTRS)

Joyner, Claude R., II; Levack, Daniel J. H.; Rhodes, Russell, E.; Robinson, John W.

2010-01-01

In defining a space vehicle architecture, the propulsion system and related subsystem choices will have a major influence on achieving the goals and objectives desired. There are many alternatives and the choices made must produce a system that meets the performance requirements, but at the same time also provide the greatest opportunity of reaching all of the required objectives. Recognizing the above, the SPST Functional Requirements subteam has drawn on the knowledge, expertise, and experience of its members, to develop insight that wiIJ effectively aid the architectural concept developer in making the appropriate choices consistent with the architecture goals. This data not only identifies many selected choices, but also, more importantly, presents the collective assessment of this subteam on the "pros" and the "cons" of these choices. The propulsion system choices with their pros and cons are presented in five major groups. A. System Integration Approach. Focused on the requirement for safety, reliability, dependability, maintainability, and low cost. B. Non-Chemical Propulsion. Focused on choice of propulsion type. C. Chemical Propulsion. Focused on propellant choice implications. D. Functional Integration. Focused on the degree of integration of the many propulsive and closely associated functions, and on the choice of the engine combustion power cycle. E. Thermal Management. Focused on propellant tank insulation and integration. Each of these groups is further broken down into subgroups, and at that level the consensus pros and cons are presented. The intended use of this paper is to provide a resource of focused material for architectural concept developers to use in designing new advanced systems including college design classes. It is also a possible source of input material for developing a model for designing and analyzing advanced concepts to help identify focused technology needs and their priorities.

The oxidation of drugs by fishes

USGS Publications Warehouse

Buhler, Donald R.; Rasmusson, Mary E.

1968-01-01

1. Fish liver microsomal systems have been found to catalyze the hydroxylation of aniline and acetanilide, the N-demethylation of aminopyrine and the O-dealkylation of phenacetin.2. These systems are similar to the corresponding mammalian enzymes and they may be considered to be mixed function oxidase since they require NADPH and oxygen. An absolute requirement for oxygen, however, was difficult to demonstrate for the hepatic phenacetin cleavage system from fish.3. Microsomal drug metabolizing systems from fish have temperature optima which are considerably lower than those of corresponding mammalian systems

Reactive scattering with row-orthonormal hyperspherical coordinates. 4. Four-dimensional-space Wigner rotation function for pentaatomic systems.

PubMed

Kuppermann, Aron

2011-05-14

The row-orthonormal hyperspherical coordinate (ROHC) approach to calculating state-to-state reaction cross sections and bound state levels of N-atom systems requires the use of angular momentum tensors and Wigner rotation functions in a space of dimension N - 1. The properties of those tensors and functions are discussed for arbitrary N and determined for N = 5 in terms of the 6 Euler angles involved in 4-dimensional space.

A ground based phase control system for the solar power satellite, volume 4

NASA Technical Reports Server (NTRS)

Chie, C. M.

1980-01-01

A ground phase control system is studied as an alternative approach to the current reference retrodirective phase control system in order to simplify the spaceborne hardware requirement. Based on waveform selections, functional subsystems to implement the ground-based phase control concept are identified and functionally represented. It was concluded that the feasibility of the concept becomes unclear if the conditions of the ionosphere and satellite motion are not met.

Applications of CCSDS recommendations to Integrated Ground Data Systems (IGDS)

NASA Technical Reports Server (NTRS)

Mizuta, Hiroshi; Martin, Daniel; Kato, Hatsuhiko; Ihara, Hirokazu

1993-01-01

This paper describes an application of the CCSDS Principle Network (CPH) service model to communications network elements of a postulated Integrated Ground Data System (IGDS). Functions are drawn principally from COSMICS (Cosmic Information and Control System), an integrated space control infrastructure, and the Earth Observing System Data and Information System (EOSDIS) Core System (ECS). From functional requirements, this paper derives a set of five communications network partitions which, taken together, support proposed space control infrastructures and data distribution systems. Our functional analysis indicates that the five network partitions derived in this paper should effectively interconnect the users, centers, processors, and other architectural elements of an IGDS. This paper illustrates a useful application of the CCSDS (Consultive Committee for Space Data Systems) Recommendations to ground data system development.

Evolution of enzymes in a series is driven by dissimilar functional demands.

PubMed

Salvador, Armindo; Savageau, Michael A

2006-02-14

That distinct enzyme activities in an unbranched metabolic pathway are evolutionarily tuned to a single functional requirement is a pervasive assumption. Here we test this assumption by examining the activities of two consecutively acting enzymes in human erythrocytes with an approach to quantitative evolutionary design that avoids the above-mentioned assumption. We previously found that avoidance of NADPH depletion during the pulses of oxidative load to which erythrocytes are normally exposed is the main functional requirement mediating selection for high glucose-6-phosphate dehydrogenase activity. In the present study, we find that, in contrast, the maintenance of oxidized glutathione at low concentrations is the main functional requirement mediating selection for high glutathione reductase activity. The results in this case show that, contrary to the assumption of a single functional requirement, natural selection for the normal activities of the distinct enzymes in the pathway is mediated by different requirements. On the other hand, the results agree with the more general principles that underlie our approach. Namely, that (i) the values of biochemical parameters evolve so as to fulfill the various performance requirements that are relevant to achieve high fitness, and (ii) these performance requirements can be inferred from quantitative systems theory considerations, informed by knowledge of specific aspects of the biochemistry, physiology, genetics, and ecology of the organism.

UML and Model Checking

NASA Technical Reports Server (NTRS)

Schneider, F.

1999-01-01

UML use cases conceptually identify function points or major requirements that a software system must satisfy. Sequence diagrams expand each use case to show in temporal sequence a more detailed notion of intended system behavior.

Robot-Assisted Fracture Surgery: Surgical Requirements and System Design.

PubMed

Georgilas, Ioannis; Dagnino, Giulio; Tarassoli, Payam; Atkins, Roger; Dogramadzi, Sanja

2018-03-09

The design of medical devices is a complex and crucial process to ensure patient safety. It has been shown that improperly designed devices lead to errors and associated accidents and costs. A key element for a successful design is incorporating the views of the primary and secondary stakeholders early in the development process. They provide insights into current practice and point out specific issues with the current processes and equipment in use. This work presents how information from a user-study conducted in the early stages of the RAFS (Robot Assisted Fracture Surgery) project informed the subsequent development and testing of the system. The user needs were captured using qualitative methods and converted to operational, functional, and non-functional requirements based on the methods derived from product design and development. This work presents how the requirements inform a new workflow for intra-articular joint fracture reduction using a robotic system. It is also shown how the various elements of the system are developed to explicitly address one or more of the requirements identified, and how intermediate verification tests are conducted to ensure conformity. Finally, a validation test in the form of a cadaveric trial confirms the ability of the designed system to satisfy the aims set by the original research question and the needs of the users.

Analysis of UAS DAA Surveillance in Fast-Time Simulations without DAA Mitigation

NASA Technical Reports Server (NTRS)

Thipphavong, David P.; Santiago, Confesor; Isaacson, David R.; Lee, Seung Man; Refai, Mohamad Said; Snow, James William

2015-01-01

Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of performance standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA surveillance system performance. A recent study conducted using NASA's ACES (Airspace Concept Evaluation System) simulation capability begins to address questions surrounding the development of draft MOPS for DAA surveillance systems. ACES simulations were conducted to study the performance of sensor systems proposed by the SC-228 DAA Surveillance sub-group. Analysis included but was not limited to: 1) number of intruders (both IFR and VFR) detected by all sensors as a function of UAS flight time, 2) number of intruders (both IFR and VFR) detected by radar alone as a function of UAS flight time, and 3) number of VFR intruders detected by all sensors as a function of UAS flight time. The results will be used by SC-228 to inform decisions about the surveillance standards of UAS DAA systems and future requirements development and validation efforts.

Technology requirements for communication satellites in the 1980's

NASA Technical Reports Server (NTRS)

Burtt, J. E.; Moe, C. R.; Elms, R. V.; Delateur, L. A.; Sedlacek, W. C.; Younger, G. G.

1973-01-01

The key technology requirements are defined for meeting the forecasted demands for communication satellite services in the 1985 to 1995 time frame. Evaluation is made of needs for services and technical and functional requirements for providing services. The future growth capabilities of the terrestrial telephone network, cable television, and satellite networks are forecasted. The impact of spacecraft technology and booster performance and costs upon communication satellite costs are analyzed. Systems analysis techniques are used to determine functional requirements and the sensitivities of technology improvements for reducing the costs of meeting requirements. Recommended development plans and funding levels are presented, as well as the possible cost saving for communications satellites in the post 1985 era.

Towards Requirements in Systems Engineering for Aerospace IVHM Design

NASA Technical Reports Server (NTRS)

Saxena, Abhinav; Roychoudhury, Indranil; Lin, Wei; Goebel, Kai

2013-01-01

Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or 'band-aid' solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design.

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 4: PEP functional specification

NASA Technical Reports Server (NTRS)

1979-01-01

The functional, performance, design, and test requirements for the Orbiter power extension package and its associated ground support equipment are defined. Both government and nongovernment standards and specifications are cited for the following subsystems: electrical power, structural/mechanical, avionics, and thermal control. Quality control assurance provisions and preparation for delivery are also discussed.

Security Criteria for Distributed Systems: Functional Requirements.

DTIC Science & Technology

1995-09-01

Open Company Limited. Ziv , J. and A. Lempel . 1977. A Universal Algorithm for Sequential Data Compression . IEEE Transactions on Information Theory Vol...3, SCF-5 DCF-7. Configurable Cryptographic Algorithms (a) It shall be possible to configure the system such that the data confidentiality functions...use different cryptographic algorithms for different protocols (e.g., mail or interprocess communication data ). (b) The modes of encryption

Dynamic reconfiguration of frontal brain networks during executive cognition in humans

PubMed Central

Braun, Urs; Schäfer, Axel; Walter, Henrik; Erk, Susanne; Romanczuk-Seiferth, Nina; Haddad, Leila; Schweiger, Janina I.; Grimm, Oliver; Heinz, Andreas; Tost, Heike; Meyer-Lindenberg, Andreas; Bassett, Danielle S.

2015-01-01

The brain is an inherently dynamic system, and executive cognition requires dynamically reconfiguring, highly evolving networks of brain regions that interact in complex and transient communication patterns. However, a precise characterization of these reconfiguration processes during cognitive function in humans remains elusive. Here, we use a series of techniques developed in the field of “dynamic network neuroscience” to investigate the dynamics of functional brain networks in 344 healthy subjects during a working-memory challenge (the “n-back” task). In contrast to a control condition, in which dynamic changes in cortical networks were spread evenly across systems, the effortful working-memory condition was characterized by a reconfiguration of frontoparietal and frontotemporal networks. This reconfiguration, which characterizes “network flexibility,” employs transient and heterogeneous connectivity between frontal systems, which we refer to as “integration.” Frontal integration predicted neuropsychological measures requiring working memory and executive cognition, suggesting that dynamic network reconfiguration between frontal systems supports those functions. Our results characterize dynamic reconfiguration of large-scale distributed neural circuits during executive cognition in humans and have implications for understanding impaired cognitive function in disorders affecting connectivity, such as schizophrenia or dementia. PMID:26324898

Ontogeny and function of the fifth limb in Cypridocopain ostracods.

PubMed

Kaji, Tomonari

2010-08-01

The exoskeleton of arthropods undergoes reformation at every molting. Accordingly, external morphology can metamorphose through molting. In some crustaceans, the function of appendages is modified through ontogeny. These morphological modifications require accordant modification of the correlation between different body parts because the morphological function depends on the combined correlation between different parts. In the case of crustacean morphology, exoskeleton and muscles are correlated to each other. The functional morphology of the fifth limb of cypridoid ostracods transforms from "walking leg + mouthparts (+ possibly respiratory parts)" to "mouthparts + respiratory parts + grasping hook (in males only)" through ontogeny. In this study, the three-dimensional structures of the exoskeleton and muscular systems were observed by confocal laser-scanning microscopy in some species of suborder Cypridocopina. The muscular system is reportedly not changed by the ontogeny of appendages in females, but it does change in males. Furthermore, regional cell proliferation, which was detected previously, represented the causal factor of exoskeletal modification. I therefore conclude that the enlarged endite in the female fifth limb is produced by exoskeletal modification based on regional cell proliferation, rather than by a change in the muscular system. In contrast, modification in the male requires a change in the muscular system in addition to exoskeletal modification.

Logistics Reduction and Repurposing Beyond Low Earth Orbit

NASA Technical Reports Server (NTRS)

Broyan, James Lee, Jr.; Ewert, Michael K.

2011-01-01

All human space missions, regardless of destination, require significant logistical mass and volume that is strongly proportional to mission duration. Anything that can be done to reduce initial mass and volume of supplies or reuse items that have been launched will be very valuable. Often, the logistical items require disposal and represent a trash burden. Utilizing systems engineering to analyze logistics from cradle-to-grave and then to potential reuse, can minimize logistics contributions to total mission architecture mass. In NASA's Advanced Exploration Systems Logistics Reduction and Repurposing Project , various tasks will reduce the intrinsic mass of logistical packaging, enable reuse and repurposing of logistical packaging and carriers for other habitation, life support, crew health, and propulsion functions, and reduce or eliminate the nuisances aspects of trash at the same time. Repurposing reduces the trash burden and eliminates the need for hardware whose function can be provided by use of spent logistic items. However, these reuse functions need to be identified and built into future logical systems to enable them to effectively have a secondary function. These technologies and innovations will help future logistic systems to support multiple exploration missions much more efficiently.

Design and experiment of a neural signal detection using a FES driving system.

PubMed

Zonghao, Huang; Zhigong, Wang; Xiaoying, Lu; Wenyuan, Li; Xiaoyan, Shen; Xintai, Zhao; Shushan, Xie; Haixian, Pan; Cunliang, Zhu

2010-01-01

The channel bridging, signal regenerating, and functional rebuilding of injured nerves is one of the most important issues in life science research. In recent years, some progresses in the research area have been made in repairing injured nerves with microelectronic neural bridge. Based on the previous work, this paper presents a neural signal detection and functional electrical stimulation (FES) driving system with using high performance operational amplifiers, which has been realized. The experimental results show that the designed system meets requirements. In animal experiments, sciatic nerve signal detection, regeneration and function rebuilding between two toads have been accomplished successfully by using the designed system.

A pilot's opinion - VTOL control design requirements for the instrument approach task.

NASA Technical Reports Server (NTRS)

Patton, J. M., Jr.

1972-01-01

This paper presents pilot opinion supported by test data concerning flight control and display concepts and control system design requirements for VTOL aircraft in the instrument approach task. Material presented is drawn from research flights in the following aircraft: Dornier DO-31, Short SC-1, LTV XC-142A, and Boeing-Vertol CH-46. The control system concepts and mechanizations employed in the above aircraft are discussed, and the effect of control system augmentation is shown on performance. Operational procedures required in the instrument approach task are described, with comments on need for automation and combining of control functions.

Space shuttle main engine definition (phase B). Volume 2: Avionics. [for space shuttle

NASA Technical Reports Server (NTRS)

1971-01-01

The advent of the space shuttle engine with its requirements for high specific impulse, long life, and low cost have dictated a combustion cycle and a closed loop control system to allow the engine components to run close to operating limits. These performance requirements, combined with the necessity for low operational costs, have placed new demands on rocket engine control, system checkout, and diagnosis technology. Based on considerations of precision environment, and compatibility with vehicle interface commands, an electronic control, makes available many functions that logically provide the information required for engine system checkout and diagnosis.

Technology demonstrator program for Space Station Environmental Control Life Support System

NASA Technical Reports Server (NTRS)

Adams, Alan M.; Platt, Gordon K.; Claunch, William C.; Humphries, William R.

1987-01-01

The main objectives and requirements of the NASA/Marshall Space Flight Center Technology Demonstration Program are discussed. The program consists of a comparative test and a 90-day manned system test to evaluate an Environmental Control and Life Support System (ECLSS). In the comparative test phase, 14 types of subsystems which perform oxygen and water reclamation functions are to be examined in terms of performance maintenance/service requirements, reliability, and safety. The manned chamber testing phase involves a four person crew using a partial ECLSS for 90 days. The schedule for the program and the program hardware requirements are described.

Space shuttle propulsion systems on-board checkout and monitoring system development study

NASA Technical Reports Server (NTRS)

1971-01-01

Investigations on the fundamental space shuttle propulsion systems program are reported, with emphasis on in-depth reviews of preliminary drafts of the guidelines. The guidelines will be used to incorporate the onboard checkout and monitoring function into the basic design of the propulsion systems and associated interfacing systems. The analysis of checkout and monitoring requirements of the Titan 3 L expandable booster propulsion systems was completed, and the techniques for accomplishing the checkout and monitoring functions were determined. Updating results of the basic study of propulsion system checkout and monitoring is continuing.

Final Report - Regulatory Considerations for Adaptive Systems

NASA Technical Reports Server (NTRS)

Wilkinson, Chris; Lynch, Jonathan; Bharadwaj, Raj

2013-01-01

This report documents the findings of a preliminary research study into new approaches to the software design assurance of adaptive systems. We suggest a methodology to overcome the software validation and verification difficulties posed by the underlying assumption of non-adaptive software in the requirementsbased- testing verification methods in RTCA/DO-178B and C. An analysis of the relevant RTCA/DO-178B and C objectives is presented showing the reasons for the difficulties that arise in showing satisfaction of the objectives and suggested additional means by which they could be satisfied. We suggest that the software design assurance problem for adaptive systems is principally one of developing correct and complete high level requirements and system level constraints that define the necessary system functional and safety properties to assure the safe use of adaptive systems. We show how analytical techniques such as model based design, mathematical modeling and formal or formal-like methods can be used to both validate the high level functional and safety requirements, establish necessary constraints and provide the verification evidence for the satisfaction of requirements and constraints that supplements conventional testing. Finally the report identifies the follow-on research topics needed to implement this methodology.

Multipurpose silicon photonics signal processor core.

PubMed

Pérez, Daniel; Gasulla, Ivana; Crudgington, Lee; Thomson, David J; Khokhar, Ali Z; Li, Ke; Cao, Wei; Mashanovich, Goran Z; Capmany, José

2017-09-21

Integrated photonics changes the scaling laws of information and communication systems offering architectural choices that combine photonics with electronics to optimize performance, power, footprint, and cost. Application-specific photonic integrated circuits, where particular circuits/chips are designed to optimally perform particular functionalities, require a considerable number of design and fabrication iterations leading to long development times. A different approach inspired by electronic Field Programmable Gate Arrays is the programmable photonic processor, where a common hardware implemented by a two-dimensional photonic waveguide mesh realizes different functionalities through programming. Here, we report the demonstration of such reconfigurable waveguide mesh in silicon. We demonstrate over 20 different functionalities with a simple seven hexagonal cell structure, which can be applied to different fields including communications, chemical and biomedical sensing, signal processing, multiprocessor networks, and quantum information systems. Our work is an important step toward this paradigm.Integrated optical circuits today are typically designed for a few special functionalities and require complex design and development procedures. Here, the authors demonstrate a reconfigurable but simple silicon waveguide mesh with different functionalities.

Multi-level Expression Design Language: Requirement level (MEDL-R) system evaluation

NASA Technical Reports Server (NTRS)

1980-01-01

An evaluation of the Multi-Level Expression Design Language Requirements Level (MEDL-R) system was conducted to determine whether it would be of use in the Goddard Space Flight Center Code 580 software development environment. The evaluation is based upon a study of the MEDL-R concept of requirement languages, the functions performed by MEDL-R, and the MEDL-R language syntax. Recommendations are made for changes to MEDL-R that would make it useful in the Code 580 environment.

IGDS/TRAP Interface Program (ITIP). Software Design Document

NASA Technical Reports Server (NTRS)

Jefferys, Steve; Johnson, Wendell

1981-01-01

The preliminary design of the IGDS/TRAP Interface Program (ITIP) is described. The ITIP is implemented on the PDP 11/70 and interfaces directly with the Interactive Graphics Design System and the Data Management and Retrieval System. The program provides an efficient method for developing a network flow diagram. Performance requirements, operational rquirements, and design requirements are discussed along with sources and types of input and destination and types of output. Information processing functions and data base requirements are also covered.

An iterative requirements specification procedure for decision support systems.

PubMed

Brookes, C H

1987-08-01

Requirements specification is a key element in a DSS development project because it not only determines what is to be done, it also drives the evolution process. A procedure for requirements elicitation is described that is based on the decomposition of the DSS design task into a number of functions, subfunctions, and operators. It is postulated that the procedure facilitates the building of a DSS that is complete and integrates MIS, modelling and expert system components. Some examples given are drawn from the health administration field.

75 FR 2597 - Positive Train Control Systems

Federal Register 2010, 2011, 2012, 2013, 2014

2010-01-15

... requirements for PTC system standard design and functionality, the associated submissions for FRA PTC system..., notwithstanding enforcement of railroad operating rules designed to prevent them. As early as 1970, following its... workers continued as a result of the absence of effective enforcement systems designed to compensate for...

HAL/S-FC compiler system functional specification

NASA Technical Reports Server (NTRS)

1974-01-01

Compiler organization is discussed, including overall compiler structure, internal data transfer, compiler development, and code optimization. The user, system, and SDL interfaces are described, along with compiler system requirements. Run-time software support package and restrictions and dependencies are also considered of the HAL/S-FC system.

Smed-dynA-1 is a planarian nervous system specific dynamin 1 homolog required for normal locomotion.

PubMed

Talbot, Jared A; Currie, Ko W; Pearson, Bret J; Collins, Eva-Maria S

2014-06-20

Dynamins are GTPases that are required for separation of vesicles from the plasma membrane and thus are key regulators of endocytosis in eukaryotic cells. This role for dynamin proteins is especially crucial for the proper function of neurons, where they ensure that synaptic vesicles and their neurotransmitter cargo are recycled in the presynaptic cell. Here we have characterized the dynamin protein family in the freshwater planarian Schmidtea mediterranea and showed that it possesses six dynamins with tissue specific expression profiles. Of these six planarian homologs, two are necessary for normal tissue homeostasis, and the loss of another, Smed-dynA-1, leads to an abnormal behavioral phenotype, which we have quantified using automated center of mass tracking. Smed-dynA-1 is primarily expressed in the planarian nervous system and is a functional homolog of the mammalian Dynamin I. The distinct expression profiles of the six dynamin genes makes planarians an interesting new system to reveal novel dynamin functions, which may be determined by their differential tissue localization. The observed complexity of neurotransmitter regulation combined with the tools of quantitative behavioral assays as a functional readout for neuronal activity, renders planarians an ideal system for studying how the nervous system controls behavior. © 2014. Published by The Company of Biologists Ltd.

Smed-dynA-1 is a planarian nervous system specific dynamin 1 homolog required for normal locomotion

PubMed Central

Talbot, Jared A.; Currie, Ko W.; Pearson, Bret J.; Collins, Eva-Maria S.

2014-01-01

ABSTRACT Dynamins are GTPases that are required for separation of vesicles from the plasma membrane and thus are key regulators of endocytosis in eukaryotic cells. This role for dynamin proteins is especially crucial for the proper function of neurons, where they ensure that synaptic vesicles and their neurotransmitter cargo are recycled in the presynaptic cell. Here we have characterized the dynamin protein family in the freshwater planarian Schmidtea mediterranea and showed that it possesses six dynamins with tissue specific expression profiles. Of these six planarian homologs, two are necessary for normal tissue homeostasis, and the loss of another, Smed-dynA-1, leads to an abnormal behavioral phenotype, which we have quantified using automated center of mass tracking. Smed-dynA-1 is primarily expressed in the planarian nervous system and is a functional homolog of the mammalian Dynamin I. The distinct expression profiles of the six dynamin genes makes planarians an interesting new system to reveal novel dynamin functions, which may be determined by their differential tissue localization. The observed complexity of neurotransmitter regulation combined with the tools of quantitative behavioral assays as a functional readout for neuronal activity, renders planarians an ideal system for studying how the nervous system controls behavior. PMID:24950970

Statistical Requirements For Pass-Fail Testing Of Contraband Detection Systems

NASA Astrophysics Data System (ADS)

Gilliam, David M.

2011-06-01

Contraband detection systems for homeland security applications are typically tested for probability of detection (PD) and probability of false alarm (PFA) using pass-fail testing protocols. Test protocols usually require specified values for PD and PFA to be demonstrated at a specified level of statistical confidence CL. Based on a recent more theoretical treatment of this subject [1], this summary reviews the definition of CL and provides formulas and spreadsheet functions for constructing tables of general test requirements and for determining the minimum number of tests required. The formulas and tables in this article may be generally applied to many other applications of pass-fail testing, in addition to testing of contraband detection systems.

Conceptual design studies of control and instrumentation systems for ignition experiments

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

Nicholson, P.J.; Dewolf, J.B.; Heinemann, P.C.

1978-03-01

Studies at the Charles Stark Draper Laboratory in the past year were a continuation of prior studies of control and instrumentation systems for current and next generation Tokomaks. Specifically, the FY 77 effort has focused on the following two main efforts: (1) control requirements--(a) defining and evolving control requirements/concepts for a prototype experimental power reactor(s), and (b) defining control requirements for diverters and mirror machines, specifically the MX; and (2) defining requirements and scoping design for a functional control simulator. Later in the year, a small additional task was added: (3) providing analysis and design support to INESCO for itsmore » low cost fusion power system, FPC/DMT.« less

Development of functional requirements for electronic health communication: preliminary results from the ELIN project.

PubMed

Christensen, Tom; Grimsmo, Anders

2005-01-01

User participation is important for developing a functional requirements specification for electronic communication. General practitioners and practising specialists, however, often work in small practices without the resources to develop and present their requirements. It was necessary to find a method that could engage practising doctors in order to promote their needs related to electronic communication. Qualitative research methods were used, starting a process to develop and study documents and collect data from meetings in project groups. Triangulation was used, in that the participants were organised into a panel of experts, a user group, a supplier group and an editorial committee. The panel of experts created a list of functional requirements for electronic communication in health care, consisting of 197 requirements, in addition to 67 requirements selected from an existing Norwegian standard for electronic patient records (EPRs). Elimination of paper copies sent in parallel with electronic messages, optimal workflow, a common electronic 'envelope' with directory services for units and end-users, and defined requirements for content with the possibility of decision support were the most important requirements. The results indicate that we have found a method of developing functional requirements which provides valid results both for practising doctors and for suppliers of EPR systems.

Planetary data system requirements: Multi-mission radio science requirements for the 1978 to 1988 era

NASA Technical Reports Server (NTRS)

Howard, H. T. (Editor)

1979-01-01

The functional and performance requirements for support of multimission radio science are established. The classes of radio science investigation are described and the needed data is discussed. This document is for a sliding ten year period and will be iterated as the mission set evolves.

25 CFR 273.54 - Privacy Act requirements.

Code of Federal Regulations, 2012 CFR

2012-04-01

... 25 Indians 1 2012-04-01 2011-04-01 true Privacy Act requirements. 273.54 Section 273.54 Indians... Privacy Act requirements. (a) When a contractor operates a system of records to accomplish a Bureau function, the contractor shall comply with subpart D of 43 CFR part 2 which implements the Privacy Act (5 U...

25 CFR 273.54 - Privacy Act requirements.

Code of Federal Regulations, 2013 CFR

2013-04-01

... 25 Indians 1 2013-04-01 2013-04-01 false Privacy Act requirements. 273.54 Section 273.54 Indians... Privacy Act requirements. (a) When a contractor operates a system of records to accomplish a Bureau function, the contractor shall comply with subpart D of 43 CFR part 2 which implements the Privacy Act (5 U...

25 CFR 273.54 - Privacy Act requirements.

Code of Federal Regulations, 2011 CFR

2011-04-01

... 25 Indians 1 2011-04-01 2011-04-01 false Privacy Act requirements. 273.54 Section 273.54 Indians... Privacy Act requirements. (a) When a contractor operates a system of records to accomplish a Bureau function, the contractor shall comply with subpart D of 43 CFR part 2 which implements the Privacy Act (5 U...

25 CFR 273.54 - Privacy Act requirements.

Code of Federal Regulations, 2014 CFR

2014-04-01

... 25 Indians 1 2014-04-01 2014-04-01 false Privacy Act requirements. 273.54 Section 273.54 Indians... Privacy Act requirements. (a) When a contractor operates a system of records to accomplish a Bureau function, the contractor shall comply with subpart D of 43 CFR part 2 which implements the Privacy Act (5 U...

25 CFR 273.54 - Privacy Act requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 25 Indians 1 2010-04-01 2010-04-01 false Privacy Act requirements. 273.54 Section 273.54 Indians... Privacy Act requirements. (a) When a contractor operates a system of records to accomplish a Bureau function, the contractor shall comply with subpart D of 43 CFR part 2 which implements the Privacy Act (5 U...

76 FR 58803 - Commission Information Collection Activities (FERC-725A); Comment Request; Submitted for OMB Review

Federal Register 2010, 2011, 2012, 2013, 2014

2011-09-22

... in Docket No. RD11-4-000 under the requirements of FERC-725A, ``Mandatory Reliability Standards for the Bulk-Power System'' (OMB No. 1902-0244), is required by Commission-approved Reliability Standard EOP-008-1 (Loss of Control Center Functionality) that requires reliability coordinators, transmission...

Shuttle ku-band communications/radar technical concepts

NASA Technical Reports Server (NTRS)

Griffin, J. W.; Kelley, J. S.; Steiner, A. W.; Vang, H. A.; Zrubek, W. E.; Huth, G. K.

1985-01-01

Technical data on the Shuttle Orbiter K sub u-band communications/radar system are presented. The more challenging aspects of the system design and development are emphasized. The technical problems encountered and the advancements made in solving them are discussed. The radar functions are presented first. Requirements and design/implementation approaches are discussed. Advanced features are explained, including Doppler measurement, frequency diversity, multiple pulse repetition frequencies and pulse widths, and multiple modes. The communications functions that are presented include advances made because of the requirements for multiple communications modes. Spread spectrum, quadrature phase shift keying (QPSK), variable bit rates, and other advanced techniques are discussed. Performance results and conclusions reached are outlined.