Cold Vacuum Drying facility civil structural system design description (SYS 06)

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

PITKOFF, C.C.

This document describes the Cold Vacuum Drying (CVD) Facility civil - structural system. This system consists of the facility structure, including the administrative and process areas. The system's primary purpose is to provide for a facility to house the CVD process and personnel and to provide a tertiary level of containment. The document provides a description of the facility and demonstrates how the design meets the various requirements imposed by the safety analysis report and the design requirements document.

76 FR 49303 - Approval and Promulgation of Air Quality Implementation Plans; Minnesota; Rules Update

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-10

... design requirements for the monitoring systems. The revised CMS rules also delineate the recordkeeping..., [Insert page number where the document begins]. 7017.1140 CEMS design 03/01/99 08/10/11, [Insert page...]. 7017.1190 COMS design 03/01/99 08/10/11, [Insert page requirements. number where the document begins...

Standardization of a Safing and Arming Device for Artillery Ammunition

DTIC Science & Technology

1976-10-01

designated by other author- ized documents. UNCLASSIFIED SECURITY CLASSIFICATION OF THIS PAGE (When Dala Entered) REPORT DOCUMENTATION PAGE READ...establish the physical and military requirements. Design studies were initiated on the current S&A devices. • DD FOR’* •’*• 1 JAN 73 1473...A developer. In the design of any mechanism, a precise definition of S&A requirements for all fuze applications is required prior to development

IT Requirements Integration in High-Rise Construction Design Projects

NASA Astrophysics Data System (ADS)

Levina, Anastasia; Ilin, Igor; Esedulaev, Rustam

2018-03-01

The paper discusses the growing role of IT support for the operation of modern high-rise buildings, due to the complexity of managing engineering systems of buildings and the requirements of consumers for the IT infrastructure. The existing regulatory framework for the development of design documentation for construction, including high-rise buildings, is analyzed, and the lack of coherence in the development of this documentation with the requirements for the creation of an automated management system and the corresponding IT infrastructure is stated. The lack of integration between these areas is the cause of delays and inefficiencies both at the design stage and at the stage of putting the building into operation. The paper proposes an approach to coordinate the requirements of the IT infrastructure of high-rise buildings and design documentation for construction. The solution to this problem is possible within the framework of the enterprise architecture concept by coordinating the requirements of the IT and technological layers at the design stage of the construction.

CANISTER HANDLING FACILITY DESCRIPTION DOCUMENT

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

J.F. Beesley

The purpose of this facility description document (FDD) is to establish requirements and associated bases that drive the design of the Canister Handling Facility (CHF), which will allow the design effort to proceed to license application. This FDD will be revised at strategic points as the design matures. This FDD identifies the requirements and describes the facility design, as it currently exists, with emphasis on attributes of the design provided to meet the requirements. This FDD is an engineering tool for design control; accordingly, the primary audience and users are design engineers. This FDD is part of an iterative designmore » process. It leads the design process with regard to the flowdown of upper tier requirements onto the facility. Knowledge of these requirements is essential in performing the design process. The FDD follows the design with regard to the description of the facility. The description provided in this FDD reflects the current results of the design process.« less

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.

Transit safety retrofit package development : architecture and design specifications.

DOT National Transportation Integrated Search

2014-05-01

The Architecture and Design Specifications capture the TRP system architecture and design that fulfills the technical objectives stated in the TRP requirements document. The document begins with an architectural overview that identifies and describes...

Designing Flightdeck Procedures

NASA Technical Reports Server (NTRS)

Barshi, Immanuel; Mauro, Robert; Degani, Asaf; Loukopoulou, Loukia

2016-01-01

The primary goal of this document is to provide guidance on how to design, implement, and evaluate flight deck procedures. It provides a process for developing procedures that meet clear and specific requirements. This document provides a brief overview of: 1) the requirements for procedures, 2) a process for the design of procedures, and 3) a process for the design of checklists. The brief overview is followed by amplified procedures that follow the above steps and provide details for the proper design, implementation and evaluation of good flight deck procedures and checklists.

System analysis study of space platform and station accommodations for life sciences research facilities. Volume 1: Executive summary. Phase A: Conceptual design and programmatics

NASA Technical Reports Server (NTRS)

1985-01-01

The study was conducted in 3 parts over a 3 year period. The study schedule and the documentation associated with each study part is given. This document summarized selected study results from the conceptual design and programmatics segment of the effort. The objectives were: (1) to update requirements and tradeoffs and develop a detailed design and mission requirements document; (2) to develop conceptual designs and mission descriptions; and (3) to develop programmatic, i.e., work breakdown structure and work breakdown structure dictionary, estimated cost, and implementing plans and schedules.

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

Tiradani, Tiradani,Anthony; Altunay, Mine; Dagenhart, David

The Decision Engine is a critical component of the HEP Cloud Facility. It provides the functionality of resource scheduling for disparate resource providers, including those which may have a cost or a restricted allocation of cycles. Along with the architecture, design, and requirements for the Decision Engine, this document will provide the rationale and explanations for various design decisions. In some cases, requirements and interfaces for a limited subset of external services will be included in this document. This document is intended to be a high level design. The design represented in this document is not complete and does notmore » break everything down in detail. The class structures and pseudo-code exist for example purposes to illustrate desired behaviors, and as such, should not be taken literally. The protocols and behaviors are the important items to take from this document. This project is still in prototyping mode so flaws and inconsistencies may exist and should be noted and treated as failures.« less

Safeguards Guidance Document for Designers of Commercial Nuclear Facilities: International Nuclear Safeguards Requirements and Practices For Uranium Enrichment Plants

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

Robert Bean; Casey Durst

2009-10-01

This report is the second in a series of guidelines on international safeguards requirements and practices, prepared expressly for the designers of nuclear facilities. The first document in this series is the description of generic international nuclear safeguards requirements pertaining to all types of facilities. These requirements should be understood and considered at the earliest stages of facility design as part of a new process called “Safeguards-by-Design.” This will help eliminate the costly retrofit of facilities that has occurred in the past to accommodate nuclear safeguards verification activities. The following summarizes the requirements for international nuclear safeguards implementation at enrichmentmore » plants, prepared under the Safeguards by Design project, and funded by the U.S. Department of Energy (DOE) National Nuclear Security Administration (NNSA), Office of NA-243. The purpose of this is to provide designers of nuclear facilities around the world with a simplified set of design requirements and the most common practices for meeting them. The foundation for these requirements is the international safeguards agreement between the country and the International Atomic Energy Agency (IAEA), pursuant to the Treaty on the Non-proliferation of Nuclear Weapons (NPT). Relevant safeguards requirements are also cited from the Safeguards Criteria for inspecting enrichment plants, found in the IAEA Safeguards Manual, Part SMC-8. IAEA definitions and terms are based on the IAEA Safeguards Glossary, published in 2002. The most current specification for safeguards measurement accuracy is found in the IAEA document STR-327, “International Target Values 2000 for Measurement Uncertainties in Safeguarding Nuclear Materials,” published in 2001. For this guide to be easier for the designer to use, the requirements have been restated in plainer language per expert interpretation using the source documents noted. The safeguards agreement is fundamentally a legal document. As such, it is written in a legalese that is understood by specialists in international law and treaties, but not by most outside of this field, including designers of nuclear facilities. For this reason, many of the requirements have been simplified and restated. However, in all cases, the relevant source document and passage is noted so that readers may trace the requirement to the source. This is a helpful living guide, since some of these requirements are subject to revision over time. More importantly, the practices by which the requirements are met are continuously modernized by the IAEA and nuclear facility operators to improve not only the effectiveness of international nuclear safeguards, but also the efficiency. As these improvements are made, the following guidelines should be updated and revised accordingly.« less

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.

Automated documentation generator for advanced protein crystal growth

NASA Technical Reports Server (NTRS)

Maddux, Gary A.; Provancha, Anna; Chattam, David

1994-01-01

To achieve an environment less dependent on the flow of paper, automated techniques of data storage and retrieval must be utilized. This software system, 'Automated Payload Experiment Tool,' seeks to provide a knowledge-based, hypertext environment for the development of NASA documentation. Once developed, the final system should be able to guide a Principal Investigator through the documentation process in a more timely and efficient manner, while supplying more accurate information to the NASA payload developer. The current system is designed for the development of the Science Requirements Document (SRD), the Experiment Requirements Document (ERD), the Project Plan, and the Safety Requirements Document.

2002 Controls Design Challenge

NASA Technical Reports Server (NTRS)

Hess, Ronald A.; Vetter, T. K.; Wells, S. R.

2002-01-01

This document is intended to provide the specifications and requirements for a flight control system design challenge. The response to the challenge will involve documenting whether the particular design has met the stated requirements through analysis and computer simulation. The response should be written in the general format of a technical publication with corresponding length limits, e.g., an approximate maximum length of 45 units, with each full-size figure and double-spaced typewritten page constituting one unit.

Spaceflight Human System Standards

NASA Technical Reports Server (NTRS)

Holubec, Keith; Tillman, Barry; Connolly, Jan

2009-01-01

NASA created a new approach for human system integration and human performance standards. NASA created two documents a standard and a reference handbook. The standard is titled NASA Space Flight Human-System Standard (SFHSS) and consists of two-volumes: Volume 1- Crew Health This volume covers standards needed to support astronaut health (medical care, nutrition, sleep, exercise, etc.) Volume 2 Human Factors, Habitability and Environmental Health This volume covers the standards for system design that will maintain astronaut performance (ie., environmental factors, design of facilities, layout of workstations, and lighting requirements). It includes classic human factors requirements. The new standards document is written in terms so that it is applicable to a broad range of present and future NASA systems. The document states that all new programs prepare system-specific requirements that will meet the general standards. For example, the new standard does not specify a design should accommodate specific percentiles of a defined population. Rather, NASA-STD-3001, Volume 2 states that all programs shall prepare program-specific requirements that define the user population and their size ranges. The design shall then accommodate the full size range of those users. The companion reference handbook, Human Integration Design Handbook (HIDH), was developed to capture the design consideration information from NASA-STD-3000, and adds spaceflight lessons learned, gaps in knowledge, example solutions, and suggests research to further mature specific disciplines. The HIDH serves two major purposes: HIDH is the reference document for writing human factors requirements for specific systems. HIDH contains design guidance information that helps insure that designers create systems which safely and effectively accommodate the capabilities and limitations of space flight crews.

Crewed Space Vehicle Battery Safety Requirements

NASA Technical Reports Server (NTRS)

Jeevarajan, Judith A.; Darcy, Eric C.

2014-01-01

This requirements document is applicable to all batteries on crewed spacecraft, including vehicle, payload, and crew equipment batteries. It defines the specific provisions required to design a battery that is safe for ground personnel and crew members to handle and/or operate during all applicable phases of crewed missions, safe for use in the enclosed environment of a crewed space vehicle, and safe for use in launch vehicles, as well as in unpressurized spaces adjacent to the habitable portion of a space vehicle. The required provisions encompass hazard controls, design evaluation, and verification. The extent of the hazard controls and verification required depends on the applicability and credibility of the hazard to the specific battery design and applicable missions under review. Evaluation of the design and verification program results shall be completed prior to certification for flight and ground operations. This requirements document is geared toward the designers of battery systems to be used in crewed vehicles, crew equipment, crew suits, or batteries to be used in crewed vehicle systems and payloads (or experiments). This requirements document also applies to ground handling and testing of flight batteries. Specific design and verification requirements for a battery are dependent upon the battery chemistry, capacity, complexity, charging, environment, and application. The variety of battery chemistries available, combined with the variety of battery-powered applications, results in each battery application having specific, unique requirements pertinent to the specific battery application. However, there are basic requirements for all battery designs and applications, which are listed in section 4. Section 5 includes a description of hazards and controls and also includes requirements.

NASA Software Documentation Standard

NASA Technical Reports Server (NTRS)

1991-01-01

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Optimization in the systems engineering process

NASA Technical Reports Server (NTRS)

Lemmerman, Loren A.

1993-01-01

The essential elements of the design process consist of the mission definition phase that provides the system requirements, the conceptual design, the preliminary design and finally the detailed design. Mission definition is performed largely by operations analysts in conjunction with the customer. The result of their study is handed off to the systems engineers for documentation as the systems requirements. The document that provides these requirements is the basis for the further design work of the design engineers at the Lockheed-Georgia Company. The design phase actually begins with conceptual design, which is generally conducted by a small group of engineers using multidisciplinary design programs. Because of the complexity of the design problem, the analyses are relatively simple and generally dependent on parametric analyses of the configuration. The result of this phase is a baseline configuration from which preliminary design may be initiated.

Structural Design Requirements and Factors of Safety for Spaceflight Hardware: For Human Spaceflight. Revision A

NASA Technical Reports Server (NTRS)

Bernstein, Karen S.; Kujala, Rod; Fogt, Vince; Romine, Paul

2011-01-01

This document establishes the structural requirements for human-rated spaceflight hardware including launch vehicles, spacecraft and payloads. These requirements are applicable to Government Furnished Equipment activities as well as all related contractor, subcontractor and commercial efforts. These requirements are not imposed on systems other than human-rated spacecraft, such as ground test articles, but may be tailored for use in specific cases where it is prudent to do so such as for personnel safety or when assets are at risk. The requirements in this document are focused on design rather than verification. Implementation of the requirements is expected to be described in a Structural Verification Plan (SVP), which should describe the verification of each structural item for the applicable requirements. The SVP may also document unique verifications that meet or exceed these requirements with NASA Technical Authority approval.

A knowledge-based approach to configuration layout, justification, and documentation

NASA Technical Reports Server (NTRS)

Craig, F. G.; Cutts, D. E.; Fennel, T. R.; Case, C.; Palmer, J. R.

1990-01-01

The design, development, and implementation is described of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on Space Station Freedom. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

A Knowledge-Based Approach to Configuration Layout, Justification, and Documentation

NASA Technical Reports Server (NTRS)

Craig, F. G.; Cutts, D. E.; Fennel, T. R.; Case, C. M.; Palmer, J. R.

1991-01-01

The design, development, and implementation of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on the Space Station Freedom are described. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

Fort Hood Solar Total Energy Project. Volume II. Preliminary design. Part 1. System criteria and design description. Final report

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

None,

1979-01-01

This volume documents the preliminary design developed for the Solar Total Energy System to be installed at Fort Hood, Texas. Current system, subsystem, and component designs are described and additional studies which support selection among significant design alternatives are presented. Overall system requirements which form the system design basis are presented. These include program objectives; performance and output load requirements; industrial, statutory, and regulatory standards; and site interface requirements. Material in this section will continue to be issued separately in the Systems Requirements Document and maintained current through revision throughout future phases of the project. Overall system design and detailedmore » subsystem design descriptions are provided. Consideration of operation and maintenance is reflected in discussion of each subsystem design as well as in an integrated overall discussion. Included are the solar collector subsystem; the thermal storage subsystem, the power conversion sybsystem (including electrical generation and distribution); the heating/cooling and domestic hot water subsystems; overall instrumentation and control; and the STES building and physical plant. The design of several subsystems has progressed beyond the preliminary stage; descriptions for such subsystems are therefore provided in more detail than others to provide complete documentation of the work performed. In some cases, preliminary design parameters require specific verificaton in the definitive design phase and are identified in the text. Subsystem descriptions will continue to be issued and revised separately to maintain accuracy during future phases of the project. (WHK)« less

GCS programmer's manual

NASA Technical Reports Server (NTRS)

Lowman, Douglas S.; Withers, B. Edward; Shagnea, Anita M.; Dent, Leslie A.; Hayhurst, Kelly J.

1990-01-01

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

Flight design system-1 system design. Volume 5: Data management and data base documentation support system. [for shuttle flight planning

NASA Technical Reports Server (NTRS)

1979-01-01

Application software intended to reduce the man-hours required per flight design cycle by producing major flight design documents with little or no manual typing is described. The documentation support software is divided into two separately executable processors. However, since both processors support the same overall functions, and most of the software contained in one is also contained in the other, both are collectively presented.

A nursing-specific model of EPR documentation: organizational and professional requirements.

PubMed

von Krogh, Gunn; Nåden, Dagfinn

2008-01-01

To present the Norwegian documentation KPO model (quality assurance, problem solving, and caring). To present the requirements and multiple electronic patient record (EPR) functions the model is designed to address. The model's professional substance, a conceptual framework for nursing practice is developed by examining, reorganizing, and completing existing frameworks. The model's methodology, an information management system, is developed using an expert group. Both model elements were clinically tested over a period of 1 year. The model is designed for nursing documentation in step with statutory, organizational, and professional requirements. Complete documentation is arranged for by incorporating the Nursing Minimum Data Set. A systematic and comprehensive documentation is arranged for by establishing categories as provided in the model's framework domains. Consistent documentation is arranged for by incorporating NANDA-I Nursing Diagnoses, Nursing Intervention Classification, and Nursing Outcome Classification. The model can be used as a tool in cooperation with vendors to ensure the interests of the nursing profession is met when developing EPR solutions in healthcare. The model can provide clinicians with a framework for documentation in step with legal and organizational requirements and at the same time retain the ability to record all aspects of clinical nursing.

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

The Johnson Space Center Management Information Systems (JSCMIS). 1: Requirements Definition and Design Specifications for Versions 2.1 and 2.1.1. 2: Documented Test Scenario Environments. 3: Security Design and Specifications

NASA Technical Reports Server (NTRS)

1986-01-01

The Johnson Space Center Management Information System (JSCMIS) is an interface to computer data bases at NASA Johnson which allows an authorized user to browse and retrieve information from a variety of sources with minimum effort. This issue gives requirements definition and design specifications for versions 2.1 and 2.1.1, along with documented test scenario environments, and security object design and specifications.

50 CFR 221.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2010 CFR

2010-10-01

... the requirements for requests for documents or tangible things or entry on land? (a) Motion. Except... tangible things or entry on designated land must file a motion under § 221.41(c). A request may include any..., testing, or sampling; or (3) Entry on designated land or other property for inspection and measuring...

50 CFR 221.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2011 CFR

2011-10-01

... the requirements for requests for documents or tangible things or entry on land? (a) Motion. Except... tangible things or entry on designated land must file a motion under § 221.41(c). A request may include any..., testing, or sampling; or (3) Entry on designated land or other property for inspection and measuring...

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.

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

NASA Technical Reports Server (NTRS)

1989-01-01

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

Higher speed freight truck design : performance requirements.

DOT National Transportation Integrated Search

2013-10-01

This proposed requirements document combines a set of requirements for high-speed freight car truck design and performance : from the generally accepted standards in the U.S. Code of Federal Regulation (CFR), the Association of American Railroads : (...

Maintainability Program Requirements for Space Systems

NASA Technical Reports Server (NTRS)

1987-01-01

This document is established to provide common general requirements for all NASA programs to: design maintainability into all systems where maintenance is a factor in system operation and mission success; and ensure that maintainability characteristics are developed through the systems engineering process. These requirements are not new. Design for ease of maintenance and minimization of repair time have always been fundamental requirements of the systems engineering process. However, new or reusable orbital manned and in-flight maintainable unmanned space systems demand special emphasis on maintainability, and this document has been prepared to meet that need. Maintainability requirements on many NASA programs differ in phasing and task emphasis from requirements promulgated by other Government agencies. This difference is due to the research and development nature of NASA programs where quantities produced are generally small; therefore, the depth of logistics support typical of many programs is generally not warranted. The cost of excessive maintenance is very high due to the logistics problems associated with the space environment. The ability to provide timely maintenance often involves safety considerations for manned space flight applications. This document represents a basic set of requirements that will achieve a design for maintenance. These requirements are directed primarily at manned and unmanned orbital space systems. To be effective, maintainability requirements should be tailored to meet specific NASA program and project needs and constraints. NASA activities shall invoke the requirements of this document consistent with program planning in procurements or on inhouse development efforts.

Crewed Space Vehicle Battery Safety Requirements Revision D

NASA Technical Reports Server (NTRS)

Russell, Samuel

2017-01-01

The Crewed Space Vehicle Battery Safety Requirements document has been prepared for use by designers of battery-powered vehicles, portable equipment, and experiments intended for crewed spaceflight. The purpose of the requirements document is to provide battery designers with information on design provisions to be incorporated in and around the battery and on the verification to be undertaken to demonstrate a safe battery is provided. The term "safe battery" means that the battery is safe for ground personnel and crew members to handle and use; safe to be used in the enclosed environment of a crewed space vehicle; and safe to be mounted or used in unpressurized spaces adjacent to habitable areas. Battery design review, approval, and certification is required before the batteries can be used for ground operations and be certified for flight.

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.

Deep Borehole Field Test Requirements and Controlled Assumptions.

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

Hardin, Ernest

2015-07-01

This document presents design requirements and controlled assumptions intended for use in the engineering development and testing of: 1) prototype packages for radioactive waste disposal in deep boreholes; 2) a waste package surface handling system; and 3) a subsurface system for emplacing and retrieving packages in deep boreholes. Engineering development and testing is being performed as part of the Deep Borehole Field Test (DBFT; SNL 2014a). This document presents parallel sets of requirements for a waste disposal system and for the DBFT, showing the close relationship. In addition to design, it will also inform planning for drilling, construction, and scientificmore » characterization activities for the DBFT. The information presented here follows typical preparations for engineering design. It includes functional and operating requirements for handling and emplacement/retrieval equipment, waste package design and emplacement requirements, borehole construction requirements, sealing requirements, and performance criteria. Assumptions are included where they could impact engineering design. Design solutions are avoided in the requirements discussion. Deep Borehole Field Test Requirements and Controlled Assumptions July 21, 2015 iv ACKNOWLEDGEMENTS This set of requirements and assumptions has benefited greatly from reviews by Gordon Appel, Geoff Freeze, Kris Kuhlman, Bob MacKinnon, Steve Pye, David Sassani, Dave Sevougian, and Jiann Su.« less

Conceptual design of a monitoring system for the Charters of Freedom

NASA Technical Reports Server (NTRS)

Cutts, J. A.

1984-01-01

A conceptual design of a monitoring system for the Charters of Freedom was developed for the National Archives and Records Service. The monitoring system would be installed at the National Archives and used to document the condition of the Charters as part of a regular inspection program. The results of an experimental measurements program that led to the definition of analysis system requirements are presented, a conceptual design of the monitoring system is described and the alternative approaches to implementing this design were discussed. The monitoring system is required to optically detect and measure deterioration in documents that are permanently encapsulated in glass cases. An electronic imaging system with the capability for precise photometric measurements of the contrast of the script on the documents can perform this task. Two general types of imaging systems are considered (line and area array), and their suitability for performing these required measurements are compared. A digital processing capability for analyzing the electronic imaging data is also required, and several optional levels of complexity for this digital analysis system are evaluated.

TOPEX Software Document Series. Volume 5; Rev. 1; TOPEX GDR Processing

NASA Technical Reports Server (NTRS)

Lee, Jeffrey; Lockwood, Dennis; Hancock, David W., III

2003-01-01

This document is a compendium of the WFF TOPEX Software Development Team's knowledge regarding Geophysical Data Record (GDR) Processing. It includes many elements of a requirements document, a software specification document, a software design document, and a user's manual. In the more technical sections, this document assumes the reader is familiar with TOPEX and instrument files.

Development of Innovative Design Processor

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

Park, Y.S.; Park, C.O.

2004-07-01

The nuclear design analysis requires time-consuming and erroneous model-input preparation, code run, output analysis and quality assurance process. To reduce human effort and improve design quality and productivity, Innovative Design Processor (IDP) is being developed. Two basic principles of IDP are the document-oriented design and the web-based design. The document-oriented design is that, if the designer writes a design document called active document and feeds it to a special program, the final document with complete analysis, table and plots is made automatically. The active documents can be written with ordinary HTML editors or created automatically on the web, which ismore » another framework of IDP. Using the proper mix-up of server side and client side programming under the LAMP (Linux/Apache/MySQL/PHP) environment, the design process on the web is modeled as a design wizard style so that even a novice designer makes the design document easily. This automation using the IDP is now being implemented for all the reload design of Korea Standard Nuclear Power Plant (KSNP) type PWRs. The introduction of this process will allow large reduction in all reload design efforts of KSNP and provide a platform for design and R and D tasks of KNFC. (authors)« less

Loads and Structural Dynamics Requirements for Spaceflight Hardware

NASA Technical Reports Server (NTRS)

Schultz, Kenneth P.

2011-01-01

The purpose of this document is to establish requirements relating to the loads and structural dynamics technical discipline for NASA and commercial spaceflight launch vehicle and spacecraft hardware. Requirements are defined for the development of structural design loads and recommendations regarding methodologies and practices for the conduct of load analyses are provided. As such, this document represents an implementation of NASA STD-5002. Requirements are also defined for structural mathematical model development and verification to ensure sufficient accuracy of predicted responses. Finally, requirements for model/data delivery and exchange are specified to facilitate interactions between Launch Vehicle Providers (LVPs), Spacecraft Providers (SCPs), and the NASA Technical Authority (TA) providing insight/oversight and serving in the Independent Verification and Validation role. In addition to the analysis-related requirements described above, a set of requirements are established concerning coupling phenomena or other interaction between structural dynamics and aerodynamic environments or control or propulsion system elements. Such requirements may reasonably be considered structure or control system design criteria, since good engineering practice dictates consideration of and/or elimination of the identified conditions in the development of those subsystems. The requirements are included here, however, to ensure that such considerations are captured in the design space for launch vehicles (LV), spacecraft (SC) and the Launch Abort Vehicle (LAV). The requirements in this document are focused on analyses to be performed to develop data needed to support structural verification. As described in JSC 65828, Structural Design Requirements and Factors of Safety for Spaceflight Hardware, implementation of the structural verification requirements is expected to be described in a Structural Verification Plan (SVP), which should describe the verification of each structural item for the applicable requirements. The requirement for and expected contents of the SVP are defined in JSC 65828. The SVP may also document unique verifications that meet or exceed these requirements with Technical Authority approval.

TOPEX SDR Processing, October 1998. Volume 4

NASA Technical Reports Server (NTRS)

Lee, Jeffrey E.; Lockwood, Dennis W.

2003-01-01

This document is a compendium of the WFF TOPEX Software Development Team's knowledge regarding Sensor Data Record (SDR) Processing. It includes many elements of a requirements document, a software specification document, a software design document, and a user's manual. In the more technical sections, this document assumes the reader is familiar with TOPEX and instrument files.

Concept document of the repository-based software engineering program: A constructive appraisal

NASA Technical Reports Server (NTRS)

1992-01-01

A constructive appraisal of the Concept Document of the Repository-Based Software Engineering Program is provided. The Concept Document is designed to provide an overview of the Repository-Based Software Engineering (RBSE) Program. The Document should be brief and provide the context for reading subsequent requirements and product specifications. That is, all requirements to be developed should be traceable to the Concept Document. Applied Expertise's analysis of the Document was directed toward assuring that: (1) the Executive Summary provides a clear, concise, and comprehensive overview of the Concept (rewrite as necessary); (2) the sections of the Document make best use of the NASA 'Data Item Description' for concept documents; (3) the information contained in the Document provides a foundation for subsequent requirements; and (4) the document adequately: identifies the problem being addressed; articulates RBSE's specific role; specifies the unique aspects of the program; and identifies the nature and extent of the program's users.

Army-NASA aircrew/aircraft integration program. Phase 5: A3I Man-Machine Integration Design and Analysis System (MIDAS) software concept document

NASA Technical Reports Server (NTRS)

Banda, Carolyn; Bushnell, David; Chen, Scott; Chiu, Alex; Neukom, Christian; Nishimura, Sayuri; Prevost, Michael; Shankar, Renuka; Staveland, Lowell; Smith, Greg

1992-01-01

This is the Software Concept Document for the Man-machine Integration Design and Analysis System (MIDAS) being developed as part of Phase V of the Army-NASA Aircrew/Aircraft Integration (A3I) Progam. The approach taken in this program since its inception in 1984 is that of incremental development with clearly defined phases. Phase 1 began in 1984 and subsequent phases have progressed at approximately 10-16 month intervals. Each phase of development consists of planning, setting requirements, preliminary design, detailed design, implementation, testing, demonstration and documentation. Phase 5 began with an off-site planning meeting in November, 1990. It is expected that Phase 5 development will be complete and ready for demonstration to invited visitors from industry, government and academia in May, 1992. This document, produced during the preliminary design period of Phase 5, is intended to record the top level design concept for MIDAS as it is currently conceived. This document has two main objectives: (1) to inform interested readers of the goals of the MIDAS Phase 5 development period, and (2) to serve as the initial version of the MIDAS design document which will be continuously updated as the design evolves. Since this document is written fairly early in the design period, many design issues still remain unresolved. Some of the unresolved issues are mentioned later in this document in the sections on specific components. Readers are cautioned that this is not a final design document and that, as the design of MIDAS matures, some of the design ideas recorded in this document will change. The final design will be documented in a detailed design document published after the demonstrations.

Controls Over Ministry of Interior Fuel Contracts Could be Improved

DTIC Science & Technology

2016-01-20

Fiscal Year 1395 Commitment Letter improved reporting requirements designed to specify adequate documentation of the Afghan Ministry of Interior fuel...1395 Commitment Letter improved reporting requirements designed to specify adequate documentation of the Afghan Ministry of Interior fuel consumption...of Defense F r a u d , W a s t e & A b u s e FOR OFFICIAL USE ONLY FOR OFFICIAL USE ONLY Results in Brief Controls Over Ministry of Interior Fuel

STV engine design considerations

NASA Technical Reports Server (NTRS)

1991-01-01

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

An electronic regulatory document management system for a clinical trial network.

PubMed

Zhao, Wenle; Durkalski, Valerie; Pauls, Keith; Dillon, Catherine; Kim, Jaemyung; Kolk, Deneil; Silbergleit, Robert; Stevenson, Valerie; Palesch, Yuko

2010-01-01

A computerized regulatory document management system has been developed as a module in a comprehensive Clinical Trial Management System (CTMS) designed for an NIH-funded clinical trial network in order to more efficiently manage and track regulatory compliance. Within the network, several institutions and investigators are involved in multiple trials, and each trial has regulatory document requirements. Some of these documents are trial specific while others apply across multiple trials. The latter causes a possible redundancy in document collection and management. To address these and other related challenges, a central regulatory document management system was designed. This manuscript shares the design of the system as well as examples of it use in current studies. Copyright (c) 2009 Elsevier Inc. All rights reserved.

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

Arndt, T.E., Fluor Daniel Hanford

A previous evaluation documented in report WHC-SD-GN-RPT-30005, Rev. 0, titled ``Evaluation on Self-Contained High Efficiency Particulate Filters,`` revealed that the SCHEPA filters do not have required documentation to be in compliance with the design, testing, and fabrication standards required in ASME N-509, ASME N-510, and MIL-F-51068. These standards are required by DOE Order 6430.IA. Without this documentation, filter adequacy cannot be verified. The existing SCHEPA filters can be removed and replaced with new filters and filter housing which meet current codes and standards.

WFF TOPEX Software Documentation Altimeter Instrument File (AIF) Processing, October 1998. Volume 3

NASA Technical Reports Server (NTRS)

Lee, Jeffrey; Lockwood, Dennis

2003-01-01

This document is a compendium of the WFF TOPEX Software Development Team's knowledge regarding Sensor Data Record (SDR) Processing. It includes many elements of a requirements document, a software specification document, a software design document, and a user's manual. In the more technical sections, this document assumes the reader is familiar with TOPEX and instrument files.

49 CFR 551.63 - May a foreign manufacturer submit a designation by email or facsimile?

Code of Federal Regulations, 2010 CFR

2010-10-01

... email or facsimile? 551.63 Section 551.63 Transportation Other Regulations Relating to Transportation... foreign manufacturer submit a designation by email or facsimile? No, the statute requires designation... designation documents submitted via email or facsimile, as they do not satisfy this requirement. ...

NASA Manned Launch Vehicle Lightning Protection Development

NASA Technical Reports Server (NTRS)

McCollum, Matthew B.; Jones, Steven R.; Mack, Jonathan D.

2009-01-01

Historically, the National Aeronautics and Space Administration (NASA) relied heavily on lightning avoidance to protect launch vehicles and crew from lightning effects. As NASA transitions from the Space Shuttle to the new Constellation family of launch vehicles and spacecraft, NASA engineers are imposing design and construction standards on the spacecraft and launch vehicles to withstand both the direct and indirect effects of lightning. A review of current Space Shuttle lightning constraints and protection methodology will be presented, as well as a historical review of Space Shuttle lightning requirements and design. The Space Shuttle lightning requirements document, NSTS 07636, Lightning Protection, Test and Analysis Requirements, (originally published as document number JSC 07636, Lightning Protection Criteria Document) was developed in response to the Apollo 12 lightning event and other experiences with NASA and the Department of Defense launch vehicles. This document defined the lightning environment, vehicle protection requirements, and design guidelines for meeting the requirements. The criteria developed in JSC 07636 were a precursor to the Society of Automotive Engineers (SAE) lightning standards. These SAE standards, along with Radio Technical Commission for Aeronautics (RTCA) DO-160, Environmental Conditions and Test Procedures for Airborne Equipment, are the basis for the current Constellation lightning design requirements. The development and derivation of these requirements will be presented. As budget and schedule constraints hampered lightning protection design and verification efforts, the Space Shuttle elements waived the design requirements and relied on lightning avoidance in the form of launch commit criteria (LCC) constraints and a catenary wire system for lightning protection at the launch pads. A better understanding of the lightning environment has highlighted the vulnerability of the protection schemes and associated risk to the vehicle, which has resulted in lost launch opportunities and increased expenditures in manpower to assess Space Shuttle vehicle health and safety after lightning events at the launch pad. Because of high-percentage launch availability and long-term on-pad requirements, LCC constraints are no longer considered feasible. The Constellation vehicles must be designed to withstand direct and indirect effects of lightning. A review of the vehicle design and potential concerns will be presented as well as the new catenary lightning protection system for the launch pad. This system is required to protect the Constellation vehicles during launch processing when vehicle lightning effects protection might be compromised by such items as umbilical connections and open access hatches.

24 CFR 972.206 - Required initial assessments.

Code of Federal Regulations, 2011 CFR

2011-04-01

