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.

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...

An Object-Based Requirements Modeling Method.

ERIC Educational Resources Information Center

Cordes, David W.; Carver, Doris L.

1992-01-01

Discusses system modeling and specification as it relates to object-based information systems development and software development. An automated system model based on the objects in the initial requirements document is described, the requirements document translator is explained, and a sample application of the technique is provided. (12…

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

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

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

1978-09-01

This document is the General Research Corporation report on Task V of a study for the Office of Inspection and Enforcement of the Nuclear Regulatory Commission (NRC/IE). The full title of this study is ''Development of Qualification Requirements, Training Programs, Career Plans, and Methodologies for Effective Management and Training of Inspection and Enforcement Personnel.'' Task V required the development of an automated personnel data base system for NRC/IE. This system is identified as the NRC/IE Personnel, Assignment, Qualifications, and Training System (PAQTS). This Task V report provides the documentation for PAQTS including the Functional Requirements Document (FRD), the Data Requirementsmore » Document (DRD), the Hardware and Software Capabilities Assessment, and the Detailed Implementation Schedule. Specific recommendations to facilitate implementation of PAQTS are also included.« 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.

42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

Code of Federal Regulations, 2011 CFR

2011-10-01

... 42 Public Health 5 2011-10-01 2011-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

Code of Federal Regulations, 2013 CFR

2013-10-01

... 42 Public Health 5 2013-10-01 2013-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

Code of Federal Regulations, 2012 CFR

2012-10-01

... 42 Public Health 5 2012-10-01 2012-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

Code of Federal Regulations, 2014 CFR

2014-10-01

... 42 Public Health 5 2014-10-01 2014-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

42 CFR 495.336 - Health information technology planning advance planning document requirements (HIT PAPD).

Code of Federal Regulations, 2010 CFR

2010-10-01

... 42 Public Health 5 2010-10-01 2010-10-01 false Health information technology planning advance... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.336 Health information technology planning advance planning document requirements...

Theater Blood Application Was Not Effectively Developed and Implemented

DTIC Science & Technology

2015-07-17

blood product by unit; and • monitor non- Food and Drug Administration Blood Product Testing. The CONOPS document also identified over 400 specific...time of a transfusion. However, this requirement was not identified in the CONOPS document. Further, PEO DHCS officials provided a traceability ...the CONOPS document, requirements management database, and the traceability matrix increased the risk that the Theater Blood Application

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.

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.

Smart roadside initiative : system requirements specifications.

DOT National Transportation Integrated Search

2015-09-01

This document describes the system requirements specifications (SyRS) for the Smart Roadside Initiative (SRI) Prototype for the delivery of capabilities related to wireless roadside inspections, electronic screening/virtual weigh stations, universal ...

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.

78 FR 22554 - Document to Support Submission of an Electronic Common Technical Document-Specifications for File...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-04-16

... documents at either http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements...Vaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm . Dated: April 10, 2013. Leslie Kux...

Dynamic mobility applications open source application development portal : Task 4 : system requirements specifications : final report.

DOT National Transportation Integrated Search

2016-10-12

This document describes the System Requirements Specifications (SyRS) of the Dynamic Mobility Applications (DMA) Open Source Application Development Portal (OSADP) system in details according to IEEE-Std. 1233-1998. The requirement statements discuss...

Atmospheric, Magnetospheric and Plasmas in space (AMPS) spacelab payload definition study. Volume 4. Part 1, AMPS program specification

NASA Technical Reports Server (NTRS)

Keeley, J. T.

1976-01-01

The AMPS Program Specification delineates the AMPS Program requirements consistent with the resources defined in the AMPS Project Plan. All subsidiary specifications and requirements shall conform to the requirements presented. The requirements hierarchy for the AMPS program is illustrated. A brief description of each of the requirements documents and their intended use is provided.

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.

222-S Laboratory Quality Assurance Plan. Revision 1

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

Meznarich, H.K.

1995-07-31

This Quality Assurance Plan provides,quality assurance (QA) guidance, regulatory QA requirements (e.g., 10 CFR 830.120), and quality control (QC) specifications for analytical service. This document follows the U.S Department of Energy (DOE) issued Hanford Analytical Services Quality Assurance Plan (HASQAP). In addition, this document meets the objectives of the Quality Assurance Program provided in the WHC-CM-4-2, Section 2.1. Quality assurance elements required in the Guidelines and Specifications for Preparing Quality Assurance Program Plans (QAMS-004) and Interim Guidelines and Specifications for Preparing Quality Assurance Project Plans (QAMS-005) from the US Environmental Protection Agency (EPA) are covered throughout this document. A qualitymore » assurance index is provided in the Appendix A. This document also provides and/or identifies the procedural information that governs laboratory operations. The personnel of the 222-S Laboratory and the Standards Laboratory including managers, analysts, QA/QC staff, auditors, and support staff shall use this document as guidance and instructions for their operational and quality assurance activities. Other organizations that conduct activities described in this document for the 222-S Laboratory shall follow this QA/QC document.« less

Department of Defense Federal Supply Classification Listing of DoD standardization Documents

DTIC Science & Technology

1989-07-01

military activities . This mandatory provision requires that the Federal and Military specifications, standards, and related standardization documents be...fiche as follows: a. DODISS Alphabetic Listing - Reflects all active documents alphabetically by nomenclature cross referenced to document number...document date, preparing activity and custodians. b. DODISS Numerical Listing - Reflects all active documents. New, revised, amended, changed and

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.

Connected Vehicle Pilot Deployment Program phase 1 : System Requirements Specification (SyRS) : Tampa (THEA) : final report.

DOT National Transportation Integrated Search

2016-08-01

This document describes the System Requirements Specification (SyRS) for the Tampa Hillsborough Expressway Authority (THEA) Connected Vehicle (CV) Pilot Deployment. This SyRS describes the current system requirements derived from the user needs, Conc...

42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

Code of Federal Regulations, 2011 CFR

2011-10-01

... 42 Public Health 5 2011-10-01 2011-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

Code of Federal Regulations, 2012 CFR

2012-10-01

... 42 Public Health 5 2012-10-01 2012-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

Code of Federal Regulations, 2014 CFR

2014-10-01

... 42 Public Health 5 2014-10-01 2014-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

Code of Federal Regulations, 2013 CFR

2013-10-01

... 42 Public Health 5 2013-10-01 2013-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

42 CFR 495.338 - Health information technology implementation advance planning document requirements (HIT IAPD).

Code of Federal Regulations, 2010 CFR

2010-10-01

... 42 Public Health 5 2010-10-01 2010-10-01 false Health information technology implementation... CERTIFICATION STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.338 Health information technology implementation advance planning document...

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.

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.

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.

Proposed GTA welding specification and acceptance criteria for the MC4163

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

Kwiatkowski, J.J.

1991-04-12

This specification documents the gas tungsten arc (GTA) welding process and production weld acceptance criteria requirements for the MC4163. This document is written specifically to apply to the welds on the MC4163 and is not to be used as a general gas tungsten arc welding specification. All sections of this specification must be complied with unless specifically exempted in writing. There are a total of five welds with three different joint designs required to fabricate the MC4163. In the order of fabrication they are (1) initiator closure disc, (2) nozzle to case girth welds, two and, (3) nozzle closure discmore » welds, two. This specification will only address the nozzle to case girth welds and the nozzle closure disc welds.« less

System Definition Document

DOT National Transportation Integrated Search

1996-06-12

The Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center : (C-TIC) System Definition Document describes the C-TIC concept and defines the : high level processes and dataflows. The Requirements Specification together : with the Inte...

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

Collision Avoidance Functional Requirements for Step 1. Revision 6

NASA Technical Reports Server (NTRS)

2006-01-01

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

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.

49 CFR 105.35 - Serving documents in PHMSA proceedings.

Code of Federal Regulations, 2010 CFR

2010-10-01

... following methods, except where a different method of service is specifically required: (1) Registered or... document by one of the following methods, except where a different method of service is specifically... at http://www.regulations.gov. [67 FR 42951, June 25, 2002, as amended at 72 FR 55682, Oct. 1, 2007] ...

42 CFR 495.340 - As-needed HIT PAPD update and as-needed HIT IAPD update requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.340 As... document or the HIT implementation advance planning document. (d) A change in implementation concept or a change to the scope of the project. (e) A change to the approved cost allocation methodology. ...

42 CFR 495.340 - As-needed HIT PAPD update and as-needed HIT IAPD update requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.340 As... document or the HIT implementation advance planning document. (d) A change in implementation concept or a change to the scope of the project. (e) A change to the approved cost allocation methodology. ...

System requirement specification for the IH-10 Integrated Corridor Management System (ICMS) in San Antonio, Texas

DOT National Transportation Integrated Search

2008-03-31

This Requirements Specification Document (RSD) was developed under the project titled TransGuide Integrated Corridor Management Stage 1 as part of the United States Department of Transportation (USDOT) Integrated Corridor Management (ICM) p...

Repository-based software engineering program: Concept document

NASA Technical Reports Server (NTRS)

1992-01-01

This document provides the context for Repository-Based Software Engineering's (RBSE's) evolving functional and operational product requirements, and it is the parent document for development of detailed technical and management plans. When furnished, requirements documents will serve as the governing RBSE product specification. The RBSE Program Management Plan will define resources, schedules, and technical and organizational approaches to fulfilling the goals and objectives of this concept. The purpose of this document is to provide a concise overview of RBSE, describe the rationale for the RBSE Program, and define a clear, common vision for RBSE team members and customers. The document also provides the foundation for developing RBSE user and system requirements and a corresponding Program Management Plan. The concept is used to express the program mission to RBSE users and managers and to provide an exhibit for community review.

Virtual Reality Transfer Protocol (VRTP): Implementing a Monitor Application for the Real-Time Transport Protocol (RTP) Using the JAVA Media Framework (JMF)

DTIC Science & Technology

1999-09-01

application, a complete specification will require one or more companion documents, as follows. 1. Profile Specification Documents A Profile...Rio de Janeiro - RJ - Brazil 21. Diretoria de Sistemas de Armas da Marinha Rua Primeiro de Marco, 118 Rio de Janeiro - RJ - Brazil CEP 20010 22

The Development and Initial Evaluation of the Human Readiness Level Framework

DTIC Science & Technology

2010-06-01

View ICD Initial Capabilities Document ICW Interactive Course Ware ILE Interactive Learning Environment ILT Instructor Led Training IOC...Programmatic Environmental Safety and Health Evaluation PHA Preliminary Hazard Analysis PHL Preliminary Hazard List xiv PM Program Manager PQS...Occupational Health SOW Statement of Work SRD System Requirements Document SPS System Performance Specification SRR System Requirements Review SVR

Sampling and Analysis Plan for U.S. Department of Energy Office of Legacy Management Sites

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

None

2012-10-24

This plan incorporates U.S. Department of Energy (DOE) Office of Legacy Management (LM) standard operating procedures (SOPs) into environmental monitoring activities and will be implemented at all sites managed by LM. This document provides detailed procedures for the field sampling teams so that samples are collected in a consistent and technically defensible manner. Site-specific plans (e.g., long-term surveillance and maintenance plans, environmental monitoring plans) document background information and establish the basis for sampling and monitoring activities. Information will be included in site-specific tabbed sections to this plan, which identify sample locations, sample frequencies, types of samples, field measurements, and associatedmore » analytes for each site. Additionally, within each tabbed section, program directives will be included, when developed, to establish additional site-specific requirements to modify or clarify requirements in this plan as they apply to the corresponding site. A flowchart detailing project tasks required to accomplish routine sampling is displayed in Figure 1. LM environmental procedures are contained in the Environmental Procedures Catalog (LMS/PRO/S04325), which incorporates American Society for Testing and Materials (ASTM), DOE, and U.S. Environmental Protection Agency (EPA) guidance. Specific procedures used for groundwater and surface water monitoring are included in Appendix A. If other environmental media are monitored, SOPs used for air, soil/sediment, and biota monitoring can be found in the site-specific tabbed sections in Appendix D or in site-specific documents. The procedures in the Environmental Procedures Catalog are intended as general guidance and require additional detail from planning documents in order to be complete; the following sections fulfill that function and specify additional procedural requirements to form SOPs. Routine revision of this Sampling and Analysis Plan will be conducted annually at the beginning of each fiscal year when attachments in Appendix D, including program directives and sampling location/analytical tables, will be reviewed by project personnel and updated. The sampling location/analytical tables in Appendix D, however, may have interim updates according to project direction that are not reflected in this plan. Deviations from location/analytical tables in Appendix D prior to sampling will be documented in project correspondence (e.g., startup letters). If significant changes to other aspects of this plan are required before the annual update, then the plan will be revised as needed.« less

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

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.

DoD’s War on Hazardous Waste. Volume 3. Identifying Specifications That Require the Use of Hazardous Substances

DTIC Science & Technology

1991-07-01

of all DoD and Federal standardization documents on file, refer to one or more of the 132 hazardous materials. Based on our... the use of the material as an option. In addition , we found 200 documents (14 percent) that specifically prohibit the use of one or more of the ...hazardous materials. Listing of standardization documents referring to chemicals are provided. We recommend more sophisticated review approaches and the provision

TOPEX Project Radar Altimeter Development Requirements and Specifications, Version 6.0

NASA Technical Reports Server (NTRS)

Rossi, Laurence C.

2003-01-01

This document provides the guidelines by which the TOPEX Radar Altimeter hardware development effort for the TOPEX flight project shall be implemented and conducted. The conduct of this activity shall take maximum advantage of the efforts expended during the TOPEX Radar Altimeter Advanced Technology Model development program and other related Radar Altimeter development efforts. This document complies with the TOPEX Project Office document 633-420 (D-2218), entitled, "TOPEX Project Requirements and Constraints for the NASA Radar Altimeter" dated December 1987.

Connected Vehicle Pilot Deployment Program Phase 1, System Requirements Specification (SyRS) – New York City.

DOT National Transportation Integrated Search

2016-07-28

This document describes the System Requirements Specification (SyRS) for the New York City Department of Transportation (NYC) Connected Vehicle Pilot Deployment (CVPD) Project. This SyRS describes the results of the definition of need, the operationa...

System requirement specification for the I-15 integrated corridor management system (ICMS) in San Diego, California.

DOT National Transportation Integrated Search

2008-03-31

This document presents a System Requirement Specification for an Integrated Corridor Management System (ICMS) in the I-15 Corridor in San Diego, California. The ICMS will consist of two major subsystems: the existing Intermodal Transportation Managem...

High-Speed Maglev Trains; German Safety Requirements

DOT National Transportation Integrated Search

1991-12-31

This document is a translation of technology-specific safety requirements developed : for the German Transrapid Maglev technology. These requirements were developed by a : working group composed of representatives of German Federal Railways (DB), Tes...

Using resources for scientific-driven pharmacovigilance: from many product safety documents to one product safety master file.

PubMed

Furlan, Giovanni

2012-08-01

Current regulations require a description of the overall safety profile or the specific risks of a drug in multiple documents such as the Periodic and Development Safety Update Reports, Risk Management Plans (RMPs) and Signal Detection Reports. In a resource-constrained world, the need for preparing multiple documents reporting the same information results in shifting the focus from a thorough scientific and medical evaluation of the available data to maintaining compliance with regulatory timelines. Since the aim of drug safety is to understand and characterize product issues to take adequate risk minimization measures rather than to comply with bureaucratic requirements, there is the need to avoid redundancy. In order to identify core drug safety activities that need to be undertaken to protect patient safety and reduce the number of documents reporting the results of these activities, the author has reviewed the main topics included in the drug safety guidelines and templates. The topics and sources that need to be taken into account in the main regulatory documents have been found to greatly overlap and, in the future, as a result of the new Periodic Safety Update Report structure and requirements, in the author's opinion this overlap is likely to further increase. Many of the identified inter-document differences seemed to be substantially formal. The Development Safety Update Report, for example, requires separate presentation of the safety issues emerging from different sources followed by an overall evaluation of each safety issue. The RMP, instead, requires a detailed description of the safety issues without separate presentation of the evidence derived from each source. To some extent, however, the individual documents require an in-depth analysis of different aspects; the RMP, for example, requires an epidemiological description of the indication for which the drug is used and its risks. At the time of writing this article, this is not specifically required by other documents. The author has identified signal detection (intended not only as adverse event disproportionate reporting, but including non-clinical, laboratory, clinical analysis data and literature screening) and characterization as the basis for the preparation of all drug safety documents, which can be viewed as different ways of presenting the results of this activity. Therefore, the author proposes to merge all the aggregate reports required by current regulations into a single document - the Drug Safety Master File. This report should contain all the available information, from any source, regarding the potential and identified risks of a drug. It should be a living document updated and submitted to regulatory authorities on an ongoing basis.

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

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.

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

Guyer, H.B.; McChesney, C.A.

The overall primary Objective of HDAR is to create a repository of historical personnel security documents and provide the functionality needed for archival and retrieval use by other software modules and application users of the DISS/ET system. The software product to be produced from this specification is the Historical Document Archival and Retrieval Subsystem The product will provide the functionality to capture, retrieve and manage documents currently contained in the personnel security folders in DOE Operations Offices vaults at various locations across the United States. The long-term plan for DISS/ET includes the requirement to allow for capture and storage ofmore » arbitrary, currently undefined, clearance-related documents that fall outside the scope of the ``cradle-to-grave`` electronic processing provided by DISS/ET. However, this requirement is not within the scope of the requirements specified in this document.« less

One Methodology for Proving Compliance to the Commercial Crew Program (CCP) Abort Capability Requirement

NASA Technical Reports Server (NTRS)

Proud, Ryan; Adam, Jason

2011-01-01

As of Draft 4.0 of the CCT-REQ-1130 requirements document for CCP, ISS Crew Transportation and Services Requirements Document, specific language for the verification of the abort capability requirement, 3.3.1.4, was added. The abort capability requirement ensures that the CTS under dispersed conditions is always capable of aborting from a failed LV. The Integrated Aborts IPT was asked to author a memo for how this verification might be completed. The following memo dictates one way that this requirement and its verification could be met, but this is the not the only method.

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.

Experiment Document for 01-E077 Microgravity Investigation of Crew Reactions in 0-G (MICRO-G)

NASA Technical Reports Server (NTRS)

Newman, Dava J.

2003-01-01

The Experiment Document (ED) serves the following purposes: a) It provides a vehicle for Principal Investigators (PIS) to formally specify the requirements for performing their experiments. b) It provides a technical Statement of Work (SOW). c) It provides experiment investigators and hardware developers with a convenient source of information about Human Life Sciences (HLS) requirements for the development and/or integration of flight experiment projects. d) It is the primary source of experiment specifications for the HLS Research Program Office (RPO). Inputs from this document will be placed into a controlled database that will be used to generate other documents.

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.

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.

International Space Station Human Behavior and Performance Competency Model: Volume II

NASA Technical Reports Server (NTRS)

Schmidt, Lacey

2008-01-01

This document further defines the behavioral markers identified in the document "Human Behavior and Performance Competency Model" Vol. I. The Human Behavior and Performance (HBP) competencies were recommended as requirements to participate in international long duration missions, and form the basis for determining the HBP training curriculum for long duration crewmembers. This document provides details, examples, knowledge areas, and affective skills to support the use of the HBP competencies in training and evaluation. This document lists examples and details specific to HBP competencies required of astronauts/cosmonauts who participate in ISS expedition and other international long-duration missions. Please note that this model does not encompass all competencies required. While technical competencies are critical for crewmembers, they are beyond the scope of this document. Additionally, the competencies in this model (and subsequent objectives) are not intended to limit the internal activities or training programs of any international partner.

ASTP experiment support data processing

NASA Technical Reports Server (NTRS)

Osburn, R. K.; Barnett, E. L.; Moore, H. L.; Moore, J. B.; Ball, J. R.

1975-01-01

Activities associated with the generation of ASTP experiment support data in the areas of spacecraft ephemeris and orientation and instrument pointing and field-of-view are documented. It is intended that this document represent a cradle-to-grave chronicle of these activities. To satisfy this intent while facilitating the ready dissemination of information, the document is being published twice. The first publication, scheduled for release prior to ASTP liftoff, includes all preflight phases of the experiment support activity in addition to those appendixes that do not pertain to any mission-specific data. The second publication will provide any required updates to the original documentation and will add all mission-specific data, including documentation of all postflight data processing activities and data archiving information.

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.

Functional Requirements for an Electronic Work Package System

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

Oxstrand, Johanna H.

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

Review of the Constellation Level II Safety, Reliability, and Quality Assurance (SR&QA) Requirements Documents during Participation in the Constellation Level II SR&QA Forum

NASA Technical Reports Server (NTRS)

Cameron, Kenneth D.; Gentz, Steven J.; Beil, Robert J.; Minute, Stephen A.; Currie, Nancy J.; Scott, Steven S.; Thomas, Walter B., III; Smiles, Michael D.; Schafer, Charles F.; Null, Cynthia H.;

Potential to Emit (PTE) Guidance for Specific Source Categories

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.

Dry Creek Joint Elementary School District. Educational Specifications: Dry Creek Middle School.

ERIC Educational Resources Information Center

Dry Creek Joint Elementary School District, Roseville, CA.

An Educational Specification Committee was convened to determine the design specifications required for a new middle school in Roseville, California's Dry Creek District. This report presents revisions to an earlier document that examined school room specifications for each grade level and administrative area. Specification considerations are…

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...

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.

Instrument constraints and interface specifications. Earth Observatory Satellite system definition study (EOS)

NASA Technical Reports Server (NTRS)

1974-01-01

The equipment specifications for the thematic mapper and high resolution pointable imager for use on the Earth Observatory Satellite (EOS) are presented. The interface requirements of the systems are defined. The interface requirements are extracted from the equipment specifications and are intended as a summary to be used by the system and spacecraft designer. The appropriate documentation from which the specifications of the equipment are established are identified.

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.

Voyager electronic parts radiation program. Volume 2: Test requirements and procedures

NASA Technical Reports Server (NTRS)

Stanley, A. G.; Martin, K. E.; Price, W. E.

1978-01-01

Documents are presented outlining the conditions and requirements of the test program. The Appendixes are as follows: appendix A -- Electron Simulation Radiation Test Specification for Voyager Electronic Parts and Devices, appendix B -- Electronic Piece-Part Testing Program for Voyager, appendix C -- Test Procedure for Radiation Screening of Voyager Piece Parts, appendix D -- Boeing In Situ Test Fixture, and appendix E -- Irradiate - Anneal (IRAN) Screening Documents.

Region 7 Quality Management Plan

EPA Pesticide Factsheets

To document adherence to EPA Order 5360.1 A2, EPA requires each organizational unitto develop a quality management plan per the specifications in EPA Requirements for QualityManagement Plans, EPA QA R-2.

Phase 111A Crew Interface Specifications Development for Inflight Maintenance and Stowage Functions

NASA Technical Reports Server (NTRS)

Carl, John G.

1973-01-01

This report presents the findings and data products developed during the Phase IIIA Crew Interface Specification Study for Inflight Maintenance and Stowage Functions, performed by General Electric for the NASA, Johnson Space Center with a set of documentation that can be used as definitive guidelines to improve the present process of defining, controlling and managing flight crew interface requirements that are related to inflight maintenance (including assembly and servicing) and stowage functions. During the Phase IIIA contract period, the following data products were developed: 1) Projected NASA Crew Procedures/Flight Data File Development Process. 2) Inflight Maintenance Management Process Description. 3) Preliminary Draft, General Specification, Inflight Maintenance Management Requirements. 4) Inflight Maintenance Operational Process Description. 5) Preliminary Draft, General Specification, Inflight Maintenance Task and Support Requirements Analysis. 6) Suggested IFM Data Processing Reports for Logistics Management The above Inflight Maintenance data products have been developed during the Phase IIIA study after review of Space Shuttle Program Documentation, including the Level II Integrated Logistics Requirements and other DOD and NASA data relative to Payloads Accommodations and Satellite On-Orbit Servicing. These Inflight Maintenance data products were developed to be in consonance with Space Shuttle Program technical and management requirements.

42 CFR 495.328 - Request for reconsideration of adverse determination.

Code of Federal Regulations, 2010 CFR

2010-10-01

... RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the Medicaid Program § 495.328 Request for... planning document or State Medicaid HIT Plan under this subpart, or determines that requirements are met...

Facilitating access to information in large documents with an intelligent hypertext system

NASA Technical Reports Server (NTRS)

Mathe, Nathalie

1993-01-01

Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation) and tested it on the Space Station Freedom requirement documents. The CID system enables integration of various technical documents in a hypertext framework and includes an intelligent context-sensitive indexing and retrieval mechanism. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time.

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).

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.'

Development of requirements and functional specifications for crash event data recorders : final report

DOT National Transportation Integrated Search

2004-12-01

The U.S. DOT has conducted research on the requirements for a Crash Event Data Recorder to facilitate the reconstruction of commercial motor vehicle crashes. This report documents the work performed on the Development of Requirements and Functiona...

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.

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.

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...

Computer-Aided Discovery of Formal Specification Behavioral Requirements and Requirement to Implementation Mappings

DTIC Science & Technology

2014-01-01

the executable SRM is developed according to the specification and marketing documents. Hence, for example, the Vehicles, Car, and Truck classes in...transitions ternary relation: transitions ⊆ states x transitionIDs x states, such as <"Init", "Tr1", " stP "> • A conditions unary relation bound to

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.

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

Integrated Advanced Microwave Sounding Unit-A (AMSU-A). Test Report, Electromagnetic Interference (EMI)/Electromagnetic Radiation(EMR) and Electromagnetic Capability (EMC) for the EOS/AMSU-A1

NASA Technical Reports Server (NTRS)

Paliwoda, L.

1998-01-01

This document contains the procedure and the test results of the Advanced Microwave Sounding Unit-A (AMSU-A) Earth Observing System (EOS) Project, assembly part number 1356008-1, serial number 202, Electromagnetic Interference (EMI) and Electromagnetic Susceptibility (EMC) qualification test. The test was conducted in accordance with the approved EMI/EMC Test Plan/Procedure, Specification number AE-26151/8B, dated 10 September 1998. Aerojet intends that the presentation and submittal of this document, prepared in accordance with the objectives established by the aforementioned Test Plan/Procedure, document number AE-26151/8B, will satisfy the data requirement with respect to the AMSU-A/EOS instrument operational compliance of the EMI/EMC test requirement. Test for the AMSU-A/EOS instrument have been completed and all the requirements per General Interface Requirement Document (GIRD), GSFC 422-11-12-01, for EOS Common Spacecraft/Instruments, paragraph 10.11, were met with the exceptions of the test methods CE03, RE01, and RE02, as described in this document.

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...

40 CFR 62.14620 - What site-specific documentation is required?

Code of Federal Regulations, 2011 CFR

2011-07-01

... POLLUTANTS Federal Plan Requirements for Commercial and Industrial Solid Waste Incineration Units That...) Procedures for receiving, handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction... limits. (7) Reporting and recordkeeping procedures. (8) The waste management plan required under §§ 62...

Comparative Analysis of the Specifications on the Power Quality of the European Union and the Russian Federation

NASA Astrophysics Data System (ADS)

Ded, A. V.; Maltsev, V. N.; Sikorski, S. P.

2018-04-01

Since July 2014 the interstate standard GOST 32144-2013 is the only document that defines standard requirements for the power quality in the territory of the Russian Federation. The new standard preamble specifies that this document considers the requirements of the European regional standard EN 50160-2010. However, GOST authors established the degree of standards conformity as nonequivalent. In connection with Russia's accession to the World Trade Organization (WTO) all requirements for goods including electric energy should correspond the international standard requirements. The article analyzes the above standard requirements and assesses the requirements for the power quality standards used in the European Union and in the Russian Federation.

24 CFR 1710.209 - Title and land use.

Code of Federal Regulations, 2010 CFR

2010-04-01

... all public records which may contain documents affecting title to the land or the developer's ability... cases, the required statement shall clearly reflect the documents and periods searched. (e) Items to be... include specific references to the instruments in the public records upon which they are based). When an...

Earth Observing System/Meteorological Satellite (EOS/METSAT). Advanced Microwave Sounding Unit-A (AMSU-A) Contamination Control Plan

NASA Technical Reports Server (NTRS)

Fay, M.

1998-01-01

This Contamination Control Plan is submitted in response the Contract Document requirements List (CDRL) 007 under contract NAS5-32314 for the Earth Observing System (EOS) Advanced Microwave Sounding Unit A (AMSU-A). In response to the CDRL instructions, this document defines the level of cleanliness and methods/procedures to be followed to achieve adequate cleanliness/contamination control, and defines the required approach to maintain cleanliness/contamination control through shipping, observatory integration, test, and flight. This plan is also applicable to the Meteorological Satellite (METSAT) except where requirements are identified as EOS-specific. This plan is based on two key factors: a. The EOS/METSAT AMSU-A Instruments are not highly contamination sensitive. b. Potential contamination of other EOS Instruments is a key concern as addressed in Section 9/0 of the Performance Assurance Requirements for EOS/METSAT Integrated Programs AMSU-A Instrument (MR) (NASA Specification S-480-79).

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.

Faying Surface Lubrication Effects on Nut Factors

NASA Technical Reports Server (NTRS)

Taylor, Deneen M.; Morrison, Raymond F.

2006-01-01

Bolted joint analysis typically is performed using nut factors derived from textbooks and procedures from program requirement documents. Joint specific testing was performed for a critical International Space Station (ISS) joint. Test results indicate that for some configurations the nut factor may be significantly different than accepted textbook values. This paper presents results of joint specific testing to aid in determining if joint specific testing should be performed to insure required preloads are obtained.

A computer-based specification methodology

NASA Technical Reports Server (NTRS)

Munck, Robert G.

1986-01-01

Standard practices for creating and using system specifications are inadequate for large, advanced-technology systems. A need exists to break away from paper documents in favor of documents that are stored in computers and which are read and otherwise used with the help of computers. An SADT-based system, running on the proposed Space Station data management network, could be a powerful tool for doing much of the required technical work of the Station, including creating and operating the network itself.

78 FR 16825 - Approval of Air Quality Implementation Plans; Navajo Nation; Regional Haze Requirements for...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-03-19

... Quality Implementation Plans; Navajo Nation; Regional Haze Requirements for Navajo Generating Station... source-specific federal implementation plan (FIP) requiring the Navajo Generating Station (NGS), located... . SUPPLEMENTARY INFORMATION: Throughout this document, ``we'', ``us'', and ``our'' refer to EPA. Table of Contents...

Quarantine provisions for unmanned extra-terrestrial missions

NASA Technical Reports Server (NTRS)

1976-01-01

This document sets forth requirements applicable to unmanned planetary flight programs which are necessary to enable the Associate Administrator for Space Science to fulfill those responsibilities pertaining to planetary quarantine as stated in NPD 8020.7 and NPD 8020.10A. This document is specifically directed to the control of terrestrial microbial contamination associated with unmanned space vehicles intended to encounter, orbit, flyby, or otherwise be in the vicinity of extra-terrestrial solar system bodies. The requirements of this document apply to all unmanned planetary flight programs. This includes solar system exploratory missions to the major planets as well as missions to planet satellites, or to other solar system objects that may be of scientific interest. This document is not applicable to terrestrial (including lunar) missions and manned missions. NASA officials having cognizance of applicable flight programs will invoke these requirements in such directives or contractual instruments as may be necessary to assure their implementation.

TRACER - TRACING AND CONTROL OF ENGINEERING REQUIREMENTS

NASA Technical Reports Server (NTRS)

Turner, P. R.

1994-01-01

TRACER (Tracing and Control of Engineering Requirements) is a database/word processing system created to document and maintain the order of both requirements and descriptive material associated with an engineering project. A set of hierarchical documents are normally generated for a project whereby the requirements of the higher level documents levy requirements on the same level or lower level documents. Traditionally, the requirements are handled almost entirely by manual paper methods. The problem with a typical paper system, however, is that requirements written and changed continuously in different areas lead to misunderstandings and noncompliance. The purpose of TRACER is to automate the capture, tracing, reviewing, and managing of requirements for an engineering project. The engineering project still requires communications, negotiations, interactions, and iterations among people and organizations, but TRACER promotes succinct and precise identification and treatment of real requirements separate from the descriptive prose in a document. TRACER permits the documentation of an engineering project's requirements and progress in a logical, controllable, traceable manner. TRACER's attributes include the presentation of current requirements and status from any linked computer terminal and the ability to differentiate headers and descriptive material from the requirements. Related requirements can be linked and traced. The program also enables portions of documents to be printed, individual approval and release of requirements, and the tracing of requirements down into the equipment specification. Requirement "links" can be made "pending" and invisible to others until the pending link is made "binding". Individuals affected by linked requirements can be notified of significant changes with acknowledgement of the changes required. An unlimited number of documents can be created for a project and an ASCII import feature permits existing documents to be incorporated. TRACER can automatically renumber section headers when inserting or deleting sections of a document and generate sign-off forms for any approval process as well as a table of contents. TRACER was implemented on an IBM PC under PC-DOS. The program requires 640K RAM, a hard disk, and PC-DOS version 3.3 or higher. It was written in CLIPPER (Summer '87). TRACER is available on two 5.25 inch 1.2Mb MS-DOS format diskettes. The executable program is also provided with the distribution. TRACER is a copyrighted work with all copyright vested in the National Aeronautics and Space Administration. IBM PC and PC-DOS are registered trademarks of International Business Machines. CLIPPER is a trademark of Nantucket Corporation.

Use of a structured template to facilitate practice-based learning and improvement projects.

PubMed

McClain, Elizabeth K; Babbott, Stewart F; Tsue, Terance T; Girod, Douglas A; Clements, Debora; Gilmer, Lisa; Persons, Diane; Unruh, Greg

2012-06-01

The Accreditation Council for Graduate Medical Education (ACGME) requires residency programs to meet and demonstrate outcomes across 6 competencies. Measuring residents' competency in practice-based learning and improvement (PBLI) is particularly challenging. We developed an educational tool to meet ACGME requirements for PBLI. The PBLI template helped programs document quality improvement (QI) projects and supported increased scholarly activity surrounding PBLI learning. We reviewed program requirements for 43 residency and fellowship programs and identified specific PBLI requirements for QI activities. We also examined ACGME Program Information Form responses on PBLI core competency questions surrounding QI projects for program sites visited in 2008-2009. Data were integrated by a multidisciplinary committee to develop a peer-protected PBLI template guiding programs through process, documentation, and evaluation of QI projects. All steps were reviewed and approved through our GME Committee structure. An electronic template, companion checklist, and evaluation form were developed using identified project characteristics to guide programs through the PBLI process and facilitate documentation and evaluation of the process. During a 24 month period, 27 programs have completed PBLI projects, and 15 have reviewed the template with their education committees, but have not initiated projects using the template. The development of the tool generated program leaders' support because the tool enhanced the ability to meet program-specific objectives. The peer-protected status of this document for confidentiality and from discovery has been beneficial for program usage. The document aggregates data on PBLI and QI initiatives, offers opportunities to increase scholarship in QI, and meets the ACGME goal of linking measures to outcomes important to meeting accreditation requirements at the program and institutional level.

Use of a Structured Template to Facilitate Practice-Based Learning and Improvement Projects

PubMed Central

McClain, Elizabeth K.; Babbott, Stewart F.; Tsue, Terance T.; Girod, Douglas A.; Clements, Debora; Gilmer, Lisa; Persons, Diane; Unruh, Greg

2012-01-01

Background The Accreditation Council for Graduate Medical Education (ACGME) requires residency programs to meet and demonstrate outcomes across 6 competencies. Measuring residents' competency in practice-based learning and improvement (PBLI) is particularly challenging. Purpose We developed an educational tool to meet ACGME requirements for PBLI. The PBLI template helped programs document quality improvement (QI) projects and supported increased scholarly activity surrounding PBLI learning. Methods We reviewed program requirements for 43 residency and fellowship programs and identified specific PBLI requirements for QI activities. We also examined ACGME Program Information Form responses on PBLI core competency questions surrounding QI projects for program sites visited in 2008–2009. Data were integrated by a multidisciplinary committee to develop a peer-protected PBLI template guiding programs through process, documentation, and evaluation of QI projects. All steps were reviewed and approved through our GME Committee structure. Results An electronic template, companion checklist, and evaluation form were developed using identified project characteristics to guide programs through the PBLI process and facilitate documentation and evaluation of the process. During a 24 month period, 27 programs have completed PBLI projects, and 15 have reviewed the template with their education committees, but have not initiated projects using the template. Discussion The development of the tool generated program leaders' support because the tool enhanced the ability to meet program-specific objectives. The peer-protected status of this document for confidentiality and from discovery has been beneficial for program usage. The document aggregates data on PBLI and QI initiatives, offers opportunities to increase scholarship in QI, and meets the ACGME goal of linking measures to outcomes important to meeting accreditation requirements at the program and institutional level. PMID:23730444

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.

Purple Computational Environment With Mappings to ACE Requirements for the General Availability User Environment Capabilities

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

Barney, B; Shuler, J

2006-08-21

Purple is an Advanced Simulation and Computing (ASC) funded massively parallel supercomputer located at Lawrence Livermore National Laboratory (LLNL). The Purple Computational Environment documents the capabilities and the environment provided for the FY06 LLNL Level 1 General Availability Milestone. This document describes specific capabilities, tools, and procedures to support both local and remote users. The model is focused on the needs of the ASC user working in the secure computing environments at Los Alamos National Laboratory, Lawrence Livermore National Laboratory, and Sandia National Laboratories, but also documents needs of the LLNL and Alliance users working in the unclassified environment. Additionally,more » the Purple Computational Environment maps the provided capabilities to the Trilab ASC Computing Environment (ACE) Version 8.0 requirements. The ACE requirements reflect the high performance computing requirements for the General Availability user environment capabilities of the ASC community. Appendix A lists these requirements and includes a description of ACE requirements met and those requirements that are not met for each section of this document. The Purple Computing Environment, along with the ACE mappings, has been issued and reviewed throughout the Tri-lab community.« less

Study of solid rocket motors for a space shuttle booster. Appendix B: Prime item development specification

NASA Technical Reports Server (NTRS)

1972-01-01

The specifications for the performance, design, development, and test requirements of the P2-156, S3-156, and S6-120 space shuttle booster solid rocket motors are presented. The applicable documents which form a part of the specifications are listed.

Specification for Qualification and Certification for Entry Level Welders.

ERIC Educational Resources Information Center

American Welding Society, Miami, FL.

This document provides a standard that defines the requirements and program for the American Welding Society to certify entry-level welders. The certification of entry-level welders requires performance qualification and practical knowledge tests that require a minimum of reading, computation, and manual skills to complete. The Entry-Level Welder…

Saint Lawrence Seaway Navigation-Aid System Study : Volume III - Appendix C - User's Manual and Documentation of the Ship Maneuvering Requirements Computer Program

DOT National Transportation Integrated Search

1978-09-01

The requirements for a navigation guidance system which will effect an increase in the ship processing capacity of the Saint Lawrence Seaway (Lake Ontario to Montreal, Quebec) are developed. The requirements include a specification of system position...

The Role of CMR and Others in Project Implementation using the CM Method to Support the Government

NASA Astrophysics Data System (ADS)

Tada, Hiroshi; Miyatake, Ichiro; Mouri, Junji; Endo, Kenji; Fueta, Toshiharu

In Japan, the construction management (CM) method has been introduced as a measure to support the governmental agencies, in developing and maintaining local infrastructures, or in executing public works projects in an appropriate manner, etc. The scope of work of the Construction Manager (CMR) of the CM method is specified as work items, in the special specification document for CM services contained in the contract documents, as a reflection of the client's expectations towards the performance of CMR. However, the CM services has been conducted as required on a case-by-case basis, because it is not possible to anticipate the actual construction status in advance, and thus the special specification document does not provide full detail of the scope of work of CMR. In such case, there may be a difference in the way the scope of work in the special specification document is recognized between the client and the CMR, which could make the CM method less effective. Moreover, there is a case in which the role sharing between the client and the CMR is not clearly defined, and both parties may engage in the same task in such case, causing an obstacle for smooth project implementation. For this reason, it is required to prepare the special specification document which clearly defines the scope of work of CMR, by examining the status of application of the CM method in actual project cases, and to improve the practices of the CM method as necessary. In view of this background, this study looks in to the actual project cases using the CM method, for the purpose of clarifying the actual scope of work of CMR for each task item defined in the special specification document, and the role sharing between the client and CMR, in the aim of contributing the promotion of the use and the effective application of the CM method.

Guidance on validation and qualification of processes and operations involving radiopharmaceuticals.

PubMed

Todde, S; Peitl, P Kolenc; Elsinga, P; Koziorowski, J; Ferrari, V; Ocak, E M; Hjelstuen, O; Patt, M; Mindt, T L; Behe, M

2017-01-01

Validation and qualification activities are nowadays an integral part of the day by day routine work in a radiopharmacy. This document is meant as an Appendix of Part B of the EANM "Guidelines on Good Radiopharmacy Practice (GRPP)" issued by the Radiopharmacy Committee of the EANM, covering the qualification and validation aspects related to the small-scale "in house" preparation of radiopharmaceuticals. The aim is to provide more detailed and practice-oriented guidance to those who are involved in the small-scale preparation of radiopharmaceuticals which are not intended for commercial purposes or distribution. The present guideline covers the validation and qualification activities following the well-known "validation chain", that begins with editing the general Validation Master Plan document, includes all the required documentation (e.g. User Requirement Specification, Qualification protocols, etc.), and leads to the qualification of the equipment used in the preparation and quality control of radiopharmaceuticals, until the final step of Process Validation. A specific guidance to the qualification and validation activities specifically addressed to small-scale hospital/academia radiopharmacies is here provided. Additional information, including practical examples, are also available.

a Restoration Oriented Hbim System for Cultural Heritage Documentation: the Case Study of Parma Cathedral

NASA Astrophysics Data System (ADS)

Bruno, N.; Roncella, R.

2018-05-01

The need to safeguard and preserve Cultural Heritage (CH) is increasing and especially in Italy, where the amount of historical buildings is considerable, having efficient and standardized processes of CH management and conservation becomes strategic. At the time being, there are no tools capable of fulfilling all the specific functions required by Cultural Heritage documentation and, due to the complexity of historical assets, there are no solution as flexible and customizable as CH specific needs require. Nevertheless, BIM methodology can represent the most effective solution, on condition that proper methodologies, tools and functions are made available. The paper describes an ongoing research on the implementation of a Historical BIM system for the Parma cathedral, aimed at the maintenance, conservation and restoration. Its main goal was to give a concrete answer to the lack of specific tools required by Cultural Heritage documentation: organized and coordinated storage and management of historical data, easy analysis and query, time management, 3D modelling of irregular shapes, flexibility, user-friendliness, etc. The paper will describe the project and the implemented methodology, focusing mainly on survey and modelling phases. In describing the methodology, critical issues about the creation of a HBIM will be highlighted, trying to outline a workflow applicable also in other similar contexts.

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.

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.

Space Launch System (SLS) Mission Planner's Guide

NASA Technical Reports Server (NTRS)

Smith, David Alan

2017-01-01

The purpose of this Space Launch System (SLS) Mission Planner's Guide (MPG) is to provide future payload developers/users with sufficient insight to support preliminary SLS mission planning. Consequently, this SLS MPG is not intended to be a payload requirements document; rather, it organizes and details SLS interfaces/accommodations in a manner similar to that of current Expendable Launch Vehicle (ELV) user guides to support early feasibility assessment. Like ELV Programs, once approved to fly on SLS, specific payload requirements will be defined in unique documentation.

W-320 Department of Health documentation

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

Bailey, J.W.

1998-08-07

The purpose of this document is to gather information required to show that Project W-320 is in compliance with Washington State Department of Health requirements as specified in Radioactive Air Emissions Notice of Construction Project W-320, Tank 241-C-106 Sluicing, DOE/RL-95-45. Specifically, that W-320 is in compliance with ASME N509-1989 (Nuclear Power Plant Air-Cleaning Units and Components) and ASME N5 10-1989 (Testing of Nuclear Air Treatment Systems) for the 296-C-006 exhaust 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

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.

Response to Specific Questions on Interstate Trading and New Source Review (NSR) Under the Nitrogen Oxides (NOx) Emissions Budget Concept

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.

40 CFR 62.14620 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

... the incinerator and associated air pollution control systems within the standards established under... required? 62.14620 Section 62.14620 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED...) Procedures for receiving, handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction...

Dry Creek Joint Elementary School District. Educational Specifications: K-5 Permanent (Revised 1998).

ERIC Educational Resources Information Center

Dry Creek Joint Elementary School District, Roseville, CA.

An Educational Specification Committee was convened to determine the design specifications required for a new K-5 (and temporarily 6-8 grade) elementary school in Roseville, California's Dry Creek District. This report presents revisions to an earlier document that examined school room specifications for each grade level and administrative area.…

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

NASA Technical Reports Server (NTRS)

Wilber, George F.

2017-01-01

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

40 CFR 60.2910 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

... the incinerator and associated air pollution control systems within the standards established under... required? 60.2910 Section 60.2910 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR...) Procedures for receiving, handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction...

40 CFR 60.2660 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

... required? 60.2660 Section 60.2660 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR..., handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction procedures. (4) Procedures for maintaining proper combustion air supply levels. (5) Procedures for operating the incinerator and...

40 CFR 60.2095 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

.... (5) Procedures for operating the incinerator and associated air pollution control systems within the... incinerator operating limits. (7) Reporting and recordkeeping procedures. (8) The waste management plan... required? 60.2095 Section 60.2095 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR...

40 CFR 60.3019 - What site-specific documentation is required?

Code of Federal Regulations, 2010 CFR

2010-07-01

... required? 60.3019 Section 60.3019 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) AIR...) Incinerator startup, shutdown, and malfunction procedures. (4) Procedures for maintaining proper combustion air supply levels. (5) Procedures for operating the incinerator and associated air pollution control...

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

None

This document provides guidance for retrofitting existing fluorescent troffers including the LED and associated control options available, the pro/cons and costs/benefits of each option, and agency specific requirements (where applicable).

Product Structure, the Heart of Product Definition

NASA Technical Reports Server (NTRS)

DeHoog, C., Jr.

1999-01-01

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

The National Map seamless digital elevation model specifications

USGS Publications Warehouse

Archuleta, Christy-Ann M.; Constance, Eric W.; Arundel, Samantha T.; Lowe, Amanda J.; Mantey, Kimberly S.; Phillips, Lori A.

2017-08-02

This specification documents the requirements and standards used to produce the seamless elevation layers for The National Map of the United States. Seamless elevation data are available for the conterminous United States, Hawaii, Alaska, and the U.S. territories, in three different resolutions—1/3-arc-second, 1-arc-second, and 2-arc-second. These specifications include requirements and standards information about source data requirements, spatial reference system, distribution tiling schemes, horizontal resolution, vertical accuracy, digital elevation model surface treatment, georeferencing, data source and tile dates, distribution and supporting file formats, void areas, metadata, spatial metadata, and quality assurance and control.

Advanced information processing system: Input/output network management software

NASA Technical Reports Server (NTRS)

Nagle, Gail; Alger, Linda; Kemp, Alexander

1988-01-01

The purpose of this document is to provide the software requirements and specifications for the Input/Output Network Management Services for the Advanced Information Processing System. This introduction and overview section is provided to briefly outline the overall architecture and software requirements of the AIPS system before discussing the details of the design requirements and specifications of the AIPS I/O Network Management software. A brief overview of the AIPS architecture followed by a more detailed description of the network architecture.

Analysis of a risk prevention document using dependability techniques: a first step towards an effectiveness model

NASA Astrophysics Data System (ADS)

Ferrer, Laetitia; Curt, Corinne; Tacnet, Jean-Marc

2018-04-01

Major hazard prevention is a main challenge given that it is specifically based on information communicated to the public. In France, preventive information is notably provided by way of local regulatory documents. Unfortunately, the law requires only few specifications concerning their content; therefore one can question the impact on the general population relative to the way the document is concretely created. Ergo, the purpose of our work is to propose an analytical methodology to evaluate preventive risk communication document effectiveness. The methodology is based on dependability approaches and is applied in this paper to the Document d'Information Communal sur les Risques Majeurs (DICRIM; in English, Municipal Information Document on Major Risks). DICRIM has to be made by mayors and addressed to the public to provide information on major hazards affecting their municipalities. An analysis of law compliance of the document is carried out thanks to the identification of regulatory detection elements. These are applied to a database of 30 DICRIMs. This analysis leads to a discussion on points such as usefulness of the missing elements. External and internal function analysis permits the identification of the form and content requirements and service and technical functions of the document and its components (here its sections). Their results are used to carry out an FMEA (failure modes and effects analysis), which allows us to define the failure and to identify detection elements. This permits the evaluation of the effectiveness of form and content of each components of the document. The outputs are validated by experts from the different fields investigated. Those results are obtained to build, in future works, a decision support model for the municipality (or specialised consulting firms) in charge of drawing up documents.

HALE UAS Concept of Operations. Version 3.0

NASA Technical Reports Server (NTRS)

2006-01-01

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

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

NASA Technical Reports Server (NTRS)

1976-01-01

General physical, functional, and operational interface control requirements for instruments on the first AMPS payload are presented. Interface specifications are included to satisfy ground handling, prelaunch, launch, stowage, operation, and landing activities. Applicable supporting documentation to implement the information is also given.

Solid waste information and tracking system server conversion project management plan

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

MAY, D.L.

1999-04-12

The Project Management Plan governing the conversion of Solid Waste Information and Tracking System (SWITS) to a client-server architecture. The Solid Waste Information and Tracking System Project Management Plan (PMP) describes the background, planning and management of the SWITS conversion. Requirements and specification documentation needed for the SWITS conversion will be released as supporting documents.

How to become a competent medical writer?

PubMed

Sharma, Suhasini

2010-01-01

Medical writing involves writing scientific documents of different types which include regulatory and research-related documents, disease or drug-related educational and promotional literature, publication articles like journal manuscripts and abstracts, content for healthcare websites, health-related magazines or news articles. The scientific information in these documents needs to be presented to suit the level of understanding of the target audience, namely, patients or general public, physicians or the regulators. Medical writers require an understanding of the medical concepts and terminology, knowledge of relevant guidelines as regards the structure and contents of specific documents, and good writing skills. They also need to be familiar with searching medical literature, understanding and presenting research data, the document review process, and editing and publishing requirements. Many resources are now available for medical writers to get the required training in the science and art of medical writing, and upgrade their knowledge and skills on an ongoing basis. The demand for medical writing is growing steadily in pharmaceutical and healthcare communication market. Medical writers can work independently or be employed as full time professionals. Life sciences graduates can consider medical writing as a valuable career option.

Establishment and implementation of common product assurance and safety requirements for the contractors of the Columbus programme

NASA Astrophysics Data System (ADS)

Wessels, H.; Stephan, H. J.

1991-08-01

When establishing the Columbus Product Assurance (PA)/safety requirements, the international environment of the Space Station Freedom program has to be taken into account. Considerations given to multiple ways of requirement definition and stages within the European Space Agency (ESA) Procedures, Specifications, and Standards (PSS-01) series of documents and the NASA Space Station requirements are discussed. A series of adaptations introduced by way of tailoring the basic ESA and NASA requirement sets to the Columbus program's needs are described. For the implementation of these tailored requirements, a scheme is developed, which recognizes the PA/safety approach within the European industries by way of various company handbooks and manuals. The changes introduced in the PSS-01 series and the applicable NASA Space Station requirements in recent years, has coincided with the establishment of Columbus PA/safety requirements. To achieve the necessary level of cooperation between ESA and the Columbus industries, a PA Working Group (PAWG) is established. The PAWG supervises the establishement of the Common PA/Safety Plan and the Standards to be used. Due to the high number of European industries participating in the Columbus program, a positive influence on the evolution of the industrial approaches in PA/safety can be expected. Cooperation in the PAWG has brought issues to light which are related to the ESA PSS-01 series and its requirements. Due to the rapid changes of recent years, basic company documentation has not followed the development, specifically as various recent ESA projects use different project specifc issues of the evolving PSS-01 documents.

40 CFR 62.14620 - What site-specific documentation is required?

Code of Federal Regulations, 2013 CFR

2013-07-01

... POLLUTANTS Federal Plan Requirements for Commercial and Industrial Solid Waste Incineration Units That Commenced Construction On or Before November 30, 1999 Operator Training and Qualification § 62.14620 What...) Procedures for receiving, handling, and charging waste. (3) Incinerator startup, shutdown, and malfunction...

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

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

Document fraud deterrent strategies: four case studies

NASA Astrophysics Data System (ADS)

Mercer, John W.

1998-04-01

This paper discusses the approaches taken to deter fraud committed against four documents: the machine-readable passport; the machine-readable visa; the Consular Report of Birth Abroad; and the Border Crossing Card. General approaches are discussed first, with an emphasis on the reasons for the document, the conditions of its use and the information systems required for it to function. A cost model of counterfeit deterrence is introduced. Specific approaches to each of the four documents are then discussed, in light of the issuance circumstances and criteria, the intent of the issuing authority, the applicable international standards and the level of protection and fraud resistance appropriate for the document.

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

Emergency Operation Center

NASA Technical Reports Server (NTRS)

Chinea, Anoushka Z.

1995-01-01

The Emergency Operation Center (EOC) is a site from which NASA LaRC Emergency Preparedness Officials exercise control and direction in an emergency. Research was conducted in order to determine what makes an effective EOC. Specifically information concerning the various types of equipment and communication capability that an efficient EOC should contain (i.e., computers, software, telephone systems, radio systems, etc.) was documented. With this information a requirements document was written stating a brief description of the equipment and required quantity to be used in an EOC and then compared to current capabilities at the NASA Langley Research Center.

NOSS Altimeter Detailed Algorithm specifications

NASA Technical Reports Server (NTRS)

Hancock, D. W.; Mcmillan, J. D.

1982-01-01

The details of the algorithms and data sets required for satellite radar altimeter data processing are documented in a form suitable for (1) development of the benchmark software and (2) coding the operational software. The algorithms reported in detail are those established for altimeter processing. The algorithms which required some additional development before documenting for production were only scoped. The algorithms are divided into two levels of processing. The first level converts the data to engineering units and applies corrections for instrument variations. The second level provides geophysical measurements derived from altimeter parameters for oceanographic users.

Digitization of medical documents: an X-Windows application for fast scanning.

PubMed

Muñoz, A; Salvador, C H; Gonzalez, M A; Dueñas, A

1992-01-01

This paper deals with digitization, using a commercial scanner, of medical documents as still images for introduction into a computer-based Information System. Document management involves storing, editing and transmission. This task has usually been approached from the perspective of the difficulties posed by radiologic images because of their indisputable qualitative and quantitative significance. However, healthcare activities require the management of many other types of documents and involve the requirements of numerous users. One key to document management will be the availability of a digitizer to deal with the greatest possible number of different types of documents. This paper describes the relevant aspects of documents and the technical specifications that digitizers must fulfill. The concept of document type is introduced as the ideal set of digitizing parameters for a given document. The use of document type parameters can drastically reduce the time the user spends in scanning sessions. Presentation is made of an application based on Unix, X-Windows and OSF/Motif, with a GPIB interface, implemented around the document type concept. Finally, the results of the evaluation of the application are presented, focusing on the user interface, as well as on the viewing of color images in an X-Windows environment and the use of lossy algorithms in the compression of medical images.

Requirements and design structure for Surya Satellite-1

NASA Astrophysics Data System (ADS)

Steven, H.; Huzain, M. F.

2018-05-01

Currently, there are various references on the manufacture of nanosatellite specifications weighing 1KG - 10KG.The Surya Satellite-1 is the first nanosatellite made by universities in Indonesia. The Surya Satellite-1 team gets a launch offer from Japan Aerospace Exploration Agency (JAXA) and, all the nanosatellites manufacturer racers at ICD (Interface Control Document) obtained from JAXA. The formation of the Satellite-1 Surya framework is also based on the provisions of JAXA. The various specifications and requirements specified by the JAXA space agency consisting of specific specifications such as the mass of nanosatellite 1U (10cm x 10cm x 11.65cm) size of at least 0.13KG and a maximum of 1.33KG, with the determination of a gravity point not exceeding 2 cm from the nanosatellite geometry center point. In the case of preventing solar radiation in space, there is a requirement that the structure of satellite structures on hard black anodization should be more than 10 meters in the surface of the satellite structure. In terms of detail, the satellite structure is a black hard anodized aluminum after its manufacturing process derived from the MIL-A-8625 document, type 3.

Draft Geologic Disposal Requirements Basis for STAD Specification

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

Ilgen, Anastasia G.; Bryan, Charles R.; Hardin, Ernest

2015-03-25

This document provides the basis for requirements in the current version of Performance Specification for Standardized Transportation, Aging, and Disposal Canister Systems, (FCRD-NFST-2014-0000579) that are driven by storage and geologic disposal considerations. Performance requirements for the Standardized Transportation, Aging, and Disposal (STAD) canister are given in Section 3.1 of that report. Here, the requirements are reviewed and the rationale for each provided. Note that, while FCRD-NFST-2014-0000579 provides performance specifications for other components of the STAD storage system (e.g. storage overpack, transfer and transportation casks, and others), these have no impact on the canister performance during disposal, and are not discussedmore » here.« less

Requirement of scientific documentation for the development of Naturopathy.

PubMed

Rastogi, Rajiv

2006-01-01

Past few decades have witnessed explosion of knowledge in almost every field. This has resulted not only in the advancement of the subjects in particular but also have influenced the growth of various allied subjects. The present paper explains about the advancement of science through efforts made in specific areas and also through discoveries in different allied fields having an indirect influence upon the subject in proper. In Naturopathy this seems that though nothing particular is added to the basic thoughts or fundamental principles of the subject yet the entire treatment understanding is revolutionised under the influence of scientific discoveries of past few decades. Advent of information technology has further added to the boom of knowledge and many times this seems impossible to utilize these informations for the good of human being because these are not logically arranged in our minds. In the above background, the author tries to define documentation stating that we have today ocean of information and knowledge about various things- living or dead, plants, animals or human beings; the geographical conditions or changing weather and environment. What required to be done is to extract the relevant knowledge and information required to enrich the subject. The author compares documentation with churning of milk to extract butter. Documentation, in fact, is churning of ocean of information to extract the specific, most appropriate, relevant and defined information and knowledge related to the particular subject . The paper besides discussing the definition of documentation, highlights the areas of Naturopathy requiring an urgent necessity to make proper documentations. Paper also discusses the present status of Naturopathy in India, proposes short-term and long-term goals to be achieved and plans the strategies for achieving them. The most important aspect of the paper is due understanding of the limitations of Naturopathy but a constant effort to improve the same with the growth made in various discipline of science so far.

24 CFR 1710.15 - Regulatory exemption-multiple site subdivision-determination required.

Code of Federal Regulations, 2010 CFR

2010-04-01