... designated for occupancy by the elderly and/or persons with disabilities (i.e., is not a general occupancy... the necessary conditions for voluntary conversion described § 972.224. (c) Documentation. A PHA must maintain documentation of the reasoning with respect to each required initial assessment. (d) Timing of...

24 CFR 972.206 - Required initial assessments.

Code of Federal Regulations, 2010 CFR

2010-04-01

... designated for occupancy by the elderly and/or persons with disabilities (i.e., is not a general occupancy... the necessary conditions for voluntary conversion described § 972.224. (c) Documentation. A PHA must maintain documentation of the reasoning with respect to each required initial assessment. (d) Timing of...

Human machine interface display design document.

DOT National Transportation Integrated Search

2008-01-01

The purpose of this document is to describe the design for the human machine interface : (HMI) display for the Next Generation 9-1-1 (NG9-1-1) System (or system of systems) : based on the initial Tier 1 requirements identified for the NG9-1-1 S...

NASA Docking System (NDS) Users Guide: International Space Station Program. Type 4

NASA Technical Reports Server (NTRS)

Tabakman, Alexander

2010-01-01

The NASA Docking System (NDS) Users Guide provides an overview of the basic information needed to integrate the NDS onto a Host Vehicle (HV). This Users Guide is intended to provide a vehicle developer with a fundamental understanding of the NDS technical and operations information to support their program and engineering integration planning. The Users Guide identifies the NDS Specification, Interface Definition or Requirement Documents that contain the complete technical details and requirements that a vehicle developer must use to design, develop and verify their systems will interface with NDS. This Guide is an initial reference and must not be used as a design document. In the event of conflict between this Users Guide and other applicable interface definition or requirements documents; the applicable document will take precedence. This Users Guide is organized in three main sections. Chapter 1 provides an overview of the NDS and CDA hardware and the operations concepts for the NDS. Chapter 2 provides information for Host Vehicle Program integration with the NDS Project Office. Chapter 2 describes the NDS Project organization, integration and verification processes, user responsibilities, and specification and interface requirement documents. Chapter 3 provides a summary of basic technical information for the NDS design. Chapter 3 includes NDS hardware component descriptions, physical size and weight characteristics, and summary of the capabilities and constraints for the various NDS sub-systems.

International Low Impact Docking System (iLIDS) Project Technical Requirements Specification, Revision F

NASA Technical Reports Server (NTRS)

Lewis, James L.

2011-01-01

The NASA Docking System (NDS) is NASA's implementation for the emerging International Docking System Standard (IDSS) using low impact docking technology. The NASA Docking System Project (NDSP) is the International Space Station (ISS) Program's project to produce the NDS, Common Docking Adapter (CDA) and Docking Hub. The NDS design evolved from the Low Impact Docking System (LIDS). The acronym international Low Impact Docking System (iLIDS) is also used to describe this system as well as the Government Furnished Equipment (GFE) project designing the NDS for the NDSP. NDS and iLIDS may be used interchangeability. This document will use the acronym iLIDS. Some of the heritage documentation and implementations (e.g., software command names, requirement identification (ID), figures, etc.) used on NDS will continue to use the LIDS acronym. This specification defines the technical requirements for the iLIDS GFE delivered to the NDSP by the iLIDS project. This document contains requirements for two iLIDS configurations, SEZ29101800-301 and SEZ29101800-302. Requirements with the statement, iLIDS shall, are for all configurations. Examples of requirements that are unique to a single configuration may be identified as iLIDS (-301) shall or iLIDS (-302) shall. Furthermore, to allow a requirement to encompass all configurations with an exception, the requirement may be designated as iLIDS (excluding -302) shall. Verification requirements for the iLIDS project are identified in the Verification Matrix (VM) provided in the iLIDS Verification and Validation Document, JSC-63966. The following definitions differentiate between requirements and other statements: Shall: This is the only verb used for the binding requirements. Should/May: These verbs are used for stating non-mandatory goals. Will: This verb is used for stating facts or declaration of purpose. A Definition of Terms table is provided in Appendix B to define those terms with specific tailored uses in this document.

NASA Construction of Facilities Validation Processes - Total Building Commissioning (TBCx)

NASA Technical Reports Server (NTRS)

Hoover, Jay C.

2004-01-01

Key Atributes include: Total Quality Management (TQM) System that looks at all phases of a project. A team process that spans boundaries. A Commissioning Authority to lead the process. Commissioning requirements in contracts. Independent design review to verify compliance with Facility Project Requirements (FPR). Formal written Commissioning Plan with Documented Results. Functional performance testing (FPT) against the requirements document.

Document Storage and Retrieval in the Electronic Office.

ERIC Educational Resources Information Center

Ashford, John

1985-01-01

Proposals are made for practical approaches to the design of electronic office systems to provide for the effective storage and retrieval of the documents that they generate. Problems of records management and requirements to be met by the designer of an electronic office system are highlighted. Nineteen references are cited. (EJS)

7 CFR 1.645 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2010 CFR

2010-01-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 1.641(c). A...

50 CFR 221.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2014 CFR

2014-10-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 221.41(c). A...

7 CFR 1.645 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2013 CFR

2013-01-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 1.641(c). A...

7 CFR 1.645 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2014 CFR

2014-01-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 1.641(c). A...

7 CFR 1.645 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2012 CFR

2012-01-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 1.641(c). A...

7 CFR 1.645 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2011 CFR

2011-01-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 1.641(c). A...

50 CFR 221.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2012 CFR

2012-10-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 221.41(c). A...

50 CFR 221.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2013 CFR

2013-10-01

... measuring, surveying, photographing, testing, or sampling either the property or any designated object or...? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under § 221.41(c). A...

Safeguards-by-Design: Guidance for Independent Spent Fuel Dry Storage Installations (ISFSI)

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

Trond Bjornard; Philip C. Durst

2012-05-01

This document summarizes the requirements and best practices for implementing international nuclear safeguards at independent spent fuel storage installations (ISFSIs), also known as Away-from- Reactor (AFR) storage facilities. These installations may provide wet or dry storage of spent fuel, although the safeguards guidance herein focuses on dry storage facilities. In principle, the safeguards guidance applies to both wet and dry storage. The reason for focusing on dry independent spent fuel storage installations is that this is one of the fastest growing nuclear installations worldwide. Independent spent fuel storage installations are typically outside of the safeguards nuclear material balance area (MBA)more » of the reactor. They may be located on the reactor site, but are generally considered by the International Atomic Energy Agency (IAEA) and the State Regulator/SSAC to be a separate facility. The need for this guidance is becoming increasingly urgent as more and more nuclear power plants move their spent fuel from resident spent fuel ponds to independent spent fuel storage installations. The safeguards requirements and best practices described herein are also relevant to the design and construction of regional independent spent fuel storage installations that nuclear power plant operators are starting to consider in the absence of a national long-term geological spent fuel repository. The following document has been prepared in support of two of the three foundational pillars for implementing Safeguards-by-Design (SBD). These are: i) defining the relevant safeguards requirements, and ii) defining the best practices for meeting the requirements. This document was prepared with the design of the latest independent dry spent fuel storage installations in mind and was prepared specifically as an aid for designers of commercial nuclear facilities to help them understand the relevant international requirements that follow from a country’s safeguards agreement with the IAEA. If these requirements are understood at the earliest stages of facility design, it will help eliminate the costly retrofit of facilities that has occurred in the past to accommodate nuclear safeguards, and will help the IAEA implement nuclear safeguards worldwide, especially in countries building their first nuclear facilities. It is also hoped that this guidance document will promote discussion between the IAEA, State Regulator/SSAC, Project Design Team, and Facility Owner/Operator at an early stage to ensure that new ISFSIs will be effectively and efficiently safeguarded. This is intended to be a living document, since the international nuclear safeguards requirements may be subject to revision over time. More importantly, the practices by which the requirements are met are continuously modernized by the IAEA and facility operators for greater efficiency and cost effectiveness. As these improvements are made, it is recommended that the subject guidance document be updated and revised accordingly.« less

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

NASA Technical Reports Server (NTRS)

1979-01-01

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

Seismology software: state of the practice

NASA Astrophysics Data System (ADS)

Smith, W. Spencer; Zeng, Zheng; Carette, Jacques

2018-05-01

We analyzed the state of practice for software development in the seismology domain by comparing 30 software packages on four aspects: product, implementation, design, and process. We found room for improvement in most seismology software packages. The principal areas of concern include a lack of adequate requirements and design specification documents, a lack of test data to assess reliability, a lack of examples to get new users started, and a lack of technological tools to assist with managing the development process. To assist going forward, we provide recommendations for a document-driven development process that includes a problem statement, development plan, requirement specification, verification and validation (V&V) plan, design specification, code, V&V report, and a user manual. We also provide advice on tool use, including issue tracking, version control, code documentation, and testing tools.

Seismology software: state of the practice

NASA Astrophysics Data System (ADS)

Smith, W. Spencer; Zeng, Zheng; Carette, Jacques

2018-02-01

We analyzed the state of practice for software development in the seismology domain by comparing 30 software packages on four aspects: product, implementation, design, and process. We found room for improvement in most seismology software packages. The principal areas of concern include a lack of adequate requirements and design specification documents, a lack of test data to assess reliability, a lack of examples to get new users started, and a lack of technological tools to assist with managing the development process. To assist going forward, we provide recommendations for a document-driven development process that includes a problem statement, development plan, requirement specification, verification and validation (V&V) plan, design specification, code, V&V report, and a user manual. We also provide advice on tool use, including issue tracking, version control, code documentation, and testing tools.

7 CFR 25.403. - Ongoing 2-year work plan requirement.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 25.403. Agriculture Office of the Secretary of Agriculture RURAL EMPOWERMENT ZONES AND ENTERPRISE COMMUNITIES Post-Designation Requirements § 25.403. Ongoing 2-year work plan requirement. (a) Each Empowerment... conditional upon the designation of the community as an Empowerment Zone; and (iv) Documentation of...

7 CFR 25.403. - Ongoing 2-year work plan requirement.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 25.403. Agriculture Office of the Secretary of Agriculture RURAL EMPOWERMENT ZONES AND ENTERPRISE COMMUNITIES Post-Designation Requirements § 25.403. Ongoing 2-year work plan requirement. (a) Each Empowerment... conditional upon the designation of the community as an Empowerment Zone; and (iv) Documentation of...

7 CFR 25.403. - Ongoing 2-year work plan requirement.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 25.403. Agriculture Office of the Secretary of Agriculture RURAL EMPOWERMENT ZONES AND ENTERPRISE COMMUNITIES Post-Designation Requirements § 25.403. Ongoing 2-year work plan requirement. (a) Each Empowerment... conditional upon the designation of the community as an Empowerment Zone; and (iv) Documentation of...

7 CFR 25.403. - Ongoing 2-year work plan requirement.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 25.403. Agriculture Office of the Secretary of Agriculture RURAL EMPOWERMENT ZONES AND ENTERPRISE COMMUNITIES Post-Designation Requirements § 25.403. Ongoing 2-year work plan requirement. (a) Each Empowerment... conditional upon the designation of the community as an Empowerment Zone; and (iv) Documentation of...

Development of integrated programs for Aerospace-vehicle Design (IPAD): Product program management systems

NASA Technical Reports Server (NTRS)

Isenberg, J. M.; Southall, J. W.

1979-01-01

The Integrated Programs for Aerospace Vehicle Design (IPAD) is a computing system to support company-wide design information processing. This document presents a brief description of the management system used to direct and control a product-oriented program. This document, together with the reference design process (CR 2981) and the manufacture interactions with the design process (CR 2982), comprises the reference information that forms the basis for specifying IPAD system requirements.

Requirements report for SSTO vertical take-off/horizontal landing vehicle

NASA Technical Reports Server (NTRS)

Greenberg, H. S.

1994-01-01

This document describes the detailed design requirements and design criteria to support Structures/TPS Technology development for SSTO winged vehicle configurations that use vertical take-off and horizontal landing and deliver 25,000 lb payloads to a 220 nm circular orbit at an inclination of 51.6 degrees or 40,000 lb payloads to a 150 nm circular orbit at a 28.5 degree of inclination. This document will be updated on a timely basis as informatIon becomes available throughout the project.

Requirements report for SSTO vertical take-off/horizontal landing vehicle

NASA Astrophysics Data System (ADS)

Greenberg, H. S.

1994-07-01

This document describes the detailed design requirements and design criteria to support Structures/TPS Technology development for SSTO winged vehicle configurations that use vertical take-off and horizontal landing and deliver 25,000 lb payloads to a 220 nm circular orbit at an inclination of 51.6 degrees or 40,000 lb payloads to a 150 nm circular orbit at a 28.5 degree of inclination. This document will be updated on a timely basis as informatIon becomes available throughout the project.

Supplemental design requirements document, Multifunction Waste Tank Facility, Project W-236A. Revision 1

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

Groth, B.D.

The Multi-Function Waste Tank Facility (MWTF) consists of four, nominal 1 million gallon, underground double-shell tanks, located in the 200-East area, and two tanks of the same capacity in the 200-West area. MWTF will provide environmentally safe storage capacity for wastes generated during remediation/retrieval activities of existing waste storage tanks. This document delineates in detail the information to be used for effective implementation of the Functional Design Criteria requirements.

NOSC Program Managers Handbook. Revision 1

DTIC Science & Technology

1988-02-01

cost. The effects of application of life-cycle cost analysis through the planning and RIDT&E phases of a program, and the " design to cost" concept on...is the plan for assuring the quality of the design , design documentation, and fabricated/assembled hardware and associated computer software. 13.5.3.2...listings and printouts, which document the n. requirements, design , or details of compute : software; explain the capabilities and limitations of the

Guideline for Software Documentation Management.

ERIC Educational Resources Information Center

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

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

NASA software documentation standard software engineering program

NASA Technical Reports Server (NTRS)

1991-01-01

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

How Well Can Existing Software Support Processes Accomplish Sustainment of a Non-Developmental Item-Based Acquisition Strategy

DTIC Science & Technology

2017-04-06

Research Hypothesis ........................................................................................................... 15 Research Design ...user community and of accommodating advancing software applications by the vendors. Research Design My approach to this project was to conduct... design descriptions , requirements specifications, test documentation, interface requirement specifications, product specifications, and software

GEOSAT Follow-On (GFO) Altimeter Document Series. Volume 5; Version 1; GFO Radar Altimeter Processing at Wallops Flight Facility

NASA Technical Reports Server (NTRS)

Lockwood, Dennis W.; Conger, A. M.

2003-01-01

This document is a compendium of the WFF GFO Software Development Team's knowledge regarding of GDO CAL/VAL Data. It includes many elements of a requirements document, a software specification document, a software design document, and a user's guide. In the more technical sections, this document assumes the reader is familiar with GFO and its CAL/VAL Data.