... non-waivable provision in bold face type (which must be distinguished from the type used for the rest... contract or other document by requiring a specific type of notice or by requiring that notice be given at a... font. A copy of the acknowledgement will be maintained by the developer for three years and will be...

I-880 Integrated Corridor Management ICM System Requirements : Final Submittal : System Requirement Specification for the I-880 Corridor in Oakland, California

DOT National Transportation Integrated Search

2008-03-31

This document summarizes the efforts conducted by the I-880 ICM team for the development of the system requirements for the I-880 Integrated Corridor Management System (ICMS). It describes the approach that the I-880 team took in defining the ICMS an...

Environmental Response Laboratory Network (ERLN) Data Submission Requirements

EPA Pesticide Factsheets

These Environmental Response Laboratory Network specifications are essential to the mission of providing consistent analytical data of know and documented quality for each Analytical Service Request (ASR).

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

DOT National Transportation Integrated Search

1981-01-01

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

Medical Treatment Facility Workload Documentation Guide.

DTIC Science & Technology

1980-04-15

to the system implementation should be presented. This document is intended as a guidebook for determining the site specific characteristics of an...wide volume analysis of a communications system. Prior to collecting any data, objectives and initial operating characteristics of the system(s...unique characteristics involved. An on-site inspection of all spaces to be impacted by NIS implementation is required initially. During this inspection

Revision of ISO 15859 Aerospace Fluid Standards

NASA Technical Reports Server (NTRS)

Greene, Benjamin; McClure, Mark B.

2012-01-01

A detailed review of ISO 15859 "Space Systems - Fluid Characteristics, Sampling and Test Methods" was performed An approach to revising Parts 1-9 and 11-13 was developed and concurred by the NASA Technical Standards Program Office. The approach was to align them with the highest level source documents, and not to program-specific requirements. The updated documents were prepared and presented.

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.

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

NASA Technical Reports Server (NTRS)

Roberts, Barry C.

2017-01-01

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.

Schema for the LANL infrasound analysis tool, infrapy

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

Dannemann, Fransiska Kate; Marcillo, Omar Eduardo

2017-04-14

The purpose of this document is to define the schema used for the operation of the infrasound analysis tool, infrapy. The tables described by this document extend the CSS3.0 or KB core schema to include information required for the operation of infrapy. This document is divided into three sections, the first being this introduction. Section two defines eight new, infrasonic data processing-specific database tables. Both internal (ORACLE) and external formats for the attributes are defined, along with a short description of each attribute. Section three of the document shows the relationships between the different tables by using entity-relationship diagrams.

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.

RH Packaging Program Guidance

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

Washington TRU Solutions, LLC

The purpose of this program guidance document is to provide technical requirements for use, operation, inspection, and maintenance of the RH-TRU 72-B Waste Shipping Package and directly related components. This document complies with the requirements as specified in the RH-TRU 72-B Safety Analysis Report for Packaging (SARP), and Nuclear Regulatory Commission (NRC) Certificate of Compliance (C of C) 9212. If there is a conflict between this document and the SARP and/or C of C, the SARP and/or C of C shall govern. The C of C states: ''...each package must be prepared for shipment and operated in accordance with themore » procedures described in Chapter 7.0, ''Operating Procedures,'' of the application.'' It further states: ''...each package must be tested and maintained in accordance with the procedures described in Chapter 8.0, ''Acceptance Tests and Maintenance Program of the Application.'' Chapter 9.0 of the SARP tasks the Waste Isolation Pilot Plant (WIPP) Management and Operating (M&O) contractor with assuring the packaging is used in accordance with the requirements of the C of C. Because the packaging is NRC approved, users need to be familiar with 10 CFR {section} 71.11, ''Deliberate Misconduct.'' Any time a user suspects or has indications that the conditions of approval in the C of C were not met, the Carlsbad Field Office (CBFO) shall be notified immediately. CBFO will evaluate the issue and notify the NRC if required. This document details the instructions to be followed to operate, maintain, and test the RH-TRU 72-B packaging. This Program Guidance standardizes instructions for all users. Users shall follow these instructions. Following these instructions assures that operations are safe and meet the requirements of the SARP. This document is available on the Internet at: ttp://www.ws/library/t2omi/t2omi.htm. Users are responsible for ensuring they are using the current revision and change notices. Sites may prepare their own document using the word-for-word steps in th is document, in sequence, including Notes and cautions. Site specific information may be included as necessary. The document, and revisions, must then be submitted to CBFO at sitedocuments@wipp.ws for approval. A copy of the approval letter from CBFO shall be available for audit purposes. Users may develop site-specific procedures addressing preoperational activities, quality assurance (QA), hoisting and rigging, and radiation health physics to be used with the instructions contained in this document. Users may recommend changes to this document by submitting their recommendations (in writing) to the WIPP M&O Contractor RH Packaging Maintenance Engineer for evaluation. If approved, the change(s) will be incorporated into this document for use by ALL users. Before first use and every 12 months after, user sites will be audited to this document to ensure compliance. They will also be audited within one year from the effective date of revisions to this document.« less

State Competencies for Writing: Grades K-6. Technical Note.

ERIC Educational Resources Information Center

Lawlor, Joseph

This paper contains descriptions of mandated minimum competency documents from seven states: Florida, Georgia, Louisiana, Michigan, Oklahoma, Tennessee, and Texas. Each description provides a picture of the general nature of the state requirements and a discussion of the specific writing skills requirements. The procedures used to compile a…

Specification for Qualification and Certification for Level II - Advanced Welders.

ERIC Educational Resources Information Center

American Welding Society, Miami, FL.

This document defines the requirements and program for the American Welding Society (AWS) to certify advanced-level welders through an evaluation process entailing performance qualification and practical knowledge tests requiring the use of advanced reading, computational, and manual skills. The following items are included: statement of the…

Specification for Qualification and Certification for Level III - Expert Welders.

ERIC Educational Resources Information Center

American Welding Society, Miami, FL.

This document defines the requirements and program for the American Welding Society to certify expert welders through an evaluation process entailing performance qualification and practical knowledge tests requiring the use of advanced reading, computational, and manual skills. The following items are included: statement of the standard's scope;…

AgRISTARS: Yield model development/soil moisture. Interface control document

NASA Technical Reports Server (NTRS)

1980-01-01

The interactions and support functions required between the crop Yield Model Development (YMD) Project and Soil Moisture (SM) Project are defined. The requirements for YMD support of SM and vice-versa are outlined. Specific tasks in support of these interfaces are defined for development of support functions.

Saint Lawrence Seaway Navigation-Aid System Study : Volume II - Appendix B - User's Manual and Documentation of Seaway Capacity and Capacity Analysis Programs

DOT National Transportation Integrated Search

1978-09-01

The requirements for a navigation guidance system which will effect an increase in the ship processing capacity of the Saint Lawrence Seaway (Lake Ontario to Montreal, Quebec) are developed. The requirements include a specification of system position...

78 FR 16840 - Submission for OMB Review; Comment Request: Testing and Recordkeeping Requirements Under the...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-03-19

... specimens of each of their mattress prototypes before mattresses based on that prototype may be introduced into commerce. The Mattress Open-Flame standard requires detailed documentation of prototype identification and testing records, model and prototype specifications, inputs used, name and location of...

mREST Interface Specification

NASA Technical Reports Server (NTRS)

McCartney, Patrick; MacLean, John

2012-01-01

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

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.

Human computer interface guide, revision A

NASA Technical Reports Server (NTRS)

1993-01-01

The Human Computer Interface Guide, SSP 30540, is a reference document for the information systems within the Space Station Freedom Program (SSFP). The Human Computer Interface Guide (HCIG) provides guidelines for the design of computer software that affects human performance, specifically, the human-computer interface. This document contains an introduction and subparagraphs on SSFP computer systems, users, and tasks; guidelines for interactions between users and the SSFP computer systems; human factors evaluation and testing of the user interface system; and example specifications. The contents of this document are intended to be consistent with the tasks and products to be prepared by NASA Work Package Centers and SSFP participants as defined in SSP 30000, Space Station Program Definition and Requirements Document. The Human Computer Interface Guide shall be implemented on all new SSFP contractual and internal activities and shall be included in any existing contracts through contract changes. This document is under the control of the Space Station Control Board, and any changes or revisions will be approved by the deputy director.

Guidelines for applying the Composite Specification Model (CSM)

NASA Technical Reports Server (NTRS)

Agresti, William

1987-01-01

The Composite Specification Model (CSM) is an approach to representing software requirements. Guidelines are provided for applying CSM and developing each of the three descriptive views of the software: the contextual view, using entities and relationships; the dynamic view, using states and transitions; and the function view, using data flows and processes. Using CSM results in a software specification document, which is outlined.

Highway Funding 1995-1998

DOT National Transportation Integrated Search

2012-07-01

This document describes the system requirements for three connected vehicle V2I safety applications related to intersection safety and speed management. Specifically, these applications include: Red-Light Violation Warning (RLVW) Stop Sign Ga...

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

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

Engels, J.

The Environmental Restoration (ER) Program was established for the investigation and remediation of inactive US Department of Energy (DOE) sites and facilities that have been declared surplus in terms of their previous uses. The purpose of this document is to Specify ER requirements for quality control (QC) of analytical data. Activities throughout all phases of the investigation may affect the quality of the final data product, thus are subject to control specifications. Laboratory control is emphasized in this document, and field concerns will be addressed in a companion document Energy Systems, in its role of technical coordinator and at themore » request of DOE-OR, extends the application of these requirements to all participants in ER activities. Because every instance and concern may not be addressed in this document, participants are encouraged to discuss any questions with the ER Quality Assurance (QA) Office, the Analytical Environmental Support Group (AESG), or the Analytical Project Office (APO).« less

Formation and Propagation of Love Waves in a Surface Layer with a P-Wave Source

DTIC Science & Technology

1990-04-01

notices on a specific document requires that it be returned. REPORT DOCUMENTATION PAGE 0M N 070. 4181 A0e4. ,wi.~g mee " Doftnw "-a awe~ o u - e t U6 U W...Massachusetts Institute of Technology Cambridge, MA 02139 Prof. Art Frankel Robert C. Kemerait Mail Stop 922 ENSCO, Inc. Geological Survey 445 Pineda

A hypertext system that learns from user feedback

NASA Technical Reports Server (NTRS)

Mathe, Nathalie

1994-01-01

Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation). Besides providing an hypertext interface for browsing large documents, the CID system automatically acquires and reuses the context in which previous searches were appropriate. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. Thus, the user continually augments and refines the intelligence of the retrieval system. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time. We successfully tested the CID system with users of the Space Station Freedom requirements documents. We are currently extending CID to other application domains (Space Shuttle operations documents, airplane maintenance manuals, and on-line training). We are also exploring the potential commercialization of this technique.

Software attribute visualization for high integrity software

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

Pollock, G.M.

1998-03-01

This report documents a prototype tool developed to investigate the use of visualization and virtual reality technologies for improving software surety confidence. The tool is utilized within the execution phase of the software life cycle. It provides a capability to monitor an executing program against prespecified requirements constraints provided in a program written in the requirements specification language SAGE. The resulting Software Attribute Visual Analysis Tool (SAVAnT) also provides a technique to assess the completeness of a software specification.

Software requirements specification for the GIS-T/ISTEA pooled fund study phase C linear referencing engine

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

Amai, W.; Espinoza, J. Jr.; Fletcher, D.R.

1997-06-01

This Software Requirements Specification (SRS) describes the features to be provided by the software for the GIS-T/ISTEA Pooled Fund Study Phase C Linear Referencing Engine project. This document conforms to the recommendations of IEEE Standard 830-1984, IEEE Guide to Software Requirements Specification (Institute of Electrical and Electronics Engineers, Inc., 1984). The software specified in this SRS is a proof-of-concept implementation of the Linear Referencing Engine as described in the GIS-T/ISTEA pooled Fund Study Phase B Summary, specifically Sheet 13 of the Phase B object model. The software allows an operator to convert between two linear referencing methods and a datummore » network.« less

Resolving the problem of compliance with the ever increasing and changing regulations

NASA Astrophysics Data System (ADS)

Leigh, Harley

1992-01-01

The most common problem identified at several U.S. Department of Energy (DOE) sites is regulatory compliance. Simply, the project viability depends on identifying regulatory requirements at the beginning of a specific project to avoid possible delays and cost overruns. The Radioisotope Power Systems Facility (RPSF) is using the Regulatory Compliance System (RCS) to deal with the problem that well over 1000 regulatory documents had to be reviewed for possible compliance requirements applicable to the facility. This overwhelming number of possible documents is not atypical of all DOE facilities thus far reviewed using the RCS system. The RCS was developed to provide control and tracking of all the regulatory and institutional requirements on a given project. WASTREN, Inc., developed the RCS through various DOE contracts and continues to enhance and update the system for existing and new contracts. The RCS provides the information to allow the technical expert to assimilate and manage accurate resource information, compile the necessary checklists, and document that the project or facility fulfills all of the appropriate regulatory requirements. The RCS provides on-line information, including status throughout the project life, thereby allowing more intelligent and proactive decision making. Also, consistency and traceability are provided for regulatory compliance documentation.

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

47 CFR 95.1221 - RF exposure.

Code of Federal Regulations, 2013 CFR

2013-10-01

... requirements specified in §§ 1.1307(b) and 2.1093 of this chapter, as appropriate. Applications for equipment... that supporting documentation and/or specific absorption rate (SAR) measurement data be submitted. [78...

47 CFR 95.1221 - RF exposure.

Code of Federal Regulations, 2014 CFR

2014-10-01

... requirements specified in §§ 1.1307(b) and 2.1093 of this chapter, as appropriate. Applications for equipment... that supporting documentation and/or specific absorption rate (SAR) measurement data be submitted. [78...

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.

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.

33 CFR 157.12g - Plan approval requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... must cover the arrangements and operation of the system as a whole and must specifically describe parts.... This documentation must include the vibration report for the control section of the monitoring section...

33 CFR 157.12g - Plan approval requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... must cover the arrangements and operation of the system as a whole and must specifically describe parts.... This documentation must include the vibration report for the control section of the monitoring section...

33 CFR 157.12g - Plan approval requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... must cover the arrangements and operation of the system as a whole and must specifically describe parts.... This documentation must include the vibration report for the control section of the monitoring section...

33 CFR 157.12g - Plan approval requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... must cover the arrangements and operation of the system as a whole and must specifically describe parts.... This documentation must include the vibration report for the control section of the monitoring section...

Instrumentation and Control for Fossil-Energy Processes

NASA Technical Reports Server (NTRS)

Mark, A., Jr.

1984-01-01

Instrumentation and control requirements for fossil-energy processes discussed in working document. Published to foster advancement of instrumentation and control technology by making equipment suppliers and others aware of specifications, needs, and potential markets.

40 CFR 53.50 - General provisions.

Code of Federal Regulations, 2010 CFR

2010-07-01

... the specific tests that must be carried out and the test results, evidence, documentation, and other... specifications set forth in appendix L or O, respectively, of part 50 of this chapter as well as additional requirements specified in this subpart E. Some or all of these tests may also be applicable to a candidate...

Using Niche-Market Magazines to Teach Audience

ERIC Educational Resources Information Center

Tichenor, Stuart

2006-01-01

In technical writing classes, audience is one of the most important concepts. Technical writing is typically written to a specific audience for a specific purpose. In addition, as audiences change, so must the way a document is written. An audience's lack of knowledge in a technical area, for example, would require more background information or…

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

Not Available

The Office of Civilian Radioactive Waste Management Systems Engineering Management Plan (OCRWM SEMP) specifies the technical management approach for the development of the waste management system, and specifies the approach for the development of each of the system elements -- the waste acceptance system, the transportation system, the Monitored Retrievable Storage (MRS) facility, and the mined geologic disposal system, which includes site characterization activity. The SEMP also delineates how systems engineering will be used by OCRWM to describe the system development process; it identifies responsibilities for its implementation, and specifies the minimum requirements for systems engineering. It also identifies themore » close interrelationship of system engineering and licensing processes. This SEMP, which is a combined OCRWM and M&O SEMP, is part of the top-level program documentation and is prepared in accordance with the direction provided in the Program Management System Manual (PMSM). The relationship of this document to other top level documents in the CRWMS document hierarchy is defined in the PMSM. A systems engineering management plan for each project, which specifies the actions to be taken in implementing systems engineering at the project level, shall be prepared by the respective project managers. [``Program`` refers to the CRWMS-wide activity and ``project`` refers to that level responsible for accomplishing the specific activities of that segment of the program.] The requirements for the project level SEMPs are addressed in Section 4.2.2.2. They represent the minimum set of requirements, and do not preclude the broadening of systems engineering activities to meet the specific needs of each project.« less

78 FR 40997 - Enhanced Document Requirements To Support Use of the Dolphin Safe Label on Tuna Products

Federal Register 2010, 2011, 2012, 2013, 2014

2013-07-09

...; modifies the reporting requirements associated with tracking domestic tuna canning and processing... products. The law addressed a Congressional finding that ``consumers would like to know if the tuna they... implement the DPCIA, including specifically the authority to establish a domestic tracking and verification...

Advanced Platform Systems Technology study. Volume 2: Trade study and technology selection

NASA Technical Reports Server (NTRS)

1983-01-01

Three primary tasks were identified which include task 1-trade studies, task 2-trade study comparison and technology selection, and task 3-technology definition. Task 1 general objectives were to identify candidate technology trade areas, determine which areas have the highest potential payoff, define specific trades within the high payoff areas, and perform the trade studies. In order to satisfy these objectives, a structured, organized approach was employed. Candidate technology areas and specific trades were screened using consistent selection criteria and considering possible interrelationships. A data base comprising both manned and unmanned space platform documentation was used as a source of system and subsystem requirements. When requirements were not stated in the data base documentation, assumptions were made and recorded where necessary to characterize a particular spacecraft system. The requirements and assumptions were used together with the selection criteria to establish technology advancement goals and select trade studies. While both manned and unmanned platform data were used, the study was focused on the concept of an early manned space station.

Atmospheric, Magnetospheric and plasmas in Space (AMPS) spacelab payload definition study; Volume 4: Part 3, Labcraft instrument systems general specification

NASA Technical Reports Server (NTRS)

Keeley, J. T.

1976-01-01

Guidelines and general requirements applicable to the development of instrument flight hardware intended for use on the GSFC Shuttle Scientific Payloads Program are given. Criteria, guidelines, and an organized approach to specifying the appropriate level of requirements for each instrument in order to permit its development at minimum cost while still assuring crew safety, are included. It is recognized that the instruments for these payloads will encompass wide ranges of complexity, cost, development risk, and safety hazards. The flexibility required to adapt the controls, documentation, and verification requirements in accord with the specific instrument is provided.

Requirement analysis for an electronic laboratory notebook for sustainable data management in biomedical research.

PubMed

Menzel, Julia; Weil, Philipp; Bittihn, Philip; Hornung, Daniel; Mathieu, Nadine; Demiroglu, Sara Y

2013-01-01

Sustainable data management in biomedical research requires documentation of metadata for all experiments and results. Scientists usually document research data and metadata in laboratory paper notebooks. An electronic laboratory notebook (ELN) can keep metadata linked to research data resulting in a better understanding of the research results, meaning a scientific benefit [1]. Besides other challenges [2], the biggest hurdles for introducing an ELN seem to be usability, file formats, and data entry mechanisms [3] and that many ELNs are assigned to specific research fields such as biology, chemistry, or physics [4]. We aimed to identify requirements for the introduction of ELN software in a biomedical collaborative research center [5] consisting of different scientific fields and to find software fulfilling most of these requirements.

Information governance in NHS's NPfIT: a case for policy specification.

PubMed

Becker, Moritz Y

2007-01-01

The National Health Service's (NHS's) National Programme for Information Technology (NPfIT) in the UK with its proposed nation-wide online health record service poses serious technical challenges, especially with regard to access control and patient confidentiality. The complexity of the confidentiality requirements and their constantly evolving nature (due to changes in law, guidelines and ethical consensus) make traditional technologies such as role-based access control (RBAC) unsuitable. Furthermore, a more formal approach is also needed for debating about and communicating on information governance, as natural-language descriptions of security policies are inherently ambiguous and incomplete. Our main goal is to convince the reader of the strong benefits of employing formal policy specification in nation-wide electronic health record (EHR) projects. Many difficulties could be alleviated by specifying the requirements in a formal authorisation policy language such as Cassandra. The language is unambiguous, declarative and machine-enforceable, and is based on distributed constrained Datalog. Cassandra is interpreted within a distributed Trust Management environment, where digital credentials are used for establishing mutual trust between strangers. To demonstrate how policy specification can be applied to NPfIT, we translate a fragment of natural-language NHS specification into formal Cassandra rules. In particular, we present policy rules pertaining to the management of Clinician Sealed Envelopes, the mechanism by which clinical patient data can be concealed in the nation-wide EHR service. Our case study exposes ambiguities and incompletenesses in the informal NHS documents. We strongly recommend the use of trust management and policy specification technology for the implementation of nation-wide EHR infrastructures. Formal policies can be used for automatically enforcing confidentiality requirements, but also for specification and communication purposes. Formalising the requirements also reveals ambiguities and missing details in the currently used informal specification documents.

Instrumentation Guidelines for the Advanced National Seismic System

USGS Publications Warehouse

Working Group on Instrumentation, Siting

2008-01-01

This document provides guidelines for the seismic-monitoring instrumentation used by long-term earthquake-monitoring stations that will sense ground motion, digitize and store the resulting signals in a local data acquisition unit, and optionally transmit these digital data. These guidelines are derived from specifications and requirements for data needed to address the nation's emergency response, engineering, and scientific needs as identified in U.S. Geological Survey Circular 1188 (1999). Data needs are discussed in terms of national, regional, and urban scales of monitoring in section 3. Functional performance specifications for instrumentation are introduced in section 4.3 and discussed in detail in section 6 in terms of instrument classes and definitions described in section 5. System aspects and testing recommendations are discussed in sections 7 and 8, respectively. Although U.S. Geological Survey Circular 1188 (1999) recommends that the Advanced National Seismic System (ANSS) include portable instrumentation, performance specifications for this element are not specifically addressed in this document. Nevertheless, these guidelines are largely applicable to portable instrumentation. Volcano monitoring instrumentation is also beyond the scope of this document. Guidance for ANSS structural-response monitoring is discussed briefly herein but details are deferred to the ANSS document by the ANSS Structural Response Monitoring Committee (U.S. Geological Survey, 2005). Aspects of station planning, siting, and installation other than instrumentation are beyond the scope of this document.

Tailoring of EIA-649-1: Definition of Major (Class I) Engineering Change Proposal

DTIC Science & Technology

2015-05-15

MISSILE SYSTEMS CENTER TAILORING TAILORING OF EIA -649-1: DEFINITION OF MAJOR (CLASS I) ENGINEERING CHANGE PROPOSAL APPROVED FOR...PUBLIC RELEASE; DISTRIBUTION IS UNLIMITED 1 Tailoring of EIA -649-1: Definition of Major (Class I) ECP. 1. Intent of this Tailoring Document...This tailoring document remedies a requirements gap in the industry consensus standard, EIA -649-1: 2015. Specifically, this tailoring provides a

A Specific Response to the National Institute of Education Under the Requirements as Set Forth Within Their Document Entitled: "Scope of Work."

ERIC Educational Resources Information Center

Flores, T. R.

The study sought to document how the National Institute of Education sponsored Mountain-Plains Career Education Model Four (CEM4) is improving on the advancing the family residential approach. This was accomplished by comparing aspects of the seven programs by way of: (1) a collection and review of available literature and reports, (2) site…

Implementing the EuroFIR Document and Data Repositories as accessible resources of food composition information.

PubMed

Unwin, Ian; Jansen-van der Vliet, Martine; Westenbrink, Susanne; Presser, Karl; Infanger, Esther; Porubska, Janka; Roe, Mark; Finglas, Paul

2016-02-15

The EuroFIR Document and Data Repositories are being developed as accessible collections of source documents, including grey literature, and the food composition data reported in them. These Repositories will contain source information available to food composition database compilers when selecting their nutritional data. The Document Repository was implemented as searchable bibliographic records in the Europe PubMed Central database, which links to the documents online. The Data Repository will contain original data from source documents in the Document Repository. Testing confirmed the FoodCASE food database management system as a suitable tool for the input, documentation and quality assessment of Data Repository information. Data management requirements for the input and documentation of reported analytical results were established, including record identification and method documentation specifications. Document access and data preparation using the Repositories will provide information resources for compilers, eliminating duplicated work and supporting unambiguous referencing of data contributing to their compiled data. Copyright © 2014 Elsevier Ltd. All rights reserved.

Targeting treatment technologies to address specific stormwater pollutants and numeric discharge limits.

PubMed

Clark, Shirley E; Pitt, Robert

2012-12-15

Stormwater treatment is entering a new phase with stormwater management systems being required to meet specific numeric objectives, as opposed to the historic approach of meeting guidance-document-provided percent removal rates. Meeting numeric discharge requirements will require designers to better understand and apply the physical, chemical, and biological processes underpinning these treatment technologies. This critical review paper focuses on the potential unit treatment operations available for stormwater treatment and outlines how to identify the most applicable treatment options based on the needed pollutant removal goals. Copyright © 2012 Elsevier Ltd. All rights reserved.

Validation Methods Research for Fault-Tolerant Avionics and Control Systems: Working Group Meeting, 2

NASA Technical Reports Server (NTRS)

Gault, J. W. (Editor); Trivedi, K. S. (Editor); Clary, J. B. (Editor)

1980-01-01

The validation process comprises the activities required to insure the agreement of system realization with system specification. A preliminary validation methodology for fault tolerant systems documented. A general framework for a validation methodology is presented along with a set of specific tasks intended for the validation of two specimen system, SIFT and FTMP. Two major areas of research are identified. First, are those activities required to support the ongoing development of the validation process itself, and second, are those activities required to support the design, development, and understanding of fault tolerant systems.

Women in Transportation: Changing America's History - Reference Materials

DOT National Transportation Integrated Search

2013-03-01

This document describes the system requirements for two connected vehicle V2I safety applications related to work zone safety and speed management. Specifically, these applications are: Spot Weather Information Warning (SWIW) Reduced Speed Zo...

40 CFR 80.171 - Product transfer documents (PTDs).

Code of Federal Regulations, 2012 CFR

2012-07-01

... certification. (iii) If, pursuant to § 80.163(c)(3), the fuel-specific certification for the segregated pool of... information requirements, provided that they are clear, accurate, and not misleading. (4) If product codes are...

40 CFR 80.171 - Product transfer documents (PTDs).

Code of Federal Regulations, 2014 CFR

2014-07-01

... certification. (iii) If, pursuant to § 80.163(c)(3), the fuel-specific certification for the segregated pool of... information requirements, provided that they are clear, accurate, and not misleading. (4) If product codes are...

40 CFR 80.171 - Product transfer documents (PTDs).

Code of Federal Regulations, 2013 CFR

2013-07-01

... certification. (iii) If, pursuant to § 80.163(c)(3), the fuel-specific certification for the segregated pool of... information requirements, provided that they are clear, accurate, and not misleading. (4) If product codes are...

40 CFR 80.171 - Product transfer documents (PTDs).

Code of Federal Regulations, 2011 CFR

2011-07-01

... certification. (iii) If, pursuant to § 80.163(c)(3), the fuel-specific certification for the segregated pool of... information requirements, provided that they are clear, accurate, and not misleading. (4) If product codes are...

Procedure for Electronic Management of Rulemaking and Other Docketed Records in the Federal Docket Management System

EPA Pesticide Factsheets

This procedure identifies the specific requirements, processes and supporting documents EPA uses to electronically manage rulemaking and other docketed records in the Federal Docket Management System (FDMS).

The integration of system specifications and program coding

NASA Technical Reports Server (NTRS)

Luebke, W. R.

1970-01-01

Experience in maintaining up-to-date documentation for one module of the large-scale Medical Literature Analysis and Retrieval System 2 (MEDLARS 2) is described. Several innovative techniques were explored in the development of this system's data management environment, particularly those that use PL/I as an automatic documenter. The PL/I data description section can provide automatic documentation by means of a master description of data elements that has long and highly meaningful mnemonic names and a formalized technique for the production of descriptive commentary. The techniques discussed are practical methods that employ the computer during system development in a manner that assists system implementation, provides interim documentation for customer review, and satisfies some of the deliverable documentation requirements.

Proposed best practice for projects that involve modelling and simulation.

PubMed

O'Kelly, Michael; Anisimov, Vladimir; Campbell, Chris; Hamilton, Sinéad

2017-03-01

Modelling and simulation has been used in many ways when developing new treatments. To be useful and credible, it is generally agreed that modelling and simulation should be undertaken according to some kind of best practice. A number of authors have suggested elements required for best practice in modelling and simulation. Elements that have been suggested include the pre-specification of goals, assumptions, methods, and outputs. However, a project that involves modelling and simulation could be simple or complex and could be of relatively low or high importance to the project. It has been argued that the level of detail and the strictness of pre-specification should be allowed to vary, depending on the complexity and importance of the project. This best practice document does not prescribe how to develop a statistical model. Rather, it describes the elements required for the specification of a project and requires that the practitioner justify in the specification the omission of any of the elements and, in addition, justify the level of detail provided about each element. This document is an initiative of the Special Interest Group for modelling and simulation. The Special Interest Group for modelling and simulation is a body open to members of Statisticians in the Pharmaceutical Industry and the European Federation of Statisticians in the Pharmaceutical Industry. Examples of a very detailed specification and a less detailed specification are included as appendices. Copyright © 2016 John Wiley & Sons, Ltd.

INFORMATION, STANDARDS, AND SPECIFICATIONS FOR EQUIPMENT, MATERIALS, AND MINOR REMODELING FOR MODERN FOREIGN LANGUAGES (REVISED).

ERIC Educational Resources Information Center

Illinois State Office of the Superintendent of Public Instruction, Springfield.

THE INFORMATION INCLUDED IN THIS VERY DETAILED DOCUMENT IS INTENDED FOR TEACHERS AND ADMINISTRATORS PLANNING AND IMPLEMENTING PROGRAMS TO IMPROVE FOREIGN LANGUAGE INSTRUCTION. THE SPECIFICATIONS PRESENTED ARE MINIMUM, BUT THEY MEET THE REQUIREMENTS UNDER THE PROVISIONS OF TITLE III, NDEA. THE FIRST PART OUTLINES PROCEDURES FOR THE SELECTION AND…

Postirradiation Testing Laboratory (327 Building)

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

Kammenzind, D.E.

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

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.

The A-7E Software Requirements Document: Three Years of Change Data.

DTIC Science & Technology

1982-11-08

Washington DC: Naval Research Laboratory. 1982. Interface Specifications for the A-7E Shared Services Module NRL Memorandum Report. Forthcoming...function driver module (Clements 1981), specifications for the extended computer module (Britton et al. 1982), and specifications for the shared ... services module (Clements 1982). The projected completion date for the SCR project is September 1985. As of the end of 1981, approximately 10 man-years of

NASIS data base management system - IBM 360/370 OS MVT implementation. 3: Data set specifications

NASA Technical Reports Server (NTRS)

1973-01-01

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

NASIS data base management system: IBM 360 TSS implementation. Volume 3: Data set specifications

NASA Technical Reports Server (NTRS)

1973-01-01

The data set specifications for the NASA Aerospace Safety Information System (NASIS) are presented. The data set specifications describe the content, format, and medium of communication of every data set required by the system. All relevant information pertinent to a particular data set is prepared in a standard form and centralized in a single document. The format for the data set is provided.

Lessons Learned in the Specification, Purchase, Validation and Final Installation Process of a Replacement PCM Bit Synchronizer

NASA Technical Reports Server (NTRS)

Price, Richard N.

2007-01-01

This paper intends to describe the lessons learned while specifying validating and installing a bit sync to replace the 30 year old Aydin Model 335a PCM bit sync used in the Space Shuttle Launch Control Center. The engineer had to analyze the original requirements and specifications and then create new requirements documentation that more correctly described our needs. One issue to consider was the removal of unnecessary requirements such as various data formats when only one format is used. The conversion to a system that no longer has an assortment of analog rotary switches required retraining of the operators. Finally, post-procurement corrections for undisclosed user requirements and missed design requirements required close contact with a manufacturer who was willing to accommodate the changes.

42 CFR 37.60 - Submitting required chest roentgenograms and miner identification documents.

Code of Federal Regulations, 2010 CFR

2010-10-01

... SERVICES MEDICAL CARE AND EXAMINATIONS SPECIFICATIONS FOR MEDICAL EXAMINATIONS OF UNDERGROUND COAL MINERS... number on each. If any of the forms cannot be completed because of the miner's refusal, it shall be...

42 CFR 37.60 - Submitting required chest roentgenograms and miner identification documents.

Code of Federal Regulations, 2011 CFR

2011-10-01

... SERVICES MEDICAL CARE AND EXAMINATIONS SPECIFICATIONS FOR MEDICAL EXAMINATIONS OF UNDERGROUND COAL MINERS... number on each. If any of the forms cannot be completed because of the miner's refusal, it shall be...

Why does LTPP require site-specific traffic loading data?

DOT National Transportation Integrated Search

2013-01-01

This flyer summarizes recent documents and training materials concerning road weather management and surface transportation published since June 2011. It includes reports, flyers, pamphlets, and training courses to show the progress made in the manag...

Truck side guard specifications : recommended standard

DOT National Transportation Integrated Search

2016-09-01

This document is intended to be used by (1) public or private medium/heavy-duty truck fleets considering adding side guards; (2) jurisdictions or customers that require side guards through policy or procurement; (3) manufacturers of side guards; and ...

USDOT guidance summary for connected vehicle deployments : human use approval.

DOT National Transportation Integrated Search

2016-07-01

This document provides guidance material in regards to human use approval required for the CV Pilots DeploymentConcept Development Phase. Background is provided on relevant Federal guidance and Institutional Review Boards,including specific reference...

76 FR 35619 - Labeling and Effectiveness Testing; Sunscreen Drug Products for Over-the-Counter Human Use

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-17

...The Food and Drug Administration (FDA) is issuing this document to address labeling and effectiveness testing for certain over-the counter (OTC) sunscreen products containing specified active ingredients and marketed without approved applications. This document addresses labeling and effectiveness testing issues raised by the nearly 2,900 submissions that we received in response to the sunscreen proposed rule of August 27, 2007 (2007 proposed rule). The document also identifies specific claims that render a product that is subject to this rule misbranded or would not be allowed on any OTC sunscreen product marketed without an approved application. The document does not address issues related to sunscreen active ingredients or certain other issues regarding the GRASE determination for sunscreen products. The document requires OTC sunscreen products to comply with the content and format requirements for OTC drug labeling contained in the 1999 Drug Facts final rule (published in the Federal Register of March 17, 1999, by lifting the delay of implementation date for that rule that we published on September 3, 2004).

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

Distributed EDLSI, BM25, and Power Norm at TREC 2008

DTIC Science & Technology

2008-11-01

LSI would work on the IIT Complex Document Information Processing (IIT CDIP ) test collection, which contains approximately 7 million documents (57 GB...requirements, specifically the memory, for EDLSI are reduced over LSI, they are still significant, especially for a corpus the size of IIT CDIP . After...data, for training purposes. Initially we ran the 2006 and 2007 queries against the IIT CDIP corpus and developed a pseudo submis- sion file containing

Resolving the problem of compliance with the ever increasing and changing regulations

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

Leigh, H.

1991-06-01

The most common problem identified at several US Department of Energy (DOE) sites is regulatory compliance. Simply, the project viability depends on identifying regulatory requirements at the beginning of a specific project to avoid possible delays and cost overruns. The Radioisotope Power Systems Facility (RFSP) is using the Regulatory Compliance System (RCS) to deal with the problem that well over 1000 regulatory documents had to be reviewed for possible compliance requirements applicable to the facility. This overwhelming number of possible documents is not atypical of all DOE facilities thus far reviewed using the RCS system. The RCS was developed tomore » provide a control and tracking of all the regulatory and institutional requirements on a given project. WASTREN, Inc., developed the RCS through various DOE contracts and continues to enhance and update the system for existing and new contracts. The RCS provides the information to allow the technical expert to assimilate and manage accurate resource information, compile the checklists, and document that the project or facility fulfills all of the appropriate regulatory requirements. The RCS provides on-line information, including status throughput the project life, thereby allowing more intelligent and proactive decision making. Also, consistency and traceability are provided for regulatory compliance documentation. 1 ref., 1 fig.« less

Polar Domain Discovery with Sparkler

NASA Astrophysics Data System (ADS)

Duerr, R.; Khalsa, S. J. S.; Mattmann, C. A.; Ottilingam, N. K.; Singh, K.; Lopez, L. A.

2017-12-01

The scientific web is vast and ever growing. It encompasses millions of textual, scientific and multimedia documents describing research in a multitude of scientific streams. Most of these documents are hidden behind forms which require user action to retrieve and thus can't be directly accessed by content crawlers. These documents are hosted on web servers across the world, most often on outdated hardware and network infrastructure. Hence it is difficult and time-consuming to aggregate documents from the scientific web, especially those relevant to a specific domain. Thus generating meaningful domain-specific insights is currently difficult. We present an automated discovery system (Figure 1) using Sparkler, an open-source, extensible, horizontally scalable crawler which facilitates high throughput and focused crawling of documents pertinent to a particular domain such as information about polar regions. With this set of highly domain relevant documents, we show that it is possible to answer analytical questions about that domain. Our domain discovery algorithm leverages prior domain knowledge to reach out to commercial/scientific search engines to generate seed URLs. Subject matter experts then annotate these seed URLs manually on a scale from highly relevant to irrelevant. We leverage this annotated dataset to train a machine learning model which predicts the `domain relevance' of a given document. We extend Sparkler with this model to focus crawling on documents relevant to that domain. Sparkler avoids disruption of service by 1) partitioning URLs by hostname such that every node gets a different host to crawl and by 2) inserting delays between subsequent requests. With an NSF-funded supercomputer Wrangler, we scaled our domain discovery pipeline to crawl about 200k polar specific documents from the scientific web, within a day.

UTM UAS Service Supplier Specification

NASA Technical Reports Server (NTRS)

Rios, Joseph Lucio

2017-01-01

Within the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) system, the UAS Service Supplier (USS) is a key component. The USS serves several functions. At a high level, those include the following: Bridging communication between UAS Operators and Flight Information Management System (FIMS) Supporting planning of UAS operations Assisting strategic deconfliction of the UTM airspace Providing information support to UAS Operators during operations Helping UAS Operators meet their formal requirements This document provides the minimum set of requirements for a USS. In order to be recognized as a USS within UTM, successful demonstration of satisfying the requirements described herein will be a prerequisite. To ensure various desired qualities (security, fairness, availability, efficiency, maintainability, etc.), this specification relies on references to existing public specifications whenever possible.

The Health Care Financing Administration's new examination documentation criteria: minimum auditing standards for the neurologic examination to be used by Medicare and other payors. Report from the American Academy of Neurology Medical Economics and Management Subcommittee.

PubMed

Nuwer, M R; Sigsbee, B

1998-02-01

Medicare recently announced the adoption of minimum documentation criteria for the neurologic examination. These criteria are added to existing standards for the history and medical decision-making. These criteria will be used in compliance audits by Medicare and other payors. Given the current federal initiative to eliminate fraud in the Medicare program, all neurologists need to comply with these standards. These criteria are for documentation only. Neurologic standards of care require a more complex and diverse examination pertinent to the problem(s) under consideration. Further guidance as to the content of a neurologic evaluation is outlined in the article "Practice guidelines: Neurologic evaluation" (Neurology 1990; 40: 871). The level of history and examination required for specific services is defined in the American Medical Association current procedural terminology book. Documentation standards for examination of children are not yet defined.

10 CFR 850 Implementation of Requirements

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

Lee, S

2012-01-05

10 CFR 850 defines a contractor as any entity, including affiliated entities, such as a parent corporation, under contract with DOE, including a subcontractor at any tier, with responsibility for performing work at a DOE site in furtherance of a DOE mission. The Chronic Beryllium Disease Prevention Program (CBDPP) applies to beryllium-related activities that are performed at the Lawrence Livermore National Laboratory (LLNL). The CBDPP or Beryllium Safety Program is integrated into the LLNL Worker Safety and Health Program and, thus, implementation documents and responsibilities are integrated in various documents and organizational structures. Program development and management of the CBDPPmore » is delegated to the Environment, Safety and Health (ES&H) Directorate, Worker Safety and Health Functional Area. As per 10 CFR 850, Lawrence Livermore National Security, LLC (LLNS) periodically submits a CBDPP to the National Nuclear Security Administration/Livermore Site Office (NNSA/LSO). The requirements of this plan are communicated to LLNS workers through ES&H Manual Document 14.4, 'Working Safely with Beryllium.' 10 CFR 850 is implemented by the LLNL CBDPP, which integrates the safety and health standards required by the regulation, components of the LLNL Integrated Safety Management System (ISMS), and incorporates other components of the LLNL ES&H Program. As described in the regulation, and to fully comply with the regulation, specific portions of existing programs and additional requirements are identified in the CBDPP. The CBDPP is implemented by documents that interface with the workers, principally through ES&H Manual Document 14.4. This document contains information on how the management practices prescribed by the LLNL ISMS are implemented, how beryllium hazards that are associated with LLNL work activities are controlled, and who is responsible for implementing the controls. Adherence to the requirements and processes described in the ES&H Manual ensures that ES&H practices across LLNL are developed in a consistent manner. Other implementing documents, such as the ES&H Manual, are integral in effectively implementing 10 CFR 850.« less

Public Notification Instructions and Templates for the Revised Total Coliform Rule (RTCR)

EPA Pesticide Factsheets

EPA has developed public notification (PN) templates to help with implementation of the PN Rule. This document aims to assist water systems with the Public Notification requirements specific to the Revised Total Coliform Rule (RTCR).

78 FR 51139 - Notice of Proposed Changes to the National Handbook of Conservation Practices for the Natural...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-20

... (Code 324), Field Border (Code 386), Filter Strip (Code 393), Land Smoothing (Code 466), Livestock... the implementation requirement document to the specifications and plans. Filter Strip (Code 393)--The...

Compliance Assurance Monitoring Technical Guidance Document Appendix A: Control of Other Specific Compounds

EPA Pesticide Factsheets

Compliance assurance monitoring is intended to provide a reasonable assurance of compliance with applicable requirements under the Clean Air Act for large emission units that rely on pollution control device equipment to achieve compliance.

Birth/death process model

NASA Technical Reports Server (NTRS)

Solloway, C. B.; Wakeland, W.

1976-01-01

First-order Markov model developed on digital computer for population with specific characteristics. System is user interactive, self-documenting, and does not require user to have complete understanding of underlying model details. Contains thorough error-checking algorithms on input and default capabilities.

Solid Waste Information and Tracking System Client Server Conversion Project Management Plan

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

GLASSCOCK, J.A.

2000-02-10

The Project Management Plan governing the conversion of SWITS to a client-server architecture. The PMP describes the background, planning and management of the SWITS conversion. Requirements and specification documentation needed for the SWITS conversion

Querying archetype-based EHRs by search ontology-based XPath engineering.

PubMed

Kropf, Stefan; Uciteli, Alexandr; Schierle, Katrin; Krücken, Peter; Denecke, Kerstin; Herre, Heinrich

2018-05-11

Legacy data and new structured data can be stored in a standardized format as XML-based EHRs on XML databases. Querying documents on these databases is crucial for answering research questions. Instead of using free text searches, that lead to false positive results, the precision can be increased by constraining the search to certain parts of documents. A search ontology-based specification of queries on XML documents defines search concepts and relates them to parts in the XML document structure. Such query specification method is practically introduced and evaluated by applying concrete research questions formulated in natural language on a data collection for information retrieval purposes. The search is performed by search ontology-based XPath engineering that reuses ontologies and XML-related W3C standards. The key result is that the specification of research questions can be supported by the usage of search ontology-based XPath engineering. A deeper recognition of entities and a semantic understanding of the content is necessary for a further improvement of precision and recall. Key limitation is that the application of the introduced process requires skills in ontology and software development. In future, the time consuming ontology development could be overcome by implementing a new clinical role: the clinical ontologist. The introduced Search Ontology XML extension connects Search Terms to certain parts in XML documents and enables an ontology-based definition of queries. Search ontology-based XPath engineering can support research question answering by the specification of complex XPath expressions without deep syntax knowledge about XPaths.

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.

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.

Processing woody biomass with a modified horizontal grinder

Treesearch

Dana Mitchell; John Klepac

2008-01-01

This study documents the production rate and cost of producing woody biomass chips for use in a power plant. The power plant has specific raw material handling requirements. Output from a 3-knife chipper, a tub grinder, and a horizontal grinder was considered. None of the samples from these machines met the specifications needed. A horizontal grinder was modified to...

HAL/S language specification. Version IR-542

NASA Technical Reports Server (NTRS)

1980-01-01

The formal HAL/S language specification is documented with particular referral to the essentials of HAL/S syntax and semantics. The language is intended to satisfy virtually all of the flight software requirements of NASA programs. To achieve this, HAL/S incorporates a wide range of features, including applications oriented data types and organizations, real time control mechanisms, and constructs for systems programming tasks.

Solvent Replacement for Super Corr-A Corrosion Preventive Compound (CPC)

DTIC Science & Technology

2011-08-18

AFCPCO BUSINESS SENSITIVE 8 First Article Testing Results Insert table referred to in interim report ? Requirement Test Method Specification...Vertical BUSINESS SENSITIVE 23 Conclusions • No tested lubricants met all first article testing requirements • DuPont Vertrel SDG and Kyzen Cybersolv...Paul Hoth Battelle Hill AFB Distribution Statement A Approved for public release; distribution is unlimited Report Documentation Page

75 FR 52591 - New York State Department of Environmental Conservation Requirements on Gasoline Transport Vehicles

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-26

... requirements in the HMR on the marking, maintaining, repairing, or testing of a package or container that is... gasoline cargo tanks. Documentation that the cargo tank has met the specifications of EPA Method 27 shall be carried on the cargo tank.'' 73 FR at 1949 (emphasis supplied). In addition, EPA has advised PHMSA...

12 CFR 611.1216 - Public availability of documents related to the termination.

Code of Federal Regulations, 2012 CFR

2012-01-01

... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

12 CFR 611.1216 - Public availability of documents related to the termination.

Code of Federal Regulations, 2014 CFR

2014-01-01

... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

12 CFR 611.1216 - Public availability of documents related to the termination.

Code of Federal Regulations, 2013 CFR

2013-01-01

... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

12 CFR 611.1216 - Public availability of documents related to the termination.

Code of Federal Regulations, 2011 CFR

2011-01-01

... the termination. (a) We may post on our Web site, or require you to post on your Web site: (1) Results... related transactions. (b) We will not post confidential information on our Web site and will not require you to post it on your Web site. (c) You may request that we treat specific information as...

What Evidence is Being Used to Inform Municipal Strategic Planning for Health and Wellbeing? Victoria, Australia, a Case Study

ERIC Educational Resources Information Center

Browne, Geoffrey R.; Davern, Melanie; Giles-Corti, Billie

2017-01-01

Victorian local governments (LGs) are required to develop evidence-based Municipal Public Health and Wellbeing Plans (MPHWPs) that improve health and wellbeing. This study evaluated the implementation of this requirement across 79 LGs. Evidence in 116 documents was categorised by source, issue, and policy specificity. Over 11,000…

Lunar Human Research Requirements (LHRR)

NASA Technical Reports Server (NTRS)

Denkins, Pamela

2009-01-01

Biomedical research will be conducted during transit and on the surface of the Moon to prepare for extended stays on the Moon and to prepare for the exploration of Mars. The objective of the Human Research Program (HRP) is to preserve the health and enhance performance of astronaut explorers. Specific objectives of the HRP include developing the knowledge, capabilities, and necessary countermeasures and technologies in support of human space exploration; focusing on mitigating the highest risks to crew health and performance; and defining and improving human spaceflight medical, environmental, behavioral, and human factors standards. This document contains a detailed description of the resource accommodations, interfaces, and environments to be provided by the Constellation Program (CxP) to support the HRP research in transit and on the lunar surface. Covered, specifically, are the requirements for mass and volume transport; crew availability; ground operations, baseline data collection, and payload processing; power, and data. Volumes and mass are given for transport of conditioned samples only. They do not account for the engineering solution that the Constellation Program will implement (refrigerator/freezer volume/mass). This document does not account for requirements on the Orion vehicle for transportation to and from the International Space Station (ISS). The ISS Program has supplied requirements for this mission.

Using formal methods for content validation of medical procedure documents.

PubMed

Cota, Érika; Ribeiro, Leila; Bezerra, Jonas Santos; Costa, Andrei; da Silva, Rosiana Estefane; Cota, Gláucia

2017-08-01

We propose the use of a formal approach to support content validation of a standard operating procedure (SOP) for a therapeutic intervention. Such an approach provides a useful tool to identify ambiguities, omissions and inconsistencies, and improves the applicability and efficacy of documents in the health settings. We apply and evaluate a methodology originally proposed for the verification of software specification documents to a specific SOP. The verification methodology uses the graph formalism to model the document. Semi-automatic analysis identifies possible problems in the model and in the original document. The verification is an iterative process that identifies possible faults in the original text that should be revised by its authors and/or specialists. The proposed method was able to identify 23 possible issues in the original document (ambiguities, omissions, redundant information, and inaccuracies, among others). The formal verification process aided the specialists to consider a wider range of usage scenarios and to identify which instructions form the kernel of the proposed SOP and which ones represent additional or required knowledge that are mandatory for the correct application of the medical document. By using the proposed verification process, a simpler and yet more complete SOP could be produced. As consequence, during the validation process the experts received a more mature document and could focus on the technical aspects of the procedure itself. Copyright © 2017 Elsevier B.V. All rights reserved.

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.

12 CFR 240.17 - Reservation of authority.

Code of Federal Regulations, 2014 CFR

2014-01-01

..., documentation, or other standards or requirements under this part for a specific retail forex transaction or a class of retail forex transactions if the Board determines that the modification is consistent with safety and soundness and the protection of retail forex customers. ...

National Emissions Standards for Hazardous Air Pollutants (NESHAP) for Area Source Standards for Prepared Feeds Manufacturing: Commonly Asked Questions and Answers

EPA Pesticide Factsheets

This 2011 document answers common questions about the NESHAP for Area Sources for Prepared Feeds Manufacturing. The questions range in topics including applicability, specific requirements, and recordkeeping.

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...

38 CFR 39.81 - Preapplication requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

.... (9) A gravesite assessment survey documenting the State cemetery's performance related to the..., leveling of gravesites, or turf conditions. Specifically, the preapplication should explain the need for... must blend in with adjacent grade levels. (v) Turf conditions. 100 percent of visually prominent areas...

Word Spotting for Indic Documents to Facilitate Retrieval

NASA Astrophysics Data System (ADS)

Bhardwaj, Anurag; Setlur, Srirangaraj; Govindaraju, Venu

With advances in the field of digitization of printed documents and several mass digitization projects underway, information retrieval and document search have emerged as key research areas. However, most of the current work in these areas is limited to English and a few oriental languages. The lack of efficient solutions for Indic scripts has hampered information extraction from a large body of documents of cultural and historical importance. This chapter presents two relevant topics in this area. First, we describe the use of a script-specific keyword spotting for Devanagari documents that makes use of domain knowledge of the script. Second, we address the needs of a digital library to provide access to a collection of documents from multiple scripts. This requires intelligent solutions which scale across different scripts. We present a script-independent keyword spotting approach for this purpose. Experimental results illustrate the efficacy of our methods.

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.

2007 Wholesale Power Rate Case Initial Proposal : Wholesale Power Rate Development Study.

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

United States. Bonneville Power Administration.

The Wholesale Power Rate Development Study (WPRDS) calculates BPA proposed rates based on information either developed in the WPRDS or supplied by the other studies that comprise the BPA rate proposal. All of these studies, and accompanying documentation, provide the details of computations and assumptions. In general, information about loads and resources is provided by the Load Resource Study (LRS), WP-07-E-BPA-01, and the LRS Documentation, WP-07-E-BPA-01A. Revenue requirements information, as well as the Planned Net Revenues for Risk (PNNR), is provided in the Revenue Requirement Study, WP-07-E-BPA-02, and its accompanying Revenue Requirement Study Documentation, WP-07-E-BPA-02A and WP-07-E-BPA-02B. The Market Pricemore » Forecast Study (MPFS), WP-07-E-BPA-03, and the MPFS Documentation, WP-07-E-BPA-03A, provide the WPRDS with information regarding seasonal and diurnal differentiation of energy rates, as well information regarding monthly market prices for Demand Rates. In addition, this study provides information for the pricing of unbundled power products. The Risk Analysis Study, WP-07-E-BPA-04, and the Risk Analysis Study Documentation, WP-07-E-BPA-04A, provide short-term balancing purchases as well as secondary energy sales and revenue. The Section 7(b)(2) Rate Test Study, WP-07-E-BPA-06, and the Section 7(b)(2) Rate Test Study Documentation, WP-07-E-BPA-06A, implement Section 7(b)(2) of the Northwest Power Act to ensure that BPA preference customers firm power rates applied to their general requirements are no higher than rates calculated using specific assumptions in the Northwest Power Act.« less

Integrated information systems for electronic chemotherapy medication administration.

PubMed

Levy, Mia A; Giuse, Dario A; Eck, Carol; Holder, Gwen; Lippard, Giles; Cartwright, Julia; Rudge, Nancy K

2011-07-01

Chemotherapy administration is a highly complex and distributed task in both the inpatient and outpatient infusion center settings. The American Society of Clinical Oncology and the Oncology Nursing Society (ASCO/ONS) have developed standards that specify procedures and documentation requirements for safe chemotherapy administration. Yet paper-based approaches to medication administration have several disadvantages and do not provide any decision support for patient safety checks. Electronic medication administration that includes bar coding technology may provide additional safety checks, enable consistent documentation structure, and have additional downstream benefits. We describe the specialized configuration of clinical informatics systems for electronic chemotherapy medication administration. The system integrates the patient registration system, the inpatient order entry system, the pharmacy information system, the nursing documentation system, and the electronic health record. We describe the process of deploying this infrastructure in the adult and pediatric inpatient oncology, hematology, and bone marrow transplant wards at Vanderbilt University Medical Center. We have successfully adapted the system for the oncology-specific documentation requirements detailed in the ASCO/ONS guidelines for chemotherapy administration. However, several limitations remain with regard to recording the day of treatment and dose number. Overall, the configured systems facilitate compliance with the ASCO/ONS guidelines and improve the consistency of documentation and multidisciplinary team communication. Our success has prompted us to deploy this infrastructure in our outpatient chemotherapy infusion centers, a process that is currently underway and that will require a few unique considerations.

Advanced space power requirements and techniques. Task 1: Mission projections and requirements. Volume 1: Technical report

NASA Technical Reports Server (NTRS)

Wolfe, M. G.

1978-01-01

The objectives of this study were to: (1) develop projections of the NASA, DoD, and civil space power requirements for the 1980-1995 time period; (2) identify specific areas of application and space power subsystem type needs for each prospective user; (3) document the supporting and historical base, including relevant cost related measures of performance; and (4) quantify the benefits of specific technology projection advancements. The initial scope of the study included: (1) construction of likely models for NASA, DoD, and civil space systems; (2) generation of a number of future scenarios; (3) extraction of time phased technology requirements based on the scenarios; and (4) cost/benefit analyses of some of the technologies identified.

International Space Station Human Behavior and Performance Competency Model: Volume I

NASA Technical Reports Server (NTRS)

Schmidt, Lacey

2008-01-01

This document defines Human Behavior and Performance (HBP) competencies that are recommended to be included as requirements to participate in international long duration missions. They were developed in response to the Multilateral Crew Operations Panel (MMOP) request to develop HBP training requirements for the International Space Station (ISS). The competency model presented here was developed by the ITCB HBPT WG and forms the basis for determining the HBP training curriculum for long duration crewmembers. This document lists specific HBP competencies and behaviors required of astronauts/cosmonauts who participate in ISS expedition and other international longduration missions. Please note that this model does not encompass all competencies required. For example, outside the scope of this document are cognitive skills and abilities, including but not limited to concentration, memorization, perception, imagination, and thinking. It is assumed that these skills, which are crucial in terms of human behavior and performance, are considered during selection phase since such professionally significant qualities of the operator should be taken into consideration in order to ensure sufficient baseline levels that can be further improved during general astronaut training. Also, technical competencies, even though critical for crewmembers, are beyond the scope of this document. It should also be noted that the competencies in this model (and subsequent objectives) are not intended to limit the internal activities or training programs of any international partner.

Hammam Al Alil Division Training Center Mosul, Iraq

DTIC Science & Technology

2010-01-07

displacement of the concrete slab. The SOW required translucent material for the cladding and provided specific details for windows inserted in the...of poor curing practice; however, SIGIR did not observe any significant cracking or displacement of the concrete slab. The SOW required translucent ...Documentation that addressed the safety concerns of removing the overhead baffles was not available. In addition, the contractor used precast concrete planks

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 60.2660 - What site-specific documentation is required?

Code of Federal Regulations, 2014 CFR

2014-07-01

... PROGRAMS (CONTINUED) STANDARDS OF PERFORMANCE FOR NEW STATIONARY SOURCES Emissions Guidelines and Compliance Times for Commercial and Industrial Solid Waste Incineration Units Model Rule-Operator Training... and are suitable for inspection upon request. (1) Summary of the applicable standards under this...

40 CFR 60.2660 - What site-specific documentation is required?

Code of Federal Regulations, 2013 CFR

2013-07-01

... PROGRAMS (CONTINUED) STANDARDS OF PERFORMANCE FOR NEW STATIONARY SOURCES Emissions Guidelines and Compliance Times for Commercial and Industrial Solid Waste Incineration Units Model Rule-Operator Training... and are suitable for inspection upon request. (1) Summary of the applicable standards under this...

25 CFR 162.571 - What are the consent requirements for an amendment to a WSR lease?

Code of Federal Regulations, 2014 CFR

2014-04-01

... AND WATER LEASES AND PERMITS Wind and Solar Resource Leases Wsr Lease Amendments § 162.571 What are... review. (d) Unless specifically authorized in the lease, a written power of attorney, or a court document...

25 CFR 162.571 - What are the consent requirements for an amendment to a WSR lease?

Code of Federal Regulations, 2013 CFR

2013-04-01

... AND WATER LEASES AND PERMITS Wind and Solar Resource Leases Wsr Lease Amendments § 162.571 What are... review. (d) Unless specifically authorized in the lease, a written power of attorney, or a court document...

38 CFR 39.81 - Preapplication requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

.... (9) A gravesite assessment survey documenting the State or Tribal cemetery's performance related to... headstones and markers, leveling of gravesites, or turf conditions. Specifically, the preapplication should... of the grade of every gravesite must blend in with adjacent grade levels. (v) Turf conditions. 100...

38 CFR 39.81 - Preapplication requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

.... (9) A gravesite assessment survey documenting the State or Tribal cemetery's performance related to... headstones and markers, leveling of gravesites, or turf conditions. Specifically, the preapplication should... of the grade of every gravesite must blend in with adjacent grade levels. (v) Turf conditions. 100...

38 CFR 39.81 - Preapplication requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

.... (9) A gravesite assessment survey documenting the State or Tribal cemetery's performance related to... headstones and markers, leveling of gravesites, or turf conditions. Specifically, the preapplication should... of the grade of every gravesite must blend in with adjacent grade levels. (v) Turf conditions. 100...

WATER QUALITY CRITERIA DOCUMENTS

EPA Science Inventory

Background

Water quality standards and criteria are the foundation for a wide range of programs under the Clean Water Act. Specifically, under section 304(a)(1) of the Clean Water Act it requires EPA to develop criteria for water quality that accurately re...

Noise Budget for the X-Ray Microcalorimeter Spectrometer (XMS) Core Array

NASA Technical Reports Server (NTRS)

Kilbourne, Caroline Anne

2010-01-01

The purpose of this document is to present and archive the noise budget for the XMS detector, in order, at this stage in mission planning, to learn the scale of the requirements placed on the other instrument subsystems. This document mainly concerns the core array, specifically the baseline version that emerged from the trade studies associated with the ESA Phase A study report. Qualitative extension to the Hydra approach to the outer array is included at the end.

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.

Australian Paediatric Rheumatology Group standards of care for the management of juvenile idiopathic arthritis.

PubMed

Munro, Jane; Murray, Kevin; Boros, Christina; Chaitow, Jeffrey; Allen, Roger C; Akikusa, Jonathan; Adib, Navid; Piper, Susan E; Singh-Grewal, Davinder

2014-09-01

This standards document outlines accepted standards of management for children, adolescents and young adults with juvenile idiopathic arthritis (JIA) in Australia. This document acknowledges that the chronic inflammatory arthritis conditions (JIA) in childhood are different diseases from inflammatory arthritis in adults and that specific expertise is required in the care of children with arthritis. © 2014 The Authors. Journal of Paediatrics and Child Health © 2014 Paediatrics and Child Health Division (Royal Australasian College of Physicians).

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.

Cultural Competency Training Requirements in Graduate Medical Education

PubMed Central

Ambrose, Adrian Jacques H.; Lin, Susan Y.; Chun, Maria B. J.

2013-01-01

Background Cultural competency is an important skill that prepares physicians to care for patients from diverse backgrounds. Objective We reviewed Accreditation Council for Graduate Medical Education (ACGME) program requirements and relevant documents from the ACGME website to evaluate competency requirements across specialties. Methods The program requirements for each specialty and its subspecialties were reviewed from December 2011 through February 2012. The review focused on the 3 competency domains relevant to culturally competent care: professionalism, interpersonal and communication skills, and patient care. Specialty and subspecialty requirements were assigned a score between 0 and 3 (from least specific to most specific). Given the lack of a standardized cultural competence rating system, the scoring was based on explicit mention of specific keywords. Results A majority of program requirements fell into the low- or no-specificity score (1 or 0). This included 21 core specialties (leading to primary board certification) program requirements (78%) and 101 subspecialty program requirements (79%). For all specialties, cultural competency elements did not gravitate toward any particular competency domain. Four of 5 primary care program requirements (pediatrics, obstetrics-gynecology, family medicine, and psychiatry) acquired the high-specificity score of 3, in comparison to only 1 of 22 specialty care program requirements (physical medicine and rehabilitation). Conclusions The degree of specificity, as judged by use of keywords in 3 competency domains, in ACGME requirements regarding cultural competency is highly variable across specialties and subspecialties. Greater specificity in requirements is expected to benefit the acquisition of cultural competency in residents, but this has not been empirically tested. PMID:24404264

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).

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.

Advanced information processing system: Inter-computer communication services

NASA Technical Reports Server (NTRS)

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

1991-01-01

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

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

Evaluation of metrics and baselines for tracking greenhouse gas emissions trends: Recommendations for the California climate action registry

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

Price, Lynn; Murtishaw, Scott; Worrell, Ernst

2003-06-01

Executive Summary: The California Climate Action Registry, which was initially established in 2000 and began operation in Fall 2002, is a voluntary registry for recording annual greenhouse gas (GHG) emissions. The purpose of the Registry is to assist California businesses and organizations in their efforts to inventory and document emissions in order to establish a baseline and to document early actions to increase energy efficiency and decrease GHG emissions. The State of California has committed to use its ''best efforts'' to ensure that entities that establish GHG emissions baselines and register their emissions will receive ''appropriate consideration under any futuremore » international, federal, or state regulatory scheme relating to greenhouse gas emissions.'' Reporting of GHG emissions involves documentation of both ''direct'' emissions from sources that are under the entity's control and indirect emissions controlled by others. Electricity generated by an off-site power source is consider ed to be an indirect GHG emission and is required to be included in the entity's report. Registry participants include businesses, non-profit organizations, municipalities, state agencies, and other entities. Participants are required to register the GHG emissions of all operations in California, and are encouraged to report nationwide. For the first three years of participation, the Registry only requires the reporting of carbon dioxide (CO2) emissions, although participants are encouraged to report the remaining five Kyoto Protocol GHGs (CH4, N2O, HFCs, PFCs, and SF6). After three years, reporting of all six Kyoto GHG emissions is required. The enabling legislation for the Registry (SB 527) requires total GHG emissions to be registered and requires reporting of ''industry-specific metrics'' once such metrics have been adopted by the Registry. The Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab) was asked to provide technical assistance to the California Energy Commission (Energy Commission) related to the Registry in three areas: (1) assessing the availability and usefulness of industry-specific metrics, (2) evaluating various methods for establishing baselines for calculating GHG emissions reductions related to specific actions taken by Registry participants, and (3) establishing methods for calculating electricity CO2 emission factors. The third area of research was completed in 2002 and is documented in Estimating Carbon Dioxide Emissions Factors for the California Electric Power Sector (Marnay et al., 2002). This report documents our findings related to the first areas of research. For the first area of research, the overall objective was to evaluate the metrics, such as emissions per economic unit or emissions per unit of production that can be used to report GHG emissions trends for potential Registry participants. This research began with an effort to identify methodologies, benchmarking programs, inventories, protocols, and registries that u se industry-specific metrics to track trends in energy use or GHG emissions in order to determine what types of metrics have already been developed. The next step in developing industry-specific metrics was to assess the availability of data needed to determine metric development priorities. Berkeley Lab also determined the relative importance of different potential Registry participant categories in order to asses s the availability of sectoral or industry-specific metrics and then identified industry-specific metrics in use around the world. While a plethora of metrics was identified, no one metric that adequately tracks trends in GHG emissions while maintaining confidentiality of data was identified. As a result of this review, Berkeley Lab recommends the development of a GHG intensity index as a new metric for reporting and tracking GHG emissions trends.Such an index could provide an industry-specific metric for reporting and tracking GHG emissions trends to accurately reflect year to year changes while protecting proprietary data. This GHG intensity index changes while protecting proprietary data. This GHG intensity index would provide Registry participants with a means for demonstrating improvements in their energy and GHG emissions per unit of production without divulging specific values. For the second research area, Berkeley Lab evaluated various methods used to calculate baselines for documentation of energy consumption or GHG emissions reductions, noting those that use industry-specific metrics. Accounting for actions to reduce GHGs can be done on a project-by-project basis or on an entity basis. Establishing project-related baselines for mitigation efforts has been widely discussed in the context of two of the so-called ''flexible mechanisms'' of the Kyoto Protocol to the United Nations Framework Convention on Climate Change (Kyoto Protocol) Joint Implementation (JI) and the Clean Development Mechanism (CDM).« less

Text-interpreter language for flexible generation of patient notes and instructions.

PubMed

Forker, T S

1992-01-01

An interpreted computer language has been developed along with a windowed user interface and multi-printer-support formatter to allow preparation of documentation of patient visits, including progress notes, prescriptions, excuses for work/school, outpatient laboratory requisitions, and patient instructions. Input is by trackball or mouse with little or no keyboard skill required. For clinical problems with specific protocols, the clinician can be prompted with problem-specific items of history, exam, and lab data to be gathered and documented. The language implements a number of text-related commands as well as branching logic and arithmetic commands. In addition to generating text, it is simple to implement arithmetic calculations such as weight-specific drug dosages; multiple branching decision-support protocols for paramedical personnel (or physicians); and calculation of clinical scores (e.g., coma or trauma scores) while simultaneously documenting the status of each component of the score. ASCII text files produced by the interpreter are available for computerized quality audit. Interpreter instructions are contained in text files users can customize with any text editor.

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

42 CFR 426.432 - Discovery.

Code of Federal Regulations, 2011 CFR

2011-10-01

... burdensome; or (iii) Unduly delays the proceeding. (c) Types of discovery available. A party may obtain... interrogatory questions, relating to a specific LCD. (d) Types of documents. For the purpose of this section... other data and documentary evidence. Nothing contained in this section is interpreted to require the...

The DACUM Job Analysis Process.

ERIC Educational Resources Information Center

Dofasco, Inc., Hamilton (Ontario).

This document explains the DACUM (Developing A Curriculum) process for analyzing task-based jobs to: identify where standard operating procedures are required; identify duplicated low value added tasks; develop performance standards; create job descriptions; and identify the elements that must be included in job-specific training programs. The…

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.

Population-specific documentation of pharmacogenomic markers and their allelic frequencies in FINDbase.

PubMed

Georgitsi, Marianthi; Viennas, Emmanouil; Gkantouna, Vassiliki; Christodoulopoulou, Elena; Zagoriti, Zoi; Tafrali, Christina; Ntellos, Fotios; Giannakopoulou, Olga; Boulakou, Athanassia; Vlahopoulou, Panagiota; Kyriacou, Eva; Tsaknakis, John; Tsakalidis, Athanassios; Poulas, Konstantinos; Tzimas, Giannis; Patrinos, George P

2011-01-01

Population and ethnic group-specific allele frequencies of pharmacogenomic markers are poorly documented and not systematically collected in structured data repositories. We developed the Frequency of Inherited Disorders Pharmacogenomics database (FINDbase-PGx), a separate module of the FINDbase, aiming to systematically document pharmacogenomic allele frequencies in various populations and ethnic groups worldwide. We critically collected and curated 214 scientific articles reporting pharmacogenomic markers allele frequencies in various populations and ethnic groups worldwide. Subsequently, in order to host the curated data, support data visualization and data mining, we developed a website application, utilizing Microsoft™ PivotViewer software. Curated allelic frequency data pertaining to 144 pharmacogenomic markers across 14 genes, representing approximately 87,000 individuals from 150 populations worldwide, are currently included in FINDbase-PGx. A user-friendly query interface allows for easy data querying, based on numerous content criteria, such as population, ethnic group, geographical region, gene, drug and rare allele frequency. FINDbase-PGx is a comprehensive database, which, unlike other pharmacogenomic knowledgebases, fulfills the much needed requirement to systematically document pharmacogenomic allelic frequencies in various populations and ethnic groups worldwide.

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

Aging management program of the reactor building concrete at Point Lepreau Generating Station

NASA Astrophysics Data System (ADS)

Aldea, C.-M.; Shenton, B.; Demerchant, M. M.; Gendron, T.

2011-04-01

In order for New Brunswick Power Nuclear (NBPN) to control the risks of degradation of the concrete reactor building at the Point Lepreau Generating Station (PLGS) the development of an aging management plan (AMP) was initiated. The intention of this plan was to determine the requirements for specific structural components of concrete of the reactor building that require regular inspection and maintenance to ensure the safe and reliable operation of the plant. The document is currently in draft form and presents an integrated methodology for the application of an AMP for the concrete of the reactor building. The current AMP addresses the reactor building structure and various components, such as joint sealant and liners that are integral to the structure. It does not include internal components housed within the structure. This paper provides background information regarding the document developed and the strategy developed to manage potential degradation of the concrete of the reactor building, as well as specific programs and preventive and corrective maintenance activities initiated.

Association of Medical Directors of Information Systems consensus on inpatient electronic health record documentation.

PubMed

Shoolin, J; Ozeran, L; Hamann, C; Bria, W

2013-01-01

In 2013, electronic documentation of clinical care stands at a crossroads. The benefits of creating digital notes are at risk of being overwhelmed by the inclusion of easily importable detail. Providers are the primary authors of encounters with patients. We must document clearly our understanding of patients and our communication with them and our colleagues. We want to document efficiently to meet without exceeding documentation guidelines. We copy and paste documentation, because it not only simplifies the documentation process generally, but also supports meeting coding and regulatory requirements specifically. Since the primary goal of our profession is to spend as much time as possible listening to, understanding and helping patients, clinicians need information technology to make electronic documentation easier, not harder. At the same time, there should be reasonable restrictions on the use of copy and paste to limit the growing challenge of 'note bloat'. We must find the right balance between ease of use and thoughtless documentation. The guiding principles in this document may be used to launch an interdisciplinary dialogue that promotes useful and necessary documentation that best facilitates efficient information capture and effective display.

Remotely Operated Aircraft (ROA) Impact on the National Airspace System (NAS) Work Package, 2005: Composite Report on FAA Flight Plan and Operational Evaluation Plan. Version 7.0

NASA Technical Reports Server (NTRS)

2005-01-01

The purpose of this document is to present the findings that resulted from a high-level analysis and evaluation of the following documents: (1) The OEP (Operational Evolution Plan) Version 7 -- a 10-year plan for operational improvements to increase capacity and efficiency in U.S. air travel and transport and other use of domestic airspace. The OEP is the FAA commitment to operational improvements. It is outcome driven, with clear lines of accountability within FAA organizations. The OEP concentrates on operational solutions and integrates safety, certification, procedures, staffing, equipment, avionics and research; (2) The Draft Flight Plan 2006 through 2010 -- a multi-year strategic effort, setting a course for the FAA through 2001, to provide the safest and most efficient air transportation system in the world; (3) The NAS System Architecture Version 5 -- a blueprint for modernizing the NAS and improving NAS services and capabilities through the year 2015; and (4) The NAS-SR-1000 System Requirements Specification (NASSRS) -- a compilation of requirements which describe the operational capabilities for the NAS. The analysis is particularly focused on examining the documents for relevance to existing and/or planned future UAV operations. The evaluation specifically focuses on potential factors that could materially affect the development of a commercial ROA industry, such as: (1) Design limitations of the CNS/ATM system, (2) Human limitations, The information presented was taken from program specifications or program office lead personnel.

Bridging the guideline implementation gap: a systematic, document-centered approach to guideline implementation.

PubMed

Shiffman, Richard N; Michel, George; Essaihi, Abdelwaheb; Thornquist, Elizabeth

2004-01-01

A gap exists between the information contained in published clinical practice guidelines and the knowledge and information that are necessary to implement them. This work describes a process to systematize and make explicit the translation of document-based knowledge into workflow-integrated clinical decision support systems. This approach uses the Guideline Elements Model (GEM) to represent the guideline knowledge. Implementation requires a number of steps to translate the knowledge contained in guideline text into a computable format and to integrate the information into clinical workflow. The steps include: (1) selection of a guideline and specific recommendations for implementation, (2) markup of the guideline text, (3) atomization, (4) deabstraction and (5) disambiguation of recommendation concepts, (6) verification of rule set completeness, (7) addition of explanations, (8) building executable statements, (9) specification of origins of decision variables and insertions of recommended actions, (10) definition of action types and selection of associated beneficial services, (11) choice of interface components, and (12) creation of requirement specification. The authors illustrate these component processes using examples drawn from recent experience translating recommendations from the National Heart, Lung, and Blood Institute's guideline on management of chronic asthma into a workflow-integrated decision support system that operates within the Logician electronic health record system. Using the guideline document as a knowledge source promotes authentic translation of domain knowledge and reduces the overall complexity of the implementation task. From this framework, we believe that a better understanding of activities involved in guideline implementation will emerge.

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

NASA Technical Reports Server (NTRS)

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

1987-01-01

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

A patient self-assessment tool for cardiac rehabilitation.

PubMed

Phelan, C; Finnell, M D; Mottla, K A

1989-01-01

A patient self-assessment tool was designed, tested, and implemented to promote cardiac-specific data collection, based on Gordon's Functional Health Patterns, to maximize patient/family involvement in determining a plan of care, and to streamline primary nurses' documentation requirements. Retrospective and concurrent chart reviews provided data for quality assurance monitoring. The results of the monitoring demonstrated that the self-assessment tool markedly improved the patient-specific data base.

Assessing Weapon System Acquisition Cycle Times: Setting Program Schedules

DTIC Science & Technology

2015-06-01

additional research, focused as follows: 1 . Acquisition schedule development: How are schedules for acquisition programs actually set and how are they...the germinating requirements documents specific to systems reviewed. A clear statement was found for only one system (Air and Missile Defense Radar...AMDR) when specific threat capabilities were projected to be operational. • Program schedule setting varies in rigor: 1 Up to the interim version of

Seismic Response to Sonic Boom-Coupled Rayleigh Waves

DTIC Science & Technology

1990-06-28

90 \\" VA ’ NOTICE When Government drawings, specifications, or other data are used for any purpose other than in connection with a definitely...your organization no longer employs the addressee, please nofify HSD/XART, Brooks AFB TX 78235-5000 to help us maintain a current mailing list. Copies...of this report should not be returned unless return is required by security considerations, contractual obligations, or notice on a specific document

Guidebook for Preparation of Aircraft System Survivability Requirements for Procurement Documents.

DTIC Science & Technology

1977-05-01

Hardening for Electrical arid Electronic EqJuipment .. ... .... .... ..... 91 8.6.5~ Crew Protection from Radioactive Particulate Matter .. ... ..... 93...compatible with the subject matter of the individual sections. These guidelines present alternate language for both general requirements and specific...relation to the threat." 18 I. # . .. . ..o JTCG/AS-77-D-001 "’ Pasive IR suppression will be designed into the air vehicle utilizing a combination of hot

Data Specifications for the Landsat Data Continuity Mission

USGS Publications Warehouse

Irons, J.R.; Speciale, N.J.; Douglas, McCuistion J.; Masek, J.G.; Markham, B.L.; Storey, James C.; Lencioni, D.E.; Ryan, R.E.

2003-01-01

The National Aeronautics and Space Administration (NASA) plans to procure data from a privately-owned and commercially-operated remote sensing system for the next Landsat mission, the Landsat Data Continuity Mission (LDCM). Data requirements are documented in an LDCM Data Specification. The specifications require delivery of data covering 250 Landsat scenes on a daily basis. The data are to be acquired in a manner that affords seasonal coverage of the global land mass. Data are required for the heritage reflective Thematic Mapper (TM) spectral bands plus two new bands, a blue band for coastal zone observations and a short wave infrared band for cirrus cloud detection. The specifications do not require thermal data, representing a departure from the TM heritage. The specification also requires data providing a 30 m ground sample distance for each of the spectral bands with the exception of the new cirrus cloud band at 120 m. An absolute uncertainty of 5 percent or less is required for radiometrically corrected LDCM data and the commercial operator is required to deliver data that can be registered to a cartographic projection with an uncertainty of 65 m or less. Procuring data from a commercial operator represents a new approach for the 30-year-old Landsat Program. The LDCM Data Specification will ensure that the procured data provides continuity of the Landsat data stream and advances the mission.

Requirements for a documentation of the image manipulation processes within PACS

NASA Astrophysics Data System (ADS)

Retter, Klaus; Rienhoff, Otto; Karsten, Ch.; Prince, Hazel E.