Space station system analysis study. Part 3: Documentation. Volume 2: Technical report. [structural design and construction

NASA Technical Reports Server (NTRS)

1977-01-01

An analysis of construction operation is presented as well as power system sizing requirements. Mission hardware requirements are reviewed in detail. Space construction base and design configurations are also examined.

Advanced Marketing/Coop Course Outline.

ERIC Educational Resources Information Center

Dixon, Bobby

This document contains the information required to present a 1-year school course that is the capstone class of a 2-year marketing major and is designed for high school students wishing to develop the skills required for entry into the marketing industry. The document begins with a rationale, brief course description, list of course objectives,…

42 CFR 137.365 - What is the procedure for the Secretary's review and approval of project planning and design...

Code of Federal Regulations, 2010 CFR

2010-10-01

... SERVICE, DEPARTMENT OF HEALTH AND HUMAN SERVICES TRIBAL SELF-GOVERNANCE Construction Roles of the...-Governance Tribe? (a) The Secretary shall review and approve planning documents to ensure compliance with... design documents for general compliance with requirements of the construction project agreement. (b) The...

Alternative Compliance: Guidelines for Preparing and Submitting a Waiver Request Application and Other Documentation Requirements

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

Not Available

2013-03-01

This document is designed to assist covered fleets interested in taking advantage of more flexible compliance options and to facilitate the transition from Standard Compliance to Alternative Compliance. It is designed to help fleets better understand the Alternative Compliance option and successfully complete the waiver application process.

Alternative Compliance: Guidelines for Preparing and Submitting a Waiver Request Application and Other Documentation Requirements (Brochure)

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

Not Available

2014-06-01

This document is designed to assist covered fleets interested in taking advantage of more flexible compliance options and to facilitate the transition from Standard Compliance to Alternative Compliance. It is designed to help fleets better understand the Alternative Compliance option and successfully complete the waiver application process.

Alternative Compliance: Guidelines for Preparing and Submitting a Waiver Request Application and Other Documentation Requirements

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

Sears, Ted

2014-06-01

This document is designed to assist covered fleets interested in taking advantage of more flexible compliance options and to facilitate the transition from Standard Compliance to Alternative Compliance. It is designed to help fleets better understand the Alternative Compliance option and successfully complete the waiver application process.

Alternative Compliance: Guidelines for Preparing and Submitting a Waiver Request Application and Other Documentation Requirements (Book)

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

Not Available

2010-11-01

This document is designed to assist covered fleets interested in taking advantage of more flexible compliance options and to facilitate the transition from Standard Compliance to Alternative Compliance. It is designed to help fleets better understand the Alternative Compliance option and successfully complete the waiver application process.

Modular Integrated Stackable Layers (MISL) 1.1 Design Specification. Design Guideline Document

NASA Technical Reports Server (NTRS)

Yim, Hester J.

2012-01-01

This document establishes the design guideline of the Modular Instrumentation Data Acquisition (MI-DAQ) system in utilization of several designs available in EV. The MI- DAQ provides the options to the customers depending on their system requirements i.e. a 28V interface power supply, a low power battery operated system, a low power microcontroller, a higher performance microcontroller, a USB interface, a Ethernet interface, a wireless communication, various sensor interfaces, etc. Depending on customer's requirements, the each functional board can be stacked up from a bottom level of power supply to a higher level of stack to provide user interfaces. The stack up of boards are accomplished by a predefined and standardized power bus and data bus connections which are included in this document along with other physical and electrical guidelines. This guideline also provides information for a new design options. This specification is the product of a collaboration between NASA/JSC/EV and Texas A&M University. The goal of the collaboration is to open source the specification and allow outside entities to design, build, and market modules that are compatible with the specification. NASA has designed and is using numerous modules that are compatible to this specification. A limited number of these modules will also be released as open source designs to support the collaboration. The released designs are listed in the Applicable Documents.

Baseline Design Compliance Matrix for the Rotary Mode Core Sampling System

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

LECHELT, J.A.

2000-10-17

The purpose of the design compliance matrix (DCM) is to provide a single-source document of all design requirements associated with the fifteen subsystems that make up the rotary mode core sampling (RMCS) system. It is intended to be the baseline requirement document for the RMCS system and to be used in governing all future design and design verification activities associated with it. This document is the DCM for the RMCS system used on Hanford single-shell radioactive waste storage tanks. This includes the Exhauster System, Rotary Mode Core Sample Trucks, Universal Sampling System, Diesel Generator System, Distribution Trailer, X-Ray Cart System,more » Breathing Air Compressor, Nitrogen Supply Trailer, Casks and Cask Truck, Service Trailer, Core Sampling Riser Equipment, Core Sampling Support Trucks, Foot Clamp, Ramps and Platforms and Purged Camera System. Excluded items are tools such as light plants and light stands. Other items such as the breather inlet filter are covered by a different design baseline. In this case, the inlet breather filter is covered by the Tank Farms Design Compliance Matrix.« less

Towards the formal specification of the requirements and design of a processor interface unit

NASA Technical Reports Server (NTRS)

Fura, David A.; Windley, Phillip J.; Cohen, Gerald C.

1993-01-01

Work to formally specify the requirements and design of a Processor Interface Unit (PIU), a single-chip subsystem providing memory interface, bus interface, and additional support services for a commercial microprocessor within a fault-tolerant computer system, is described. This system, the Fault-Tolerant Embedded Processor (FTEP), is targeted towards applications in avionics and space requiring extremely high levels of mission reliability, extended maintenance free operation, or both. The approaches that were developed for modeling the PIU requirements and for composition of the PIU subcomponents at high levels of abstraction are described. These approaches were used to specify and verify a nontrivial subset of the PIU behavior. The PIU specification in Higher Order Logic (HOL) is documented in a companion NASA contractor report entitled 'Towards the Formal Specification of the Requirements and Design of a Processor Interfacs Unit - HOL Listings.' The subsequent verification approach and HOL listings are documented in NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit' and NASA contractor report entitled 'Towards the Formal Verification of the Requirements and Design of a Processor Interface Unit - HOL Listings.'

Designing Control System Application Software for Change

NASA Technical Reports Server (NTRS)

Boulanger, Richard

2001-01-01

The Unified Modeling Language (UML) was used to design the Environmental Systems Test Stand (ESTS) control system software. The UML was chosen for its ability to facilitate a clear dialog between software designer and customer, from which requirements are discovered and documented in a manner which transposes directly to program objects. Applying the UML to control system software design has resulted in a baseline set of documents from which change and effort of that change can be accurately measured. As the Environmental Systems Test Stand evolves, accurate estimates of the time and effort required to change the control system software will be made. Accurate quantification of the cost of software change can be before implementation, improving schedule and budget accuracy.

Concentrating solar collector subsystem: Preliminary design package

NASA Technical Reports Server (NTRS)

1977-01-01

Preliminary design data are presented for a concentrating solar collector including an attitude controller. Provided are schedules, technical status, all documents required for preliminary design, and other program activities.

Flight Design System-1 System Design Document. Volume 9: Executive logic flow, program design language

NASA Technical Reports Server (NTRS)

1979-01-01

The detailed logic flow for the Flight Design System Executive is presented. The system is designed to provide the hardware/software capability required for operational support of shuttle flight planning.

An Analysis of the Management of RED HORSE (Rapid Engineering Deployable, Heavy Operational Repair Squadron, Engineer) Construction Projects

DTIC Science & Technology

1987-09-01

folder . 4. Reviewing design documents and supervises project if designed by other than RED HORSE. 5. Chairing design conferences. 6. Coordinating design...project folder . Air Force Regulation 93-9 requires the project manager to maintain the following records: A. Approved project programming documents. B...these records are maintained in the project folder . Depending on the current status of the project, the project folder will be available from either the

Initial SVS Integrated Technology Evaluation Flight Test Requirements and Hardware Architecture

NASA Technical Reports Server (NTRS)

Harrison, Stella V.; Kramer, Lynda J.; Bailey, Randall E.; Jones, Denise R.; Young, Steven D.; Harrah, Steven D.; Arthur, Jarvis J.; Parrish, Russell V.

2003-01-01

This document presents the flight test requirements for the Initial Synthetic Vision Systems Integrated Technology Evaluation flight Test to be flown aboard NASA Langley's ARIES aircraft and the final hardware architecture implemented to meet these requirements. Part I of this document contains the hardware, software, simulator, and flight operations requirements for this light test as they were defined in August 2002. The contents of this section are the actual requirements document that was signed for this flight test. Part II of this document contains information pertaining to the hardware architecture that was realized to meet these requirements as presented to and approved by a Critical Design Review Panel prior to installation on the B-757 Airborne Research Integrated Experiments Systems (ARIES) airplane. This information includes a description of the equipment, block diagrams of the architecture, layouts of the workstations, and pictures of the actual installations.

Design of the SGML-based electronic patient record system with the use of object-oriented analysis methods.

PubMed

Kuikka, E; Eerola, A; Porrasmaa, J; Miettinen, A; Komulainen, J

1999-01-01

Since a patient record is typically a document updated by many users, required to be represented in many different layouts, and transferred from place to place, it is a good candidate to be represented structured and coded using the SGML document standard. The use of the SGML requires that the structure of the document is defined in advance by a Document Type Definition (DTD) and the document follows it. This paper represents a method which derives an SGML DTD by starting from the description of the usage of the patient record in medical care and nursing.

40 CFR 53.51 - Demonstration of compliance with design specifications and manufacturing and test requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... compliance with design specifications and manufacturing and test requirements. (a) Overview. (1) Paragraphs... document its post-manufacturing test procedures. As a minimum, each test shall consist of the following... 40 Protection of Environment 5 2011-07-01 2011-07-01 false Demonstration of compliance with design...

40 CFR 53.51 - Demonstration of compliance with design specifications and manufacturing and test requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... compliance with design specifications and manufacturing and test requirements. (a) Overview. (1) Paragraphs... document its post-manufacturing test procedures. As a minimum, each test shall consist of the following... 40 Protection of Environment 6 2014-07-01 2014-07-01 false Demonstration of compliance with design...

40 CFR 53.51 - Demonstration of compliance with design specifications and manufacturing and test requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... compliance with design specifications and manufacturing and test requirements. (a) Overview. (1) Paragraphs... document its post-manufacturing test procedures. As a minimum, each test shall consist of the following... 40 Protection of Environment 6 2013-07-01 2013-07-01 false Demonstration of compliance with design...

40 CFR 53.51 - Demonstration of compliance with design specifications and manufacturing and test requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... compliance with design specifications and manufacturing and test requirements. (a) Overview. (1) Paragraphs... document its post-manufacturing test procedures. As a minimum, each test shall consist of the following... 40 Protection of Environment 6 2012-07-01 2012-07-01 false Demonstration of compliance with design...

Terminologie de Base de la Documentation. (Basic Terminology of Documentation).

ERIC Educational Resources Information Center

Commission des Communautes Europeennes (Luxembourg). Bureau de Terminologie.

This glossary is designed to aid non-specialists whose activities require that they have some familiarity with the terminology of the modern methods of documentation. Definitions have been assembled from various dictionaries, manuals, etc., with particular attention being given to the publications of UNESCO and the International Standards…

W-026, Waste Receiving and Processing Facility data management system validation and verification report

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

Palmer, M.E.

1997-12-05

This V and V Report includes analysis of two revisions of the DMS [data management system] System Requirements Specification (SRS) and the Preliminary System Design Document (PSDD); the source code for the DMS Communication Module (DMSCOM) messages; the source code for selected DMS Screens, and the code for the BWAS Simulator. BDM Federal analysts used a series of matrices to: compare the requirements in the System Requirements Specification (SRS) to the specifications found in the System Design Document (SDD), to ensure the design supports the business functions, compare the discreet parts of the SDD with each other, to ensure thatmore » the design is consistent and cohesive, compare the source code of the DMS Communication Module with the specifications, to ensure that the resultant messages will support the design, compare the source code of selected screens to the specifications to ensure that resultant system screens will support the design, compare the source code of the BWAS simulator with the requirements to interface with DMS messages and data transfers relating to the BWAS operations.« less

Functional requirements document for NASA/MSFC Earth Science and Applications Division: Data and information system (ESAD-DIS). Interoperability, 1992

NASA Technical Reports Server (NTRS)

Stephens, J. Briscoe; Grider, Gary W.

1992-01-01

These Earth Science and Applications Division-Data and Information System (ESAD-DIS) interoperability requirements are designed to quantify the Earth Science and Application Division's hardware and software requirements in terms of communications between personal and visualization workstation, and mainframe computers. The electronic mail requirements and local area network (LAN) requirements are addressed. These interoperability requirements are top-level requirements framed around defining the existing ESAD-DIS interoperability and projecting known near-term requirements for both operational support and for management planning. Detailed requirements will be submitted on a case-by-case basis. This document is also intended as an overview of ESAD-DIs interoperability for new-comers and management not familiar with these activities. It is intended as background documentation to support requests for resources and support requirements.

77 FR 23539 - WTO Dispute Settlement Proceeding Regarding European Communities and Certain Member States...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-04-19

... Organization (``WTO Agreement''). That request may be found at www.wto.org contained in a document designated....wto.org contained in a document designated as WT/DS316/23. Public Comment: Requirements for... available on the Web site of the World Trade Organization, www.wto.org . Comments open to public inspection...

What is the Final Verification of Engineering Requirements?

NASA Technical Reports Server (NTRS)

Poole, Eric

2010-01-01

This slide presentation reviews the process of development through the final verification of engineering requirements. The definition of the requirements is driven by basic needs, and should be reviewed by both the supplier and the customer. All involved need to agree upon a formal requirements including changes to the original requirements document. After the requirements have ben developed, the engineering team begins to design the system. The final design is reviewed by other organizations. The final operational system must satisfy the original requirements, though many verifications should be performed during the process. The verification methods that are used are test, inspection, analysis and demonstration. The plan for verification should be created once the system requirements are documented. The plan should include assurances that every requirement is formally verified, that the methods and the responsible organizations are specified, and that the plan is reviewed by all parties. The options of having the engineering team involved in all phases of the development as opposed to having some other organization continue the process once the design has been complete is discussed.

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

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

NONE

This report supplements the final safety evaluation report (FSER) for the System 80+ standard design. The FSER was issued by the US Nuclear Regulatory Commission (NRC) staff as NUREG-1462 in August 1994 to document the NRC staff`s review of the System 80+ design. The System 80+ design was submitted by Asea Brown Boveri-Combustion Engineering (ABB-CE), in accordance with the procedures of Subpart B to Part 52 of Title 10 of the Code of Federal Regulations. This supplement documents the NRC staff`s review of the changes to the System 80+ design documentation since the issuance of the FSER. ABB-CE made thesemore » changes as a result of its review of the System 80+ design details. The NRC staff concludes that the changes to the System 80+ design documentation are acceptable, and that ABB-CE`s application for design certification meets the requirements of Subpart B to 10 CFR Part 52 that are applicable and technically relevant to the System 80+ design.« less

75 FR 52543 - Notice of Proposed Information Collection for Public Comment; Requirements for Designating...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-26

... designation before they designate projects for elderly families only, non-elderly disabled families only, or elderly and disabled families. In this plan, PHAs must document why the designation is needed, information...

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.

SNL Mechanical Computer Aided Design (MCAD) guide 2007.

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

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

2007-12-01

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

Space Telecommunications Radio System (STRS) Application Repository Design and Analysis

NASA Technical Reports Server (NTRS)

Handler, Louis M.

2013-01-01

The Space Telecommunications Radio System (STRS) Application Repository Design and Analysis document describes the STRS application repository for software-defined radio (SDR) applications intended to be compliant to the STRS Architecture Standard. The document provides information about the submission of artifacts to the STRS application repository, to provide information to the potential users of that information, and for the systems engineer to understand the requirements, concepts, and approach to the STRS application repository. The STRS application repository is intended to capture knowledge, documents, and other artifacts for each waveform application or other application outside of its project so that when the project ends, the knowledge is retained. The document describes the transmission of technology from mission to mission capturing lessons learned that are used for continuous improvement across projects and supporting NASA Procedural Requirements (NPRs) for performing software engineering projects and NASAs release process.

43 CFR 45.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2014 CFR

2014-10-01

... things or entry on land? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under... for inspection and measuring, surveying, photographing, testing, or sampling either the property or...

43 CFR 45.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2012 CFR

2012-10-01

... things or entry on land? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under... for inspection and measuring, surveying, photographing, testing, or sampling either the property or...

43 CFR 45.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2013 CFR

2013-10-01

... things or entry on land? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under... for inspection and measuring, surveying, photographing, testing, or sampling either the property or...

43 CFR 45.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2010 CFR

2010-10-01

... things or entry on land? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under... for inspection and measuring, surveying, photographing, testing, or sampling either the property or...

43 CFR 45.45 - What are the requirements for requests for documents or tangible things or entry on land?

Code of Federal Regulations, 2011 CFR

2011-10-01

... things or entry on land? (a) Motion. Except upon agreement of the parties, a party wishing to request the production of designated documents or tangible things or entry on designated land must file a motion under... for inspection and measuring, surveying, photographing, testing, or sampling either the property or...

Think before You Shoot: The Relationship between Cognition and Marksmanship

DTIC Science & Technology

2011-09-01

be expedited if placed through the librarian or other person designated to request documents from DTIC. Change of address Organizations...position, policy, or decision, unless so designated by other official documentation. Citation of trade names in this report does not constitute an...cognitive impairments may require additional marksmanship training and re-learning prior to reintegration. cognition, marksmanship UNCLAS UNCLAS UNCLAS SAR

Human Integration Design Processes (HIDP)

NASA Technical Reports Server (NTRS)

Boyer, Jennifer

2014-01-01

The purpose of the Human Integration Design Processes (HIDP) document is to provide human-systems integration design processes, including methodologies and best practices that NASA has used to meet human systems and human rating requirements for developing crewed spacecraft. HIDP content is framed around human-centered design methodologies and processes in support of human-system integration requirements and human rating. NASA-STD-3001, Space Flight Human-System Standard, is a two-volume set of National Aeronautics and Space Administration (NASA) Agency-level standards established by the Office of the Chief Health and Medical Officer, directed at minimizing health and performance risks for flight crews in human space flight programs. Volume 1 of NASA-STD-3001, Crew Health, sets standards for fitness for duty, space flight permissible exposure limits, permissible outcome limits, levels of medical care, medical diagnosis, intervention, treatment and care, and countermeasures. Volume 2 of NASASTD- 3001, Human Factors, Habitability, and Environmental Health, focuses on human physical and cognitive capabilities and limitations and defines standards for spacecraft (including orbiters, habitats, and suits), internal environments, facilities, payloads, and related equipment, hardware, and software with which the crew interfaces during space operations. The NASA Procedural Requirements (NPR) 8705.2B, Human-Rating Requirements for Space Systems, specifies the Agency's human-rating processes, procedures, and requirements. The HIDP was written to share NASA's knowledge of processes directed toward achieving human certification of a spacecraft through implementation of human-systems integration requirements. Although the HIDP speaks directly to implementation of NASA-STD-3001 and NPR 8705.2B requirements, the human-centered design, evaluation, and design processes described in this document can be applied to any set of human-systems requirements and are independent of reference missions. The HIDP is a reference document that is intended to be used during the development of crewed space systems and operations to guide human-systems development process activities.

Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study. Volume 3: Interface control documents. Part 2: AMPS payload to spacelab ICD

NASA Technical Reports Server (NTRS)

1976-01-01

The AMPS to Spacelab Interface Control Document which is to be used as a guide for format and information content in generating specific AMPS Mission ICDs is presented. This document is meant to supplement the Spacelab Payload Accommodations Handbook in that it only defines interfaces which are not discussed in the handbook to the level required for design purposes. The AMPS Top Level Requirements Tree, illustrates this ICD by a shaded area and its relationship to the other AMPS technical documents. Other interface documents shown are the Level II, AMPS to Space Shuttle Vehicle ICD and the Level III, AMPS to Instruments ICD.

Shuttle unified navigation filter, revision 1

NASA Technical Reports Server (NTRS)

Muller, E. S., Jr.

1973-01-01

Equations designed to meet the navigation requirements of the separate shuttle mission phases are presented in a series of reports entitled, Space Shuttle GN and C Equation Document. The development of these equations is based on performance studies carried out for each particular mission phase. Although navigation equations have been documented separately for each mission phase, a single unified navigation filter design is embodied in these separate designs. The purpose of this document is to present the shuttle navigation equations in a form in which they would most likely be coded-as the single unified navigation filter used in each mission phase. This document will then serve as a single general reference for the navigation equations replacing each of the individual mission phase navigation documents (which may still be used as a description of a particular navigation phase).

Analysis of Data in Accordance with Space Flight Mission Environmental Requirements

NASA Technical Reports Server (NTRS)

Shei, Monica

2011-01-01

The Environmental Assurance Program sets forth standards to ensure that all flight hardware is compatible with the environments that will be encountered during a spacecraft mission. It outlines the design, test and analysis, and risk control standards for the mission and certifies that it will survive in any external or self-induced environments that the spacecraft may experience. The Environmental Requirements Document (ERD) is the most important document in the Environmental Assurance Program, providing the design and test requirements for the project's flight system, subsystems, assemblies, and instruments. This summer's project was to assist Environmental Requirements Engineers (ERE's) in completing the Environmental Assurance Program Summary Report for both the Juno Project and Mars Science Laboratory (MSL) Project. The Summary Report is a document summarizing the environmental tests and analyses of each spacecraft at both the assembly and system level. It compiles a source of all relevant information such as waivers and Problem/Failure Reports (PFRs) into a single report for easy reference of how well the spacecraft met the requirements of the project.

Software archeology: a case study in software quality assurance and design

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

Macdonald, John M; Lloyd, Jane A; Turner, Cameron J

2009-01-01

Ideally, quality is designed into software, just as quality is designed into hardware. However, when dealing with legacy systems, demonstrating that the software meets required quality standards may be difficult to achieve. As the need to demonstrate the quality of existing software was recognized at Los Alamos National Laboratory (LANL), an effort was initiated to uncover and demonstrate that legacy software met the required quality standards. This effort led to the development of a reverse engineering approach referred to as software archaeology. This paper documents the software archaeology approaches used at LANL to document legacy software systems. A case studymore » for the Robotic Integrated Packaging System (RIPS) software is included.« less

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.

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.

Assessing Leader Development: Lessons from a Historical Review of MBA Outcomes

ERIC Educational Resources Information Center

Passarelli, Angela M.; Boyatzis, Richard E.; Wei, Hongguo

2018-01-01

Graduate management education seeks to enhance the likelihood that graduates will be effective leaders, managers, or professionals. This requires programs that are designed to enable students to develop the related competencies, and increasing regulatory pressures require programs to document evidence of success. However, both the design of…

Physiology of chimpanzees in orbit. Part 2: Interface document

NASA Technical Reports Server (NTRS)

Firstenberg, A.

1972-01-01

Interface requirements are presented for the design and development of an earth orbiting experiment to be known as POCO, Physiology of Chimpanzees in Orbit. The POCO experiment may be designed to operate within an orbiting space station (provided artificial gravity measures are not employed), a Saturn 4-B workshop, an Apollo command module or service module, a Saturn-1B spacecraft LM adapter, or aboard one of the presently conceived appendages connected by an umbilical to a space station. This document sets forth the experiment definition and requirements and describes the hardware under development to accomplish these objectives.

Assured crew return vehicle man-systems integration standards

NASA Technical Reports Server (NTRS)

1991-01-01

This is Volume 6 of the Man-Systems Integration Standards (MSIS) family of documents, which is contained in several volumes and a relational database. Each volume has a specific purpose, and each has been assembled from the data contained in the relational database. Volume 6 serves as the Assured Crew Return Vehicle project man-systems integration design requirements. The data in this document is a subset of the data found in Volume 1 and defines the requirements which are pertinent to the Assured Crew Return Vehicle as defined in the SPRD. Additional data and guidelines are provided to assist in the design.

NASA-STD-(I)-6016, Standard Materials and Processes Requirements for Spacecraft

NASA Technical Reports Server (NTRS)

Pedley, Michael; Griffin, Dennis

2006-01-01

This document is directed toward Materials and Processes (M&P) used in the design, fabrication, and testing of flight components for all NASA manned, unmanned, robotic, launch vehicle, lander, in-space and surface systems, and spacecraft program/project hardware elements. All flight hardware is covered by the M&P requirements of this document, including vendor designed, off-the-shelf, and vendor furnished items. Materials and processes used in interfacing ground support equipment (GSE); test equipment; hardware processing equipment; hardware packaging; and hardware shipment shall be controlled to prevent damage to or contamination of flight hardware.

ANOPP programming and documentation standards document

NASA Technical Reports Server (NTRS)

1976-01-01

Standards defining the requirements for preparing software for the Aircraft Noise Prediction Program (ANOPP) were given. It is the intent of these standards to provide definition, design, coding, and documentation criteria for the achievement of a unity among ANOPP products. These standards apply to all of ANOPP's standard software system. The standards encompass philosophy as well as techniques and conventions.

Information System Life-Cycle And Documentation Standards (SMAP DIDS)

NASA Technical Reports Server (NTRS)

1990-01-01

Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

Crew Transportation Technical Management Processes

NASA Technical Reports Server (NTRS)

Mckinnie, John M. (Compiler); Lueders, Kathryn L. (Compiler)

2013-01-01

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document, with its sister documents, International Space Station (ISS) Crew Transportation and Services Requirements Document (CCT-REQ-1130), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), Crew Transportation Operations Standards (CCT STD-1150), and ISS to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase.

Manipulating the Geometric Computer-aided Design of the Operational Requirements-based Casualty Assessment Model within BRL-CAD

DTIC Science & Technology

2018-03-30

ARL-TR-8336 ● MAR 2018 US Army Research Laboratory Manipulating the Geometric Computer-aided Design of the Operational...so designated by other authorized documents. Citation of manufacturer’s or trade names does not constitute an official endorsement or approval of...Army Research Laboratory Manipulating the Geometric Computer-aided Design of the Operational Requirements-based Casualty Assessment Model within

Spacecraft System Integration and Test: SSTI Lewis critical design audit

NASA Technical Reports Server (NTRS)

Brooks, R. P.; Cha, K. K.

1995-01-01

The Critical Design Audit package is the final detailed design package which provides a comprehensive description of the SSTI mission. This package includes the program overview, the system requirements, the science and applications activities, the ground segment development, the assembly, integration and test description, the payload and technology demonstrations, and the spacecraft bus subsystems. Publication and presentation of this document marks the final requirements and design freeze for SSTI.

Airport Surface Traffic Control Visual Ground Aids Engineering and Development Plan

DOT National Transportation Integrated Search

1977-01-01

The plan described in this document supports the overall program at the Transportation Systems Center to define, design, develop, and evaluate systems that meet the requirements of airport surface traffic control. This plan is part of documentation s...

Detailed Design Documentation, without the Pain

NASA Astrophysics Data System (ADS)

Ramsay, C. D.; Parkes, S.

2004-06-01

Producing detailed forms of design documentation, such as pseudocode and structured flowcharts, to describe the procedures of a software system:(1) allows software developers to model and discuss their understanding of a problem and the design of a solution free from the syntax of a programming language,(2) facilitates deeper involvement of non-technical stakeholders, such as the customer or project managers, whose influence ensures the quality, correctness and timeliness of the resulting system,(3) forms comprehensive documentation of the system for its future maintenance, reuse and/or redeployment.However, such forms of documentation require effort to create and maintain.This paper describes a software tool which is currently being developed within the Space Systems Research Group at the University of Dundee which aims to improve the utility of, and the incentive for, creating detailed design documentation for the procedures of a software system. The rationale for creating such a tool is briefly discussed, followed by a description of the tool itself, a summary of its perceived benefits, and plans for future work.

Astrionics system designers handbook, volume 1

NASA Technical Reports Server (NTRS)

1973-01-01

Hardware elements in new and advanced astrionics system designs are discussed. This cost effective approach has as its goal the reduction of R&D and testing costs through the application of proven and tested astrionics components. The ready availability to the designer of data facts for applicable system components is highly desirable. The astrionics System Designers Handbook has as its objective this documenting of data facts to serve the anticipated requirements of the astrionics system designer. Eleven NASA programs were selected as the reference base for the document. These programs are: ATS-F, ERTS-B, HEAO-A, OSO-I, Viking Orbiter, OAO-C, Skylab AM/MDA, Skylab ATM, Apollo 17 CSM, Apollo 17 LM and Mariner Mars 71. Four subsystems were chosen for documentation: communications, data management, electrical power and guidance, navigation and control.

Space Telecommunications Radio System (STRS) Architecture Goals/Objectives and Level 1 Requirements

NASA Technical Reports Server (NTRS)

Briones, Janette C.; Johnson, Sandra K.; VanDerAar, Lisa

2007-01-01

The Space Telecommunications Radio System (STRS) Architecture Requirements Document provides the basis for the development of an open architecture for NASA Software Defined Radios (SDRs) for space use. The main objective of this document is to evaluate the goals and objectives and high level (Level 1) requirements that have bearing on the design of the architecture. The goals and objectives will provide broad, fundamental direction and purpose. The high level requirements (Level 1) intend to guide the broader and longer term aspects aspects of the SDR Architecture and provide guidance for the development of level 2 requirements.

[Focus Notified Bodies. New requirements for designation and monitoring].

PubMed

Poos, U; Edelhäuser, R

2014-12-01

For medical devices with a higher risk, Notified Bodies assess whether the manufacturers and their products fulfill the requirements laid down in the European directives on medical devices. Notified Bodies are designated through a designation procedure by the designating authority, in Germany by ZLG. The requirements for the designation arise from the respective annexes of the directives on medical devices. Since these are only minimal criteria, different documents have been compiled on a European and national level to concretize these minimal criteria regarding the organization, quality management system, resources, and certification procedure. The rules of the ZLG are thereby the essential documents for designation in Germany. Moreover, according to Implementing Regulation (EU) no. 912/2013, the European commission and the other European designating authorities also have to be involved in the designation process. The aim of continuous monitoring of the Notified Bodies with assessments on the bodies' premises as well as with observed audits is to ensure the permanent fulfillment of the requirements. If nonconformities are found in a body's quality management system or in its implementation of the conformity assessment procedures, the body is obliged to provide ZLG with a corrective actions plan. In the case that the nonconformities are not resolved in time or critical nonconformities are found, ZLG may take actions, e.g., restrict the scope of designation, suspend, or - as last resort - withdraw the designation.

Space station MSFC-DPD-235/DR no. MA-05 phase C/D program development plan. Volume 2: Phase C/D, programmatic requirements

NASA Technical Reports Server (NTRS)

1971-01-01

The design plan requirements define the design implementation and control requirements for Phase C/D of the Modular Space Station Project and specifically address the Initial Space Station phase of the Space Station Program (modular). It is based primarily on the specific objective of translating the requirements of the Space Station Program, Project, Interface, and Support Requirements and preliminary contract end x item specifications into detail design of the operational systems which comprise the initial space station. This document is designed to guide aerospace contractors in the planning and bidding for Phase C/D.

Designation of Issues -- World Color Press

EPA Pesticide Factsheets

This document may be of assistance in applying the New Source Review (NSR) air permitting regulations including the Prevention of Significant Deterioration (PSD) requirements. This document is part of the NSR Policy and Guidance Database. Some documents in the database are a scanned or retyped version of a paper photocopy of the original. Although we have taken considerable effort to quality assure the documents, some may contain typographical errors. Contact the office that issued the document if you need a copy of the original.

Army-NASA aircrew/aircraft integration program: Phase 4 A(3)I Man-Machine Integration Design and Analysis System (MIDAS) software detailed design document

NASA Technical Reports Server (NTRS)

Banda, Carolyn; Bushnell, David; Chen, Scott; Chiu, Alex; Constantine, Betsy; Murray, Jerry; Neukom, Christian; Prevost, Michael; Shankar, Renuka; Staveland, Lowell

1991-01-01

The Man-Machine Integration Design and Analysis System (MIDAS) is an integrated suite of software components that constitutes a prototype workstation to aid designers in applying human factors principles to the design of complex human-machine systems. MIDAS is intended to be used at the very early stages of conceptual design to provide an environment wherein designers can use computational representations of the crew station and operator, instead of hardware simulators and man-in-the-loop studies, to discover problems and ask 'what if' questions regarding the projected mission, equipment, and environment. This document is the Software Product Specification for MIDAS. Introductory descriptions of the processing requirements, hardware/software environment, structure, I/O, and control are given in the main body of the document for the overall MIDAS system, with detailed discussion of the individual modules included in Annexes A-J.

Improved Emergency Egress Lighting System for the ISS

NASA Technical Reports Server (NTRS)

Eaton, Leslie L.; Barr, Don A.

2005-01-01

Emergency lights provide illumination in corridors, stairwells, ramps, escalators, aisles, and exit passageways during power failures. Safety and visibility are critical during a power outage. If emergency lights fail to operate properly, the building occupants can become disoriented. Four documents in a collection discuss different topics relating to a proposed improved emergency egress lighting system (EELS) for the International Space Station (ISS). While the present EELS is designed around rows of green-light-emitting diodes, the proposed system contains strips of electroluminescent tape using different colors for each egress path. The proposed EELS can be powered by the same battery currently used by the present EELS, but would require an inverter because electroluminescent devices require AC. Electroluminescent devices also require significantly less current and, depending on the color, would emit 3 to 8 times the light of the present EELS. In addition, they could operate for up to 75 hours (versus .20 minutes for the present system). The first document contains a one-page summary of the proposal and an evaluation of technical merit. The second document summarizes the motivation for, and the design of, the proposed EELS. The third document addresses relevant aspects of the measurement of spectral sensitivity and the psychophysics of perception of light. The fourth document presents additional background information and technical specifications for the electroluminescent tapes.

Computer-Automated Evolution of Spacecraft X-Band Antennas

NASA Technical Reports Server (NTRS)

Lohn, Jason D.; Homby, Gregory S.; Linden, Derek S.

2010-01-01

A document discusses the use of computer- aided evolution in arriving at a design for X-band communication antennas for NASA s three Space Technology 5 (ST5) satellites, which were launched on March 22, 2006. Two evolutionary algorithms, incorporating different representations of the antenna design and different fitness functions, were used to automatically design and optimize an X-band antenna design. A set of antenna designs satisfying initial ST5 mission requirements was evolved by use these algorithms. The two best antennas - one from each evolutionary algorithm - were built. During flight-qualification testing of these antennas, the mission requirements were changed. After minimal changes in the evolutionary algorithms - mostly in the fitness functions - new antenna designs satisfying the changed mission requirements were evolved and within one month of this change, two new antennas were designed and prototypes of the antennas were built and tested. One of these newly evolved antennas was approved for deployment on the ST5 mission, and flight-qualified versions of this design were built and installed on the spacecraft. At the time of writing the document, these antennas were the first computer-evolved hardware in outer space.

Preliminary design data package, appendix C. [hybrid electric vehicles

NASA Technical Reports Server (NTRS)

1979-01-01

The data and documentation required to define the preliminary design of a near term hybrid vehicle and to quantify its operational characteristics are presented together with the assumptions and rationale behind the design decisions. Aspects discussed include development requirements for the propulsion system, the chassis system, the body, and the vehicle systems. Particular emphasis is given to the controls, the heat engine, and the batteries.

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

Consolidated Development Objectives Document (CDOD) For MB-60

NASA Technical Reports Server (NTRS)

Greene, William D.

2013-01-01

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

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.

Export Control Requirements for Tritium Processing Design and R&D

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

Hollis, William Kirk; Maynard, Sarah-Jane Wadsworth

This document will address requirements of export control associated with tritium plant design and processes. Los Alamos National Laboratory has been working in the area of tritium plant system design and research and development (R&D) since the early 1970’s at the Tritium Systems Test Assembly (TSTA). This work has continued to the current date with projects associated with the ITER project and other Office of Science Fusion Energy Science (OS-FES) funded programs. ITER is currently the highest funding area for the DOE OS-FES. Although export control issues have been integrated into these projects in the past a general guidance documentmore » has not been available for reference in this area. To address concerns with currently funded tritium plant programs and assist future projects for FES, this document will identify the key reference documents and specific sections within related to tritium research. Guidance as to the application of these sections will be discussed with specific detail to publications and work with foreign nationals.« less

ETF Mission Statement document. ETF Design Center team

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

Not Available

1980-04-01

The Mission Statement document describes the results, activities, and processes used in preparing the Mission Statement, facility characteristics, and operating goals for the Engineering Test Facility (ETF). Approximately 100 engineers and scientists from throughout the US fusion program spent three days at the Knoxville Mission Workshop defining the requirements that should be met by the ETF during its operating life. Seven groups were selected to consider one major category each of design and operation concerns. Each group prepared the findings of the assigned area as described in the major sections of this document. The results of the operations discussed mustmore » provide the data, knowledge, experience, and confidence to continue to the next steps beyond the ETF in making fusion power a viable energy option. The results from the ETF mission (operations are assumed to start early in the 1990's) are to bridge the gap between the base of magnetic fusion knowledge at the start of operations and that required to design the EPR/DEMO devices.« less

Export Control Requirements for Tritium Processing Design and R&D

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

Hollis, William Kirk; Maynard, Sarah-Jane Wadsworth

2015-10-30

This document will address requirements of export control associated with tritium plant design and processes. Los Alamos National Laboratory has been working in the area of tritium plant system design and research and development (R&D) since the early 1970’s at the Tritium Systems Test Assembly (TSTA). This work has continued to the current date with projects associated with the ITER project and other Office of Science Fusion Energy Science (OS-FES) funded programs. ITER is currently the highest funding area for the DOE OS-FES. Although export control issues have been integrated into these projects in the past a general guidance documentmore » has not been available for reference in this area. To address concerns with currently funded tritium plant programs and assist future projects for FES, this document will identify the key reference documents and specific sections within related to tritium research. Guidance as to the application of these sections will be discussed with specific detail to publications and work with foreign nationals.« less

Adapting Rational Unified Process (RUP) approach in designing a secure e-Tendering model

NASA Astrophysics Data System (ADS)

Mohd, Haslina; Robie, Muhammad Afdhal Muhammad; Baharom, Fauziah; Darus, Norida Muhd; Saip, Mohamed Ali; Yasin, Azman

2016-08-01

e-Tendering is an electronic processing of the tender document via internet and allow tenderer to publish, communicate, access, receive and submit all tender related information and documentation via internet. This study aims to design the e-Tendering system using Rational Unified Process approach. RUP provides a disciplined approach on how to assign tasks and responsibilities within the software development process. RUP has four phases that can assist researchers to adjust the requirements of various projects with different scope, problem and the size of projects. RUP is characterized as a use case driven, architecture centered, iterative and incremental process model. However the scope of this study only focusing on Inception and Elaboration phases as step to develop the model and perform only three of nine workflows (business modeling, requirements, analysis and design). RUP has a strong focus on documents and the activities in the inception and elaboration phases mainly concern the creation of diagrams and writing of textual descriptions. The UML notation and the software program, Star UML are used to support the design of e-Tendering. The e-Tendering design based on the RUP approach can contribute to e-Tendering developers and researchers in e-Tendering domain. In addition, this study also shows that the RUP is one of the best system development methodology that can be used as one of the research methodology in Software Engineering domain related to secured design of any observed application. This methodology has been tested in various studies in certain domains, such as in Simulation-based Decision Support, Security Requirement Engineering, Business Modeling and Secure System Requirement, and so forth. As a conclusion, these studies showed that the RUP one of a good research methodology that can be adapted in any Software Engineering (SE) research domain that required a few artifacts to be generated such as use case modeling, misuse case modeling, activity diagram, and initial class diagram from a list of requirements as identified earlier by the SE researchers

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.

Efficacy Requirements for Antimicrobial Pesticides

EPA Pesticide Factsheets

Pesticides designed to control microbial pests such as viruses and bacteria must have data proving their ability to kill these pests (known as efficacy). The guidance documents on this page describe current efficacy-related requirements.

Design requirements for SRB production control system. Volume 3: Package evaluation, modification and hardware

NASA Technical Reports Server (NTRS)

1981-01-01

The software package evaluation was designed to analyze commercially available, field-proven, production control or manufacturing resource planning management technology and software package. The analysis was conducted by comparing SRB production control software requirements and conceptual system design to software package capabilities. The methodology of evaluation and the findings at each stage of evaluation are described. Topics covered include: vendor listing; request for information (RFI) document; RFI response rate and quality; RFI evaluation process; and capabilities versus requirements.

Guidelines for Selection, Screening and Qualification of Low-Voltage Commercial Multilayer Ceramic Capacitors for Space Programs

NASA Technical Reports Server (NTRS)

Teverovsky, Alexander A.

2012-01-01

This document has been developed in the course of NASA Electronic Parts and Packaging (NEPP) program and is not an official endorsement of the insertion of commercial capacitors in space programs or an established set of requirements for their testing. The purpose of this document is to suggest possible ways for selection, screening, and qualification of commercial capacitors for NASA projects and open discussions in the parts engineering community related to the use of COTS ceramic capacitors. This guideline is applicable to commercial surface mount chip, simple parallel plate design, multi-layer ceramic capacitors (MLCCs) rated to voltages of 100V and less. Parts with different design, e.g. low inductance ceramic capacitors (LICA), land grid array (LGA) etc., might need additional testing and tailoring of the requirements described in this document. Although the focus of this document is on commercial MLCCs, many procedures discussed below would be beneficial for military-grade capacitors

ISS Crew Transportation and Services Requirements Document

NASA Technical Reports Server (NTRS)

Lueders, Kathryn L. (Compiler)

2015-01-01

Under the guidance of processes provided by Crew Transportation Plan (CCT-PLN-1100), this document with its sister documents, Crew Transportation Technical Management Processes (CCT-PLN-1120), Crew Transportation Technical Standards and Design Evaluation Criteria (CCT-STD-1140), and Crew Transportation Operations Standards (CCT-STD-1150), and International Space Station (ISS) to Commercial Orbital Transportation Services Interface Requirements Document (SSP 50808), provides the basis for a National Aeronautics and Space Administration (NASA) certification for services to the ISS for the Commercial Provider. When NASA Crew Transportation System (CTS) certification is achieved for ISS transportation, the Commercial Provider will be eligible to provide services to and from the ISS during the services phase of the NASA Commercial Crew Program (CCP).

Conceptual design of the National Ignition Facility

NASA Astrophysics Data System (ADS)

Paisner, Jeffrey A.; Boyes, John D.; Kumpan, Steven A.; Lowdermilk, W. Howard; Sorem, Michael S.

1995-12-01

The Secretary of the U.S. Department of Energy (DOE) commissioned a conceptual design report (CDR) for the National Ignition Facility (NIF) in January 1993 as part of a key decision zero (KD0), justification of mission need. Motivated by the progress to date by the inertial confinement fusion (ICF) program in meeting the Nova technical contract goals established by the National Academy of Sciences in 1989, the Secretary requested a design using a solid-state laser driver operating at the third harmonic (0.35 micrometer) of neodymium (Nd) glass. The participating ICF laboratories signed a memorandum of agreement in August 1993, and established a project organization, including a technical team from the Lawrence Livermore National Laboratory (LLNL), Los Alamos National Laboratory (LANL), Sandia National Laboratories (SNL), and the Laboratory for Laser Energetics at the University of Rochester. Since then, we completed the NIF conceptual design, based on standard construction at a generic DOE defense program's site, and issued a 7,000-page, 27-volume CDR in May 1994. Over the course of the conceptual design study, several other key documents were generated, including a facilities requirements document, a conceptual design scope and plan, a target physics design document, a laser design cost basis document, a functional requirements document, an experimental plan for indirect drive ignition, and a preliminary hazards analysis (PHA) document. DOE used the PHA to categorize the NIF as a low-hazard, non-nuclear facility. On October 21, 1994 the Secretary of Energy issued a key decision one (KD1) for the NIF, which approved the project and authorized DOE to request Office of Management and Budget-approval for congressional line-item FY 1996 NIF funding for preliminary engineering design and for National Environmental Policy Act activities. In addition, the Secretary declared Livermore as the preferred site for constructing the NIF. In February 1995, the NIF Project was formally submitted to Congress as part of the President's FY 1996 budget. If funded as planned, the Project will cost approximately $1.1 billion and will be completed at the end of FY 2002.

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

NASA Astrophysics Data System (ADS)

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

2012-09-01

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

Final Radiological Assessment of External Exposure for CLEAR-Line Americium Recovery Operations

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

Davis, Adam C.; Belooussova, Olga N.; Hetrick, Lucas Duane

2014-11-12

Los Alamos National Laboratory is currently planning to implement an americium recovery program. The americium, ordinarily isotopically pure 241Am, would be extracted from existing Pu materials, converted to an oxide and shipped to support fabrication of americium oxide-beryllium neutron sources. These operations would occur in the currently proposed Chloride Extraction and Actinide Recovery (CLEAR) line of glove boxes. This glove box line would be collocated with the currently-operational Experimental Chloride Extraction Line (EXCEL). The focus of this document is to provide an in-depth assessment of the currently planned radiation protection measures and to determine whether or not further design workmore » is required to satisfy design-goal and ALARA requirements. Further, this document presents a history of americium recovery operations in the Department of Energy and high-level descriptions of the CLEAR line operations to provide a basis of comparison. Under the working assumptions adopted by this study, it was found that the evaluated design appears to mitigate doses to a level that satisfies the ALARA-in-design requirements of 10 CFR 835 as implemented by the Los Alamos National Laboratory procedure P121. The analyses indicate that extremity doses would also meet design requirements. Dose-rate calculations were performed using the radiation transport code MCNP5 and doses were estimated using a time-motion study developed in consort with the subject matter expert. A copy of this report and all supporting documentation are located on the Radiological Engineering server at Y:\\Rad Engineering\\2013 PROJECTS\\TA-55 Clear Line.« less

A Design Rationale Capture Tool to Support Design Verification and Re-use

NASA Technical Reports Server (NTRS)

Hooey, Becky Lee; Da Silva, Jonny C.; Foyle, David C.

2012-01-01

A design rationale tool (DR tool) was developed to capture design knowledge to support design verification and design knowledge re-use. The design rationale tool captures design drivers and requirements, and documents the design solution including: intent (why it is included in the overall design); features (why it is designed the way it is); information about how the design components support design drivers and requirements; and, design alternatives considered but rejected. For design verification purposes, the tool identifies how specific design requirements were met and instantiated within the final design, and which requirements have not been met. To support design re-use, the tool identifies which design decisions are affected when design drivers and requirements are modified. To validate the design tool, the design knowledge from the Taxiway Navigation and Situation Awareness (T-NASA; Foyle et al., 1996) system was captured and the DR tool was exercised to demonstrate its utility for validation and re-use.

Overview of the Design, Development, and Application of Nickel-hydrogen Batteries

NASA Technical Reports Server (NTRS)

Thaller, Lawrence H.; Zimmerman, Albert H.

2003-01-01

This document provides an overview of the design, development, and application of nickel-hydrogen (Ni-H2) battery technology for aerospace applications. It complements and updates the information presented in NASA RP-1314, NASA Handbook for Nickel- Hydrogen Batteries, published in 1993. Since that time, nickel-hydrogen batteries have become widely accepted for aerospace energy storage requirements and much more has been learned. The intent of this document is to capture some of that additional knowledge. This document addresses various aspects of nickel-hydrogen technology including the electrochemical reactions, cell component design, and selection considerations; overall cell and battery design considerations; charge control considerations; and manufacturing issues that have surfaced over the years that nickel-hydrogen battery technology has been the major energy storage technology for geosynchronous and low-Earth-orbiting satellites.

Space station systems: A bibliography with indexes (supplement 6)

NASA Technical Reports Server (NTRS)

1988-01-01

This bibliography lists 1,133 reports, articles, and other documents introduced into the NASA scientific and technical information system between July 1, 1987 and December 31, 1987. Its purpose is to provide helpful information to the researcher, manager, and designer in technology development and mission design according to system, interactive analysis and design, structural and thermal analysis and design, structural concepts and control systems, electronics, advanced materials, assembly concepts, propulsion, and solar power satellite systems. The coverage includes documents that define major systems and subsystems, servicing and support requirements, procedures and operations, and missions for the current and future Space Station.

Space station systems: A bibliography with indexes (supplement 3)

NASA Technical Reports Server (NTRS)

1987-01-01

This bibliography lists 780 reports, articles and other documents introduced into the NASA scientific and technical information system between January 1, 1986 and June 30, 1986. Its purpose is to provide helpful information to the researcher, manager, and designer in technology development and mission design according to system, interactive analysis and design, structural and thermal analysis and design, structural concepts and control systems, electronics, advanced materials, assembly concepts, propulsion, and solar power satellite system. The coverage includes documents that define major systems and subsystems, servicing and support requirements, procedures and operations, and missions for the current and future space station.

Space station systems: A bibliography with indexes (supplement 2)

NASA Technical Reports Server (NTRS)

1986-01-01

This bibliography lists 904 reports, articles and other documents introduced into the NASA scientific and technical information system between July 1, 1985 and December 31, 1985. Its purpose is to provide helpful information to the researcher, manager, and designer in technology development and mission design according to system, interactive analysis and design, structural and thermal analysis and design, structural concepts and control systems, electronics, advanced materials, assembly concepts, propulsion, and solar power satellite systems. The coverage includes documents that define major systems and subsystems, servicing and support requirements, procedures and operations, and missions for the current and future space station.

Space station systems: A bibliography with indexes

NASA Technical Reports Server (NTRS)

1987-01-01

This bibliography lists 967 reports, articles, and other documents introduced into the NASA scientific and technical information system between January 1, 1987 and June 30, 1987. Its purpose is to provide helpful information to the researcher, manager, and designer in technology development and mission design according to system, interactive analysis and design, structural and thermal analysis and design, structural concepts and control systems, electronics, advanced materials, assembly concepts, propulsion, and solar power satellite systems. The coverage includes documents that define major systems and subsystems, servicing and support requirements, procedures and operations, and missions for the current and future space station.

76 FR 10269 - AP1000 Design Certification Amendment

Federal Register 2010, 2011, 2012, 2013, 2014

2011-02-24

... design control document proposals. For the final rule, the NRC will complete the review of the CIs and... control requirement includes the descriptions of the design features and functional capabilities... objective of the change controls is to determine whether the design of the facility, as changed or modified...

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

Space shuttle redesigned solid rocket motor Certificate of Qualification (COQ) data report

NASA Technical Reports Server (NTRS)

Duersch, Fred, Jr.

1990-01-01

The Space Shuttle Redesigned Solid Rocket Motor (RSRM) Certification Program provides confidence that the RSRM and its components/subsystems meet or exceed Mission Oriented Requirements when manufactured per design requirements and specified/approved processes. Certification is based on documented results of tests, analyses, inspections, similarity, and demonstrations. Evidencing information is provided to certify that each RSRM component/subsystem satisfies design, mission related requirements and objectives.

Gearbox Reliability Collaborative Projects | Wind | NREL

Science.gov Websites

partners. This process documented and analyzed the design process and produced a new drivetrain design that Reliability Collaborative) activities. The new design represents the next phase in the DRC project, and will design loads required for wind turbine gearbox design and testing standards. While wind turbine gearboxes

MARA (Multimode Airborne Radar Altimeter) system documentation. Volume 1: MARA system requirements document

NASA Technical Reports Server (NTRS)

Parsons, C. L. (Editor)

1989-01-01

The Multimode Airborne Radar Altimeter (MARA), a flexible airborne radar remote sensing facility developed by NASA's Goddard Space Flight Center, is discussed. This volume describes the scientific justification for the development of the instrument and the translation of these scientific requirements into instrument design goals. Values for key instrument parameters are derived to accommodate these goals, and simulations and analytical models are used to estimate the developed system's performance.

Electrical Auxiliary Power Unit (EAPU) Corona Design Guideline. Revised

NASA Technical Reports Server (NTRS)

Hall, David K.; Kirkici, Hulya; Schweickart, Dan L.; Dunbar, William; Hillard, Barry

2000-01-01

This document is the result of a collaborative effort between NASA's Johnson Space Center, Marshall Space Flight Center, Glenn Research Center, and the United States Air Force Research Laboratory at Wright Patterson AFB in support of the Space Shuttle Orbiter Upgrades Program, specifically the Electric Auxiliary Power Unit Program. This document is intended as a guideline for design applications for corona and partial discharge avoidance and is not a requirements specification instrument.

openECA Detailed Design Document

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

Robertson, Russell

This document describes the functional and non-functional requirements for: The openECA platform The included analytic systems that will: Validate the operational readiness and performance of the openECA platform Provide out-of-box value to those that implement the openECA platform with an initial collection of analytics

Teaching Case: IS Security Requirements Identification from Conceptual Models in Systems Analysis and Design: The Fun & Fitness, Inc. Case

ERIC Educational Resources Information Center

Spears, Janine L.; Parrish, James L., Jr.

2013-01-01

This teaching case introduces students to a relatively simple approach to identifying and documenting security requirements within conceptual models that are commonly taught in systems analysis and design courses. An introduction to information security is provided, followed by a classroom example of a fictitious company, "Fun &…

American Association of University Women: Branch Operations Data Modeling Case

ERIC Educational Resources Information Center

Harris, Ranida B.; Wedel, Thomas L.

2015-01-01

A nationally prominent woman's advocacy organization is featured in this case study. The scenario may be used as a teaching case, an assignment, or a project in systems analysis and design as well as database design classes. Students are required to document the system operations and requirements, apply logical data modeling concepts, and design…

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.

Precise Documentation: The Key to Better Software

NASA Astrophysics Data System (ADS)

Parnas, David Lorge

The prime cause of the sorry “state of the art” in software development is our failure to produce good design documentation. Poor documentation is the cause of many errors and reduces efficiency in every phase of a software product's development and use. Most software developers believe that “documentation” refers to a collection of wordy, unstructured, introductory descriptions, thousands of pages that nobody wanted to write and nobody trusts. In contrast, Engineers in more traditional disciplines think of precise blueprints, circuit diagrams, and mathematical specifications of component properties. Software developers do not know how to produce precise documents for software. Software developments also think that documentation is something written after the software has been developed. In other fields of Engineering much of the documentation is written before and during the development. It represents forethought not afterthought. Among the benefits of better documentation would be: easier reuse of old designs, better communication about requirements, more useful design reviews, easier integration of separately written modules, more effective code inspection, more effective testing, and more efficient corrections and improvements. This paper explains how to produce and use precise software documentation and illustrate the methods with several examples.

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

None

The purpose of this document is to provide the technical requirements for operation, inspection and maintenance of a TRUPACT-II Shipping Package and directly related components. This document shall supply the minimum requirements as specified in the TRUPACT-II Safety Analysis Report for Packaging (SARP) and Certificate of Compliance (C of C) 9218. In the event there is a conflict between this document and the TRUPACT-II SARP (NRC Certificate of Compliance No. 9218), the TRUPACT-II SARP shall govern. This document details the operations, maintenance, repair, replacement of components, as well as the documentation required and the procedures to be followed to maintainmore » the integrity of the TRUPACT-II container. These procedures may be modified for site use, but as a minimum all parameters and format listed herein must be included in any site modified version. For convenience and where applicable steps may be performed out of sequence. Packaging and payload handling equipment and transport trailers have been specifically designed for use with the TRUPACT-II Packaging. This document discusses the minimum required procedures for use of the adjustable center of gravity lift fixture and the TRUPACT-II transport trailer in conjunction with the TRUPACT-II Packaging.« less

Development and implementation of clinical trial protocol templates at the National Institute of Allergy and Infectious Diseases.

PubMed

Bridge, Heather; Smolskis, Mary; Bianchine, Peter; Dixon, Dennis O; Kelly, Grace; Herpin, Betsey; Tavel, Jorge

2009-08-01

A clinical research protocol document must reflect both sound scientific rationale as well as local, national and, when applicable, international regulatory and human subject protections requirements. These requirements originate from a variety of sources, undergo frequent revision and are subject to interpretation. Tools to assist clinical investigators in the production of clinical protocols could facilitate navigating these requirements and ultimately increase the efficiency of clinical research. The National Institute of Allergy and Infectious Diseases (NIAID) developed templates for investigators to serve as the foundation for protocol development. These protocol templates are designed as tools to support investigators in developing clinical protocols. NIAID established a series of working groups to determine how to improve its capacity to conduct clinical research more efficiently and effectively. The Protocol Template Working Group was convened to determine what protocol templates currently existed within NIAID and whether standard NIAID protocol templates should be produced. After review and assessment of existing protocol documents and requirements, the group reached consensus about required and optional content, determined the format and identified methods for distribution as well as education of investigators in the use of these templates. The templates were approved by the NIAID Executive Committee in 2006 and posted as part of the NIAID Clinical Research Toolkit [1] website for broad access. These documents require scheduled revisions to stay current with regulatory and policy changes. The structure of any clinical protocol template, whether comprehensive or specific to a particular study phase, setting or design, affects how it is used by investigators. Each structure presents its own set of advantages and disadvantages. While useful, protocol templates are not stand-alone tools for creating an optimal protocol document, but must be complemented by institutional resources and support. Education and guidance of investigators in the appropriate use of templates is necessary to ensure a complete yet concise protocol document. Due to changing regulatory requirements, clinical protocol templates cannot become static, but require frequent revisions.

Requirements for color technology

NASA Astrophysics Data System (ADS)

Campbell, Ronald B., Jr.

1993-06-01

The requirements for color technology in the general office are reviewed. The two most salient factors driving the requirements for color are the information explosion and the virtually negligible growth in white collar productivity in the recent past. Accordingly, the business requirement upon color technology is that it be utilized in an effective and efficient manner to increase office productivity. Recent research on productivity and growth has moved beyond the classical two factor productivity model of labor and capital to explicitly include knowledge as a third and vital factor. Documents are agents of knowledge in the general office. Documents articulate, express, disseminate, and communicate knowledge. The central question addressed here is how can color, in conjunction with other techniques such as graphics and document design, improve the growth of knowledge? The central thesis is that the effective use of color to convert information into knowledge is one of the most powerful ways to increase office productivity. Material on the value of color is reviewed. This material is related to the role of documents. Document services are the way in which users access and utilize color technology. The requirements for color technology are then defined against the services taxonomy.

Communication Skills for Workplace Assessors.

ERIC Educational Resources Information Center

Corbett, Deborah

This document is designed to help develop the communication skills of individuals training for the position of workplace assessor in Australia's National Training Framework and practicing workplace assessors who require additional assistance with on-the-job communication skills. The document consists of 11 units of study that each contain some or…

40 CFR 63.1038 - Recordkeeping requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... visual inspections as specified in § 63.1026(b)(4). (ii) Documentation of dual mechanical seal pump... frequency of drips for dual mechanical seal pumps, records of the design criteria and explanations and any...). (ii) Trial evaluation program documentation as specified in § 63.1035(d)(6)(iii). (iii) Engineering...

A proposed USAF fatigue evaluation program based upon recent systems experience

NASA Technical Reports Server (NTRS)

Haviland, G. P.; Purkey, G. F.

1972-01-01

The United States Air Force has published a document entitled Aircraft Structural Integrity Program. One phase of the program is concerned with the fatigue life certification of all types of military aircraft. The document describes the criteria, analyses, and tests that are necessary in order to satisfy the USAF fatigue life requirement. Some recent and valid criticism has been directed toward the document, particularly the fatigue-life requirements contained in it. Some changes are proposed based on surveys conducted in the United States and abroad as well as some recent systems' experience. The surveys covered both military and civilian organizations. The fatigue certification case histories of selected military and commercial aircraft are presented. The design development element tests, preproduction design verification tests, and full-scale fatigue tests of each are described. A brief status report on the revisions to the MIL-A-008860 series specifications is included.

On the typography of flight-deck documentation

NASA Technical Reports Server (NTRS)

Degani, Asaf

1992-01-01

Many types of paper documentation are employed on the flight-deck. They range from a simple checklist card to a bulky Aircraft Flight Manual (AFM). Some of these documentations have typographical and graphical deficiencies; yet, many cockpit tasks such as conducting checklists, way-point entry, limitations and performance calculations, and many more, require the use of these documents. Moreover, during emergency and abnormal situations, the flight crews' effectiveness in combating the situation is highly dependent on such documentation; accessing and reading procedures has a significant impact on flight safety. Although flight-deck documentation are an important (and sometimes critical) form of display in the modern cockpit, there is a dearth of information on how to effectively design these displays. The object of this report is to provide a summary of the available literature regarding the design and typographical aspects of printed matter. The report attempts 'to bridge' the gap between basic research about typography, and the kind of information needed by designers of flight-deck documentation. The report focuses on typographical factors such as type-faces, character height, use of lower- and upper-case characters, line length, and spacing. Some graphical aspects such as layout, color coding, fonts, and character contrast are also discussed. In addition, several aspects of cockpit reading conditions such as glare, angular alignment, and paper quality are addressed. Finally, a list of recommendations for the graphical design of flight-deck documentation is provided.

Lightning Protection for the Orion Space Vehicle

NASA Technical Reports Server (NTRS)

Scully, Robert

2015-01-01

The Orion space vehicle is designed to requirements for both direct attachment and indirect effects of lightning. Both sets of requirements are based on a full threat 200kA strike, in accordance with constraints and guidelines contained in SAE ARP documents applicable to both commercial and military aircraft and space vehicles. This paper describes the requirements as levied against the vehicle, as well as the means whereby the design shows full compliance.

Directory of Energy Information Administration model abstracts

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

Not Available

1987-08-11

This report contains brief statements from the model managers about each model's title, acronym, purpose, and status, followed by more detailed information on characteristics, uses, and requirements. Sources for additional information are identified. All models ''active'' through March 1987 are included. The main body of this directory is an alphabetical list of all active EIA models. Appendix A identifies major EIA modeling systems and the models within these systems, and Appendix B identifies active EIA models by type (basic, auxiliary, and developing). A basic model is one designated by the EIA Administrator as being sufficiently important to require sustained supportmore » and public scrutiny. An auxiliary model is one designated by the EIA Administrator as being used only occasionally in analyses, and therefore requires minimal levels of documentation. A developing model is one designated by the EIA Administrator as being under development and yet of sufficient interest to require a basic level of documentation at a future date. EIA also leases models developed by proprietary software vendors. Documentation for these ''proprietary'' models is the responsibility of the companies from which they are leased. EIA has recently leased models from Chase Econometrics, Inc., Data Resources, Inc. (DRI), the Oak Ridge National Laboratory (ORNL), and Wharton Econometric Forecasting Associates (WEFA). Leased models are not abstracted here. The directory is intended for the use of energy and energy-policy analysts in the public and private sectors.« less

Design study of RL10 derivatives. Volume 3, part 1: Preliminary interface control document. [development of baseline engines for space tug vehicles

NASA Technical Reports Server (NTRS)

Adams, A.

1973-01-01

The Interface Control Document contains engine information necessary for installation of the baseline RL10 Derivative engines in the Space Tug vehicle. The ICD presents a description of the baseline engines and their operating characteristics, mass and load characteristics, and environmental criteria. The document defines the engine/vehicle mechanical, electrical, fluid and pneumatic interface requirements.

Functional design specification for Stowage List And Hardware Tracking System (SLAHTS). [space shuttles

NASA Technical Reports Server (NTRS)

Keltner, D. J.

1975-01-01

This functional design specification defines the total systems approach to meeting the requirements stated in the Detailed Requirements Document for Stowage List and Hardware Tracking System for the space shuttle program. The stowage list and hardware tracking system is identified at the system and subsystem level with each subsystem defined as a function of the total system.

Requirements and design aspects of a data model for a data dictionary in paediatric oncology.

PubMed

Merzweiler, A; Knaup, P; Creutzig, U; Ehlerding, H; Haux, R; Mludek, V; Schilling, F H; Weber, R; Wiedemann, T

2000-01-01

German children suffering from cancer are mostly treated within the framework of multicentre clinical trials. An important task of conducting these trials is an extensive information and knowledge exchange, which has to be based on a standardised documentation. To support this effort, it is the aim of a nationwide project to define a standardised terminology that should be used by clinical trials for therapy documentation. In order to support terminology maintenance we are currently developing a data dictionary. In this paper we describe requirements and design aspects of the data model used for the data dictionary as first results of our research. We compare it with other terminology systems.

From a Content Delivery Portal to a Knowledge Management System for Standardized Cancer Documentation.

PubMed

Schlue, Danijela; Mate, Sebastian; Haier, Jörg; Kadioglu, Dennis; Prokosch, Hans-Ulrich; Breil, Bernhard

2017-01-01

Heterogeneous tumor documentation and its challenges of interpretation of medical terms lead to problems in analyses of data from clinical and epidemiological cancer registries. The objective of this project was to design, implement and improve a national content delivery portal for oncological terms. Data elements of existing handbooks and documentation sources were analyzed, combined and summarized by medical experts of different comprehensive cancer centers. Informatics experts created a generic data model based on an existing metadata repository. In order to establish a national knowledge management system for standardized cancer documentation, a prototypical tumor wiki was designed and implemented. Requirements engineering techniques were applied to optimize this platform. It is targeted to user groups such as documentation officers, physicians and patients. The linkage to other information sources like PubMed and MeSH was realized.

NASA Processes and Requirements for Conducting Human-in-the-Loop Closed Chamber Tests

NASA Technical Reports Server (NTRS)

Barta, Daniel J.; Montz, Michael E.

2004-01-01

NASA has specific processes and requirements that must be followed for tests involving human subjects to be conducted in a safe and effective manner. There are five distinct phases of test operations. Phase one, the test request phase, consists of those activities related to initiating, processing, reviewing, and evaluating the test request. Phase two, the test preparation phase consists of those activities related to planning, coordinating, documenting, and building up the test. Phase three, the test readiness phase consists of those activities related to verifying and reviewing the planned test operations. Phase four, the test activity phase, consists of all pretest operations, functional checkouts, emergency drills, and test operations. Phase five, the post test activity phase, consists of those activities performed once the test is completed, including briefings, documentation of anomalies, data reduction and archiving, and reporting. Project management processes must be followed for facility modifications and major test buildup, which include six phases: initiation and assessment, requirements evaluation, preliminary design, detailed design, use readiness review (URR) and acceptance. Compliance with requirements for safety and quality assurance are documented throughout the test buildup and test operation processes. Tests involving human subjects must be reviewed by the applicable Institutional Review Board (IRB).

40 CFR 80.1454 - What are the recordkeeping requirements under the RFS program?

Code of Federal Regulations, 2012 CFR

2012-07-01

... blending, in the designated form. (6) Copies of registration documents required under § 80.1450, including...-fossil fraction of fuel made from separated municipal solid waste. (iv) Such other records as may be...

40 CFR 80.1454 - What are the recordkeeping requirements under the RFS program?

Code of Federal Regulations, 2013 CFR

2013-07-01

... blending, in the designated form. (6) Copies of registration documents required under § 80.1450, including...-fossil fraction of fuel made from separated municipal solid waste. (iv) Such other records as may be...

40 CFR 80.1454 - What are the recordkeeping requirements under the RFS program?

Code of Federal Regulations, 2011 CFR

2011-07-01

... blending, in the designated form. (6) Copies of registration documents required under § 80.1450, including...-fossil fraction of fuel made from separated municipal solid waste. (iv) Such other records as may be...

40 CFR 80.1454 - What are the recordkeeping requirements under the RFS program?

Code of Federal Regulations, 2014 CFR

2014-07-01

... blending, in the designated form. (6) Copies of registration documents required under § 80.1450, including...-fossil fraction of fuel made from separated municipal solid waste. (iv) Such other records as may be...

49 CFR 236.1009 - Procedural requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... fraud; (ii) Potentially invalidated assumptions determined as a result of in-service experience or one... inspect processes, procedures, facilities, documents, records, design and testing materials, artifacts, training materials and programs, and any other information used in the design, development, manufacture...

Structured representation for requirements and specifications

NASA Technical Reports Server (NTRS)

Cohen, Gerald C.; Fisher, Gene; Frincke, Deborah; Wolber, Dave

1991-01-01

This document was generated in support of NASA contract NAS1-18586, Design and Validation of Digital Flight Control Systems suitable for Fly-By-Wire Applications, Task Assignment 2. Task 2 is associated with a formal representation of requirements and specifications. In particular, this document contains results associated with the development of a Wide-Spectrum Requirements Specification Language (WSRSL) that can be used to express system requirements and specifications in both stylized and formal forms. Included with this development are prototype tools to support the specification language. In addition a preliminary requirements specification methodology based on the WSRSL has been developed. Lastly, the methodology has been applied to an Advanced Subsonic Civil Transport Flight Control System.

Using Biomimicry to Engage Students in a Design-Based Learning Activity

ERIC Educational Resources Information Center

Gardner, Grant E.

2012-01-01

I describe a design-based learning activity that utilizes the interdisciplinary content domain of biomimicry. Design-based learning requires student creativity and technological innovation to address novel science problems, characteristics of the nature of science not often addressed in schools. Alignment with national standards documents,…

76 FR 27629 - Endangered and Threatened Wildlife and Plants; Listing of the Altamaha Spinymussel and...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-05-12

.... Information for this analysis was gathered from the Small Business Administration, stakeholders, and the... designation, and the amended required determinations provided in this document. We will consider information... in threat outweighs the benefit of designation such that the designation of critical habitat is not...

Design Manual: Removal of Fluoride from Drinking Water Supplies by Activated Alumina

EPA Science Inventory

This document is an updated version of the Design Manual: Removal of Fluoride from Drinking Water Supplies by Activated Alumina (Rubel, 1984). The manual is an in-depth presentation of the steps required to design and operate a fluoride removal plant using activated alumina (AA)...

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

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

Vargo, G.F. Jr.

1994-10-11

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

Orbiter Avionics Radiation Handbook

NASA Technical Reports Server (NTRS)

Reddell, Brandon D.

1999-01-01

This handbook was assembled to document he radiation environment for design of Orbiter avionics. It also maps the environment through vehicle shielding and mission usage into discrete requirements such as total dose. Some details of analytical techniques for calculating radiation effects are provided. It is anticipated that appropriate portions of this document will be added to formal program specifications.

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

NASA Technical Reports Server (NTRS)

Dorsey, John T.

2011-01-01

The Lunar Surface Systems Project developed system concepts that would be necessary to establish and maintain a permanent human presence on the Lunar surface. A variety of specific system implementations were generated as a part of the scenarios, some level of system definition was completed, and masses estimated for each system. Because the architecture studies generally spawned a large number of system concepts and the studies were executed in a short amount of time, the resulting system definitions had very low design fidelity. This paper describes the development sequence required to field a particular structural system: 1) Define Requirements, 2) Develop the Design and 3) Demonstrate Compliance of the Design to all Requirements. This paper also outlines and describes in detail the information and data that are required to establish structural design requirements and outlines the information that would comprise a planetary surface system Structures Requirements document.

System Design Description for the TMAD Code

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

Finfrock, S.H.

This document serves as the System Design Description (SDD) for the TMAD Code System, which includes the TMAD code and the LIBMAKR code. The SDD provides a detailed description of the theory behind the code, and the implementation of that theory. It is essential for anyone who is attempting to review or modify the code or who otherwise needs to understand the internal workings of the code. In addition, this document includes, in Appendix A, the System Requirements Specification for the TMAD System.

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

Implementation of New Source Review in Areas that will be Designated as Nonattainment for the New 8-Hour Ozone Standard

EPA Pesticide Factsheets

This document may be of assistance in applying the New Source Review (NSR) air permitting regulations including the Prevention of Significant Deterioration (PSD) requirements. This document is part of the NSR Policy and Guidance Database. Some documents in the database are a scanned or retyped version of a paper photocopy of the original. Although we have taken considerable effort to quality assure the documents, some may contain typographical errors. Contact the office that issued the document if you need a copy of the original.

Assessment of the Content, Design, and Dissemination of the Real Warriors Campaign

DTIC Science & Technology

2012-01-01

by law as indicated in a notice appearing later in this work. This electronic representation of RAND intellectual property is provided for non...commercial use only. Unauthorized posting of RAND electronic documents to a non-RAND website is prohibited. RAND electronic documents are protected under...copyright law. Permission is required from RAND to reproduce, or reuse in another form, any of our research documents for commercial use. For

The 3-axis Dynamic Motion Simulator (DMS) system

NASA Technical Reports Server (NTRS)

1975-01-01

A three-axis dynamic motion simulator (DMS) consisting of a test table with three degrees of freedom and an electronics control system was designed, constructed, delivered, and tested. Documentation, as required in the Data Requirements List (DRL), was also provided.

Functional design for U.S. Coast Guard intelligent communications gateway

DOT National Transportation Integrated Search

1995-02-27

This report documents the functional design of hardware and software components necessary to satisfy the U.S. Coast Guard (USCG) requirements identified for an Intelligent Gateway (IG). The IG will transfer messages from USCG shoreside networks to tr...

Detailed requirements document for the problem reporting data system (PDS). [space shuttle and batch processing

NASA Technical Reports Server (NTRS)

West, R. S.

1975-01-01

The system is described as a computer-based system designed to track the status of problems and corrective actions pertinent to space shuttle hardware. The input, processing, output, and performance requirements of the system are presented along with standard display formats and examples. Operational requirements, hardware, requirements, and test requirements are also included.

Space shuttle orbiter guidance, naviagation and control software functional requirements: Horizontal flight operations

NASA Technical Reports Server (NTRS)

1972-01-01

The shuttle GN&C software functions for horizontal flight operations are defined. Software functional requirements are grouped into two categories: first horizontal flight requirements and full mission horizontal flight requirements. The document privides the intial step in the shuttle GN&C software design process. It also serves as a management tool to identify analyses which are required to define requirements.

Intranet-based safety documentation in management of major hazards and occupational health and safety.

PubMed

Leino, Antti

2002-01-01

In the European Union, Council Directive 96/82/EC requires operators producing, using, or handling significant amounts of dangerous substances to improve their safety management systems in order to better manage the major accident potentials deriving from human error. A new safety management system for the Viikinmäki wastewater treatment plant in Helsinki, Finland, was implemented in this study. The system was designed to comply with both the new safety liabilities and the requirements of OHSAS 18001 (British Standards Institute, 1999). During the implementation phase experiences were gathered from the development processes in this small organisation. The complete documentation was placed in the intranet of the plant. Hyperlinks between documents were created to ensure convenience of use. Documentation was made accessible for all workers from every workstation.

Requirements for Space Settlement Design

NASA Astrophysics Data System (ADS)

Gale, Anita E.; Edwards, Richard P.

2004-02-01

When large space settlements are finally built, inevitably the customers who pay for them will start the process by specifying requirements with a Request for Proposal (RFP). Although we are decades away from seeing the first of these documents, some of their contents can be anticipated now, and provide insight into the variety of elements that must be researched and developed before space settlements can happen. Space Settlement Design Competitions for High School students present design challenges in the form of RFPs, which predict basic requirements for space settlement attributes in the future, including structural features, infrastructure, living conveniences, computers, business areas, and safety. These requirements are generically summarized, and unique requirements are noted for specific space settlement locations and applications.

Impact of an electronic health record operating room management system in ophthalmology on documentation time, surgical volume, and staffing.

PubMed

Sanders, David S; Read-Brown, Sarah; Tu, Daniel C; Lambert, William E; Choi, Dongseok; Almario, Bella M; Yackel, Thomas R; Brown, Anna S; Chiang, Michael F

2014-05-01

Although electronic health record (EHR) systems have potential benefits, such as improved safety and quality of care, most ophthalmology practices in the United States have not adopted these systems. Concerns persist regarding potential negative impacts on clinical workflow. In particular, the impact of EHR operating room (OR) management systems on clinical efficiency in the ophthalmic surgery setting is unknown. To determine the impact of an EHR OR management system on intraoperative nursing documentation time, surgical volume, and staffing requirements. For documentation time and circulating nurses per procedure, a prospective cohort design was used between January 10, 2012, and January 10, 2013. For surgical volume and overall staffing requirements, a case series design was used between January 29, 2011, and January 28, 2013. This study involved ophthalmic OR nurses (n = 13) and surgeons (n = 25) at an academic medical center. Electronic health record OR management system implementation. (1) Documentation time (percentage of operating time documenting [POTD], absolute documentation time in minutes), (2) surgical volume (procedures/time), and (3) staffing requirements (full-time equivalents, circulating nurses/procedure). Outcomes were measured during a baseline period when paper documentation was used and during the early (first 3 months) and late (4-12 months) periods after EHR implementation. There was a worsening in total POTD in the early EHR period (83%) vs paper baseline (41%) (P < .001). This improved to baseline levels by the late EHR period (46%, P = .28), although POTD in the cataract group remained worse than at baseline (64%, P < .001). There was a worsening in absolute mean documentation time in the early EHR period (16.7 minutes) vs paper baseline (7.5 minutes) (P < .001). This improved in the late EHR period (9.2 minutes) but remained worse than in the paper baseline (P < .001). While cataract procedures required more circulating nurses in the early EHR (mean, 1.9 nurses/procedure) and late EHR (mean, 1.5 nurses/procedure) periods than in the paper baseline (mean, 1.0 nurses/procedure) (P < .001), overall staffing requirements and surgical volume were not significantly different between the periods. Electronic health record OR management system implementation was associated with worsening of intraoperative nursing documentation time especially in shorter procedures. However, it is possible to implement an EHR OR management system without serious negative impacts on surgical volume and staffing requirements.

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.

Development of Integrated Programs for Aerospace-vehicle design (IPAD): Reference design process

NASA Technical Reports Server (NTRS)

Meyer, D. D.

1979-01-01

The airplane design process and its interfaces with manufacturing and customer operations are documented to be used as criteria for the development of integrated programs for the analysis, design, and testing of aerospace vehicles. Topics cover: design process management, general purpose support requirements, design networks, and technical program elements. Design activity sequences are given for both supersonic and subsonic commercial transports, naval hydrofoils, and military aircraft.

NASA Supportability Engineering Implementation Utilizing DoD Practices and Processes

NASA Technical Reports Server (NTRS)

Smith, David A.; Smith, John V.

2010-01-01

The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.

The design, implementation, and use of a statewide land use inventory: The New York experience

NASA Technical Reports Server (NTRS)

Hardy, E. E.

1975-01-01

The New York State land use and natural resource inventory is described with emphasis on its design, implementation, and user requirements. Other topics discussed include: classification, data acquisition, geographic referencing, data storage, data retrieval, and documentation.

11 CFR 9003.1 - Candidate and committee agreements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

11 CFR 9003.1 - Candidate and committee agreements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

11 CFR 9003.1 - Candidate and committee agreements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

11 CFR 9003.1 - Candidate and committee agreements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

11 CFR 9003.1 - Candidate and committee agreements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... documentation requirements set forth at 11 CFR 9003.5. (3) Agree that they and their authorized committee(s... subchapter (including those required to be maintained under 11 CFR 9003.5), and other information that the... and address of the depository designated by the candidates as required by 11 CFR part 103 and 11 CFR...

45 CFR 307.15 - Approval of advance planning documents for computerized support enforcement systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... feasibility of the proposed effort and provide for the conduct of a requirements analysis study which address... indicate how the results of the requirements analysis study will be incorporated into the proposed system... address requirements analysis, program design, procurement and project management; and, a description of...

Return to Our Roots: Raising Radishes To Teach Experimental Design.

ERIC Educational Resources Information Center

Stallings, William M.

To provide practice in making design decisions, collecting and analyzing data, and writing and documenting results, a professor of statistics has his graduate students in statistics and research methodology classes design and perform an experiment on the effects of fertilizers on the growth of radishes. This project has been required of students…

Analysis of the systems of ventilation of residential houses of Ukraine and Estonia

NASA Astrophysics Data System (ADS)

Savchenko, Olena; Zhelykh, Vasyl; Voll, Hendrik

2017-12-01

The most common ventilation system in residential buildings in Ukraine is natural ventilation. In recent years, due to increased tightness of structures, an increase in the content of synthetic finishing materials in them, the quality of microclimate parameters deteriorated. One of the measures to improve the parameters of indoor air in residential buildings is the use of mechanical inflow and exhaust ventilation system. In this article the regulatory documents concerning the design of ventilation systems in Ukraine and Estonia and the requirements for air exchange in residential buildings are considered. It is established that the existing normative documents in Ukraine are analogous to European norms, which allow design the system of ventilation of residential buildings according to European standards. However, the basis for the design of ventilation systems in Ukraine is the national standards, in which mechanical ventilation, unfortunately, is provided only for the design of high-rise buildings. To maintain acceptable microclimate parameters in residential buildings, it is advisable for designers to apply the requirements for designing ventilation systems in accordance with European standards.

Buddy Tag CONOPS and Requirements.

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

Brotz, Jay Kristoffer; Deland, Sharon M.

2015-12-01

This document defines the concept of operations (CONOPS) and the requirements for the Buddy Tag, which is conceived and designed in collaboration between Sandia National Laboratories and Princeton University under the Department of State Key VerificationAssets Fund. The CONOPS describe how the tags are used to support verification of treaty limitations and is only defined to the extent necessary to support a tag design. The requirements define the necessary functions and desired non-functional features of the Buddy Tag at a high level

R-189 (C-620) air compressor control logic software documentation. Revision 1

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

Walter, K.E.

1995-06-08

This relates to FFTF plant air compressors. Purpose of this document is to provide an updated Computer Software Description for the software to be used on R-189 (C-620-C) air compressor programmable controllers. Logic software design changes were required to allow automatic starting of a compressor that had not been previously started.

Project C.H.A.N.G.E.: Concepts of Handicaps and Attitudes Need Guidance and Education. Media Assessment List.

ERIC Educational Resources Information Center

Smith, M. Sherry; And Others

The document contains a compilation of materials recommended for use in Project CHANGE (Concepts of Handicaps and Attitudes Need Guidance and Education), a comprehensive curriculum designed to improve children's attitudes toward the disabled. The major portion of the document consists of forms describing required and supplemental student materials…

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

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J. (Editor)

2008-01-01

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

A multi-agent system for monitoring patient flow.

PubMed

Rosati, Samanta; Tralli, Augusta; Balestra, Gabriella

2013-01-01

Patient flow within a healthcare facility may follow different and, sometimes, complicated paths. Each path phase is associated with the documentation of the activities carried out during it and may require the consultation of clinical guidelines, medical literature and the use of specific software and decision aid systems. In this study we present the design of a Patient Flow Management System (PFMS) based on Multi Agent Systems (MAS) methodology. System requirements were identified by means of process modeling tools and a MAS consisting of six agents was designed and is under construction. Its main goal is to support both the medical staff during the health care process and the hospital managers in assuring that all the required documentation is completed and available. Moreover, such a tool can be used for the assessment and comparison of different clinical pathways, in order to identify possible improvementsand the optimum patient flow.

Extended Operating Configuration 2 (EOC-2) Design Document

NASA Technical Reports Server (NTRS)

Barkai, David; Blaylock, Bruce T. (Technical Monitor)

1994-01-01

This document describes the design and plan of the Extended Operating Configuration 2 (EOC-2) for the Numerical Aerodynamic Simulation division (NAS). It covers the changes in the computing environment for the period of '93-'94. During this period the computation capability at NAS will have quadrupled. The first section summarizes this paper: the NAS mission is to provide, by the year 2000, a computing system capable of simulating an entire aerospace vehicle in a few hours. This will require 100 GigaFlops sustained performance. The second section contains information about the NAS user community and the computational model used for projecting future requirements. In the third section, the overall requirements are presented, followed by a summary of the target EOC-2 system. The following sections cover, in more detail, each major component that will have undergone change during EOC-2: the high speed processor, mass storage, workstations, and networks.

Requirements report for SSTO vertical take-off and horizontal landing vehicle

NASA Technical Reports Server (NTRS)

Greenberg, H. S.

1994-01-01

This document describes the detailed design requirements and design criteria to support Structures/TPS Technology development for SSTO winged vehicle configurations that use vertical take-off and horizontal landing and delivers 25,000 lb payloads to a 220 nm circular orbit at an inclination of 51.6 degrees or 40,000 lb payloads to a 150 nm circular orbit at a 28.5 degree inclination.

Air Force Research Laboratory Wright Site Guide to Technical Publishing

DTIC Science & Technology

2005-04-01

Scientific and Technical Reports—Elements, Organization, and Design manual (and a version modified for documents generated for AFRL) • Merriam-Webster’s...notice page --SF 298 --original graphics /halftones Indicate the following on the letter of transmittal sheet: --quantity of copies required for...Elements, Organization and Design ? The WRS CDRL for a final report requires that the standard be followed. The only exception is SBIR Phase 1

Software Engineering Laboratory (SEL) compendium of tools, revision 1

NASA Technical Reports Server (NTRS)

1982-01-01

A set of programs used to aid software product development is listed. Known as software tools, such programs include requirements analyzers, design languages, precompilers, code auditors, code analyzers, and software librarians. Abstracts, resource requirements, documentation, processing summaries, and availability are indicated for most tools.

Contracting to improve your revenue cycle performance.

PubMed

Welter, Terri L; Semko, George A; Miller, Tony; Lauer, Roberta

2007-09-01

The following key drivers of commercial contract variability can have a material effect on your hospital's revenue cycle: Claim form variance. Benefit design. Contract complexity. Coding variance. Medical necessity. Precertification/authorization. Claim adjudication/appeal requirements. Additional documentation requirements. Timeliness of payment. Third-party payer activity.

7 CFR 1485.16 - Reimbursement rules.

Code of Federal Regulations, 2010 CFR

2010-01-01

... design and production of packaging, labeling or origin identification, to be used during the activity... exceeds locally prevailing levels which the MAP participant shall document by a salary survey or other...) Market research; (17) Evaluations, if not required by CCC to ensure compliance with program requirements...

7 CFR 1485.16 - Reimbursement rules.

Code of Federal Regulations, 2011 CFR

2011-01-01

... design and production of packaging, labeling or origin identification, to be used during the activity... exceeds locally prevailing levels which the MAP participant shall document by a salary survey or other...) Market research; (17) Evaluations, if not required by CCC to ensure compliance with program requirements...

LIFE CYCLE DESIGN GUIDANCE MANUAL: ENVIRONMENTAL REQUIREMENTS AND THE PRODUCT SYSTEM

EPA Science Inventory

This document seeks to promote the reduction of environmental impacts and health risks through a systems approach to design. he approach is based on the product life cycle, which includes raw materials acquisition and processing, manufacturing, use/service, resource recovery, and...

LIFE CYCLE DESIGN GUIDANCE MANUAL - ENVIRONMENTAL REQUIREMENTS AND THE PRODUCT SYSTEM

EPA Science Inventory

This document seeks to promote the reduction of environmental impacts and health risks through a systems approach to design. The approach is based on die product life cycle, which includes raw materials acquisition and processing, manufacturing, use/service, resource recovery, an...

76 FR 56883 - Designation of Product Categories for Federal Procurement

Federal Register 2010, 2011, 2012, 2013, 2014

2011-09-14

... and should document exceptions taken for price, performance, and availability. USDA recognizes that...) requires USDA to provide information to procuring agencies on the availability, relative price, performance... a product designated by EPA generally to procure such a product composed of the highest percentage...

Space shuttle program: Lightning protection criteria document

NASA Technical Reports Server (NTRS)

1975-01-01

The lightning environment for space shuttle design is defined and requirements that the design must satisfy to insure protection of the vehicle system from direct and indirect effects of lightning are imposed. Specifications, criteria, and guidelines included provide a practical and logical approach to protection problems.

24 CFR 598.300 - Procedure for submitting a nomination.

Code of Federal Regulations, 2010 CFR

2010-04-01

... HOUSING AND URBAN DEVELOPMENT COMMUNITY FACILITIES URBAN EMPOWERMENT ZONES: ROUND TWO AND THREE... designation as Empowerment Zones, including submission deadlines and addresses, in a document announcing the... nominations for designation as Empowerment Zones that HUD determines have met the criteria required by this...

24 CFR 598.300 - Procedure for submitting a nomination.

Code of Federal Regulations, 2011 CFR

2011-04-01

... HOUSING AND URBAN DEVELOPMENT COMMUNITY FACILITIES URBAN EMPOWERMENT ZONES: ROUND TWO AND THREE... designation as Empowerment Zones, including submission deadlines and addresses, in a document announcing the... nominations for designation as Empowerment Zones that HUD determines have met the criteria required by this...

Contingency Contractor Optimization Phase 3 Sustainment Software Design Document - Contingency Contractor Optimization Tool - Prototype

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

Durfee, Justin David; Frazier, Christopher Rawls; Bandlow, Alisa

This document describes the final software design of the Contingency Contractor Optimization Tool - Prototype. Its purpose is to provide the overall architecture of the software and the logic behind this architecture. Documentation for the individual classes is provided in the application Javadoc. The Contingency Contractor Optimization project is intended to address Department of Defense mandates by delivering a centralized strategic planning tool that allows senior decision makers to quickly and accurately assess the impacts, risks, and mitigation strategies associated with utilizing contract support. The Contingency Contractor Optimization Tool - Prototype was developed in Phase 3 of the OSD ATLmore » Contingency Contractor Optimization project to support strategic planning for contingency contractors. The planning tool uses a model to optimize the Total Force mix by minimizing the combined total costs for selected mission scenarios. The model optimizes the match of personnel types (military, DoD civilian, and contractors) and capabilities to meet mission requirements as effectively as possible, based on risk, cost, and other requirements.« less

CWA 15793 2011 Planning and Implementation Tool

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

Gross, Alan; Nail, George

This software, built on an open source platform called Electron (runs on Chromium and Node.js), is designed to assist organizations in the implementation of a biorisk management system consistent with the requirements of the international, publicly available guidance document CEN Workshop Agreement 15793:2011 (CWA 15793). The software includes tools for conducting organizational gap analysis against CWA 15793 requirements, planning tools to support the implementation of CWA 15793 requirements, and performance monitoring support. The gap analysis questions are based on the text of CWA 15793, and its associated guidance document, CEN Workshop Agreement 16393:2012. The authors have secured permission from themore » publisher of CWA 15793, the European Committee for Standardization (CEN), to use language from the document in the software, with the understanding that the software will be made available freely, without charge.« less

A New Handbook for the Development of Space Vehicle Terrestrial Environment Design Requirements.

NASA Technical Reports Server (NTRS)

Johnson, Dale L.; Vaughan, William W.

2008-01-01

A new NASA document entitled "Terrestrial Environment (Climatic) Criteria Handbook for Use in Aerospace Vehicle Development (NASA-HDBK-1001A) has been developed. The Handbook provides terrestrial environment information, data bases, models, recommendations, etc. for use in the design, development, trade studies, testing, and mission analyses for space (or launch) .vehicles. This document is organized into fourteen specific natural environment disciplines of which some are winds, atmospheric models, thermal radiation, precipitation-for-icing, cloud cover, atmospheric electricity, geologic hazards, toxic chemical release by propulsion systems, and sea state. Atmospheric phenomena play a significant role in the design and flight of aerospace vehicles and in the integrity of the associated aerospace systems and structures. Environmental design criteria guidelines in this document are based on measurements and observations of atmospheric and climatic phenomena relative to various aerospace development, operational, and vehicle launch locations. The natural environment criteria guidelines data presented in this Handbook were formulated based on discussions with and requests from engineers involved in aerospace vehicle development and operations. Therefore, they represent responses to actual engineering problems and are not just a general compilation of environmental data. The Handbook addresses the basis for the information presented, the interpretations of the terrestrial environment guideline given in the Handbook, and its application to the development of aerospace vehicle design requirements. Specific examples of the Handbook content and associated "lessons lenmed" are given in this paper.

A New Handbook for the Development of Space Vehicle Terrestrial Environment Design Requirements

NASA Technical Reports Server (NTRS)

Johnson, Dale L.; Vaughan, William W.

2008-01-01

A new NASA document entitled "Terrestrial Environment (Climatic) Criteria Handbook for Use in Aerospace Vehicle Development (NASA-HDBK-IOO1A) has been developed. The Handbook provides terrestrial environment information, data bases, models, recommendations, etc. for use in the design, development, trade studies, testing, and mission analyses for space (or launch) vehicles. This document is organized into fourteen specific natural environment disciplines of which some are winds, atmospheric models, thermal radiation, precipitation-for-icing, cloud cover, atmospheric electricity, geologic hazards, toxic chemical release by propulsion systems, and sea state. Atmospheric phenomena play a significant role in the design and flight of aerospace vehicles and in the integrity of the associated aerospace systems and structures. Environmental design criteria guidelines in this document are based on measurements and observations of atmospheric and climatic phenomena relative to various aerospace development, operational, and vehicle launch locations. The natural environment criteria guidelines data presented in this Handbook were formulated based on discussions with and requests from engineers involved in aerospace vehicle development and operations. Therefore, they represent responses to actual engineering problems and are not just a general compilation of environmental data. The Handbook addresses the basis for the information presented, the interpretations of the terrestrial environment guideline given in the Handbook, and its application to the development of aerospace vehicle design requirements. Specific examples of the Handbook content and associated "lessons lenmed" are given in this paper.

The TMIS life-cycle process document, revision A

NASA Technical Reports Server (NTRS)

1991-01-01

The Technical and Management Information System (TMIS) Life-Cycle Process Document describes the processes that shall be followed in the definition, design, development, test, deployment, and operation of all TMIS products and data base applications. This document is a roll out of TMIS Standards Document (SSP 30546). The purpose of this document is to define the life cycle methodology that the developers of all products and data base applications and any subsequent modifications shall follow. Included in this methodology are descriptions of the tasks, deliverables, reviews, and approvals that are required before a product or data base application is accepted in the TMIS environment.

Solid waste information and tracking system client-server conversion project management plan

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

May, D.L.

1998-04-15

This Project Management Plan is the lead planning document governing the proposed conversion of the Solid Waste Information and Tracking System (SWITS) to a client-server architecture. This plan presents the content specified by American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE) standards for software development, with additional information categories deemed to be necessary to describe the conversion fully. This plan is a living document that will be reviewed on a periodic basis and revised when necessary to reflect changes in baseline design concepts and schedules. This PMP describes the background, planning and management of the SWITS conversion.more » It does not constitute a statement of product requirements. Requirements and specification documentation needed for the SWITS conversion will be released as supporting documents.« less

Space station systems: A bibliography with indexes (supplement 7)

NASA Technical Reports Server (NTRS)

1988-01-01

This bibliography lists 1,158 reports, articles, and other documents introduced into the NASA scientific and technical information system between January 1, 1988 and June 30, 1988. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

Space station systems: A bibliography with indexes (supplement 10)

NASA Technical Reports Server (NTRS)

1990-01-01

This bibliography lists 1,422 reports, articles, and other documents introduced into the NASA scientific and technical information system between July 1, 1989 and December 31, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

Space Station Systems: a Bibliography with Indexes (Supplement 8)

NASA Technical Reports Server (NTRS)

1988-01-01

This bibliography lists 950 reports, articles, and other documents introduced into the NASA scientific and technical information system between July 1, 1989 and December 31, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

Space station systems: A bibliography with indexes (supplement 9)

NASA Technical Reports Server (NTRS)

1989-01-01

This bibliography lists 1,313 reports, articles, and other documents introduced into the NASA scientific and technical information system between January 1, 1989 and June 30, 1989. Its purpose is to provide helpful information to researchers, designers and managers engaged in Space Station technology development and mission design. Coverage includes documents that define major systems and subsystems related to structures and dynamic control, electronics and power supplies, propulsion, and payload integration. In addition, orbital construction methods, servicing and support requirements, procedures and operations, and missions for the current and future Space Station are included.

Land Application of Wastes: An Educational Program. Monitoring at Land Application Sites - Module 18, Objectives, Script, and Booklet.

ERIC Educational Resources Information Center

Clarkson, W. W.; And Others

This module summarizes four major reasons for employing monitoring during design and operation of a land application site: documentation of existing water quality and system performance, confirmation of design parameters, provision of data for future designs and for management decisions. Monitoring requirements are examined for different land…

40 CFR 63.1426 - Process vent requirements for determining organic HAP concentration, control efficiency, and...

Code of Federal Regulations, 2013 CFR

2013-07-01

... performance test for those control techniques in accordance with paragraph (b)(6) of this section. The design..., immediately preceding the use of the control technique. A design evaluation shall also address other vent... paragraph (f)(1)(i) of this section, the design evaluation shall document the control efficiency and address...

Retrofit and acceptance test of 30-cm ion thrusters

NASA Technical Reports Server (NTRS)

Poeschel, R. L.

1981-01-01

Six 30 cm mercury thrusters were modified to the J-series design and evaluated using standardized test procedures. The thruster performance meets the design objectives (lifetime objective requires verification), and documentation (drawings, etc.) for the design is completed and upgraded. The retrofit modifications are described and the test data for the modifications are presented and discussed.

GMSEC Interface Specification Document 2016 March

NASA Technical Reports Server (NTRS)

Handy, Matthew

2016-01-01

The GMSEC Interface Specification Document contains the standard set of defined messages. Each GMSEC standard message contains a GMSEC Information Bus Header section and a Message Contents section. Each message section identifies required fields, optional fields, data type and recommended use of the fields. Additionally, this document includes the message subjects associated with the standard messages. The system design of the operations center should ensure the components that are selected use both the API and the defined standard messages in order to achieve full interoperability from component to component.

High Reynolds Number Hybrid Laminar Flow Control (HLFC) Flight Experiment. 3; Leading Edge Design, Fabrication, and Installation

NASA Technical Reports Server (NTRS)

1999-01-01

This document describes the design, fabrication, and installation of the suction panel and the required support structure, ducting, valving, and high-lift system (Krueger flaps) for flight demonstration of hybrid laminar flow control on the Boeing 757 airplane.

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

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

Laney, T.

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

Space Technology-5 Lithium-Ion Battery Design, Qualification and Integration and Testing

NASA Technical Reports Server (NTRS)

Rao, Gopalakishna M.; Stewart, Karen; Ameen, Syed; Banfield, Peter K.

2005-01-01

This document is a viewgraph presentation that reviews the Lithium Ion Battery for the Space Technology-5 (ST-5) mission. Included in the document is a review of the ST-5 Mission, a review of the battery requirements, a description of the battery and the battery materials. The testing and the integration and qualification data is reviewed.

Governance Health Check. Diagnosing Effective Governance for FE Colleges. Second Edition. [and] Diagnosing Effective Governance for Land-Based Colleges. Second Edition.

ERIC Educational Resources Information Center

Learning and Skills Development Agency, London (England).

These two documents are designed to assist governing bodies of England's further education (FE) and land-based colleges self-assess their performance and identify ways of improving their performance. Each document contains a "healthcheck" that requires approximately 30 minutes to complete and that was developed in response to informative…

Flat-plate solar array project. Volume 6: Engineering sciences and reliability

NASA Technical Reports Server (NTRS)

Ross, R. G., Jr.; Smokler, M. I.

1986-01-01

The Flat-Plate Solar Array (FSA) Project activities directed at developing the engineering technology base required to achieve modules that meet the functional, safety, and reliability requirements of large scale terrestrial photovoltaic systems applications are reported. These activities included: (1) development of functional, safety, and reliability requirements for such applications; (2) development of the engineering analytical approaches, test techniques, and design solutions required to meet the requirements; (3) synthesis and procurement of candidate designs for test and evaluation; and (4) performance of extensive testing, evaluation, and failure analysis of define design shortfalls and, thus, areas requiring additional research and development. A summary of the approach and technical outcome of these activities are provided along with a complete bibliography of the published documentation covering the detailed accomplishments and technologies developed.

The 5-kwe reactor thermoelectric system summary

NASA Technical Reports Server (NTRS)

Vanosdol, J. H. (Editor)

1973-01-01

Design of the 5-kwe reactor thermoelectric system was initiated in February 1972 and extended through the conceptual design phase into the preliminary design phase. Design effort was terminated in January, 1973. This report documents the system and component requirements, design approaches, and performance and design characteristics for the 5-kwe system. Included is summary information on the reactor, radiation shields, power conversion systems, thermoelectric pump, radiator/structure, liquid metal components, and the control system.

44 CFR 72.6 - Unfavorable response.

Code of Federal Regulations, 2011 CFR

2011-10-01

... projects or designs and their impacts on flood hazards in a community. Requesters are not entitled to any... provide the appropriate scientific or technical documentation or to obtain required authorizations...

44 CFR 72.6 - Unfavorable response.

Code of Federal Regulations, 2010 CFR

2010-10-01

... projects or designs and their impacts on flood hazards in a community. Requesters are not entitled to any... provide the appropriate scientific or technical documentation or to obtain required authorizations...

Mod-5A wind turbine generator program design report. Volume 2: Conceptual and preliminary design, book 2

NASA Technical Reports Server (NTRS)

1984-01-01

The design, development and analysis of the 7.3 MW MOD-5A wind tunnel generator is documented. There are four volumes. In Volume 2, book 2 the requirements and criteria for the design are presented. The development tests, which determined or characterized many of the materials and components of the wind turbine generator, are described.

Reducing the complexity of the software design process with object-oriented design

NASA Technical Reports Server (NTRS)

Schuler, M. P.

1991-01-01

Designing software is a complex process. How object-oriented design (OOD), coupled with formalized documentation and tailored object diagraming techniques, can reduce the complexity of the software design process is described and illustrated. The described OOD methodology uses a hierarchical decomposition approach in which parent objects are decomposed into layers of lower level child objects. A method of tracking the assignment of requirements to design components is also included. Increases in the reusability, portability, and maintainability of the resulting products are also discussed. This method was built on a combination of existing technology, teaching experience, consulting experience, and feedback from design method users. The discussed concepts are applicable to hierarchal OOD processes in general. Emphasis is placed on improving the design process by documenting the details of the procedures involved and incorporating improvements into those procedures as they are developed.

Design-Load Basis for LANL Structures, Systems, and Components

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

I. Cuesta

2004-09-01

This document supports the recommendations in the Los Alamos National Laboratory (LANL) Engineering Standard Manual (ESM), Chapter 5--Structural providing the basis for the loads, analysis procedures, and codes to be used in the ESM. It also provides the justification for eliminating the loads to be considered in design, and evidence that the design basis loads are appropriate and consistent with the graded approach required by the Department of Energy (DOE) Code of Federal Regulation Nuclear Safety Management, 10, Part 830. This document focuses on (1) the primary and secondary natural phenomena hazards listed in DOE-G-420.1-2, Appendix C, (2) additional loadsmore » not related to natural phenomena hazards, and (3) the design loads on structures during construction.« less

Simulant Basis for the Standard High Solids Vessel Design

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

Peterson, Reid A.; Fiskum, Sandra K.; Suffield, Sarah R.

The Waste Treatment and Immobilization Plant (WTP) is working to develop a Standard High Solids Vessel Design (SHSVD) process vessel. To support testing of this new design, WTP engineering staff requested that a Newtonian simulant and a non-Newtonian simulant be developed that would represent the Most Adverse Design Conditions (in development) with respect to mixing performance as specified by WTP. The majority of the simulant requirements are specified in 24590-PTF-RPT-PE-16-001, Rev. 0. The first step in this process is to develop the basis for these simulants. This document describes the basis for the properties of these two simulant types. Themore » simulant recipes that meet this basis will be provided in a subsequent document.« less

40 CFR 63.1207 - What are the performance testing requirements?

Code of Federal Regulations, 2010 CFR

2010-07-01

... operating conditions that are most likely to reflect daily maximum operating variability, similar to a... operating variability, similar to a dioxin/furan compliance test; (B) You have not changed the design or... document the temperature location measurement in the comprehensive performance test plan, as required by...

33 CFR 157.12g - Plan approval requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... OIL IN BULK Design, Equipment, and Installation § 157.12g Plan approval requirements. Adequate documentation must be prepared well in advance of the intended installation of a monitoring system and must be... ballast handling manuals. Special considerations will be given to installations in oil tankers, which have...

Program Description: Financial Master File Processor-SWRL Financial System.

ERIC Educational Resources Information Center

Ideda, Masumi

Computer routines designed to produce various management and accounting reports required by the Southwest Regional Laboratory's (SWRL) Financial System are described. Input data requirements and output report formats are presented together with a discussion of the Financial Master File updating capabilities of the system. This document should be…

48 CFR 1352.271-85 - Documentation of requests for equitable adjustment.

Code of Federal Regulations, 2013 CFR

2013-10-01

... installation of such property shall be indicated. A separate description shall be furnished for design and... design work and production work; (4) A description of any interference or inefficiency encountered in...-referenced to the detailed information required above; and (9) A statement setting forth a comparative...

48 CFR 1352.271-85 - Documentation of requests for equitable adjustment.

Code of Federal Regulations, 2012 CFR

2012-10-01

... installation of such property shall be indicated. A separate description shall be furnished for design and... design work and production work; (4) A description of any interference or inefficiency encountered in...-referenced to the detailed information required above; and (9) A statement setting forth a comparative...

48 CFR 1352.271-85 - Documentation of requests for equitable adjustment.

Code of Federal Regulations, 2011 CFR

2011-10-01

... installation of such property shall be indicated. A separate description shall be furnished for design and... design work and production work; (4) A description of any interference or inefficiency encountered in...-referenced to the detailed information required above; and (9) A statement setting forth a comparative...

48 CFR 1352.271-85 - Documentation of requests for equitable adjustment.

Code of Federal Regulations, 2010 CFR

2010-10-01

... installation of such property shall be indicated. A separate description shall be furnished for design and... design work and production work; (4) A description of any interference or inefficiency encountered in...-referenced to the detailed information required above; and (9) A statement setting forth a comparative...

48 CFR 1352.271-85 - Documentation of requests for equitable adjustment.

Code of Federal Regulations, 2014 CFR

2014-10-01

... installation of such property shall be indicated. A separate description shall be furnished for design and... design work and production work; (4) A description of any interference or inefficiency encountered in...-referenced to the detailed information required above; and (9) A statement setting forth a comparative...

40 CFR 72.94 - Units with repowering extension plans.

Code of Federal Regulations, 2014 CFR

2014-07-01

... plans. (a) Design and engineering and contract requirements. No later than January 1, 2000, the... and the permitting authority: (1) Satisfactory documentation of a preliminary design and engineering effort. (2) A binding letter agreement for the executed and binding contract (or for each in a series of...

40 CFR 72.94 - Units with repowering extension plans.

Code of Federal Regulations, 2010 CFR

2010-07-01

... plans. (a) Design and engineering and contract requirements. No later than January 1, 2000, the... and the permitting authority: (1) Satisfactory documentation of a preliminary design and engineering effort. (2) A binding letter agreement for the executed and binding contract (or for each in a series of...

40 CFR 72.94 - Units with repowering extension plans.

Code of Federal Regulations, 2011 CFR

2011-07-01

... plans. (a) Design and engineering and contract requirements. No later than January 1, 2000, the... and the permitting authority: (1) Satisfactory documentation of a preliminary design and engineering effort. (2) A binding letter agreement for the executed and binding contract (or for each in a series of...

40 CFR 72.94 - Units with repowering extension plans.

Code of Federal Regulations, 2012 CFR

2012-07-01

... plans. (a) Design and engineering and contract requirements. No later than January 1, 2000, the... and the permitting authority: (1) Satisfactory documentation of a preliminary design and engineering effort. (2) A binding letter agreement for the executed and binding contract (or for each in a series of...

40 CFR 72.94 - Units with repowering extension plans.

Code of Federal Regulations, 2013 CFR

2013-07-01

... plans. (a) Design and engineering and contract requirements. No later than January 1, 2000, the... and the permitting authority: (1) Satisfactory documentation of a preliminary design and engineering effort. (2) A binding letter agreement for the executed and binding contract (or for each in a series of...

77 FR 43567 - Medical Area Body Network

Federal Register 2010, 2011, 2012, 2013, 2014

2012-07-25

... document requests comment on a number of issues related to the designation of Medical Body Area Network... also determined that additional notice and comment was required on key aspects related to the process and criteria for designating an MBAN coordinator. DATES: Comments must be filed on or before September...

25 CFR 542.15 - What are the minimum internal control standards for credit?

Code of Federal Regulations, 2014 CFR

2014-04-01

...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

25 CFR 542.15 - What are the minimum internal control standards for credit?

Code of Federal Regulations, 2013 CFR

2013-04-01

...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

25 CFR 542.15 - What are the minimum internal control standards for credit?

Code of Federal Regulations, 2012 CFR

2012-04-01

...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

25 CFR 542.15 - What are the minimum internal control standards for credit?

Code of Federal Regulations, 2010 CFR

2010-04-01

...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

25 CFR 542.15 - What are the minimum internal control standards for credit?

Code of Federal Regulations, 2011 CFR

2011-04-01

...) Documentation of authorization by a person designated by management to approve credit limits; and (v) Credit... approved by personnel designated by management. (4) Proper approval of credit extensions over ten percent... that require access and are so authorized by management; (ii) Outstanding credit instruments shall be...

76 FR 57056 - International Cooperation on Harmonisation of Technical Requirements for Registration of...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-09-15

... guidance document is intended to provide study design recommendations that will facilitate the universal... objective of this guidance is to provide study design recommendations that will facilitate the universal... Products; Guidance for Industry on Studies To Evaluate the Metabolism and Residue Kinetics of Veterinary...

Improving the Aircraft Design Process Using Web-Based Modeling and Simulation

NASA Technical Reports Server (NTRS)

Reed, John A.; Follen, Gregory J.; Afjeh, Abdollah A.; Follen, Gregory J. (Technical Monitor)

2000-01-01

Designing and developing new aircraft systems is time-consuming and expensive. Computational simulation is a promising means for reducing design cycle times, but requires a flexible software environment capable of integrating advanced multidisciplinary and multifidelity analysis methods, dynamically managing data across heterogeneous computing platforms, and distributing computationally complex tasks. Web-based simulation, with its emphasis on collaborative composition of simulation models, distributed heterogeneous execution, and dynamic multimedia documentation, has the potential to meet these requirements. This paper outlines the current aircraft design process, highlighting its problems and complexities, and presents our vision of an aircraft design process using Web-based modeling and simulation.

Improving the Aircraft Design Process Using Web-based Modeling and Simulation

NASA Technical Reports Server (NTRS)

Reed, John A.; Follen, Gregory J.; Afjeh, Abdollah A.

2003-01-01

Designing and developing new aircraft systems is time-consuming and expensive. Computational simulation is a promising means for reducing design cycle times, but requires a flexible software environment capable of integrating advanced multidisciplinary and muitifidelity analysis methods, dynamically managing data across heterogeneous computing platforms, and distributing computationally complex tasks. Web-based simulation, with its emphasis on collaborative composition of simulation models, distributed heterogeneous execution, and dynamic multimedia documentation, has the potential to meet these requirements. This paper outlines the current aircraft design process, highlighting its problems and complexities, and presents our vision of an aircraft design process using Web-based modeling and simulation.

Optimal Corrosion Control Treatment Evaluation Technical Recommendations

EPA Pesticide Factsheets

This document provides technical recommendations that both systems and primacy agencies can use to comply with LCR CCT requirements and effective evaluation and designation of optimal corrosion control treatment (OCCT).

Shuttle mission simulator requirements report, volume 1, revision C

NASA Technical Reports Server (NTRS)

Burke, J. F.

1973-01-01

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

Analytical study of electrical disconnect system for use on manned and unmanned missions

NASA Technical Reports Server (NTRS)

Rosener, A. A.; Lenda, J. A.; Trummer, R. O.; Jonkoniec, T. G.

1977-01-01

The program to survey existing electrical connector availability, and establish an optimum connector design for maintainable spacecraft substation interfaces is reported. Functional and operational requirements are given along with the results of the documentation survey, which disclosed that the MSFC series connectors have the preferred features of current connector technology. Optimum design concepts for EVA tasks, modules serviced by manipulators, and for manipulators independent of other servicing units are presented. It is concluded that separate connector designs are required for spacecraft replaceable modules, and for crewman EVA.

Guidance and Control Design for High-Speed Rollout and Turnoff (ROTO)

NASA Technical Reports Server (NTRS)

Goldthorpe, S. H.; Dangaran, R. D.; Dwyer, J. P.; McBee, L. S.; Norman, R. M.; Shannon, J. H.; Summers, L. G.

1996-01-01

A ROTO architecture, braking and steering control law and display designs for a research high speed Rollout and Turnoff (ROTO) system applicable to transport class aircraft are described herein. Minimum surface friction and FMS database requirements are also documented. The control law designs were developed with the aid of a non-real time simulation program incorporating airframe and gear dynamics as well as steering and braking guidance algorithms. An attainable objective of this ROTO system, as seen from the results of this study, is to assure that the studied aircraft can land with runway occupancy times less then 53 seconds. Runway occupancy time is measured from the time the aircraft crosses the runway threshold until its wing tip clears the near side of the runway. Turnoff ground speeds of 70 knots onto 30 degree exits are allowed with dry and wet surface conditions. Simulation time history and statistical data are documented herein. Parameters which were treated as variables in the simulation study include aircraft touchdown weight/speed/location, aircraft CG, runway friction, sensor noise and winds. After further design and development of the ROTO control system beyond the system developed earlier, aft CG MD-11 aircraft no longer require auto-asymmetric braking (steering) and fly-by-wire nose gear steering. However, the auto ROTO nose gear hysteresis must be less than 2 degrees. The 2 sigma dispersion certified for MD-11 CATIIIB is acceptable. Using this longitudinal dispersion, three ROTO exits are recommended at 3300, 4950 and 6750 feet past the runway threshold. The 3300 foot exit is required for MD-81 class aircraft. Designs documented in this report are valid for the assumptions/models used in this simulation. It is believed that the results will apply to the general class of transport aircraft; however further effort is required to validate this assumption for the general case.

Directory of Energy Information Administration model abstracts 1988

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

Not Available

1988-01-01

This directory contains descriptions about each basic and auxiliary model, including the title, acronym, purpose, and type, followed by more detailed information on characteristics, uses, and requirements. For developing models, limited information is provided. Sources for additional information are identified. Included in this directory are 44 EIA models active as of February 1, 1988; 16 of which operate on personal computers. Models that run on personal computers are identified by ''PC'' as part of the acronyms. The main body of this directory is an alphabetical listing of all basic and auxiliary EIA models. Appendix A identifies major EIA modeling systemsmore » and the models within these systems, and Appendix B identifies EIA models by type (basic or auxiliary). Appendix C lists developing models and contact persons for those models. A basic model is one designated by the EIA Administrator as being sufficiently important to require sustained support and public scrutiny. An auxiliary model is one designated by the EIA Administrator as being used only occasionally in analyses, and therefore requires minimal levels of documentation. A developing model is one designated by the EIA Administrator as being under development and yet of sufficient interest to require a basic level of documentation at a future date. EIA also leases models developed by proprietary software vendors. Documentation for these ''proprietary'' models is the responsibility of the companies from which they are leased. EIA has recently leased models from Chase Econometrics, Inc., Data Resources, Inc. (DRI), the Oak Ridge National Laboratory (ORNL), and Wharton Econometric Forecasting Associates (WEFA). Leased models are not abstracted here.« less

Security Policy for a Generic Space Exploration Communication Network Architecture

NASA Technical Reports Server (NTRS)

Ivancic, William D.; Sheehe, Charles J.; Vaden, Karl R.

2016-01-01

This document is one of three. It describes various security mechanisms and a security policy profile for a generic space-based communication architecture. Two other documents accompany this document- an Operations Concept (OpsCon) and a communication architecture document. The OpsCon should be read first followed by the security policy profile described by this document and then the architecture document. The overall goal is to design a generic space exploration communication network architecture that is affordable, deployable, maintainable, securable, evolvable, reliable, and adaptable. The architecture should also require limited reconfiguration throughout system development and deployment. System deployment includes subsystem development in a factory setting, system integration in a laboratory setting, launch preparation, launch, and deployment and operation in space.

Engineering risk reduction in satellite programs

NASA Technical Reports Server (NTRS)

Dean, E. S., Jr.

1979-01-01

Methods developed in planning and executing system safety engineering programs for Lockheed satellite integration contracts are presented. These procedures establish the applicable safety design criteria, document design compliance and assess the residual risks where non-compliant design is proposed, and provide for hazard analysis of system level test, handling and launch preparations. Operations hazard analysis identifies product protection and product liability hazards prior to the preparation of operational procedures and provides safety requirements for inclusion in them. The method developed for documenting all residual hazards for the attention of program management assures an acceptable minimum level of risk prior to program deployment. The results are significant for persons responsible for managing or engineering the deployment and production of complex high cost equipment under current product liability law and cost/time constraints, have a responsibility to minimize the possibility of an accident, and should have documentation to provide a defense in a product liability suit.

MODIS information, data and control system (MIDACS) level 2 functional requirements

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Sharts, B.; Folta, D.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.

1988-01-01

The MODIS Information, Data and Control System (MIDACS) Level 2 Functional Requirements Document establishes the functional requirements for MIDACS and provides a basis for the mutual understanding between the users and the designers of the EosDIS, including the requirements, operating environment, external interfaces, and development plan. In defining the requirements and scope of the system, this document describes how MIDACS will operate as an element of the EOS within the EosDIS environment. This version of the Level 2 Requirements Document follows an earlier release of a preliminary draft version. The sections on functional and performance requirements do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. Indeed, the team members have not yet been selected and the team has not yet been formed; however, it has been possible to identify many relevant requirements based on the present concept of EosDIS and through interviews and meetings with key members of the scientific community. These requirements have been grouped by functional component of the data system, and by function within each component. These requirements have been merged with the complete set of Level 1 and Level 2 context diagrams, data flow diagrams, and data dictionary.

Development and Implementation of Clinical Trial Protocol Templates at the National Institute of Allergy and Infectious Diseases

PubMed Central

Bridge, Heather; Smolskis, Mary; Bianchine, Peter; Dixon, Dennis O.; Kelly, Grace; Herpin, Betsey; Tavel, Jorge

2009-01-01

Background: A clinical research protocol document must reflect both sound scientific rationale as well as local, national and, when applicable, international regulatory and human subject protections requirements. These requirements originate from a variety of sources, undergo frequent revision and are subject to interpretation. Tools to assist clinical investigators in the production of clinical protocols could facilitate navigating these requirements and ultimately increase the efficiency of clinical research. Purpose: The National Institute of Allergy and Infectious Diseases (NIAID) developed templates for investigators to serve as the foundation for protocol development. These protocol templates are designed as tools to support investigators in developing clinical protocols. Methods: NIAID established a series of working groups to determine how to improve its capacity to conduct clinical research more efficiently and effectively. The Protocol Template Working Group was convened to determine what protocol templates currently existed within NIAID and whether standard NIAID protocol templates should be produced. After review and assessment of existing protocol documents and requirements, the group reached consensus about required and optional content, determined the format and identified methods for distribution as well as education of investigators in the use of these templates. Results: The templates were approved by the NIAID Executive Committee in 2006 and posted as part of the NIAID Clinical Research Toolkit[1]website for broad access. These documents require scheduled revisions to stay current with regulatory and policy changes. Limitations: The structure of any clinical protocol template, whether comprehensive or specific to a particular study phase, setting or design, affects how it is used by investigators. Each structure presents its own set of advantages and disadvantages. While useful, protocol templates are not stand-alone tools for creating an optimal protocol document but must be complemented by institutional resources and support. Education and guidance of investigators in the appropriate use of templates is necessary to ensure a complete yet concise protocol document. Due to changing regulatory requirements, clinical protocol templates cannot become static but require frequent revisions. Conclusions: Standard protocol templates that meet applicable regulations can be important tools to assist investigators in the effective conduct of clinical research, but they require dedicated resources and ongoing input from key stakeholders. PMID:19625326

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

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…

Improving Quality Using Architecture Fault Analysis with Confidence Arguments

DTIC Science & Technology

2015-03-01

the same time, T text, diagram, and table-based requirements documentation and the use of Microsoft Word and Dynamic Object - Oriented Requirements...Lamsweerde 2003] Van Lamsweerde, Axel & Letier, Emmanuel. “From Object Orientation to Goal Orientation : A Paradigm Shift for Requirements Engineering,” 4–8...Introduction 1 Approach , Concepts, and Notations 5 2.1 Requirement Specification and Architecture Design 5 2.2 AADL Concepts Supporting Architecture

Data Quality Objectives for Regulatory Requirements for Dangerous Waste Sampling and Analysis

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

MULKEY, C.H.

1999-07-02

This document describes sampling and analytical requirements needed to meet state and federal regulations for dangerous waste (DW). The River Protection Project (RPP) is assigned to the task of storage and interim treatment of hazardous waste. Any final treatment or disposal operations, as well as requirements under the land disposal restrictions (LDRs), fall in the jurisdiction of another Hanford organization and are not part of this scope. The requirements for this Data Quality Objective (DQO) Process were developed using the RPP Data Quality Objective Procedure (Banning 1996), which is based on the U.S. Environmental Protection Agency's (EPA) Guidance for themore » Data Quality Objectives Process (EPA 1994). Hereafter, this document is referred to as the DW DQO. Federal and state laws and regulations pertaining to waste contain requirements that are dependent upon the composition of the waste stream. These regulatory drivers require that pertinent information be obtained. For many requirements, documented process knowledge of a waste composition can be used instead of analytical data to characterize or designate a waste. When process knowledge alone is used to characterize a waste, it is a best management practice to validate the information with analytical measurements.« less

Quantitative and qualitative analysis of study-related patient information sheets in randomised neuro-oncology phase III-trials.

PubMed

Reinert, Christiane; Kremmler, Lukas; Burock, Susen; Bogdahn, Ulrich; Wick, Wolfgang; Gleiter, Christoph H; Koller, Michael; Hau, Peter

2014-01-01

In randomised controlled trials (RCTs), patient informed consent documents are an essential cornerstone of the study flow. However, these documents are often oversized in format and content. Clinical experience suggests that study information sheets are often not used as an aid to decision-making due to their complexity. We analysed nine patient informed consent documents from clinical neuro-oncological phase III-studies running at a German Brain Tumour Centre with the objective to investigate the quality of these documents. Text length, formal layout, readability, application of ethical and legal requirements, scientific evidence and social aspects were used as rating categories. Results were assessed quantitatively by two independents investigators and were depicted using net diagrams. All patient informed consent documents were of insufficient quality in all categories except that ethical and legal requirements were fulfilled. Notably, graduate levels were required to read and understand five of nine consent documents. Quality deficits were consistent between the individual study information texts. Irrespective of formal aspects, a document that is intended to inform and motivate patients to participate in a study needs to be well-structured and understandable. We therefore strongly mandate to re-design patient informed consent documents in a patient-friendly way. Specifically, standardised components with a scientific foundation should be provided that could be retrieved at various times, adapted to the mode of treatment and the patient's knowledge, and could weigh information dependent of the stage of treatment decision. Copyright © 2013 Elsevier Ltd. All rights reserved.

38 CFR 39.31 - Preapplication requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... documentation, as needed). (4) A design concept describing the major features of the project including the... space, or functional layout; and it will not enter into a construction contract for the project or...

38 CFR 39.31 - Preapplication requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... documentation, as needed). (4) A design concept describing the major features of the project including the... space, or functional layout; and it will not enter into a construction contract for the project or...

System Guidelines for EMC Safety-Critical Circuits: Design, Selection, and Margin Demonstration

NASA Technical Reports Server (NTRS)

Lawton, R. M.

1996-01-01

Demonstration of safety margins for critical points (circuits) has traditionally been required since it first became a part of systems-level Electromagnetic Compatibility (EMC) requirements of MIL-E-6051C. The goal of this document is to present cost-effective guidelines for ensuring adequate Electromagnetic Effects (EME) safety margins on spacecraft critical circuits. It is for the use of NASA and other government agencies and their contractors to prevent loss of life, loss of spacecraft, or unacceptable degradation. This document provides practical definition and treatment guidance to contain costs within affordable limits.

Space transfer concepts and analysis for exploration missions. Implementation plan and element description document (draft final). Volume 4: Solar electric propulsion vehicle

NASA Technical Reports Server (NTRS)

1991-01-01

This document presents the solar electric propulsion (SEP) concept design developed as part of the Space Transfer Concepts and Analysis for Exploration Missions (STCAEM) study. The evolution of the SEP concept is described along with the requirements, guidelines and assumptions for the design. Operating modes and options are defined and a systems description of the vehicle is presented. Artificial gravity configuration options and space and ground support systems are discussed. Finally, an implementation plan is presented which addresses technology needs, schedules, facilities, and costs.

Space transfer concepts and analysis for exploration missions. Implementation plan and element description document (draft final). Volume 3: Nuclear thermal rocket vehicle

NASA Technical Reports Server (NTRS)

1991-01-01

This document presents the nuclear thermal rocket (NTR) concept design developed in support of the Space Transfer Concepts and Analysis for Exploration Missions (STCAEM) study. The evolution of the NTR concept is described along with the requirements, guidelines and assumptions for the design. Operating modes and options are defined and a systems description of the vehicle is presented. Artificial gravity configuration options and space and ground support systems are discussed. Finally, an implementation plan is presented which addresses technology needs, schedules, facilities and costs.

SLS Model Based Design: A Navigation Perspective

NASA Technical Reports Server (NTRS)

Oliver, T. Emerson; Anzalone, Evan; Park, Thomas; Geohagan, Kevin

2018-01-01

The SLS Program has implemented a Model-based Design (MBD) and Model-based Requirements approach for managing component design information and system requirements. This approach differs from previous large-scale design efforts at Marshall Space Flight Center where design documentation alone conveyed information required for vehicle design and analysis and where extensive requirements sets were used to scope and constrain the design. The SLS Navigation Team is responsible for the Program-controlled Design Math Models (DMMs) which describe and represent the performance of the Inertial Navigation System (INS) and the Rate Gyro Assemblies (RGAs) used by Guidance, Navigation, and Controls (GN&C). The SLS Navigation Team is also responsible for navigation algorithms. The navigation algorithms are delivered for implementation on the flight hardware as a DMM. For the SLS Block 1B design, the additional GPS Receiver hardware model is managed as a DMM at the vehicle design level. This paper describes the models, and discusses the processes and methods used to engineer, design, and coordinate engineering trades and performance assessments using SLS practices as applied to the GN&C system, with a particular focus on the navigation components.

Design knowledge capture for a corporate memory facility

NASA Technical Reports Server (NTRS)

Boose, John H.; Shema, David B.; Bradshaw, Jeffrey M.

1990-01-01

Currently, much of the information regarding decision alternatives and trade-offs made in the course of a major program development effort is not represented or retained in a way that permits computer-based reasoning over the life cycle of the program. The loss of this information results in problems in tracing design alternatives to requirements, in assessing the impact of change in requirements, and in configuration management. To address these problems, the problem was studied of building an intelligent, active corporate memory facility which would provide for the capture of the requirements and standards of a program, analyze the design alternatives and trade-offs made over the program's lifetime, and examine relationships between requirements and design trade-offs. Early phases of the work have concentrated on design knowledge capture for the Space Station Freedom. Tools are demonstrated and extended which helps automate and document engineering trade studies, and another tool is being developed to help designers interactively explore design alternatives and constraints.

High density bit transition requirements versus the effects on BCH error correcting code. [bit synchronization

NASA Technical Reports Server (NTRS)

Ingels, F. M.; Schoggen, W. O.

1982-01-01

The design to achieve the required bit transition density for the Space Shuttle high rate multiplexes (HRM) data stream of the Space Laboratory Vehicle is reviewed. It contained a recommended circuit approach, specified the pseudo random (PN) sequence to be used and detailed the properties of the sequence. Calculations showing the probability of failing to meet the required transition density were included. A computer simulation of the data stream and PN cover sequence was provided. All worst case situations were simulated and the bit transition density exceeded that required. The Preliminary Design Review and the critical Design Review are documented. The Cover Sequence Generator (CSG) Encoder/Decoder design was constructed and demonstrated. The demonstrations were successful. All HRM and HRDM units incorporate the CSG encoder or CSG decoder as appropriate.

Research Grants Guidance and Policies

EPA Pesticide Factsheets

These pages are designed to assist prospective applicants as well as recent recipients by conveying key documents that describe the quality assurance, reporting requirements, forms, and FAQs for the NCER STAR grant application and implementation process.

ATMS concept of operations and generic system requirements : task B : final interim report for design of support systems for advanced traffic management systems

DOT National Transportation Integrated Search

1993-10-01

This document describes the Concept of Operations and Generic System Requirements for : the next generation of Traffic Management Centers (TMC). Four major steps comprise the : development of this Concept of Operations. The first step was to survey t...

Transport systems research vehicle color display system operations manual

NASA Technical Reports Server (NTRS)

Easley, Wesley C.; Johnson, Larry E.

1989-01-01

A recent upgrade of the Transport Systems Research Vehicle operated by the Advanced Transport Operating Systems Program Office at the NASA Langley Research Center has resulted in an all-glass panel in the research flight deck. Eight ARINC-D size CRT color displays make up the panel. A major goal of the display upgrade effort was ease of operation and maintenance of the hardware while maintaining versatility needed for flight research. Software is the key to this required versatility and will be the area demanding the most detailed technical design expertise. This document is is intended to serve as a single source of quick reference information needed for routine operation and system level maintenance. Detailed maintenance and modification of the display system will require specific design documentation and must be accomplished by individuals with specialized knowledge and experience.

75 FR 36069 - Notice of a Regional Project Waiver of Section 1605 (Buy American) of the American Recovery and...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-06-24

... design engineer. The supporting documentation and independent research and communication with select... constraints involved with the proposed project. For example, one of the design requirements noted by the City..., 5 Post Office Square, Suite 100, Boston, MA 02109-3912. SUPPLEMENTARY INFORMATION: In accordance...

National Occupational Skill Standards. CADD: Computer Aided Drafting and Design.

ERIC Educational Resources Information Center

National Coalition for Advanced Manufacturing, Washington, DC.

This document identifies computer-aided drafting and design (CADD) skills that companies require of training programs and future employees. The information was developed by two committees of technically knowledgeable CADD users from across the United States and validated by several hundred other CADD users. The skills are aimed at a beginner CADD…

OMEGA time transmissions and receiver design.

NASA Technical Reports Server (NTRS)

Chi, A. R.; Fletcher, L. A.; Casselman, C. J.

1972-01-01

This document gives a short history of the development of dual VLF time-transmission technique. The theory of time recovery from the relative phase of the dual-frequency transmission is presented. The transmission and receiving requirements for cycle identification and cycle ambiguity resolution are described. Finally, a prototype OMEGA timing receiving design is described.

E-ELT requirements management

NASA Astrophysics Data System (ADS)

Schneller, D.

2014-08-01

The E-ELT has completed its design phase and is now entering construction. ESO is acting as prime contractor and usually procures subsystems, including their design, from industry. This, in turn, leads to a large number of requirements, whose validity, consistency and conformity with user needs requires extensive management. Therefore E-ELT Systems Engineering has chosen to follow a systematic approach, based on a reasoned requirement architecture that follows the product breakdown structure of the observatory. The challenge ahead is the controlled flow-down of science user needs into engineering requirements, requirement specifications and system design documents. This paper shows how the E-ELT project manages this. The project has adopted IBM DOORTM as a supporting requirements management tool. This paper deals with emerging problems and pictures potential solutions. It shows trade-offs made to reach a proper balance between the effort put in this activity and potential overheads, and the benefit for the project.

Virtual workstations and telepresence interfaces: Design accommodations and prototypes for Space Station Freedom evolution

NASA Technical Reports Server (NTRS)

Mcgreevy, Michael W.

1990-01-01

An advanced human-system interface is being developed for evolutionary Space Station Freedom as part of the NASA Office of Space Station (OSS) Advanced Development Program. The human-system interface is based on body-pointed display and control devices. The project will identify and document the design accommodations ('hooks and scars') required to support virtual workstations and telepresence interfaces, and prototype interface systems will be built, evaluated, and refined. The project is a joint enterprise of Marquette University, Astronautics Corporation of America (ACA), and NASA's ARC. The project team is working with NASA's JSC and McDonnell Douglas Astronautics Company (the Work Package contractor) to ensure that the project is consistent with space station user requirements and program constraints. Documentation describing design accommodations and tradeoffs will be provided to OSS, JSC, and McDonnell Douglas, and prototype interface devices will be delivered to ARC and JSC. ACA intends to commercialize derivatives of the interface for use with computer systems developed for scientific visualization and system simulation.

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

NASA Technical Reports Server (NTRS)

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

2001-01-01

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

Reliability program requirements for aeronautical and space system contractors

NASA Technical Reports Server (NTRS)

1987-01-01

General reliability program requirements for NASA contracts involving the design, development, fabrication, test, and/or use of aeronautical and space systems including critical ground support equipment are prescribed. The reliability program requirements require (1) thorough planning and effective management of the reliability effort; (2) definition of the major reliability tasks and their place as an integral part of the design and development process; (3) planning and evaluating the reliability of the system and its elements (including effects of software interfaces) through a program of analysis, review, and test; and (4) timely status indication by formal documentation and other reporting to facilitate control of the reliability program.

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

High-level waste tank farm set point document

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

Anthony, J.A. III

1995-01-15

Setpoints for nuclear safety-related instrumentation are required for actions determined by the design authorization basis. Minimum requirements need to be established for assuring that setpoints are established and held within specified limits. This document establishes the controlling methodology for changing setpoints of all classifications. The instrumentation under consideration involve the transfer, storage, and volume reduction of radioactive liquid waste in the F- and H-Area High-Level Radioactive Waste Tank Farms. The setpoint document will encompass the PROCESS AREA listed in the Safety Analysis Report (SAR) (DPSTSA-200-10 Sup 18) which includes the diversion box HDB-8 facility. In addition to the PROCESS AREASmore » listed in the SAR, Building 299-H and the Effluent Transfer Facility (ETF) are also included in the scope.« less

BRD usability requirements

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

Deshpande, Alina

2015-03-12

This document describes the usability requirements for the Biosurveillance resource directory (BRD); that is, who will be using the tool and what tasks they will be using it for. It does not include information on technical implementation (e.g., whether specific information is contained in the database or pulled on demand from other sources). It also avoids specific design ideas (such as widget descriptions) unless they are necessary to illustrate a requirement.

Operational Concepts for a Generic Space Exploration Communication Network Architecture

NASA Technical Reports Server (NTRS)

Ivancic, William D.; Vaden, Karl R.; Jones, Robert E.; Roberts, Anthony M.

2015-01-01

This document is one of three. It describes the Operational Concept (OpsCon) for a generic space exploration communication architecture. The purpose of this particular document is to identify communication flows and data types. Two other documents accompany this document, a security policy profile and a communication architecture document. The operational concepts should be read first followed by the security policy profile and then the architecture document. The overall goal is to design a generic space exploration communication network architecture that is affordable, deployable, maintainable, securable, evolvable, reliable, and adaptable. The architecture should also require limited reconfiguration throughout system development and deployment. System deployment includes: subsystem development in a factory setting, system integration in a laboratory setting, launch preparation, launch, and deployment and operation in space.

Infusing Stretch Goal Requirements into the Constellation Program

NASA Technical Reports Server (NTRS)

Lee, Young H.; Galpin, Roger A.; Ingoldsby, Kevin

2008-01-01

In 2004, the Vision for Space Exploration (VSE) was announced by the United States President's Administration in an effort to explore space and to extend a human presence across our solar system. Subsequently, the National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop a constellation of new capabilities, supporting technologies, and foundational research that allows for the sustained and affordable exploration of space. Then, ESMD specified the primary mission for the Constellation Program to carry out a series of human expeditions, ranging from Low Earth Orbit (LEO) to the surface of Moon, Mars, and beyond for the purposes of conducting human exploration of space. Thus, the Constellation Program was established at the Lyndon B. Johnson Space Center (JSC) to manage the development of the flight and ground infrastructure and systems that can enable continued and extended human access to space. Constellation Program's "Design Objectives" call for an early attention to the program's life cycle costs management through the Program's Need, Goals, and Objectives (NGO) document, which provides the vision, scope, and key areas of focus for the Program. One general policy of the Constellation Program, found in the Constellation Architecture Requirements Document (CARD), states: "A sustainable program hinges on how effectively total life cycle costs are managed. Developmental costs are a key consideration, but total life cycle costs related to the production, processing, and operation of the entire architecture must be accounted for in design decisions sufficiently to ensure future resources are available for ever more ambitious missions into the solar system....It is the intent of the Constellation Program to aggressively manage this aspect of the program using the design policies and simplicity." To respond to the Program's strong desire to manage the program life cycle costs, special efforts were established to identify operability requirements to influence flight vehicle and ground infrastructure design in order to impact the life cycle operations costs, and stretch goal requirements were introduced to the Program. This paper will describe how these stretch goal requirements were identified, developed, refined, matured, approved, and infused into the CARD. The paper will also document several challenges encountered when infusing the stretch goal requirements into the Constellation Program.

Space station wardroom habitability and equipment study

NASA Technical Reports Server (NTRS)

Nixon, David; Miller, Christopher; Fauquet, Regis

1989-01-01

Experimental designs in life-size mock-up form for the wardroom facility for the Space Station Habitability Module are explored and developed. In Phase 1, three preliminary concepts for the wardroom configuration are fabricated and evaluated. In Phase 2, the results of Phase 1 are combined with a specific range of program design requirements to provide the design criteria for the fabrication of an innovative medium-fidelity mock-up of a wardrobe configuration. The study also focuses on the design and preliminary prototyping of selected equipment items including crew exercise compartments, a meal/meeting table and a portable workstation. Design criteria and requirements are discussed and documented. Preliminary and final mock-ups and equipment prototypes are described and illustrated.

A Stream lined Approach for the Payload Customer in Identifying Payload Design Requirements

NASA Technical Reports Server (NTRS)

Miller, Ladonna J.; Schneider, Walter F.; Johnson, Dexer E.; Roe, Lesa B.

2001-01-01

NASA payload developers from across various disciplines were asked to identify areas where process changes would simplify their task of developing and flying flight hardware. Responses to this query included a central location for consistent hardware design requirements for middeck payloads. The multidisciplinary team assigned to review the numerous payload interface design documents is assessing the Space Shuttle middeck, the SPACEHAB Inc. locker, as well as the MultiPurpose Logistics Module (MPLM) and EXpedite the PRocessing of Experiments to Space Station (EXPRESS) rack design requirements for the payloads. They are comparing the multiple carriers and platform requirements and developing a matrix which illustrates the individual requirements, and where possible, the envelope that encompasses all of the possibilities. The matrix will be expanded to form an overall envelope that the payload developers will have the option to utilize when designing their payload's hardware. This will optimize the flexibility for payload hardware and ancillary items to be manifested on multiple carriers and platforms with minimal impact to the payload developer.

A CMMI-based approach for medical software project life cycle study.

PubMed

Chen, Jui-Jen; Su, Wu-Chen; Wang, Pei-Wen; Yen, Hung-Chi

2013-01-01

In terms of medical techniques, Taiwan has gained international recognition in recent years. However, the medical information system industry in Taiwan is still at a developing stage compared with the software industries in other nations. In addition, systematic development processes are indispensable elements of software development. They can help developers increase their productivity and efficiency and also avoid unnecessary risks arising during the development process. Thus, this paper presents an application of Light-Weight Capability Maturity Model Integration (LW-CMMI) to Chang Gung Medical Research Project (CMRP) in the Nuclear medicine field. This application was intended to integrate user requirements, system design and testing of software development processes into three layers (Domain, Concept and Instance) model. Then, expressing in structural System Modeling Language (SysML) diagrams and converts part of the manual effort necessary for project management maintenance into computational effort, for example: (semi-) automatic delivery of traceability management. In this application, it supports establishing artifacts of "requirement specification document", "project execution plan document", "system design document" and "system test document", and can deliver a prototype of lightweight project management tool on the Nuclear Medicine software project. The results of this application can be a reference for other medical institutions in developing medical information systems and support of project management to achieve the aim of patient safety.

Decal Process Document and Catalog

NASA Technical Reports Server (NTRS)

1999-01-01

The Decal Process Document and Catalog, JSC 27260 is the standard flight decal catalog, complete with illustrations and part numbers. As hardware developers identify labels that have common applicability across end items, these labels can be evaluated for "standard decal classification" and entered into the decal catalog for general use. The hardware developer must have a label design that meets current, applicable labeling requirements, and submit to the Decal Design and Production Facility (DDPF) as a standard label candidate. Upon approval, the label will be added to the decal catalog. The Decal Process Document and Catalog provides a selection of decals from which the NASA and NASA contractor customers can easily order. The decals shown in the catalog have been previously produced and have released engineering/fabrication drawings on file in the (DDPF). A released drawing is required before a decal can be produced or placed into the catalog. Some decals included in the catalog have a common applicability and are used in various NASA vehicles/habitats. It is the intent of the DDPF to maintain this catalog as a "living document" to which decals/placards can be added as they are repeatedly used. The advantage of identifYing flight decals in this catalog is that a released drawing is already in place, and the products will be flight certified.

IPG Job Manager v2.0 Design Documentation

NASA Technical Reports Server (NTRS)

Hu, Chaumin

2003-01-01

This viewgraph presentation provides a high-level design of the IPG Job Manager, and satisfies its Master Requirement Specification v2.0 Revision 1.0, 01/29/2003. The presentation includes a Software Architecture/Functional Overview with the following: Job Model; Job Manager Client/Server Architecture; Job Manager Client (Job Manager Client Class Diagram and Job Manager Client Activity Diagram); Job Manager Server (Job Manager Client Class Diagram and Job Manager Client Activity Diagram); Development Environment; Project Plan; Requirement Traceability.

STOVL Control Integration Program

NASA Technical Reports Server (NTRS)

Weiss, C.; Mcdowell, P.; Watts, S.

1994-01-01

An integrated flight/propulsion control for an advanced vector thrust supersonic STOVL aircraft, was developed by Pratt & Whitney and McDonnell Douglas Aerospace East. The IFPC design was based upon the partitioning of the global requirements into flight control and propulsion control requirements. To validate the design, aircraft and engine models were also developed for use on a NASA Ames piloted simulator. Different flight control implementations, evaluated for their handling qualities, are documented in the report along with the propulsion control, engine model, and aircraft model.

Optical Property Requirements for Glasses, Ceramics and Plastics in Spacecraft Window Systems

NASA Technical Reports Server (NTRS)

Estes, Lynda

2011-01-01

This is a preliminary draft of a standard published by the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) that is intended to provide uniform window optical design requirements in support of the development of human-rated spaceflight hardware. The material covered in this standard is based on data from extensive testing by the Advanced Sensing and Optical Measurement Branch at NASA Langley Research Center, and compiled into requirements format by the NASA JSC Structural Engineering Division. At the time of this initial document release, a broader technical community has not reviewed this standard. The technical content of this standard is primarily based on the Constellation Program Orion Crew Exploration Vehicle Window Optical Properties Requirements, CxP 72407, Baseline. Unlike other optical requirements documents available for human rated spacecraft, this document includes requirements that ensure functionality for windows that contain glass/ceramic and/or plastic window substrate materials. These requirements were derived by measuring the optical properties of fused silica and aluminosilicate glass window assemblies and ensuring that the performance of any window assembly that includes a plastic pane or panes will meet the performance level of the all-glass assemblies. The resulting requirements are based upon the performance and parameter metrology testing of a variety of materials, including glass, transparent ceramics, acrylics, and polycarbonates. In general, these requirements are minimum specifications for each optical parameter in order to achieve the function specified for each functional category, A through D. Because acrylic materials perform at a higher level than polycarbonates in the optics regime, and CxP/Orion is planning to use acrylic in the Orion spacecraft, these requirements are based heavily on metrology from that material. As a result, two of the current Category D requirements for plastics are cited in such a way that will result in the screening out of polycarbonates. It is acknowledged that many polycarbonates can perform the functions of Category D, such as piloting and imagery with lens with apertures up to 25mm, without performance issues. Therefore, this forward warns users that certain requirements, such as birefringence and wavefront, for Category D plastics need to be revised to allow those polycarbonates that perform adequately in Category D to be accepted, while at the same time, screen out those materials that do not perform up to par. At the time of document release, the requirements in question have been identified by a TBD beside the proposed requirement criteria (which is based upon acrylic performance). Vehicles that are designed with acrylic materials for windowpanes are encouraged to use the values presented in this document for all requirements, in order to ensure adequate optical performance.

Design Manual: Removal of Fluoride from Drinking Water ...

EPA Pesticide Factsheets

This document is an updated version of the Design Manual: Removal of Fluoride from Drinking Water Supplies by Activated Alumina (Rubel, 1984). The manual is an in-depth presentation of the steps required to design and operate a fluoride removal plant using activated alumina (AA), which is a reliable and cost-effective process for treating excess fluoride from drinking water supplies. Design Manual on removing fluoride from drinking water to support the fluoride MCL - manual

Ultraviolet Free Electron Laser Facility preliminary design report

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

Ben-Zvi, I.

1993-02-01

This document, the Preliminary Design Report (PDR) for the Brookhaven Ultraviolet Free Electron Laser (UV FEL) facility, describes all the elements of a facility proposed to meet the needs of a research community which requires ultraviolet sources not currently available as laboratory based lasers. Further, for these experiments, the requisite properties are not extant in either the existing second or upcoming third generation synchrotron light sources. This document is the result of our effort at BNL to identify potential users, determine the requirements of their experiments, and to design a facility which can not only satisfy the existing need, butmore » have adequate flexibility for possible future extensions as need dictates and as evolving technology allows. The PDR is comprised of three volumes. In this, the first volume, background for the development of the proposal is given, including descriptions of the UV FEL facility, and representative examples of the science it was designed to perform. Discussion of the limitations and potential directions for growth are also included. A detailed description of the facility design is then provided, which addresses the accelerator, optical, and experimental systems. Information regarding the conventional construction for the facility is contained in an addendum to volume one (IA).« less

Energy Modeling for the Artisan Food Center

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

Goel, Supriya

2013-05-01

The Artisan Food Center is a 6912 sq.ft food processing plant located in Dayton, Washington. PNNL was contacted by Strecker Engineering to assist with the building’s energy analysis as a part of the project’s U.S. Green Building Council’s Leadership in Energy and Environmental Design (LEED) submittal requirements. The project is aiming for LEED Silver certification, one of the prerequisites to which is a whole building energy model to demonstrate compliance with American Society of Heating Refrigeration and Air Conditioning Engineers (ASHRAE) 90.1 2007 Appendix G, Performance Rating Method. The building incorporates a number of energy efficiency measures as part ofmore » its design and the energy analysis aimed at providing Strecker Engineering with the know-how of developing an energy model for the project as well as an estimate of energy savings of the proposed design over the baseline design, which could be used to document points in the LEED documentation. This report documents the ASHRAE 90.1 2007 baseline model design, the proposed model design, the modeling assumptions and procedures as well as the energy savings results in order to inform the Strecker Engineering team on a possible whole building energy model.« less

Large Bore Powder Gun Qualification (U)

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

Rabern, Donald A.; Valdiviez, Robert

A Large Bore Powder Gun (LBPG) is being designed to enable experimentalists to characterize material behavior outside the capabilities of the NNSS JASPER and LANL TA-55 PF-4 guns. The combination of these three guns will create a capability to conduct impact experiments over a wide range of pressures and shock profiles. The Large Bore Powder Gun will be fielded at the Nevada National Security Site (NNSS) U1a Complex. The Complex is nearly 1000 ft below ground with dedicated drifts for testing, instrumentation, and post-shot entombment. To ensure the reliability, safety, and performance of the LBPG, a qualification plan has beenmore » established and documented here. Requirements for the LBPG have been established and documented in WE-14-TR-0065 U A, Large Bore Powder Gun Customer Requirements. The document includes the requirements for the physics experiments, the gun and confinement systems, and operations at NNSS. A detailed description of the requirements is established in that document and is referred to and quoted throughout this document. Two Gun and Confinement Systems will be fielded. The Prototype Gun will be used primarily to characterize the gun and confinement performance and be the primary platform for qualification actions. This gun will also be used to investigate and qualify target and diagnostic modifications through the life of the program (U1a.104 Drift). An identical gun, the Physics Gun, will be fielded for confirmatory and Pu experiments (U1a.102D Drift). Both guns will be qualified for operation. The Gun and Confinement System design will be qualified through analysis, inspection, and testing using the Prototype Gun for the majority of process. The Physics Gun will be qualified through inspection and a limited number of qualification tests to ensure performance and behavior equivalent to the Prototype gun. Figure 1.1 shows the partial configuration of U1a and the locations of the Prototype and Physics Gun/Confinement Systems.« less

Thermal/Structural Tailoring of Engine Blades (T/STAEBL) User's manual

NASA Technical Reports Server (NTRS)

Brown, K. W.

1994-01-01

The Thermal/Structural Tailoring of Engine Blades (T/STAEBL) system is a computer code that is able to perform numerical optimizations of cooled jet engine turbine blades and vanes. These optimizations seek an airfoil design of minimum operating cost that satisfies realistic design constraints. This report documents the organization of the T/STAEBL computer program, its design and analysis procedure, its optimization procedure, and provides an overview of the input required to run the program, as well as the computer resources required for its effective use. Additionally, usage of the program is demonstrated through a validation test case.

Thermal/Structural Tailoring of Engine Blades (T/STAEBL): User's manual

NASA Astrophysics Data System (ADS)

Brown, K. W.

1994-03-01

The Thermal/Structural Tailoring of Engine Blades (T/STAEBL) system is a computer code that is able to perform numerical optimizations of cooled jet engine turbine blades and vanes. These optimizations seek an airfoil design of minimum operating cost that satisfies realistic design constraints. This report documents the organization of the T/STAEBL computer program, its design and analysis procedure, its optimization procedure, and provides an overview of the input required to run the program, as well as the computer resources required for its effective use. Additionally, usage of the program is demonstrated through a validation test case.

38 CFR 39.6 - Preapplication requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... documentation, as needed). (4) A design concept describing the major features of the project including the... that alter the costs of the project, use of space, or functional layout; and it will not enter into a...

Research Grants Guidance and Policies Resources

EPA Pesticide Factsheets

These pages are designed to assist prospective applicants as well as recent recipients by conveying key documents that describe the quality assurance, reporting requirements, forms, and FAQs for the NCER STAR grant application and implementation process.

Design and development of a structural mode control system

NASA Technical Reports Server (NTRS)

1977-01-01

A program was conducted to compile and document some of the existing information about the conceptual design, development, and tests of the B-1 structural mode control system (SMCS) and its impact on ride quality. This report covers the following topics: (1) Rationale of selection of SMCS to meet ride quality criteria versus basic aircraft stiffening. (2) Key considerations in designing an SMCS, including vane geometry, rate and deflection requirements, power required, compensation network design, and fail-safe requirements. (3) Summary of key results of SMCS vane wind tunnel tests. (4) SMCS performance. (5) SMCS design details, including materials, bearings, and actuators. (6) Results of qualification testing of SMCS on the "Iron Bird" flight control simulator, and lab qualification testing of the actuators. (7) Impact of SMCS vanes on engine inlet characteristics from wind tunnel tests.

Water Processor and Oxygen Generation Assembly

NASA Technical Reports Server (NTRS)

Bedard, John

1997-01-01

This report documents the results of the tasks which initiated efforts on design issues relating to the Water Processor (WP) and the Oxygen Generation Assembly (OGA) Flight Hardware for the International Space Station. This report fulfills the Statement of Work deliverables requirement for contract H-29387D. The following lists the tasks required by contract H-29387D: (1) HSSSI shall coordinate a detailed review of WP/OGA Flight Hardware program requirements with personnel from MSFC to identify requirements that can be eliminated without affecting the technical integrity of the WP/OGA Hardware; (2) HSSSI shall conduct the technical interchanges with personnel from MSFC to resolve design issues related to WP/OGA Flight Hardware; (3) HSSSI will initiate discussions with Zellwegger Analytics, Inc. to address design issues related to WP and PCWQM interfaces.

Requirements for soldered electrical connections

NASA Technical Reports Server (NTRS)

1992-01-01

This publication is applicable to NASA programs involving solder connections for flight hardware, mission essential support equipment, and elements thereof. This publication sets forth hand and wave soldering requirements for reliable electrical connections. The prime consideration is the physical integrity of solder connections. Special requirements may exist which are not in conformance with the requirements of this publication. Design documentation contains the detail for these requirements, and they take precedence over conflicting portions of this publication when they are approved in writing by the procuring NASA installation.

Fume Cupboards in Schools. (Revision of Design Note 29). Building Bulletin 88.

ERIC Educational Resources Information Center

Tawney, David

Regulations require hazardous gases in school science classrooms to be controlled, i.e., their levels in the air kept below the exposure limits, with fume cupboards being the most usual method. This document reviews the requirements for fume cupboards used in schools and colleges for teaching the sciences, mainly chemistry and biology, up to…

40 CFR Table 5 to Subpart Llll of... - Summary of Reporting Requirements for New Sewage Sludge Incineration Units a

Code of Federal Regulations, 2013 CFR

2013-07-01

.... Documentation for siting requirements. 4. Anticipated date of initial startup. § 60.4915(a). Notification of initial startup Prior to initial startup 1. Maximum design dry sewage sludge burning capacity2.... 4. Anticipated date of initial startup. 5. Site-specific monitoring plan. 6. The site-specific...

40 CFR Table 5 to Subpart Llll of... - Summary of Reporting Requirements for New Sewage Sludge Incineration Units a

Code of Federal Regulations, 2014 CFR

2014-07-01

.... Documentation for siting requirements. 4. Anticipated date of initial startup. § 60.4915(a). Notification of initial startup Prior to initial startup 1. Maximum design dry sewage sludge burning capacity2.... 4. Anticipated date of initial startup. 5. Site-specific monitoring plan. 6. The site-specific...

Work-Based Learning: Learning To Work; Working To Learn; Learning To Learn.

ERIC Educational Resources Information Center

Strumpf, Lori; Mains, Kristine

This document describes a work-based learning approach designed to integrate work and learning at the workplace and thereby help young people develop the skills required for changing workplaces. The following considerations in designing work-based programs are discussed: the trend toward high performance workplaces and changes in the way work is…

Preliminary design document: Ground based testbed for avionics systems

NASA Technical Reports Server (NTRS)

1989-01-01

The design and interface requirements for an avionics Ground Based Test bed (GBT) to support Heavy Lift Cargo Vehicles (HLCV) is presented. It also contains data on the vehicle subsystem configurations that are to be supported during their early, pre-PDR developmental phases. Several emerging technologies are also identified for support. A Preliminary Specification Tree is also presented.

Low resolution radar digital interface. [with data recorder for precipitation measurements

NASA Technical Reports Server (NTRS)

1973-01-01

This document describes the design and operation of a low resolution radar data recording system for precipitation measurements. This system records a full azimuth scan on seven track magnetic tapes every five minutes. It is designed to operate on a continuous basis with operator intervention required only for changing tape reels and calibration.

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision D

NASA Technical Reports Server (NTRS)

Roberts, Barry C.

2015-01-01

This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.

Data Quality Objectives for Tank Farms Waste Compatibility Program

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

BANNING, D.L.

1999-07-02

There are 177 waste storage tanks containing over 210,000 m{sup 3} (55 million gal) of mixed waste at the Hanford Site. The River Protection Project (RPP) has adopted the data quality objective (DQO) process used by the U.S. Environmental Protection Agency (EPA) (EPA 1994a) and implemented by RPP internal procedure (Banning 1999a) to identify the information and data needed to address safety issues. This DQO document is based on several documents that provide the technical basis for inputs and decision/action levels used to develop the decision rules that evaluate the transfer of wastes. A number of these documents are presentlymore » in the process of being revised. This document will need to be revised if there are changes to the technical criteria in these supporting documents. This DQO process supports various documents, such as sampling and analysis plans and double-shell tank (DST) waste analysis plans. This document identifies the type, quality, and quantity of data needed to determine whether transfer of supernatant can be performed safely. The requirements in this document are designed to prevent the mixing of incompatible waste as defined in Washington Administrative Code (WAC) 173-303-040. Waste transfers which meet the requirements contained in this document and the Double-Shell Tank Waste Analysis Plan (Mulkey 1998) are considered to be compatible, and prevent the mixing of incompatible waste.« less

Development and Verification of Body Armor Target Geometry Created Using Computed Tomography Scans

DTIC Science & Technology

2017-07-13

designated by other authorized documents. Citation of manufacturer’s or trade names does not constitute an official endorsement or approval of...modeling consisted of manual measurement of armor systems and translating those measurements to computer-aided design geometry, which can be tedious and...computer-aided design (CAD) human geometry model (referred to throughout as ORCA man) that is used in the Operational Requirement-based Casualty Assessment

50% Advanced Energy Design Guides: Preprint

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

Bonnema, E.; Leach, M.; Pless, S.

2012-07-01

This paper presents the process, methodology, and assumptions for the development of the 50% Energy Savings Advanced Energy Design Guides (AEDGs), a design guidance document that provides specific recommendations for achieving 50% energy savings above the requirements of ANSI/ASHRAE/IESNA Standard 90.1-2004 in four building types: (1) Small to medium office buildings, (2) K-12 school buildings, (3) Medium to big box retail buildings, (4) Large hospital buildings.

2015 Revision to 2008 Ozone National Ambient Air Quality Standards (NAAQS) Related Documents

EPA Pesticide Factsheets

Find tools for background ozone, maps of nonattainment areas, an overview of the proposal, and information on designations, monitoring and permitting requirements and a presentation on the 2015 ozone NAAQS revision.

40 CFR 80.1454 - What are the recordkeeping requirements under the RFS program?

Code of Federal Regulations, 2010 CFR

2010-07-01

..., or heating oil without further blending, in the designated form. (6) Copies of registration documents...-fossil fraction of fuel made from separated municipal solid waste. (iv) Such other records as may be...

Superfund Hazard Ranking System Training Course

EPA Pesticide Factsheets

The Hazard Ranking System (HRS) training course is a four and ½ day, intermediate-level course designed for personnel who are required to compile, draft, and review preliminary assessments (PAs), site inspections (SIs), and HRS documentation records/packag

Design review report for rotary mode core sample truck (RMCST) modifications for flammable gas tanks, preliminary design

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

Corbett, J.E.

1996-02-01

This report documents the completion of a preliminary design review for the Rotary Mode Core Sample Truck (RMCST) modifications for flammable gas tanks. The RMCST modifications are intended to support core sampling operations in waste tanks requiring flammable gas controls. The objective of this review was to validate basic design assumptions and concepts to support a path forward leading to a final design. The conclusion reached by the review committee was that the design was acceptable and efforts should continue toward a final design review.

Space station definition and preliminary design, WP-01. Volume 2: Results

NASA Technical Reports Server (NTRS)

Lenda, J. A.

1987-01-01

The basis for the studies and analyses which led to the results and conclusions documented and summarized, was the Engineering Master Schedule (EMS) generated by NASA and used as the controlling set of milestones and associated activities required to produce in a timely manner those products needed by all program participants in the establishment of an approved program baseline. The EMS consisted of twenty themes grouped into categories covering requirements, configurations, and strategies. A number of studies and analyses that were coordinated with the MSFC program and technical personnel as being needed to provide the requisite back-up material to satify the EMS were identified. These studies and analyses provided the data sufficient to support the conclusions and recommendations given to the MSFC in response to their EMS activity and to support the system level and conceptual design level approaches developed and reflected in the detailed sections of this document.

Coupled optical/thermal/fluid analysis and design requirements for operation and testing of a supercritical CO 2 solar receiver.

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

Khivsara, Sagar

Recent studies have evaluated closed-loop supercritical carbon dioxide (s-CO 2) Brayton cycles to be a higher energy-density system in comparison to conventional superheated steam Rankine systems. At turbine inlet conditions of 923K and 25 MPa, high thermal efficiency (~50%) can be achieved. Achieving these high efficiencies will make concentrating solar power (CSP) technologies a competitive alternative to current power generation methods. To incorporate a s-CO 2 Brayton power cycle in a solar power tower system, the development of a solar receiver capable of providing an outlet temperature of 923 K (at 25 MPa) is necessary. To satisfy the temperature requirementsmore » of a s-CO 2 Brayton cycle with recuperation and recompression, it is required to heat s-CO 2 by a temperature of ~200 K as it passes through the solar receiver. Our objective was to develop an optical-thermal-fluid model to design and evaluate a tubular receiver that will receive a heat input ~1 MWth from a heliostat field. We also undertook the documentation of design requirements for the development, testing and safe operation of a direct s-CO 2 solar receiver. The main purpose of this document is to serve as a reference and guideline for design and testing requirements, as well as to address the technical challenges and provide initial parameters for the computational models that will be employed for the development of s-CO 2 receivers.« less

Automated Visibility Measurements with a Horizon Scanning Imager. Volume 1. Technical Discussion

DTIC Science & Technology

1990-12-01

environment, if one difficult. In the case of many relatively simplistic "rule assumes that the measured values of Cr are consistently following...report unless contractual obligations or notices on a specific document requires that it be returned. REPORT DOCUMENTATION PAGE Approved OMB No. 0704-0188...control computer from the original Zenith Z-248 incentive being that the sooner one identifies the class desktop to the Texas Micro Systems (TMI) design

A Polyamine Oxidizing Enzyme as a Drug to Treat Breast Cancer

DTIC Science & Technology

2008-07-01

construed as an official Department of the Army position , policy or decision unless so designated by other documentation. REPORT DOCUMENTATION...polysac- charides. The polysaccharides are required for SAO to act a vascular adhesion protein-1 ( VAP -1) (6). If the polysaccharides are not block on...SAO, when injected into the blood of test mice, it may interfere with the endogenous VAP -1. In addition, a low-level PEGylation probably will not

Project Quality Assurance Plan for research and development services provided by Oak Ridge National Laboratory in support of the Westinghouse Materials Company of Ohio Operable Unit 1 Stabilization Development and Treatability Studies Program

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

Gilliam, T.M.

1991-05-01

This Project Quality Assurance Plan (PQAP) sets forth the quality assurance (QA) requirements that are applied to those elements of the Westinghouse Materials Company of Ohio (WMCO) Operable Unit 1 support at Oak Ridge National Laboratory (ORNL) project that involve research and development (R D) performed at ORNL. This is in compliance with the applicable criteria of 10 CFR Part 50, Appendix B, ANSI/ASME NQA-1, as specified by Department of Energy (DOE) Oak Ridge Operations (ORO) Order 5700.6B. For this application, NQA-1 is the core QA Program requirements document. QA policy, normally found in the requirements document, is contained herein.more » The requirements of this PQAP apply to project activities that affect the quality and reliability/credibility of research, development, and investigative data and documentation. These activities include the functions of attaining quality objectives and assuring that an appropriate QA program scope is established. The scope of activities affecting quality includes organization; personnel training and qualifications; design control; procurement; material handling and storage; operating procedures; testing, surveillance, and auditing; R D investigative activities and documentation; deficiencies; corrective actions; and QA record keeping. 12 figs.« less

A review of the FDA draft guidance document for software validation: guidance for industry.

PubMed

Keatley, K L

1999-01-01

A Draft Guidance Document (Version 1.1) was issued by the United States Food and Drug Administration (FDA) to address the software validation requirement of the Quality System Regulation, 21 CFR Part 820, effective June 1, 1997. The guidance document outlines validation considerations that the FDA regards as applicable to both medical device software and software used to "design, develop or manufacture" medical devices. The Draft Guidance is available at the FDA web site http:@www.fda.gov/cdrh/comps/swareval++ +.html. Presented here is a review of the main features of the FDA document for Quality System Regulation (QSR), and some guidance for its implementation in industry.

Waste Package Component Design Methodology Report

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

D.C. Mecham

2004-07-12

This Executive Summary provides an overview of the methodology being used by the Yucca Mountain Project (YMP) to design waste packages and ancillary components. This summary information is intended for readers with general interest, but also provides technical readers a general framework surrounding a variety of technical details provided in the main body of the report. The purpose of this report is to document and ensure appropriate design methods are used in the design of waste packages and ancillary components (the drip shields and emplacement pallets). The methodology includes identification of necessary design inputs, justification of design assumptions, and usemore » of appropriate analysis methods, and computational tools. This design work is subject to ''Quality Assurance Requirements and Description''. The document is primarily intended for internal use and technical guidance for a variety of design activities. It is recognized that a wide audience including project management, the U.S. Department of Energy (DOE), the U.S. Nuclear Regulatory Commission, and others are interested to various levels of detail in the design methods and therefore covers a wide range of topics at varying levels of detail. Due to the preliminary nature of the design, readers can expect to encounter varied levels of detail in the body of the report. It is expected that technical information used as input to design documents will be verified and taken from the latest versions of reference sources given herein. This revision of the methodology report has evolved with changes in the waste package, drip shield, and emplacement pallet designs over many years and may be further revised as the design is finalized. Different components and analyses are at different stages of development. Some parts of the report are detailed, while other less detailed parts are likely to undergo further refinement. The design methodology is intended to provide designs that satisfy the safety and operational requirements of the YMP. Four waste package configurations have been selected to illustrate the application of the methodology during the licensing process. These four configurations are the 21-pressurized water reactor absorber plate waste package (21-PWRAP), the 44-boiling water reactor waste package (44-BWR), the 5 defense high-level radioactive waste (HLW) DOE spent nuclear fuel (SNF) codisposal short waste package (5-DHLWDOE SNF Short), and the naval canistered SNF long waste package (Naval SNF Long). Design work for the other six waste packages will be completed at a later date using the same design methodology. These include the 24-boiling water reactor waste package (24-BWR), the 21-pressurized water reactor control rod waste package (21-PWRCR), the 12-pressurized water reactor waste package (12-PWR), the 5 defense HLW DOE SNF codisposal long waste package (5-DHLWDOE SNF Long), the 2 defense HLW DOE SNF codisposal waste package (2-MC012-DHLW), and the naval canistered SNF short waste package (Naval SNF Short). This report is only part of the complete design description. Other reports related to the design include the design reports, the waste package system description documents, manufacturing specifications, and numerous documents for the many detailed calculations. The relationships between this report and other design documents are shown in Figure 1.« less

Leo Spacecraft Charging Design Guidelines: A Proposed NASA Standard

NASA Technical Reports Server (NTRS)

Hillard, G. B.; Ferguson, D. C.

2004-01-01

Over the past decade, Low Earth Orbiting (LEO) spacecraft have gradually required ever-increasing power levels. As a rule, this has been accomplished through the use of high voltage systems. Recent failures and anomalies on such spacecraft have been traced to various design practices and materials choices related to the high voltage solar arrays. NASA Glenn has studied these anomalies including plasma chamber testing on arrays similar to those that experienced difficulties on orbit. Many others in the community have been involved in a comprehensive effort to understand the problems and to develop practices to avoid them. The NASA Space Environments and Effects program, recognizing the timeliness of this effort, commissioned and funded a design guidelines document intended to capture the current state of understanding. This document, which was completed in the spring of 2003, has been submitted as a proposed NASA standard. We present here an overview of this document and discuss the effort to develop it as a NASA standard.

NASA preferred reliability-practices for design and test

NASA Technical Reports Server (NTRS)

Lisk, Ronald C.

1992-01-01

NASA HQ established the NASA R&M Steering Committee (R&MSC) comprised of membership from each NASA field center. The primary charter of the R&MSC is to obtain, record, and share the best design practices that NASA has applied to successful space flight programs and current design considerations (guidelines) that should enhance flight reliability on emerging programs. The practices and guidelines are being assembled in a living document for distribution to NASA centers and the aerospace community. The document will be updated annually with additional practices and guidelines as contributions from the centers are reviewed and approved by the R&MSC. Practices and guidelines are not requirements, but rather a means of sharing procedures and techniques that a given center and the R&MSC together feel have strong technical merit and application to the design of space-related equipment.

A framework for developing research protocols for evaluation of microbial hazards and controls during production that pertain to the quality of agricultural water contacting fresh produce that may be consumed raw.

PubMed

Harris, Linda J; Bender, Jeff; Bihn, Elizabeth A; Blessington, Tyann; Danyluk, Michelle D; Delaquis, Pascal; Goodridge, Lawrence; Ibekwe, A Mark; Ilic, Sanja; Kniel, Kali; Lejeune, Jeffrey T; Schaffner, Donald W; Stoeckel, Don; Suslow, Trevor V

2012-12-01

Agricultural water may contact fresh produce during irrigation and/or when crop protection sprays (e.g., cooling to prevent sunburn, frost protection, and agrochemical mixtures) are applied. This document provides a framework for designing research studies that would add to our understanding of preharvest microbial food safety hazards and control measures pertaining to agricultural water. Researchers will be able to use this document to design studies, to anticipate the scope and detail of data required, and to evaluate previously published work. This document should also be useful for evaluating the strength of existing data and thus should aid in identifying future research needs. Use of this document by the research community may lead to greater consistency or comparability than currently exists among research studies, which may ultimately facilitate direct comparison of hazards and efficacy of controls among different commodities, conditions, and practices.

Poster - 28: Shielding of X-ray Rooms in Ontario in the Absence of Best Practice

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

Frimeth, Jeff; Richer, Jeff; Nesbitt, James

This poster will be strictly based on the Healing Arts Radiation Protection (HARP) Act, Regulation 543 under this Act (X-ray Safety Code), and personal communication the presenting author has had. In Ontario, the process of approval of an X-ray machine installation by the Director of the X-ray Inspection Service (XRIS) follows a certain protocol. Initially, the applicant submits a series of forms, including recommended shielding amounts, in order to satisfy the law. This documentation is then transferred to a third-party vendor (i.e. a professional engineer – P.Eng.) outsourced by the Ministry of Health and Long-term Care (MOHLTC). The P.Eng. thenmore » evaluates the submitted documentation for appropriate fulfillment of the HARP Act and Reg. 543 requirements. If the P.Eng.’s evaluation of the documentation is to their satisfaction, the XRIS is then notified. Finally, the Director will then issue a letter of approval to install the equipment at the facility. The methodology required to be used by the P.Eng. in order to determine the required amounts of protective barriers, and recommended to be used by the applicant, is contained within Safety Code 20A. However, Safety Code 35 has replaced the obsolete Safety Code 20A document and employs best practices in shielding design. This talk will focus further on specific intentions and limitations of Safety Code 20A. Furthermore, this talk will discuss the definition of the “practice of professional engineering” in Ontario. COMP members who are involved in shielding design are strongly encouraged to attend.« less

Safety policy and requirements for payloads using the Space Transportation System (STS)

NASA Technical Reports Server (NTRS)

1982-01-01

The Space Transportation Operations (STO) safety policy is to minimize STO involvement in the payload and its GSE (ground support equipment) design process while maintaining the assurance of a safe operation. Requirements for assuring payload mission success are the responsibility of the payload organization and are beyond the scope of this document. The intent is to provide the overall safety policies and requirements while allowing for negotiation between the payload organization and the STO operator in the method of implementation of payload safety. This revision provides for a relaxation in the monitoring requirements for inhibits, allows the payload organization to pursue design options and reflects, additionally, some new requirements. As of the issue date of this NHB, payloads which have completed the formal safety assessment reviews of their preliminary design on the basis of the May 1979 issue will be reassessed for compliance with the above changes.

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.

Equipment concept design and development plans for microgravity science and applications research on space station: Combustion tunnel, laser diagnostic system, advanced modular furnace, integrated electronics laboratory

NASA Technical Reports Server (NTRS)

Uhran, M. L.; Youngblood, W. W.; Georgekutty, T.; Fiske, M. R.; Wear, W. O.

1986-01-01

Taking advantage of the microgravity environment of space NASA has initiated the preliminary design of a permanently manned space station that will support technological advances in process science and stimulate the development of new and improved materials having applications across the commercial spectrum. Previous studies have been performed to define from the researcher's perspective, the requirements for laboratory equipment to accommodate microgravity experiments on the space station. Functional requirements for the identified experimental apparatus and support equipment were determined. From these hardware requirements, several items were selected for concept designs and subsequent formulation of development plans. This report documents the concept designs and development plans for two items of experiment apparatus - the Combustion Tunnel and the Advanced Modular Furnace, and two items of support equipment the Laser Diagnostic System and the Integrated Electronics Laboratory. For each concept design, key technology developments were identified that are required to enable or enhance the development of the respective hardware.

Application of the Hardman methodology to the Army Remotely Piloted Vehicle (RPV)

NASA Technical Reports Server (NTRS)

1983-01-01

The application of the HARDMAN Methodology to the Remotely Piloted Vehicle (RPV) is described. The methodology was used to analyze the manpower, personnel, and training (MPT) requirements of the proposed RPV system design for a number of operating scenarios. The RPV system is defined as consisting of the equipment, personnel, and operational procedures needed to perform five basic artillery missions: reconnaissance, target acquisition, artillery adjustment, target designation and damage assessment. The RPV design evaluated includes an air vehicle (AV), a modular integrated communications and navigation system (MICNS), a ground control station (GCS), a launch subsystem (LS), a recovery subsystem (RS), and a number of ground support requirements. The HARDMAN Methodology is an integrated set of data base management techniques and analytic tools, designed to provide timely and fully documented assessments of the human resource requirements associated with an emerging system's design.

Contingency Contractor Optimization Phase 3 Sustainment Requirements Document Contingency Contractor Optimization Tool - Prototype

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

Bandlow, Alisa; Durfee, Justin David; Frazier, Christopher Rawls

2016-05-01

This requirements document serves as an addendum to the Contingency Contractor Optimization Phase 2, Requirements Document [1] and Phase 3 Requirements Document [2]. The Phase 2 Requirements document focused on the high-level requirements for the tool. The Phase 3 Requirements document provided more detailed requirements to which the engineering prototype was built in Phase 3. This document will provide detailed requirements for features and enhancements being added to the production pilot in the Phase 3 Sustainment.

PRISM Spectrograph Optical Design

NASA Technical Reports Server (NTRS)

Chipman, Russell A.

1995-01-01

The objective of this contract is to explore optical design concepts for the PRISM spectrograph and produce a preliminary optical design. An exciting optical configuration has been developed which will allow both wavelength bands to be imaged onto the same detector array. At present the optical design is only partially complete because PRISM will require a fairly elaborate optical system to meet its specification for throughput (area*solid angle). The most complex part of the design, the spectrograph camera, is complete, providing proof of principle that a feasible design is attainable. This camera requires 3 aspheric mirrors to fit inside the 20x60 cm cross-section package. A complete design with reduced throughput (1/9th) has been prepared. The design documents the optical configuration concept. A suitable dispersing prism material, CdTe, has been identified for the prism spectrograph, after a comparison of many materials.

2014 Proposed Revision to 2008 Ozone National Ambient Air Quality Standards (NAAQS) Supporting Documents

EPA Pesticide Factsheets

Find information on the 2014 proposed ozone NAAQS revision, and find tools for background ozone, maps of nonattainment areas, an overview of the proposal, and information on designations, monitoring and permitting requirements

Students' Use of Mathematical Representations in Problem Solving.

ERIC Educational Resources Information Center

Santos-Trigo, Manuel

2002-01-01

Documents the experiences of 25 first-year university students with regard to the kinds of tasks calculus instructors should design in order to engage students in mathematical practices that often require the use of a graphing calculator. (MM)

Superfund Hazard Ranking System Training Course: Table of Contents

EPA Pesticide Factsheets

The Hazard Ranking System (HRS) training course is a four and ½ day, intermediate-level course designed for personnel who are required to compile, draft, and review preliminary assessments (PAs), site inspections (SIs), and HRS documentation records/packag

14 CFR 1216.304 - Categorical exclusions.

Code of Federal Regulations, 2013 CFR

2013-01-01

... funds. (iv) Preparation of documents, including design and feasibility studies, analytical supply and... sampling, cultural resources surveys, biological surveys, geologic surveys, modeling or simulations, and... Indian tribe, State, and/or local law or requirements. (3) Research and Development (R&D) Activities...

Space Station Freedom biomedical monitoring and countermeasures: Biomedical facility hardware catalog

NASA Technical Reports Server (NTRS)

1990-01-01

This hardware catalog covers that hardware proposed under the Biomedical Monitoring and Countermeasures Development Program supported by the Johnson Space Center. The hardware items are listed separately by item, and are in alphabetical order. Each hardware item specification consists of four pages. The first page describes background information with an illustration, definition and a history/design status. The second page identifies the general specifications, performance, rack interface requirements, problems, issues, concerns, physical description, and functional description. The level of hardware design reliability is also identified under the maintainability and reliability category. The third page specifies the mechanical design guidelines and assumptions. Described are the material types and weights, modules, and construction methods. Also described is an estimation of percentage of construction which utilizes a particular method, and the percentage of required new mechanical design is documented. The fourth page analyzes the electronics, the scope of design effort, and the software requirements. Electronics are described by percentages of component types and new design. The design effort, as well as, the software requirements are identified and categorized.

NDT applications in a successful fracture critical bridge inspection program and anchor bolt inspection program

NASA Astrophysics Data System (ADS)

Fish, Philip E.

1995-05-01

In 1978, Wisconsin Department of Transportation discovered major cracking on a two-girder, fracture critical structure, just four years after it was constructed. In 1981, on the same structure, now seven years old, major cracking was discovered in the tie girder flange of the tied arch span. This is one example of the type of failures that transportation departments discovered on welded structures in the 1970's and '80's. The failures from welded details and pinned connections lead to much stricter standards for present day designs. All areas were affected: design with identification of fatigue-prone details and classification of fatigue categories; material requirements with emphasis on toughness and weldability; increased welding and fabrication standards with licensure of fabrication shops to minimum quality standards including personnel; and an increased effort on inspection of existing bridges, where critical details were overlooked or missed in the past. FHWA inspection requirements for existing structures increased through this same time period, in reaction to the failures that had occurred. Obviously, many structures in Wisconsin were not built to the standards now required, thus the importance for quality inspection techniques. The new FHWA inspection requirements now being implemented throughout the nation require an in-depth, hands-on type inspection at a specified frequency, on all fracture critical structures. Wisconsin Department of Transportation started an in-depth inspection program in 1985 and made it a full time program in 1987. This program included extensive nondestructive testing. Ultrasonic inspection has played a major role in this type of inspection. All fracture critical structures, pin and hanger systems, and pinned connections are inspected on a five-year cycle now. The program requires an experienced inspection team and a practical inspection approach. Extensive preparation is required with review of all design, construction, and maintenance documents. An inspection plan is developed from the review and downloaded to a laptop computer. Inspection emphasis are on 'hands on' visual and nondestructive evaluation. Report documentation includes all design plans, pictorial documentation of structural deficiencies, nondestructive evaluation reports, conclusions, and recommendations. Planned changes in the program include implementation of an engineering work station as a 'single source' information file and reporting file for the inspection program. This would include scanning all current information into the file such as design, construction, and maintenance history. It would also include all inspection data with pictures. Inspections would be performed by downloading data onto a laptop and then uploading after completion of inspection. Pictures and nondestructive data would be entered by digital disks.

Constellation Program Human-System Integration Requirements. Revision E, Nov. 19, 2010

NASA Technical Reports Server (NTRS)

Dory, Jonathan

2010-01-01

The Human-Systems Integration Requirements (HSIR) in this document drive the design of space vehicles, their systems, and equipment with which humans interface in the Constellation Program (CxP). These requirements ensure that the design of Constellation (Cx) systems is centered on the needs, capabilities, and limitations of the human. The HSIR provides requirements to ensure proper integration of human-to-system interfaces. These requirements apply to all mission phases, including pre-launch, ascent, Earth orbit, trans-lunar flight, lunar orbit, lunar landing, lunar ascent, Earth return, Earth entry, Earth landing, post-landing, and recovery. The Constellation Program must meet NASA's Agency-level human rating requirements, which are intended to ensure crew survival without permanent disability. The HSIR provides a key mechanism for achieving human rating of Constellation systems.

Building Safer Systems With SpecTRM

NASA Technical Reports Server (NTRS)

2003-01-01

System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.

First incremental buy for Increment 2 of the Space Transportation System (STS)

NASA Technical Reports Server (NTRS)

1989-01-01

Thiokol manufactured and delivered 9 flight motors to KSC on schedule. All test flights were successful. All spent SRMs were recovered. Design, development, manufacture, and delivery of required transportation, handling, and checkout equipment to MSFC and to KSC were completed on schedule. All items of data required by DPD 400 were prepared and delivered as directed. In the system requirements and analysis area, the point of departure from Buy 1 to the operational phase was developed in significant detail with a complete set of transition documentation available. The documentation prepared during the Buy 1 program was maintained and updated where required. The following flight support activities should be continued through other production programs: as-built materials usage tracking on all flight hardware; mass properties reporting for all flight hardware until sample size is large enough to verify that the weight limit requirements were met; ballistic predictions and postflight performance assessments for all production flights; and recovered SRM hardware inspection and anomaly identification. In the safety, reliability, and quality assurance area, activities accomplished were assurance oriented in nature and specifically formulated to prevent problems and hardware failures. The flight program to date has adequately demonstrated the success of this assurance approach. The attention focused on details of design, analysis, manufacture, and inspection to assure the production of high-quality hardware has resulted in the absence of flight failures. The few anomalies which did occur were evaluated, design or manufacturing changes incorporated, and corrective actions taken to preclude recurrence.

Description of CASCOMP Comprehensive Airship Sizing and Performance Computer Program, Volume 2

NASA Technical Reports Server (NTRS)

Davis, J.

1975-01-01

The computer program CASCOMP, which may be used in comparative design studies of lighter than air vehicles by rapidly providing airship size and mission performance data, was prepared and documented. The program can be used to define design requirements such as weight breakdown, required propulsive power, and physical dimensions of airships which are designed to meet specified mission requirements. The program is also useful in sensitivity studies involving both design trade-offs and performance trade-offs. The input to the program primarily consists of a series of single point values such as hull overall fineness ratio, number of engines, airship hull and empennage drag coefficients, description of the mission profile, and weights of fixed equipment, fixed useful load and payload. In order to minimize computation time, the program makes ample use of optional computation paths.

System Guidelines for EMC Safety-Critical Circuits: Design, Selection, and Margin Demonstration

NASA Technical Reports Server (NTRS)

Lawton, R. M.

1996-01-01

Demonstration of required safety margins on critical electrical/electronic circuits in large complex systems has become an implementation and cost problem. These margins are the difference between the activation level of the circuit and the electrical noise on the circuit in the actual operating environment. This document discusses the origin of the requirement and gives a detailed process flow for the identification of the system electromagnetic compatibility (EMC) critical circuit list. The process flow discusses the roles of engineering disciplines such as systems engineering, safety, and EMC. Design and analysis guidelines are provided to assist the designer in assuring the system design has a high probability of meeting the margin requirements. Examples of approaches used on actual programs (Skylab and Space Shuttle Solid Rocket Booster) are provided to show how variations of the approach can be used successfully.

Reading Framework for the 2009 National Assessment of Educational Progress

ERIC Educational Resources Information Center

National Assessment Governing Board, 2008

2008-01-01

This document sets forth the design of a test of reading comprehension. The exam requires students to read passages of written English text--either literary or informational--and to answer questions about what they have read. In some cases, the questions deal with facts in the text or vocabulary. In other cases, a complete answer requires a clear…

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

None

The final rule of the Energy Policy Act of 2005 and its associated regulations enable covered state and alternative fuel provider fleets to obtain waivers from the alternative fuel vehicle (AFV)-acquisition requirements of Standard Compliance. Under Alternative Compliance, covered fleets instead meet a petroleum-use reduction requirement. This guidance document is designed to help fleets better understand the Alternative Compliance option and successfully complete the waiver application process.

Guidelines for a Training Program for Audiometric Technicians. Report of Working Group 66.

ERIC Educational Resources Information Center

Glorig, Aram, Ed.; And Others

The document outlines a course designed to train audiometric technicians who will conduct pure-tone conduction tests as part of a program on hearing conservation in noise. A minimum of two days is required for the completion of the course. The outline of the training program presents nine topics with an indication of the minimum time required for…

The making of the mechanical universe

NASA Technical Reports Server (NTRS)

Blinn, James

1989-01-01

The Mechanical Universe project required the production of over 550 different animated scenes, totaling about 7 and 1/2 hours of screen time. The project required the use of a wide range of techniques and motivated the development of several different software packages. A documentation is presented of many aspects of the project, encompassing artistic design issues, scientific simulations, software engineering, and video engineering.

Mod-5A wind turbine generator program design report. Volume 4: Drawings and specifications, book 2

NASA Technical Reports Server (NTRS)

1984-01-01

The design, development and analysis of the 7.3 MW MOD-5A wind turbine generator is documented. There are four volumes. This volume contains the drawings and specifications that were developed in preparation for building the MOD-5A wind turbine generator. This is the second book of volume four. Some of the items it contains are specs for the emergency shutdown panel, specs for the simulator software, simulator hardware specs, site operator terminal requirements, control data system requirements, software project management plan, elastomeric teeter bearing requirement specs, specs for the controls electronic cabinet, and specs for bolt pretensioning.

Access 5 - Step 1: Human Systems Integration Program Plan (HSIPP)

NASA Technical Reports Server (NTRS)

2005-01-01

This report describes the Human System Interface (HSI) analysis, design and test activities that will be performed to support the development of requirements and design guidelines to facilitate the incorporation of High Altitude Long Endurance (HALE) Remotely Operated Aircraft (ROA) at or above FL400 in the National Airspace System (NAS). These activities are required to support the design and development of safe, effective and reliable ROA operator and ATC interfaces. This plan focuses on the activities to be completed for Step 1 of the ACCESS 5 program. Updates to this document will be made for each of the four ACCESS 5 program steps.

Integral flange design program. [procedure for computing stresses

NASA Technical Reports Server (NTRS)

Wilson, J. F.

1974-01-01

An automated interactive flange design program utilizing an electronic desk top calculator is presented. The program calculates the operating and seating stresses for circular flanges of the integral or optional type subjected to internal pressure. The required input information is documented. The program provides an automated procedure for computing stresses in selected flange geometries for comparison to the allowable code values.

Collective Designing and Sharing of Open Educational Resources: A Study of the French CARTOUN Platform

ERIC Educational Resources Information Center

Quere, Nolwenn

2017-01-01

Designing and sharing Open Educational Resources (OERs) requires teachers to develop new competences, in particular with digital resources. In this paper, the case of a language resource production group is introduced. Due to the centrality of the OERs in their collective activity, I show that the documents they produce are essential to the…

Dynamic mobility applications open source application development portal task 6.1a : architecture and high-level design task 6.1b : list of requirements included in initial architecture and high-level design.

DOT National Transportation Integrated Search

2016-10-12

This document offers a detailed discussion of the systems functionality that was planned to be implemented. However, following the Agile Development methodology, during the course of system development, diligent decisions were made based on the la...

Design Criteria for Controlling Stress Corrosion Cracking

NASA Technical Reports Server (NTRS)

Franklin, D. B.

1987-01-01

This document sets forth the criteria to be used in the selection of materials for space vehicles and associated equipment and facilities so that failure resulting from stress corrosion will be prevented. The requirements established herein apply to all metallic components proposed for use in space vehicles and other flight hardware, ground support equipment, and facilities for testing. These requirements are applicable not only to items designed and fabricated by MSFC (Marshall Space Flight Center) and its prime contractors, but also to items supplied to the prime contractor by subcontractors and vendors.

Synthesis: Intertwining product and process

NASA Technical Reports Server (NTRS)

Weiss, David M.

1990-01-01

Synthesis is a proposed systematic process for rapidly creating different members of a program family. Family members are described by variations in their requirements. Requirements variations are mapped to variations on a standard design to generate production quality code and documentation. The approach is made feasible by using principles underlying design for change. Synthesis incorporates ideas from rapid prototyping, application generators, and domain analysis. The goals of Synthesis and the Synthesis process are discussed. The technology needed and the feasibility of the approach are also briefly discussed. The status of current efforts to implement Synthesis methodologies is presented.

Marksmanship Requirements From the Perspective of Combat Veterans - Volume I: Main Report

DTIC Science & Technology

2016-02-01

Research Report are not to be construed as an official Department of the Army position, unless so designated by other authorized documents. i REPORT... designated marksmanship (SDM) training was cited, but it was not always clear whether this course was given by the unit or by the United States Army...Appendix D. Some units designed specific marksmanship training programs. Collective training. Collective training was also cited (215 comments

Generalized Information Architecture for Managing Requirements in IBM?s Rational DOORS(r) Application.

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

Aragon, Kathryn M.; Eaton, Shelley M.; McCornack, Marjorie Turner

When a requirements engineering effort fails to meet expectations, often times the requirements management tool is blamed. Working with numerous project teams at Sandia National Laboratories over the last fifteen years has shown us that the tool is rarely the culprit; usually it is the lack of a viable information architecture with well- designed processes to support requirements engineering. This document illustrates design concepts with rationale, as well as a proven information architecture to structure and manage information in support of requirements engineering activities for any size or type of project. This generalized information architecture is specific to IBM's Rationalmore » DOORS (Dynamic Object Oriented Requirements System) software application, which is the requirements management tool in Sandia's CEE (Common Engineering Environment). This generalized information architecture can be used as presented or as a foundation for designing a tailored information architecture for project-specific needs. It may also be tailored for another software tool. Version 1.0 4 November 201« less

Final design review summary report for the TN-WHC cask and transportation system

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

Kee, A.T.

1997-01-17

This document represents comments generated from a review of Transnuclear`s Final Design Package distributed on December 10, 1996 and a review of the Final Design Analysis Report meeting held on December 17 & 18, 1996. The Final design describes desicn features and presents final analyses @j performed to fabricate and operate the system while meeting the Cask/Transportation Functions and Requirements, WHC-SD-SNF-FRD-011, Rev. 0 and specification WHC-S-0396, Rev. 1.

Final safety analysis report for the Galileo Mission: Volume 1, Reference design document

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

Not Available

The Galileo mission uses nuclear power sources called Radioisotope Thermoelectric Generators (RTGs) to provide the spacecraft's primary electrical power. Because these generators contain nuclear material, a Safety Analysis Report (SAR) is required. A preliminary SAR and an updated SAR were previously issued that provided an evolving status report on the safety analysis. As a result of the Challenger accident, the launch dates for both Galileo and Ulysses missions were later rescheduled for November 1989 and October 1990, respectively. The decision was made by agreement between the DOE and the NASA to have a revised safety evaluation and report (FSAR) preparedmore » on the basis of these revised vehicle accidents and environments. The results of this latest revised safety evaluation are presented in this document (Galileo FSAR). Volume I, this document, provides the background design information required to understand the analyses presented in Volumes II and III. It contains descriptions of the RTGs, the Galileo spacecraft, the Space Shuttle, the Inertial Upper Stage (IUS), the trajectory and flight characteristics including flight contingency modes, and the launch site. There are two appendices in Volume I which provide detailed material properties for the RTG.« less

ANSI/ASHRAE/IES Standard 90.1-2010 Performance Rating Method Reference Manual

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

Goel, Supriya; Rosenberg, Michael I.

This document is intended to be a reference manual for the Appendix G Performance Rating Method (PRM) of ANSI/ASHRAE/IES Standard 90.1- 2010 (Standard 90.1-2010).The PRM is used for rating the energy efficiency of commercial and high-rise residential buildings with designs that exceed the requirements of Standard 90.1. The procedures and processes described in this manual are designed to provide consistency and accuracy by filling in gaps and providing additional details needed by users of the PRM. It should be noted that this document is created independently from ASHRAE and SSPC 90.1 and is not sanctioned nor approved by either ofmore » those entities . Potential users of this manual include energy modelers, software developers and implementers of “beyond code” energy programs. Energy modelers using ASHRAE Standard 90.1-2010 for beyond code programs can use this document as a reference manual for interpreting requirements of the Performance Rating method. Software developers, developing tools for automated creation of the baseline model can use this reference manual as a guideline for developing the rules for the baseline model.« less

Authorization basis supporting documentation for plutonium finishing plant

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

King, J.P., Fluor Daniel Hanford

1997-03-05

The identification and definition of the authorization basis for the Plutonium Finishing Plant (PFP) facility and operations are essential for compliance to DOE Order 5480.21, Unreviewed Safety Questions. The authorization basis, as defined in the Order, consists of those aspects of the facility design basis, i.e., the structures, systems and components (SSCS) and the operational requirements that are considered to be important to the safety of operations and are relied upon by DOE to authorize operation of the facility. These facility design features and their function in various accident scenarios are described in WHC-SD-CP-SAR-021, Plutonium Finishing Plant Final Safety Analysismore » Report (FSAR), Chapter 9, `Accident Analysis.` Figure 1 depicts the relationship of the Authorization Basis to its components and other information contained in safety documentation supporting the Authorization Basis. The PFP SSCs that are important to safety, collectively referred to as the `Safety Envelope` are discussed in various chapters of the FSAR and in WHC-SD-CP-OSR-010, Plutonium Finishing Plant Operational Safety Requirements. Other documents such as Criticality Safety Evaluation Reports (CSERS) address and support some portions of the Authorization Basis and Safety Envelope.« less

The software development process at the Chandra X-ray Center

NASA Astrophysics Data System (ADS)

Evans, Janet D.; Evans, Ian N.; Fabbiano, Giuseppina

2008-08-01

Software development for the Chandra X-ray Center Data System began in the mid 1990's, and the waterfall model of development was mandated by our documents. Although we initially tried this approach, we found that a process with elements of the spiral model worked better in our science-based environment. High-level science requirements are usually established by scientists, and provided to the software development group. We follow with review and refinement of those requirements prior to the design phase. Design reviews are conducted for substantial projects within the development team, and include scientists whenever appropriate. Development follows agreed upon schedules that include several internal releases of the task before completion. Feedback from science testing early in the process helps to identify and resolve misunderstandings present in the detailed requirements, and allows review of intangible requirements. The development process includes specific testing of requirements, developer and user documentation, and support after deployment to operations or to users. We discuss the process we follow at the Chandra X-ray Center (CXC) to develop software and support operations. We review the role of the science and development staff from conception to release of software, and some lessons learned from managing CXC software development for over a decade.

Mechanical flexible joint design document

NASA Technical Reports Server (NTRS)

Daily, Vic

1993-01-01

The purpose of this report is to document the status of the Mechanical Flexible Joint (MFJ) Design Subtask with the intent of halting work on the design. Recommendations for future work is included in the case that the task is to be resumed. The MFJ is designed to eliminate two failure points from the current flex joint configuration, the inner 'tripod configuration' and the outer containment jacket. The MFJ will also be designed to flex 13.5 degrees and have three degrees of freedom. By having three degrees of freedom, the MFJ will allow the Low Pressure Fuel Duct to twist and remove the necessity to angulate the full 11 degrees currently required. The current flex joints are very labor intensive and very costly and a simple alternative is being sought. The MFJ is designed with a greater angular displacement, with three degrees of freedom, to reside in the same overall envelope, to meet weight constraints of the current bellows, to be compatible with cryogenic fuel and oxidizers, and also to be man-rated.

Administrative Support Occupations Skill Standards.

ERIC Educational Resources Information Center

Professional Secretaries International, Kansas City, MO.

This document establishes a set of performance expectations based on current practices in administrative support occupations. It is designed to assist individuals, training providers, employers, management personnel, and professional organizations in matching knowledge, abilities, and interests to knowledge and skills required for success in…

A strategic plan for the design and creation of a safety management system for the Commonwealth of Virginia.

DOT National Transportation Integrated Search

1994-01-01

The Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991 required that states develop systems for managing highway pavement, bridges, safety, congestion, public transportation, and intermodal transportation. This document is Virginia's wo...

40 CFR 35.6270 - Standards for financial management systems.

Code of Federal Regulations, 2012 CFR

2012-07-01

... OTHER FEDERAL ASSISTANCE STATE AND LOCAL ASSISTANCE Cooperative Agreements and Superfund State Contracts for Superfund Response Actions Financial Administration Requirements Under A Cooperative Agreement... costs must be documented under a single Superfund account number designated specifically for the pre...

40 CFR 35.6270 - Standards for financial management systems.

Code of Federal Regulations, 2013 CFR

2013-07-01

... OTHER FEDERAL ASSISTANCE STATE AND LOCAL ASSISTANCE Cooperative Agreements and Superfund State Contracts for Superfund Response Actions Financial Administration Requirements Under A Cooperative Agreement... costs must be documented under a single Superfund account number designated specifically for the pre...

40 CFR 35.6270 - Standards for financial management systems.

Code of Federal Regulations, 2014 CFR

2014-07-01

... OTHER FEDERAL ASSISTANCE STATE AND LOCAL ASSISTANCE Cooperative Agreements and Superfund State Contracts for Superfund Response Actions Financial Administration Requirements Under A Cooperative Agreement... costs must be documented under a single Superfund account number designated specifically for the pre...

LogiKit - assisting complex logic specification and implementation for embedded control systems

NASA Astrophysics Data System (ADS)

Diglio, A.; Nicolodi, B.

2002-07-01

LogiKit provides an overall lifecycle solution. LogiKit is a powerful software engineering case toolkit for requirements specification, simulation and documentation. LogiKit also provides an automatic ADA software design, code and unit test generator.

14 CFR § 1216.304 - Categorical exclusions.

Code of Federal Regulations, 2014 CFR

2014-01-01

... funds. (iv) Preparation of documents, including design and feasibility studies, analytical supply and... sampling, cultural resources surveys, biological surveys, geologic surveys, modeling or simulations, and... Indian tribe, State, and/or local law or requirements. (3) Research and Development (R&D) Activities...

8 CFR 103.38 - Genealogy Program.

Code of Federal Regulations, 2013 CFR

2013-01-01

...; BIOMETRIC REQUIREMENTS; AVAILABILITY OF RECORDS Availability of Records § 103.38 Genealogy Program. (a... is a fee-for-service program designed to provide genealogical and historical records and reference services to genealogists, historians, and others seeking documents maintained within the historical record...

8 CFR 103.38 - Genealogy Program.

Code of Federal Regulations, 2012 CFR

2012-01-01

...; BIOMETRIC REQUIREMENTS; AVAILABILITY OF RECORDS Availability of Records § 103.38 Genealogy Program. (a... is a fee-for-service program designed to provide genealogical and historical records and reference services to genealogists, historians, and others seeking documents maintained within the historical record...

8 CFR 103.38 - Genealogy Program.

Code of Federal Regulations, 2014 CFR

2014-01-01

...; BIOMETRIC REQUIREMENTS; AVAILABILITY OF RECORDS Availability of Records § 103.38 Genealogy Program. (a... is a fee-for-service program designed to provide genealogical and historical records and reference services to genealogists, historians, and others seeking documents maintained within the historical record...

Vehicle information exchange needs for mobility applications : version 3.0.

DOT National Transportation Integrated Search

1996-06-01

The Evaluatory Design Document provides a unifying set of assumptions for other evaluations to utilize. Many of the evaluation activities require the definition of an actual implementation in order to be performed. For example, to cost the elements o...

MODIS Information, Data, and Control System (MIDACS) system specifications and conceptual design

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.; Sharts, B.; Folta, D.

1988-01-01

The MODIS Information, Data, and Control System (MIDACS) Specifications and Conceptual Design Document discusses system level requirements, the overall operating environment in which requirements must be met, and a breakdown of MIDACS into component subsystems, which include the Instrument Support Terminal, the Instrument Control Center, the Team Member Computing Facility, the Central Data Handling Facility, and the Data Archive and Distribution System. The specifications include sizing estimates for the processing and storage capacities of each data system element, as well as traffic analyses of data flows between the elements internally, and also externally across the data system interfaces. The specifications for the data system, as well as for the individual planning and scheduling, control and monitoring, data acquisition and processing, calibration and validation, and data archive and distribution components, do not yet fully specify the data system in the complete manner needed to achieve the scientific objectives of the MODIS instruments and science teams. The teams have not yet been formed; however, it was possible to develop the specifications and conceptual design based on the present concept of EosDIS, the Level-1 and Level-2 Functional Requirements Documents, the Operations Concept, and through interviews and meetings with key members of the scientific community.

Training Manual for Elements of Interface Definition and Control

NASA Technical Reports Server (NTRS)

Lalli, Vincent R. (Editor); Kastner, Robert E. (Editor); Hartt, Henry N. (Editor)

1997-01-01

The primary thrust of this manual is to ensure that the format and information needed to control interfaces between equipment are clear and understandable. The emphasis is on controlling the engineering design of the interface and not on the functional performance requirements of the system or the internal workings of the interfacing equipment. Interface control should take place, with rare exception, at the interfacing elements and no further. There are two essential sections of the manual. Chapter 2, Principles of Interface Control, discusses how interfaces are defined. It describes different types of interfaces to be considered and recommends a format for the documentation necessary for adequate interface control. Chapter 3, The Process: Through the Design Phases, provides tailored guidance for interface definition and control. This manual can be used to improve planned or existing interface control processes during system design and development. It can also be used to refresh and update the corporate knowledge base. The information presented herein will reduce the amount of paper and data required in interface definition and control processes by as much as 50 percent and will shorten the time required to prepare an interface control document. It also highlights the essential technical parameters that ensure that flight subsystems will indeed fit together and function as intended after assembly and checkout.

FBI fingerprint identification automation study: AIDS 3 evaluation report. Volume 9: Functional requirements

NASA Technical Reports Server (NTRS)

1980-01-01

The current system and subsystem used by the Identification Division are described. System constraints that dictate the system environment are discussed and boundaries within which solutions must be found are described. The functional requirements were related to the performance requirements. These performance requirements were then related to their applicable subsystems. The flow of data, documents, or other pieces of information from one subsystem to another or from the external world into the identification system is described. Requirements and design standards for a computer based system are presented.

Challenges And Concepts for Design of An Interaction Region With Push-Pull Arrangement of Detectors - An Interface Document

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

Parker, B.; /Brookhaven; Herve, Alain

2011-10-14

Two experimental detectors working in a push-pull mode has been considered for the Interaction Region of the International Linear Collider. The push-pull mode of operation sets specific requirements and challenges for many systems of detector and machine, in particular for the IR magnets, for the cryogenics and alignment system, for beamline shielding, for detector design and overall integration, and so on. These challenges and the identified conceptual solutions discussed in the paper intend to form a draft of the Interface Document which will be developed further in the nearest future. The authors of the present paper include the organizers andmore » conveners of working groups of the workshop on engineering design of interaction region IRENG07, the leaders of the IR Integration within Global Design Effort Beam Delivery System, and the representatives from each detector concept submitting the Letters Of Intent.« less

Strategies for Time-resolved X-ray Diffraction of Phase Transitions with Laser Compression

NASA Astrophysics Data System (ADS)

Benedetti, Laura Robin; Eggert, J. H.; Bradley, D. K.; Bell, P. M.; Kilkenny, J. D.; Palmer, N.; Petre, R. B.; Rygg, J. R.; Sorce, C.; Collins, G. W.; Boehly, T. R.

2017-10-01

As part of a program to document kinetics of phase transitions under laser-driven dynamic compression, we are designing a platform to make multiple x-ray diffraction measurements during a single laser experiment. Our plans include experimental development at Omega-EP and eventual implementation at NIF. We will present our strategy for designing a robust platform that can effectively document a wide variety of phase transformations by utilizing both streaked and multiple-frame imaging detectors. Preliminary designs utilize a novel CMOS detector designed by Sandia National Lab. Our initial experiments include scoping studies that will focus on photometrics and shielding requirements in the high EMP environment close to the target. This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344. Lawrence Livermore National Security, LLC, LLNL-ABS-734470.

International Docking Standard (IDSS) Interface Definition Document (IDD) . E; Revision

NASA Technical Reports Server (NTRS)

Kelly, Sean M.; Cryan, Scott P.

2016-01-01

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

Development of an open metadata schema for prospective clinical research (openPCR) in China.

PubMed

Xu, W; Guan, Z; Sun, J; Wang, Z; Geng, Y

2014-01-01

In China, deployment of electronic data capture (EDC) and clinical data management system (CDMS) for clinical research (CR) is in its very early stage, and about 90% of clinical studies collected and submitted clinical data manually. This work aims to build an open metadata schema for Prospective Clinical Research (openPCR) in China based on openEHR archetypes, in order to help Chinese researchers easily create specific data entry templates for registration, study design and clinical data collection. Singapore Framework for Dublin Core Application Profiles (DCAP) is used to develop openPCR and four steps such as defining the core functional requirements and deducing the core metadata items, developing archetype models, defining metadata terms and creating archetype records, and finally developing implementation syntax are followed. The core functional requirements are divided into three categories: requirements for research registration, requirements for trial design, and requirements for case report form (CRF). 74 metadata items are identified and their Chinese authority names are created. The minimum metadata set of openPCR includes 3 documents, 6 sections, 26 top level data groups, 32 lower data groups and 74 data elements. The top level container in openPCR is composed of public document, internal document and clinical document archetypes. A hierarchical structure of openPCR is established according to Data Structure of Electronic Health Record Architecture and Data Standard of China (Chinese EHR Standard). Metadata attributes are grouped into six parts: identification, definition, representation, relation, usage guides, and administration. OpenPCR is an open metadata schema based on research registration standards, standards of the Clinical Data Interchange Standards Consortium (CDISC) and Chinese healthcare related standards, and is to be publicly available throughout China. It considers future integration of EHR and CR by adopting data structure and data terms in Chinese EHR Standard. Archetypes in openPCR are modularity models and can be separated, recombined, and reused. The authors recommend that the method to develop openPCR can be referenced by other countries when designing metadata schema of clinical research. In the next steps, openPCR should be used in a number of CR projects to test its applicability and to continuously improve its coverage. Besides, metadata schema for research protocol can be developed to structurize and standardize protocol, and syntactical interoperability of openPCR with other related standards can be considered.

Acceptance test report for portable exhauster POR-007/Skid E

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

Kriskovich, J.R.

1998-07-24

This document describes Acceptance Testing performed on Portable Exhauster POR-007/Skid E. It includes measurements of bearing vibration levels, pressure decay testing, programmable logic controller interlocks, high vacuum, flow and pressure control functional testing. The purpose of Acceptance testing documented by this report was to demonstrate compliance of the exhausters with the performance criteria established within HNF-0490, Rev. 1 following a repair and upgrade effort at Hanford. In addition, data obtained during this testing is required for the resolution of outstanding Non-conformance Reports (NCR), and finally, to demonstrate the functionality of the associated software for the pressure control and high vacuummore » exhauster operating modes provided for by W-320. Additional testing not required by the ATP was also performed to assist in the disposition and close out of receiving inspection report and for application design information (system curve). Results of this testing are also captured within this document.« less

An analysis of electronic document management in oncology care.

PubMed

Poulter, Thomas; Gannon, Brian; Bath, Peter A

2012-06-01

In this research in progress, a reference model for the use of electronic patient record (EPR) systems in oncology is described. The model, termed CICERO, comprises technical and functional components, and emphasises usability, clinical safety and user acceptance. One of the functional components of the model-an electronic document and records management (EDRM) system-is monitored in the course of its deployment at a leading oncology centre in the UK. Specifically, the user requirements and design of the EDRM solution are described.The study is interpretative and forms part a wider research programme to define and validate the CICERO model. Preliminary conclusions confirm the importance of a socio-technical perspective in Onco-EPR system design.

Launch Deployment Assembly Extravehicular Activity Neutral Buoyancy Development Test Report

NASA Technical Reports Server (NTRS)

Loughead, T.

1996-01-01

This test evaluated the Launch Deployment Assembly (LDA) design for Extravehicular Activity (EVA) work sites (setup, igress, egress), reach and visual access, and translation required for cargo item removal. As part of the LDA design, this document describes the method and results of the LDA EVA Neutral Buoyancy Development Test to ensure that the LDA hardware support the deployment of the cargo items from the pallet. This document includes the test objectives, flight and mockup hardware description, descriptions of procedures and data collection used in the testing, and the results of the development test at the National Aeronautics and Space Administrations (NASA) Marshall Space Flight Center (MSFC) Neutral Buoyancy Simulator (NBS).

75 FR 5375 - Hazardous Material; Miscellaneous Packaging Amendments

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-02

...In this final rule, PHMSA is amending packaging requirements in the Hazardous Materials Regulations to enhance compliance flexibility, improve clarity, and reduce regulatory burdens. Specifically, we are revising several packaging related definitions; adding provisions to allow more flexibility when preparing and transmitting closure instructions, including conditions under which closure instructions may be transmitted electronically; adding a requirement for shippers to retain packaging closure instructions; incorporating new language that will allow for a practicable means of stenciling the ``UN'' symbol on packagings; and clarifying a requirement to document the methodology used when determining whether a change in packaging configuration requires retesting as a new design or may be considered a variation of a previously tested design. This final rule also incorporates requirements for construction, maintenance, and use of Large Packagings.

MarFS-Requirements-Design-Configuration-Admin

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

Kettering, Brett Michael; Grider, Gary Alan

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

Design and Manufacture of Wood Blades for Windtunnel Fans

NASA Technical Reports Server (NTRS)

Richardson, S. E.

1998-01-01

Many windtunnels use wooden fan blades, however, because of their usual long life (often in excess of 50 years) wooden blades typically do not have to be replaced very often; therefore, the expertise for designing and building wooden windtunnel fan blades is being lost. The purpose of this report is to document the design and build process so that when replacement blades are eventually required some of the critical information required is available. Information useful to fan-blade designers, fabricators, inspectors, and windtunnel operations personnel is included. Fixed pitch and variable pitch fans as well as fans which range in size from a few feet in diameter to over 40 ft. in diameter are described. Woods, adhesives, and coverings are discussed.

Advanced EVA system design requirements study

NASA Technical Reports Server (NTRS)

Woods, T. G.

1988-01-01

The results are presented of a study to identify specific criteria regarding space station extravehicular activity system (EVAS) hardware requirements. Key EVA design issues include maintainability, technology readiness, LSS volume vs. EVA time available, suit pressure/cabin pressure relationship and productivity effects, crew autonomy, integration of EVA as a program resource, and standardization of task interfaces. A variety of DOD EVA systems issues were taken into consideration. Recommendations include: (1) crew limitations, not hardware limitations; (2) capability to perform all of 15 generic missions; (3) 90 days on-orbit maintainability with 50 percent duty cycle as minimum; and (4) use by payload sponsors of JSC document 10615A plus a Generic Tool Kit and Specialized Tool Kit description. EVA baseline design requirements and criteria, including requirements of various subsystems, are outlined. Space station/EVA system interface requirements and EVA accommodations are discussed in the areas of atmosphere composition and pressure, communications, data management, logistics, safe haven, SS exterior and interior requirements, and SS airlock.

Automated Ground Umbilical Systems (AGUS) Project

NASA Technical Reports Server (NTRS)

Gosselin, Armand M.

2007-01-01

All space vehicles require ground umbilical systems for servicing. Servicing requirements can include, but are not limited to, electrical power and control, propellant loading and venting, pneumatic system supply, hazard gas detection and purging as well as systems checkout capabilities. Of the various types of umbilicals, all require several common subsystems. These typically include an alignment system, mating and locking system, fluid connectors, electrical connectors and control !checkout systems. These systems have been designed to various levels of detail based on the needs for manual and/or automation requirements. The Automated Ground Umbilical Systems (AGUS) project is a multi-phase initiative to develop design performance requirements and concepts for launch system umbilicals. The automation aspect minimizes operational time and labor in ground umbilical processing while maintaining reliability. This current phase of the project reviews the design, development, testing and operations of ground umbilicals built for the Saturn, Shuttle, X-33 and Atlas V programs. Based on the design and operations lessons learned from these systems, umbilicals can be optimized for specific applications. The product of this study is a document containing details of existing systems and requirements for future automated umbilical systems with emphasis on design-for-operations (DFO).

Air Force Space Command. Space and Missile Systems Center Standard. Electromagnetic Compatibility Requirements for Space Equipment and Systems

DTIC Science & Technology

2008-06-13

technology developments. 2. This new-issue SMC standard comprises the text of The Aerospace Corporation report number TOR-2005( 8583 )-1. 3...issues of the documents are the current versions. 1. Aerospace Report No. TOR-2005( 8583 )-2, Electrical Power Systems, Direct Current, Space Vehicle...Design Requirements, The Aerospace Corp., 13 January 2005. 2. Aerospace Report No. TR-2004( 8583 )-1 (proposed MIL-STD-1540E), Test Requirements for

An automated program for reinforcement requirements for openings in cylindrical pressure vessels

NASA Technical Reports Server (NTRS)

Wilson, J. F.; Taylor, J. T.

1975-01-01

An automated interactive program for calculating the reinforcement requirements for openings in cylindrical pressure vessels subjected to internal pressure is described. The program is written for an electronic desk top calculator. The program calculates the required area of reinforcement for a given opening and compares this value with the area of reinforcement provided by a proposed design. All program steps, operating instructions, and example problems with input and sample output are documented.

Partial Automation of Requirements Tracing

NASA Technical Reports Server (NTRS)

Hayes, Jane; Dekhtyar, Alex; Sundaram, Senthil; Vadlamudi, Sravanthi

2006-01-01

Requirements Tracing on Target (RETRO) is software for after-the-fact tracing of textual requirements to support independent verification and validation of software. RETRO applies one of three user-selectable information-retrieval techniques: (1) term frequency/inverse document frequency (TF/IDF) vector retrieval, (2) TF/IDF vector retrieval with simple thesaurus, or (3) keyword extraction. One component of RETRO is the graphical user interface (GUI) for use in initiating a requirements-tracing project (a pair of artifacts to be traced to each other, such as a requirements spec and a design spec). Once the artifacts have been specified and the IR technique chosen, another component constructs a representation of the artifact elements and stores it on disk. Next, the IR technique is used to produce a first list of candidate links (potential matches between the two artifact levels). This list, encoded in Extensible Markup Language (XML), is optionally processed by a filtering component designed to make the list somewhat smaller without sacrificing accuracy. Through the GUI, the user examines a number of links and returns decisions (yes, these are links; no, these are not links). Coded in XML, these decisions are provided to a "feedback processor" component that prepares the data for the next application of the IR technique. The feedback reduces the incidence of erroneous candidate links. Unlike related prior software, RETRO does not require the user to assign keywords, and automatically builds a document index.

Design criteria for payload workstation accommodations

NASA Technical Reports Server (NTRS)

Watters, H. H.; Stokes, J. W.

1975-01-01

Anticipated shuttle sortie payload man-system design criteria needs are investigated. Man-system interactions for the scientific disciplines are listed and the extent is assessed to which documented Skylab experience is expected to provide system design guidance for each of the identified interactions. Where the analysis revealed that the reduced Skylab data does not answer the anticipated needs candidate criteria, based on unreduced Skylab data, available prior research, original analysis, or related requirements derived from previous space programs, are provided.

Special Plans and Operations: Assessment of Allegations Concerning Traumatic Brain Injury Research Integrity in Iraq

DTIC Science & Technology

2011-03-31

protocols conducted in Iraq. His office had been designated by the 1 A research protocol is a formal document detailing the study methodology and the...Human Research Protections Program plan requires scientific peer review to ensure that research is scientifically sound in its design and methods, and...ofthe approved research protocol and IRB minutes, revealed that there was no mention of "active rehabilitation and exercise" under the design

Human Research Program Requirements Document (Revision C)

NASA Technical Reports Server (NTRS)

Vargas, Paul R.

2009-01-01

The purpose of this document is to define, document, and allocate the Human Research Program (HRP) requirements to the HRP Program Elements. It establishes the flow-down of requirements from Exploration Systems Mission Directorate (ESMD) and Office of the Chief Health and Medical Officer (OCHMO) to the various Program Elements of the HRP to ensure that human research and technology countermeasure investments are made to insure the delivery of countermeasures and technologies that satisfy ESMD's and OCHMO's exploration mission requirements. Requirements driving the HRP work and deliverables are derived from the exploration architecture, as well as Agency standards regarding the maintenance of human health and performance. Agency human health and performance standards will define acceptable risk for each type and duration of exploration mission. It is critical to have the best available scientific and clinical evidence in setting and validating these standards. In addition, it is imperative that the best available evidence on preventing and mitigating human health and performance risks is incorporated into exploration mission and vehicle designs. These elements form the basis of the HRP research and technology development requirements and highlight the importance of HRP investments in enabling NASA's exploration missions. This PRD defines the requirements of the HRP which is comprised of the following major Program Elements: Behavioral Health and Performance (BHP), Exploration Medical Capability (ExMC), Human Health Countermeasures (HHC), ISS Medical Project (ISSMP), Space Human Factors and Habitability (SHFH), and Space Radiation (SR).

Development of a Hand Held Thromboelastograph

DTIC Science & Technology

2015-01-01

documents will be referenced during the Entegrion PCM System design, verification and validation activities. EN 61010 -1:2010 (Edition3.0) Safety...requirements for electrical equipment for measurement, control, and laboratory use – Part 1: General requirements. EN 61010 -2-101:2002 Safety...IPC-A-610E Acceptability of Electronic Assemblies IPC 7711/21B Rework, Modification and Repair of Electronic Assemblies. IEC 62304:2006/AC:2008

76 FR 66862 - Opening of Boquillas Border Crossing and Update to the Class B Port of Entry Description

Federal Register 2010, 2011, 2012, 2013, 2014

2011-10-28

... documentary requirements.\\4\\ \\1\\ A port of entry is defined in 19 CFR 101.1 as ``any place designated by... port of entry in 8 CFR 100.4(a) refers to aliens admissible without documents under documentary waivers... Regulations, 8 CFR 212.0, 212.1, and 235.1, pertaining to documentary requirements for nonimmigrants and the...

Defense Acquisition Research Journal. Volume 23, Number 4, Issue 79, October 2016

DTIC Science & Technology

2016-10-01

the final word on ship design decisions, including critical operational requirements and costs. Kuehn provides a captivating description of how the...requires using material from primary sources, including program documents, policy papers, memoranda, surveys , interviews, etc. Articles are...instrument, • describe the limitations of the research, • ensure results are quantitative and qualitative, • determine if the study can be replicated, and

Multilayer Insulation Material Guidelines

NASA Technical Reports Server (NTRS)

Finckenor, M. M.; Dooling, D.

1999-01-01

Multilayer Insulation Material Guidelines provides data on multilayer insulation materials used by previous spacecraft such as Spacelab and the Long-Duration Exposure Facility and outlines other concerns. The data presented in the document are presented for information only. They can be used as guidelines for multilayer insulation design for future spacecraft provided the thermal requirements of each new design and the environmental effects on these materials are taken into account.

Trilateration range and range rate system. Volume 1: CDA system manual

NASA Technical Reports Server (NTRS)

1976-01-01

This document is one of a series of manuals designed to provide the information required to operate and maintain the Command and Data Acquisition (CDA) equipment of the Trilateration Range and Range Rate (TRRR) System. Information pertaining to the equipment in the Trilateration Range and Range Rate System which is designed to interface with existing NASA equipment located at Wallops Island, Virginia is presented.

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...

40 CFR 265.1064 - Recordkeeping requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... waste management units in one recordkeeping system if the system identifies each record by each...) Design documentation and monitoring, operating, and inspection information for each closed-vent system...) An up-to-date analysis and the supporting information and data used to determine whether or not...

Design Document for Differential GPS Ground Reference Station Pseudorange Correction Generation Algorithm

DOT National Transportation Integrated Search

1986-12-01

The algorithms described in this report determine the differential corrections to be broadcast to users of the Global Positioning System (GPS) who require higher accuracy navigation or position information than the 30 to 100 meters that GPS normally ...

NHDOT : process for municipally-managed state bridge aid program projects

DOT National Transportation Integrated Search

2007-09-12

The document sets for the requirements for a municipality which to manage the design and construction of a bridge rehabilitation or replacement project and receive Bridge Aid under the applicable provisions of RSA 234. Bridge Aid provided to a Munici...

Function algorithms for MPP scientific subroutines, volume 1

NASA Technical Reports Server (NTRS)

Gouch, J. G.

1984-01-01

Design documentation and user documentation for function algorithms for the Massively Parallel Processor (MPP) are presented. The contract specifies development of MPP assembler instructions to perform the following functions: natural logarithm; exponential (e to the x power); square root; sine; cosine; and arctangent. To fulfill the requirements of the contract, parallel array and solar implementations for these functions were developed on the PDP11/34 Program Development and Management Unit (PDMU) that is resident at the MPP testbed installation located at the NASA Goddard facility.

Wrong kind of networking.

PubMed

Ortolon, Ken

2011-04-01

Patients who pay for out-of-network benefits should have the right to use those benefits, the Texas Medical Association believes. But TMA fears that a new CIGNA policy is designed to discourage enrollees from using their out-of-network benefits and will create huge administrative hassles for physicians who refer patients to out-of-network providers. TMA officials say the policy requires physicians to document that they told patients that they are being referred to out-of-network providers and to keep the documentation in their records indefinitely.

Crew procedures development techniques

NASA Technical Reports Server (NTRS)

Arbet, J. D.; Benbow, R. L.; Hawk, M. L.; Mangiaracina, A. A.; Mcgavern, J. L.; Spangler, M. C.

1975-01-01

The study developed requirements, designed, developed, checked out and demonstrated the Procedures Generation Program (PGP). The PGP is a digital computer program which provides a computerized means of developing flight crew procedures based on crew action in the shuttle procedures simulator. In addition, it provides a real time display of procedures, difference procedures, performance data and performance evaluation data. Reconstruction of displays is possible post-run. Data may be copied, stored on magnetic tape and transferred to the document processor for editing and documentation distribution.

Sandia National Laboratories Facilities Management and Operations Center Design Standards Manual

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

Peterson, Timothy L.

2014-09-01

At Sandia National Laboratories in New Mexico (SNL/NM), the design, construction, operation, and maintenance of facilities is guided by industry standards, a graded approach, and the systematic analysis of life cycle benefits received for costs incurred. The design of the physical plant must ensure that the facilities are "fit for use," and provide conditions that effectively, efficiently, and safely support current and future mission needs. In addition, SNL/NM applies sustainable design principles, using an integrated whole-building design approach, from site planning to facility design, construction, and operation to ensure building resource efficiency and the health and productivity of occupants. Themore » safety and health of the workforce and the public, any possible effects on the environment, and compliance with building codes take precedence over project issues, such as performance, cost, and schedule. These design standards generally apply to all disciplines on all SNL/NM projects. Architectural and engineering design must be both functional and cost-effective. Facility design must be tailored to fit its intended function, while emphasizing low-maintenance, energy-efficient, and energy-conscious design. Design facilities that can be maintained easily, with readily accessible equipment areas, low maintenance, and quality systems. To promote an orderly and efficient appearance, architectural features of new facilities must complement and enhance the existing architecture at the site. As an Architectural and Engineering (A/E) professional, you must advise the Project Manager when this approach is prohibitively expensive. You are encouraged to use professional judgment and ingenuity to produce a coordinated interdisciplinary design that is cost-effective, easily contractible or buildable, high-performing, aesthetically pleasing, and compliant with applicable building codes. Close coordination and development of civil, landscape, structural, architectural, fire protection, mechanical, electrical, telecommunications, and security features is expected to ensure compatibility with planned functional equipment and to facilitate constructability. If portions of the design are subcontracted to specialists, delivery of the finished design documents must not be considered complete until the subcontracted portions are also submitted for review. You must, along with support consultants, perform functional analyses and programming in developing design solutions. These solutions must reflect coordination of the competing functional, budgetary, and physical requirements for the project. During design phases, meetings between you and the SNL/NM Project Team to discuss and resolve design issues are required. These meetings are a normal part of the design process. For specific design-review requirements, see the project-specific Design Criteria. In addition to the design requirements described in this manual, instructive information is provided to explain the sustainable building practice goals for design, construction, operation, and maintenance of SNL/NM facilities. Please notify SNL/NM personnel of design best practices not included in this manual, so they can be incorporated in future updates. You must convey all documents describing work to the SNL/NM Project Manager in both hard copy and in an electronic format compatible with the SNL/NM-prescribed CADD and other software packages, and in accordance with a SNL/NM approved standard format. Print all hard copy versions of submitted documents (excluding drawings and renderings) double-sided when practical.« less

Development and evaluation of a web-based application for digital findings and documentation in physiotherapy education.

PubMed

Spieler, Bernadette; Burgsteiner, Harald; Messer-Misak, Karin; Gödl-Purrer, Barbara; Salchinger, Beate

2015-01-01

Findings in physiotherapy have standardized approaches in treatment, but there is also a significant margin of differences in how to implement these standards. Clinical decisions require experience and continuous learning processes to consolidate personal values and opinions and studies suggest that lecturers can influence students positively. Recently, the study course of Physiotherapy at the University of Applied Science in Graz has offered a paper based finding document. This document supported decisions through the adaption of the clinical reasoning process. The document was the starting point for our learning application called "EasyAssess", a Java based web-application for a digital findings documentation. A central point of our work was to ensure efficiency, effectiveness and usability of the web-application through usability tests utilized by both students and lecturers. Results show that our application fulfills the previously defined requirements and can be efficiently used in daily routine largely because of its simple user interface and its modest design. Due to the close cooperation with the study course Physiotherapy, the application has incorporated the various needs of the target audiences and confirmed the usefulness of our application.

Ares V Utilization in Support of a Human Mission to Mars

NASA Technical Reports Server (NTRS)

Holladay, J. B.; Jaap, J. P.; Pinson, R. M.; Creech, S. D.; Ryan, R. M.; Monk, T. S.; Baggett. K. E.; Runager, M. D.; Dux, I. J.; Hack, K. J.;

Design and Data Management System

NASA Technical Reports Server (NTRS)

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

2007-01-01

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

GATOR: Requirements capturing of telephony features

NASA Technical Reports Server (NTRS)

Dankel, Douglas D., II; Walker, Wayne; Schmalz, Mark

1992-01-01

We are developing a natural language-based, requirements gathering system called GATOR (for the GATherer Of Requirements). GATOR assists in the development of more accurate and complete specifications of new telephony features. GATOR interacts with a feature designer who describes a new feature, set of features, or capability to be implemented. The system aids this individual in the specification process by asking for clarifications when potential ambiguities are present, by identifying potential conflicts with other existing features, and by presenting its understanding of the feature to the designer. Through user interaction with a model of the existing telephony feature set, GATOR constructs a formal representation of the new, 'to be implemented' feature. Ultimately GATOR will produce a requirements document and will maintain an internal representation of this feature to aid in future design and specification. This paper consists of three sections that describe (1) the structure of GATOR, (2) POND, GATOR's internal knowledge representation language, and (3) current research issues.

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.

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.

A thermal shield concept for the Solar Probe mission

NASA Technical Reports Server (NTRS)

Miyake, Robert N.; Millard, Jerry M.; Randolph, James E.

1991-01-01

The Solar Probe spacecraft will travel to within 4 solar radii of the sun's center while performing a variety of fundamental experiments in space physics. Exposure to 2900 earth suns (400 W/sq cm) at perihelion imposes severe thermal and material demands on a solar shield system designed to protect the payload that will reside within the shield's shadow envelope or umbra. The design of the shield subsystem is a thermal/materials challenge requiring new technology development. While currently in the preproject study phase, anticipating a 1995 project start, shield preliminary design efforts are currently underway. This paper documents the current status of the mission concept, the materials issues, the configuration concept for the shield subsystem, the current configuration studies performed to date, and the required material testing to provide a database to support a design effort required to develop the shield subsystem.

Flammability, Odor, Offgassing, and Compatibility Requirements and Test Procedures for Materials in Environments that Support Combustion

NASA Technical Reports Server (NTRS)

1998-01-01

This handbook establishes NASA program requirements for evaluation, testing, and selection of materials to preclude unsafe conditions related to flammability, odor, offgassing, and fluid compatibility. Materials intended for use in space vehicles, specified test facilities, and specified ground support equipment (GSE) must meet the requirements of this document. Additional materials performance requirements may be specified in other program or NASA center specific documentation. Responsible NASA centers materials organizations must include applicable requirements of this document in their materials control programs. Materials used in habitable areas of spacecraft, including the materials of the spacecraft, stowed equipment, and experiments, must be evaluated for flammability, odor, and offgassing characteristics. All materials used in other areas must be evaluated for flammability characteristics. In addition, materials that are exposed to liquid oxygen (LOX), gaseous oxygen (GOX), and other reactive fluids' must be evaluated for compatibility with the fluid in their use application. Materials exposed to pressurized breathing gases also must be evaluated for odor and offgassing characteristics. The worst-case anticipated use environment (most hazardous pressure, temperature, material thickness, and fluid exposure conditions) must be used in the evaluation process. Materials that have been shown to meet the criteria of the required tests are acceptable for further consideration in design. Whenever possible, materials should be selected that have already been shown to meet the test criteria in the use environment. Existing test data are compiled in the NASA Marshall Space Flight Center (MSFC) Materials and Processes Technical Information System (MAPTIS) and published periodically as the latest revision of a joint document with Johnson Space Center (JSC), MSFC-HDBK-527/JSC 09604. MAPTIS can be accessed by computer datalink. Systems containing materials that have not been tested or do not meet the criteria of the required tests must be verified to be acceptable in the use configuration by analysis or testing. This verification rationale must be documented and submitted to the responsible NASA center materials organization for approval.

Mod-5A Wind Turbine Generator Program Design Report. Volume 2: Conceptual and Preliminary Design, Book 1

NASA Technical Reports Server (NTRS)

1984-01-01

The design, development and analysis of the 7.3 MW MOD-5A wind turbine generator is documented. There are four volumes. In Volume 2, book 1 the requirements and criteria for the design are presented. The conceptual design studies, which defined a baseline configuration and determined the weights, costs and sizes of each subsystem, are described. The development and optimization of the wind turbine generator are presented through the description of the ten intermediate configurations between the conceptual and final designs. Analyses of the system's load and dynamics are presented.

Software Safety Risk in Legacy Safety-Critical Computer Systems

NASA Technical Reports Server (NTRS)

Hill, Janice; Baggs, Rhoda

2007-01-01

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

Simulation Data Management - Requirements and Design Specification

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

Clay, Robert L.; Friedman-Hill, Ernest J.; Gibson, Marcus J.

Simulation Data Management (SDM), the ability to securely organize, archive, and share analysis models and the artifacts used to create them, is a fundamental requirement for modern engineering analysis based on computational simulation. We have worked separately to provide secure, network SDM services to engineers and scientists at our respective laboratories for over a decade. We propose to leverage our experience and lessons learned to help develop and deploy a next-generation SDM service as part of a multi-laboratory team. This service will be portable across multiple sites and platforms, and will be accessible via a range of command-line tools andmore » well-documented APIs. In this document, we’ll review our high-level and low-level requirements for such a system, review one existing system, and briefly discuss our proposed implementation.« less

Measure Guideline: Passive Vents

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

Berger, David; Neri, Robin

2016-02-05

This document addresses the use of passive vents as a source of outdoor air in multifamily buildings. The challenges associated with implementing passive vents and the factors affecting performance are outlined. A comprehensive design methodology and quantified performance metrics are provided. Two hypothetical design examples are provided to illustrate the process. This document is intended to be useful to designers, decision-makers, and contractors implementing passive ventilation strategies. It is also intended to be a resource for those responsible for setting high-performance building program requirements, especially pertaining to ventilation and outdoor air. To ensure good indoor air quality, a dedicated sourcemore » of outdoor air is an integral part of high-performance buildings. Presently, there is a lack of guidance pertaining to the design and installation of passive vents, resulting in poor system performance. This report details the criteria necessary for designing, constructing, and testing passive vent systems to enable them to provide consistent and reliable levels of ventilation air from outdoors.« less

Cryogenic On-Orbit Liquid Depot-Storage, Acquisition and Transfer (COLD-SAT) Experiment Conceptual Design and Feasibility Study

NASA Technical Reports Server (NTRS)

Kramer, Edward (Editor)

1998-01-01

The cryogenic fluid management technologies required for the exploration of the solar system can only be fully developed via space-based experiments. A dedicated spacecraft is the most efficient way to perform these experiments. This report documents the extended conceptual design of the COLD-SAT spacecraft, capable of meeting these experimental requirements. All elements, including the spacecraft, ground segment, launch site modifications and launch vehicle operations, and flight operations are included. Greatly expanded coverage is provided for those areas unique to this cryogenic spacecraft, such as the experiment system, attitude control system, and spacecraft operations. Supporting analyses are included as are testing requirements, facilities surveys, and proposed project timelines.

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.

Heating and Cooling System Design for a Modern Transportable Container

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

Berger, Jason E.

Sandia National Laboratories (SNL) has been tasked with the design of a modern transportable container (MTC) for use in high reliability transportation environments. The container is required to transport cargo capable of generating its own heat and operate under the United States’ climatic extremes. In response to these requirements, active heating and cooling is necessary to maintain a controlled environment inside the container. The following thesis project documents the design of an active heating, active cooling, and combined active heating and cooling system (now referred to as active heating and cooling systems) through computational thermal analyses, scoping of commercial systemmore » options, and mechanical integration with the container’s structure.« less

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

NASA Technical Reports Server (NTRS)

1976-01-01

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

Language and Program for Documenting Software Design

NASA Technical Reports Server (NTRS)

Kleine, H.; Zepko, T. M.

1986-01-01

Software Design and Documentation Language (SDDL) provides effective communication medium to support design and documentation of complex software applications. SDDL supports communication among all members of software design team and provides for production of informative documentation on design effort. Use of SDDL-generated document to analyze design makes it possible to eliminate many errors not detected until coding and testing attempted. SDDL processor program translates designer's creative thinking into effective document for communication. Processor performs as many automatic functions as possible, freeing designer's energy for creative effort. SDDL processor program written in PASCAL.

75 FR 8854 - Teacher Incentive Fund Program

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-26

...The Secretary of Education (Secretary) proposes priorities, requirements, definitions, and selection criteria under the Teacher Incentive Fund (TIF) program. These proposed priorities, requirements, definitions, and selection criteria are designed to be used in two separate and distinct TIF grant competitions: The Main TIF competition, which will provide TIF funding to eligible entities to support their implementation of performance-based compensation systems (PBCSs) in accordance with the priorities, the Main TIF requirements, the definitions, and the selection criteria proposed in this document, and the TIF Evaluation competition, which will provide, in accordance with the priorities, the Main TIF requirements, the definitions, and the selection criteria as well as the Evaluation requirements proposed in this document, TIF funding to help pay for the costs of implementing these eligible entities' PBCS in exchange for an agreement to participate in the national evaluation. The Secretary may use these proposed TIF priorities, requirements, definitions, and selection criteria in fiscal year (FY) 2010 and subsequent years. We intend the proposed priorities, requirements, definitions, and selection criteria to improve student achievement in high-need schools by creating incentives for effective teachers and principals in these schools.

Center-TRACON Automation System (CTAS) En Route Trajectory Predictor Requirements and Capabilities

NASA Technical Reports Server (NTRS)

Vivona, Robert; Cate, Karen Tung

2013-01-01

This requirements framework document is designed to support the capture of requirements and capabilities for state-of-the-art trajectory predictors (TPs). This framework has been developed to assist TP experts in capturing a clear, consistent, and cross-comparable set of requirements and capabilities. The goal is to capture capabilities (types of trajectories that can be built), functional requirements (including inputs and outputs), non-functional requirements (including prediction accuracy and computational performance), approaches for constraint relaxation, and input uncertainties. The sections of this framework are based on the Common Trajectory Predictor structure developed by the FAA/Eurocontrol Cooperative R&D Action Plan 16 Committee on Common Trajectory Prediction. It is assumed that the reader is familiar with the Common TP Structure.1 This initial draft is intended as a first cut capture of the En Route TS Capabilities and Requirements. As such, it contains many annotations indicating possible logic errors in the CTAS code or in the description provided. It is intended to work out the details of the annotations with NASA and to update this document at a later time.

Uniform Federal Accessibility Standards.

ERIC Educational Resources Information Center

Department of Housing and Urban Development, Washington, DC.

The document presents uniform standards for facility accessibility by physically handicapped persons for Federal and federally funded facilities. The standards are to be applied during the design, construction, and alteration of buildings and facilities to the extent required by the Architectural Barriers Act of 1968, as amended. Technical…

Report on Development of Specification for Design and Performance of 40 Ft. Transit Buses

DOT National Transportation Integrated Search

1971-11-01

The purpose of the specification documented in this report is to define the performance requirements of the standard vehicle--a forty foot transit coach--intended to revitalize urban bus fleets over the near-term future. The specification defines the...

Mathematics at Work in Alberta.

ERIC Educational Resources Information Center

Glanfield, Florence, Ed.; Tilroe, Daryle, Ed.

This document is designed to assist teachers by providing practical examples of real world applications of high school mathematics. Fifteen problems are presented that individuals in industry and business solve using mathematics. Each problem provides the contributor's name, suggested skills required to solve the problem, background information…

HANDBOOK: GUIDE TO TECHNICAL RESOURCES FOR THE DESIGN OF LAND DISPOSAL FACILITIES

EPA Science Inventory

This Handbook facilitates the preparation and processing of land disposal permit applications. It directs the regulated community and the regulators to the appropriate EPA technical resource documents, as they prepare or review permits required under PL 480 (RCRA). Topics discuss...

Desktop Publishing in Education.

ERIC Educational Resources Information Center

Hall, Wendy; Layman, J.

1989-01-01

Discusses the state of desktop publishing (DTP) in education today and describes the weaknesses of the systems available for use in the classroom. Highlights include document design and layout; text composition; graphics; word processing capabilities; a comparison of commercial and educational DTP packages; and skills required for DTP. (four…

Study to evaluate the integration of a mass spectrometer with a wet chemistry instrument. [for amino acid analysis

NASA Technical Reports Server (NTRS)

1974-01-01

The charactertistics and performance capability of the current Viking '75 Gas Chromatograph/Mass Spectrometer Instrument are reviewed and documented for the purpose of possible integration with a wet chemistry instrument. Interface, high mass discrimination, and vacuum requirements were determined in a simulated flight investigation. Suggestions for future investigations, tradeoff studies, and design modifications are presented, along with the results of column bleed measurements. A preliminary design of an integrated Wet Chemistry/Mass Spectrometer instrument for amino acid analysis is shown, including estimates of additional weight, volume, and power requirements.

Program Criteria Specifications Document. Computer Program TWDA for Design and Analysis of Inverted-T Retaining Walls and Floodwalls.

DTIC Science & Technology

1981-02-01

or analysis IloduIls,* each pCr forming one specific step in the design or analysis process. These modules will be callable , in any logical sequence...tempt to 1)l 1cC Cind cut of I bar, hut Will slow the required steel area and bond r i u I rl- t t)s per I oot at Uitablt intervals across the base... bond strength) shall be as required in ACI 318-71 Chapter 12, except that computed shear V shall be multiplied by 2.0 and substituted for V u. Tn