1990-08-01

This paper discusses to which extent manipulation functions which have been applied to images handled in PACS should be documented. After postulating an increasing amount of postprocessing features on PACS-consoles, legal, educational and medical reasons for a documentation of image manipulation processes are presented. Besides legal necessities, aspects of storage capacity, response time, and potential uses determine the extent of this documentation. Is there a specific kind of manipulation functions which has to be documented generally? Should the physician decide which parts of the various pathways he tries are recorded by the system? To distinguish, for example, between reversible and irreversible functions or between interactive and non-interactive functions is one step towards a solution. Another step is to establish definitions for terms like "raw" and "final" image. The paper systematizes these questions and offers strategic help. The answers will have an important impact on PACS design and functionality.

Framework for Architecture Trade Study Using MBSE and Performance Simulation

NASA Technical Reports Server (NTRS)

Ryan, Jessica; Sarkani, Shahram; Mazzuchim, Thomas

2012-01-01

Increasing complexity in modern systems as well as cost and schedule constraints require a new paradigm of system engineering to fulfill stakeholder needs. Challenges facing efficient trade studies include poor tool interoperability, lack of simulation coordination (design parameters) and requirements flowdown. A recent trend toward Model Based System Engineering (MBSE) includes flexible architecture definition, program documentation, requirements traceability and system engineering reuse. As a new domain MBSE still lacks governing standards and commonly accepted frameworks. This paper proposes a framework for efficient architecture definition using MBSE in conjunction with Domain Specific simulation to evaluate trade studies. A general framework is provided followed with a specific example including a method for designing a trade study, defining candidate architectures, planning simulations to fulfill requirements and finally a weighted decision analysis to optimize system objectives.

25 CFR 900.45 - What specific minimum requirements shall an Indian tribe or tribal organization's financial...

Code of Federal Regulations, 2010 CFR

2010-04-01

.... (b) Accounting records. The financial management system shall maintain records sufficiently detailed... Principles for Educational Institutions.” (f) Source documentation. The financial management system shall... or tribal organization's financial management system contain to meet these standards? 900.45 Section...

31 CFR 103.28 - Identification required.

Code of Federal Regulations, 2010 CFR

2010-07-01

... cashing checks for nondepositors (e.g., a drivers license or credit card). A bank signature card may be... specific identifying information (i.e., the account number of the credit card, the driver's license number... the United States must be made by passport, alien identification card, or other official document...

A Syllabus for Biol 242--Human Anatomy.

ERIC Educational Resources Information Center

Jacob, Willis H.

This document is the fall and spring semester course syllabus of Biology 242--Human Anatomy at Southern University (Louisiana). Sections include: (1) Descriptive Information; (2) Specification of Course Goals and Objectives; (3) Readings; (4) Description of Instructional Procedures; (5) Course Requirements; (6) Course Schedule; (7) Evaluation of…

Incipient I Fire Brigade Training & Certification.

ERIC Educational Resources Information Center

Anoka-Hennepin Technical Coll., Minneapolis, MN.

This document contains course materials for the minimum general and Koch-specific requirements for the fire suppression training and education portion of the integrated industrial emergency response team training program. The various levels of performance were developed with the National Fire standard 600, Private Fire Brigades. The training is…

The Bartlesville System; TGISS Software Documentation.

ERIC Educational Resources Information Center

Roberts, Tommy L.; And Others

TGISS (Total Guidance Information Support System) is an information storage and retrieval system specifically designed to meet the needs and requirements of a counselor in the Bartlesville Public School environment. The system, which is a combination of man/machine capabilities, includes the hardware and software necessary to extend the…

Cryptographic framework for document-objects resulting from multiparty collaborative transactions.

PubMed

Goh, A

2000-01-01

Multiparty transactional frameworks--i.e. Electronic Data Interchange (EDI) or Health Level (HL) 7--often result in composite documents which can be accurately modelled using hyperlinked document-objects. The structural complexity arising from multiauthor involvement and transaction-specific sequencing would be poorly handled by conventional digital signature schemes based on a single evaluation of a one-way hash function and asymmetric cryptography. In this paper we outline the generation of structure-specific authentication hash-trees for the the authentication of transactional document-objects, followed by asymmetric signature generation on the hash-tree value. Server-side multi-client signature verification would probably constitute the single most compute-intensive task, hence the motivation for our usage of the Rabin signature protocol which results in significantly reduced verification workloads compared to the more commonly applied Rivest-Shamir-Adleman (RSA) protocol. Data privacy is handled via symmetric encryption of message traffic using session-specific keys obtained through key-negotiation mechanisms based on discrete-logarithm cryptography. Individual client-to-server channels can be secured using a double key-pair variation of Diffie-Hellman (DH) key negotiation, usage of which also enables bidirectional node authentication. The reciprocal server-to-client multicast channel is secured through Burmester-Desmedt (BD) key-negotiation which enjoys significant advantages over the usual multiparty extensions to the DH protocol. The implementation of hash-tree signatures and bi/multidirectional key negotiation results in a comprehensive cryptographic framework for multiparty document-objects satisfying both authentication and data privacy requirements.

Integrated Information Systems for Electronic Chemotherapy Medication Administration

PubMed Central

Levy, Mia A.; Giuse, Dario A.; Eck, Carol; Holder, Gwen; Lippard, Giles; Cartwright, Julia; Rudge, Nancy K.

2011-01-01

Introduction: Chemotherapy administration is a highly complex and distributed task in both the inpatient and outpatient infusion center settings. The American Society of Clinical Oncology and the Oncology Nursing Society (ASCO/ONS) have developed standards that specify procedures and documentation requirements for safe chemotherapy administration. Yet paper-based approaches to medication administration have several disadvantages and do not provide any decision support for patient safety checks. Electronic medication administration that includes bar coding technology may provide additional safety checks, enable consistent documentation structure, and have additional downstream benefits. Methods: We describe the specialized configuration of clinical informatics systems for electronic chemotherapy medication administration. The system integrates the patient registration system, the inpatient order entry system, the pharmacy information system, the nursing documentation system, and the electronic health record. Results: We describe the process of deploying this infrastructure in the adult and pediatric inpatient oncology, hematology, and bone marrow transplant wards at Vanderbilt University Medical Center. We have successfully adapted the system for the oncology-specific documentation requirements detailed in the ASCO/ONS guidelines for chemotherapy administration. However, several limitations remain with regard to recording the day of treatment and dose number. Conclusion: Overall, the configured systems facilitate compliance with the ASCO/ONS guidelines and improve the consistency of documentation and multidisciplinary team communication. Our success has prompted us to deploy this infrastructure in our outpatient chemotherapy infusion centers, a process that is currently underway and that will require a few unique considerations. PMID:22043185

Public health law for the collection and reporting of health care-associated infections.

PubMed

Meier, Benjamin Mason; Stone, Patricia W; Gebbie, Kristine M

2008-10-01

State-based laws for reporting of health care-associated infections (HAI) have developed and changed dramatically in recent years, affecting the costs of reporting and impact on infection rates. It is necessary for practitioners of infection control to understand these changing legal frameworks and their application to practice. Employing systematic state-based research, the researchers have documented legislation and administrative regulations for institution-specific HAI reporting, using this information to create a comprehensive resource on state-based laws for mandatory HAI reporting. As of August 27, 2007, 24 states have adopted laws requiring reporting of HAI rates, with an additional 7 states currently considering legislation that would require HAI reporting and 19 states employing detailed regulation in the absence of any current legislative authorization specific to HAI. This study documents (1) which states require reporting of HAI and, if so, whether this is done by legislation or administrative regulation; (2) whether the specific HAIs to be reported are identified in state law or codified generally as "diseases of public health importance," with reporting specified by administrative regulation; and (3) what reporting policies and procedures are detailed in law. Through analysis of the collected information, the researchers have examined the degree to which states have modernized their respective public health laws to approach mandatory reporting by way of general legislation regarding "matters of public health importance" and subsequent detailed administrative regulation to specify those matters.

Robust Requirements Tracing via Internet Search Technology: Improving an IV and V Technique. Phase 2

NASA Technical Reports Server (NTRS)

Hayes, Jane; Dekhtyar, Alex

2004-01-01

There are three major objectives to this phase of the work. (1) Improvement of Information Retrieval (IR) methods for Independent Verification and Validation (IV&V) requirements tracing. Information Retrieval methods are typically developed for very large (order of millions - tens of millions and more documents) document collections and therefore, most successfully used methods somewhat sacrifice precision and recall in order to achieve efficiency. At the same time typical IR systems treat all user queries as independent of each other and assume that relevance of documents to queries is subjective for each user. The IV&V requirements tracing problem has a much smaller data set to operate on, even for large software development projects; the set of queries is predetermined by the high-level specification document and individual requirements considered as query input to IR methods are not necessarily independent from each other. Namely, knowledge about the links for one requirement may be helpful in determining the links of another requirement. Finally, while the final decision on the exact form of the traceability matrix still belongs to the IV&V analyst, his/her decisions are much less arbitrary than those of an Internet search engine user. All this suggests that the information available to us in the framework of the IV&V tracing problem can be successfully leveraged to enhance standard IR techniques, which in turn would lead to increased recall and precision. We developed several new methods during Phase II; (2) IV&V requirements tracing IR toolkit. Based on the methods developed in Phase I and their improvements developed in Phase II, we built a toolkit of IR methods for IV&V requirements tracing. The toolkit has been integrated, at the data level, with SAIC's SuperTracePlus (STP) tool; (3) Toolkit testing. We tested the methods included in the IV&V requirements tracing IR toolkit on a number of projects.

Hanford Site National Environmental Policy Act (NEPA) Characterization Report, Revision 17

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

Neitzel, Duane A.; Bunn, Amoret L.; Cannon, Sandra D.

2005-09-30

This document describes the U.S. Department of Energy’s (DOE) Hanford Site environment. It is updated each year and is intended to provide a consistent description of the Hanford Site environment for the many environmental documents being prepared by DOE contractors concerning the National Environmental Policy Act (NEPA). No statements about significance or environmental consequences are provided. This year’s report is the seventeenth revision of the original document published in 1988 and is (until replaced by the eighteenth revision) the only version that is relevant for use in the preparation of Hanford NEPA, State Environmental Policy Act (SEPA), and Comprehensive Environmentalmore » Response, Compensation, and Liability Act (CERCLA) documents. The two chapters included in this document (Chapters 4 and 6) are numbered to correspond to the chapters where such information is typically presented in environmental impact statements (EISs) and other Hanford Site NEPA or CERCLA documentation. Chapter 4.0 (Affected Environment) describes Hanford Site climate and meteorology; air quality; geology; hydrology; ecology; cultural, archaeological, and historical resources; socioeconomics; noise; and occupational health and safety. Sources for extensive tabular data related to these topics are provided in the chapter. Most subjects are divided into a general description of the characteristics of the Hanford Site, followed by site-specific information, where available, of the 100, 200, 300, and other areas. This division allows the reader to go directly to those sections of particular interest. When specific information on each of these separate areas is not complete or available, the general Hanford Site description should be used. Chapter 6.0 (Statutory and Regulatory Requirements) describes federal and state laws and regulations, DOE directives and permits, and presidential executive orders that are applicable to the NEPA documents prepared for Hanford Site activities. Information in Chapter 6 of this document can be adapted and supplemented with specific information for a chapter covering statutory and regulatory requirements in an environmental assessment or environmental impact statement. When preparing environmental assessments and EISs, authors should also be cognizant of the document titled Recommendations for the Preparation of Environmental Assessments and Environmental Impact Statements published by the DOE Office of NEPA Oversight (DOE 2004). Additional guidance on preparing DOE NEPA documents can be found at http://tis.eh.doe.gov/nepa/guidance.html. Any interested individual seeking baseline data on the Hanford Site and its past activities may also use the information contained in this document to evaluate projected activities and their impacts. For this 2005 revision, the following sections of the document were reviewed by the authors and updated with the best available information through May 2005: Climate and Meteorology Air Quality Geology – Seismicity section only Hydrology – Flow charts for the Columbia and Yakima rivers only Ecology – Threatened and Endangered Species subsection only Socioeconomics Occupational Safety All of Chapter 6.« less

Tank waste remediation system functions and requirements document

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

Carpenter, K.E

1996-10-03

This is the Tank Waste Remediation System (TWRS) Functions and Requirements Document derived from the TWRS Technical Baseline. The document consists of several text sections that provide the purpose, scope, background information, and an explanation of how this document assists the application of Systems Engineering to the TWRS. The primary functions identified in the TWRS Functions and Requirements Document are identified in Figure 4.1 (Section 4.0) Currently, this document is part of the overall effort to develop the TWRS Functional Requirements Baseline, and contains the functions and requirements needed to properly define the top three TWRS function levels. TWRS Technicalmore » Baseline information (RDD-100 database) included in the appendices of the attached document contain the TWRS functions, requirements, and architecture necessary to define the TWRS Functional Requirements Baseline. Document organization and user directions are provided in the introductory text. This document will continue to be modified during the TWRS life-cycle.« less

Actual issues of introduction of continuous emission monitoring systems for control of negative impact of TPP to atmospheric air

NASA Astrophysics Data System (ADS)

Kondrateva, O. E.; Roslyakov, P. V.; Borovkova, A. M.; Loktionov, O. A.

2017-11-01

Over the past 3 years there have been significant changes in Russian environmental legislation related to the transition to technological regulation based on the principles of the best available technologies (BAT). These changes also imply control and accounting of the harmful impact of industrial enterprises on the environment. Therefore, a mandatory requirement for equipping automatic continuous emission monitoring systems (ACEMS) is established for all large TPPs. For a successful practical solution of the problem of introducing such systems in the whole country there is an urgent need to develop the governing regulatory document for the design and operation of systems for continuous monitoring of TPP emissions into the air, allowing within reasonable limits to unify these systems for their work with the state data fund of state environmental monitoring and make easier the process of their implementation at operating facilities for industrial enterprises. Based on the large amount of research in the field of creation of ACEMS, which conducted in National Research University “MPEI”, a draft guidance document was developed, which includes the following regulatory provisions: goals and objectives of ACEMS, the stages of their introduction rules of carrying out preliminary inspection of energy facilities, requirements to develop technical specifications, general requirements for the operation of ACEMS, requirements to the structure and elements of ACEMS, recommendations on selection of places of measuring equipment installation, rules for execution, commissioning and acceptance testing, continuous measurement method, method for determination of the current gross and specific emissions. The draft guidance document, developed by the National Research University “MPEI”, formed the basis of the Preliminary national standards PNST 187-2017 “Automatic systems for continuous control and metering of contaminants emissions from thermal electric power stations into the atmospheric air. General requirements”. [1

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.

Facility effluent monitoring plan for the plutonium uranium extraction facility

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

Wiegand, D.L.

A facility effluent monitoring plan is required by the US Department of Energy in DOE Order 5400.1 for any operations that involve hazardous materials and radioactive substances that could impact employee or public safety or the environment. This document is prepared using the specific guidelines identified in A Guide for Preparing Hanford Site Facility Effluent Monitoring Plans, WHC-EP-0438-01. This facility effluent monitoring plan assesses effluent monitoring systems and evaluates whether they are adequate to ensure the public health and safety as specified in applicable federal, state, and local requirements. This facility effluent monitoring plan shall ensure long-range integrity of themore » effluent monitoring systems by requiring an update whenever a new process or operation introduces new hazardous materials or significant radioactive materials. This document must be reviewed annually even if there are no operational changes, and it must be updated at a minimum of every three years.« less

20 CFR 655.167 - Document retention requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 20 Employees' Benefits 3 2010-04-01 2010-04-01 false Document retention requirements. 655.167... retention requirements. (a) Entities required to retain documents. All employers filing an Application for... retain the documents and records proving compliance with this subpart. (b) Period of required retention...

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.

Qualification Strategies of Field Programmable Gate Arrays (FPGAs) for Space Application

NASA Technical Reports Server (NTRS)

Sheldon, Douglas; Schone, Harald

2005-01-01

This viewgraph document reviews the issue of using Field Programmable Gate Arrays (FPGAs) in Space Application, and the some of the strategies for qualifying the FPGA. Qualification and risk management of such complex systems requires new approaches. The paper presents a matrix approach to qualification has been presented that: - Complements historical specifications - Highlights the importance of device physics as a cornerstone to qualification. - Provides levels of risk management that expressly document trade offs. - Stresses the role of the FPGA vendor as team member in the development of modern spacecraft.

Specialty and Systems Engineering Supplement to IEEE 15288.1

DTIC Science & Technology

2017-08-28

requirements with a space-specific recommended practice. (8) Added Section 3.2.21, Systems Engineering Data Item Descriptions (DIDs...Systems Engineering Data Item Descriptions ........................................................ 17 4. Applicable Documents...and life cycle cost analyses. d. Alternative designs and capabilities of manufacturing are evaluated . e. Long-lead-time items, material source

50 CFR 660.11 - General definitions.

Code of Federal Regulations, 2010 CFR

2010-10-01

... General definitions. These definitions are specific to the fisheries covered in subparts C through G of..., subpart C; documentation of the weighing of fish relative to the requirements of § 660.13, subpart C; and... contributing to the rebuilding of overfished West Coast groundfish species. Regulations at § 660.70, Subpart C...

48 CFR 811.104-70 - Brand name or equal purchase descriptions.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 48 Federal Acquisition Regulations System 5 2010-10-01 2010-10-01 false Brand name or equal... Requirements Documents 811.104-70 Brand name or equal purchase descriptions. (a) The specification writer may use purchase descriptions that contain references to one or more brand name products only in...

A Descriptive Evaluation of Long-Term Treatment Integrity

ERIC Educational Resources Information Center

Arkoosh, Maire Kathryn; Derby, K. Mark; Wacker, David P.; Berg, Wendy; McLaughlin, T. F.; Barretto, Anjali

2007-01-01

The validity of selecting treatment contingencies on the basis of the results obtained through functional analysis is well documented. However, a number of second-generation questions have emerged: For example, what are the parameters required to achieve desired treatment outcomes? More specifically, what is the degree of treatment integrity…

75 FR 59143 - Magnuson-Stevens Fishery Conservation and Management Act; Regional Fishery Management Councils...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-09-27

... Coordinating Committee (CCC), require that the Councils' science and statistical committee (SSC) members... Council's Internet site, with alternative methods of retrieval for specific documents. The words ``to the... restrictions on lobbying; the procedures for Council member nomination, including timing for submission of...

Specifications and Other Standardization Documents Involving Cellular Plastics (Plastic Foams), Cushioning and Related Materials

DTIC Science & Technology

1976-07-01

FOR MEDICAL MATERIAL REQUIRING CONTROLLED TEMPERATURE RANGES 258 PPP-C-1683(1) 8135 69 10 Oct 73 CUSHIONING MATERIAL, EXPANDED POLYSTYRENE LOOSE FILL...Liquid immersion effect on properties of elastoaeric vulcanizates - 45 Lead deflection characteristics - 264 Loose-fill expanded polystyrene - 25f

14 CFR 49.45 - Recording of releases, cancellations, discharges, and satisfactions: special requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... DOCUMENTS Encumbrances Against Specifically Identified Aircraft Engines and Propellers § 49.45 Recording of... one engine or propeller, or both, are listed in an instrument, recorded under this subpart, that... the release, cancellation, discharge, or satisfaction must state that all of the encumbered engines or...

14 CFR 49.45 - Recording of releases, cancellations, discharges, and satisfactions: special requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... DOCUMENTS Encumbrances Against Specifically Identified Aircraft Engines and Propellers § 49.45 Recording of... one engine or propeller, or both, are listed in an instrument, recorded under this subpart, that... the release, cancellation, discharge, or satisfaction must state that all of the encumbered engines or...

14 CFR 49.45 - Recording of releases, cancellations, discharges, and satisfactions: special requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... DOCUMENTS Encumbrances Against Specifically Identified Aircraft Engines and Propellers § 49.45 Recording of... one engine or propeller, or both, are listed in an instrument, recorded under this subpart, that... the release, cancellation, discharge, or satisfaction must state that all of the encumbered engines or...

14 CFR 49.45 - Recording of releases, cancellations, discharges, and satisfactions: special requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... DOCUMENTS Encumbrances Against Specifically Identified Aircraft Engines and Propellers § 49.45 Recording of... one engine or propeller, or both, are listed in an instrument, recorded under this subpart, that... the release, cancellation, discharge, or satisfaction must state that all of the encumbered engines or...

40 CFR 172.52 - Notification exemption process.

Code of Federal Regulations, 2011 CFR

2011-07-01

... EXPERIMENTAL USE PERMITS Notification for Certain Genetically Modified Microbial Pesticides § 172.52... notification requirements of this subpart for a specific microbial pesticide or class of microbial pesticides...' Document Processing Desk at the appropriate address as set forth in 40 CFR 150.17(a) or (b). (3) Content of...

40 CFR 172.52 - Notification exemption process.

Code of Federal Regulations, 2010 CFR

2010-07-01

... EXPERIMENTAL USE PERMITS Notification for Certain Genetically Modified Microbial Pesticides § 172.52... notification requirements of this subpart for a specific microbial pesticide or class of microbial pesticides...' Document Processing Desk at the appropriate address as set forth in 40 CFR 150.17(a) or (b). (3) Content of...

36 CFR 1234.10 - What are the facility requirements for all records storage facilities?

Code of Federal Regulations, 2014 CFR

2014-07-01

... the HVAC systems, fire alarm and fire protection systems. Manual switching between sources of service... elements are protected by a properly installed, properly maintained wet-pipe automatic sprinkler system, as... must provide documentation that the facility has a fire suppression system specifically designed to...

47 CFR 1.734 - Specifications as to pleadings, briefs, and other documents; subscription.

Code of Federal Regulations, 2011 CFR

2011-10-01

... GENERAL PRACTICE AND PROCEDURE Complaints, Applications, Tariffs, and Reports Involving Common Carriers... good faith argument for the extension, modification, or reversal of existing law; and that it is not.... Upon showing of good cause, the Commission may waive the requirements of this paragraph. [53 FR 11855...

Federal Programs of Assistance to American Indians.

ERIC Educational Resources Information Center

Jones, Richard S.

Comprehensive descriptions of all federal programs which specifically benefit American Indians are compiled in this document which utilizes information contributed by government agencies and departments in 1974. The format of each program includes: (1) the name, nature, and purpose of the program; (2) eligibility requirements; (3) how to apply…

Participatory Data Collection Technique for Capturing Beginning Farmer Program Outcomes

ERIC Educational Resources Information Center

Eschbach, Cheryl L.; Sirrine, J. R.; Lizotte, Erin; Rothwell, N. L.

2016-01-01

This article describes an innovative evaluation plan we employed to capture outcomes of a multiyear beginning farmer program and, specifically, highlights the facilitation technique we used to document short-term and intermediate goals of the program that matched U.S. Department of Agriculture grant requirements and Extension administration…

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

Web Prep: How to Prepare NAS Reports For Publication on the Web

NASA Technical Reports Server (NTRS)

Walatka, Pamela; Balakrishnan, Prithika; Clucas, Jean; McCabe, R. Kevin; Felchle, Gail; Brickell, Cristy

1996-01-01

This document contains specific advice and requirements for NASA Ames Code IN authors of NAS reports. Much of the information may be of interest to other authors writing for the Web. WebPrep has a graphic Table of Contents in the form of a WebToon, which simulates a discussion between a scientist and a Web publishing consultant. In the WebToon, Frequently Asked Questions about preparing reports for the Web are linked to relevant text in the body of this document. We also provide a text-only Table of Contents. The text for this document is divided into chapters: each chapter corresponds to one frame of the WebToons. The chapter topics are: converting text to HTML, converting 2D graphic images to gif, creating imagemaps and tables, converting movie and audio files to Web formats, supplying 3D interactive data, and (briefly) JAVA capabilities. The last chapter is specifically for NAS staff authors. The Glossary-Index lists web related words and links to topics covered in the main text.

24 CFR 5.502 - Requirements concerning documents.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 24 Housing and Urban Development 1 2010-04-01 2010-04-01 false Requirements concerning documents... § 5.502 Requirements concerning documents. For any notice or document (decision, declaration, consent... regulations for requirements concerning communications with persons with disabilities.) ...

Section 3. The SPARROW Surface Water-Quality Model: Theory, Application and User Documentation

USGS Publications Warehouse

Schwarz, G.E.; Hoos, A.B.; Alexander, R.B.; Smith, R.A.

2006-01-01

SPARROW (SPAtially Referenced Regressions On Watershed attributes) is a watershed modeling technique for relating water-quality measurements made at a network of monitoring stations to attributes of the watersheds containing the stations. The core of the model consists of a nonlinear regression equation describing the non-conservative transport of contaminants from point and diffuse sources on land to rivers and through the stream and river network. The model predicts contaminant flux, concentration, and yield in streams and has been used to evaluate alternative hypotheses about the important contaminant sources and watershed properties that control transport over large spatial scales. This report provides documentation for the SPARROW modeling technique and computer software to guide users in constructing and applying basic SPARROW models. The documentation gives details of the SPARROW software, including the input data and installation requirements, and guidance in the specification, calibration, and application of basic SPARROW models, as well as descriptions of the model output and its interpretation. The documentation is intended for both researchers and water-resource managers with interest in using the results of existing models and developing and applying new SPARROW models. The documentation of the model is presented in two parts. Part 1 provides a theoretical and practical introduction to SPARROW modeling techniques, which includes a discussion of the objectives, conceptual attributes, and model infrastructure of SPARROW. Part 1 also includes background on the commonly used model specifications and the methods for estimating and evaluating parameters, evaluating model fit, and generating water-quality predictions and measures of uncertainty. Part 2 provides a user's guide to SPARROW, which includes a discussion of the software architecture and details of the model input requirements and output files, graphs, and maps. The text documentation and computer software are available on the Web at http://usgs.er.gov/sparrow/sparrow-mod/.

Technical Support Document for Version 3.9.0 of the COMcheck Software

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

Bartlett, Rosemarie; Connell, Linda M.; Gowri, Krishnan

2011-09-01

COMcheck provides an optional way to demonstrate compliance with commercial and high-rise residential building energy codes. Commercial buildings include all use groups except single family and multifamily not over three stories in height. COMcheck was originally based on ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989) requirements and is intended for use with various codes based on Standard 90.1, including the Codification of ASHRAE/IES Standard 90.1-1989 (90.1-1989 Code) (ASHRAE 1989a, 1993b) and ASHRAE/IESNA Standard 90.1-1999 (Standard 90.1-1999). This includes jurisdictions that have adopted the 90.1-1989 Code, Standard 90.1-1989, Standard 90.1-1999, or their own code based on one of these. We view Standard 90.1-1989more » and the 90.1-1989 Code as having equivalent technical content and have used both as source documents in developing COMcheck. This technical support document (TSD) is designed to explain the technical basis for the COMcheck software as originally developed based on the ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989). Documentation for other national model codes and standards and specific state energy codes supported in COMcheck has been added to this report as appendices. These appendices are intended to provide technical documentation for features specific to the supported codes and for any changes made for state-specific codes that differ from the standard features that support compliance with the national model codes and standards. Beginning with COMcheck version 3.8.0, support for 90.1-1989, 90.1-1999, and the 1998 IECC are no longer included, but those sections remain in this document for reference purposes.« less

Technical Support Document for Version 3.9.1 of the COMcheck Software

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

Bartlett, Rosemarie; Connell, Linda M.; Gowri, Krishnan

2012-09-01

COMcheck provides an optional way to demonstrate compliance with commercial and high-rise residential building energy codes. Commercial buildings include all use groups except single family and multifamily not over three stories in height. COMcheck was originally based on ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989) requirements and is intended for use with various codes based on Standard 90.1, including the Codification of ASHRAE/IES Standard 90.1-1989 (90.1-1989 Code) (ASHRAE 1989a, 1993b) and ASHRAE/IESNA Standard 90.1-1999 (Standard 90.1-1999). This includes jurisdictions that have adopted the 90.1-1989 Code, Standard 90.1-1989, Standard 90.1-1999, or their own code based on one of these. We view Standard 90.1-1989more » and the 90.1-1989 Code as having equivalent technical content and have used both as source documents in developing COMcheck. This technical support document (TSD) is designed to explain the technical basis for the COMcheck software as originally developed based on the ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989). Documentation for other national model codes and standards and specific state energy codes supported in COMcheck has been added to this report as appendices. These appendices are intended to provide technical documentation for features specific to the supported codes and for any changes made for state-specific codes that differ from the standard features that support compliance with the national model codes and standards. Beginning with COMcheck version 3.8.0, support for 90.1-1989, 90.1-1999, and the 1998 IECC and version 3.9.0 support for 2000 and 2001 IECC are no longer included, but those sections remain in this document for reference purposes.« less

Requirements-Based Conformance Testing of ARINC 653 Real-Time Operating Systems

NASA Astrophysics Data System (ADS)

Maksimov, Andrey

2010-08-01

Requirements-based testing is emphasized in avionics certification documents because this strategy has been found to be the most effective at revealing errors. This paper describes the unified requirements-based approach to the creation of conformance test suites for mission-critical systems. The approach uses formal machine-readable specifications of requirements and finite state machine model for test sequences generation on-the-fly. The paper also presents the test system for automated test generation for ARINC 653 services built on this approach. Possible application of the presented approach to various areas of avionics embedded systems testing is discussed.

Specific application for Oak Ridge National Laboratory dismantlement of Building 3004. Appendix A -- Quality assurance plan; Appendix B -- Records management plan

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

NONE

This quality assurance (QA) plan defines the QA requirements for the dismantlement and removal of Building 3004 at Oak Ridge National Laboratory (ORNL). The building is a four-story wooden trained structure with wooden siding, which resides approximately 150 ft west of the Bulk Shielding Reactor, and only several feet away from the visitors entrance to the Graphite Reactor museum. Complete descriptions and sketches are in the Performance Specification document for this project. This project is being conducted as a non-CERCLA maintenance action. This plan is an appendix to the QA plan for the ORNL Environmental Restoration (ER) Program. ORNL/ER-225, whichmore » is the source of the project QA requirements, tailors those QA requirements to the specific needs of this project as defined in ORNL/ER-225. Project-specific description and organization are also provided in this plan. Appendix B, Records Management Plan, is included.« 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

76 FR 26750 - Agency Information Collection Activities: Documentation Requirements for Articles Entered Under...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-05-09

... Activities: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions...: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions. This request... collection: Title: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment...

76 FR 39416 - Agency Information Collection Activities: Documentation Requirements for Articles Entered Under...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-07-06

... Activities: Documentation Requirements for Articles Entered Under Various Special Tariff Treatment Provisions... accordance with the Paperwork Reduction Act: Documentation Requirements for Articles Entered Under Various... techniques or other forms of information. Title: Documentation Requirements for Articles Entered Under...

5 CFR 1315.9 - Required documentation.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 5 Administrative Personnel 3 2010-01-01 2010-01-01 false Required documentation. 1315.9 Section 1315.9 Administrative Personnel OFFICE OF MANAGEMENT AND BUDGET OMB DIRECTIVES PROMPT PAYMENT § 1315.9 Required documentation. Agencies are required to ensure the following payment documentation is established...

Overseas Assignment of Sponsors who have Children with Disabilities Who Are Space-Required Students in the Department of Defense Dependents Schools (DoDDS)

DTIC Science & Technology

1992-03-01

reference (d)), general medical care is provided to family members on a space-available basis. 7. ’ndivuglzed Education Program. ( IEP ) A written document...participate in and benefit from his or her education. The IEP is further described in, and prepared under, reference (b). 8. pin oint Location. A specific...member the special education or related services required by an IEP or an evaluation required by DoD Instruction 1342.12 (reference (b)). 5. This

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.

Hanford Site National Environmental Policy Act (NEPA) Characterization

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

Duncan, Joanne P.; Burk, Kenneth W.; Chamness, Mickie A.

2007-09-27

This document describes the U.S. Department of Energy’s (DOE) Hanford Site environment. It is intended to provide a consistent description of the Hanford Site for the many environmental documents being prepared by DOE contractors concerning the National Environmental Policy Act (NEPA). No statements regarding significance or environmental consequences are provided. This year’s report is the eighteen revision of the original document published in 1988 and is (until replaced by the nineteenth revision) the only version that is relevant for use in the preparation of Hanford NEPA, State Environmental Policy Act (SEPA), and Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA)more » documents. Two chapters are included in this document (Chapters 4 and 6), numbered to correspond to chapters typically presented in environmental impact statements (EISs) and other Hanford Site NEPA or CERCLA documentation. Chapter 4.0 (Affected Environment) describes Hanford Site climate and meteorology; air quality; geology; hydrology; ecology; cultural, archaeological, and historical resources; socioeconomics; noise; and occupational health and safety. Sources for extensive tabular data related to these topics are provided in the chapter. When possible, subjects are divided into a general description of the characteristics of the Hanford Site, followed by site-specific information, where available, for the 100, 200, 300 and other areas. This division allows the reader to go directly to those sections of particular interest. When specific information on each of these separate areas is not complete or available, the general Hanford Site description should be used. Chapter 6.0 (Statutory and Regulatory Requirements) describes federal and state laws and regulations, DOE directives and permits, and presidential executive orders that are applicable to NEPA documents prepared for Hanford Site activities. Information in Chapter 6 can be adapted and supplemented with specific information covering statutory and regulatory requirements for use in an environmental assessment or environmental impact statement. When preparing environmental assessments and EISs, authors should consult Recommendations for the Preparation of Environmental Assessments and Environmental Impact Statements published by the DOE Office of NEPA Oversight (DOE 2004). Additional direction and guidance on the preparation of DOE NEPA documents can be found at http://tis.eh.doe.gov/nepa/guidance.html. Individuals seeking baseline data on the Hanford Site and its past activities may also use the information contained in this document to evaluate projected activities and their impacts. Pacific Northwest National Laboratory (PNNL) staff prepared individual sections of this document, with input from other Hanford Site contractors with the best available information through May 2007. More detailed data are available from reference sources cited or from the authors. For this 2007 revision, the following sections of the document were reviewed by the authors and updated with the best available information through May 2005: Climate and Meteorology Air Quality Geology – Seismicity section only Hydrology – Flow charts for the Columbia and Yakima rivers only Ecology – Threatened and Endangered Species subsection only Socioeconomics Occupational Safety All of Chapter 6.« less

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

Criticality Safety Evaluation of Standard Criticality Safety Requirements #1-520 g Operations in PF-4

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

Yamanaka, Alan Joseph Jr.

Guidance has been requested from the Nuclear Criticality Safety Division (NCSD) regarding processes that involve 520 grams of fissionable material or less. This Level-3 evaluation was conducted and documented in accordance with NCS-AP-004 (Ref. 1), formerly NCS-GUIDE-01. This evaluation is being written as a generic evaluation for all operations that will be able to operate using a 520-gram mass limit. Implementation for specific operations will be performed using a Level 1 CSED, which will confirm and document that this CSED can be used for the specific operation as discussed in NCS-MEMO-17-007 (Ref. 2). This Level 3 CSED updates and supersedesmore » the analysis performed in NCS-TECH-14-014 (Ref. 3).« less

NASA/NBS (National Aeronautics and Space Administration/National Bureau of Standards) standard reference model for telerobot control system architecture (NASREM)

NASA Technical Reports Server (NTRS)

Albus, James S.; Mccain, Harry G.; Lumia, Ronald

1989-01-01

The document describes the NASA Standard Reference Model (NASREM) Architecture for the Space Station Telerobot Control System. It defines the functional requirements and high level specifications of the control system for the NASA space Station document for the functional specification, and a guideline for the development of the control system architecture, of the 10C Flight Telerobot Servicer. The NASREM telerobot control system architecture defines a set of standard modules and interfaces which facilitates software design, development, validation, and test, and make possible the integration of telerobotics software from a wide variety of sources. Standard interfaces also provide the software hooks necessary to incrementally upgrade future Flight Telerobot Systems as new capabilities develop in computer science, robotics, and autonomous system control.

Goals, Objectives, and Requirements (GOR) of the Ground-based Nuclear Detonation Detection (GNDD) Team for the Office of Defense Nuclear Nonproliferation Research and Development (DNN R&D)

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

Casey, Leslie A.

The goal, objectives, and requirements (GOR) presented in this document define a framework for describing research directed specifically by the Ground-based Nuclear Detonation Detection (GNDD) Team of the National Nuclear Security Administration (NNSA). The intent of this document is to provide a communication tool for the GNDD Team with NNSA management and with its stakeholder community. It describes the GNDD expectation that much of the improvement in the proficiency of nuclear explosion monitoring will come from better understanding of the science behind the generation, propagation, recording, and interpretation of seismic, infrasound, hydroacoustic, and radionuclide signals and development of "game-changer" advancesmore » in science and technology.« less

Extracting biomedical events from pairs of text entities

PubMed Central

2015-01-01

Background Huge amounts of electronic biomedical documents, such as molecular biology reports or genomic papers are generated daily. Nowadays, these documents are mainly available in the form of unstructured free texts, which require heavy processing for their registration into organized databases. This organization is instrumental for information retrieval, enabling to answer the advanced queries of researchers and practitioners in biology, medicine, and related fields. Hence, the massive data flow calls for efficient automatic methods of text-mining that extract high-level information, such as biomedical events, from biomedical text. The usual computational tools of Natural Language Processing cannot be readily applied to extract these biomedical events, due to the peculiarities of the domain. Indeed, biomedical documents contain highly domain-specific jargon and syntax. These documents also describe distinctive dependencies, making text-mining in molecular biology a specific discipline. Results We address biomedical event extraction as the classification of pairs of text entities into the classes corresponding to event types. The candidate pairs of text entities are recursively provided to a multiclass classifier relying on Support Vector Machines. This recursive process extracts events involving other events as arguments. Compared to joint models based on Markov Random Fields, our model simplifies inference and hence requires shorter training and prediction times along with lower memory capacity. Compared to usual pipeline approaches, our model passes over a complex intermediate problem, while making a more extensive usage of sophisticated joint features between text entities. Our method focuses on the core event extraction of the Genia task of BioNLP challenges yielding the best result reported so far on the 2013 edition. PMID:26201478

Drivers of Dashboard Development (3-D): A Curricular Continuous Quality Improvement Approach.

PubMed

Shroyer, A Laurie; Lu, Wei-Hsin; Chandran, Latha

2016-04-01

Undergraduate medical education (UME) programs are seeking systematic ways to monitor and manage their educational performance metrics and document their achievement of external goals (e.g., Liaison Committee on Medical Education [LCME] accreditation requirements) and internal objectives (institution-specific metrics). In other continuous quality improvement (CQI) settings, summary dashboard reports have been used to evaluate and improve performance. The Stony Brook University School of Medicine UME leadership team developed and implemented summary dashboard performance reports in 2009 to document LCME standards/criteria compliance, evaluate medical student performance, and identify progress in attaining institutional curricular goals and objectives. Key performance indicators (KPIs) and benchmarks were established and have been routinely monitored as part of the novel Drivers of Dashboard Development (3-D) approach to curricular CQI. The systematic 3-D approach has had positive CQI impacts. Substantial improvements over time have been documented in KPIs including timeliness of clerkship grades, midclerkship feedback, student mistreatment policy awareness, and student satisfaction. Stakeholder feedback indicates that the dashboards have provided useful information guiding data-driven curricular changes, such as integrating clinician-scientists as lecturers in basic science courses to clarify the clinical relevance of specific topics. Gaining stakeholder acceptance of the 3-D approach required clear communication of preestablished targets and annual meetings with department leaders and course/clerkship directors. The 3-D approach may be considered by UME programs as a template for providing faculty and leadership with a CQI framework to establish shared goals, document compliance, report accomplishments, enrich communications, facilitate decisions, and improve performance.

Cielo Computational Environment Usage Model With Mappings to ACE Requirements for the General Availability User Environment Capabilities Release Version 1.1

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

Vigil,Benny Manuel; Ballance, Robert; Haskell, Karen

Cielo is a massively parallel supercomputer funded by the DOE/NNSA Advanced Simulation and Computing (ASC) program, and operated by the Alliance for Computing at Extreme Scale (ACES), a partnership between Los Alamos National Laboratory (LANL) and Sandia National Laboratories (SNL). The primary Cielo compute platform is physically located at Los Alamos National Laboratory. This Cielo Computational Environment Usage Model documents the capabilities and the environment to be provided for the Q1 FY12 Level 2 Cielo Capability Computing (CCC) Platform Production Readiness Milestone. This document describes specific capabilities, tools, and procedures to support both local and remote users. The model ismore » focused on the needs of the ASC user working in the secure computing environments at Lawrence Livermore National Laboratory (LLNL), Los Alamos National Laboratory, or Sandia National Laboratories, but also addresses the needs of users working in the unclassified environment. The Cielo Computational Environment Usage Model maps the provided capabilities to the tri-Lab ASC Computing Environment (ACE) Version 8.0 requirements. The ACE requirements reflect the high performance computing requirements for the Production Readiness Milestone user environment capabilities of the ASC community. A description of ACE requirements met, and those requirements that are not met, are included in each section of this document. The Cielo Computing Environment, along with the ACE mappings, has been issued and reviewed throughout the tri-Lab community.« less

Bridging the Guideline Implementation Gap: A Systematic, Document-Centered Approach to Guideline Implementation

PubMed Central

Shiffman, Richard N.; Michel, George; Essaihi, Abdelwaheb; Thornquist, Elizabeth

2004-01-01

Objective: A gap exists between the information contained in published clinical practice guidelines and the knowledge and information that are necessary to implement them. This work describes a process to systematize and make explicit the translation of document-based knowledge into workflow-integrated clinical decision support systems. Design: This approach uses the Guideline Elements Model (GEM) to represent the guideline knowledge. Implementation requires a number of steps to translate the knowledge contained in guideline text into a computable format and to integrate the information into clinical workflow. The steps include: (1) selection of a guideline and specific recommendations for implementation, (2) markup of the guideline text, (3) atomization, (4) deabstraction and (5) disambiguation of recommendation concepts, (6) verification of rule set completeness, (7) addition of explanations, (8) building executable statements, (9) specification of origins of decision variables and insertions of recommended actions, (10) definition of action types and selection of associated beneficial services, (11) choice of interface components, and (12) creation of requirement specification. Results: The authors illustrate these component processes using examples drawn from recent experience translating recommendations from the National Heart, Lung, and Blood Institute's guideline on management of chronic asthma into a workflow-integrated decision support system that operates within the Logician electronic health record system. Conclusion: Using the guideline document as a knowledge source promotes authentic translation of domain knowledge and reduces the overall complexity of the implementation task. From this framework, we believe that a better understanding of activities involved in guideline implementation will emerge. PMID:15187061

OSHA medical and workplace surveillance requirements and NIOSH recommendations (for employees exposed to toxic substances and other work hazards)

NASA Technical Reports Server (NTRS)

Cooper, L. P.

1983-01-01

Both OSHA medical and work place surveillance requirements and NIOSH recommendations were prepared as a desk reference to help occupational health professionals to perform their duties. The medical surveillance information focuses on frequency of physical examinations, specific problems that may arise as a result of exposure (e.g., decreased immunocompetence, weight loss, ets.), conditions that intensify the harmful effects of exposure (e.g., medication an exposed employee may be taking, cigarette smoking, etc.), the areas that should be scrutinized in medical and work histories and during the physical exam, and specific clinical tests that should be conducted. Recordkeeping requirements are also specified. The workplace surveillance information consists of monitoring requirements, personal protective equipment requirements, and recordkeeping requirements. Such details as the sampling devices that should be used, the type of respirators that should be worn, and the frequency of inspections are included. This document does not specify the training, labeling and posting, and safe work practice requirements and recommendations due to space considerations.

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

Quality assurance in digital dental radiography--justification and dose reduction in dental and maxillofacial radiology.

PubMed

Hellstern, F; Geibel, M-A

2012-01-01

To evaluate the implementation of quality assurance requirements for digital dental radiography in routine clinical practice. The results should be discussed by radiation protection authorities in the context of the relevant legal requirements and current debates on radiation protection. Two hundred digital dental radiographs were randomly selected from the digital database of the Department of Dentistry's Dental and Maxillofacial Surgery Clinic, Ulm University, and evaluated for various aspects of image quality and compliance with radiographic documentation requirements. The dental films were prepared by different radiology assistants (RAs) using one of two digital intraoral radiographic systems: Sirona Heliodent DS, 60 kV, focal spot size: 0.7 mm (group A) or KaVo Gendex 765 DC, 65 kV, focal spot size: 0.4 mm (group B). Radiographic justification was documented in 70.5% of cases, and the radiographic findings in 76.5%. Both variables were documented in the patient records as well as in the software in 14% of cases. Clinical documentation of the required information (name of the responsible dentist and radiology assistant, date, patient name, department, tube voltage, tube current, exposure time, type of radiograph, film size, department and serial number of the dental radiograph) was 100% complete in all cases. Moreover, the department certified according to DIN ISO 9001:2008 specifications demonstrated complete clinical documentation of radiographic justifications and radiographic findings. The entire dentition was visible on 83% of the digital films. The visible area corresponded to the target region on 85.7% of the digital dental radiographs. Seven to 8.5% of the images were classified as "hypometric" or "hypermetric". This study indicates that improvements in radiology training and continuing education fordentists and dental staff performing x-ray examinations are needed to ensure consistent high quality of digital dental radiography. Implementation of internal radiological quality assurance programs, as required by public law in Germany since 2010 (SGB V), would appear prudent.

Developing topic-specific search filters for PubMed with click-through data.

PubMed

Li, J; Lu, Z

2013-01-01

Search filters have been developed and demonstrated for better information access to the immense and ever-growing body of publications in the biomedical domain. However, to date the number of filters remains quite limited because the current filter development methods require significant human efforts in manual document review and filter term selection. In this regard, we aim to investigate automatic methods for generating search filters. We present an automated method to develop topic-specific filters on the basis of users' search logs in PubMed. Specifically, for a given topic, we first detect its relevant user queries and then include their corresponding clicked articles to serve as the topic-relevant document set accordingly. Next, we statistically identify informative terms that best represent the topic-relevant document set using a background set composed of topic irrelevant articles. Lastly, the selected representative terms are combined with Boolean operators and evaluated on benchmark datasets to derive the final filter with the best performance. We applied our method to develop filters for four clinical topics: nephrology, diabetes, pregnancy, and depression. For the nephrology filter, our method obtained performance comparable to the state of the art (sensitivity of 91.3%, specificity of 98.7%, precision of 94.6%, and accuracy of 97.2%). Similarly, high-performing results (over 90% in all measures) were obtained for the other three search filters. Based on PubMed click-through data, we successfully developed a high-performance method for generating topic-specific search filters that is significantly more efficient than existing manual methods. All data sets (topic-relevant and irrelevant document sets) used in this study and a demonstration system are publicly available at http://www.ncbi.nlm.nih.gov/CBBresearch/Lu/downloads/CQ_filter/

Developing Topic-Specific Search Filters for PubMed with Click-Through Data

PubMed Central

Li, Jiao; Lu, Zhiyong

2013-01-01

Summary Objectives Search filters have been developed and demonstrated for better information access to the immense and ever-growing body of publications in the biomedical domain. However, to date the number of filters remains quite limited because the current filter development methods require significant human efforts in manual document review and filter term selection. In this regard, we aim to investigate automatic methods for generating search filters. Methods We present an automated method to develop topic-specific filters on the basis of users’ search logs in PubMed. Specifically, for a given topic, we first detect its relevant user queries and then include their corresponding clicked articles to serve as the topic-relevant document set accordingly. Next, we statistically identify informative terms that best represent the topic-relevant document set using a background set composed of topic irrelevant articles. Lastly, the selected representative terms are combined with Boolean operators and evaluated on benchmark datasets to derive the final filter with the best performance. Results We applied our method to develop filters for four clinical topics: nephrology, diabetes, pregnancy, and depression. For the nephrology filter, our method obtained performance comparable to the state of the art (sensitivity of 91.3%, specificity of 98.7%, precision of 94.6%, and accuracy of 97.2%). Similarly, high-performing results (over 90% in all measures) were obtained for the other three search filters. Conclusion Based on PubMed click-through data, we successfully developed a high-performance method for generating topic-specific search filters that is significantly more efficient than existing manual methods. All data sets (topic-relevant and irrelevant document sets) used in this study and a demonstration system are publicly available at http://www.ncbi.nlm.nih.gov/CBBresearch/Lu/downloads/CQ_filter/ PMID:23666447

Criteria Considered in Selecting Feed Items for Americium-241 Oxide Production Operations

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

Schulte, Louis D.

The analysis in this document serves the purpose of defining a number of attributes in selection of feed items to be utilized in recovery/recycle of Pu and also production operations of 241AmO 2 material intended to meet specification requirements. This document was written in response to a specific request on the part of the 2014 annual program review which took place over the dates of October 28-29, 2014. A number of feed attributes are noted including: (1) Non-interference with existing Pu recovery operations; (2) Content of sufficient 241Am to allow process efficiency in recovery operations; (3) Absence of indications thatmore » 243Am might be mixed in with the Pu/ 241Am material; (4) Absence of indications that Cm might be mixed in with the Pu/ 241Am material; (5) Absence of indications of other chemical elements that would present difficulty in chemical separation from 241Am; (6) Feed material not expected to present difficulty in dissolution; (7) Dose issues; (8) Process efficiency; (9) Size; (10) Hazard associated with items and package configuration in the vault; (11) Within existing NEPA documentation. The analysis in this document provides a baseline of attributes considered for feed materials, but does not presume to replace the need for technical expertise and judgment on the part of individuals responsible for selecting the material feed to be processed. This document is not comprehensive as regards all attributes that could prove to be important. The value of placing a formal QA hold point on accepting feed items versus more informal management of feed items is discussed in the summation of this analysis. The existing planned QA hold points on 241AmO 2 products produced and packaged may be adequate as the entire project is based on QA of the product rather than QA of the process. The probability of introduction of items that would inherently cause the 241AmO 2 products produced to be outside of specification requirements appears to be rather small.« less

Modeling Rare and Unique Documents: Using FRBR[subscript OO]/CIDOC CRM

ERIC Educational Resources Information Center

Le Boeuf, Patrick

2012-01-01

Both the library and the museum communities have developed conceptual models for the information they produce about the collections they hold: FRBR (Functional Requirements for Bibliographic Records) and CIDOC CRM (Conceptual Reference Model). But neither proves perfectly adequate when it comes to some specific types of rare and unique materials:…

40 CFR 60.2910 - What site-specific documentation is required?

Code of Federal Regulations, 2011 CFR

2011-07-01

... paragraphs (a)(1) through (9) of this section. You must maintain this information and the training records...) Records showing the names of OSWI unit operators who have completed review of the information in paragraph... review and all subsequent annual reviews. (2) Records showing the names of the OSWI unit operators who...

40 CFR 60.2910 - What site-specific documentation is required?

Code of Federal Regulations, 2012 CFR

2012-07-01

... paragraphs (a)(1) through (9) of this section. You must maintain this information and the training records...) Records showing the names of OSWI unit operators who have completed review of the information in paragraph... review and all subsequent annual reviews. (2) Records showing the names of the OSWI unit operators who...

Extended School Year (ESY) Services: Iowa Standards for Students with Disabilities.

ERIC Educational Resources Information Center

Iowa State Dept. of Education, Des Moines. Bureau of Children, Family and Community Services.

This publication is intended to ensure that consideration for and provision of extended school year services (ESY services) for students with disabilities are consistent with the requirements of federal law, Iowa state rules, and Iowa's adopted educational standards. Part 1 of the document discusses the specific addition of ESY services to the…

Jobs for Which Junior College, Technical Institute, or Other Specialized Training Is Usually Required.

ERIC Educational Resources Information Center

Bureau of Labor Statistics (DOL), Washington, DC.

Selected from the "Occupational Outlook Handbook," the listings included in this document represent a number of occupations for which junior college or other special training is useful. Each listing, grouped under a broader occupational area, provides a specific occupational title, number employed in the occupation in 1974, qualifications and…

School Facilities: America's Schools Not Designed or Equipped for 21st Century. Report to Congressional Requesters.

ERIC Educational Resources Information Center

General Accounting Office, Washington, DC. Health, Education, and Human Services Div.

This document presents findings of a General Accounting Office study that examined the extent to which America's schools have the physical capacity to support learning into the 21st century. Specifically, it looked at facilities requirements, environmental conditions, educational technologies, and facility infrastructure. Data were collected…

Coastal coho salmon research in the West Fork Smith River: Patterns of coho salmon size and survival within a complex watershed

EPA Science Inventory

Effective habitat restoration planning requires the ability to anticipate fish population responses to altered habitats. The EPA has conducted network-scale research to document habitat-specific growth and survival of juvenile salmonids in a complex watershed. These findings ha...

Information Brokers: Case Studies of Successful Ventures.

ERIC Educational Resources Information Center

Holland Johnson, Alice Jane

This guide is intended for librarians planning to start an information brokerage, whether as an entrepreneur or as a member of a document delivery group in a library. The guide identifies specific skills and relevant characteristics required to establish a successful information brokerage firm and describes a model to assist readers in the process…

Fish and other aquatic resource trends in the United States

Treesearch

Andrew J. Loftus; Curtis H. Flather

2000-01-01

This report documents the general trends in fisheries and aquatic resources for the nation as required by the Renewable Resources Planning Act (RPA) of 1974. The report highlights major trends in water quality, specific fish populations, resource utilization, and imperiled aquatic fauna. Relationships between land use, water quality, and aquatic species conditions are...

75 FR 76731 - Request for Comment for Report on In-State Broadcast Programming

Federal Register 2010, 2011, 2012, 2013, 2014

2010-12-09

...; solicitation of comments. SUMMARY: This document solicits public comments and data for use in preparation of a.... In addition, the Bureau requests data for use in preparation of the report. 4. Section 304(1... use in preparation of the required report. 2. Specifically, Section 304 of STELA states: SEC. 304...

A Model for Effectively Assessing Student Learning Outcomes

ERIC Educational Resources Information Center

Ohia, Uche O.

2011-01-01

This paper describes a model proven to be effective for assessing and documenting evidence of student learning outcomes. Specifically, it will share a model, F.A.M.O.U.S. Copyright ©2008, which is an acronym exemplifying six effective steps for complying with institutional accountability and eternal assessment requirements proscribed by the…

Federal Guidelines - Operation and Maintenance of Wastewater Treatment Facilities.

ERIC Educational Resources Information Center

Environmental Protection Agency, Washington, DC. Office of Water Programs.

This document contains the federal guidelines for meeting the specific requirements of the Federal Water Pollution Control Act Amendments of 1972. These guidelines are also intended to assist in meeting the regulations for grant assisted facility construction and to provide information on the key elements to be included in the operation plans for…

Wind shear training applications for 91/135

NASA Technical Reports Server (NTRS)

Arbon, ED

1991-01-01

The requirement for wind shear training of all pilots has been demonstrated too often by the accident statistics of past years. Documents were developed to train airline crews on specific aircraft and to teach recognition of the meteorological conditions that are conducive to wind shear and microburst formation. A Wind Shear Training Aid program is discussed.

Technical Support Document for Version 3.4.0 of the COMcheck Software

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

Bartlett, Rosemarie; Connell, Linda M.; Gowri, Krishnan

2007-09-14

COMcheck provides an optional way to demonstrate compliance with commercial and high-rise residential building energy codes. Commercial buildings include all use groups except single family and multifamily not over three stories in height. COMcheck was originally based on ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989) requirements and is intended for use with various codes based on Standard 90.1, including the Codification of ASHRAE/IES Standard 90.1-1989 (90.1-1989 Code) (ASHRAE 1989a, 1993b) and ASHRAE/IESNA Standard 90.1-1999 (Standard 90.1-1999). This includes jurisdictions that have adopted the 90.1-1989 Code, Standard 90.1-1989, Standard 90.1-1999, or their own code based on one of these. We view Standard 90.1-1989more » and the 90.1-1989 Code as having equivalent technical content and have used both as source documents in developing COMcheck. This technical support document (TSD) is designed to explain the technical basis for the COMcheck software as originally developed based on the ANSI/ASHRAE/IES Standard 90.1-1989 (Standard 90.1-1989). Documentation for other national model codes and standards and specific state energy codes supported in COMcheck has been added to this report as appendices. These appendices are intended to provide technical documentation for features specific to the supported codes and for any changes made for state-specific codes that differ from the standard features that support compliance with the national model codes and standards.« less

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.

50 CFR 300.185 - Documentation, reporting and recordkeeping requirements for consignment documents and re-export...

Code of Federal Regulations, 2012 CFR

2012-10-01

... recordkeeping requirements for consignment documents and re-export certificates. 300.185 Section 300.185..., reporting and recordkeeping requirements for consignment documents and re-export certificates. (a) Imports... apply only to entries for consumption. The reporting requirements of paragraph (a)(3) of this section do...

50 CFR 300.185 - Documentation, reporting and recordkeeping requirements for consignment documents and re-export...

Code of Federal Regulations, 2014 CFR

2014-10-01

... recordkeeping requirements for consignment documents and re-export certificates. 300.185 Section 300.185..., reporting and recordkeeping requirements for consignment documents and re-export certificates. (a) Imports... apply only to entries for consumption. The reporting requirements of paragraph (a)(3) of this section do...

50 CFR 300.185 - Documentation, reporting and recordkeeping requirements for consignment documents and re-export...

Code of Federal Regulations, 2013 CFR

2013-10-01

... recordkeeping requirements for consignment documents and re-export certificates. 300.185 Section 300.185..., reporting and recordkeeping requirements for consignment documents and re-export certificates. (a) Imports... apply only to entries for consumption. The reporting requirements of paragraph (a)(3) of this section do...

22 CFR 40.71 - Documentation requirements for immigrants.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 22 Foreign Relations 1 2010-04-01 2010-04-01 false Documentation requirements for immigrants. 40... NONIMMIGRANTS AND IMMIGRANTS UNDER THE IMMIGRATION AND NATIONALITY ACT, AS AMENDED Documentation Requirements § 40.71 Documentation requirements for immigrants. INA 212(a)(7)(A) is not applicable at the time of...

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.

Basic Hitchhiker Payload Requirements

NASA Technical Reports Server (NTRS)

Horan, Stephen

1999-01-01

This document lists the requirements for the NMSU Hitchhiker experiment payload that were developed as part of the EE 498/499 Capstone Design class during the 1999-2000 academic year. This document is used to describe the system needs as described in the mission document. The requirements listed here are those primarily used to generate the basic electronic and data processing requirements developed in the class design document. The needs of the experiment components are more fully described in the draft NASA hitchhiker customer requirements document. Many of the details for the overall payload are given in full detail in the NASA hitchhiker documentation.

Functions and requirements document for interim store solidified high-level and transuranic waste

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

Smith-Fewell, M.A., Westinghouse Hanford

1996-05-17

The functions, requirements, interfaces, and architectures contained within the Functions and Requirements (F{ampersand}R) Document are based on the information currently contained within the TWRS Functions and Requirements database. The database also documents the set of technically defensible functions and requirements associated with the solidified waste interim storage mission.The F{ampersand}R Document provides a snapshot in time of the technical baseline for the project. The F{ampersand}R document is the product of functional analysis, requirements allocation and architectural structure definition. The technical baseline described in this document is traceable to the TWRS function 4.2.4.1, Interim Store Solidified Waste, and its related requirements, architecture,more » and interfaces.« less

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

Public health law for the collection and reporting of health care–associated infections

PubMed Central

Meier, Benjamin Mason; Stone, Patricia W.; Gebbie, Kristine M.

2015-01-01

Background State-based laws for reporting of health care-associated infections (HAI) have developed and changed dramatically in recent years, affecting the costs of reporting and impact on infection rates. It is necessary for practitioners of infection control to understand these changing legal frameworks and their application to practice. Methods Employing systematic state-based research, the researchers have documented legislation and administrative regulations for institution-specific HAI reporting, using this information to create a comprehensive resource on state-based laws for mandatory HAI reporting. Results As of August 27, 2007, 24 states have adopted laws requiring reporting of HAI rates, with an additional 7 states currently considering legislation that would require HAI reporting and 19 states employing detailed regulation in the absence of any current legislative authorization specific to HAI. This study documents (1) which states require reporting of HAI and, if so, whether this is done by legislation or administrative regulation; (2) whether the specific HAIs to be reported are identified in state law or codified generally as “diseases of public health importance,” with reporting specified by administrative regulation; and (3) what reporting policies and procedures are detailed in law. Conclusion Through analysis of the collected information, the researchers have examined the degree to which states have modernized their respective public health laws to approach mandatory reporting by way of general legislation regarding “matters of public health importance” and subsequent detailed administrative regulation to specify those matters. PMID:18926306

Multisource data fusion for documenting archaeological sites

NASA Astrophysics Data System (ADS)

Knyaz, Vladimir; Chibunichev, Alexander; Zhuravlev, Denis

2017-10-01

The quality of archaeological sites documenting is of great importance for cultural heritage preserving and investigating. The progress in developing new techniques and systems for data acquisition and processing creates an excellent basis for achieving a new quality of archaeological sites documenting and visualization. archaeological data has some specific features which have to be taken into account when acquiring, processing and managing. First of all, it is a needed to gather as full as possible information about findings providing no loss of information and no damage to artifacts. Remote sensing technologies are the most adequate and powerful means which satisfy this requirement. An approach to archaeological data acquiring and fusion based on remote sensing is proposed. It combines a set of photogrammetric techniques for obtaining geometrical and visual information at different scales and detailing and a pipeline for archaeological data documenting, structuring, fusion, and analysis. The proposed approach is applied for documenting of Bosporus archaeological expedition of Russian State Historical Museum.

A Feature-Reinforcement-Based Approach for Supporting Poly-Lingual Category Integration

NASA Astrophysics Data System (ADS)

Wei, Chih-Ping; Chen, Chao-Chi; Cheng, Tsang-Hsiang; Yang, Christopher C.

Document-category integration (or category integration for short) is fundamental to many e-commerce applications, including information integration along supply chains and information aggregation by intermediaries. Because of the trend of globalization, the requirement for category integration has been extended from monolingual to poly-lingual settings. Poly-lingual category integration (PLCI) aims to integrate two document catalogs, each of which consists of documents written in a mix of languages. Several category integration techniques have been proposed in the literature, but these techniques focus only on monolingual category integration rather than PLCI. In this study, we propose a feature-reinforcement-based PLCI (namely, FR-PLCI) technique that takes into account the master documents of all languages when integrating source documents (in the source catalog) written in a specific language into the master catalog. Using the monolingual category integration (MnCI) technique as a performance benchmark, our empirical evaluation results show that our proposed FR-PLCI technique achieves better integration accuracy than MnCI does in both English and Chinese category integration tasks.

An open annotation ontology for science on web 3.0

PubMed Central

2011-01-01

Background There is currently a gap between the rich and expressive collection of published biomedical ontologies, and the natural language expression of biomedical papers consumed on a daily basis by scientific researchers. The purpose of this paper is to provide an open, shareable structure for dynamic integration of biomedical domain ontologies with the scientific document, in the form of an Annotation Ontology (AO), thus closing this gap and enabling application of formal biomedical ontologies directly to the literature as it emerges. Methods Initial requirements for AO were elicited by analysis of integration needs between biomedical web communities, and of needs for representing and integrating results of biomedical text mining. Analysis of strengths and weaknesses of previous efforts in this area was also performed. A series of increasingly refined annotation tools were then developed along with a metadata model in OWL, and deployed for feedback and additional requirements the ontology to users at a major pharmaceutical company and a major academic center. Further requirements and critiques of the model were also elicited through discussions with many colleagues and incorporated into the work. Results This paper presents Annotation Ontology (AO), an open ontology in OWL-DL for annotating scientific documents on the web. AO supports both human and algorithmic content annotation. It enables “stand-off” or independent metadata anchored to specific positions in a web document by any one of several methods. In AO, the document may be annotated but is not required to be under update control of the annotator. AO contains a provenance model to support versioning, and a set model for specifying groups and containers of annotation. AO is freely available under open source license at http://purl.org/ao/, and extensive documentation including screencasts is available on AO’s Google Code page: http://code.google.com/p/annotation-ontology/ . Conclusions The Annotation Ontology meets critical requirements for an open, freely shareable model in OWL, of annotation metadata created against scientific documents on the Web. We believe AO can become a very useful common model for annotation metadata on Web documents, and will enable biomedical domain ontologies to be used quite widely to annotate the scientific literature. Potential collaborators and those with new relevant use cases are invited to contact the authors. PMID:21624159

An open annotation ontology for science on web 3.0.

PubMed

Ciccarese, Paolo; Ocana, Marco; Garcia Castro, Leyla Jael; Das, Sudeshna; Clark, Tim

2011-05-17

There is currently a gap between the rich and expressive collection of published biomedical ontologies, and the natural language expression of biomedical papers consumed on a daily basis by scientific researchers. The purpose of this paper is to provide an open, shareable structure for dynamic integration of biomedical domain ontologies with the scientific document, in the form of an Annotation Ontology (AO), thus closing this gap and enabling application of formal biomedical ontologies directly to the literature as it emerges. Initial requirements for AO were elicited by analysis of integration needs between biomedical web communities, and of needs for representing and integrating results of biomedical text mining. Analysis of strengths and weaknesses of previous efforts in this area was also performed. A series of increasingly refined annotation tools were then developed along with a metadata model in OWL, and deployed for feedback and additional requirements the ontology to users at a major pharmaceutical company and a major academic center. Further requirements and critiques of the model were also elicited through discussions with many colleagues and incorporated into the work. This paper presents Annotation Ontology (AO), an open ontology in OWL-DL for annotating scientific documents on the web. AO supports both human and algorithmic content annotation. It enables "stand-off" or independent metadata anchored to specific positions in a web document by any one of several methods. In AO, the document may be annotated but is not required to be under update control of the annotator. AO contains a provenance model to support versioning, and a set model for specifying groups and containers of annotation. AO is freely available under open source license at http://purl.org/ao/, and extensive documentation including screencasts is available on AO's Google Code page: http://code.google.com/p/annotation-ontology/ . The Annotation Ontology meets critical requirements for an open, freely shareable model in OWL, of annotation metadata created against scientific documents on the Web. We believe AO can become a very useful common model for annotation metadata on Web documents, and will enable biomedical domain ontologies to be used quite widely to annotate the scientific literature. Potential collaborators and those with new relevant use cases are invited to contact the authors.

RH-TRU Waste Inventory Characterization by AK and Proposed WIPP RH-TRU Waste Characterization Objectives

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

Most, W. A.; Kehrman, R.; Gist, C.

2002-02-26

The U.S. Department of Energy (DOE)-Carlsbad Field Office (CBFO) has developed draft documentation to present the proposed Waste Isolation Pilot Plant (WIPP) remote-handled (RH-) transuranic (TRU) waste characterization program to its regulators, the U.S. Environmental Protection Agency and the New Mexico Environment Department. Compliance with Title 40, Code of Federal Regulations, Parts 191 and 194; the WIPP Land Withdrawal Act (PL 102-579); and the WIPP Hazardous Waste Facility Permit, as well as the Certificates of Compliance for the 72-B and 10-160B Casks, requires that specific waste parameter limits be imposed on DOE sites disposing of TRU waste at WIPP. Themore » DOE-CBFO must control the sites' compliance with the limits by specifying allowable characterization methods. As with the established WIPP contact handled TRU waste characterization program, the DOE-CBFO has proposed a Remote-Handled TRU Waste Acceptance Criteria (RH-WAC) document consolidating the requirements from various regulatory drivers and proposed allowable characterization methods. These criteria are consistent with the recommendation of a recent National Academy Sciences/National Research Council to develop an RH-TRU waste characterization approach that removes current self imposed requirements that lack a legal or safety basis. As proposed in the draft RH-WAC and other preliminary documents, the DOE-CBFO RH-TRU waste characterization program proposes the use of acceptable knowledge (AK) as the primary method for obtaining required characterization information. The use of AK involves applying knowledge of the waste in light of the materials or processes used to generate the waste. Documentation, records, or processes providing information about various attributes of a waste stream, such as chemical, physical, and radiological properties, may be used as AK and may be applied to individual waste containers either independently or in conjunction with radiography, visual examination, assay, and other sampling and analytical data. RH-TRU waste cannot be shipped to WIPP on the basis of AK alone if documentation demonstrating that all of the prescribed limits in the RH-WAC are met is not available, discrepancies exist among AK source documents describing the same waste stream and the most conservative assumptions regarding those documents indicates that a limit will not be met, or all required data are not available for a given waste stream.« less

Advance care planning in Australia: what does the law say?

PubMed

Carter, Rachel Z; Detering, Karen M; Silvester, William; Sutton, Elizabeth

2016-09-01

Advance care planning (ACP) assists people to plan for their future health and personal care. ACP encourages a person to legally appoint a substitute decision maker (SDM) and to document any specific wishes regarding their future health care in an advance care directive (ACD). Formal documentation of wishes increases the chances that a person's wishes will be known and followed. However, one of the biggest impediments for doctors following the person's wishes is uncertainty surrounding the law, which is complicated and varies between the states and territories of Australia. SDM legislation varies regarding who can be appointed, how they are appointed, the powers that an SDM can be given and the decision-making principles that the SDM needs to follow. In circumstances where an SDM has not been appointed, the hierarchy for determining the default SDM for a person also varies between states. Although many states have legislated ACD forms allowing for documentation of a person's health care wishes, these forms allow for different things to be documented and have different requirements to be valid. The Australian population is mobile, with patients frequently moving between states. The status of ACP documentation created in a state other than the state in which a patient requires treatment also varies, with some states recognising interstate ACDs whereas others do not. This article outlines the legal status of ACDs, within Australian jurisdictions, including the legal validity of interstate ACDs, and argues that uniform laws and documents would assist with awareness and understanding of, and compliance with, ACDs.

Range Flight Safety Requirements

NASA Technical Reports Server (NTRS)

Loftin, Charles E.; Hudson, Sandra M.

2018-01-01

The purpose of this NASA Technical Standard is to provide the technical requirements for the NPR 8715.5, Range Flight Safety Program, in regards to protection of the public, the NASA workforce, and property as it pertains to risk analysis, Flight Safety Systems (FSS), and range flight operations. This standard is approved for use by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers, and may be cited in contract, program, and other Agency documents as a technical requirement. This standard may also apply to the Jet Propulsion Laboratory or to other contractors, grant recipients, or parties to agreements to the extent specified or referenced in their contracts, grants, or agreements, when these organizations conduct or participate in missions that involve range flight operations as defined by NPR 8715.5.1.2.2 In this standard, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.”1.3 TailoringTailoring of this standard for application to a specific program or project shall be formally documented as part of program or project requirements and approved by the responsible Technical Authority in accordance with NPR 8715.3, NASA General Safety Program Requirements.

Space shuttle configuration accounting functional design specification

NASA Technical Reports Server (NTRS)

1974-01-01

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

Analysis of commercial equipment and instrumentation for Spacelab payloads. Volume 3: Design analysis and trade studies

NASA Technical Reports Server (NTRS)

1974-01-01

A detailed analysis is presented of each selected equipment item, and suitability and cost analyses were documented by equipment item. Tradeoffs of alternative specification requirements are presented which include possible relaxation of vibration, material control, fungus and corrosion requirements for experiment equipment. An additional tradeoff was performed to determine whether it is cost effective to modify experiment equipment to be compatible with a 28-volt dc power source rather than the conventional 110-volt ac source. Programmatic analysis data are given which were used as the basis for the extension of results from the analyses of specific equipment items to the entire spacelab experiment program.

Slurry Coating System Statement of Work and Specification

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

Chan, S. M.

2017-02-06

The Slurry Coating System will be used to coat crystals with a polymer to support Lawrence Livermore National Security, LLC (LLNS) research and development at Lawrence Livermore National Laboratory (LLNL). The crystals will be suspended in water in a kettle. A polymer solution is added, temperature of the kettle is raised and aggregates of the crystals and polymer form. The slurry is heated under vacuum to drive off the solvents and slowly cooled while mixing to room temperature. The resulting aggregates are then filtered and dried. The performance characteristics and fielding constraints define a unique set of requirements for amore » new system. This document presents the specifications and requirements for the system.« less

Requirements, Verification, and Compliance (RVC) Database Tool

NASA Technical Reports Server (NTRS)

Rainwater, Neil E., II; McDuffee, Patrick B.; Thomas, L. Dale

2001-01-01

This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

Scientific and technical services directed toward the development of planetary quarantine measures for automated spacecraft

NASA Technical Reports Server (NTRS)

1974-01-01

The work is reported, which was performed in the specific tasks of the Planetary Quarantine research program for developing parameter specifications of unmanned scientific missions to the planets. The effort was directed principally toward the advancement of the quarantine technology, applicable to all future missions to planets of biological interest. The emphasis of the research was on coordinated evaluation, analysis, documentation, and presentation of PQ requirements for flight projects such as Viking and Pioneer.

Analyzing Document Retrievability in Patent Retrieval Settings

NASA Astrophysics Data System (ADS)

Bashir, Shariq; Rauber, Andreas

Most information retrieval settings, such as web search, are typically precision-oriented, i.e. they focus on retrieving a small number of highly relevant documents. However, in specific domains, such as patent retrieval or law, recall becomes more relevant than precision: in these cases the goal is to find all relevant documents, requiring algorithms to be tuned more towards recall at the cost of precision. This raises important questions with respect to retrievability and search engine bias: depending on how the similarity between a query and documents is measured, certain documents may be more or less retrievable in certain systems, up to some documents not being retrievable at all within common threshold settings. Biases may be oriented towards popularity of documents (increasing weight of references), towards length of documents, favour the use of rare or common words; rely on structural information such as metadata or headings, etc. Existing accessibility measurement techniques are limited as they measure retrievability with respect to all possible queries. In this paper, we improve accessibility measurement by considering sets of relevant and irrelevant queries for each document. This simulates how recall oriented users create their queries when searching for relevant information. We evaluate retrievability scores using a corpus of patents from US Patent and Trademark Office.

Evaluation of a Constrained Facet Analysis Efficiency Model for Identifying the Efficiency of Medical Treatment Facilities in the Army Medical Department

DTIC Science & Technology

1990-07-31

examples on their use is available with the PASS User Documentation Manual. 2 The data structure of PASS requires a three- lvel organizational...files, and missing control variables. A specific problem noted involved the absence of 8087 mathematical co-processor on the target IBM-XT 21 machine...System, required an operational understanding of the advanced mathematical technique used in the model. Problems with the original release of the PASS

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.

10 CFR 1707.203 - Filing requirements for demands or requests for documents or testimony.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 10 Energy 4 2011-01-01 2011-01-01 false Filing requirements for demands or requests for documents... Production of Documents § 1707.203 Filing requirements for demands or requests for documents or testimony. You must comply with the following requirements whenever you issue demands or requests to a DNFSB...

Requirements for migration of NSSD code systems from LTSS to NLTSS

NASA Technical Reports Server (NTRS)

Pratt, M.

1984-01-01

The purpose of this document is to address the requirements necessary for a successful conversion of the Nuclear Design (ND) application code systems to the NLTSS environment. The ND application code system community can be characterized as large-scale scientific computation carried out on supercomputers. NLTSS is a distributed operating system being developed at LLNL to replace the LTSS system currently in use. The implications of change are examined including a description of the computational environment and users in ND. The discussion then turns to requirements, first in a general way, followed by specific requirements, including a proposal for managing the transition.

34 CFR 300.311 - Specific documentation for the eligibility determination.

Code of Federal Regulations, 2010 CFR

2010-07-01

... Specific Learning Disabilities § 300.311 Specific documentation for the eligibility determination. (a) For a child suspected of having a specific learning disability, the documentation of the determination... has a specific learning disability; (2) The basis for making the determination, including an assurance...

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

Hitchhiker: Customer Accommodations and Requirements Specifications (CARS)

NASA Technical Reports Server (NTRS)

1992-01-01

In 1984, NASA Headquarters established projects at the Goddard Space Flight Center (GSFC) and the Marshall Space Flight Center (MSFC) to develop quick-reaction carrier systems for low-cost 'flight of opportunity' or secondary payloads on the Space Transportation System (STS). One of these projects is the Hitchhiker (HH) Program. GSFC has developed a family of carrier equipment known as the Shuttle Payload of Opportunity Carrier (SPOC) system for mounting small payloads such as HH to the side of the Orbiter payload bay. The side-mounted HHs are referred to as Hitchhiker-G (HH-G). MSFC developed a cross-bay 'bridge-type' carrier structure called the Hitchhiker-M (HH-M). In 1987, responsibility for the HH-M carrier was transferred to and is now managed by the HH Project Office at the GSFC. The HH-M carrier now uses the same interchangeable SPOC avionics unit and the same electrical interfaces and services developed for HH-G. National Aeronautics and Space Administration (NASA) has created this document to acquaint potential HH system customers with the facilities NASA provides and the requirements which customers must satisfy to use these facilities. This publication defines interface items required for integrating customer equipment with the HH carrier system. Those items such as mounting equipment and electrical inputs and outputs; configuration, environmental, command, telemetry, and operational constraints are described as well as weight, power, and communications. The purpose of this publication is to help the customer understand essential integration documentation requirements and to prepare a Customer Payload Requirements (CPR) document.

Automatic generation of Web mining environments

NASA Astrophysics Data System (ADS)

Cibelli, Maurizio; Costagliola, Gennaro

1999-02-01

The main problem related to the retrieval of information from the world wide web is the enormous number of unstructured documents and resources, i.e., the difficulty of locating and tracking appropriate sources. This paper presents a web mining environment (WME), which is capable of finding, extracting and structuring information related to a particular domain from web documents, using general purpose indices. The WME architecture includes a web engine filter (WEF), to sort and reduce the answer set returned by a web engine, a data source pre-processor (DSP), which processes html layout cues in order to collect and qualify page segments, and a heuristic-based information extraction system (HIES), to finally retrieve the required data. Furthermore, we present a web mining environment generator, WMEG, that allows naive users to generate a WME specific to a given domain by providing a set of specifications.

Advanced Life Support Systems

NASA Technical Reports Server (NTRS)

Barta, Daniel J.

2004-01-01

This presentation is planned to be a 10-15 minute "catalytic" focused presentation to be scheduled during one of the working sessions at the TIM. This presentation will focus on Advanced Life Support technologies key to future human Space Exploration as outlined in the Vision, and will include basic requirements, assessment of the state-of-the-art and gaps, and include specific technology metrics. The presentation will be technical in character, lean heavily on data in published ALS documents (such as the Baseline Values and Assumptions Document) but not provide specific technical details or build to information on any technology mentioned (thus the presentation will be benign from an export control and a new technology perspective). The topics presented will be focused on the following elements of Advanced Life Support: air revitalization, water recovery, waste management, thermal control, habitation systems, food systems and bioregenerative life support.

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.

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.

Proton Particle Test Fluence: What's the Right Number?

NASA Technical Reports Server (NTRS)

LaBel, Kenneth A.; Ladbury, Raymond

2015-01-01

While we have been utilizing standard fluence levels such as those listed in the JESD57 document, we have begun revisiting what an appropriate test fluence is when it comes to qualifying a device for single events. Instead of a fixed fluence level or until a specific number of events occurs, a different thought process is required.

Benefits and Challenges of Architecture Frameworks

DTIC Science & Technology

2011-06-01

systems and identify emerging and obsolete standards. • The NATO Capability View ( NCV ) serves the analysis and optimization of military ca- pabilities... NCVs show the dependencies between different capabilities and allow detecting gaps and overlaps of capabilities. NCVs deliver indirectly requirements...Email (possibly with vendor-specific extensions/modifications) • Proprietary, and possibly not well-documented, message formats • Web services

42 CFR 495.370 - Appeals process for a Medicaid provider receiving electronic health record incentive payments.

Code of Federal Regulations, 2011 CFR

2011-10-01

... STANDARDS FOR THE ELECTRONIC HEALTH RECORD TECHNOLOGY INCENTIVE PROGRAM Requirements Specific to the... in § 447.253(e) of this chapter for a provider or entity to appeal the following issues related to... entity) has an opportunity to challenge the State's determination under this Part by submitting documents...

Particle Test Fluence: What's the Right Number?

NASA Technical Reports Server (NTRS)

LaBel, Kenneth A.

2014-01-01

While we have been utilizing standard fluence levels such as those listed in the JESD57 document, we have begun revisiting what an appropriate test fluence is when it comes to qualifying a device for single events. Instead of a fixed fluence level or until a specific number of events occurs, a different thought process is required.

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.

48 CFR Appendix A to Chapter 2 - Armed Services Board of Contract Appeals

Code of Federal Regulations, 2010 CFR

2010-10-01

... officer has failed to issue a decision within a reasonable time, taking into account such factors as the... exhibits, post-hearing briefs, and documents which the Board has specifically designated be made a part of... order of appeals, Rule 12 requirements, and other pertinent factors. On request or motion by either...

Competency Based Training Program for Department Chairpersons and Other Resource Personnel.

ERIC Educational Resources Information Center

Bingen, Frances N.; And Others

The Competency Based Training Program is a three part, three phase package. It contains: (1) a research document; (2) a set of 18 programed units and; (3) cassettes to accompany two specific units. The program phases require that: (1) the participant and a training advisor jointly perform a needs assessment activity and select appropriate units…

Countermeasure Evaluation and Validation Project (CEVP) Database Requirement Documentation

NASA Technical Reports Server (NTRS)

Shin, Sung Y.

2003-01-01

The initial focus of the project by the JSC laboratories will be to develop, test and implement a standardized complement of integrated physiological test (Integrated Testing Regimen, ITR) that will examine both system and intersystem function, and will be used to validate and certify candidate countermeasures. The ITR will consist of medical requirements (MRs) and non-MR core ITR tests, and countermeasure-specific testing. Non-MR and countermeasure-specific test data will be archived in a database specific to the CEVP. Development of a CEVP Database will be critical to documenting the progress of candidate countermeasures. The goal of this work is a fully functional software system that will integrate computer-based data collection and storage with secure, efficient, and practical distribution of that data over the Internet. This system will provide the foundation of a new level of interagency and international cooperation for scientific experimentation and research, providing intramural, international, and extramural collaboration through management and distribution of the CEVP data. The research performed this summer includes the first phase of the project. The first phase of the project is a requirements analysis. This analysis will identify the expected behavior of the system under normal conditions and abnormal conditions; that could affect the system's ability to produce this behavior; and the internal features in the system needed to reduce the risk of unexpected or unwanted behaviors. The second phase of this project have also performed in this summer. The second phase of project is the design of data entry screen and data retrieval screen for a working model of the Ground Data Database. The final report provided the requirements for the CEVP system in a variety of ways, so that both the development team and JSC technical management have a thorough understanding of how the system is expected to behave.

48 CFR 11.101 - Order of precedence for requirements documents.

Code of Federal Regulations, 2011 CFR

2011-10-01

.... (2) Performance-oriented documents (e.g., a PWS or SOO). (See 2.101.) (3) Detailed design-oriented... requirements documents. 11.101 Section 11.101 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION ACQUISITION PLANNING DESCRIBING AGENCY NEEDS Selecting and Developing Requirements Documents 11...

Development of Methodologic Tools for Planning and Managing Library Services: II. Measuring a Library's Capability for Providing Documents *

PubMed Central

Orr, Richard H.; Pings, Vern M.; Pizer, Irwin H.; Olson, Edwin E.; Spencer, Carol C.

1968-01-01

A method of measuring a library's capability for providing the documents its users need has been developed. The library is tested with a representative sample of such documents to determine how long would be required for users to obtain these documents. Test results are expressed in terms of a Capability Index, which has a maximal value of 100 only if all the sample documents are found “on shelf.” Specific tests employing samples of 300 documents have been developed that are appropriate for academic and for “reservoir” biomedical libraries. Realistic field trials have demonstrated that these two tests are practical to administer and that test results are adequately reproducible. When strict comparability is not important, a library can test itself. In assessing a reservoir library, test results are supplemented by data on its typical processing time for interlibrary loan requests. Currently these tests are being used in a national survey. The general method is applicable to other types of libraries, provided appropriate test samples are established. If their limitations are clearly understood, these “Document Delivery Tests” can be valuable tools for planning and managing library services. PMID:5665969

SU-G-PinS Room/Hall E-00: HAZMAT Training for the Medical Physicist - Part II

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

NONE

Medical Physicists are frequently involved in shipping radioactive materials or supervising those who do. Current U.S. Department of Transportation Hazardous Material Regulations, 49 CFR Parts 171 - 185, require hazmat employees to have documented training specified in 49 CFR 172 Subpart H. A hazmat employee is defined as an individual who: (1) loads, unloads or handles hazardous material; (2) manufactures, tests, reconditions, repairs, modifies, marks or otherwise represents containers, drums or packagings as qualified for use in the transportation of hazardous materials; (3) prepares hazardous materials for transportation; (4) is responsible for safety of transporting hazardous materials; or (5) operatesmore » a vehicle used to transport hazardous materials. Recurrent training is required at least once every three years. (The IATA two year training interval is not applicable and is generally misunderstood.) FAA has escalated inspection and enforcement. Facilities who ship radiopharmaceuticals to other laboratories, return radiopharmaceuticals or radioactive sources to suppliers, or otherwise ship radioactive materials have been cited for failure to provide and document the required training. The interrelationship of transportation regulations, 49 CFR, IATA, ICAO and other transportation regulations, which are frequently misunderstood, will be explained. The course will cover typical shipments by air and highway which are encountered in a medical institution. Items such as fissile materials, highway route controlled quantities, rail shipments, vessel shipments and such will be omitted; although specific questions may be addressed. A major objective of the course is to present the process of shipping radioactive material in a sequential and logical fashion. How radioactive materials for transportation purposes are defined by activity concentrations for exempt materials and activity limits for exempt consignments will be explained. Radioactive material shipments of excepted packages and Type A packages will be emphasized. The program is designed to meet the function specific DOT training requirements for shippers of medical radioactive materials. General awareness training and security awareness training can be obtained from two free DOT training CDs. Safety training and security awareness training is generally satisfied by the training required under the institution’s radioactive material license. For shippers of radioactive Yellow III labeled packages an in-depth written security plan and training are no longer required as of April 8, 2010. In general almost all shippers of medical radioactive material are now not required to have an in-depth security plan. Contents of general awareness training, security awareness training and in-depth security plans will be briefly outlined. It is the hazmat employer’s responsibility to ensure that each hazmat employee is properly trained. No third party can fulfill that requirement. It is the hazmat employer’s responsibility to determine the degree to which this course meets the employer’s requirements, including contents of the course and the examination. Participants will gain sufficient knowledge to prepare hazmat training programs for others in their institutions. A handout will be posted which should be printed out and brought to the course for reference during the presentation. The handout will also satisfy part of the training documentation required by DOT. A feature handout section is a composite table which provides A1, A2, RQ, Exempt Concentration, and Exempt Consignment values in a single table in both Becquerel and Curie units. Course attendance will be certified through the AAPM CEU documentation system. Learning Objectives: Understand the regulatory requirements for shipping radioactive materials. Understand the regulatory requirements for training of hazmat employees. Comprehend how to classify, package, mark, label, document, placard, and transport radioactive materials.« less

SU-CD-PinS Room/Hall E-00: HAZMAT Training for the Medical Physicist - Part I

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

NONE

Medical Physicists are frequently involved in shipping radioactive materials or supervising those who do. Current U.S. Department of Transportation Hazardous Material Regulations, 49 CFR Parts 171 - 185, require hazmat employees to have documented training specified in 49 CFR 172 Subpart H. A hazmat employee is defined as an individual who: (1) loads, unloads or handles hazardous material; (2) manufactures, tests, reconditions, repairs, modifies, marks or otherwise represents containers, drums or packagings as qualified for use in the transportation of hazardous materials; (3) prepares hazardous materials for transportation; (4) is responsible for safety of transporting hazardous materials; or (5) operatesmore » a vehicle used to transport hazardous materials. Recurrent training is required at least once every three years. (The IATA two-year training interval is not applicable and is generally misunderstood.) FAA has escalated inspection and enforcement. Facilities who ship radiopharmaceuticals to other laboratories, return radiopharmaceuticals or radioactive sources to suppliers, or otherwise ship radioactive materials have been cited for failure to provide and document the required training. The interrelationship of transportation regulations, 49 CFR, IATA, ICAO and other transportation regulations, which are frequently misunderstood, will be explained. The course will cover typical shipments by air and highway which are encountered in a medical institution. Items such as fissile materials, highway route controlled quantities, rail shipments, vessel shipments and such will be omitted; although specific questions may be addressed. A major objective of the course is to present the process of shipping radioactive material in a sequential and logical fashion. How radioactive materials for transportation purposes are defined by activity concentrations for exempt materials and activity limits for exempt consignments will be explained. Radioactive material shipments of excepted packages and Type A packages will be emphasized. The program is designed to meet the function specific DOT training requirements for shippers of medical radioactive materials. General awareness training and security awareness training can be obtained from two free DOT training CDs. Safety training and security awareness training is generally satisfied by the training required under the institution’s radioactive material license. For shippers of radioactive Yellow III labeled packages an in-depth written security plan and training are no longer required as of April 8, 2010. In general almost all shippers of medical radioactive material are now not required to have an in-depth security plan. Contents of general awareness training, security awareness training and in-depth security plans will be briefly outlined. It is the hazmat employer’s responsibility to ensure that each hazmat employee is properly trained. No third party can fulfill that requirement. It is the hazmat employer’s responsibility to determine the degree to which this course meets the employer’s requirements, including contents of the course and the examination. Participants will gain sufficient knowledge to prepare hazmat training programs for others in their institutions. A handout will be posted which should be printed out and brought to the course for reference during the presentation. The handout will also satisfy part of the training documentation required by DOT. A feature handout section is a composite table which provides A1, A2, RQ, Exempt Concentration, and Exempt Consignment values in a single table in both Becquerel and Curie units. Course attendance will be certified through the AAPM CEU documentation system. Learning Objectives: Understand the regulatory requirements for shipping radioactive materials. Understand the regulatory requirements for training of hazmat employees. Comprehend how to classify, package, mark, label, document, placard, and transport radioactive materials.« less

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

Parker, R.

Medical Physicists are frequently involved in shipping radioactive materials or supervising those who do. Current U.S. Department of Transportation Hazardous Material Regulations, 49 CFR Parts 171 - 185, require hazmat employees to have documented training specified in 49 CFR 172 Subpart H. A hazmat employee is defined as an individual who: (1) loads, unloads or handles hazardous material; (2) manufactures, tests, reconditions, repairs, modifies, marks or otherwise represents containers, drums or packagings as qualified for use in the transportation of hazardous materials; (3) prepares hazardous materials for transportation; (4) is responsible for safety of transporting hazardous materials; or (5) operatesmore » a vehicle used to transport hazardous materials. Recurrent training is required at least once every three years. (The IATA two-year training interval is not applicable and is generally misunderstood.) FAA has escalated inspection and enforcement. Facilities who ship radiopharmaceuticals to other laboratories, return radiopharmaceuticals or radioactive sources to suppliers, or otherwise ship radioactive materials have been cited for failure to provide and document the required training. The interrelationship of transportation regulations, 49 CFR, IATA, ICAO and other transportation regulations, which are frequently misunderstood, will be explained. The course will cover typical shipments by air and highway which are encountered in a medical institution. Items such as fissile materials, highway route controlled quantities, rail shipments, vessel shipments and such will be omitted; although specific questions may be addressed. A major objective of the course is to present the process of shipping radioactive material in a sequential and logical fashion. How radioactive materials for transportation purposes are defined by activity concentrations for exempt materials and activity limits for exempt consignments will be explained. Radioactive material shipments of excepted packages and Type A packages will be emphasized. The program is designed to meet the function specific DOT training requirements for shippers of medical radioactive materials. General awareness training and security awareness training can be obtained from two free DOT training CDs. Safety training and security awareness training is generally satisfied by the training required under the institution’s radioactive material license. For shippers of radioactive Yellow III labeled packages an in-depth written security plan and training are no longer required as of April 8, 2010. In general almost all shippers of medical radioactive material are now not required to have an in-depth security plan. Contents of general awareness training, security awareness training and in-depth security plans will be briefly outlined. It is the hazmat employer’s responsibility to ensure that each hazmat employee is properly trained. No third party can fulfill that requirement. It is the hazmat employer’s responsibility to determine the degree to which this course meets the employer’s requirements, including contents of the course and the examination. Participants will gain sufficient knowledge to prepare hazmat training programs for others in their institutions. A handout will be posted which should be printed out and brought to the course for reference during the presentation. The handout will also satisfy part of the training documentation required by DOT. A feature handout section is a composite table which provides A1, A2, RQ, Exempt Concentration, and Exempt Consignment values in a single table in both Becquerel and Curie units. Course attendance will be certified through the AAPM CEU documentation system. Learning Objectives: Understand the regulatory requirements for shipping radioactive materials. Understand the regulatory requirements for training of hazmat employees. Comprehend how to classify, package, mark, label, document, placard, and transport radioactive materials.« less

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

Parker, R.

Medical Physicists are frequently involved in shipping radioactive materials or supervising those who do. Current U.S. Department of Transportation Hazardous Material Regulations, 49 CFR Parts 171 - 185, require hazmat employees to have documented training specified in 49 CFR 172 Subpart H. A hazmat employee is defined as an individual who: (1) loads, unloads or handles hazardous material; (2) manufactures, tests, reconditions, repairs, modifies, marks or otherwise represents containers, drums or packagings as qualified for use in the transportation of hazardous materials; (3) prepares hazardous materials for transportation; (4) is responsible for safety of transporting hazardous materials; or (5) operatesmore » a vehicle used to transport hazardous materials. Recurrent training is required at least once every three years. (The IATA two year training interval is not applicable and is generally misunderstood.) FAA has escalated inspection and enforcement. Facilities who ship radiopharmaceuticals to other laboratories, return radiopharmaceuticals or radioactive sources to suppliers, or otherwise ship radioactive materials have been cited for failure to provide and document the required training. The interrelationship of transportation regulations, 49 CFR, IATA, ICAO and other transportation regulations, which are frequently misunderstood, will be explained. The course will cover typical shipments by air and highway which are encountered in a medical institution. Items such as fissile materials, highway route controlled quantities, rail shipments, vessel shipments and such will be omitted; although specific questions may be addressed. A major objective of the course is to present the process of shipping radioactive material in a sequential and logical fashion. How radioactive materials for transportation purposes are defined by activity concentrations for exempt materials and activity limits for exempt consignments will be explained. Radioactive material shipments of excepted packages and Type A packages will be emphasized. The program is designed to meet the function specific DOT training requirements for shippers of medical radioactive materials. General awareness training and security awareness training can be obtained from two free DOT training CDs. Safety training and security awareness training is generally satisfied by the training required under the institution’s radioactive material license. For shippers of radioactive Yellow III labeled packages an in-depth written security plan and training are no longer required as of April 8, 2010. In general almost all shippers of medical radioactive material are now not required to have an in-depth security plan. Contents of general awareness training, security awareness training and in-depth security plans will be briefly outlined. It is the hazmat employer’s responsibility to ensure that each hazmat employee is properly trained. No third party can fulfill that requirement. It is the hazmat employer’s responsibility to determine the degree to which this course meets the employer’s requirements, including contents of the course and the examination. Participants will gain sufficient knowledge to prepare hazmat training programs for others in their institutions. A handout will be posted which should be printed out and brought to the course for reference during the presentation. The handout will also satisfy part of the training documentation required by DOT. A feature handout section is a composite table which provides A1, A2, RQ, Exempt Concentration, and Exempt Consignment values in a single table in both Becquerel and Curie units. Course attendance will be certified through the AAPM CEU documentation system. Learning Objectives: Understand the regulatory requirements for shipping radioactive materials. Understand the regulatory requirements for training of hazmat employees. Comprehend how to classify, package, mark, label, document, placard, and transport radioactive materials.« less

Overview of Energy Systems' safety analysis report programs

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

Not Available

1992-03-01

The primary purpose of an Safety Analysis Report (SAR) is to provide a basis for judging the adequacy of a facility's safety. The SAR documents the safety analyses that systematically identify the hazards posed by the facility, analyze the consequences and risk of potential accidents, and describe hazard control measures that protect the health and safety of the public and employees. In addition, some SARs document, as Technical Safety Requirements (TSRs, which include Technical Specifications and Operational Safety Requirements), technical and administrative requirements that ensure the facility is operated within prescribed safety limits. SARs also provide conveniently summarized information thatmore » may be used to support procedure development, training, inspections, and other activities necessary to facility operation. This Overview of Energy Systems Safety Analysis Report Programs'' Provides an introduction to the programs and processes used in the development and maintenance of the SARs. It also summarizes some of the uses of the SARs within Energy Systems and DOE.« less

Overview of Energy Systems` safety analysis report programs. Safety Analysis Report Update Program

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

Not Available

1992-03-01

The primary purpose of an Safety Analysis Report (SAR) is to provide a basis for judging the adequacy of a facility`s safety. The SAR documents the safety analyses that systematically identify the hazards posed by the facility, analyze the consequences and risk of potential accidents, and describe hazard control measures that protect the health and safety of the public and employees. In addition, some SARs document, as Technical Safety Requirements (TSRs, which include Technical Specifications and Operational Safety Requirements), technical and administrative requirements that ensure the facility is operated within prescribed safety limits. SARs also provide conveniently summarized information thatmore » may be used to support procedure development, training, inspections, and other activities necessary to facility operation. This ``Overview of Energy Systems Safety Analysis Report Programs`` Provides an introduction to the programs and processes used in the development and maintenance of the SARs. It also summarizes some of the uses of the SARs within Energy Systems and DOE.« less

Fabrication Control Plan for ORNL RH-LOCA ATF Test Specimens to be Irradiated in the ATR

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

Field, Kevin G.; Howard, Richard; Teague, Michael

2014-06-01

The purpose of this fabrication plan is (1) to summarize the design of a set of rodlets that will be fabricated and then irradiated in the Advanced Test Reactor (ATR) and (2) provide requirements for fabrication and acceptance criteria for inspections of the Light Water Reactor (LWR) – Accident Tolerant Fuels (ATF) rodlet components. The functional and operational (F&OR) requirements for the ATF program are identified in the ATF Test Plan. The scope of this document only covers fabrication and inspections of rodlet components detailed in drawings 604496 and 604497. It does not cover the assembly of these items tomore » form a completed test irradiation assembly or the inspection of the final assembly, which will be included in a separate INL final test assembly specification/inspection document. The controls support the requirements that the test irradiations must be performed safely and that subsequent examinations must provide valid results.« less

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

Schmoyer, RLS

The United States Department of Energy (DOE) currently manages the UF{sub 6} Cylinder Project. The project was formed to maintain and safely manage the depleted uranium hexafluoride (UF{sub 6}) stored in approximately 50,000 carbon steel cylinders. The cylinders are located at three DOE sites: the ETTP site (K-25) at Oak Ridge, Tennessee; the Paducah Gaseous Diffusion Plant (PGDP) in Paducah, Kentucky, and the Portsmouth Gaseous Diffusion Plant (PORTS) in Portsmouth, Ohio. The System Requirements Document (SRD) (LMES 1997a) delineates the requirements of the project. The appropriate actions needed to fulfill these requirements are then specified within the System Engineering Managementmore » Plan (SEMP) (LMES 1997b). This report documents activities that in whole or in part satisfy specific requirements and actions stated in the UF{sub 6} Cylinder Project SRD and SEMP with respect to forecasting cylinder conditions. The results presented here supercede those presented previously (Lyon 1995, 1996, 1997, 1998, 2000). Many of the wall thickness projections made in this report are conservative, because they are based on the assumption that corrosion trends will continue, despite activities such as improved monitoring, relocations to better storage, and painting.« less

NASA Battery Working Group - 2007-2008: Battery Task Summary Report

NASA Technical Reports Server (NTRS)

Manzo, Michelle

2008-01-01

This presentation provides a summary of the 2007-2008 NASA Battery Working Group efforts completed in support of the NASA Engineering Safety Center (NESC). The effort covered a series of pro-active tasks that address the following: Binding Procurements -- guidelines related to requirements for the battery system that should be considered at the time of contract award Wet Life of Ni-H2 Batteries -- issues/strategies for effective storage and impact of long-term storage on performance and life Generic Guidelines for Lithium-ion Safety, Handling and Qualification -- Standardized approaches developed and risk assessments (1) Lithium-ion Performance Assessment -- survey of manufacturers and capabilities to meet mission needs. Guidelines document generated (2) Conditions Required for using Pouch Cells in Aerospace Missions -- focus on corrosion, thermal excursions and long-term performance issues. Document defining requirements to maintain performance and life (3) High Voltage Risk Assessment -- focus on safety and abuse tolerance of battery module assemblies. Recommendations of features required for safe implementation (4) Procedure for Determination of Safe Charge Rates -- evaluation of various cell chemistries and recommendation of safe operating regimes for specific cell designs

The implementation and use of Ada on distributed systems with high reliability requirements

NASA Technical Reports Server (NTRS)

Knight, J. C.

1987-01-01

A preliminary analysis of the Ada implementation of the Advanced Transport Operating System (ATOPS), an experimental computer control system developed at NASA Langley for a modified Boeing 737 aircraft, is presented. The criteria that was determined for the evaluation of this approach is described. A preliminary version of the requirements for the ATOPS is contained. This requirements specification is not a formal document, but rather a description of certain aspects of the ATOPS system at a level of detail that best suits the needs of the research. The survey of backward error recovery techniques is also presented.

[Local approval procedures act as a brake on RCTs].

PubMed

van der Stok, E P; Huiskens, J; Hemmes, B; Grünhagen, D J; van Gulik, T M; Verhoef, C; Punt, C J A

2016-01-01

Large multicentre randomised controlled trials (RCTs) in the Netherlands are increasingly being impeded by major differences between local approval procedures. However, no national agenda exists as yet to improve this situation. The existence of major local differences in processing time and documentation required has been reported previously but little is known about the costs incurred and whether or not specific certifications and research contracts are mandatory. The current study evaluated these aspects of local procedures for obtaining approval of two oncological multicentre RCTs. Retrospective, descriptive. All local procedures for obtaining approval of two randomised clinical trials were evaluated: the CAIRO5 and CHARISMA trials initiated by the Dutch Colorectal Cancer Group (DCCG). We objectified time between approval by the Medical Ethics Review Committee (METC) and final approval by the Board of Directors (RvB), the type and number of documents needed, and costs charged. The median time interval between the approval by the Medical Ethics Review Committee and the approval by the Board of Directors was 90 days (range 4-312). The number of documents required per centre ranged from 6-20. The costs charged ranged from € 0-€ 1750, and amounted to € 8575 for all procedures combined. No costs were charged by the majority of the centres. The approval procedures for multicentre clinical trials in the Netherlands demonstrate major differences. Processing times, documentation required and costs are unpredictable; greater uniformity is highly desirable in this context.

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.

Preoperational Subsurface Conditions at the Idaho Nuclear Technology and Engineering Center Service Waste Disposal Facility

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

Ansley, Shannon Leigh

2002-02-01

The Idaho Nuclear Technology and Engineering Center (INTEC) Service Wastewater Discharge Facility replaces the existing percolation ponds as a disposal facility for the INTEC Service Waste Stream. A preferred alternative for helping decrease water content in the subsurface near INTEC, closure of the existing ponds is required by the INTEC Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA) Record of Decision (ROD) for Waste Area Group 3 Operable Unit 3-13 (DOE-ID 1999a). By August 2002, the replacement facility was constructed approximately 2 miles southwest of INTEC, near the Big Lost River channel. Because groundwater beneath the Idaho National Engineering andmore » Environmental Laboratory (INEEL) is protected under Federal and State of Idaho regulations from degradation due to INEEL activities, preoperational data required by U.S. Department of Energy (DOE) Order 5400.1 were collected. These data include preexisting physical, chemical, and biological conditions that could be affected by the discharge; background levels of radioactive and chemical components; pertinent environmental and ecological parameters; and potential pathways for human exposure or environmental impact. This document presents specific data collected in support of DOE Order 5400.1, including: four quarters of groundwater sampling and analysis of chemical and radiological parameters; general facility description; site specific geology, stratigraphy, soils, and hydrology; perched water discussions; and general regulatory requirements. However, in order to avoid duplication of previous information, the reader is directed to other referenced publications for more detailed information. Documents that are not readily available are compiled in this publication as appendices. These documents include well and borehole completion reports, a perched water evaluation letter report, the draft INEEL Wellhead Protection Program Plan, and the Environmental Checklist.« less

45 CFR 164.316 - Policies and procedures and documentation requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... when it last was in effect, whichever is later. (ii) Availability (Required). Make documentation.... (iii) Updates (Required). Review documentation periodically, and update as needed, in response to...

20 CFR 655.1319 - Document retention requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... 20 Employees' Benefits 3 2010-04-01 2010-04-01 false Document retention requirements. 655.1319... Employment in the United States (H-2A Workers) § 655.1319 Document retention requirements. (a) Entities... retention. Records and documents must be retained for a period of 3 years from the date of certification of...

46 CFR 67.105 - Requirement for determination.

Code of Federal Regulations, 2013 CFR

2013-10-01

... DOCUMENTATION OF VESSELS Tonnage and Dimension Requirements for Vessel Documentation § 67.105 Requirement for determination. The gross and net tonnage and dimensions of a vessel must be determined: (a) For initial documentation; (b) Whenever there is a change in the gross or net tonnage or dimensions of a documented vessel...

46 CFR 67.105 - Requirement for determination.

Code of Federal Regulations, 2014 CFR

2014-10-01

... DOCUMENTATION OF VESSELS Tonnage and Dimension Requirements for Vessel Documentation § 67.105 Requirement for determination. The gross and net tonnage and dimensions of a vessel must be determined: (a) For initial documentation; (b) Whenever there is a change in the gross or net tonnage or dimensions of a documented vessel...

46 CFR 67.105 - Requirement for determination.

Code of Federal Regulations, 2012 CFR

2012-10-01

... DOCUMENTATION OF VESSELS Tonnage and Dimension Requirements for Vessel Documentation § 67.105 Requirement for determination. The gross and net tonnage and dimensions of a vessel must be determined: (a) For initial documentation; (b) Whenever there is a change in the gross or net tonnage or dimensions of a documented vessel...

46 CFR 67.105 - Requirement for determination.

Code of Federal Regulations, 2010 CFR

2010-10-01

... DOCUMENTATION OF VESSELS Tonnage and Dimension Requirements for Vessel Documentation § 67.105 Requirement for determination. The gross and net tonnage and dimensions of a vessel must be determined: (a) For initial documentation; (b) Whenever there is a change in the gross or net tonnage or dimensions of a documented vessel...

46 CFR 67.105 - Requirement for determination.

Code of Federal Regulations, 2011 CFR

2011-10-01

... DOCUMENTATION OF VESSELS Tonnage and Dimension Requirements for Vessel Documentation § 67.105 Requirement for determination. The gross and net tonnage and dimensions of a vessel must be determined: (a) For initial documentation; (b) Whenever there is a change in the gross or net tonnage or dimensions of a documented vessel...

Model-Drive Architecture for Agent-Based Systems

NASA Technical Reports Server (NTRS)

Gradanin, Denis; Singh, H. Lally; Bohner, Shawn A.; Hinchey, Michael G.

2004-01-01

The Model Driven Architecture (MDA) approach uses a platform-independent model to define system functionality, or requirements, using some specification language. The requirements are then translated to a platform-specific model for implementation. An agent architecture based on the human cognitive model of planning, the Cognitive Agent Architecture (Cougaar) is selected for the implementation platform. The resulting Cougaar MDA prescribes certain kinds of models to be used, how those models may be prepared and the relationships of the different kinds of models. Using the existing Cougaar architecture, the level of application composition is elevated from individual components to domain level model specifications in order to generate software artifacts. The software artifacts generation is based on a metamodel. Each component maps to a UML structured component which is then converted into multiple artifacts: Cougaar/Java code, documentation, and test cases.

Comparison of Commercial Electromagnetic Interface Test Techniques to NASA Electromagnetic Interference Test Techniques

NASA Astrophysics Data System (ADS)

Smith, V.

2000-11-01

This report documents the development of analytical techniques required for interpreting and comparing space systems electromagnetic interference test data with commercial electromagnetic interference test data using NASA Specification SSP 30237A "Space Systems Electromagnetic Emission and Susceptibility Requirements for Electromagnetic Compatibility." The PSpice computer simulation results and the laboratory measurements for the test setups under study compare well. The study results, however, indicate that the transfer function required to translate test results of one setup to another is highly dependent on cables and their actual layout in the test setup. Since cables are equipment specific and are not specified in the test standards, developing a transfer function that would cover all cable types (random, twisted, or coaxial), sizes (gauge number and length), and layouts (distance from the ground plane) is not practical.

Comparison of Commercial Electromagnetic Interface Test Techniques to NASA Electromagnetic Interference Test Techniques

NASA Technical Reports Server (NTRS)

Smith, V.; Minor, J. L. (Technical Monitor)

2000-01-01

This report documents the development of analytical techniques required for interpreting and comparing space systems electromagnetic interference test data with commercial electromagnetic interference test data using NASA Specification SSP 30237A "Space Systems Electromagnetic Emission and Susceptibility Requirements for Electromagnetic Compatibility." The PSpice computer simulation results and the laboratory measurements for the test setups under study compare well. The study results, however, indicate that the transfer function required to translate test results of one setup to another is highly dependent on cables and their actual layout in the test setup. Since cables are equipment specific and are not specified in the test standards, developing a transfer function that would cover all cable types (random, twisted, or coaxial), sizes (gauge number and length), and layouts (distance from the ground plane) is not practical.

Mental Health Nursing, Mechanical Restraint Measures and Patients’ Legal Rights

PubMed Central

Birkeland, Soren; Gildberg, Frederik A.

2016-01-01

Coercive mechanical restraint (MR) in psychiatry constitutes the perhaps most extensive exception from the common health law requirement for involving patients in health care decisions and achieving their informed consent prior to treatment. Coercive measures and particularly MR seriously collide with patient autonomy principles, pose a particular challenge to psychiatric patients’ legal rights, and put intensified demands on health professional performance. Legal rights principles require rationale for coercive measure use be thoroughly considered and rigorously documented. This article presents an in-principle Danish Psychiatric Complaint Board decision concerning MR use initiated by untrained staff. The case illustrates that, judicially, weight must be put on the patient perspective on course of happenings and especially when health professional documentation is scant, patients’ rights call for taking notice of patient evaluations. Consequently, if it comes out that psychiatric staff failed to pay appropriate consideration for the patient’s mental state, perspective, and expressions, patient response deviations are to be judicially interpreted in this light potentially rendering MR use illegitimated. While specification of law criteria might possibly improve law use and promote patients’ rights, education of psychiatry professionals must address the need for, as far as possible, paying due regard to meeting patient perspectives and participation principles as well as formal law and documentation requirements. PMID:27123152

Development of a web-based, specialty specific portfolio.

PubMed

Clay, A S; Petrusa, E; Harker, M; Andolsek, K

2007-05-01

This article illustrates the creation of a specialty specific portfolio that can be used by several different residency programs to document resident competence during a given rotation. Three different disciplines (anesthesiology, surgery and medicine) worked together to create a critical care medicine portfolio. We began by reviewing the curriculum requirements for critical care medicine and organized these requirements into the six ACGME core competencies. We then developed learner led exercises in each core competency that were specific to critical care. Each exercise includes assessment of resident knowledge and application, an evaluation of the exercise, a learner self-assessment of skill, and a review of performance by a faculty member. Portfolio entries are highlighted in a multi-disciplinary weekly conference and posted on a critical care web site at our University. Creation of specialty specific portfolio reduces redundancy between disciplines, allows for increased time to be spent on the development of exercises specific to rotation objectives, and aids program directors in the collection of portfolio entries for each resident over the course of a residency.

Systems Maintenance Automated Repair Tasks (SMART)

NASA Technical Reports Server (NTRS)

Schuh, Joseph; Mitchell, Brent; Locklear, Louis; Belson, Martin A.; Al-Shihabi, Mary Jo Y.; King, Nadean; Norena, Elkin; Hardin, Derek

2010-01-01

SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.

Mission-oriented requirements for updating MIL-H-8501: Calspan proposed structure and rationale

NASA Technical Reports Server (NTRS)

Chalk, C. R.; Radford, R. C.

1985-01-01

This report documents the effort by Arvin/Calspan Corporation to formulate a revision of MIL-H-8501A in terms of Mission-Oriented Flying Qualities Requirements for Military Rotorcraft. Emphasis is placed on development of a specification structure which will permit addressing Operational Missions and Flight Phases, Flight Regions, Classification of Required Operational Capability, Categorization of Flight Phases, and Levels of Flying Qualities. A number of definitions is established to permit addressing the rotorcraft state, flight envelopes, environments, and the conditions under which degraded flying qualities are permitted. Tentative requirements are drafted for Required Operational Capability Class 1. Also included is a Background Information and Users Guide for the draft specification structure proposed for the MIL-H-8501A revision. The report also contains a discussion of critical data gaps and attempts to prioritize these data gaps and to suggest experiments that should be performed to generate data needed to support formulation of quantitative design criteria for the additional Operational Capability Classes 2, 3, and 4.

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.

Dynamic visualization techniques for high consequence software

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

Pollock, G.M.

1998-02-01

This report documents a prototype tool developed to investigate the use of visualization and virtual reality technologies for improving software surety confidence. The tool is utilized within the execution phase of the software life cycle. It provides a capability to monitor an executing program against prespecified requirements constraints provided in a program written in the requirements specification language SAGE. The resulting Software Attribute Visual Analysis Tool (SAVAnT) also provides a technique to assess the completeness of a software specification. The prototype tool is described along with the requirements constraint language after a brief literature review is presented. Examples of howmore » the tool can be used are also presented. In conclusion, the most significant advantage of this tool is to provide a first step in evaluating specification completeness, and to provide a more productive method for program comprehension and debugging. The expected payoff is increased software surety confidence, increased program comprehension, and reduced development and debugging time.« less

Science-based requirements and operations development for the Maunakea Spectroscopic Explorer

NASA Astrophysics Data System (ADS)

McConnachie, Alan W.; Flagey, Nicolas; Murowinski, Rick; Szeto, Kei; Salmon, Derrick; Withington, Kanoa; Mignot, Shan

2016-07-01

MSE is a wide field telescope (1.5 square degree field of view) with an aperture of 11.25m. It is dedicated to multi-object spectroscopy at several different spectral resolutions in the range R 2500 - 40000 over a broad wavelength range (0:36 - 1:8μm). MSE enables transformational science in areas as diverse as exoplanetary host characterization; stellar monitoring campaigns; tomographic mapping of the interstellar and intergalactic media; the in-situ chemical tagging of the distant Galaxy; connecting galaxies to the large scale structure of the Universe; measuring the mass functions of cold dark matter sub-halos in galaxy and cluster-scale hosts; reverberation mapping of supermassive black holes in quasars. Here, we summarize the Observatory and describe the development of the top level science requirements and operational concepts. Specifically, we describe the definition of the Science Requirements to be the set of capabilities that allow certain high impact science programs to be conducted. We cross reference these science cases to the science requirements to illustrate the traceability of this approach. We further discuss the operations model for MSE and describe the development of the Operations Concept Document, one of the foundational documents for the project. We also discuss the next stage in the science based development of MSE, specifically the development of the initial Legacy Survey that will occupy a majority of time on the telescope over the first few years of operation.

Reporting of feasibility factors in publications on integrated treatment programs for women with substance abuse issues and their children: a systematic review and analysis.

PubMed

Henderson, Joanna; Milligan, Karen; Niccols, Alison; Thabane, Lehana; Sword, Wendy; Smith, Ainsley; Rosenkranz, Susan

2012-12-07

Implementation of evidence-based practices in real-world settings is a complex process impacted by many factors, including intervention, dissemination, service provider, and organizational characteristics. Efforts to improve knowledge translation have resulted in greater attention to these factors. Researcher attention to the applicability of findings to applied settings also has increased. Much less attention, however, has been paid to intervention feasibility, an issue important to applied settings. In a systematic review of 121 documents regarding integrated treatment programs for women with substance abuse issues and their children, we examined the presence of feasibility-related information. Specifically, we analysed study descriptions for information regarding feasibility factors in six domains (intervention, practitioner, client, service delivery, organizational, and service system). On average, fewer than half of the 25 feasibility details assessed were included in the documents. Most documents included some information describing the participating clients, the services offered as part of the intervention, the location of services, and the expected length of stay or number of sessions. Only approximately half of the documents included specific information about the treatment model. Few documents indicated whether the intervention was manualized or whether the intervention was preceded by a standardized screening or assessment process. Very few provided information about the core intervention features versus the features open to local adaptation, or the staff experience or training required to deliver the intervention. As has been found in reviews of intervention studies in other fields, our findings revealed that most documents provide some client and intervention information, but few documents provided sufficient information to fully evaluate feasibility. We consider possible explanations for the paucity of feasibility information and provide suggestions for better reporting to promote diffusion of evidence-based practices.

Transitioning from conceptual design to construction performance specification

NASA Astrophysics Data System (ADS)

Jeffers, Paul; Warner, Mark; Craig, Simon; Hubbard, Robert; Marshall, Heather

2012-09-01

On successful completion of a conceptual design review by a funding agency or customer, there is a transition phase before construction contracts can be placed. The nature of this transition phase depends on the Project's approach to construction and the particular subsystem being considered. There are generically two approaches; project retention of design authority and issuance of build to print contracts, or issuance of subsystem performance specifications with controlled interfaces. This paper relates to the latter where a proof of concept (conceptual or reference design) is translated into performance based sub-system specifications for competitive tender. This translation is not a straightforward process and there are a number of different issues to consider in the process. This paper deals with primarily the Telescope mount and Enclosure subsystems. The main subjects considered in this paper are: • Typical status of design at Conceptual Design Review compared with the desired status of Specifications and Interface Control Documents at Request for Quotation. • Options for capture and tracking of system requirements flow down from science / operating requirements and sub-system requirements, and functional requirements derived from reference design. • Requirements that may come specifically from the contracting approach. • Methods for effective use of reference design work without compromising a performance based specification. • Management of project team's expectation relating to design. • Effects on cost estimates from reference design to actual. This paper is based on experience and lessons learned through this process on both the VISTA and the ATST projects.

75 FR 29588 - Notice of Availability of the Models for Plant-Specific Adoption of Technical Specifications Task...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-05-26

... Documents Access and Management System (ADAMS) under Accession Number ML090510686. The proposed changes... Documents Access and Management System (ADAMS): Publicly available documents created or received at the NRC... expedited approval of plant-specific adoption of TSTF- 501, Revision 1. Documents: You can access publicly...

75 FR 26294 - Notice of Availability of the Models for Plant-Specific Adoption of Technical Specifications Task...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-05-11

... an errata sheet are available in the Agencywide Documents Access and Management System (ADAMS) under... Agencywide Documents Access and Management System (ADAMS): Publicly available documents created or received... facilitate expedited approval of plant-specific adoption of TSTF-493, Revision 4. Documents: You can access...

Secure HL7 transactions using Internet mail (Internet draft).

PubMed

Schadow, Gunther; Tucker, Mark; Rishel, Wes

2002-01-01

The document describes the applicability of the Internet standardisation efforts on secure electronic data interchange (EDI) transactions for Health Level-7 (HL7), an EDI standard for Healthcare used world-wide. The document heavily relies on the work in progress by the IETF EDIINT working group. It is in most parts a restatement of the EDIINTs requirements document and application statement 1 (AS#1) tailored to the needs of the HL7 audience. The authors tried to make the document as self consistent as possible. The goal is to give to the reader who is not a security or Internet standards expert enough foundational and detail information to enable him to build communication software that complies to the Internet standards. Even though the authors rely on and promote the respective Internet standards and drafts, they did not withstand from commenting on and criticising the work where they see upcoming problems in use with HL7 or other EDI protocols that have not been in the initial focus of the EDIINT working group. The authors make suggestions to add parameters to the specification of the MIME type for EDI messages in RFC 1767 in order to enhance functionality. The authors give use cases for a larger subset of disposition types and modifiers of message disposition notifications. One key issue where the document goes beyond the current EDIINT drafts is the concept of non-repudiation of commitment to an EDI transaction. Secure EDI transactions should be regarded as "distributed contracts," i.e. not only the sending and receiving of single messages should be non-refutable but also the connection between messages interchanges. In anticipation of this requirement HL7 usually requires a response message to be sent to acknowledge every transaction. The authors therefore have the requirement to securely couple an EDI response message to its request message. Given the current shape of RFC 1767 this is generally possible only if a response message is coupled with an MDN receipt and the combination of both signed by the responder. The document describes a protocol to bundle MDN and response that uses the MIME multi-part/related content type in RFC 2112.

International laser-safety regulations: a status update

NASA Astrophysics Data System (ADS)

Weiner, Robert M.

1990-07-01

There is an increase in international laser safety requirements as part of the emphasis on world-wide standardization of products and regulations. In particular the documents which will evolve from the 1992 consolidation efforts of the European Community (EC) will impact both laser manufacturers and users. This paper provides a discussion of the current status of the various laser radiation standards. NORTH AMERICAN REQUIREMENTS United States Requirements on manufacturers from the Food and Drug Administration (FDA) have been in effect since 1975. The Center for Devices and Radiological Health (CDRH) within that agency ensures that these mandatory requirements [1] are satisfied. The CDRH regulations include the division of products into classes depending on their potential for hazard criteria for power measurement and requirements for product features labels and manuals and records and reports. Manufacturers must test products and certify that they comply with the CDRH requirements. User requirements are found in a standard published by the American National Standards Institute (ANSI) and in requirements from several individual states. Specific ANSI standards have also been published for fiber communications systems [34] and for lasers in medical applications [35]. Please note that the Appendix includes additional information on the standards discussed in this paper including sources for obtaining the documents. Canada In the past Canada has had requirements for two specified product categories (bar code scanners and educational lasers) [26 These will be replaced

Critical Review of NOAA's Observation Requirements Process

NASA Astrophysics Data System (ADS)

LaJoie, M.; Yapur, M.; Vo, T.; Templeton, A.; Bludis, D.

2017-12-01

NOAA's Observing Systems Council (NOSC) maintains a comprehensive database of user observation requirements. The requirements collection process engages NOAA subject matter experts to document and effectively communicate the specific environmental observation measurements (parameters and attributes) needed to produce operational products and pursue research objectives. User observation requirements documented using a structured and standardized manner and framework enables NOAA to assess its needs across organizational lines in an impartial, objective, and transparent manner. This structure provides the foundation for: selecting, designing, developing, acquiring observing technologies, systems and architectures; budget and contract formulation and decision-making; and assessing in a repeatable fashion the productivity, efficiency and optimization of NOAA's observing system enterprise. User observation requirements are captured independently from observing technologies. Therefore, they can be addressed by a variety of current or expected observing capabilities and allow flexibility to be remapped to new and evolving technologies. NOAA's current inventory of user observation requirements were collected over a ten-year period, and there have been many changes in policies, mission priorities, and funding levels during this time. In light of these changes, the NOSC initiated a critical, in-depth review to examine all aspects of user observation requirements and associated processes during 2017. This presentation provides background on the NOAA requirements process, major milestones and outcomes of the critical review, and plans for evolving and connecting observing requirements processes in the next year.

25 CFR 559.7 - May a tribe submit documents required by this part electronically?

Code of Federal Regulations, 2013 CFR

2013-04-01

... 25 Indians 2 2013-04-01 2013-04-01 false May a tribe submit documents required by this part... NOTIFICATIONS AND SUBMISSIONS § 559.7 May a tribe submit documents required by this part electronically? Yes. Tribes wishing to submit documents electronically should contact the Commission for guidance on...

25 CFR 559.7 - May a tribe submit documents required by this part electronically?

Code of Federal Regulations, 2014 CFR

2014-04-01

... 25 Indians 2 2014-04-01 2014-04-01 false May a tribe submit documents required by this part... NOTIFICATIONS AND SUBMISSIONS § 559.7 May a tribe submit documents required by this part electronically? Yes. Tribes wishing to submit documents electronically should contact the Commission for guidance on...

42 CFR 102.53 - Documentation a survivor must submit to be deemed eligible by the Secretary.

Code of Federal Regulations, 2012 CFR

2012-10-01

... AND HUMAN SERVICES VACCINES SMALLPOX COMPENSATION PROGRAM Required Documentation To Be Deemed Eligible... documentation required in: (1) Section 102.51(a)(2)-(4) (documentation requirements for smallpox vaccine recipients), in the case of a deceased smallpox vaccine recipient. The survivor requester may submit a...

42 CFR 102.53 - Documentation a survivor must submit to be deemed eligible by the Secretary.

Code of Federal Regulations, 2014 CFR

2014-10-01

... AND HUMAN SERVICES VACCINES SMALLPOX COMPENSATION PROGRAM Required Documentation To Be Deemed Eligible... documentation required in: (1) Section 102.51(a)(2)-(4) (documentation requirements for smallpox vaccine recipients), in the case of a deceased smallpox vaccine recipient. The survivor requester may submit a...

42 CFR 102.53 - Documentation a survivor must submit to be deemed eligible by the Secretary.

Code of Federal Regulations, 2013 CFR

2013-10-01

... AND HUMAN SERVICES VACCINES SMALLPOX COMPENSATION PROGRAM Required Documentation To Be Deemed Eligible... documentation required in: (1) Section 102.51(a)(2)-(4) (documentation requirements for smallpox vaccine recipients), in the case of a deceased smallpox vaccine recipient. The survivor requester may submit a...

42 CFR 102.53 - Documentation a survivor must submit to be deemed eligible by the Secretary.

Code of Federal Regulations, 2011 CFR

2011-10-01

... AND HUMAN SERVICES VACCINES SMALLPOX COMPENSATION PROGRAM Required Documentation To Be Deemed Eligible... documentation required in: (1) Section 102.51(a)(2)-(4) (documentation requirements for smallpox vaccine recipients), in the case of a deceased smallpox vaccine recipient. The survivor requester may submit a...

42 CFR 102.53 - Documentation a survivor must submit to be deemed eligible by the Secretary.

Code of Federal Regulations, 2010 CFR

2010-10-01

... AND HUMAN SERVICES VACCINES SMALLPOX COMPENSATION PROGRAM Required Documentation To Be Deemed Eligible... documentation required in: (1) Section 102.51(a)(2)-(4) (documentation requirements for smallpox vaccine recipients), in the case of a deceased smallpox vaccine recipient. The survivor requester may submit a...

Site Safety and Health Plan (Phase 3) for the treatability study for in situ vitrification at Seepage Pit 1 in Waste Area Grouping 7, Oak Ridge National Laboratory, Oak Ridge, TN

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

Spalding, B.P.; Naney, M.T.

1995-06-01

This plan is to be implemented for Phase III ISV operations and post operations sampling. Two previous project phases involving site characterization have been completed and required their own site specific health and safety plans. Project activities will take place at Seepage Pit 1 in Waste Area Grouping 7 at ORNL, Oak Ridge, Tennessee. Purpose of this document is to establish standard health and safety procedures for ORNL project personnel and contractor employees in performance of this work. Site activities shall be performed in accordance with Energy Systems safety and health policies and procedures, DOE orders, Occupational Safety and Healthmore » Administration Standards 29 CFR Part 1910 and 1926; applicable United States Environmental Protection Agency requirements; and consensus standards. Where the word ``shall`` is used, the provisions of this plan are mandatory. Specific requirements of regulations and orders have been incorporated into this plan in accordance with applicability. Included from 29 CFR are 1910.120 Hazardous Waste Operations and Emergency Response; 1910.146, Permit Required - Confined Space; 1910.1200, Hazard Communication; DOE Orders requirements of 5480.4, Environmental Protection, Safety and Health Protection Standards; 5480.11, Radiation Protection; and N5480.6, Radiological Control Manual. In addition, guidance and policy will be followed as described in the Environmental Restoration Program Health and Safety Plan. The levels of personal protection and the procedures specified in this plan are based on the best information available from reference documents and site characterization data. Therefore, these recommendations represent the minimum health and safety requirements to be observed by all personnel engaged in this project.« less

Cargo Movement Operations System (CMOS) Software Requirements Specification Increment II

DTIC Science & Technology

1990-05-17

NO [ ] COMMENT DISPOSITION: ACCEPT [ ] REJECT [ ] COMMENT STATUS: OPEN [ ] CLOSED [ ] Cmnt Page Paragraph No. No. Number Comment 1. 6 Table 1.2 Change SC1.4 to SC14. 2. 11 2.1.3.5 Add the following document: Preliminary Interface Design Document (IDD) for CMOS Increment I, CDRL A008, DCN: 3231 IDD *182*.01, April 9, 1990. 3. 19 3.1.19 In the "Brief Description" paragraph, line 12, hyphenate the word "off line". 4. 25 Fig. 3.2b The number ř" at the top of this figure is out of order. The preceding figure is Ŕ" and the

78 FR 74222 - Hours of Service of Drivers: Oregon Trucking Associations; Application for Exemption

Federal Register 2010, 2011, 2012, 2013, 2014

2013-12-10

... a limited exemption from the 30-minute rest-break requirement of the Agency's hours-of-service... including the specific section of this document to which each comment applies, and provide a reason for each... decision of the Agency must be published in the Federal Register (49 CFR 381.315(b)) with the reasons for...

The Autism Mental Status Exam: Sensitivity and Specificity Using DSM-5 Criteria for Autism Spectrum Disorder in Verbally Fluent Adults

ERIC Educational Resources Information Center

Grodberg, David; Weinger, Paige M.; Halpern, Danielle; Parides, Michael; Kolevzon, Alexander; Buxbaum, Joseph D.

2014-01-01

The phenotypic heterogeneity of adults suspected of autism spectrum disorder (ASD) requires a standardized diagnostic approach that is feasible in all clinical settings. The autism mental status exam (AMSE) is an eight-item observational assessment that structures the observation and documentation of social, communicative and behavioral signs and…

27 CFR 73.31 - May I submit forms electronically to TTB?

Code of Federal Regulations, 2010 CFR

2010-04-01

... requirement in this chapter, only if: (a) We have published a notice in the Federal Register and on our Web... Register and on our Web site as stated above; (c) You submit the electronic form to an electronic document receiving system that we have designated for the receipt of that specific form; and (d) The electronic form...

NextGen Avionics Roadmap Version 2.0

DTIC Science & Technology

2011-09-30

Avoid system (e.g. self -separation system) to be specifically authorized and delegated authority by the air traffic service provider in...provide any traffic flow management services within self -separation airspace. Aircraft must meet equi- page requirements to enter self -separation... traffic management systems and aircraft avionics systems. Aviation stakeholders will also benefit from reading this document because it provides a

Using LibQUAL+[R] Survey Results to Document the Adequacy of Services to Distance Learning Students for an Accreditation Review

ERIC Educational Resources Information Center

Lewis, Janice S.

2011-01-01

Accreditation is critical to the viability of institutions of higher education. Each of the six regional groups that accredit two- and four-year institutions has standards specifically addressing online or distance learning. In general, these standards require institutions to show that distance learners have adequate access to appropriate library…

Stability studies needed to define the handling and transport conditions of sensitive pharmaceutical or biotechnological products.

PubMed

Ammann, Claude

2011-12-01

Many pharmaceutical or biotechnological products require transport using temperature-controlled systems to keep their therapeutic properties. There are presently no official guidelines for testing pharmaceutical products in order to define suitable transport specifications. After reviewing the current guidance documents, this paper proposes a methodology for testing pharmaceutical products and defining appropriate transport conditions.

Italian chapter of the International Society of cardiovascular ultrasound expert consensus document on training requirements for noncardiologists using hand-carried ultrasound devices.

PubMed

Pelliccia, Francesco; Palmiero, Pasquale; Maiello, Maria; Losi, Maria-Angela

2012-07-01

Hand-carried ultrasound devices (HCDs), also named personal use echo, are pocket-size, compact, and battery-equipped echocardiographic systems. They have limited technical capabilities but offer some advantages compared with standard echocardiographic devices due to their simplicity of use, immediate availability at the patient's bedside, transportability, and relatively low cost. Current HCDs are considered as screening tools and are used to complement the physical examination by cardiologists. Many noncardiologic subspecialists, however, have adopted this technologic advancement rapidly raising the concern of an inappropriate use of HCD by health professionals who do not have any specific training. In keeping with the mission of the International Society of Cardiovascular Ultrasound to advance the science and art of cardiovascular ultrasound and encourage the knowledge of this subject, the purpose of this Expert Consensus document is to focus on the training for all health care professionals considering the use of HCD. Accordingly, this paper summarizes general aspects of HCD, such as technical characteristics and clinical indications, and then details the specific training requirements for noncardiologists (i.e., training program, minimum case load, duration, and certification of competence). © 2012, Wiley Periodicals, Inc.

A Model-Based Approach to Engineering Behavior of Complex Aerospace Systems

NASA Technical Reports Server (NTRS)

Ingham, Michel; Day, John; Donahue, Kenneth; Kadesch, Alex; Kennedy, Andrew; Khan, Mohammed Omair; Post, Ethan; Standley, Shaun

2012-01-01

One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.

Superfund record of decision (EPA Region 9): Mather Air Force Base, Soil and Groundwater operable units, Sacramento, CA, June 21, 1996

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

NONE

The decision document presents the selected remedial actions for the Soil Operable Unit (OU) Sites and Groundwater OU Plumes, at the formerly active Mather Air Force Base (AFB), Sacramento County, California. The purpose of the Record of Decision (ROD) is to decide the appropriate level of remediation necessary to protect human health and the environment, and determine what requirements are applicable or relevant and appropriate requirements (ARARs) based on the groundwater beneficial use designation and site-specific conditions. The ROD has been divided into seven sections which specifically address the range of selected remedial actions for the Soil OU sites andmore » Groundwater OU plumes.« less

Homeopathy in the treatment of tubercular lymphadenitis (TBLN)--an Indian experience.

PubMed

Chand, S Kusum; Manchanda, R K; Batra, Sudhir; Mittal, Renu

2011-07-01

Tuberculosis (TB) has been known since antiquity. In spite of effective antibiotic treatment, it is still a major worldwide public health problem. Endogenous factors are important in the development of active disease. Homeopathic medicines have the potential for immune-modulation and hence to influence endogenous factors in disease. In India, patients with tubercular lymphadenitis (TBLN) often consult homeopaths but such cases are seldom documented. The objective of the present study is to document such experience. A retrospective exploratory study of 25 positively diagnosed cases of TBLN has lead to the development of a homeopathic regime consisting of a patient specific constitutional medicine, one disease specific biotherapy (Tuberculinum) and Silicea 6x as supportive medicine. Homeopathy can be used as a complement to conventional anti tubercular treatment (ATT) with beneficial results. Further validation in controlled trials with immunological markers is required. Copyright © 2011 The Faculty of Homeopathy. Published by Elsevier Ltd. All rights reserved.

OSH technical reference manual

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

Not Available

1993-11-01

In an evaluation of the Department of Energy (DOE) Occupational Safety and Health programs for government-owned contractor-operated (GOCO) activities, the Department of Labor`s Occupational Safety and Health Administration (OSHA) recommended a technical information exchange program. The intent was to share written safety and health programs, plans, training manuals, and materials within the entire DOE community. The OSH Technical Reference (OTR) helps support the secretary`s response to the OSHA finding by providing a one-stop resource and referral for technical information that relates to safe operations and practice. It also serves as a technical information exchange tool to reference DOE-wide materials pertinentmore » to specific safety topics and, with some modification, as a training aid. The OTR bridges the gap between general safety documents and very specific requirements documents. It is tailored to the DOE community and incorporates DOE field experience.« less

Waste treatability guidance program. User`s guide. Revision 0

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

Toth, C.

1995-12-21

DOE sites across the country generate and manage radioactive, hazardous, mixed, and sanitary wastes. It is necessary for each site to find the technologies and associated capacities required to manage its waste. One role of DOE HQ Office of Environmental Restoration and Waste Management is to facilitate the integration of the site- specific plans into coherent national plans. DOE has developed a standard methodology for defining and categorizing waste streams into treatability groups based on characteristic parameters that influence waste management technology needs. This Waste Treatability Guidance Program automates the Guidance Document for the categorization of waste information into treatabilitymore » groups; this application provides a consistent implementation of the methodology across the National TRU Program. This User`s Guide provides instructions on how to use the program, including installations instructions and program operation. This document satisfies the requirements of the Software Quality Assurance Plan.« less

Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems

NASA Technical Reports Server (NTRS)

Lutz, Robyn R.

1993-01-01

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

The 30/20 GHz flight experiment system, phase 2. Volume 3: Experiment system requirement document

NASA Technical Reports Server (NTRS)

Bronstein, L.; Kawamoto, Y.; Ribarich, J. J.; Scope, J. R.; Forman, B. J.; Berman, S. G.; Reisenfeld, S.

1981-01-01

An approach to the requirements document to be used to procure the system by NASA is presented. The basic approach is similar to the requirements document used in the commercial communication satellite. Enough detail requirements are given to define the system without tight constraints.